Occasionally we are asked to supply a driver where the identity of the touch screen is unknown. This document suggests ways of identifying an unknown controller in use. Most touch screens that we deal with are connected to monitors. However, it is unlikely the monitor manufacturer is also the manufacturer of the touch screen.

Company-specific Linux drivers. See the Technology notes for each driver on the Driver and File Downloads page to verify support for your touchscreen technology. How to get eGalax TouchScreen film (0eef:0001) working in. Ltd eGalax TouchScreen. The Linux kernel. It should be detected as USB Touch Screen of Serial Input. Linux Touch Screen HOWTO (c. Dev/ttyS1' # for a device at serial port 2 DeviceName 'TouchScreen' #could be any. Linux Touch Panel Drivers for the. TouchKit driver user guide for Linux This driver/utility package supports TouchKit controllers only. Driver “egalax”. This driver supports serial RS232.

This will almost certainly have been supplied from a third party touch screen manufacturer. It is possible that we don’t support a given touch screen and we can add support if we are supplied relevant technical information as described in our.

Here are the various ways you might be able to identify the touch screen in use: faSometimes the in use. Monitor product literature or specification may identify the manufacturer or give clues, such as 8 wire touch screen, of which there are only a few in production. Touch manufacturer’s labels may be attached to the base or back of the monitor. Install Module In Opencart.

Supplied drivers may identify the manufacturer or touch screen. Contacting the technical department of the monitor manufacturer for advice. Depending on the hardware port in use by the touch device we may be able to identify the device from information gleaned from the device: PS/2 If using a PS/2 port you will need to identify from the suggestions above. Serial If using a serial port the best option is to identify from the suggestions above. Failing that, there is a on our web site which can be used to identify the touch data packet seen at the serial port.

We can sometimes identify the controller solely based on this data, which can be saved to a log and emailed to us. USB If using a USB controller, which by definition is a Plug and Play device, there are ways of identifying the controller from the PnP information passed from the device to the system. Given this information we can identify the touch controller in use from our database of touch controller settings. The required information is the Vendor id (VID), Product id (PID) and, if available, the manufacturer’s id, which can be viewed in, and as described below. Once you have identified the Vendor and production id use the to help identify the device Alternatively there are a number of vendor and product id listings on the web, such as:.

We cannot vouch for the completeness or accuracy of these lists. Linux To view the USB vendor and product ids in Linux you can use a graphical viewer or the CAT / LSUSB commands as described below. There may be other methods.

LSUSB command If the optional USBUTILS package is installed on your system you can also obtain a list of USB devices using the LSUSB command. The USB devices are listed in the following format: Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 003 Device 002: ID 066b:2213 Linksys, Inc. WUSB12v1.1 802.11b Adapter Bus 003 Device 003: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 002 Device 001: ID 0000:0000 Bus 002 Device 002: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen Bus 001 Device 001: ID 0000:0000 In the above example, the highlighted entry is a USB touch screen controller. Cat Command Open a terminal window and type cat /proc/bus/usb/devices. This is best performed with all other USB devices unplugged as sometimes it is unclear which device is which, especially if the description string has not been implemented in the device. Typically, the output will be in the format shown below.

For clarity, the USB touch screen is shown in bold, but does not appear highlighted in the actual output. The VID = 0AFA and the PID = 03E8.