Our driver works with many touch devices (controllers) and operating systems in many different system configuration and environments.
This document lists known issues or configuration consideration that we have observed / discovered along the way.
| Hardware |
Description |
| USB 3.0 issue |
A number of Mac customers have reported difficulties with touch devices plugged into USB 3.0 ports that do not arise when used in USB 2.0 ports / hubs. This was observed thus far on the following controllers but could be more widespread:
iNexio, HID Multi-touch, USB
|
| 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, Touch, Lift off time setting should be set to 0 to reflect this mode of operation.
Known controllers that operate in this mode are:
Elo Touchsystems, Smartset 2216, USB
3M, SC3, Serial - see below for more details. |
| WIMAXIT, M1560CT2 |
Under MacOS, touch does not work after resume from sleep.
This requires global setting power.stop_after_wake to be enabled. This can be set in UPDD Console, General tab, Advanced function. With this set the driver process is terminated after a power management "wake" event. The driver will then be restarted by the OS specific launcher allowing for a full software reset |
| Multitou.ch MultiTaction |
This device is not directly supported by the driver but can be utilized in Mac OS X via our Commander software (configured to receive co-ordinate data in from TUIO). A ‘dummy’ UPDD driver needs to be installed to allow this to work.
You have to set the incoming TUIO port to that defined by the Multitou.ch software.
We have also experimented with a modified gesture engine to interface directly with this device via the Cornerstone SDK which appeared to work well (albeit the development was not completely finished) as the TUIO interface worked equally well.
The incoming TUIO data is associated with a specific display so can only be used to control one Mac OS X desktop.
Please contact Touch-Base for further details. |
| Microchip mTouch |
Although this is a USB device it is actually a Microchip USB to UART bridge so requires the Microchip USB Serial Port Driver to create the virtual com port. |
| iNexio |
Their USB device with vendor id 1870 and product id 0001 is available as a single touch device which uses firmware 1.x and a dual touch device which uses firmware 2.x. Firmware 1.x outputs 5 bytes of touch data and 2.x outputs 100’s of bytes of data and caters for 2 stylus and unfortunately we do not know it’s format, hence it is not supported. The 2 stylus 0001 controller was soon replaced with 1870 / 010x which we do support.
To summarise:
1870/0001 – single touch – firmware 1.x – 5 bytes of data – supported
1870/0001 – dual touch – firmware 2.x – 100’s bytes of data – not supported
1870/010x – dual touch – supported
|
| OneTouch USB |
The OneTouch USB controller is actually an onboard Prolific PL2320 serial to USB adaptor so requires an appropriate driver to create a virtual serial port. For Mac OS X, OneTouch sent us file md_pl2303H_HX_X_dmg_v1.1.ob1.zip for testing which worked fine. Once this driver is installed use the OneTouch UPDD serial driver to support the device |
| ITM Touch, FTDI, “USB” |
We believe this to be a USB to Serial adaptor from FTDI and that you need their driver to create the virtual serial port and access it as a serial touch screen. To create the virtual serial port download the driver from here: http://www.ftdichip.com/FTDrivers.htm
The driver you use will need to have been configured for the 0403/6001 device. See http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_100_USB_VID-PID_Guidelines.pdf
|
| 3M, SC3, Serial |
In UPDD V6 this is set to expect the device to be running at 9600 baud rate. However, these devices can be configured to be running at 2400, 9600 or 19200. You will need to adjust the baud rate accordingly in the UPDD settings. Further, they can be set to output continious touch data or single touch point and click. If the device is only outputting single pen down/up sequence on touch it must be treated as a delta mode touch device as described above. |