This section describes how to configure the program.
The default configuration file of application may be found from config/default.cfg. The configuration file is read with ConfigParser. Section names are ignored and may be overwritten.
Available parameters are:
ip port device_path max_tcp_freq require_gui client_id
/dev/input/event4) can be defined. If not, app will list devices to user and user will choose the device when launching the app.
If GUI is required, no parameter is mandatory. Necessary parameters are obtained from the device and GUI. Mandatory parameters (when running headless) are:
Other parameters will get default values, if not defined in configuration file:
Logger configuration is read by default from file config/logging.json. It includes different loggers and their settings. By default, it will log with level DEBUG to file
log/devicelog.log. Maximum size is 1MB and can be changed. 10 log files are saved and file rotation used. Size may be raised according to needs.
OptoFidelity Touch Testto DUT home (
/etc/init/to start python script when user logs in.
python start.py [-c <path_to_your_config_file>] [-l <path_to_your_logging_conf>] For example: python start.py -c config/default.cfg -l config/logging.json
--configas app configuration file.
--log_configwhich defines logging configuration file.
Chromium OS GUI app is quite similar to other OptoFidelity Touch Test applications. There are two input fields, one for ip and another for port number. These are used when DUT is connecting to Sequencer. In addition to those, the input device can be choosed from dropdown list. These devices are listed as
After the GUI has connected to the background Python-script, the “Start testing” button will be enabled. Also the default ip and port will be inserted to according fields when default values are received from Python script.
After pushing the Start testing -button, DUT will connect to the Sequencer with given address and port.
Testing screen may be exited by swiping the screen with non-measured device. This means that if the stylus is tested, touching the screen with finger will stop measurement, and other way around. Measured device (eg. stylus device) cannot emit the touch events, since the device is grabbed to Python script. Thus only other devices will work.