t2mi_plp_id from satellites.xml. What uses this in enigma?
t2mi_plp_id
Begonnen door: Huevos, 08 aug 2018 21:08
Er zijn 4 reacties in dit onderwerp
Re: t2mi_plp_id #2
-
- PLi® Core member
- 8458 berichten
+327
Excellent
Geplaatst op 8 augustus 2018 - 21:52
Nothing yet.
There was some discussion about adding build-in support for t2-mi in enigma2 but no progress 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
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
Re: t2mi_plp_id #3
-
- PLi® Contributor
- 4244 berichten
+158
Excellent
Geplaatst op 8 augustus 2018 - 22:12
Ah, is that what McCelliot's tutorials were about?
Veranderd door Huevos, 8 augustus 2018 - 22:12
Re: t2mi_plp_id #4
-
- PLi® Core member
- 8458 berichten
+327
Excellent
Geplaatst op 9 augustus 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.
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
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
Re: t2mi_plp_id #5
-
- PLi® Contributor
- 4244 berichten
+158
Excellent
Geplaatst op 9 augustus 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.
1 gebruiker(s) lezen dit onderwerp
0 leden, 1 bezoekers, 0 anonieme gebruikers
