Manpage of EVIOTEST
Section: FreeVR Commands (1FV)
Updated: 19 August 2013
Return to Main Contents
- test the setup of an input device connected via the Linux
input event systems (aka evdev or EVIO).
eviotest [-list] [-nodata] [-repunk] [<event device>]
The eviotest program is used to interface with devices connected via
the Linux input event system. This system is sometimes called "evdev",
or can be referenced by the IOCTL code of "EVIO". The eviotest
program can be used to list input devices and provide their self-reported
names, or to provide a live report of the inputs.
Before rendering the input stream, eviotest will output information
specific to the input device such as the number and name of all button
inputs, absolute axis (aka valuator) inputs and all relative axis inputs.
The program is terminated by pressing the interrupt key (usually ^C).
Note that sometimes this doesn't fully work the first time, but it will
work the second time.
The -list option lists all Linux event devices of the form
"/dev/input/event<N>", where N is from [0:512].
It will only list devices that exist.
For devices that exist, but for which the current user does not have
permission to access, then this information will be reported.
All other arguments are ignored when "-list" is specified.
The -nodata option reports detailed information about the device and
The reported data includes the name of the device, the manufacturer id,
and item code as well as the name and number of all inputs.
The -repunk option will report all unknown input events.
Typically, unknown events will go unreported so as to not sully the event
output with undesired information.
However, for debugging purposes it may be of interest to know whether there
are other input events being received, and what they might be.
- [<event device>]
The <event device> argument is a filesystem path pointing to a specific
Linux input event device - for example "/dev/input/event5".
Set the path of the default input device to read when no device argument
- List all Linux input event devices:
% eviotest -list
- Report inputs from the device at "/dev/input/event5":
% eviotest /dev/input/event5
- Set the default input device to be "/dev/input/event6" and then report those events:
% setenv EVIO_DEVICE /dev/input/event6
The fact that eviotest does not always terminate when receiving the
first interrupt signal (ie. ^C) may be considered a bug. The workaround
is already coded in the program - just send a second interrupt.
It would be nice to manipulate device LEDs
It would be nice to manipulate device force feedback events
Implement a screen-rendering option
The source code for eviotest is in the "vr_input.evio.c" file,
which also handles the EVIO input interface to the FreeVR library.
Copyright 2013, Bill Sherman, All rights reserved.
- ENVIRONMENT VARIABLES
- SEE ALSO
This document was created by
using the manual pages.
Time: 05:02:19 GMT, December 13, 2013