[VU+ Zero4K] Blind scan transponders

[ccs]

Maybe this Vu commit in August was the problem.....

https://github.com/oe-alliance/oe-alliance-core/commit/595cafe210ebe677abbba40f49dcc2f32094d206

 

[Huevos]

Maybe this Vu commit in August was the problem.....

https://github.com/oe-alliance/oe-alliance-core/commit/595cafe210ebe677abbba40f49dcc2f32094d206

That change is correct. Look at the URL...

code.vuplus.com/download/release/utils/vuplus-blindscan-utils-5.1_arm.tar.bz2

 

[Huevos]

Blindscan for c band works in 5.4.014, but not in 5.4.015 or 5.4.016.

You can move plugin.pyo in blindscan folder from 5.4.014 image To 5.4.015 OR 5.4.016 images and blindscan will work.

You can move plugin.pyo in blindscan folder from 5.4.014 image To 6.0.003 image and blindscan will Not work.

Blindscan starts normal in the 6.0.003 image, but the spinner becomes active for a noticeable amount of seconds between steps 1 and 2, then the spinner becomes active again after step 2 for a noticeable amount of seconds before displaying "no transponders found." I guess the spinner is active due to the garbage being generated.

If you are available tonight we can meet on Skype and trawl through the commits one at a time to find where they introduced the bug.

 

[ccs]

Is this relevant, I can't see it committed in OE?

https://github.com/vu-plus/meta-vuplus/commit/4ed3f3707b8a85a6ec777bc561a203101e91be1b

 

[lme]

Blindscan for c band works in 5.4.014, but not in 5.4.015 or 5.4.016.

You can move plugin.pyo in blindscan folder from 5.4.014 image To 5.4.015 OR 5.4.016 images and blindscan will work.

You can move plugin.pyo in blindscan folder from 5.4.014 image To 6.0.003 image and blindscan will Not work.

Blindscan starts normal in the 6.0.003 image, but the spinner becomes active for a noticeable amount of seconds between steps 1 and 2, then the spinner becomes active again after step 2 for a noticeable amount of seconds before displaying "no transponders found." I guess the spinner is active due to the garbage being generated.

5.4.015 has softcam manager broken, so is useless.
5.4.xxx uses python2 version as the reason for version 6.0.xxx was to implement python3 version (why??), so you can not mix files from 5.4 with 6.0 & viceversa...

 

[twol]

5.4.015 has softcam manager broken, so is useless.
5.4.xxx uses python2 version as the reason for version 6.0.xxx was to implement python3 version (why??), so you can not mix files from 5.4 with 6.0 & viceversa...

“ 5.4.015 has softcam manager broken, so is useless.“ - since when???

If you haven‘t noticed, python2 has been superceded by python3 - if you don‘t like that go speak to the python guru‘s
Vu+ in their customer friendly way only supply binary modules (not pyo)
Lastly there is no basic issue transferring a .py module between python2 and python3 providing it supports both environments which we have tried to do with OpenViX…. The issue is when you have only a .pyo and even then you can re-engineer back to python.

 

[lme]

5.4.015 was replaced few days later by 5.4.016 for this reason: softcam manager was dead.

 

[Huevos]

5.4.xxx uses python2 version as the reason for version 6.0.xxx was to implement python3 version (why??),

Python 3 was created to replace Python 2 ten years ago. Python 2 has not been maintained for more than a year. Most 3rd party libraries have already switched. Any project that does not update will soon be dead.

 

[Huevos]

5.4.015 was replaced few days later by 5.4.016 for this reason: softcam manager was dead.

Please stop talking complete rubbish.

 

[lme]

Please stop talking complete rubbish.

please stop making rubbish images.

 

[el bandido]

please stop making rubbish images.

A tidbit of information for you: This blindscan problem exists in other images besides OpenVix.

 

[Huevos]

please stop making rubbish images.

If that is what you think what are you doing here?

And as pointed out by ElBandido blindscan is a common plugin.

 

[lme]

The best i could do is to replace not working plugin.pyo file from 5.4.016 with the working plugin.pyo file from 5.4.014.
and blind scan is working again:

 

[el bandido]

I think we can eliminate the blindscan plugin using command line in terminal.
(1) Loaded the same image into MIO+ and Zero4K from Vix servers, which is 6.0.003
(2) Setup telnet and run command line blindscan on each box

Welcome to OpenViX for osmio4kplus
openvix 6.0 osmio4kplus

osmio4kplus login: root
Password:
Last login: Tue Nov 23 20:27:49 EST 2021 on pts/1
root@osmio4kplus:~# cd /usr/bin
root@osmio4kplus:/usr/bin# ./blindscan --start=950 --stop=2150 --min=1 --max=45 --slot=0 --i2c=2 --vertical
OK VERTICAL 11307000 7200000 DVB-S2 INVERSION_AUTO PILOT_ON FEC_3_4 8PSK ROLLOFF_35 1 -1 0
OK VERTICAL 11361000 29267000 DVB-S INVERSION_AUTO PILOT_OFF FEC_1_2 QPSK ROLLOFF_35 1 -1 0
OK VERTICAL 11400000 30002000 DVB-S2 INVERSION_AUTO PILOT_ON FEC_5_6 8PSK ROLLOFF_35 1 -1 0
OK VERTICAL 11521000 30000000 DVB-S2 INVERSION_AUTO PILOT_ON FEC_5_6 8PSK ROLLOFF_35 1 -1 0
OK VERTICAL 11549000 10000000 DVB-S INVERSION_AUTO PILOT_OFF FEC_AUTO QPSK ROLLOFF_35 1 -1 0
OK VERTICAL 11561000 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_AUTO QPSK ROLLOFF_35 1 -1 0
OK VERTICAL 11565000 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_AUTO QPSK ROLLOFF_35 1 -1 0
OK VERTICAL 11600000 29999000 DVB-S2 INVERSION_AUTO PILOT_ON FEC_5_6 8PSK ROLLOFF_35 1 -1 0
OK VERTICAL 11568000 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_AUTO QPSK ROLLOFF_35 1 -1 0
OK VERTICAL 11572000 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_AUTO QPSK ROLLOFF_35 1 -1 0
OK VERTICAL 11576000 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_AUTO QPSK ROLLOFF_35 1 -1 0
OK VERTICAL 11640000 30002000 DVB-S2 INVERSION_AUTO PILOT_OFF FEC_5_6 8PSK ROLLOFF_35 1 -1 0
root@osmio4kplus:/usr/bin# init 4 && init 3
root@osmio4kplus:/usr/bin#

