Sundtek Support Forum

English => VU+ - VU Duo Settopbox => Thema gestartet von: v1c10u5 am Februar 01, 2015, 08:14:59 Nachmittag

Titel: Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: v1c10u5 am Februar 01, 2015, 08:14:59 Nachmittag
Hello,

I recently purchased your your MediaTV Digital Home and managed to install it succesfully on my VU+ solo2 running the latest OpenPLI image.
Currently the only option to scan for channels is through the Manual scan.
The Automatic scan is giving me:"ERROR - failed to scan (error starting scanning)!".
Blindscan 1.4 and Fast scan are not recognizing the DVB-C tuner in the Tuner option inside the plugin. (I can only scan the built-in Tuner A and Tuner B).

Any ideas what i'm doing wrong or how can i get the blindscan plugin to recognize your usb tuner?

Thanks in advance,
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am Februar 01, 2015, 11:51:16 Nachmittag
Blindscan is not supported by external tuners at the moment, we will release an update within the next 1-2 Weeks which finally will add support for this.

For now you need to scan one frequency manually and enable the network scan. This should discover all Transponders in your network.
Please note even we add support for Blindscan in the near future this will only work with tuners from 2014 on (earlier versions do not have hardware support for that).
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: v1c10u5 am Februar 02, 2015, 02:12:04 Nachmittag
Thank you for the fast and informative reply.

Do you by any chance know how i could check if my solo2 hardware supports blindscan or not?
And also do you have any idea why the Automatic scan is giving me an error message?
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am Februar 02, 2015, 11:18:19 Nachmittag
When did you buy the Tuner?

All tuners from 2014 support Blindscan.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 08, 2015, 05:09:09 Nachmittag
Blindscan support is available with the latest driver update.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 07, 2016, 07:13:47 Nachmittag
openpli 4 et8500




et8500 login: root
root@et8500:~# /opt/bin/mediaclient  --blindscan 5
waiting for 1 seconds
Scanning 13V Lowband
OK 968531 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1006579 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1045411 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1083876 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1121689 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1199053 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1241576 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1283529 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1366119 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1407853 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1449517 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1527929 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1565821 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1642485 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1719620 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1758435 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1790734 22000 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1834496 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1873110 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1911252 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1976636 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2053649 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2091872 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 35899 ms (found 23 muxes)
Scanning 18V Lowband
OK 977039 30000 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1024288 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1064483 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1102519 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1141275 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1179779 30000 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1220971 29700 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1262442 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1304004 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1344848 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1387013 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1583393 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1659924 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1699306 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1737222 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1853449 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1891774 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1930355 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1996403 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2034334 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2073045 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 33276 ms (found 21 muxes)
Scanning 13V Highband
OK 985159 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1023445 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1061877 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1127794 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1165629 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1242792 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1281108 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1319362 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1357169 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1472277 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1587338 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1626211 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1702675 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1741065 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1779255 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1817391 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1865801 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1919845 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1957901 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1996884 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 35692 ms (found 20 muxes)
Scanning 18V Highband
OK 1004153 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1042628 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1080693 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1146236 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1185000 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1223392 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1261954 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1300078 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1337908 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1376715 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1453236 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1491829 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1530255 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1568463 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1606407 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1645320 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1683136 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1721839 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1759809 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1837006 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1875705 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1976975 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2053411 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2092282 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 34548 ms (found 24 muxes)
root@et8500:~#

scaning sat 13e

Question what is the frequency?
The second column?
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 07, 2016, 07:39:08 Nachmittag
Is that Ku-Band? The frequency is usually the second column. The third column is the symbol rate.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 07, 2016, 07:45:35 Nachmittag
Yes Ku band 13E
In the second column the wrong digit.
if freq < 4201000 and freq > 2999000 :
band = 'C'
self.is_c_band_scan = True
elif freq < 12751000 and freq > 10700000 :
band = 'Ku'
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 07, 2016, 08:14:45 Nachmittag
It depends how you scan, I see that the value is in the intermediate band 950-2150 MHz you need to re-calculate it by yourself.

