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

alien2924 · February 18, 2014 at 6:21 PM

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 :

Code

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10000000000000 0


I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0


I: Bus=0003 Vendor=04f2 Product=0860 Version=0111
N: Name="Chicony 2.4G Multimedia Wireless Kit"
P: Phys=usb-0000:00:04.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb3/3-1/3-1:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7


I: Bus=0003 Vendor=04f2 Product=0860 Version=0111
N: Name="Chicony 2.4G Multimedia Wireless Kit"
P: Phys=usb-0000:00:04.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:04.0/usb3/3-1/3-1:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=17
B: KEY=70000 2000000 387ad801d001 1e000000000000 0
B: REL=103
B: MSC=10


I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Eee PC WMI hotkeys"
P: Phys=eeepc-wmi/input0
S: Sysfs=/devices/platform/eeepc-wmi/input/input4
U: Uniq=
H: Handlers=rfkill kbd event4
B: PROP=0
B: EV=100013
B: KEY=7e00000 0 0 0 0 11400800100000 8300080001100000 e000000000000 0
B: MSC=10


I: Bus=0003 Vendor=2040 Product=9301 Version=0000
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:00:06.1-3/ir0
S: Sysfs=/devices/pci0000:00/0000:00:06.1/usb2/2-3/input/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=400000000afc302 200280500000000 0 18000 18040000801 9e168000000000 80020000000ffc


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.0/sound/card0/input6
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=10


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.0/sound/card0/input7
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=4


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia Line-Out"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.0/sound/card0/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=40

Display More

ir-keytable :

Code

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

evtest /dev/input/event5 :

Code

Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x2040 product 0x9301 version 0x0
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 41 (KEY_GRAVE)
	Event code 55 (KEY_KPASTERISK)
	Event code 103 (KEY_UP)
	Event code 105 (KEY_LEFT)
	Event code 106 (KEY_RIGHT)
	Event code 108 (KEY_DOWN)
	Event code 113 (KEY_MUTE)
	Event code 114 (KEY_VOLUMEDOWN)
	Event code 115 (KEY_VOLUMEUP)
	Event code 116 (KEY_POWER)
	Event code 119 (KEY_PAUSE)
	Event code 128 (KEY_STOP)
	Event code 139 (KEY_MENU)
	Event code 158 (KEY_BACK)
	Event code 167 (KEY_RECORD)
	Event code 168 (KEY_REWIND)
	Event code 207 (KEY_PLAY)
	Event code 208 (KEY_FASTFORWARD)
	Event code 352 (KEY_OK)
	Event code 354 (KEY_GOTO)
	Event code 363 (KEY_CHANNEL)
	Event code 365 (KEY_EPG)
	Event code 377 (KEY_TV)
	Event code 385 (KEY_RADIO)
	Event code 392 (KEY_AUDIO)
	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 405 (KEY_LAST)
	Event code 407 (KEY_NEXT)
	Event code 442 (?)

Display More

Result when i push some keys on remote :

Code

