Ergebnis 1 bis 8 von 8

Thema: RCU Button

  1. #1
    Anfänger
    Registriert seit
    30.12.2018
    Beiträge
    26
    Thanks (gegeben)
    7
    Thanks (bekommen)
    2
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke

    RCU Button

    Context button on my Amiko vipercombohdd RCU does not work. No response from the box at all.
    Looking at IR of RCU with mobile phone camera, I can see the IR is flashing when I press the button.
    The button works OK on virtual RCU in OpenWebif. It shows extension selection menu when clicked.
    Also Hotkey Setup is possible in OpenWebif interface as the printscreen shows.

    RCU Button-rcu.jpg

    Any idea what could be wrong?

    •   Alt Advertising

       

  2. #2
    Avatar von Mr.Servo
    Registriert seit
    10.08.2020
    Ort
    Pfalz / Palatinate
    Beiträge
    2.656
    Thanks (gegeben)
    1811
    Thanks (bekommen)
    2434
    Total Downloaded
    56,91 MB
    Total Downloaded
    56,91 MB
    ReceiverDanke
    Box 1:
    GigaBlue UHD UE 4k Cable (openATV 7.4)
     
     
    Box 2:
    Mut@nt HD51 4k Cable (oATV DEVEL)
     
     
    Hi again

    Just an idea: Maybe you have to change to another remote control driver? Seems to be that the RCU-button is "unknown" due to using "not correct" remote control driver? Maybe there are existing some RC-designs for your box...?

    You find this under "Extended GUI -> Input devices" (example for a Mut@nt HD51, RCs have been delivered by image)
    RCU Button-eingabegeraet_auswaehlen.jpg

    Regards.......Mr.Servo

  3. #3
    Anfänger
    Registriert seit
    30.12.2018
    Beiträge
    26
    Thanks (gegeben)
    7
    Thanks (bekommen)
    2
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    Hi Mr.Servo,
    I have dreambox advanced remote control (native) in my image.
    I asked s3n0 yesterday, to check his Formuler F4 Turbo, because RCU of Formuler looks exactly the same as mine.
    His button works. So the question is: what is the Formuler's input device?

    Regards, smilan1

  4. #4
    Avatar von Mr.Servo
    Registriert seit
    10.08.2020
    Ort
    Pfalz / Palatinate
    Beiträge
    2.656
    Thanks (gegeben)
    1811
    Thanks (bekommen)
    2434
    Total Downloaded
    56,91 MB
    Total Downloaded
    56,91 MB
    ReceiverDanke
    Box 1:
    GigaBlue UHD UE 4k Cable (openATV 7.4)
     
     
    Box 2:
    Mut@nt HD51 4k Cable (oATV DEVEL)
     
     
    Sorry, I have no further ideas.

    But follow this thread in the next days, maybe a solution will occure here. @feedhunter will have the same problem with his F3 and F4 keys on his RCU.

    Regards.......Mr.Servo

  5. Thanks smilan1 bedankten sich
  6. #5
    Anfänger
    Registriert seit
    30.12.2018
    Beiträge
    26
    Thanks (gegeben)
    7
    Thanks (bekommen)
    2
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    I've got an information, that on Formuler 4 Turbo running OpenATV 6.4 Context button works.

    Can someone who owns that box help here?

    E.g.
    - what is the box Input device? Is different from dreambox advanced remote control (native)?
    - what is the code in debug mode that box receives when the Context button is pressed? Is it "438"?
    - keyids.py
    - keymap.xml
    - or anything else involved

    Thanks in advance.

  7. #6
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Ort
    Slovakia
    Beiträge
    1.463
    Thanks (gegeben)
    91
    Thanks (bekommen)
    420
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDanke
    Box 1:
    Vu+ Zero 4K
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    If this "Context" button works via OpenWebif, then OpenATV responds to the function correctly and that mean - the error must then be in the RCU hardware driver, which probably does not recognize this IR code from the RCU or the error is maybe in the RCU button codes.

    You also wrote in a private message that you do not see any reaction to pressing the RCU "Context" button in the debug-log. But the other RCU buttons respond correctly. So even this gives indications that the error is either in the hardware driver or in the RCU button codes.

    Try to check again at all and what code is shown in the Enigma2 debug-log if you press the "Context" button on your RCU (on your Amiko device "ViperComboHDD"). Or is there really no code in the debug-log ? Is there no response ?


    EDIT:

    As for the code of the "Context" button in OpenATV 6.4 - debug log, via the Formuler F4-Turbo device, here it is:
    Code:
    15:16:34.8854 [   ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 1 1b6 1
    15:16:35.0873 [   ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 0 1b6 1
    1B6 hex = 438 dec

    Also, this button code can be found in the OpenATV Enigma source code:
    enigma2/keyids.py at 6.4 . openatv/enigma2 . GitHub
    Code:
    "KEY_CONTEXT_MENU": 438

  8. Thanks Mr.Servo bedankten sich
  9. #7
    Anfänger
    Registriert seit
    30.12.2018
    Beiträge
    26
    Thanks (gegeben)
    7
    Thanks (bekommen)
    2
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    Bad news...

    20:19:48.3101 [ ] driver/rcinput.cpp:775 add [eInputDeviceInit] adding device /dev/input/event0
    20:19:48.3115 [ ] driver/rcinput.cpp:702 eRCDeviceInputDev [eRCDeviceInputDev] device "dreambox front panel" is a remotecontrol
    20:19:48.3118 [ ] driver/rcinput.cpp:775 add [eInputDeviceInit] adding device /dev/input/event1
    20:19:48.3123 [ ] driver/rcinput.cpp:702 eRCDeviceInputDev [eRCDeviceInputDev] device "dreambox advanced remote control (native)" is a remotecontrol
    20:19:48.3126 [ ] driver/rcinput.cpp:760 eInputDeviceInit [eInputDeviceInit] Found 2 input devices.
    ************************************************** *************
    20:23 HERE I PRESSED CONTEXT_BUTTON SEVERAL TIMES then INFO button
    ************************************************** *************
    20:23:18.8650 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 1 166 1
    20:23:18.8768 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:23:18+0100 [-] KEY: 358 0 KEY_INFO INFO
    20:23:19.1690 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 0 166 1
    20:23:19.1793 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:23:19+0100 [-] KEY: 358 1 KEY_INFO INFO
    20:23:24.1263 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 1 ae 1
    20:23:24.1324 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:23:24+0100 [-] KEY: 174 0 KEY_EXIT EXIT
    20:23:24.4323 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 0 ae 1
    20:23:24.4396 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:23:24+0100 [-] KEY: 174 1 KEY_EXIT EXIT
    ************************************************** *************
    20:27 HERE I PRESSED LONG_CONTEXT_BUTTON then EPG button
    ************************************************** *************
    20:27:06.8812 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 1 16d 1
    20:27:06.8875 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:27:06+0100 [-] KEY: 365 0 KEY_EPG EPG
    20:27:07.1924 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 0 16d 1
    20:27:10.7669 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 1 ae 1
    20:27:10.7734 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:27:10+0100 [-] KEY: 174 0 KEY_EXIT EXIT
    20:27:11.0724 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 0 ae 1
    20:27:11.0778 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:27:11+0100 [-] KEY: 174 1 KEY_EXIT EXIT
    20:27:20.5715 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 1 8b 1
    20:27:20.5789 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:27:20+0100 [-] KEY: 139 0 KEY_MENU MENU
    20:27:21.9980 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 0 8b 1
    20:27:22.0030 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:27:22+0100 [-] KEY: 139 1 KEY_MENU MENU
    20:27:23.4658 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 1 6c 1
    20:27:23.4710 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:27:23+0100 [-] KEY: 108 0 KEY_DOWN DOWN
    20:27:23.7765 [ ] driver/rcinput.cpp:38 handleCode [eRCDeviceInputDev] 0 6c 1
    20:27:23.7819 { } /usr/lib/python2.7/site-packages/twisted/python/util.py:815 untilConcludes 2021-01-19 20:27:23+0100 [-] KEY: 108 1 KEY_DOWN DOWN

  10. #8
    Anfänger
    Registriert seit
    30.12.2018
    Beiträge
    26
    Thanks (gegeben)
    7
    Thanks (bekommen)
    2
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    I got the information that ViperCombo RCU sends "0 FF 29" when Context button is pressed.
    It seems the code is missing in Box HW driver. Test from compatible Formuler RCU done with the same result.
    All buttons work, except Context button.
    Geändert von smilan1 (29.01.2021 um 19:31 Uhr)


Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 20:52 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2024 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,26%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com