View Full Version : [VU+ Zero4K] Blind scan transponders
Blind scan for transponders doesn't work: always get message from pic blindscan3:
62835628366283762838
Where are you located? 55W is pretty low on the horizon from UK/Ireland. I used to receive from 58W with my 1.1m dish some years ago, but can't pick up any transponders now as I think the Europe beams were discontinued.
What box and tuner number?
What box and tuner number?
The box brand is in the title of the post, but here it is:62842
It doesn't matter what satellite: it is the same issue.
Didn't have this issue with openvix-5.4.016.release-vuzero4k_usb.
BrokenUnusableAccount
18-11-21, 18:18
Are you always scanning with "only scan unknown transponders" switched on?
If so try with it switched off.
Are you always scanning with "only scan unknown transponders" switched on?
If so try with it switched off.That's why it's called blindscan. Finds unknown transponders. Why would anyone do a blindscan for known transponders? For that a regular scan is much faster.
BrokenUnusableAccount
19-11-21, 01:15
But the original complaint was that i wasn't finding anything,
Are we sure there are any unknown transponders?
But the original complaint was that i wasn't finding anything,
Are we sure there are any unknown transponders?Probably, but anyway he is going to need a dish 1.80cm or bigger to get any sort of reasonable reception from that satellite.
Probably, but anyway he is going to need a dish 1.80cm or bigger to get any sort of reasonable reception from that satellite.
I believe the dish 10'=3m that i have, is good enough for a "reasonable reception" !!!
the same settings was finding transponders in every image up to version 6.
I believe the dish 10'=3m that i have, is good enough for a "reasonable reception" !!!
the same settings was finding transponders in every image up to version 6.There is no change in the plugin between version 5.4 and 6.0. Please post the full debug logs of the scan.
That's all i found:
62871
And this:62872
el bandido
21-11-21, 05:49
Are any channels or services found in a regular scan?
Looks like the binary is outputting junk.
It is the same issue after openvix-6.0.003.release-vuzero4k!
62881
log after upgrade from internet:62880
not only that is not fixed, but 4 out of 5 times there is no log at all !!!
finally the log after flushing the box from usb:62882
It is the same issue after openvix-6.0.003.release-vuzero4k!
62881
log after upgrade from internet:62880
not only that is not fixed, but 4 out of 5 times there is no log at all !!!
finally the log after flushing the box from usb:62882
Like I said earlier the binary is outputting junk. That is nothing to do with OpenViX image or the plugin. This file is supplied by the manufacturer.
Like I said earlier the binary is outputting junk. That is nothing to do with OpenViX image or the plugin. This file is supplied by the manufacturer.
so, in other words better go back to the last 5.4 working version.
Hopefully no more features are vanishing in the future 6.0 versions !
so, in other words better go back to the last 5.4 working version.
Hopefully no more features are vanishing in the future 6.0 versions !
Read again .... binary ---->> manufacturer supplied
All I can tell you is the plugin sends the correct command to the binary and the binary returns rubbish.
Read again .... binary ---->> manufacturer supplied
the manufacturer didn't change anything in the box since i got the box, or since 5.4.016 version.
only the image has been changed, and a lot of features of the image have been altered with the introduction of py3.
So, i don't see any involvement of the manufacturer !
If you read the log that you posted you will see it is the manufacturer binary that is outputting junk. And that binary comes from the box manufacturer.
If you read the log that you posted you will see it is the manufacturer binary that is outputting junk. And that binary comes from the box manufacturer.
but the binary was there since the beginning. nobody changed.
can the 6.0 version(s) acomodate it? if NO that means the box is garbage too.
is like we to trash the car because the software can't cope with it !
el bandido
22-11-21, 18:18
Something is not right.
My Zero 4K also returns "No transponders found" for a c band scan using image openvix-6.0.002.release-vuzero4k_usb.
spanner123
22-11-21, 18:22
I don't have a Zero 4K but blaming the box after only a software change seems very strange!
I don't have a Zero 4K but blaming the box after only a software change seems very strange!FFS, no one is blaming the box. The binary is outputting junk.
I just tried the same scan on OS Mio 4K and the output is good. So not OpenViX, not enigma, not Python 3, and not the plugin at fault.
And if you look at the input command to the binary (in your log) you can see it is good. You can even call the binary from the command line with that command and will be able to see the output is junk.
This is closed source code from the manufacturer, so no idea what you think we are supposed to do.
spanner123
22-11-21, 18:55
I am only commenting out of interest, so openvix 5.4 understands the junk and openvix 6.0 doesn't?
BrokenUnusableAccount
22-11-21, 19:04
FFS, no one is blaming the box. The binary is outputting junk.
I just tried the same scan on OS Mio 4K and the output is good. So not OpenViX, not enigma, not Python 3, and not the plugin at fault.
And if you look at the input command to the binary (in your log) you can see it is good. You can even call the binary from the command line with that command and will be able to see the output is junk.
This is closed source code from the manufacturer, so no idea what you think we are supposed to do.
You haven't given any reason why you can't go back to the binary from the manufacturer that worked right and was in OpenViX 5.4.016.
I am only commenting out of interest, so openvix 5.4 understands the junk and openvix 6.0 doesn't?
I have no clue what is happening in 5.4 because the log provided was for 6.0.
You haven't given any reason why you can't go back to the binary from the manufacturer that worked right and was in OpenViX 5.4.016.No idea what you are talking about. Has someone changed the binary?
BrokenUnusableAccount
22-11-21, 21:07
I have no clue what is happening in 5.4 because the log provided was for 6.0.
Ah.
There's the next step then.
Somebody needs to get a debug log from 5.4.016 on the same box.
Ah.
There's the next step then.
Somebody needs to get a debug log from 5.4.016 on the same box.
Well, I did, but before i checked the blindscan feature: not working up to back to 5.4.015 version !
the last version when blindscan was working is 5.4.014:6289762898628996290062901
here are the logs:
629026290362904
hope will help to fix the issue.
So take the binary out of 5.4.014 and drop it in 6.0.xxx so we can be sure it is this.
So take the binary out of 5.4.014 and drop it in 6.0.xxx so we can be sure it is this.
where is binary file located ?
/usr/bin .
what is the name of the file ?
el bandido
23-11-21, 02:22
Changing the blindscan binaries in /usr/bin to 5.4.014 did not help my Zero4k. I would expect others to have the same results.
Changing the blindscan binaries in /usr/bin to 5.4.014 did not help my Zero4k. I would expect others to have the same results.Can you confirm 014 works and 015 does not?
Changing the blindscan binaries in /usr/bin to 5.4.014 did not help my Zero4k. I would expect others to have the same results.
what's the name of the binaries file ?
So, blind scan for C band is broken as it was for Ku band.
nice.
what is next ?
el bandido
23-11-21, 05:44
Can you confirm 014 works and 015 does not?
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.
el bandido
23-11-21, 05:48
So, blind scan for C band is broken as it was for Ku band.
nice.
what is next ?
Purchase a receiver that has a good working blindscan instead of a Vu+ product.,..Other than doing that, wait and see what happens.
Maybe this Vu commit in August was the problem.....
https://github.com/oe-alliance/oe-alliance-core/commit/595cafe210ebe677abbba40f49dcc2f32094d206
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
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.
Is this relevant, I can't see it committed in OE?
https://github.com/vu-plus/meta-vuplus/commit/4ed3f3707b8a85a6ec777bc561a203101e91be1b
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...
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.
5.4.015 was replaced few days later by 5.4.016 for this reason: softcam manager was dead.
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.
5.4.015 was replaced few days later by 5.4.016 for this reason: softcam manager was dead.
Please stop talking complete rubbish.
Please stop talking complete rubbish.
please stop making rubbish images.
el bandido
23-11-21, 19:28
please stop making rubbish images.
A tidbit of information for you: This blindscan problem exists in other images besides OpenVix.
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.
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:
6291162912
el bandido
24-11-21, 03:03
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
24-11-21, 03:34
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
24-11-21, 04:00
Edited line#930 in the attached plugin.py file as a Zero4k test. It works, but it needs proper fixing.
@Ime or @el bandido, can you get the output from "cat /proc/bus/nim_sockets" from the command line please.
I think I have found where they f**ked it up. And as usual hidden by a try/except.
el bandido
24-11-21, 16:14
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:~#
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.
el bandido
25-11-21, 04:40
Blindscan works correctly with your modified plugin. I verified your changes were in it.
THANKS!
BrokenUnusableAccount
25-11-21, 11:37
Great work everyone.
where can i find the new file ?
where can i find the new file ?
Never mind. i got it.
Never mind. i got it.
So now you can test in 6.0
So now you can test in 6.0
yes. i did it & it's ok for c-band. ku-band was from the beginnig & it's still broken.
thx.
is it going to be in the next version ?
is it going to be in the next version ?I thought you said "it's still broken".
I thought you said "it's still broken".
for ku band it's broken.
Please provide a debug log.
Please provide a debug log.
It's working. i had the wrong lnb setting. my fault.
sorry.
el bandido
27-11-21, 17:48
The universal blindscan problem has been fixed??? I don't think so.
The broken ku blindscan in the Vu+ Zero 4K is the dumbest thing I have seen in a fta receiver. This problem has been reported several times to Vu+ and nothing has been done to fix it. Simply put, 22KHz tone is set to OFF in the Zero4K binary.
C band blindscan works in the Zero4K because the low band is scanned which means no 22 KHz tone is needed.
Circular lnb type (10750 l.o.) works because only low band is scanned which means no 22 KHz tone is needed.
Universal lnb type will not work because 22KHz tone is set to OFF in the vuzero4k blindscan binary. The blindscan binary takes precedent over any other 22 KHz tone setting, which means you cannot set the 22 KHz tone to ON using the blindscan plugin or in the antenna settings.
A 22KHz tone generator that is inserted into the cable between the receiver and lnb will allow the high side (10600 l.o.) of the universal lnb to be scanned by manually activating the 22 KHz tone generator. This is the only way I could find to make the Zero4K blindscan the high side of the universal lnb.
It would be nice to see this problem solved, but this problem has been reported more than once to Vu+ years ago and nothing has been done to fix it.
Well, if lnb is set to Universal, blindscan works.
but when set to user with high of 10750 (as for north america), it doesn't work.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.