Testing ... (interrupt to exit)Event: time 1392743839.301533, type 1 (EV_KEY), code 352 (KEY_OK), value 1
Event: time 1392743839.301537, -------------- SYN_REPORT ------------
Event: time 1392743839.301568, type 1 (EV_KEY), code 352 (KEY_OK), value 0
Event: time 1392743839.301571, -------------- SYN_REPORT ------------
Event: time 1392743840.001557, type 1 (EV_KEY), code 352 (KEY_OK), value 1
Event: time 1392743840.001560, -------------- SYN_REPORT ------------
Event: time 1392743840.001612, type 1 (EV_KEY), code 352 (KEY_OK), value 0
Event: time 1392743840.001615, -------------- SYN_REPORT ------------
Event: time 1392743840.301532, type 1 (EV_KEY), code 352 (KEY_OK), value 1
Event: time 1392743840.301536, -------------- SYN_REPORT ------------
Event: time 1392743840.301567, type 1 (EV_KEY), code 352 (KEY_OK), value 0
Event: time 1392743840.301569, -------------- SYN_REPORT ------------
Event: time 1392743840.701534, type 1 (EV_KEY), code 352 (KEY_OK), value 1
Event: time 1392743840.701538, -------------- SYN_REPORT ------------
Event: time 1392743840.701568, type 1 (EV_KEY), code 352 (KEY_OK), value 0
Event: time 1392743840.701570, -------------- SYN_REPORT ------------
Event: time 1392743843.801581, type 1 (EV_KEY), code 2 (KEY_1), value 1
Event: time 1392743843.801585, -------------- SYN_REPORT ------------
Event: time 1392743843.801619, type 1 (EV_KEY), code 2 (KEY_1), value 0
Event: time 1392743843.801622, -------------- SYN_REPORT ------------
Event: time 1392743844.801554, type 1 (EV_KEY), code 3 (KEY_2), value 1
Event: time 1392743844.801559, -------------- SYN_REPORT ------------
Event: time 1392743844.801587, type 1 (EV_KEY), code 3 (KEY_2), value 0
Event: time 1392743844.801589, -------------- SYN_REPORT ------------
Event: time 1392743845.001534, type 1 (EV_KEY), code 3 (KEY_2), value 1
Event: time 1392743845.001537, -------------- SYN_REPORT ------------
Event: time 1392743845.001565, type 1 (EV_KEY), code 3 (KEY_2), value 0
Event: time 1392743845.001568, -------------- SYN_REPORT ------------
Event: time 1392743845.801546, type 1 (EV_KEY), code 4 (KEY_3), value 1
Event: time 1392743845.801550, -------------- SYN_REPORT ------------
Event: time 1392743845.801577, type 1 (EV_KEY), code 4 (KEY_3), value 0
Event: time 1392743845.801580, -------------- SYN_REPORT ------------
Event: time 1392743846.901533, type 1 (EV_KEY), code 398 (KEY_RED), value 1
Event: time 1392743846.901536, -------------- SYN_REPORT ------------
Event: time 1392743846.901566, type 1 (EV_KEY), code 398 (KEY_RED), value 0
Event: time 1392743846.901570, -------------- SYN_REPORT ------------
Event: time 1392743847.501543, type 1 (EV_KEY), code 399 (KEY_GREEN), value 1
Event: time 1392743847.501546, -------------- SYN_REPORT ------------
Event: time 1392743847.501575, type 1 (EV_KEY), code 399 (KEY_GREEN), value 0
Event: time 1392743847.501577, -------------- SYN_REPORT ------------
Event: time 1392743848.401573, type 1 (EV_KEY), code 400 (KEY_YELLOW), value 1
Event: time 1392743848.401577, -------------- SYN_REPORT ------------
Event: time 1392743848.401609, type 1 (EV_KEY), code 400 (KEY_YELLOW), value 0
Event: time 1392743848.401612, -------------- SYN_REPORT ------------
Event: time 1392743848.901431, type 1 (EV_KEY), code 401 (KEY_BLUE), value 1
Event: time 1392743848.901435, -------------- SYN_REPORT ------------
Event: time 1392743848.901485, type 1 (EV_KEY), code 401 (KEY_BLUE), value 0
Event: time 1392743848.901488, -------------- SYN_REPORT ------------

Display More

A idea ?

Thanks in advance.

seahawk1986 · February 18, 2014 at 6:36 PM

Hello,

Quote from alien2924

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

alien2924 · February 18, 2014 at 6:51 PM

Hi seahawk1986

Thank's for you quick response !

Here the result :