/opt/bin/mediaclient --blindscan /dev/dvb/adapter1/frontend0 will retrieve the Ku-Band frequencies.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 07, 2016, 08:21:16 Nachmittag
It depends how you scan, I see that the value is in the intermediate band 950-2150 MHz you need to re-calculate it by yourself.

/opt/bin/mediaclient --blindscan /dev/dvb/adapter1/frontend0 will retrieve the Ku-Band frequencies.
/dev/dvb/adapter1/frontend0 busy DVB-T
root@et8500:~# /opt/bin/mediaclient --blindscan /dev/dvb/adapter1/frontend0
Succeeded this device supports Hardware Blindscan
MODE: DVB-T FREQUENCY: 474000000 BANDWIDTH: 8000000
MODE: DVB-T FREQUENCY: 490000000 BANDWIDTH: 8000000
^C
Please write re-calculate command :)
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 07, 2016, 09:57:00 Nachmittag
What does /opt/bin/mediaclient -e show up? I guess you have more than one tuner attached.
I guess you have used the wrong tuner. try adapter2 then possibly.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 08, 2016, 07:13:41 Vormittag
What does /opt/bin/mediaclient -e show up? I guess you have more than one tuner attached.
I guess you have used the wrong tuner. try adapter2 then possibly.
oot@et8500:~# /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [MediaTV Digital Home III (EU)]  DVB-C, DVB-T, DVB-T2, REMOTE-CONTROL
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 1-1.2
  [SERIAL]:
     ID: U150511201402
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

device 1: [Sundtek SkyTV Ultimate V (2015)]  DVB-S/S2, ANALOG-TV, REMOTE-CONTROL, OSS-AUDIO
  [INFO]:
     STATUS: STANDBY
  [BUS]:
     ID: 1-1.3
  [SERIAL]:
     ID: U151218192625
  [DVB-S/S2]:
     FESTATUS: STANDBY
     LNBVOLTAGE: DISABLED
     LNBSUPPLY: ACADAPTER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter2/frontend0
     DVR: /dev/dvb/adapter2/dvr0
     DMX: /dev/dvb/adapter2/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput1
  [OSS]:
     OSS0: /dev/dsp0

root@et8500:~#
ok,excellent answers
root@et8500:~# /opt/bin/mediaclient --blindscan /dev/dvb/adapter2/frontend0
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): 10756 SYMBOL_RATE: 27499 MODULATION: PSK8 VOLTAGE: 13V TONE: OFF
MODE: DVB-S2 FREQUENCY(MHz): 10795 SYMBOL_RATE: 27500 MODULATION: PSK8 VOLTAGE: 13V TONE: OFF
MODE: DVB-S2 FREQUENCY(MHz): 10833 SYMBOL_RATE: 27500 MODULATION: PSK8 VOLTAGE: 13V TONE: OFF
But...
I need this format for --blindscan [nim_socket]
I make support Sundtek in  plugin Blind scan.

