Jump to content


Photo

t2mi_plp_id


  • Please log in to reply
4 replies to this topic

#1 Huevos

  • Senior Member
  • 1,937 posts

+104
Excellent

Posted 8 August 2018 - 21:08

t2mi_plp_id from satellites.xml. What uses this in enigma?



Re: t2mi_plp_id #2 athoik

  • PLi® Core member
  • 7,415 posts

+261
Excellent

Posted 8 August 2018 - 21:52

Nothing yet.

There was some discussion about adding build-in support for t2-mi in enigma2 but no progress yet.
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: t2mi_plp_id #3 Huevos

  • Senior Member
  • 1,937 posts

+104
Excellent

Posted 8 August 2018 - 22:12

Ah, is that what McCelliot's tutorials were about?


Edited by Huevos, 8 August 2018 - 22:12.


Re: t2mi_plp_id #4 athoik

  • PLi® Core member
  • 7,415 posts

+261
Excellent

Posted 9 August 2018 - 05:32

No, those are using today's enigma2 + astra-sm build in t2-mi de-encapsulator in order to get those channels.

They do not use t2mi_plp_id.
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: t2mi_plp_id #5 Huevos

  • Senior Member
  • 1,937 posts

+104
Excellent

Posted 9 August 2018 - 11:38

Thanks, so I'm not going to add this to OE-A version for the moment. Doesn't seem to make sense showing multiple transponders in satellites.xml where there is no support for the feature. Just going to slow down scans.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users