Help > Software
[ SOLVED ] DVB-T USB Dongle Infra Red Control
Was_Just19:
I returned to this topic today for a time.
First the good news ..... I found explicit instructions on how to generate a keymap file for the remote controller.
It seemed to work fine. File looked like it might be right.
So, here are the links if anyone wants to have a 'play' :D
http://www.videoguidelinux.org/en/hardware/62-configurazione-linux-lirc-per-telecomando-dvb-t
With this video
Linux LIRC Configuration for DVB-T Remote Control
My summary is as follows ....
Assuming that the DVB-T device is installed and functioning correctly .... as root do the following ...
Run
cat /proc/bus/input/devices | grep -n10 9016 <-- the device ID from running LSUSB
to find the Handler event number .... in my case it was event6
Modify the file
/etc/sysconfig/lircd
as follows ....
Top line
DRIVER="devinput"
...
# with devfs enabled
DEVICE=/dev/input/event6 <-- use the event number received above
#DEVICE=/dev/lirc/serial
I guess this one needs editing too .....
# Hardware driver module to load
HWMOD=""
but I have not yet figured that out.
To get the allowed names of Keys on Remote
irrecord --list-namespace
To assign names to the IR and create the file lircd.conf
irrecord -H dev/input -f -d /dev/input/event6 ~/lircd.conf
Copy the new config file to the /etc and/or (?) /etc/lirc/ directory
cp ~/lircd.conf /etc/
cp /etc/lircd.conf /etc/lirc/
LIRC service start
/etc/init.d/lircd restart
*******
So I got to find the info I missed about that HWMOD entry ...... and then find out what is supposed to happen when I press some of those buttons on the R/C ;D ;D
Was_Just19:
I found that I had either used the incorrect event# or it had changed!
I redid what I had done previously, and then set up just one command in KDE - HArdware - Input Devices - Remote Controls which launched Kaffeine on the last channel used, when I press the Power button of the little remote.
I have yet to add the other keys .... in fact some seem to be dodgy so will likely not work or not do what they are supposed to do ...... but that matters little at this moment!
I got it to work! Just too pleased with myself! ;D ;D
Was_Just19:
Today's report:
I cold booted this am, and attempted to use the IR, but no good.
Tried to use irw to see if the signals were getting in to the PC and nothing showed.
On checking, the event# had changed to event6 again!
This time, instead of changing files, I unplugged the device, and then replugged it.
It then got event3 as yesterday.
Everything worked as set up yesterday.
I have unplugged and replugged a few times since, even using different USB sockets ... on board and hub .... and every time it has taken event3
So it seems to me that if this is permanently attached it will use event6 and if plugged in after booting it will take event3.
I am happy enough with plugging it in after booting to enable the IR.
regards.
--- Code: ---57:I: Bus=0003 Vendor=15a4 Product=9016 Version=0200
58-N: Name="IR-receiver inside an USB DVB receiver"
59-P: Phys=usb-0000:00:1d.7-8/ir0
60-S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-8/rc/rc3/input11
61-U: Uniq=
62-H: Handlers=kbd event3
63-B: PROP=0
64-B: EV=100013
65-B: KEY=1000000 0 0 0 0
66-B: MSC=10
--- End code ---
Was_Just19:
Well it seems that this event# ID is going to cause all sorts of problems as it is inconsistent ..... it seems to cycle through the event numbers depending on who knows what?
--- Quote ---57:I: Bus=0003 Vendor=15a4 Product=9016 Version=0200
58-N: Name="IR-receiver inside an USB DVB receiver"
59-P: Phys=usb-0000:00:1d.7-2.4.1/ir0
60-S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2.4/1-2.4.1/rc/rc8/input22
61-U: Uniq=
62-H: Handlers=kbd event5
63-B: PROP=0
64-B: EV=100013
65-B: KEY=1000000 0 0 0 0
66-B: MSC=10
--- End quote ---
I suppose there may be a means of using a variable in place of the event# within the conf file/s, having caught the correct number on plug in ........ probably not worth the hassle though .......
regards.
MBantz:
For some kernels I need to create this file:
/etc/udev/rules.d/10-local.rules
containing:
--- Code: ---KERNEL=="event*", ATTRS{name}=="IR-receiver inside an USB DVB receiver", SYMLINK+="input/dvb-ir"
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version