irrecord(1) [suse man page]
IRRECORD(1) FSF IRRECORD(1) NAME
irrecord - application for recording IR-codes for usage with LIRC SYNOPSIS
irrecord [options] file DESCRIPTION
This program will record the signals from your remote control and create a config file for lircd. A proper config file for lircd is maybe the most vital part of this package, so you should invest some time to create a working config file. Although I put a good deal of effort in this program it is often not possible to automatically recognize all features of a remote control. If the program fails to recognize the protocol of the remote control you should use the --force option to at least create a config file in raw mode. If file already exists and contains a valid config irrecord will use the protocol description found there and will only try to record the buttons. This is very useful if you want to learn a remote where config files of the same brand are already available. Of course this will only work if the remotes use the same protocol but it's worth a try. You will find template files for the most common protocols in the remotes/generic/ directory of this package. The name of the new file is created by appending .conf to the given filename in this case. -h --help display this message -v --version display version -a --analyse analyse raw_codes config files -f --force force raw mode -n --disable-namespace disables namespace checks -l --list-namespace list valid button names -H --driver=driver use given driver -d --device=device read from given device SEE ALSO
The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory. Further information on this topic is available in section "Adding new remote controls" in html/help.html irrecord $Revision: 5.100 $ May 2010 IRRECORD(1)
Check Out this Related Man Page
LIRCMD(8) FSF LIRCMD(8) NAME
lircmd - LIRC mouse daemon translates infrared signals into mouse events SYNOPSIS
lircmd [options] [config-file] DESCRIPTION
This daemon can simulate a MouseSystems, IntelliMouse or IMPS/2 type mouse. It gets the received buttons from lircd and converts them to mouse events. To make this possible, lircmd needs a config file located in /etc/lircmd.conf. In this file you have to determine which but- ton from which remote causes a mouse move or a mouse button click. You can also specify a special button which activates or deactivates the mouse mode. -h --help display this message -v --version display version -n --nodaemon don't fork to background -u --uinput generate Linux input events OPTIONS
If you provide the --nodaemon option lircmd won't fork to background. On Linux systems the --uinput option will enable automatic generation of Linux input events. lircmd will open /dev/input/uinput and inject the simulated mouse events into the Linux kernel rather than creating the /dev/lircm device. FILES
lircmd will use syslogd to output error messages. It depends on your system configuration where they will show up. DAEMONS
lircd and lircmd are daemons. You should start them in some init script depending on your system. There are some example scripts for dif- ferent distributions in the contrib directory. lircmd has to be started after lircd as it connects to the socket lircd provides. If you start lircd or lircmd from your shell prompt you will usually get back immediately to the prompt. Often people think that the pro- gram has died. But this is not an error. lircd and lircmd are daemons. Daemons always run in background. SEE ALSO
The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory. lircmd 0.8.7pre1 May 2010 LIRCMD(8)