· 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.
· Supplied drivers may identify the manufacturer or touch screen.
· Contacting the technical department of the monitor manufacturer for advice.
If using a PS/2 port you will need to identify from the suggestions above.
If using a serial port the best option is to identify from the suggestions above. Failing that, there is a data scope program on FTP folder ftp://scope:scope@ftp2.touch-base.com or available from the Utilities page of 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.
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 extracted as follows….
Linux
Graphical
viewer
Use a graphical USB Viewer available on the web
(Google ‘usb view download’), such as the one at http://www.kroah.com/linux/usb/
When run, this will show the USB devices, as shown
in the following example:
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. The manufacturer/controller id = TSC-10 DMC.
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01
Dev#= 3 Spd=1.5 MxCh= 0
D: Ver= 1.00 Cls=ff(vend.)
Sub=00 Prot=ff MxPS= 8 #Cfgs= 1
P: Vendor=0afa ProdID=03e8 Rev= 1.10
S:
Manufacturer=TSC-10 DMC
C:* #Ifs= 1 Cfg#=
1 Atr=a0 MxPwr=100mA
I:
If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.)
Sub=ff Prot=ff Driver=(none)
E: Ad=81(I) Atr=03(Int.) MxPS= 5 Ivl= 10ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02
Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc )
Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=045e ProdID=0039 Rev= 3.00
S:
Manufacturer=Microsoft
S:
Product=Microsoft 5-Button Mouse with IntelliEye(TM)
C:* #Ifs= 1
Cfg#= 1 Atr=a0 MxPwr=100mA
I:
If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02
Driver=hid
E:
Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl= 10ms
Note: On SuSE 10.1 systems
(and possibly others) the USB file system isn’t enabled by default. This should
be enabled by editing the file "/etc/fstab"
and change the line that says:
usbfs /proc/bus/usbfs noauto 00
to
usbfs /proc/bus/usbfs auto
00 and then reboot your system.
This is required to get the output of “cat /proc/bus/usb/devices”
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
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.
Mac OS X
Run the System Profiler from the Utilities folder, expand the USB entry
and locate the touch screen from the listed USB controllers, as shown:
Windows
There are many ways to identify USB devices plugged into a Windows USB compliant system (98,ME,2000,XP) and we list here a few methods we use:
Device Manager
Depending on the operating system in use the device’s entry in the Device Manager may show the required information.
The following screen shots, taken on XP, show two devices with one being handled by UPDD (shown in the Mouse section) and the other HID (shown in the USB Human Interface Devices)
The touch controller entry also shows the serial number for the device (i.e. 07G57498)
Graphical
viewer
Use a graphical USB Viewer. We have used two such viewers:
1) USB Deview from Nirsoft - http://www.nirsoft.net/utils/usb_devices_view.html
2) USB View available on the web (Google ‘usb view download’), such as the one at http://www.microsoft.com/whdc/device/stream/vidcap/UVCView.mspx
(this is the same as USB viewer)
When run, this will show the USB devices, as
shown in the following example:
In this example UPDD is loaded and handling the device. If the USB HID driver is handling the device it will show
[Portn] : USB Human Interface Device
Registry entries
Relevant
USB information is stored in the registry. With the device plugged in and using
Regedit program supplied with Windows dump registry
tree HKEY_LOCAL_M
In the above example, two Elo Touch 2500U Intellitouch controllers are plugged in to the system and are being handled by UPDD. If HID driver is supporting the device then the DeviceDesc will show “USB Human Interface Device"
USB Vendor and Product id listings
An incomplete list is held at http://www.linux-usb.org/usb.ids
Contact
For further information or technical assistance please email the technical support team at technical@touch-base.com