Code

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.


  looking at device '/devices/pci0000:00/0000:00:06.1/usb2/2-3/input/input5/event5':
	KERNEL=="event5"
	SUBSYSTEM=="input"
	DRIVER==""


  looking at parent device '/devices/pci0000:00/0000:00:06.1/usb2/2-3/input/input5':
	KERNELS=="input5"
	SUBSYSTEMS=="input"
	DRIVERS==""
	ATTRS{name}=="IR-receiver inside an USB DVB receiver"
	ATTRS{phys}=="usb-0000:00:06.1-3/ir0"
	ATTRS{uniq}==""
	ATTRS{properties}=="0"


  looking at parent device '/devices/pci0000:00/0000:00:06.1/usb2/2-3':
	KERNELS=="2-3"
	SUBSYSTEMS=="usb"
	DRIVERS=="usb"
	ATTRS{configuration}==""
	ATTRS{bNumInterfaces}==" 1"
	ATTRS{bConfigurationValue}=="1"
	ATTRS{bmAttributes}=="80"
	ATTRS{bMaxPower}=="500mA"
	ATTRS{urbnum}=="6504028"
	ATTRS{idVendor}=="2040"
	ATTRS{idProduct}=="9301"
	ATTRS{bcdDevice}=="0000"
	ATTRS{bDeviceClass}=="00"
	ATTRS{bDeviceSubClass}=="00"
	ATTRS{bDeviceProtocol}=="00"
	ATTRS{bNumConfigurations}=="1"
	ATTRS{bMaxPacketSize0}=="64"
	ATTRS{speed}=="480"
	ATTRS{busnum}=="2"
	ATTRS{devnum}=="2"
	ATTRS{devpath}=="3"
	ATTRS{version}==" 2.00"
	ATTRS{maxchild}=="0"
	ATTRS{quirks}=="0x0"
	ATTRS{avoid_reset_quirk}=="0"
	ATTRS{authorized}=="1"
	ATTRS{product}=="SOHO-FX2"
	ATTRS{serial}=="9301-00-F00B3010"


  looking at parent device '/devices/pci0000:00/0000:00:06.1/usb2':
	KERNELS=="usb2"
	SUBSYSTEMS=="usb"
	DRIVERS=="usb"
	ATTRS{configuration}==""
	ATTRS{bNumInterfaces}==" 1"
	ATTRS{bConfigurationValue}=="1"
	ATTRS{bmAttributes}=="e0"
	ATTRS{bMaxPower}=="  0mA"
	ATTRS{urbnum}=="32"
	ATTRS{idVendor}=="1d6b"
	ATTRS{idProduct}=="0002"
	ATTRS{bcdDevice}=="0302"
	ATTRS{bDeviceClass}=="09"
	ATTRS{bDeviceSubClass}=="00"
	ATTRS{bDeviceProtocol}=="00"
	ATTRS{bNumConfigurations}=="1"
	ATTRS{bMaxPacketSize0}=="64"
	ATTRS{speed}=="480"
	ATTRS{busnum}=="2"
	ATTRS{devnum}=="1"
	ATTRS{devpath}=="0"
	ATTRS{version}==" 2.00"
	ATTRS{maxchild}=="6"
	ATTRS{quirks}=="0x0"
	ATTRS{avoid_reset_quirk}=="0"
	ATTRS{authorized}=="1"
	ATTRS{manufacturer}=="Linux 3.2.0-58-generic ehci_hcd"
	ATTRS{product}=="EHCI Host Controller"
	ATTRS{serial}=="0000:00:06.1"
	ATTRS{authorized_default}=="1"


  looking at parent device '/devices/pci0000:00/0000:00:06.1':
	KERNELS=="0000:00:06.1"
	SUBSYSTEMS=="pci"
	DRIVERS=="ehci_hcd"
	ATTRS{vendor}=="0x10de"
	ATTRS{device}=="0x0aa9"
	ATTRS{subsystem_vendor}=="0x1043"
	ATTRS{subsystem_device}=="0x83e9"
	ATTRS{class}=="0x0c0320"
	ATTRS{irq}=="18"
	ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000f"
	ATTRS{local_cpulist}=="0-3"
	ATTRS{numa_node}=="-1"
	ATTRS{dma_mask_bits}=="32"
	ATTRS{consistent_dma_mask_bits}=="32"
	ATTRS{enable}=="1"
	ATTRS{broken_parity_status}=="0"
	ATTRS{msi_bus}==""
	ATTRS{companion}==""
	ATTRS{uframe_periodic_max}=="100"


  looking at parent device '/devices/pci0000:00':
	KERNELS=="pci0000:00"
	SUBSYSTEMS==""
	DRIVERS==""

