Edision Mio+ DVBS2X vs DVBS2

[cyberham]

I am monitoring 81W 12010 V 13333. I find I can receive and lock onto a stable 10 dB data transponder here on 24/7 using Tuner A (DVB-S2X) but using Tuner B (DVB-S2) I receive nothing. I can't even tell there is a fairly strong transponder on that frequency. I recall encountering this years ago when monitoring a data transponder on 22W. Same results I'm seeing now on 81W. I had a different Mio+ box in those years.

Am I right to conclude that there is nothing wrong with my receiver but simply that there are some transponders which DVB-S2X can handle whereas DVB-S2 can't?

[el bandido]

DVB-S2X could be thought of as an extension of DVB-S2. DVB-S2X Is not defined in Linux TV as of today. Vu+ (Bless Their Hearts) defined DVB-S2X in their Factory images which made DVB-S2X transponders display correctly as DVB-S2X.

Enigma2 images mostly do not have provisions needed to properly identify DVB-S2X transponders, so the DVB-S2X transponders are shown as DVB-S2 in most enigma2 images.

The FEC is different in DVB-S2X. Most enigma2 images identify the DVB-S2X FEC as "Auto".

Having said this, Any DVB-S2 transponder that has a FEC of "Auto" in a blindscan may be DVB-S2X. The transponder you mention may be DVB-S2X which would explain Why the other tuner does not show a signal. The second tuner in the MIO+ receiver is a poor performer when compared to the first satellite tuner. So your transponder may not be DVB-S2X after all. It just may be in a format that the second tuner cannot understand or is not capable of receiving.

[cyberham]

The data transponder on 81W is identified with an auto FEC. The transponder is important since it's the only full-time tp on 81W. Now that I've zeroed the fixed dish on 81W it's no longer important if I can receive the data transponder. This is why I've put my system back on Tuner A now with the fixed dish on Tuner B. I would have paid the extra for a better quality Tuner B.

[el bandido]

[Only registered and activated users can see links]