Edision MIO+ 4K Australian experience

[Aust-VAST]

Hi all,

A newly arrived receiver, very impressive, very powerful, many features, will report more on this in later posts.

The MIO+ 4K mastered our favourite Satellite in 3 minutes flat, albeit 47,300 SR, multistream !!

When its ready for the HT, it will revise our entertainment away from the CA based FTA VAST slow and incomplete service.

I have a random tune failed error.

It seems to emerge if I am say recording a terrestrial service for some time and then tuning back to the satellite bouquet "Tune failed" and a reboot is required.

The recording will succeed, but I have had terrestrial bouquet reception fail in reverse on occasion too?

Also if the device is left in playback and a track ends the satellite usually is "Tune failed" if, say it has been unattended for maybe a time/ 20 minutes.

There are some remarks in the log, so I hope that is useful.

ODU/ LNB is a single, various in simple mode and I have two G-Sat unicables (https://www.world-of-satellite.com/showthread.php?65726-Unicable-assistance-from-Australia-!) but they won't work other than legacy mode.

64612

[Huevos]

This is most likely due to incorrect timing setup of Unicable LNB.

Start by reading this thread:
https://www.world-of-satellite.com/showthread.php?58679-Unicable-devices-and-tune-failed-messages

Start at 3000 ms and work down.

I'm sure 3000 should be enough delay for any Unicable device but if still happens increase it further.

[Huevos]

Hmm just read again and you are in legacy mode. Then it is probably not timing, but maybe it still is. It will be a different setting in that timing plugin.

Probably will be "delay after enable voltage before switch command", not "Unicable delay after enable voltage before switch command".

I've got a Mio4k+ and not had the problem you report.

For testing I would try reverting to your Universal LNB.

[Aust-VAST]

Hmm just read again and you are in legacy mode. Then it is probably not timing, but maybe it still is. It will be a different setting in that timing plugin.

Probably will be "delay after enable voltage before switch command", not "Unicable delay after enable voltage before switch command".

I've got a Mio4k+ and not had the problem you report.

For testing I would try reverting to your Universal LNB.

Yes true using legacy mode.

I will vary about with adjustment and report the results.

Many thanks.

[Aust-VAST]

This is most likely due to incorrect timing setup of Unicable LNB.

Start by reading this thread:
https://www.world-of-satellite.com/showthread.php?58679-Unicable-devices-and-tune-failed-messages

Start at 3000 ms and work down.

I'm sure 3000 should be enough delay for any Unicable device but if still happens increase it further.

Yes have tried the plugin for the Unicable LNB (https://www.world-of-satellite.com/showthread.php?65726-Unicable-assistance-from-Australia-!) but even varying and rebooting with a wide range of choices, the services still fluctuate on a pattern every few seconds, so, plan to abandon and return to legacy mode for now as it is quite good even without the advantages of Unicable.

[Aust-VAST]

Hi all,

Need some help here, a month out and the Edision isn't ready for the HT yet.

Today the DVB-S tuning is very sensitive.

If I want to test a PiP session, main focus DVB-S, the other (PiP) DVB-T, then the DVB-S service is "Tune Failed".

When I check the LNB sometimes has no voltage in the cable ('0' volts) sometimes it does !

Have been varying the "delay after enable voltage before switch command" up and down, but doesn't seem to solve the drop of satellite services. :confused:

DVB-S Tuner is Legacy mode GT S1dCSS24, service SR = 47,300 fwiw.

Log attached.

Ok branched out, just booted into Slot #1 and I can PiP, (DVB-S + DVB-T) and play back media/usb, wow, Open ATV 6.3 more testing needed, I am going out to leave it on for 24H (have log).

[Aust-VAST]

Hi all,

Well after 24 hours testing, PiP, multiple recording, playback no problems with OpenATV, very smooth.

Where to from here?

I see in the log that the satellitequipmentcontrol is in use already in this o/s (OpenATV).

There seems to be a lot of "tune failed" entries in the VIX log and rebooting to temporary solve:

< 327.8665> [eDVBServicePMTHandler] tune failed.
< 327.8665> [eDVBServicePlay] DVB service failed to tune - error 1
< 327.8672> [Notifications] RemovePopup, id = ZapError
< 327.8672> [Notifications] AddPopup, id = ZapError
< 327.8682> [Skin] Processing screen 'MessageBoxSimple' from list 'MessageBoxSimple, MessageBox', position=(480, 532), size=(960 x 15) for module 'MessageBox'.
< 327.8750> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Tune failed!).
< 327.8758> [Pixmap] setPixmapNum(3) failed! defined pixmaps: []
< 327.8792> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 327.8792> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 327.8792> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 327.8792> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 327.8795> [eDVBFrontend0] invalidate current switch params
< 327.8795> [eDVBFrontend0] set sequence pos 3
< 327.8796> [eDVBFrontend0] set sequence pos 3
< 327.8796> [eDVBFrontend0] update current switch params
< 327.8796> [eDVBFrontend0] startTuneTimeout 5000
< 327.8796> [eDVBFrontend0] setFrontend 1
< 327.8796> [eDVBFrontend0] setting frontend
< 327.8797> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 327.8797> [eDVBFrontend0] sleep 500ms
< 328.7992> [eDVBServicePlay] Start timeshift!
< 330.8503> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 330.8503> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 330.8503> [eDVBChannel] OURSTATE: failed, retune
< 330.8503> [eDVBFrontend0] tune
< 330.8504> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 330.8504> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 330.8504> [eDVBFrontend0] tuning to 1870 mhz
< 330.8504> [eDVBChannel] OURSTATE: tuning
< 330.8504> [eDVBServicePMTHandler] tune failed.
< 330.8504> [eDVBServicePlay] DVB service failed to tune - error 1
< 330.8509> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 330.8509> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 330.8509> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 330.8509> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 330.8510> [eDVBFrontend0] invalidate current switch params
< 330.8511> [eDVBFrontend0] set sequence pos 3
< 330.8511> [eDVBFrontend0] set sequence pos 3
< 330.8511> [eDVBFrontend0] update current switch params
< 330.8511> [eDVBFrontend0] startTuneTimeout 5000
< 330.8511> [eDVBFrontend0] setFrontend 1
< 330.8511> [eDVBFrontend0] setting frontend
< 330.8967> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 330.8967> [eDVBFrontend0] sleep 500ms
< 331.6413> [eInputDeviceInit] 1 ae (174) 1
< 331.6413> [eRCDeviceInputDev] emit: 1
< 331.6419> [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 331.6420> [ActionMap] Keymap 'InfobarShowHideActions' -> Action = 'hide'.
< 331.8561> [eInputDeviceInit] 0 ae (174) 1
< 331.8562> [eRCDeviceInputDev] emit: 0
< 331.8567> [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 332.8098> [eDVBServicePlay] Start timeshift!
< 333.7112> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 333.7117> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 333.7120> [eDVBChannel] OURSTATE: failed, retune
< 333.7122> [eDVBFrontend0] tune
< 333.7124> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 333.7127> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 333.7131> [eDVBFrontend0] tuning to 1870 mhz
< 333.7133> [eDVBChannel] OURSTATE: tuning
< 333.7136> [eDVBServicePMTHandler] tune failed.
< 333.7138> [eDVBServicePlay] DVB service failed to tune - error 1
< 333.7142> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 333.7142> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 333.7142> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 333.7142> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 333.7143> [eDVBFrontend0] invalidate current switch params
< 333.7143> [eDVBFrontend0] set sequence pos 3
< 333.7144> [eDVBFrontend0] set sequence pos 3
< 333.7144> [eDVBFrontend0] update current switch params
< 333.7144> [eDVBFrontend0] startTuneTimeout 5000
< 333.7144> [eDVBFrontend0] setFrontend 1
< 333.7144> [eDVBFrontend0] setting frontend
< 333.7597> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 333.7597> [eDVBFrontend0] sleep 500ms
< 333.8730> [eInputDeviceInit] 1 8b (139) 1
< 333.8731> [eRCDeviceInputDev] emit: 1
< 333.8736> [InfoBarGenerics] Key: 139 (Make) KeyID='KEY_MENU' Binding='('MENU',)'.
< 333.8737> [ActionMap] Keymap 'InfobarMenuActions' -> Action = 'mainMenu'.
< 333.8772> [Skin] Processing screen 'menu_mainmenu' from list 'menu_mainmenu, Menu', position=(0, 0), size=(1920 x 1080) for module 'MainMenu'.
< 333.8870> [Skin] Processing screen 'MenuSummary' from list 'menu_mainmenuSummary, MenuSummary, ScreenSummary, menu_mainmenu_summary, Menu_summary, SimpleSummary', position=(0, 0), size=(128 x 32) for module 'MenuSummary'.
< 334.0882> [eInputDeviceInit] 0 8b (139) 1
< 334.0882> [eRCDeviceInputDev] emit: 0
< 334.0886> [InfoBarGenerics] Key: 139 (Break) KeyID='KEY_MENU' Binding='('MENU',)'.
< 335.0511> [eInputDeviceInit] 1 67 (103) 1
< 335.0511> [eRCDeviceInputDev] emit: 1
< 335.0516> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 335.2644> [eInputDeviceInit] 0 67 (103) 1
< 335.2653> [eRCDeviceInputDev] emit: 0
< 335.2663> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 336.4463> [eInputDeviceInit] 1 160 (352) 1
< 336.4468> [eRCDeviceInputDev] emit: 1
< 336.4474> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 336.4478> [ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
< 336.4519> [Skin] Processing screen 'Menu' from list 'menu_shutdown, Menu', position=(0, 0), size=(1920 x 1080) for module 'Menu'.
< 336.4610> [Skin] Processing screen 'MenuSummary' from list 'menu_shutdownSummary, MenuSummary, ScreenSummary, menu_shutdown_summary, Menu_summary, SimpleSummary', position=(0, 0), size=(128 x 32) for module 'MenuSummary'.
< 336.6324> [eInputDeviceInit] 0 160 (352) 1
< 336.6324> [eRCDeviceInputDev] emit: 0
< 336.6328> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 336.6362> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 336.6362> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 336.6363> [eDVBChannel] OURSTATE: failed, retune
< 336.6363> [eDVBFrontend0] tune
< 336.6363> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 336.6363> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 336.6363> [eDVBFrontend0] tuning to 1870 mhz
< 336.6363> [eDVBChannel] OURSTATE: tuning
< 336.6364> [eDVBServicePMTHandler] tune failed.
< 336.6364> [eDVBServicePlay] DVB service failed to tune - error 1
< 336.6368> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 336.6368> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 336.6368> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 336.6368> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 336.6369> [eDVBFrontend0] invalidate current switch params
< 336.6369> [eDVBFrontend0] set sequence pos 3
< 336.6370> [eDVBFrontend0] set sequence pos 3
< 336.6370> [eDVBFrontend0] update current switch params
< 336.6370> [eDVBFrontend0] startTuneTimeout 5000
< 336.6371> [eDVBFrontend0] setFrontend 1
< 336.6371> [eDVBFrontend0] setting frontend
< 336.6827> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 336.6827> [eDVBFrontend0] sleep 500ms
< 336.8171> [eDVBServicePlay] Start timeshift!
< 338.0893> [eInputDeviceInit] 1 67 (103) 1
< 338.0893> [eRCDeviceInputDev] emit: 1
< 338.0898> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 338.3043> [eInputDeviceInit] 0 67 (103) 1
< 338.3044> [eRCDeviceInputDev] emit: 0
< 338.3048> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 338.3683> [eInputDeviceInit] 1 67 (103) 1
< 338.3686> [eRCDeviceInputDev] emit: 1
< 338.3693> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 338.5200> [eInputDeviceInit] 0 67 (103) 1
< 338.5205> [eRCDeviceInputDev] emit: 0
< 338.5215> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 338.6161> [eInputDeviceInit] 1 67 (103) 1
< 338.6166> [eRCDeviceInputDev] emit: 1
< 338.6172> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 338.8001> [eInputDeviceInit] 0 67 (103) 1
< 338.8005> [eRCDeviceInputDev] emit: 0
< 338.8011> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 339.0500> [eInputDeviceInit] 1 160 (352) 1
< 339.0505> [eRCDeviceInputDev] emit: 1
< 339.0511> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 339.0515> [ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
< 339.0549> [Skin] Processing screen 'MessageBoxSimple', position=(480, 532), size=(960 x 15) for module 'TryQuitMainloop'.
< 339.0630> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.Standby.TryQuitMainloop'>(Recording(s) are in progress or coming up in few seconds!

Really reboot now?).< 339.0639>
< 339.0648> [Pixmap] setPixmapNum(0) failed! defined pixmaps: []
< 339.0672> [Skin] Processing screen 'MessageBoxSimple_summary' from list 'MessageBoxSimpleSummary, ScreenSummary, MessageBoxSimple_summary, SimpleSummary', position=(0, 0), size=(128 x 32) for module 'ScreenSummary'.
< 339.2323> [eInputDeviceInit] 0 160 (352) 1
< 339.2323> [eRCDeviceInputDev] emit: 0
< 339.2327> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 339.5373> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 339.5373> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 339.5373> [eDVBChannel] OURSTATE: failed, retune
< 339.5373> [eDVBFrontend0] tune
< 339.5374> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 339.5374> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 339.5374> [eDVBFrontend0] tuning to 1870 mhz
< 339.5374> [eDVBChannel] OURSTATE: tuning

[Huevos]

It makes no sense that it would work in ATV and not ViX as the tuning is done in the drivers.

[twol]

Hi all,

Well after 24 hours testing, PiP, multiple recording, playback no problems with OpenATV, very smooth.

Where to from here?

I see in the log that the satellitequipmentcontrol is in use already in this o/s (OpenATV).

There seems to be a lot of "tune failed" entries in the VIX log and rebooting to temporary solve:

< 327.8665> [eDVBServicePMTHandler] tune failed.
< 327.8665> [eDVBServicePlay] DVB service failed to tune - error 1
< 327.8672> [Notifications] RemovePopup, id = ZapError
< 327.8672> [Notifications] AddPopup, id = ZapError
< 327.8682> [Skin] Processing screen 'MessageBoxSimple' from list 'MessageBoxSimple, MessageBox', position=(480, 532), size=(960 x 15) for module 'MessageBox'.
< 327.8750> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.MessageBox.MessageBox'>(Tune failed!).
< 327.8758> [Pixmap] setPixmapNum(3) failed! defined pixmaps: []
< 327.8792> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 327.8792> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 327.8792> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 327.8792> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 327.8795> [eDVBFrontend0] invalidate current switch params
< 327.8795> [eDVBFrontend0] set sequence pos 3
< 327.8796> [eDVBFrontend0] set sequence pos 3
< 327.8796> [eDVBFrontend0] update current switch params
< 327.8796> [eDVBFrontend0] startTuneTimeout 5000
< 327.8796> [eDVBFrontend0] setFrontend 1
< 327.8796> [eDVBFrontend0] setting frontend
< 327.8797> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 327.8797> [eDVBFrontend0] sleep 500ms
< 328.7992> [eDVBServicePlay] Start timeshift!
< 330.8503> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 330.8503> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 330.8503> [eDVBChannel] OURSTATE: failed, retune
< 330.8503> [eDVBFrontend0] tune
< 330.8504> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 330.8504> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 330.8504> [eDVBFrontend0] tuning to 1870 mhz
< 330.8504> [eDVBChannel] OURSTATE: tuning
< 330.8504> [eDVBServicePMTHandler] tune failed.
< 330.8504> [eDVBServicePlay] DVB service failed to tune - error 1
< 330.8509> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 330.8509> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 330.8509> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 330.8509> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 330.8510> [eDVBFrontend0] invalidate current switch params
< 330.8511> [eDVBFrontend0] set sequence pos 3
< 330.8511> [eDVBFrontend0] set sequence pos 3
< 330.8511> [eDVBFrontend0] update current switch params
< 330.8511> [eDVBFrontend0] startTuneTimeout 5000
< 330.8511> [eDVBFrontend0] setFrontend 1
< 330.8511> [eDVBFrontend0] setting frontend
< 330.8967> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 330.8967> [eDVBFrontend0] sleep 500ms
< 331.6413> [eInputDeviceInit] 1 ae (174) 1
< 331.6413> [eRCDeviceInputDev] emit: 1
< 331.6419> [InfoBarGenerics] Key: 174 (Make) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 331.6420> [ActionMap] Keymap 'InfobarShowHideActions' -> Action = 'hide'.
< 331.8561> [eInputDeviceInit] 0 ae (174) 1
< 331.8562> [eRCDeviceInputDev] emit: 0
< 331.8567> [InfoBarGenerics] Key: 174 (Break) KeyID='KEY_EXIT' Binding='('EXIT',)'.
< 332.8098> [eDVBServicePlay] Start timeshift!
< 333.7112> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 333.7117> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 333.7120> [eDVBChannel] OURSTATE: failed, retune
< 333.7122> [eDVBFrontend0] tune
< 333.7124> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 333.7127> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 333.7131> [eDVBFrontend0] tuning to 1870 mhz
< 333.7133> [eDVBChannel] OURSTATE: tuning
< 333.7136> [eDVBServicePMTHandler] tune failed.
< 333.7138> [eDVBServicePlay] DVB service failed to tune - error 1
< 333.7142> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 333.7142> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 333.7142> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 333.7142> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 333.7143> [eDVBFrontend0] invalidate current switch params
< 333.7143> [eDVBFrontend0] set sequence pos 3
< 333.7144> [eDVBFrontend0] set sequence pos 3
< 333.7144> [eDVBFrontend0] update current switch params
< 333.7144> [eDVBFrontend0] startTuneTimeout 5000
< 333.7144> [eDVBFrontend0] setFrontend 1
< 333.7144> [eDVBFrontend0] setting frontend
< 333.7597> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 333.7597> [eDVBFrontend0] sleep 500ms
< 333.8730> [eInputDeviceInit] 1 8b (139) 1
< 333.8731> [eRCDeviceInputDev] emit: 1
< 333.8736> [InfoBarGenerics] Key: 139 (Make) KeyID='KEY_MENU' Binding='('MENU',)'.
< 333.8737> [ActionMap] Keymap 'InfobarMenuActions' -> Action = 'mainMenu'.
< 333.8772> [Skin] Processing screen 'menu_mainmenu' from list 'menu_mainmenu, Menu', position=(0, 0), size=(1920 x 1080) for module 'MainMenu'.
< 333.8870> [Skin] Processing screen 'MenuSummary' from list 'menu_mainmenuSummary, MenuSummary, ScreenSummary, menu_mainmenu_summary, Menu_summary, SimpleSummary', position=(0, 0), size=(128 x 32) for module 'MenuSummary'.
< 334.0882> [eInputDeviceInit] 0 8b (139) 1
< 334.0882> [eRCDeviceInputDev] emit: 0
< 334.0886> [InfoBarGenerics] Key: 139 (Break) KeyID='KEY_MENU' Binding='('MENU',)'.
< 335.0511> [eInputDeviceInit] 1 67 (103) 1
< 335.0511> [eRCDeviceInputDev] emit: 1
< 335.0516> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 335.2644> [eInputDeviceInit] 0 67 (103) 1
< 335.2653> [eRCDeviceInputDev] emit: 0
< 335.2663> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 336.4463> [eInputDeviceInit] 1 160 (352) 1
< 336.4468> [eRCDeviceInputDev] emit: 1
< 336.4474> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 336.4478> [ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
< 336.4519> [Skin] Processing screen 'Menu' from list 'menu_shutdown, Menu', position=(0, 0), size=(1920 x 1080) for module 'Menu'.
< 336.4610> [Skin] Processing screen 'MenuSummary' from list 'menu_shutdownSummary, MenuSummary, ScreenSummary, menu_shutdown_summary, Menu_summary, SimpleSummary', position=(0, 0), size=(128 x 32) for module 'MenuSummary'.
< 336.6324> [eInputDeviceInit] 0 160 (352) 1
< 336.6324> [eRCDeviceInputDev] emit: 0
< 336.6328> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 336.6362> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 336.6362> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 336.6363> [eDVBChannel] OURSTATE: failed, retune
< 336.6363> [eDVBFrontend0] tune
< 336.6363> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 336.6363> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 336.6363> [eDVBFrontend0] tuning to 1870 mhz
< 336.6363> [eDVBChannel] OURSTATE: tuning
< 336.6364> [eDVBServicePMTHandler] tune failed.
< 336.6364> [eDVBServicePlay] DVB service failed to tune - error 1
< 336.6368> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 336.6368> [eDVBServicePMTHandler] incorrect namespace. expected: 6400000 current: ffffffff
< 336.6368> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 223 current: ffffffff
< 336.6368> [eDVBServicePMTHandler] incorrect original_network_id. expected: 1010 current: ffffffff
< 336.6369> [eDVBFrontend0] invalidate current switch params
< 336.6369> [eDVBFrontend0] set sequence pos 3
< 336.6370> [eDVBFrontend0] set sequence pos 3
< 336.6370> [eDVBFrontend0] update current switch params
< 336.6370> [eDVBFrontend0] startTuneTimeout 5000
< 336.6371> [eDVBFrontend0] setFrontend 1
< 336.6371> [eDVBFrontend0] setting frontend
< 336.6827> [eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
< 336.6827> [eDVBFrontend0] sleep 500ms
< 336.8171> [eDVBServicePlay] Start timeshift!
< 338.0893> [eInputDeviceInit] 1 67 (103) 1
< 338.0893> [eRCDeviceInputDev] emit: 1
< 338.0898> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 338.3043> [eInputDeviceInit] 0 67 (103) 1
< 338.3044> [eRCDeviceInputDev] emit: 0
< 338.3048> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 338.3683> [eInputDeviceInit] 1 67 (103) 1
< 338.3686> [eRCDeviceInputDev] emit: 1
< 338.3693> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 338.5200> [eInputDeviceInit] 0 67 (103) 1
< 338.5205> [eRCDeviceInputDev] emit: 0
< 338.5215> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 338.6161> [eInputDeviceInit] 1 67 (103) 1
< 338.6166> [eRCDeviceInputDev] emit: 1
< 338.6172> [InfoBarGenerics] Key: 103 (Make) KeyID='KEY_UP' Binding='('UP',)'.
< 338.8001> [eInputDeviceInit] 0 67 (103) 1
< 338.8005> [eRCDeviceInputDev] emit: 0
< 338.8011> [InfoBarGenerics] Key: 103 (Break) KeyID='KEY_UP' Binding='('UP',)'.
< 339.0500> [eInputDeviceInit] 1 160 (352) 1
< 339.0505> [eRCDeviceInputDev] emit: 1
< 339.0511> [InfoBarGenerics] Key: 352 (Make) KeyID='KEY_OK' Binding='('OK',)'.
< 339.0515> [ActionMap] Keymap 'OkCancelActions' -> Action = 'ok'.
< 339.0549> [Skin] Processing screen 'MessageBoxSimple', position=(480, 532), size=(960 x 15) for module 'TryQuitMainloop'.
< 339.0630> [Screen] Warning: Skin is missing element 'icon' in <class 'Screens.Standby.TryQuitMainloop'>(Recording(s) are in progress or coming up in few seconds!

Really reboot now?).< 339.0639>
< 339.0648> [Pixmap] setPixmapNum(0) failed! defined pixmaps: []
< 339.0672> [Skin] Processing screen 'MessageBoxSimple_summary' from list 'MessageBoxSimpleSummary, ScreenSummary, MessageBoxSimple_summary, SimpleSummary', position=(0, 0), size=(128 x 32) for module 'ScreenSummary'.
< 339.2323> [eInputDeviceInit] 0 160 (352) 1
< 339.2323> [eRCDeviceInputDev] emit: 0
< 339.2327> [InfoBarGenerics] Key: 352 (Break) KeyID='KEY_OK' Binding='('OK',)'.
< 339.5373> [eDVBFrontend0] fe event: status 20, inversion off, m_tuning 2
< 339.5373> [eDVBFrontend0] FE_TIMEDOUT! ..abort
< 339.5373> [eDVBChannel] OURSTATE: failed, retune
< 339.5373> [eDVBFrontend0] tune
< 339.5374> [eDVBSatelliteEquipmentControl] RotorCmd ffffffff, lastRotorCmd ffffffff
< 339.5374> [eDVBFrontend0] prepare_sat System 1 Freq 12470000 Pol 0 SR 47300000 INV 2 FEC 8 orbpos 1600 system 1 modulation 1 pilot 2, rolloff 0, is_id 121, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
< 339.5374> [eDVBFrontend0] tuning to 1870 mhz
< 339.5374> [eDVBChannel] OURSTATE: tuning
How far apart timewise are the tests between atv and vix? The tuners on the mio4k need a good signal to consistently lock - depending on the time of day sometimes it takes ages (if at all) to hold - been testing another box using the same input and it has no issues

[Huevos]

Also post a debug log from ATV so we can see the tuning parameters are identical.

[Aust-VAST]

How far apart timewise are the tests between atv and vix? The tuners on the mio4k need a good signal to consistently lock - depending on the time of day sometimes it takes ages (if at all) to hold - been testing another box using the same input and it has no issues

Good point, I have ATV 6.3 in slot 1 and VIX 6.3 in #2, can switch in the boot time between the two.

Signal wise, it is stable, especially on the low noise LNBF's from WOS.

Just now I ended 30 hours on ATV with PiP and I can switch to/ from standby, playback etc.

However swing over to slot #2 and VIX 6.3 and the box won't always return from standby "Tune failed" !

[Aust-VAST]

Also post a debug log from ATV so we can see the tuning parameters are identical.

Logs attached, VIX 6.3 and just before capture I put the OSIO MIO+ into standby which produced a "Tune failed".
(VIX 6.3-Enigma2_debug_2023-01-31_09-05-51.log).


Also attached is ATV 6.3 log and a switch to and back from standby didn't produce a "Tune failed" although to confuse things if the receiver is left in standby for an extended period, perhaps >20 minutes, sometimes it doesn't tune DVB-S2X whilst DVB-T2 is still working.
(ATV 6.3-Enigma2-debug-20230131_09-05-19.log).

[Aust-VAST]

64678

Signal and quality if relevant.

[Aust-VAST]

64679

Tuner wise, Unicable/SCR in ATV has the "Tuning algorithm" feature and it is working, (not that it is any advantage without an FBC such as in our DUO4KSE's).

Actually the signal is a little weaker in Unicable so reverting to legacy/ up on the roof again and its only 32°C today! :rolleyes:

[twol]

64679

Tuner wise, Unicable/SCR in ATV has the "Tuning algorithm" feature and it is working, (not that it is any advantage without an FBC such as in our DUO4KSE's).

Actually the signal is a little weaker in Unicable so reverting to legacy/ up on the roof again and its only 32°C today! :rolleyes:

Can you do one thing and eeither add or switch OpenATV to python 3 (7.2) .. just want both images off same base

[Aust-VAST]

Now that is interesting, moving to 7.2 and the MIO+ won't recover from standby and tune DVB-S2X on tuner A, and this is similar/ same as VIX 6.3 from what I can tell.

ATV 6.3 was more predictable and even if the USB HDD was in standby on 6.3 it would continue on tuner A.

ATV 7.2 log attached.

[Edit] Actually it is so brittle that If I edit Tuner A and don't zap back to the service, we are off tune/ 0 signal.

[Huevos]

Now that is interesting, moving to 7.2 and the MIO+ won't recover from standby and tune DVB-S2X on tuner A, and this is similar/ same as VIX 6.3 from what I can tell.

ATV 6.3 was more predictable and even if the USB HDD was in standby on 6.3 it would continue on tuner A.

ATV 7.2 log attached.

[Edit] Actually it is so brittle that If I edit Tuner A and don't zap back to the service, we are off tune/ 0 signal.


It makes no sense that it would work in ATV and not ViX as the tuning is done in the drivers.

Between OpenATV 6.3 and OpenATV 7.2 there have been 8 driver changes and 4 kernel changes.

And also difficult for us to check because it is related to this ACM transponder.

For me I don't suffer any tune failed.

Best course of action with this is report it to Edision.

One other possible test you could try is pull the drivers out of your OpenATV 6.3 image and try them in the later images.

[el bandido]

Octagon was mentioned, but we are discussing Edision MIO+, correct?

On the MIO+, you cannot swap tuner drivers unless the kernel is the same. Swapping drivers from different kernels will cause the MIO+ not to boot.

OpenATV 6.3 seems to be a 2018 image version. Edision added T2MI capabilities to the driver, but I cannot remember the exact year this was done? T2MI drivers made the AVL6261 perform a bit different on some transponders that are not T2MI, and I wonder if that has anything to do with the problem? Knowing the exact file size of the AVL6261 driver in the 6.3 ATV image might help as there is a difference in file sizes of T2MI and non-T2MI drivers. The location of the AVL6261.ko driver in the receiver is: lib--->modules--->5.15.0--->extra--->avl6261.ko.

Note that the 5.15.0 is the kernel version. This is the last kernel Edision released for the MIO+. OpenATV 6.3 would have a different folder number because the kernel is older. The location path in the receiver's files (except for the kernel number) for the avl6261.ko file is the same.

[Huevos]

Octagon was mentioned, but we are discussing Edision MIO+, correct?Yes, was a slip.

[Aust-VAST]

Hi everyone,

How are we going with this?

Is there some way I can log this condition to the makers' / coders for resolution in the drivers?

Thanks.

[el bandido]

Knowing the exact file size of the AVL6261 driver in the 6.3 ATV image might help as there is a difference in file sizes of T2MI and non-T2MI drivers. The location of the AVL6261.ko driver in the receiver is: lib--->modules--->5.15.0--->extra--->avl6261.ko.

What is the Exact size of your driver file in the 6.3 ATV image??

[Aust-VAST]

Knowing the exact file size of the AVL6261 driver in the 6.3 ATV image might help as there is a difference in file sizes of T2MI and non-T2MI drivers. The location of the AVL6261.ko driver in the receiver is: lib--->modules--->5.15.0--->extra--->avl6261.ko.

What is the Exact size of your driver file in the 6.3 ATV image??

Hi thanks,

It is:

64730

Any value in attaching it to a post?

I also contacted Edision Tech and they said the behaviour is specific to the O/s and couldn't assist further and referred me to this forum after looking at this thread.

> which EDISION is not involved into.

[el bandido]

That thing is 106KB which I am fairly certain is Not T2MI. Was the folder number 5.09 (lib--->modules--->5.09.0--->extra--->avl6261.ko)?

Anyway, attached is a non-T2MI driver for kernel 5.15. Replace the file here: lib--->modules--->5.15.0--->extra--->avl6261.ko
Then REBOOT the receiver.
Save your original avl6261.ko file that is in the 5.15--->extra folder so you can replace it if the image does not boot. The attached file is for kernel 5.15. It is a No T2MI driver. I think you should be able to find the kernel information in About (Menu--->Information--->About).

The receiver will Not Boot completely if you install the attached driver in an image that is not 5.15 kernel!!!

[Aust-VAST]

Swapped out the driver and rebooted.

Intial tests; Standby and resume from standby, play media and return to Tuner A, use tuner B and return to A, switch between sequential tuner A and B channels across bouquets.

All these work well, can it be done in VIX?

[Huevos]

ViX is built from oe-alliance-core so it gets the latest drivers. No idea which drivers these are. And if there are newer drivers they must fix something, they wouldn't have been created for nothing. Someone needs to write to Edision and tell them the problem and which drivers work.

[Aust-VAST]

Swapped out the driver and rebooted. All these work well, can it be done in VIX?

Swapped out the driver in VIX as I noticed the Kernel was the same and all excellent. :cool:

[el bandido]

That driver file will work in any image as long as the folder in the file path to install it has 5.15 which is the kernel version. Edision seems to have quit updating the kernel, so keep your driver file for use on future images.

[el bandido]

ViX is built from oe-alliance-core so it gets the latest drivers. No idea which drivers these are. And if there are newer drivers they must fix something, they wouldn't have been created for nothing. Someone needs to write to Edision and tell them the problem and which drivers work.

To make a long story short, there is nothing special about that driver, except it does not have T2MI capability. When T2MI was added to the driver, it messed up some channels on transponders that were spaced closely together on North American satellites. A request was made to Edision to provide a non-T2MI driver so we could enjoy the channels on the closely spaced transponders in future images. The non-T2MI driver also blindscans DVB-S/S2 slightly different than the T2MI driver.

The non-T2MI driver would have little if any advantages when used in Europe, and that is probably why it was never added in a proper fashion.

[Aust-VAST]

Hi all,

Finally migrated the MIO+ 4K into the HT.

I hadn't touched it for seven months and it powered up perfectly on all the services, so swapped out the "VU+ DUO 4K SE" seamlessly to the attachments (Sony combo amp, Sony HDTV and RM-VLZ620 rcu.

Second day it was working rather hard on a sport program (car racing) and we did lose the DVB-T tuner (locked up / still image) and I was told that switching to DVB-S and back to DVB-T solved the outage, so no reboot required.

Other than that, very impressive.

My question is (from the very informed here), is there an equivalent specification on the market (50,000+ SR, internal HDD, multi DVB-T tuners, we miss the ability of the DUO 4K SE) to record multiple DVB-T services' as a background capture of preferred programs, ever day). :)

[Huevos]

Simple answer is no. There is nothing on the market with more that 2 DVB-T tuners except expensive boxes like the Duo4k and then you have 4... or use USB tuners, which is horrible.

[ArloGuthrie]

If I may. Since we appear as if we know a bit about tuner drivers I would like to suggest an idea.
I have the os mio4K. Used OpenATV for the longest time. Eventually installing ver. 7.
Currently running ViX 6.4. Versus 6.3 is seems to start a bit slow. Hanging a bit on 35 on the display before muddling to operation.
I also have TNAP installed in a slot. I don't use it much. ViX is what I now use all of the time.

In blindscans for the USA I noticed some missed transponders with ViX. Narrowing my scanning ranges helped a bit. But sometimes not.
TNAP hit them every time. Speaking of closely spaced tp frequencies.
I got curious and placed the TNAP tuner drivers in ViX and re-scanned the problem satellites. The issues were solved. So that is now "how I roll".
Just because the image is tweaked for N. America doesn't particularly mean it won't work for other regions. And the tuner drivers were directly developed to address closely spaced transponders and such.

[Huevos]

Which tuner drivers? Are you saying those drivers are for the internal tuner. If so where can we get those from?

[ArloGuthrie]

LegitFTA. Get the TNAP multiboot image. Extract with 7zip. Extract until you get to rootfs.tar group. Keep extracting until you get to the familiar E2 file system.
Your drivers are in the usual lib/modules directories. Hopefully you can take it from there.

[el bandido]

Which tuner drivers? Are you saying those drivers are for the internal tuner. If so where can we get those from?

See posts #23 and #28 of this thread.

[Aust-VAST]

Simple answer is no. There is nothing on the market with more that 2 DVB-T tuners except expensive boxes like the Duo4k and then you have 4... or use USB tuners, which is horrible.

Thanks for the reply and on that advice I will keep the DUO4k and return it to the HT as a network mount so we can use the multi tuners' again, should be good and, I am planning a :thumbsup: 2.4M PF antenna.

[Aust-VAST]

We are experiencing some frequent picture freezes with audio drop out on DTV, solution is to use Tuner A for a moment then revert to Tuner B again; All ok for maybe the rest of the day.

I have replaced the 23 year old MH amp and its external 4G LTE low pass filter with a new fully screened variant including an internal low pass filter at 16M on our comms tower where there is a high gain array for the sender 59KM away.

Better S/n and stable pic now DVB-T, but still the freezes persist.

Maybe the earlier driver for this tuner, as with the satellite side in post #23 in this thread.