Known Hardware Issues


Our driver works with many touch screens, digitizers, pens and whiteboard type devices and operating systems in many system configuration and environments.

This document lists any known issues or configuration considerations.

General issues
Delta mode devices Controllers that operate in what we refer to as “delta mode” are controllers whereby touch co-ordinates are not transmitted when touch is held steady in the same position. The UPDD Console, Properties, Lift off time setting should be set to 0 to reflect this mode of operation. Delta mode devices that do not have this set will find it difficult to calibrate as the calibration algorithm expects more than 2 touch packets to accept a calibration point unless. Delta mode devices will send a pen down and pen up packet with nothing in between.
Known controllers that operate in this mode are:
Elo Touchsystems, Smartset 2216, USB
Multi-touch devices in non Windows systems.  The vast majority of modern USB touchscreens are now multi-touch and therefore require a multi-touch driver to support them. The standard Windows 7,8 and 10 HID driver supports multi-touch devices but other OS may not.  To overcome this issue in non Windows systems some touchscreen devices try to be clever and recognise when they are plugged into a non-Windows system and deliberately switch mode of operation to be that of a single touch 'mouse' like device so as to work in single touch mode.

In this case, when UPDD is installed to support the device and queries its capabilities it discovers that it is a single touch mouse and acts accordingly!  To overcome this problem we can extract the multi-touch configuration file from the device when plugged into a Windows system and embed it the driver so that it can revert the device back to working as a multi-touch device in non Windows systems.
 USB stalls We have discovered that some devices can stall when initialised and may need to be configured to bypass the initialisation process.
Hardware specific issues

These notes decribe know issues with certain touch hardware:

Baanto, Optical It is our understanding that this device can be placed in Mac mode – we are unsure exactly what mode this is (some sort of single touch mode) but our driver requires that this device is running in multi-touch mode.
The Apple Mac setting is in Baanto Dash board software.
Cocopar Y156UH7R Monitor has an OSD option for MAC. With this enabled the device runs in single touch mode. Once disabled it is important is to turn monitor power off then power cycle computer so thie single touch mode is fully cleared.  
CVTE We embed HID Report Descriptors for touch devices that outout 38 and 62 byte touch packets but there is also a 64  byte device for which we do not have the HID RD and therefore the CVTE driver does not work. Ideally we would like a HID RD extracted from a Windows system for this device but in the meantime we have modified driver with manual HID definitions that does work available on request.
DMC DUS serial When using this controller you may need the heartbeat set to keep the device alive. See RS232 settings.
rs232.macro.keepalive.ms=2000   -  set using upddutils set rs232.macro.keepalive.ms 2000.
rs232.macro.keepalive=02 4C 02 04 00 02 4C 02 81 01 - set using upddutils set rs232.macro.keepalive "02 4C 02 04 00 02 4C 02 81 01"
After setting these values you need to reload the driver or reboot the system.
We can supply software with the above settings preset if required.
eGalax old Single Touch The old eGalax single touch device (USB vendor id 0EEF, product id 0001) comes in a number of flavors, both HID and non-HID compatible. For HID compatible devices UPDD V6 will work automatically with the device. For non-HID we pre-configure the device and we have 3 configurations, one 5 byte touch data packet version and two different 6 byte data packet versions. It is important that the correct one is supplied when a non-hid device is in use.
ELO, APR 7000 series This series is not supported by our drivers - USB vendor / product id 4E7/71,73,74. We do however support the APR 7010 series 4E7/7A device.
Ilyama TF6537UHSC-B1AG We have encountered this device on two occasions under MacOS. On one occasion the device showed USB hardware errors when plugged into the Mac. On another occasion, single touch worked fine with the native HID device but as soon as UPDD was loaded and requested the device enter multi-touch mode then no touch data was sent from the device.
Currently UPDD v6 does not support this device.
PQLabs PQlabs have various touch screen products, starting at G3 and, at the time of writing - May 2018, shipping G9. Some of the early versions of the PQlabs hardware are not-HID compatible and need a custom driver to work as supplied by PQlabs. PQlabs never shared the touch data format of the non-HID devices with us so we have never been able to support them with our drivers, therefore we can only support HID compatible versions. We believe these to be G5 and above.

Unfortunately, it is our understanding that both non-hid and HID versions can share the same USB vendor and product id so it is difficult to distinguish which is which when connected to a system other than to know some work and some don’t. When a device does not work we can capture touch data to confirm if it is a non-hid compliant device.

We have further discovered that some PQLabs devices can run in both 'non-hid' and 'HID' mode. A customer wanted to use UPDD to support the device in multi-touch mode in MacOS and installed UPDD and reported touch was not working. We ran our diagnostics procedure and could see the device was registered in the Mac as USB device 1EF1/0001 and the captured data was non-HID. Rebooting the system did not change the situation. However, physically unplugging and replugging the device resulted in the device switching to HID mode, USB device 1EF1/0057 (presenting a different HID descriptor to the system), and touch worked in multi-touch mode. We are unsure why a reboot did not give the same results but physically disconnecting did as our driver would be issuing the same USB requests (to switch to MT mode) in both cases.

These are the files captured by are diagnostics program showing the switch from 0001 to 0057 USB devices:


Sharp devices The old UPDD V5 driver worked well with these devices but V6 has been intermittent. In V6 there are various device settings to control some of the USB initialisation features and these values seem to be the best combination:
disable_get_max_contacts: 1
disable_remote_wakeup: 0
disable_set_alt0: 1
disable_set_device_mode: 1
Slate Digital Raven To connect an additional touch monitor to this device you will need a custom driver from us that supports the Slate touch screen and the touch screen on your touch monitor.  The driver will then support both devices.  Thereafter in the Raven software you will need to select the ‘Dual’ mode option during Raven startup. This is in the same dialog where you select the desired DAW.
Zaagtech Some Zaagtech multi-touch devices switches to single touch mouse mode in MacOS and will not switch back. Regarding the device with USB product code C021 earlier versions of the device were fixed single touch in MacOS but a later release introduced a 'forced multi-touch' switch that allows it to work in MT. The C031 controllers also work in multi-touch mode with UPDD.
If the UPDD Test program shows single touch then you are likely to be stuck in single touch mode. If you run UPDD diagnostics and open up the resultant .zip file and look at the captured data in updd.raw.txt and it is in the format '03 01 59 12 99 38' then this will confirm its running in single touch.
Search