Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Summary of Contents for DIEBOLD NIXDORF WN UTD
- Page 1 WN UTD Universal Touch Driver Linux User Manual...
- Page 2 Universal Touch Driver Linux User Manual Edition 2.1.10, August 2017 UTD User Manual...
- Page 3 All brand and product names mentioned in this document are trademarks of their respective owners. Copyright © Wincor Nixdorf International GmbH, 2017 The reproduction, transmission or use of this document or its contents is not permitted without express authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved.
-
Page 4: Table Of Contents
Content Introduction ................... 6 Used Symbols ................. 6 Identification of the Driver Version ..........6 Identification of Touch Monitors ............ 7 Installation of the Touch Driver on WNLPOS3 and WNLPOS4 ..9 Installing RPM ................. 9 Configuring the Daemon ............... 10 Configuring the Touch-Input device and Monitor mappings... - Page 5 UTD User Manual...
-
Page 6: Introduction
Introduction The Universal Touch Driver for WNLPOS 3 and WNLPOS 4 supports the Wincor Nixdorf touch screens BA8x /irTouch, BA80 /rTouch, BA9x /pcTouch, BA9x /rTouch and the touch devices BEETLE /iPOS+ and BEETLE /iPOS+ Advanced and others (see chapter “Identification of Touch Monitors”... -
Page 7: Identification Of Touch Monitors
Identification of Touch Monitors This driver supports the following Wincor Nixdorf touch screens. They can be identified by the name, the type label or by its USB ids. The USB id can be read in the operating system. Touch screen Type label USB ids name... - Page 8 /rTouch - iPOS+ Ad- Product=7201 vanced /pcTouch Product=B100 Product=B10E Product=B10F - BA91w Vendor=0eef Product=B10C /pcTouch The Touch Monitors of the BA82 /cTouch, BA83 /cTouch and BA7x family are not supported by this version of WN UTD. UTD User Manual...
-
Page 9: Installation Of The Touch Driver On Wnlpos3 And Wnlpos4
Installation of the Touch Driver on WNLPOS3 and WNLPOS4 On WNLPOS 3: Use files from centos65-32\noarch and centos65-32\i686 On WNLPOS 4: Use files from centos7\noarch and centos7\x86_64 Installing RPM open a terminal / shell as root users delete any preinstalled wntouch packages >>... -
Page 10: Configuring The Daemon
Configuring the Daemon The directory will be filled with template files /etc/opt/wn/wntouch during installation. If it is empty, the driver will still be able to run, but using default settings (no multi-screen setup, no advanced set- tings, no calibration). The easiest way to change the initial settings is opening a terminal and running the touchscreen configuration tool as administrator >>... -
Page 11: Device Configuration File
commands. For these cases a script-hook to /etc/opt/wn/wntouch/postmapping.sh is implemented in . A sample can be found in the same directory wnmaping /etc/opt/wn/wntouch/postmapping.sh.template Device Configuration File The device file is needed to define a specific order in which the driver ad- dresses the touch controllers. -
Page 12: Options File
Options File The options file is located at /etc/opt/wn/wntouch/options It can be created by the configuration tool (see above). It contains options handed to the driver as command line parameters by the daemon start script. It may contain the following options and settings: Setting the touch mode TOUCH_MODE=(touch|release|mouse|multitouch|passthrough) The default mode is ‘touch’... -
Page 13: Edge Acceleration Settings
(e.g.: PCM_NAME=<sound device> PCM_NAME=default PCM_NAME=hw:1,0 Option b – setting per touch device Please note, that the parameters have to be numbered with _1 und _2 and not with _0 und _1. BEEP_PER_DEVICE=(1|TRUE|ON|YES) Option b1 – PC-Speaker: and/or BEEP_TYPE_1=system BEEP_TYPE_2=system and/or BEEP_DEVICE_1=<console>... -
Page 14: Device Selection Settings
EDGE_MUL=<acceleration multiplier for all edges> (e.g.: EDGE_MUL=1.5 Option 2 – settings per touch device Please note, that the parameters have to be numbered with _1 und _2 and not with _0 und _1. EDGE_PER_DEVICE=(1|TRUE|ON|YES) Set the following values (if desired) as described above: EDGE_RANGE_V_1= EDGE_RANGE_H_1= EDGE_MUL_1=... -
Page 15: Minleftclickduration Setting
The minimum delay is 0 msec. The maximum is 300 msec. MinLeftclickDuration setting In click-on-touch mode the minimum left click duration defines the time (in ms) between the faked touch and release events passed to the OS when the touch device was touched. The default setting is 10 msec. -
Page 16: Daemon Calibration
TOUCH_MODE=touch DEBUG_LEVEL=2 EDGE_RANGE_H=75 EDGE_RANGE_V=75 EDGE_MUL=1.5 BEEP_TYPE=system TOUCH_DELAY=20 MIN_LEFTCLICK_DURATION=15 MAX_LEFTCLICK_DURATION=250 Daemon Calibration After installation and configuration, touch devices should match the corre- sponding monitors. In rare cases, touch position and cursor position may be off by a few pixels. In these cases, the calibration tool can be used while the wntouch daemon is running: >>... -
Page 17: Xserver Configuration
XServer Configuration Now even though the driver daemon might be running (after a restart with the correct settings), the X11 server may not yet know about the inputs it provides. During installation, a configuration file is being added to /etc/X11/xorg.conf.d/: Section "InputClass"... -
Page 18: Touchcontroller Vs. Monitor Configuration
</device> </deviceinfo> This file is no longer needed in CentOS 7, but still kept for reference. If the wntouch packages were installed for the first time after the X-Server has already been started already, it may be necessary to restart X11 be- cause the X-Server only reads its configuration files once during start up. -
Page 19: Right-Click Emulation
If called manually with no parameters, wnmapping will map all touchde- vice - monitor combinations in /etc/opt/wn/wntouch/mappings add a “best guess” mapping for those devices not listed in the config file. It can also be used independently of the wntouch daemon in order to map the “raw”... - Page 20 # EMULATE_MENU_TIMEOUT=3000 # Jitter elimination (virtual pixels per duration) # EMULATE_MENU_THRESHOLD=1000 UTD User Manual...
-
Page 21: Restart
Restart Shutdown the X11 server, restart the wntouch daemon and restart the X11 server. This could also be done by a system reset (e.g. init 6). Quicker would be to log out the current user (end the X11 server and fall back to console) stop the wntouch daemon >>... -
Page 22: Pointers And Screens Don't Match
position of the displays. Rename or remove /etc/opt/wn/wntouch/calibration* See chapter “Configuring the Touch-Input device and Monitor map- pings” and “Daemon Calibration” for more information Pointers and screens don’t match If after restart the pointer moves out on the other screen, you probably only have to exchange or remove the files in calibrationX... - Page 23 # Let's make it the default! pcm.!default { type pulse hint { description "Default" ctl.!default { type pulse hint { description "Default" and some lines should be added to make it look like: # PulseAudio plugin configuration # $Id: pulse-default.conf,v 1.3 2008/03/09 15:50:49 lkundrak Exp $ # Let's create a virtual device "pulse"...
- Page 24 pcm.dmixer0 { type plug slave.pcm "dmix:0,0" pcm.dmixer1 { type plug slave.pcm "dmix:1,0" pcm.!default { type plug slave.pcm "dmix:1,0" hint { description "Default" Now the two devices 'dmixer0' and 'dmixer1' can be used for output to the two available sound cards (internal and USB). Please note that you might need to adapt this to your system setup and soundcards available and/or desired for output.
-
Page 25: The Touch Driver In Detail
The Touch Driver in Detail Architecture: The touch controllers are exposed as evdev devices in . By default they are recognized as mouse by the /dev/input/eventX kernel and all events are routed to a device which is /dev/input/mouseX also automatically used by the xorg server. Some newer touchscreen de- vices may not be recognized at all by the X-Server though, because of an unknown product/vendor id, these will only be functional with a version of wntouch that knows and translates their events to mouse clicks or touch... -
Page 26: Mapping Tool
evaluated and assembled into one large commandline by on system boot time. /etc/init.d/wntouch start Mapping Tool In order to allow automatic configuration changes and mappings of newly attached devices, the wnmapping tool is called by udev each time a new supported device is detected. -
Page 27: Additional Configuration Files
If the connection to the wntouch driver is disconnected before sending the save command, the original calibration is restored by the wntouch driver. The wntouch driver will store the calibration data as text file in , containing the min_x, max_x, /etc/opt/wn/wntouch/calibrationX min_y and max_y values on individual lines. -
Page 28: Driver Version History
Driver Version History 2.1.8 – Initial release of WN-UTD 2.1 2.1.9 – Added hook-script support for mapping 2.1.10 – Fixed race condition resulting in high CPU load Wincor Nixdorf International GmbH D-33094 Paderborn UTD User Manual...
Need help?
Do you have a question about the WN UTD and is the answer not in the manual?
Questions and answers