Anysee E30 DVB-T kaukosäädin, eikö enää tarvita LIRC paketteja?

[Marko5]

Yritin virittää Anysee E30 DVB-T laitteen kaukosäädintä toimimaan. Tarvitaanko enää LIRCin paketteja, että laitteen saisi ohjaamaan VDR, Kaffeine tai VLC ohjelmia? Nyt kun laite tunnistuu eventiksi niin on mennyt vähän sormi suuhun.

lsusb

Koodia: [Valitse]

Bus 001 Device 002: ID 04b4:861f Cypress Semiconductor Corp. Anysee E30 USB 2.0 DVB-T Receiver
evtest

Koodia: [Valitse]

     
    /dev/input/event6:      IR-receiver inside an USB DVB receiver

    Input driver version is 1.0.1
    Input device ID: bus 0x3 vendor 0x4b4 product 0x861f version 0x100
    Input device name: "IR-receiver inside an USB DVB receiver"
    Supported events:

      Event type 0 (EV_SYN)
      Event type 1 (EV_KEY)
        Event code 2 (KEY_1)
        Event code 3 (KEY_2)
        Event code 4 (KEY_3)
        Event code 5 (KEY_4)
        Event code 6 (KEY_5)
        Event code 7 (KEY_6)
        Event code 8 (KEY_7)
        Event code 9 (KEY_8)
        Event code 10 (KEY_9)
        Event code 11 (KEY_0)
        Event code 113 (KEY_MUTE)
        Event code 114 (KEY_VOLUMEDOWN)
        Event code 115 (KEY_VOLUMEUP)
        Event code 119 (KEY_PAUSE)
        Event code 128 (KEY_STOP)
        Event code 139 (KEY_MENU)
        Event code 142 (KEY_SLEEP)
        Event code 167 (KEY_RECORD)
        Event code 207 (KEY_PLAY)
        Event code 212 (KEY_CAMERA)
        Event code 352 (KEY_OK)
        Event code 355 (KEY_CLEAR)
        Event code 356 (KEY_POWER2)
        Event code 358 (KEY_INFO)
        Event code 363 (KEY_CHANNEL)
        Event code 364 (KEY_FAVORITES)
        Event code 365 (KEY_EPG)
        Event code 368 (KEY_LANGUAGE)
        Event code 370 (KEY_SUBTITLE)
        Event code 372 (KEY_ZOOM)
        Event code 375 (KEY_SCREEN)
        Event code 385 (KEY_RADIO)
        Event code 388 (KEY_TEXT)
        Event code 393 (KEY_VIDEO)
        Event code 398 (KEY_RED)
        Event code 399 (KEY_GREEN)
        Event code 400 (KEY_YELLOW)
        Event code 401 (KEY_BLUE)
        Event code 402 (KEY_CHANNELUP)
        Event code 403 (KEY_CHANNELDOWN)
        Event code 407 (KEY_NEXT)
        Event code 412 (KEY_PREVIOUS)
        Event code 464 (KEY_FN)
      Event type 4 (EV_MSC)
        Event code 4 (MSC_SCAN)
      Event type 20 (EV_REP)
    Testing ... (interrupt to exit)

    Event: time 1400787558.229902, type 4 (EV_MSC), code 4 (MSC_SCAN), value 814
    Event: time 1400787558.229904, type 1 (EV_KEY), code 403 (KEY_CHANNELDOWN), value 1
    Event: time 1400787558.229905, -------------- SYN_REPORT ------------
    Event: time 1400787558.481559, type 1 (EV_KEY), code 403 (KEY_CHANNELDOWN), value 0
    Event: time 1400787558.481560, -------------- SYN_REPORT ------------
    Event: time 1400787560.245902, type 4 (EV_MSC), code 4 (MSC_SCAN), value 811
    Event: time 1400787560.245905, type 1 (EV_KEY), code 402 (KEY_CHANNELUP), value 1
    Event: time 1400787560.245906, -------------- SYN_REPORT ------------
    Event: time 1400787560.497531, type 1 (EV_KEY), code 402 (KEY_CHANNELUP), value 0
    Event: time 1400787560.497532, -------------- SYN_REPORT ------------
    Event: time 1400787561.253902, type 4 (EV_MSC), code 4 (MSC_SCAN), value 813
    Event: time 1400787561.253906, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
    Event: time 1400787561.253907, -------------- SYN_REPORT ------------
    Event: time 1400787561.505521, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
    Event: time 1400787561.505522, -------------- SYN_REPORT ------------
    Event: time 1400787564.781905, type 4 (EV_MSC), code 4 (MSC_SCAN), value 805
    Event: time 1400787564.781908, type 1 (EV_KEY), code 6 (KEY_5), value 1
    Event: time 1400787564.781909, -------------- SYN_REPORT ------------
    55Event: time 1400787565.033548, type 1 (EV_KEY), code 6 (KEY_5), value 0
    Event: time 1400787565.033549, -------------- SYN_REPORT ------------
    Event: time 1400787565.537904, type 4 (EV_MSC), code 4 (MSC_SCAN), value 802
    Event: time 1400787565.537908, type 1 (EV_KEY), code 3 (KEY_2), value 1
    Event: time 1400787565.537909, -------------- SYN_REPORT ------------
    22Event: time 1400787565.789548, type 1 (EV_KEY), code 3 (KEY_2), value 0
    Event: time 1400787565.789549, -------------- SYN_REPORT ------------
    Event: time 1400787566.545902, type 4 (EV_MSC), code 4 (MSC_SCAN), value 804
    Event: time 1400787566.545905, type 1 (EV_KEY), code 5 (KEY_4), value 1
    Event: time 1400787566.545906, -------------- SYN_REPORT ------------
    4Event: time 1400787566.797513, type 1 (EV_KEY), code 5 (KEY_4), value 0
    Event: time 1400787566.797514, -------------- SYN_REPORT ------------
    Event: time 1400787574.365905, type 4 (EV_MSC), code 4 (MSC_SCAN), value 821
    Event: time 1400787574.365908, type 1 (EV_KEY), code 375 (KEY_SCREEN), value 1
    Event: time 1400787574.365909, -------------- SYN_REPORT ------------
    Event: time 1400787574.617552, type 1 (EV_KEY), code 375 (KEY_SCREEN), value 0
    Event: time 1400787574.617553, -------------- SYN_REPORT ------------


[Marko5]

ir-keytable or: How I Learned to Stop Worrying about the LIRC Kernel Tuon perusteella tarvitsis, mutta jokin on omalla kohdallani väärin, sillä evtest komento ei kerro mitään tuettuja protokollia.  Myös näppäilyt toistuvat tuplina evtestissä.

[Postimies]

Tarkoitatko vdr-sxfe ohjaamista? Lirc-tarvitaan tuohon. Monet lirc ajurit nykyään kernelissä Ja X:n evdev tunnistaa kauko-ohjaimen usein näppäimistöksi. Usein nuo kaksi yhdessä aiheittavat tuplaklikkauksia. XBMC toimii ilman lirc asennusta esim MCE yhteesopivalla kakella. Iselläni on Anysee E30 DVB-C ja kauko-ohjain toistaiseksi käyttämättä. Kerro jos toimii vdr-sxfe kanssa.