[SOLVED] YaVDR 0.5 + Hauppauge Remote don't work

  • Hi everybody,


    I just finish to install YaVDR 0.5.0 on my Asus eeBox EB1501.
    Everything working well but i have a problem with the remote.
    My DVB-T adapter is a Hauppauge WinTV NOVA-T USB2 with a inside IR receiver


    Here some informations and tests i have allready do :


    dmesg :

    Code
    [   16.960501] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state.
    [   16.960814] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
    [   16.964589] DVB: registering new adapter (Hauppauge WinTV-NOVA-T usb2)
    [   16.965640] dvb-usb: MAC address: 00:0d:fe:ff:ff:ff
    [   16.970798] DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)...
    [   17.057241] FS-Cache: Loaded
    [   17.560506] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:06.1/usb2/2-3/input/input5
    [   17.560789] dvb-usb: schedule remote query interval to 100 msecs.
    [   17.560807] dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected.
    [   17.560902] usbcore: registered new interface driver dvb_usb_nova_t_usb2


    lsusb :

    Code
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
    Bus 003 Device 002: ID 04f2:0860 Chicony Electronics Co., Ltd 2.4G Multimedia Wireless Kit
    Bus 002 Device 002: ID 2040:9301 Hauppauge WinTV NOVA-T USB2 (warm)


    cat /proc/bus/input/devices :


    ir-keytable :

    Code
    Couldn't find any node at /sys/class/rc/rc*.


    evtest /dev/input/event5 :


    Result when i push some keys on remote :


    A idea ?


    Thanks in advance.

    VDRBox : yaVDR-0.5 - eeBox Asus EB1501 - Intel ATOM N330 / 2 Go / 320 Go / GeForce 9400 ION - TT Connect 3600 / WinTV NOVA-T USB2 - VDRUser #1112

    Einmal editiert, zuletzt von alien2924 ()

  • Hello,

    A idea ?


    You might have to add an udev rule in order to tell eventlircd to read from the kernel input device created for your IR receiver.


    Can you post the udev information about the receiver?

    Code
    udevadm info --query=all --attribute-walk --name=/dev/input/event5

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Hi seahawk1986


    Thank's for you quick response !


    Here the result :

    VDRBox : yaVDR-0.5 - eeBox Asus EB1501 - Intel ATOM N330 / 2 Go / 320 Go / GeForce 9400 ION - TT Connect 3600 / WinTV NOVA-T USB2 - VDRUser #1112

  • Try to add this to your /lib/udev/rules.d/98-eventlircd.rules (at this position: https://github.com/yavdr/yavdr…8-eventlircd.rules#L163):

    Code
    ATTRS{idVendor}=="2040", ATTRS{idProduct}=="9301", \
      ENV{eventlircd_enable}="true", \
      ENV{eventlircd_evmap}="03_$attr{idVendor}_$attr{idProduct}.evmap"


    Also you need to create an evmap (to remap the keys on the remote):

    Code
    sudo touch /etc/eventlircd.d/03_2040_9301.evmap


    After a reboot you should be able to see the key presses when running

    Code
    sudo irw

    and most keys should work already for the VDR and XBMC.


    According to the output of evtest there are some keys you might want to remap to another key name:

    Code
    KEY_KPASTERISK
    KEY_POWER
    KEY_BACK
    KEY_GOTO
    KEY_TV
    KEY_RADIO
    KEY_AUDIO
    KEY_VIDEO
    KEY_LAST


    So for example you could write something like this in the evmap file:

    Code
    KEY_POWER = KEY_POWER2
    KEY_BACK = KEY_ESC
    KEY_LAST = KEY_PREVIOUS


    You can find the expected key names and their functions in this table: http://www.yavdr.org/documenta…n/ch03s03.html#idp6187920


    To apply changes you made to an evmap simply restart eventlircd:

    Code
    sudo restart eventlircd

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Wonderful, everything works perfectly now that either VDR or XBMC :]


    Thank you very much seahawk1986, you are the best.


    Here is a copy of then new 98-eventlircd.rules file with modification so you can add it automatically in future releases of yaVDR


    I finish to write the 03_2040_9301.evmap remap file and I'll put it available tomorrow so you can also add it for future releases of yaVDR.


    Bye.
    alien2924.

    VDRBox : yaVDR-0.5 - eeBox Asus EB1501 - Intel ATOM N330 / 2 Go / 320 Go / GeForce 9400 ION - TT Connect 3600 / WinTV NOVA-T USB2 - VDRUser #1112

  • Hello,


    as promised, here is the final file 03_2040_9301.evmap :

    Code
    KEY_KPASTERISK = KEY_INFO
    KEY_POWER  	= KEY_POWER2
    KEY_BACK   	= KEY_ESC
    KEY_GOTO   	= KEY_TEXT
    KEY_TV     	= KEY_SUBTITLE
    KEY_RADIO  	= KEY_TIME
    KEY_AUDIO  	= KEY_MODE
    KEY_VIDEO  	= KEY_PVR
    KEY_LAST   	= KEY_PREVIOUS
    KEY_GRAVE  	= KEY_SETUP


    Bye

    VDRBox : yaVDR-0.5 - eeBox Asus EB1501 - Intel ATOM N330 / 2 Go / 320 Go / GeForce 9400 ION - TT Connect 3600 / WinTV NOVA-T USB2 - VDRUser #1112

  • Thank you very much, I added the extended udev rule and the evmap to the yavdr-remote package.

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Ich hätte da auch noch nen Empfänger, siehe signatur, allerdings mit eigener rc_map, sonst prellen mit ner Harmany die Tasten wie sau, trotz repeat filter..


    patch für 98-eventlird.rules:


    03_147a_e03e.evmap:


    und die rc-keymap:

  • allerdings mit eigener rc_map, sonst prellen mit ner Harmany die Tasten wie sau, trotz repeat filter..

    Mir ist nicht so ganz klar, warum das einen Unterschied machen sollte ?(
    IMHO ist es nicht sinnvoll lirc (und mehr als die benötigten Protokolle) in der keymap zu setzen, reicht da nicht einfach dieser Header?

    Code
    # table rc-rc6-mce, type:RC-6


    BTW: was für ein Profil hast du bei der Harmony eingestellt?

    yaVDR-Dokumentation (Ceterum censeo enchiridia esse lectitanda.)

  • Eingestellt ist das Windows MediaCenter SE.


    Die SmartRemote, reagirt anders als die One, welche ich vorher hatte, die lags usw. sind völlig verschwunden, reagiert also sofort.
    Ich weiss auch nicht, woran es liegt aber mit der HOPLOrc6 hatte ich immer doppelte Tastendrücke. Ich hab dann mit deinem rc-core-script die map erstellt und das problem war verschwunden. Insofern hab ich nicht weiter gesucht, weil es einfacher war da zwei custom templates drum zu klöpeln.
    Ich hab ende nächster Woche Urlaub, kann dann mal schauen ob ich ne lösung finde die standard-konformer ist.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!