Blind scan transponders

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

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