22 replies to this topic

[kalehrl]

Hi

I noticed that when I switch to a DVB-S2 transponder, the info given is always DVB-S.
The info shown in webif is correct - DVB-S2.
Is this a bug maybe?

Attached Files

•  screenshot.jpg   93.25KB   51 downloads

Edited by kalehrl, 7 March 2012 - 21:57.

[Dimitrij]

DVB-T,DVB-C

[kalehrl]

Sorry but I don't understand.
Are you saying that the available options are DVB-S, DVB-T and DVB-C?
Maybe DVB-S2 should be added.

[littlesat]

You're right.. even in the service information menu there is always DVB-S... without the 2.... Soon I'll taka a look into that...

And I already get it... The tuner_type is displayed there... I should change that to system...

frontendData.get("system") (from pliExpertInfo)....

Edited by littlesat, 8 March 2012 - 08:02.

[Erik Slagter]

I think it's indeed intentional, to differentiate between DVB-S/DVB-C/DVB-T not between DVB-S/DVB-S2.

[littlesat]

I'll change that today or tomorrow. I'll add a "tuningSystem" function that will return DVB-S2, DVB-S, DVB-T or DVB-C.... (which later e.g. could be expand to DVB-T2 and DVB-C2)... this will check the tuner type and in case it is DVB-S it will return the poper mode... when it is DVB-T/C it will just return that.

In addition at the information->current service screen this could be somehow "adapted"... There we also see only DVB-S (in case it might be DVB-S2).

Thanks for reporting and please hold-on....

Edited by littlesat, 8 March 2012 - 10:47.

[Huevos]

I reported this the other day along with all the other errors on the info bar but just got a negative response.
Thread here -> http://openpli.org/f...obar-are-wrong/

Glad to see you've had a more positive reply.

The data E2 is supplying PliExpertInfo.py is just plain incorrect

Edited by Huevos, 8 March 2012 - 13:34.

[Erik Slagter]

Not only that information. The information about FEC is incorrect as well (always "auto").

[littlesat]

I reported this the other day along with all the other errors on the info bar but just got a negative response.
Thread here -> http://openpli.org/f...obar-are-wrong/

Glad to see you've had a more positive reply.

That time is was hooked to a different issue... and in fact it is a different issue, namely the lamedb issue in combination with a tuner that can correct incorrect parameters by it's own....

The DVB-S with or without the two is different... e.g. in the previous Coder the pliExertInfo.py this was displayed in the correct way....

[Huevos]

I reported this the other day along with all the other errors on the info bar but just got a negative response.
Thread here -> http://openpli.org/f...obar-are-wrong/

Glad to see you've had a more positive reply.

That time is was hooked to a different issue... and in fact it is a different issue, namely the lamedb issue in combination with a tuner that can correct incorrect parameters by it's own....

The DVB-S with or without the two is different... e.g. in the previous Coder the pliExertInfo.py this was displayed in the correct way....

Ok, so you are saying it is down to the hardware, right? Well in that case just a couple of questions:

1) Why did it display correctly in the past?
2) Why does the screen grab attached show the correct info?

Attached Files

•  screenshot.jpg   30.91KB   41 downloads

[littlesat]

1) Because your lamedb was not fault then?
2) How did you get this grab?

[Huevos]

Not only that information. The information about FEC is incorrect as well (always "auto").

Also CR and CL polarisation both report as C... 8PSK reports as QPSK...

[littlesat]

Nice..... here do you see circular polarization.... I get this date from standard E2 code. Then there it is already faulty and should be changed there.... So indeed there might be some extra work there.... But nice to report that Circular polarization does only indicate a C... (better should be L and R together with V H to keep it to one digit.)

But why your screendump show better tuning data I really do not know....????

Edited by littlesat, 8 March 2012 - 14:29.

[littlesat]

I just checked based on the code... Circular polarization should be displayed as H V R and L..... so no C??? Do you have a schreengrab were it is a C??

When the FEC is auto then this is an issue from your lamedb....

Edited by littlesat, 8 March 2012 - 14:35.

[Huevos]

1) Because your lamedb was not fault then?
2) How did you get this grab?

1) Because your lamedb was not fault then?
2) How did you get this grab?

I just loaded glassysutil 5 minutes ago purely to see what it reported.

But also see attached screen grab below. This is from the "manual scan" screen which automatically loads the current transponder and all info in there is correct.

Also 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

In English I take that to mean:[list=1]
[*]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]

Attached Files

•  screenshot.jpg   181.49KB   29 downloads

[littlesat]

And the screendump from normal pliHD skin now?

[Huevos]

No, it's from a VIX skin, but like I said the error is in the data imported from E2 by PliExpertInfo.py, so it is happening before the skin. The "C" error might have been introduced by me. I need to check on that. I guess it is in the method ConvertToHumanReadable() but I've forgotten which file that is located in. What file did you check those polarisation settings in?

And are you in agreement there is nothing wrong with the lamedb settings I posted above?

[littlesat]

PliExtraInfo gets except from the sat polar position in degrees everything from ConvertToHumanReadable... that is located in Tools...... so if there something is wrong.... the info on your skin is also wrong.... ... This is therefore not PliExtraInfo related

But I understand now that you made changes to ConvertToHumanReadable.... so?????

I just committed a fix for the DVB-S/DVB-S2 indication.

Pobably in ViX you have a correct lamedb......

Edited by littlesat, 8 March 2012 - 19:18.

[kalehrl]

Thank you littlesat.
Now DVB-S2 is shown correctly.

[Huevos]

I just committed a fix for the DVB-S/DVB-S2 indication.

What was the fix if you don't mind me asking?