Display More

seahawk1986 · February 18, 2014 at 7:23 PM

Try to add this to your /lib/udev/rules.d/98-eventlircd.rules (at this position: https://github.com/yavdr/yavdr-re…cd.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/documentation/…html#idp6187920

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

Code

sudo restart eventlircd

alien2924 · February 18, 2014 at 8:23 PM

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

Code

################################################################################
# An example udev rules file for eventlircd.
#
# This rules file does not start eventlircd. Many applications only check for
# the lircd socket at application lauch. Therefore, it is better to start
# eventlircd in an init script so that eventlircd creates the lircd socket
# before any applications that use LIRC launch.
################################################################################


# eventlircd only does something for "add" and "remove" actions.
ACTION!="add|remove", GOTO="end"


# eventlircd only does something "input" subsystem devices.
SUBSYSTEM!="input", GOTO="end"


# eventlircd can only handle event devices.
KERNEL!="event[0-9]*", GOTO="end"


# eventlircd ignores devices created by eventlircd.
ATTRS{name}=="eventlircd", GOTO="end"


#-------------------------------------------------------------------------------
# Ask eventlircd to handle input event devices created by lircd. For this to
# work, lircd must be configured to output Linux input events and must be
# configured to output key names that conform to the LIRC namespace derived from
# the Linux key/button event names. This rule assumes that lircd performs all
# key mappings, so the rule does not provide a value for "eventlircd_evmap".
# For more information on lircd, see <http://www.lirc.org/>.
#-------------------------------------------------------------------------------
ATTRS{name}=="lircd", \
  ENV{eventlircd_enable}="true"


#-------------------------------------------------------------------------------
# Ask eventlircd to handle input event devices created by irserver2uinput. 
#-------------------------------------------------------------------------------
ATTRS{name}=="irserver2uinput", \
  ENV{eventlircd_enable}="true"


#-------------------------------------------------------------------------------
# Ask eventlircd to handle input event devices created by bdremoteng. For this
# to work, bdremoteng must be configured to output Linux input events and must
# be configured to output key names that conform to LIRC namespace derived
# from the Linux key/button event names. For more information on bdremoteng,
# see <http://code.google.com/p/bdremote-ng/>.
#-------------------------------------------------------------------------------
ATTRS{name}=="bdremoteng", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="bdremoteng.evmap"


#-------------------------------------------------------------------------------
# Ask eventlircd to handle input event devices created by wminput. This rule
# assumes that wminput performs all key mappings, so the rule does not provide a
# value for "eventlircd_evmap" For more information on wminput, see
# <http://abstrakraft.org/cwiid/>.
#-------------------------------------------------------------------------------
ATTRS{name}=="bdremoteng", \
  ENV{eventlircd_enable}="true"


#-------------------------------------------------------------------------------
# Ask eventlircd to handle input event devices created by ir-core (kernel).
#-------------------------------------------------------------------------------
SUBSYSTEMS=="rc", \
  ENV{eventlircd_enable}="true"


#-------------------------------------------------------------------------------
# overwrites for ircore mapping
#-------------------------------------------------------------------------------


SUBSYSTEM=="input", ATTRS{idVendor}=="1c73", ATTRS{idProduct}=="861f", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="anysee.evmap"


#-------------------------------------------------------------------------------
# Ask eventlircd to handle USB HID devices that show up as event devices and are
# known to be remote controls. For simplicity, the event map file names have the
# format <BUSTYPE>_<VENDOR>_<PRODUCT>.evmap.
#-------------------------------------------------------------------------------
SUBSYSTEMS=="usb", GOTO="begin-usb"
GOTO="end-usb"
LABEL="begin-usb"


ENV{ID_USB_INTERFACES}=="", IMPORT{program}="usb_id --export %p"


ENV{ID_VENDOR_ID}=="0419", ENV{ID_MODEL_ID}=="0001", \
  ENV{eventlircd_enable}="true",\
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="05a4", ENV{ID_MODEL_ID}=="9881", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="hama-mce.evmap"


ENV{ID_VENDOR_ID}=="4243", ENV{ID_MODEL_ID}=="ee08", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="1934", ENV{ID_MODEL_ID}=="5168", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="0755", ENV{ID_MODEL_ID}=="2626", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="045e", ENV{ID_MODEL_ID}=="006d", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="0766", ENV{ID_MODEL_ID}=="0204", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="1241", ENV{ID_MODEL_ID}=="e000", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="147a", ENV{ID_MODEL_ID}=="e02d", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="mce.evmap"


ENV{ID_VENDOR_ID}=="147a", ENV{ID_MODEL_ID}=="e03a", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="mce.evmap"


ENV{ID_VENDOR_ID}=="0c16", ENV{ID_MODEL_ID}=="0002", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="04_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="0755", ENV{ID_MODEL_ID}=="2626", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="0471", ENV{ID_MODEL_ID}=="060c", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="0471", ENV{ID_MODEL_ID}=="0815", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="18b1", ENV{ID_MODEL_ID}=="0037", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="04b4", ENV{ID_MODEL_ID}=="0100", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="04b4", ENV{ID_MODEL_ID}=="0101", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="1d57", ENV{ID_MODEL_ID}=="ac01", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap" 


ENV{ID_VENDOR_ID}=="22b8", ENV{ID_MODEL_ID}=="003b", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"


ENV{ID_VENDOR_ID}=="1784", ENV{ID_MODEL_ID}=="0004", \
  ENV{eventlircd_enable}="true", \
  ENV{eventlircd_evmap}="default.evmap"


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


# Enable wake-on-usb for the USB remotes.
ENV{eventlircd_enable}=="true", RUN+="wakeup_enable"


LABEL="end-usb"


LABEL="end"

Display More

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.

alien2924 · February 19, 2014 at 7:15 PM

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

seahawk1986 · February 19, 2014 at 7:57 PM

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

TesaFilm · February 23, 2014 at 11:39 AM

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:

Diff

--- 98-eventlircd.rules.orig    2014-02-23 11:13:12.111218463 +0100
+++ 98-eventlircd.rules 2014-02-23 11:14:18.236127390 +0100
@@ -121,6 +121,10 @@
   ENV{eventlircd_enable}="true", \
   ENV{eventlircd_evmap}="mce.evmap"
 
+ENV{ID_VENDOR_ID}=="147a", ENV{ID_MODEL_ID}=="e03e", \
+  ENV{eventlircd_enable}="true", \
+  ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"
+
 ENV{ID_VENDOR_ID}=="0c16", ENV{ID_MODEL_ID}=="0002", \
   ENV{eventlircd_enable}="true", \
   ENV{eventlircd_evmap}="04_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"

Display More

03_147a_e03e.evmap:

Code

KEY_EPG             = KEY_FN
KEY_EXIT                =KEY_ESC        #Taste App. Exit
KEY_POWER               =KEY_POWER2     #Taste Power
KEY_SLEEP               =KEY_POWER2
KEY_PROG1               =KEY_MENU       #Taste GO
KEY_BACK        = KEY_ESC
#KEY_ESC                        =KEY_EXIT       #Taste ESC/CLEAR
KEY_NUMERIC_0           =KEY_0          #Taste 0
KEY_NUMERIC_1           =KEY_1          #Taste 1
KEY_NUMERIC_2           =KEY_2          #Taste 2
KEY_NUMERIC_3           =KEY_3          #Taste 3
KEY_NUMERIC_4           =KEY_4          #Taste 4
KEY_NUMERIC_5           =KEY_5          #Taste 5
KEY_NUMERIC_6           =KEY_6          #Taste 6
KEY_NUMERIC_7           =KEY_7          #Taste 7
KEY_NUMERIC_8           =KEY_8          #Taste 8
KEY_NUMERIC_9           =KEY_9          #Taste 9
KEY_MEDIA               =KEY_MENU

Display More

und die rc-keymap:

Code

# table rc-rc6-mce, type:NEC RC-5 RC-6 JVC SONY LIRC other
0x800f0400 = KEY_NUMERIC_0
0x800f0401 = KEY_NUMERIC_1
0x800f0402 = KEY_NUMERIC_2
0x800f0403 = KEY_NUMERIC_3
0x800f0404 = KEY_NUMERIC_4
0x800f0405 = KEY_NUMERIC_5
0x800f0406 = KEY_NUMERIC_6
0x800f0407 = KEY_NUMERIC_7
0x800f0408 = KEY_NUMERIC_8
0x800f0409 = KEY_NUMERIC_9
0x800f040a = KEY_DELETE
0x800f040b = KEY_ENTER
0x800f040c = KEY_SLEEP
0x800f040d = KEY_MEDIA
0x800f040e = KEY_MUTE
0x800f040f = KEY_INFO
0x800f0410 = KEY_VOLUMEUP
0x800f0411 = KEY_VOLUMEDOWN
0x800f0412 = KEY_CHANNELUP
0x800f0413 = KEY_CHANNELDOWN
0x800f0414 = KEY_FASTFORWARD
0x800f0415 = KEY_REWIND
0x800f0416 = KEY_PLAY
0x800f0417 = KEY_RECORD
0x800f0418 = KEY_PAUSE
0x800f0419 = KEY_STOP
0x800f041a = KEY_NEXT
0x800f041b = KEY_PREVIOUS
0x800f041c = KEY_NUMERIC_POUND
0x800f041d = KEY_NUMERIC_STAR
0x800f041e = KEY_UP
0x800f041f = KEY_DOWN
0x800f0420 = KEY_LEFT
0x800f0421 = KEY_RIGHT
0x800f0422 = KEY_OK
0x800f0423 = KEY_EXIT
0x800f0424 = KEY_DVD
0x800f0425 = KEY_TUNER
0x800f0426 = KEY_EPG
0x800f0427 = KEY_ZOOM
0x800f0432 = KEY_MODE
0x800f0433 = KEY_PRESENTATION
0x800f0434 = KEY_EJECTCD
0x800f043a = KEY_BRIGHTNESSUP
0x800f0446 = KEY_TV
0x800f0447 = KEY_AUDIO
0x800f0448 = KEY_PVR
0x800f0449 = KEY_CAMERA
0x800f044a = KEY_VIDEO
0x800f044c = KEY_LANGUAGE
0x800f044d = KEY_TITLE
0x800f044e = KEY_PRINT
0x800f0450 = KEY_RADIO
0x800f045a = KEY_SUBTITLE
0x800f045b = KEY_RED
0x800f045c = KEY_GREEN
0x800f045d = KEY_YELLOW
0x800f045e = KEY_BLUE
0x800f0465 = KEY_POWER2
0x800f046e = KEY_PLAYPAUSE
0x800f046f = KEY_PLAYER
0x800f0480 = KEY_BRIGHTNESSDOWN
0x800f0481 = KEY_PLAYPAUSE

Display More

seahawk1986 · February 23, 2014 at 12:40 PM

Quote from TesaFilm

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?

TesaFilm · February 23, 2014 at 1:30 PM

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.

Participate now!