Welcome to OpenViX for vuzero4k
openvix 6.0 vuzero4k

vuzero4k login: root
Password:
Last login: Wed Nov 24 01:41:09 GMT 2021 on pts/1
root@vuzero4k:~# cd /usr/bin
root@vuzero4k:/usr/bin# ./vuplus_blindscan 950 2150 2 45 1 0 0 2
After Write
After Write
After Write
After Write
After Write
After Write
I2CDevAdapter[3] ReadWithoutStop Error.
After Write
I2CDevAdapter[3] ReadWithoutStop Error.
After Write
I2CDevAdapter[3] ReadWithoutStop Error.
After Write
I2CDevAdapter[3] ReadWithoutStop Error.
After Write
I2CDevAdapter[3] ReadWithoutStop Error.

The MIO+ and the Zero4K are "seeing" the same c band satellite in this test. The MIO+ returns ku frequencies in the scan results, but the correct c band command for Edision is not entered. The point I am trying to make is the MIO+ receiver returns transponders in this test while the Zero4K returns garbage.

I think this shows the plugin for blindscan is not the problem.

 

[el bandido]

Maybe not calling the right blindscan binary is the problem. Look at this:

root@vuzero4k:/usr/bin# ./vuplus_si2166_blindscan 950 2150 2 45 1 0 0 2
OK VERTICAL 11305890 7200000 DVB-S2 INVERSION_AUTO PILOT_OFF FEC_3_4 8PSK ROLLOFF_35
OK VERTICAL 11333022 7500000 DVB-S2 INVERSION_AUTO PILOT_OFF FEC_3_4 8PSK ROLLOFF_35
OK VERTICAL 11359695 29268000 DVB-S INVERSION_AUTO PILOT_OFF FEC_3_4 QPSK ROLLOFF_35
OK VERTICAL 11397050 30001000 DVB-S2 INVERSION_AUTO PILOT_OFF FEC_5_6 8PSK ROLLOFF_35
OK VERTICAL 11519144 30002000 DVB-S2 INVERSION_AUTO PILOT_OFF FEC_5_6 8PSK ROLLOFF_35
OK VERTICAL 11547718 10000000 DVB-S INVERSION_AUTO PILOT_OFF FEC_5_6 QPSK ROLLOFF_35
OK VERTICAL 11555713 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_5_6 QPSK ROLLOFF_35
OK VERTICAL 11559711 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_5_6 QPSK ROLLOFF_35
OK VERTICAL 11563708 2735000 DVB-S INVERSION_AUTO PILOT_OFF FEC_5_6 QPSK ROLLOFF_35
OK VERTICAL 11567706 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_5_6 QPSK ROLLOFF_35
OK VERTICAL 11571704 2735000 DVB-S INVERSION_AUTO PILOT_OFF FEC_5_6 QPSK ROLLOFF_35
OK VERTICAL 11575701 2734000 DVB-S INVERSION_AUTO PILOT_OFF FEC_5_6 QPSK ROLLOFF_35
OK VERTICAL 11600474 30001000 DVB-S2 INVERSION_AUTO PILOT_OFF FEC_5_6 8PSK ROLLOFF_35
OK VERTICAL 11638157 30001000 DVB-S2 INVERSION_AUTO PILOT_OFF FEC_5_6 8PSK ROLLOFF_35
root@vuzero4k:/usr/bin#

These blindscan binaries are located in /usr/bin:
vuplus_6211_blindscan
vuplus_6222_blindscan
vuplus_blindscan
vuplus_si2166_blindscan

 

[el bandido]

Edited line#930 in the attached plugin.py file as a Zero4k test. It works, but it needs proper fixing.

 

[Huevos]

@Ime or @el bandido, can you get the output from "cat /proc/bus/nim_sockets" from the command line please.

 

[Huevos]

I think I have found where they f**ked it up. And as usual hidden by a try/except.

 

[el bandido]

Output of cat /proc/bus/nim_sockets:

Welcome to OpenViX for vuzero4k
openvix 6.0 vuzero4k

vuzero4k login: root
Password:
root@vuzero4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
Type: DVB-S2X
Name: Vuplus DVB-S NIM(SI2166)
Frontend_Device: 0
I2C_Device: 2
root@vuzero4k:~#

 

[Huevos]

https://github.com/oe-alliance/oe-alliance-plugins/commit/269feb5a4a340bf5a8f4195e41ee1229bb474058

Try this... I can't test because I don't have a blindscan capable Vu.