[VU+ Zero4K] Blind scan transponders

[lme]

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]

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]

I don't have a Zero 4K but blaming the box after only a software change seems very strange!

 

[Huevos]

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]

I am only commenting out of interest, so openvix 5.4 understands the junk and openvix 6.0 doesn't?

 

[BrokenUnusableAccount]

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.

 

[Huevos]

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.

 

[Huevos]

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]

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.

 

[lme]

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:

here are the logs:
View attachment blindscan_89W_22-11-2021_17-17-50.xmlView attachment blindscan_91W_22-11-2021_17-07-13.xmlView attachment Enigma2_debug_2021-11-22_17-03-53.log
hope will help to fix the issue.

 

[Huevos]

So take the binary out of 5.4.014 and drop it in 6.0.xxx so we can be sure it is this.

 

[lme]

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 ?

 

[Huevos]

/usr/bin .

 

[lme]

/usr/bin .

what is the name of the file ?

 

[el bandido]

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.

 

[Huevos]

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?

 

[lme]

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 ?

 

[lme]

So, blind scan for C band is broken as it was for Ku band.
nice.
what is next ?

 

[el bandido]

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]

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.