Guess the number adapter[1? 2? 3? or 4???] can not be.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 08, 2016, 09:43:45 Vormittag
I think it is better to calculate it by yourself

                                                if(strcasecmp(band, "C-BAND")==0) {
                                                        frequency = 5150000-feparm.frequency;
                                                } else if(strcasecmp(band, "UNIVERSAL")==0) {
                                                        if (tone == SEC_TONE_ON) {
                                                                frequency=feparm.frequency+10600000;
                                                        } else {
                                                                frequency=feparm.frequency+9750000;
                                                        }
                                                } else {


There's C-band and Ku-band

Low Band V = 13V No tone
Low Band H = 18V No tone
High Band V = 13V + 22khz tone
High Band H = 18V + 22khz tone

edit: copied the wrong code snippet, the current one shows you how to calculate the frequency
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 08, 2016, 10:29:28 Vormittag
Sorry, this is С++.
I need Python code.
C-BAND? where does this matter?

OK 968531 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
MODE: DVB-S  FREQUENCY(MHz): 10718 SYMBOL_RATE: 27500 MODULATION: QPSK VOLTAGE: 13V TONE: OFF
this is egual value.Only different formats.

is 968531 need 10718 why?




Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 08, 2016, 11:06:06 Vormittag
C-Band is used in America, we also have users in the United States and Canada who use Settopboxes.

For Ku-Band:
MODE: DVB-S  FREQUENCY(MHz): 10718 SYMBOL_RATE: 27500 MODULATION: QPSK VOLTAGE: 13V TONE: OFF

it says 10718 MHz
while
OK 968531 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
is in KHz

10718XXX KHz = 968531 KHz + 9750000 (=10718531) -- since tone is off you only need to add 9750000, if tone would be on you would need to add 10600000


It's about the calculation itself and that one should be clear (regardless of the programming language).

For C-Band you need to calculate it that way:
cband_frequency = 5150000-tuner_frequency;

the tuner_frequency is always between 950 - 2150 MHz (950.000 - 2150.000 KHz)

This is an example for a C-Band Satellite:
http://www.lyngsat.com/Telkom-1.html

see the frequency they are comparable low compared with the Ku-Band Satellites.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 08, 2016, 12:32:20 Nachmittag
Thanks for the help.

But still full information would be more practical to get by for --blindscan [nim_socket]
Or add a response from drivers:
/opt/bin/mediaclient --frontend [nim_socket]
return /dev/dvb/adapterN/frontend0
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 08, 2016, 04:57:56 Nachmittag
I think you can just figure it out by doing cat /proc/bus/nim_sockets

it will show you nim_socket and the frontend number
The frontend number you can connect with /dev/dvb/adapter/frontendN
which you should be able to use with blindscan as well.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 08, 2016, 06:03:38 Nachmittag
Super
root@et8500:~# /opt/bin/mediaclient  --blindscan /dev/dvb/adapter0/frontend4
Succeeded this device supports Hardware Blindscan
MODE: DVB-T FREQUENCY: 474000000 BANDWIDTH: 8000000
MODE: DVB-T FREQUENCY: 490000000 BANDWIDTH: 8000000
^C
root@et8500:~# /opt/bin/mediaclient  --blindscan /dev/dvb/adapter0/frontend5
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: 13V TONE: OFF
MODE: DVB-S2 FREQUENCY(MHz): 10795 SYMBOL_RATE: 27500 MODULATION: PSK8 VOLTAGE: 13V TONE: OFF
^C
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 08, 2016, 10:45:46 Nachmittag
There is one problem.
Earlier, last year, each scan line ends '\n'
Now it's one line.

And
MODE: DVB-S2 FREQUENCY(MHz): 10757 SYMBOL_RATE: 27499 MODULATION: PSK8 VOLTAGE: 13V TONE: OFFPSK8 need 8PSK
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 09, 2016, 11:14:34 Vormittag
Please help, give me a command response DVB-C mode,I do not use DVB-C:
1)
/opt/bin/mediaclient --blindscan [nim_socket]

2)
/opt/bin/mediaclient --blindscan /dev/dvb/adapter0/frontend[nim_socket]
First, see [nim_socket]:
cat /proc/bus/nim_sockets
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 09, 2016, 11:41:55 Vormittag
I don't understand, we already have support for

/opt/bin/mediaclient --blindscan [nimsocket]

The modes and everything can either be picked up from /proc/bus/nim_sockets or the python structures itself within enigma2
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 09, 2016, 03:36:07 Nachmittag
I have to compare the answers DVB-C mode.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 09, 2016, 10:33:35 Nachmittag
Universal LNB
Scanning 18V Lowband
OK 1024288 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF

