This board features a new protocol for conveying IR information to the host. Rather than just sending the demodulated IR data this board decodes the key code in firmware so the host does not have to.
This has the advantage that LIRC doesn't need to decode IR pulse/space data but has the disadvantage that some 3rd party remote controls may not work.
For those of you that have this board I've uploaded a new experimental version of the driver (lirc_imon.c) and a template lircd config file (imon).
After compiling and loading lirc_dev and lirc_imon, use irrecord to generate a config file for your remote as follows.
- Code: Select all
irrecord -d /dev/lirc0 imon
If successful irrecord will generate an imon.conf file for use with lircd.
If you have the joystick remote note that the joystick has 16 positions each with its own code so you need to record each of them. You can use names like N, E, W, S, NE, NNE, ENE, ... to refer to the 16 positions.
Venky
P.S. If this works for you please send me a copy of your imon.conf file.
Update:
I've slightly modified the config file submitted by Lito (Thank you Lito!). You may use this imon.conf file if you don't want to record it yourself using irrecord.
I would like to thank Silverstonetek Co. for sending me an iMON PAD and IR/VFD unit for testing the new driver. I've tested the experimental driver and the lircd config file and everything looks good. The joystick requires additional work and is unsupported at this time. It is not a 16-position stick as I had initially assumed but more like a mouse.