Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 1 of 3 123 LastLast
Results 1 to 15 of 36

Thread: Edision MIO+ 4K Australian experience

  1. #1
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts

    Edision MIO+ 4K Australian experience

    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 but they won't work other than legacy mode.

    Enigma2_debug_2023-01-04_15-58-39.log
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  2. #2
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,945
    Thanks
    2,062
    Thanked 5,145 Times in 3,395 Posts
    This is most likely due to incorrect timing setup of Unicable LNB.

    Start by reading this thread:
    https://www.world-of-satellite.com/s...ailed-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.
    Help keep OpenViX servers online.Please donate!

  3. The Following User Says Thank You to Huevos For This Useful Post:

    Aust-VAST (06-01-23)

  4. #3
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,945
    Thanks
    2,062
    Thanked 5,145 Times in 3,395 Posts
    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.
    Help keep OpenViX servers online.Please donate!

  5. The Following User Says Thank You to Huevos For This Useful Post:

    Aust-VAST (06-01-23)

  6. #4
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    Quote Originally Posted by Huevos View Post
    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.
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  7. #5
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    Quote Originally Posted by Huevos View Post
    This is most likely due to incorrect timing setup of Unicable LNB.

    Start by reading this thread:
    https://www.world-of-satellite.com/s...ailed-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/s...rom-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.
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  8. #6
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    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.

    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).
    Attached Files Attached Files
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  9. #7
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    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
    Attached Files Attached Files
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  10. #8
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,945
    Thanks
    2,062
    Thanked 5,145 Times in 3,395 Posts
    It makes no sense that it would work in ATV and not ViX as the tuning is done in the drivers.
    Help keep OpenViX servers online.Please donate!

  11. #9
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,618
    Thanks
    1,009
    Thanked 2,964 Times in 2,305 Posts
    Quote Originally Posted by Aust-VAST View Post
    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
    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)
    .......................
    Vu+ Uno4KSE, Dreambox dm900
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  12. The Following User Says Thank You to twol For This Useful Post:

    Aust-VAST (30-01-23)

  13. #10
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,945
    Thanks
    2,062
    Thanked 5,145 Times in 3,395 Posts
    Also post a debug log from ATV so we can see the tuning parameters are identical.
    Help keep OpenViX servers online.Please donate!

  14. The Following User Says Thank You to Huevos For This Useful Post:

    Aust-VAST (30-01-23)

  15. #11
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    Quote Originally Posted by twol View Post
    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" !
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  16. #12
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    Quote Originally Posted by Huevos View Post
    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).
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  17. #13
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    screenshot_20230131122329.jpg

    Signal and quality if relevant.
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  18. #14
    Aust-VAST's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Jan 2018
    Location
    Central NSW Australia
    Posts
    73
    Thanks
    67
    Thanked 17 Times in 14 Posts
    OpenATV-Tuner-Config-122329.jpg

    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!
    --

    "corporate greed and chemicals are killin' the land" Neil Young - Greendale 2004.

  19. #15
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,618
    Thanks
    1,009
    Thanked 2,964 Times in 2,305 Posts
    Quote Originally Posted by Aust-VAST View Post
    OpenATV-Tuner-Config-122329.jpg

    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!
    Can you do one thing and eeither add or switch OpenATV to python 3 (7.2) .. just want both images off same base
    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)
    .......................
    Vu+ Uno4KSE, Dreambox dm900
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  20. The Following User Says Thank You to twol For This Useful Post:

    Aust-VAST (01-02-23)

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.