LIRC is required for these tools to work.
For kernel versions 3.0 onwards, RedRat3 support is built in so IR Tools should work without any further updates (apart from enabling the learning/wideband detector in irinput).
For kernel version of 2.6 or lower, RedRat3 LIRC support needs to be installed. Please see the RedRat LIRC page for details.
They also require the Standard Template Library (STL).
Build with the following commands:
A program for reading IR signals from a RedRat3. Typical usage is:
irinput -d /dev/lircX
where /dev/lircX corresponds to the RedRat3.
If irinput is run with no options it will try to use /dev/lirc0.
Output is similar to that of mode2, one of the LIRC test programs. Pressing Ctrl+C brings up a menu that allows the learning detector to be enabled and disabled. Enabling the learning detector disables the long range detector and vice versa. Signal modulation frequency packets are returned when the learning detector is enabled. The learning detector will be disabled after either a successful signal capture or selecting “Disable learning detector” from the menu.
A program for transmitting IR signals with a RedRat3. Typical usage is:
As with irinput, specifying the device to use is optional and /dev/lirc0 is the default.
The configuration file lists the IR signals for a device and two examples are provided in the config folder.
The IR signal database utility V3.03 onwards can export these files directly, or they can be written by hand. (irinput can’t generate these files at the moment.)
Commands are signal names (as specified in the configuration file) optionally followed by the number of repeat signals to send. By default each signal is followed by one repeat signal because this is typical of what is sent when a person operates a remote control. This can be changed using the -n switch.
Thus, if play were a valid signal name for a given device, the command play sends the play signal once and, by default, the repeat signal once. The command play 2 will send the main play signal once and the repeat play signal twice, overriding the default repeat count, assuming that 2 is not a valid signal name. If it is, 2 is interpreted as a signal and not as a repeat count.
To avoid ambiguity with repeat counts, the -r switch can be used. For example, the above could be rewritten as play -r 2 to send the play signal with two repeats.