so, in other words better go back to the last 5.4 working version.Originally Posted by Huevos
Hopefully no more features are vanishing in the future 6.0 versions !
Read again .... binary ---->> manufacturer supplied
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
.......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
Zgemma H9 C/S into Giga4K
All I can tell you is the plugin sends the correct command to the binary and the binary returns rubbish.
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 !
Last edited by lme; 22-11-21 at 16:32.
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 !
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.
lme (22-11-21)
I don't have a Zero 4K but blaming the box after only a software change seems very strange!
lme (22-11-21)
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.
I am only commenting out of interest, so openvix 5.4 understands the junk and openvix 6.0 doesn't?
lme (22-11-21)
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.
lme (22-11-21)
I have no clue what is happening in 5.4 because the log provided was for 6.0.
No idea what you are talking about. Has someone changed the binary?
ccs (22-11-21)
Ah.
There's the next step then.
Somebody needs to get a debug log from 5.4.016 on the same box.
lme (22-11-21)
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:blind1.jpgblind2.jpgblind3.jpgblind4.jpgblind5.jpg
here are the logs:
blindscan_89W_22-11-2021_17-17-50.xmlblindscan_91W_22-11-2021_17-07-13.xmlEnigma2_debug_2021-11-22_17-03-53.log
hope will help to fix the issue.
Posting Permissions
Reply With Quote