<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<TITLE>LIRC - Linux Infrared Remote Control</TITLE>
<LINK REL="stylesheet" TYPE="text/css" HREF="lirc.css">
<LINK REL="shortcut icon" HREF="../images/favicon.ico">
<META NAME="description" CONTENT="LIRC - Linux Infrared Remote Control">
<META NAME="keywords" CONTENT="linux remote control, multimedia">
<META charset="UTF-8">
</HEAD>
<body>
<TABLE CLASS="menu"><TR>
<TD CLASS="menu"><IMG class="menuimg" SRC="../images/diode.gif" ALT="LIRC icon" ALIGN="LEFT"></TD>
<TD><IMG class="menuimg" SRC="../images/lirc.gif" ALT="LIRC logo" ALIGN="RIGHT"></TD>
</TR></TABLE>
<h1>irtestcase</h1>
Section: User Commands (1)<br>Updated: Last change: Oct 2015<br><a href="#index">Index</a>
<a href="index.html">Return to Main Contents</a><hr>
<a name="lbAB"> </a>
<h2>NAME</h2>
<p>
<b>irtestcas</b>e - Create or check decoding testcases.
<a name="lbAC"> </a>
</p>
<h2>SYNOPSIS</h2>
<p>
<b>irtestcase</b> [<i>-l lircrc-file -p prog</i>] <<i>socket</i>>
</p>
<p>
<b>irtestcase</b> [<i>-l lircrc-file -p prog</i>] -t <i>testdata</i> <<i>socket</i>>
</p>
<p>
<b>irtestcase</b> [<i>-v</i>|<i>-h</i>]
</p>
<p>
<a name="lbAD"> </a>
</p>
<h2>DESCRIPTION</h2>
<p>
<b>irtestcase</b> is a tool which can record keypresses from a remote together
with the decoded values. Given output from another session, it can
also verify that the decoding still works as expected.
</p>
<p>
In the first form irtestcase will wait for input and create log files
for it. Doing so, it also echoes received buttons on stdout. There is
no way to stop the program in a clean way, just use ctrl-C when completed.
</p>
<p>
In the second form it will feed the data from the testdata file to lircd
and log the the decoded data as usually. Thus, this makes it possible to
test the output from the remote which generated the testdata. In this
form lircd must be running with the "file" driver.
</p>
<p>
The optional socket is the lircd output socket (lircd must be running). It
defaults to LIRC_SOCKET_PATH in environment, falling back to a hardcoded
default value (/run/lirc/lircd).
</p>
<p>
<a name="lbAE"> </a>
</p>
<h2>OPTIONS</h2>
<p>
</p>
<dl>
<div><dt>
<b>-l, --lircrc</b> <i><lircrc config file></i>
</dt></div>
<dd>
Log also applications strings (as <a href="ircat.html">ircat</a>(1)) using lircrc type config file.
<p>
</p>
</dd>
<div><dt>
<b>-p, --prog</b> <i><program id></i>
</dt></div>
<dd>
When using -l/--lircrc, the program name matching the PROG = entries
in lircrc
<p>
</p>
</dd>
<div><dt><b>-t, --testdata</b></dt></div>
<dd>
Use data i file instead of "live" input from the remote. This can be
the durations.log file from a previous run, see FILES. It can also
be logged output from <a href="mode2.html">mode2</a>(1).
<p>
</p>
</dd>
<div><dt><b>-v , --version</b></dt></div>
<dd>
Print version and exit.
<p>
</p>
</dd>
<div><dt><b>-h , --help</b></dt></div>
<dd>
Print help message.
<p>
</p>
</dd>
</dl>
<a name="lbAF"> </a>
<h2>ENVIRONMENT</h2>
irtestcase respects LIRC_SOCKET_PATH which if defined holds the
path to the lircd output socket to listen to.
<p>
<a name="lbAG"> </a>
</p>
<h2>FILES</h2>
<dl>
<div><dt>
<b>/tmp/irtestcase</b>
</dt></div>
<dd>
irtestcase creates files in /tmp/irtestcase (hardcoded, sorry). After a
successful run here is:
<dl>
<div><dt></dt></div>
<dd>
<dl>
<div><dt>
<b>durations.log</b>
</dt></div>
<dd>
Printable space/pulse durations in the same format as <a href="mode2.html">mode2</a>(1). This file
is usable as -t/--testdata input.
</dd>
<div><dt>
<b>codes.log</b>
</dt></div>
<dd>
The decoded buttons, in same format as <a href="irw.html">irw</a>(1).
</dd>
<div><dt>
<b>app_strings.log</b>
</dt></div>
<dd>
The application strings, as presented by <a href="ircat.html">ircat</a>(1).
</dd>
</dl>
</dd>
</dl>
</dd>
<div><dt>
<b>~/.cache/irtestcase.log</b>
</dt></div>
<dd>
Debug log. Setting the XDG_CACHE_HOME environment variable relocates this
file to $XDG_CACHE_HOME/irtestcase.log. The amount of logging respects the
LIRC_LOGLEVEL environment variable, defaulting to the debug value
in the [lircd] section of lirc_options.conf.
<p>
</p>
</dd>
</dl>
<a name="lbAH"> </a>
<h2>SEE ALSO</h2>
<p>
The documentation for <b>lirc</b>
is maintained as html pages. They are located under html/ in the
documentation directory.
</p>
<p>
</p>
<hr>
<a name="index"> </a><h2>Index</h2>
<dl>
<div><dt><a href="#lbAB">NAME</a></dt></div>
<dd>
</dd>
<div><dt><a href="#lbAC">SYNOPSIS</a></dt></div>
<dd>
</dd>
<div><dt><a href="#lbAD">DESCRIPTION</a></dt></div>
<dd>
</dd>
<div><dt><a href="#lbAE">OPTIONS</a></dt></div>
<dd>
</dd>
<div><dt><a href="#lbAF">ENVIRONMENT</a></dt></div>
<dd>
</dd>
<div><dt><a href="#lbAG">FILES</a></dt></div>
<dd>
</dd>
<div><dt><a href="#lbAH">SEE ALSO</a></dt></div>
<dd>
</dd>
</dl>
<hr>
<p>
This document was created by
<a href="index.html">man2html</a>,
using the manual pages.<br>
Time: 12:55:08 GMT, February 16, 2019
</p>
<p class="footer">
[<A HREF="http://www.lirc.org/">LIRC homepage</A>]
</p>
</body>
</html>
