Forums

Parameters shown on Infobar are wrong.
System, FEC, Modulation, and Polarisation are all wrong.

Here are a couple of examples:

C4 HD, on 28E. Real parameters: DVB-S2, 8PSK, 2/3. Infobar shows: DVB-S, QPSK, Auto.

BBC HD, on 28E. Real parameters: DVB-S2, QPSK, 8/9. Infobar shows: DVB-S, QPSK, Auto.

Also anything with circular polarisation shows as "C" when it should show as "CR" or "CL".

I've had a look in pliExpertInfo.py as I thought something was mapped wrong in there but the data is already faulty when it is imported by service.frontendInfo() so it looks like an error in E2.

This could indeed happening sometimes . Especially when you have a box with a tuner that can do FEC and modulation type or so automatically.... Once in the settings this is "poked" correct it takes "the good" values from that....

From the curculare polarization I was not aware yet...

Well it happens on the Vu Duo too and that does not do Auto FEC for DVB-S2. Anyway in theory Auto FEC doesn't exist in DVB-S2.

This could indeed happening sometimes . Especially when you have a box with a tuner that can do FEC and modulation type or so automatically.... Once in the settings this is "poked" correct it takes "the good" values from that....

From the curculare polarization I was not aware yet...

This used to be fine in the past so I can't see how it can be a hardware issue. It doesn't display the correct parameters on the Vu+ Duo and Vu+ Ultimo. I don't have any other receivers to try. Can anyone who is using a different receiver from these two comment on whether these parameters are wrongly displayed on their infobar.

I can check on my 800se when I get back home.
Can you please give more examples of such channels?
I can't access Astra 1N, so I cannot check the 2 examples given in the first post.

ET-9100 and Vu+Duo here, both with OpenPLi 2.1 rather latest.

I had a similar encounter just a few days ago:

my channel search is allways done on the ET and the resulting lamedb is then copied to the VU.
the AutoMotorSport HD on 23.5°E worked fine on the ET but yielded a "Tuning failed" on the VU.

when I checked the channel infos with dreamset I found out that the channel in the lamedb was definitely with the wrong params compared to the listing in KingsOfSat.
but the ET did produce a picture correctly anyway whereas the VU did not.

I then did a manual search with the settings found at KingOfSat, replicated those to the VU as well and it worked.

Anyway there was nothing wrong with the display of the parameters in the extended Infobar - it was always displayed what in the lamedeb was found.

Razorback
Veranderd door razorback, 29 februari 2012 - 10:21

- it was always displayed what in the lamedeb was found.

There we go....

when I checked the channel infos with dreamset I found out that the channel in the lamedb was definitely with the wrong params compared to the listing in KingsOfSat.
but the ET did produce a picture correctly anyway whereas the VU did not.

That's a completely different issue. The ET9x00 and Vu+ Ultimo/Uno have blindscan capable tuners so you can feed them any nonsense values as long as the frequency and polarisation are correct. The Duo is not blindscan capable so does need the correct parameters to do a search. But once the scan is done the values displayed on the infobar should correspond with the values stored in lamedb and that is not happening. If this really is a hardware issue why did the info bar display the correct values in the past?

Anyway if I do a blindscan for C4 HD it returns correct values for System and Modulation so why doesn't it display these values correctly on the infobar? The only thing the tuner of the Ultimo gets wrong is FEC, which it lists as 3/4 for every single service that it finds (which is why your ET search won't work on your Duo).

....aaahhh....
maybe you got the wrong skin ???
shit happens, you know ??

I use HD-Glass latest and everything displays as listed in lamedb.

