Man page - irsimsend(1)
Packages contains this manual
- irexec(1)
- irsimsend(1)
- lircd-uinput(8)
- lircrcd(8)
- lirc-lsremotes(1)
- lirc-make-devinput(1)
- lirc-setup(1)
- irw(1)
- irpty(1)
- lircmd(8)
- irtestcase(1)
- irsend(1)
- irrecord(1)
- irsimreceive(1)
- ircat(1)
- lircd.conf(5)
- pronto2lirc(1)
- irdb-get(1)
- lirc-config-tool(1)
- irtext2udp(1)
- lircd-setup(8)
- lircrc(5)
- lircd(8)
- lirc-lsplugins(1)
- lirc-postinstall(1)
- irpipe(1)
- mode2(1)
apt-get install lirc
Manual
irsimsend
NAMESYNOPSIS
DESCRIPTION
OPTIONS
FILES
SEE ALSO
NAME
irsimsend - Send simulated IR data.
SYNOPSIS
irsimsend [-k keysym |-l listfile ] [other options] < file >
irsimsend [ -v | -h ]
irsimsend < configfile >
DESCRIPTION
irsimsend is a simple test tool which given a lircd configuration file will send all keys defined in that file, the keys listed in another file or a symbol defined on the command line.
The program uses the file driver to log all sent data (pulses/spaces durations) into a file βsimsend.outβ. The symbols sent are printed on stdout.
OPTIONS
-c, --count < count >
Repeat each sent signal <count> times.
-U, --plugindir < path >
Load drivers from path , a β:β separated search path similar to $PATH.
-l,--listfile < path >
Send symbols listed in file instead of just the symbols in the config file. The file could either be listing a single key symbol per line, or have a complete code string like 000000000000a123 01 KEY_POWER brand on each line.
-k , --keysym
Send a single key symbol defined in file .
-s , --start-space < useconds >
Send an initial space before sending data.
-v , --version
Print version and exit.
-h , --help
Print help message.
FILES
Λ/.cache/irsimsend.log
Debug log. Setting the XDG_CACHE_HOME environment variable relocates this file to $XDG_CACHE_HOME/irsimsend.log. The amount of logging respects the LIRC_LOGLEVEL environment variable, defaulting to the debug value in the[lircd] section of lirc_options.conf.
SEE ALSO
The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory.