English > VU+ - VU Duo Settopbox

Blindscan on VU+ Solo2 with OpenPLI image

<< < (9/9)

Dima73:

--- Zitat von: Sundtek am November 20, 2016, 02:02:51 Nachmittag ---What does ls /dev/dvb/frontend* show up?

--- Ende Zitat ---
mediaclient old
yes, /dev/dvb/adapter0/frontend11 work

--- Code: ---root@vusolo4k:~# /opt/bin/mediaclient --blindscan 11
root@vusolo4k:~# /opt/bin/mediaclient --blindscan /dev/dvb/adapter0/frontend11
Succeeded this device supports Hardware Blindscan
Scanning 13V Lowband
MODE: DVB-S  FREQUENCY(MHz): 10718 SYMBOL_RATE: 27500 MODULATION: QPSK VOLTAGE: 13V TONE: OFF
MODE: DVB-S2 FREQUENCY(MHz): 10757 SYMBOL_RATE: 27499 MODULATION: PSK8 VOLTAGE:
--- Ende Code ---

I had just made:
https://github.com/OpenPLi/enigma2-plugins/blob/master/blindscan/src/plugin.py#L788

test

--- Code: ---root@vusolo4k:~# //opt/bin/mediaclient
//opt/bin/mediaclient: line 1: syntax error: unexpected "("
root@vusolo4k:~# uname -a
Linux vusolo4k 3.14.28-1.8 #1 SMP Fri Sep 9 01:28:49 EEST 2016 armv7l GNU/Linux

--- Ende Code ---

Dima73:
Another question...

--- Code: ---Dear Sundtek,


Recently we added DVB API v5 statistics into Enigma2 (see: https://github.com/O...7cb9b043797834)

I've got a request from a user that since above commit dB/snr caclulation is broken for Sundtek DVB-T (III).

I guess that you are using DVB API v5 statistics!

Could you please fill DVB API v5 statistics properly?

Currently we need at least the following: DTV_STAT_SIGNAL_STRENGTH scaled as FE_SCALE_RELATIVE, DTV_STAT_CNR scaled as FE_SCALE_DECIBEL and FE_SCALE_RELATIVE

Example values:

DTV_STAT_SIGNAL_STRENGTH S: 59172 U: 59172 L: 1 Scale: FE_SCALE_RELATIVE
DTV_STAT_CNR S: 12453 U: 12453 L: 2 Scale: FE_SCALE_DECIBEL
DTV_STAT_CNR S: 51007 U: 51007 L: 2 Scale: FE_SCALE_RELATIVE

Please let me know of your thoughts.

Best Regards,
Athoik on behalf of OpenPLi team
--- Ende Code ---

for  DVB API v5
Sundtek DVB-T (III) snr always 99%
Sundtek DVB-S/S2 (IV) snr always 88-89%

My workaround has been removed recently:
https://github.com/OpenPLi/enigma2/commit/abaabfdad4f278cbcfcf7e4915d2a8e20486bfac

--- Code: ---When either signalquality or signalqualitydb are nonzero, the driver
implements the DTV_STAT_CNR property.
And we have to trust the driver to report the correct values, no need to
make any exceptions.

Perhaps this commit was meant to force snr percentage to dB calculation
for Sundtek, but in that case a different, more generic fix should be
made to calculate dB values based on the FE_SCALE_RELATIVE value
reported by the DTV_STAT_CNR property.
--- Ende Code ---

Sundtek:
use this one for ARM

Dima73:

--- Zitat von: Sundtek am November 20, 2016, 04:54:01 Nachmittag ---use this one for ARM

--- Ende Zitat ---
Thanks,work fine...

--- Code: ---root@vusolo4k:~# mediaclient --blindscan 11
waiting for 1 seconds
Scanning 13V Lowband
OK DVB-S 968361 27500 QPSK V OFF
OK DVB-S2 1006490 27499 8PSK V OFF
OK DVB-S2 1045633 27500 8PSK V OFF
OK DVB-S2 1083311 27501 8PSK V OFF
OK DVB-S 1122257 27500 QPSK V OFF
OK DVB-S2 1160689 27501 8PSK V OFF
....

--- Ende Code ---

Dima73:
Sundtek
About this question...
http://support.sundtek.com/index.php/topic,1833.msg17003.html#msg17003

You can make changes to the drivers.
Return the DTV_STAT_SIGNAL_STRENGTH / DTV_STAT_CNR value as zero.
Or at least add a key to start the driver DTV_STAT_SIGNAL_STRENGTH/ DTV_STAT_CNR S with zero.

Please help :(.

Navigation

[0] Themen-Index

[*] Vorherige Sete