That's right?

FREQUENCY: 1024288+9750000
Polarisation: Horizontal

?
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Tryon am April 10, 2016, 10:34:31 Nachmittag
Super
root@et8500:~# /opt/bin/mediaclient  --blindscan /dev/dvb/adapter0/frontend4
Succeeded this device supports Hardware Blindscan
MODE: DVB-T FREQUENCY: 474000000 BANDWIDTH: 8000000
MODE: DVB-T FREQUENCY: 490000000 BANDWIDTH: 8000000
^C
root@et8500:~# /opt/bin/mediaclient  --blindscan /dev/dvb/adapter0/frontend5
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: 13V TONE: OFF
MODE: DVB-S2 FREQUENCY(MHz): 10795 SYMBOL_RATE: 27500 MODULATION: PSK8 VOLTAGE: 13V TONE: OFF
^C
Cleaner output?
root@et8500:~# mediaclient  --blindscan /dev/dvb/adapter0/frontend4
Succeeded this device supports Hardware Blindscan
MODE   FREQUENCY    BANDWIDTH
DVB-T  474.000        8
DVB-T  490.000        8
^C
root@et8500:~# mediaclient  --blindscan /dev/dvb/adapter0/frontend5
Succeeded this device supports Hardware Blindscan
Scanning 13V Lowband(TONE: OFF)
MODE   FREQUENCY(MHz) SYMBOL_RATE   POL     MODULATION
DVB-S     10718         27500        V       QPSK
DVB-S2    10757         27499        V       8PSK
DVB-S2    10795         27500        V       8PSK
^C
Can you confirm overlap of some results(like 11824 both in Lowband and highband)?
Also add option for scanning only 1 band(--range VL)?
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 10, 2016, 10:55:18 Nachmittag
Can you confirm overlap of some results(like 11824 both in Lowband and highband)?

which satellite?
I haven't noticed any overlapping results but I'm mainly using Astra 19.2 at Sundtek (though others could be used)

Zitat
Also add option for scanning only 1 band(--range VL)?

we certainly can do that, there are some more updates coming including a nice small streamingserver.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 11, 2016, 06:49:58 Vormittag

Can you confirm overlap of some results(like 11824 both in Lowband and highband)?

yes,full scan 13e
root@et8500:~# /opt/bin/mediaclient  --blindscan 5
waiting for 1 seconds
Scanning 13V Lowband
OK 968531 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1006579 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1045411 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1083876 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1121689 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1199053 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1241576 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1283529 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1366119 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1407853 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1449517 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1527929 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1565821 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1642485 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1719620 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1758435 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1790734 22000 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1834496 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1873110 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1911252 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1976636 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2053649 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2091872 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 35899 ms (found 23 muxes)
Scanning 18V Lowband
OK 977039 30000 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1024288 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1064483 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1102519 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1141275 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1179779 30000 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1220971 29700 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1262442 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1304004 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1344848 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1387013 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1583393 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1659924 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1699306 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1737222 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1853449 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1891774 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1930355 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1996403 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2034334 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2073045 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 33276 ms (found 21 muxes)
Scanning 13V Highband
OK 985159 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1023445 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1061877 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1127794 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1165629 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1242792 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1281108 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1319362 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1357169 27501 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1472277 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1587338 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1626211 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1702675 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1741065 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1779255 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1817391 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1865801 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1919845 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1957901 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1996884 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 35692 ms (found 20 muxes)
Scanning 18V Highband
OK 1004153 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1042628 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1080693 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1146236 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1185000 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1223392 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1261954 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1300078 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1337908 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1376715 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1453236 29901 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1491829 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1530255 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1568463 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1606407 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1645320 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1683136 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1721839 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1759809 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1837006 29899 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1875705 29900 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 1976975 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2053411 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
OK 2092282 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
scan took 34548 ms (found 24 muxes)
After channel scan for this frequency there a lot of wrong services.
When zap to on such a service,show message "Service not found!\n(SID not found in PAT)"
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 11, 2016, 07:55:08 Vormittag
The principle is (universal lnb):

