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
Edited by kalehrl, 7 March 2012 - 21:57.
Posted 8 March 2012 - 07:59
Edited by littlesat, 8 March 2012 - 08:02.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 8 March 2012 - 10:39
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 8 March 2012 - 10:46
Edited by littlesat, 8 March 2012 - 10:47.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 8 March 2012 - 13:30
Edited by Huevos, 8 March 2012 - 13:34.
Posted 8 March 2012 - 13:47
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 8 March 2012 - 13:50
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....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.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 8 March 2012 - 14:21
Ok, so you are saying it is down to the hardware, right? Well in that case just a couple of questions: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....
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 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....
Posted 8 March 2012 - 14:28
Edited by littlesat, 8 March 2012 - 14:29.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 8 March 2012 - 14:34
Edited by littlesat, 8 March 2012 - 14:35.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 8 March 2012 - 15:24
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.1) Because your lamedb was not fault then?
2) How did you get this grab?
Posted 8 March 2012 - 16:45
Posted 8 March 2012 - 19:17
Edited by littlesat, 8 March 2012 - 19:18.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
0 members, 7 guests, 0 anonymous users