Unfortunately I can not really test it, because in the south of Vienna I cannot receive anything from Astra 2D (or 1N at that) because of the Spot beam - so the genuine BBC-HD is not visible for me from 28,2 (and I'm afraid so will be C4 HD as well).

R

....aaahhh....
maybe you got the wrong skin ???
shit happens, you know ??

How can it be the skin? The values are alreay wrong before they are imported into pliExpertInfo.py

well, I am definitely NOT a linux programmer - by far not - but I am familiar with strange behaviours of skins as an adventurous user.

values displayed on one skin correctly may come up with different values (or no values at all at that) on another.

maybe you want to check your lamedb - maybe your "blind scan" is the culprit and returns wrong values.
Try a manual scan with the proper values and then you might find the reason.

R
Veranderd door razorback, 29 februari 2012 - 14:27

shit happens, you know ??

Nope, it doesn't. It needs an asshole to be produced.........

maybe you want to check your lamedb

And maybe you should read my posts properly. I have already said the values don't correspond with lamedb and that it is happening before pliExpertInfo.py imports the parameters. There is nothing wrong with my lamedb or scans. This is confirmed if I go into the manual scan screen as these parameters are correctly displayed in there when the current transponder auto loads.

This never reach logical conclusion so I have decided to bump it with a bit more info.

Receiver: Vu+ Ultimo.

C4 HD, on 28E. Real parameters: DVB-S2, 8PSK, 2/3. Infobar shows: DVB-S, QPSK, Auto.

lamedb is correct. Have a look at my breakdown below. Everything in there looks correct:

/
011a0000:0814:0002
s 11126000:22000000:1:2:282:2:0:1:2:0:2

52d0:011a0000:0814:0002:25:0
Channel 4 HD
p:BSkyB,c:000901,c:020905,c:030901,c:040902,c:050001

lamedb transponder parameters:[list]
[*]Frequency in Hertz.
[*]Symbol rate in bits per second.
[*]Polarization: 0=Horizontal, 1=Vertical, 2=Circular Left, 3=Circular right.
[*]Forward Error Control (FEC): 0=Auto, 1=1/2, 2=2/3, 3=3/4 4=5/6, 5=7/8, 6=3/5, 7=4/5, 8=8/9, 9=9/10.
[*]Orbital Position: in degrees East: 130 is 13.0E, 192 is 19.2E. Negative values are West -123 is 12.3West.
[*]Inversion: 0=Auto, 1=On, 2=Off
[*]Flags (Only in version 4): Field is absent in version 3.
[*]System: 0=DVB-S 1=DVB-S2.
[*]Modulation: 0=Auto, 1=QPSK, 2=8PSK, 3=QAM16.
[*]Rolloff (Only used in DVB-S2): 0=0.35, 1=0.25, 3=0.20
[*]Pilot (Only used in DVB-S2): 0=Auto, 1=Off, 2=On.
[/list]
Freq :Symb :F:Orb:I:F:S:M:R:P

11126000:22000000:1:2:282:2:0:1:2:0:2

I take that to mean:[list]
[*]Freq: 11126000
[*]Symb: 22000000
[*]Pol: V
[*]FEC: 2/3
[*]Orb: 28.2E
[*]Inv: Off
[*]Sys: DVB-S2
[*]Mod: 8PSK
[*]Rol: 0.35
[*]Pil: on
[/list]
I've echo'ed "fedata" and this is what it returns:

{'inversion': 'On', 'tuner_signal_quality': 63568, 'modulation': 'QPSK', 'tuner_type': 'Satellite', 'symbol_rate': 22000000, 'system': 'DVB-S', 'polarization_abbreviation': 'V', 'tuner_state': 'LOCKED', 'polarization': 'Vertical', 'tuner_bit_error_rate': 0, 'fec_inner': 'Auto', 'orbital_position': 'Eutelsat 28A & Astra 1N/2A/2B(28.2E Ku-band)', 'frequency': 11126000, 'tuner_signal_quality_db': None, 'tuner_locked': 1, 'tuner_number': 0, 'tuner_synced': 1, 'tuner_signal_power': 45864}

So why does that not correspond with any of the following which all contain the correct data:[list]
[*]lamedb
[*]satellites.xml
[*]the manual scan screen
[/list]
Veranderd door Huevos, 9 maart 2012 - 01:29

Hi Huevos,
I would like to give it a try but unfortunately I cannot receive Astra 1N/2D in my location because of the spotbeam.
Reception is good on all other Sats on 28.2 E

So could you post another sample I could use for a comparison ?
(e.g. channel 5 HD, FXHD, E4 HD, Atlantic HD etc.)
Or is this the one special channel where this occurs ?

thx

The biggest issue here for Huevos is that at least I cannot verify his issue.... Does someone else???

fedata comes from elsewere in enigma2.... so the "echo'd fedata" does verify that most likely this is not PliExtraInfo.py related... so somewere on the box this data get incorrect...
Veranderd door littlesat, 9 maart 2012 - 07:21

This 'fedata' seems like the data which the frontend returns as status.
And the 'FEC' is returned as auto, I've seen that before.

(In the menu, under 'Information', the FEC from the frontend status would get replaced by the transponder property, if it is 'auto'. So usually you would not even notice that the frontend returns auto.)

Apart from the FEC, what else is wrong?

Ok, I am going to start fresh so anyone can replicate this exactly (using a 19E transponder).

Vu+ Ultimo,
Flash with a virgin copy of OpenPli (OpenPLi-2.1-beta-vuultimo-20120309_usb.zip),
Configure tuner for 19E,
Manual scan of transponder, (DVB-S2, 11362, H, 22000, 2/3, 8PSK)
Channel = Das Erste HD

Info bar displays: DVB-S, 11362, H, 22000, Auto, QPSK, 19.2E.

Pieterg, fedata is feraw after it has gone through the method convertToHumanReadable(). Before it goes through that method it looks like this:

{'inversion': 1, 'tuner_signal_quality': 65535, 'modulation': 1, 'tuner_type': 'DVB-S', 'symbol_rate': 22000000, 'system': 0, 'tuner_state': 'LOCKED', 'polarization': 0, 'tuner_bit_error_rate': 0, 'fec_inner': 0, 'orbital_position': 192, 'frequency': 11361000, 'tuner_signal_quality_db': None, 'tuner_locked': 1, 'tuner_number': 0, 'tuner_synced': 1, 'tuner_signal_power': 51760}
Veranderd door Huevos, 9 maart 2012 - 13:36

Problem of VU or all boxes ?
My dm800se: ARD DVB-S2 11361 H 21997 2/3 8PSK 19.2E

feraw = service.frontendInfo.getAll() with 'original' set to False.
So the data comes directly from FE_GET_FRONTEND (and FE_GET_PROPERTY).

So whatever is in feraw, is simply the status as the frontend reports it.