OK frequency 27500 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
13V Lowband
-----------
Frequency: frequency KHz+9750000
Polarisation: vertical

13V Highband
-----------
Frequency: frequency KHz+10600000
Polarisation: vertical

18V Lowband
-----------
Frequency: frequency KHz+9750000
Polarisation: horizontal

18V Highband
Frequency: frequency KHz+10600000
Polarisation: horizontal


That's right?



Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 11, 2016, 12:29:11 Nachmittag
Should be right that way, the blindscan is okay we have tested this. If you get wrong channels then you have probably saved the wrong values (maybe mixed up KHz with MHz somewhere?)
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 14, 2016, 09:32:02 Vormittag
Should be right that way, the blindscan is okay we have tested this. If you get wrong channels then you have probably saved the wrong values (maybe mixed up KHz with MHz somewhere?)
Ок,this solved.

Next big problem...

example:
Scanning 13V Lowband
OK 1006579 27499 FEC_AUTO NOT_IMPLEMENTED INVERSION_OFF
We are aware of only three values-->frequency,symbol rate, polarisation
 +
orbpos

For enigma2 service scan need this values:
transponder = (frequency, symbolrate, polarisation, fec, inversion, orbpos, system, modulation, rolloff, pilot, tsid, onid)Substitute all the values automatically.
+ parm = eDVBFrontendParametersSatellite()
+ parm.orbital_position = self.orb_position
+ parm.polarisation = self.Sundtek_pol
+ frequency = ((int(data[1]) + self.offset) / 1000) * 1000
+ parm.frequency = frequency
+ symbol_rate = int(data[2]) * 1000
+ parm.symbol_rate = symbol_rate
+ parm.system = parm.System_DVB_S
+ parm.inversion = parm.Inversion_Off
+ parm.pilot = parm.Pilot_Off
+ parm.fec = parm.FEC_Auto
+ parm.modulation = parm.Modulation_QPSK
+ parm.rolloff = parm.RollOff_alpha_0_35
+ self.tmp_tplist.append(parm)
After scan tuner (sundtek sky tv ultimate 5) --> 0 channels found
After scan any internal tuner  --> more channels found (all values is same)

So.
It is a bug in the sundtek drivers.


Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 14, 2016, 12:30:21 Nachmittag
I see what you mean the values are incomplete compared with the "native scan" using adapterN/frontendN

I think that output is derived from the DVB-C scan, it will be updated with the next version.
The next version should be available around next week (due other updates as well).
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 14, 2016, 05:31:48 Nachmittag
The problem is related to the channel scan.
blindscan_13E_14-04-2016_18-17-04.xml
Please see:
<?xml version="1.0" encoding="iso-8859-1"?>

<!--
File created on Четверг, 14 of апреля 2016, 18:17:04
using et8500 receiver running Enigma2 image, version 2016-03-17,
image Openpli 4, with the Blind scan plugin

Search parameters:
Тюнер F: Sundtek DVB-S/S2 (IV) (0/0) (USB) (DVB-S2)
Satellite: 13.0E Eutelsat Hot Bird 13B/13C/13D
Start frequency: 10700MHz
Stop frequency: 12750MHz
Polarization: vertical and horizontal
Lower symbol rate: 2000
Upper symbol rate: 45000
Only save unknown tranponders: yes
Filter out adjacent satellites: up to 3 degrees
-->

<satellites>
<sat name="13.0E Eutelsat Hot Bird 13B/13C/13D" flags="0" position="130">
<transponder frequency="10774000" symbol_rate="27500000" polarization="0" fec_inner="0" system="0" modulation="1"/>
</sat>
</satellites>
After scan tuner (sundtek sky tv ultimate 5) --> 0 channels found
After scan any internal tuner  --> 2 channels found

