ABM scans after running DVB-T frequency finder.

[ccs]

You really should start another thread as this is not a Py3 problem.

DVB standard says all sections of "SDT actual" must be transmitted at least once every 2 seconds, and, all sections of "SDT other" must be transmitted at least once every 15 seconds, so a 20 second timeout is good for any mux that complies with the standard, but obviously yours doesn't, or is broken.

Please get a debug log of the scan with extra debug activated.

End of original thread - https://www.world-of-satellite.com/s...l=1#post514976


Running DVB-T frequency finder (UK freeview) on Python P2 and P3 images produces different terrestrial_finder.xml files - the same expected data, but in a different order.

This means that the mux chosen by ABM to run a "scan" is different from P2 and doesn't (for some unknown reason) find the correct number of channels in P3.

(If the same mux is forced onto P2, it fails in the same way.)

So the mux chosen is critical, increasing the SDT_TIMEOUT in dvbscanner.py fixes it, but breaks the rules.

Here are 3 sets of logs, a working mux, a non working mux, and a non working mux which works when the timeout is increased....