Protocol capture procedure Revision 1.1 – 7th Mar 2011
Windows	Mac OS X	Linux	Screens	Log file	Contact
This document describes the procedure we have built in to the calibration program to capture the touch data generated from a pointer device and store it in a log file for further analysis. The data is captured from a series of 5 screens, each displaying a different pattern to capture the data when a stylus is used the trace the pattern on the touch surface. Running the calibration program with the ‘diag’ parameter will initiate the sequence that will display five line patterns to be traced. The data generated by the touch screen is captured and saved to a log file. When using this command please consider the following requirements: The driver must be configured correctly for the device, e.g. in the case of a USB device the correct Vendor and product id must be defined in the driver such that the UPDD driver is seen by the OS PnP manager as the device driver for the device. In the case of serial the correct com port and baud rate must be selected. The device name should show in black if it has correctly connected with the USB device or opened the com port: 2. The diag function captures data being delivered from the com port or USB device. USB data is captured using interrupt transfers. Under Windows this data is captured on USB via the first ‘in’ endpoint on interface 0. Under Linux or Mac OS X the data is captured on endpoint 1, interface 0. If no data is captured then it is likely that either the device is not working, the device needs initializing before touch data is generated, the device needs to be placed into a special mode of operation or, for usb devices, the output is delivered on a different endpoint / interface or via an unsupported USB transfer mode, such as Isochronous. For USB devices whereby no data is captured there are other options available to capture the protocol data. 3. If executed on a multi touch device system only the first device is tested, or you can pass Device=n to define a UPDD device handle. 4. The log file is written to the current directory so the user must have write access 5. On windows systems ensure that you run the program as an administrator. 6. On non-windows systems ensure that you run the program from a writeable directory, e.g. “~” (home). One way to run the tbcalib command is via a command/terminal dialog as shown: Windows - Start, Run, cmd If, after running the protocol capture procedure, no file is created it is likely that the command prompt is not running as Administrator. This is particularly true in Windows 7 with UAC enabled. In this case, right click on the Command Prompt task bar entry and right click on the Command Prompt menu item and select Run as administrator. This should work in most cases: Mac OS X – Utilities/terminal Linux – Applications/accessories/terminal (location dependant on distribution) Screen sequence The sequence below shows the screens that are displayed to capture touch packet information 1 - This screen captures vertical, top to bottom data sequence 2 - This screen captures horizontal, left to right data sequence 3 - This screen captures clockwise circular motion 4 - This screen captures dual touches, left to right diagonal. On a single touch system still touch with 2 fingers and follow instructions. 5 - This screen captures dual touches, left to right diagonal with a different stylus lift off sequence. On a single touch system still touch with 2 fingers and follow instructions. Log file The log file, tbcalib.log, will record captured data. If the files is empty: It is most likely that… for serial devices you have the wrong com port, communication parameters or the controller needs initialising to enable touch data. for USB devices the touch data is not delivered on endpoint 1 or the controller need initialising to enable touch data. If you are using a USB device, see here for an alternative method of capturing the data and/or the initialisation sequence. If data has been captured there will be 5 entries headed ‘Starting point n of 5’ representing the data captured from the 5 screens: Send the log for further analysis! Contact For further information or technical assistance please email the technical support team at technical@touch-base.com.