Use manual scan, if set System_DVB_S2 --> scan tuner (sundtek sky tv ultimate 5) --> 2 channels found

It should not be.
This is a bug in the drivers.
It can be fixed?
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 14, 2016, 06:15:45 Nachmittag
Which satellite do you use with Blindscan?
Blindscan is currently set up for Astra 19.2 (and similar ones).
The blindscan will need some symbol rates pre-set (currently we have only hard-coded the ones which are common on Astra 19.2 / Thor5 / Hotbird )
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 14, 2016, 06:51:52 Nachmittag
Satellite: 13.0E Eutelsat Hot Bird 13B/13C/13D
this feed transponder
<transponder frequency="10774000" symbol_rate="27500000" polarization="0" fec_inner="0" system="0" modulation="1"/>
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 18, 2016, 09:05:33 Vormittag
Sundtek
please see this
http://forums.openpli.org/topic/37608-announce-blindscan-support-for-sundtek-tuners-dvb-c/?view=findpost&p=543323
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am April 18, 2016, 09:41:10 Vormittag
The S2 Blindscan output for the nim sockets will be modified with the next update (however it's a bit unclear when the next one will be available since we have several updates and a new RTSP streamingserver upcoming)
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am April 21, 2016, 10:10:29 Vormittag
Support Sundtek S2 Blindscan added in plugin Blindscan(feed avaibale):
1)openPli image
2)images based of oe-alliance (openATV,openVIX and etc)
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am Mai 29, 2016, 12:23:59 Nachmittag
Tested.
Scan for new drivers(25.05.2016) works fine.
Fixed new output blind scan:
1)openPli image
https://github.com/OpenPLi/enigma2-plugins/commit/75aa34b103c6e78678f78f54952fb9c9fce2bd7e
2)images based of oe-alliance (openATV,openVIX and etc)
https://github.com/oe-alliance/oe-alliance-plugins/commit/96975356a3a9e67d1a948ba64f7f13a233e94819
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am November 19, 2016, 11:33:48 Nachmittag
Hi.
Blind scan not work.
NIM Socket 5:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 8
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 9
        I2C_Device: 4

NIM Socket 10:
        Type: DVB-T
        Name: Sundtek DVB-T (III) (1/0) (USB)
        Frontend_Device: 10
NIM Socket 11:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USBDVB-S2
        Frontend_Device: 11root@vusolo4k:~#
root@vusolo4k:~# /opt/bin/mediaclient --build
Build date: 2016-10-20 11:51:28
root@vusolo4k:~# /opt/bin/mediaclient --blindscan 10
root@vusolo4k:~# /opt/bin/mediaclient --blindscan 11
root@vusolo4k:~#
answer zero

Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am November 20, 2016, 02:02:51 Nachmittag
What does ls /dev/dvb/frontend* show up?
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am November 20, 2016, 02:49:44 Nachmittag
try attached mediaclient file

put it to /opt/bin

Zitat
cd /opt/bin
chmod 777 mediaclient

I see it was only possible to support up to 9 tuners on a system for the blindscan, the 10th was truncated to 1 with the mediaclient blindscan command.
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am November 20, 2016, 03:56:11 Nachmittag
What does ls /dev/dvb/frontend* show up?
mediaclient old
yes, /dev/dvb/adapter0/frontend11 work
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:

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

test
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
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am November 20, 2016, 04:15:41 Nachmittag
Another question...
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

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
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.

Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Sundtek am November 20, 2016, 04:54:01 Nachmittag
use this one for ARM
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am November 20, 2016, 05:56:53 Nachmittag
use this one for ARM
Thanks,work fine...
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
....
Titel: Re:Blindscan on VU+ Solo2 with OpenPLI image
Beitrag von: Dima73 am Januar 24, 2017, 11:13:30 Vormittag
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 :(.