Copyright: Copyright « ...


Contents
Touch Panel Device Driver

Version 1.0D and above - 2002. Copyright © Gunze Limited 2001,02. All rights reserved

Welcome to the Touch Panel Device Driver (TPDD).

Please select the topic of interest

 License Agreement

 Overview

 Installing or Uninstalling

 Disabling or Unloading the driver

 Driver Control Utility

 Calibration

 Event Selector

 System Tray Utilities

 Troubleshooting

 Maintenance and Support

 Glossary


License Agreement

This Touch Panel Device Driver, TPDD, is copyright (c) 2004 by Gunze Limited.

Gunze Limited shall permit the non-transferable nonexclusive right for using the software program and printed matter (henceforth "consent software").  Gunze will offer to use the software and printed matter based on the following provisions with this contract, and a customer shall agree with the following provision of the contract. Gunze Ltd. owns the complete copyrights for this software.

1. Contract Period

This contract goes into effect from the day when the packing of consent software is opened, and this contract is valid and effective till a customer makes it end by serving the written notice for less than one month or our company makes it end based on the following. Terms:

.	When a customer terminates the royalty based on this contract by issuing the notice of a document within one month always.

.	When it infringes on the copyright of Gunze Ltd. and other rights when a customer breaks one provision of these contracts or, our company can terminate this royalty or can terminate this contract.

2. Royalty

A customer can use the consent software within the limits of this contract only. A customer is allowed to use this software on one system (henceforth a "specification system") as per the agreement of this consent contract. When using consent software by more than one system, it is required to collect royalty separately. A customer can transfer the components of this software to which the royalty by this contract is applied, or others, can permit a re-royalty for a third person, or cannot transfer. Moreover, it is not permitted to carry out analysis or alteration of any components of the software or reverse engineer or compile, etc. The duplication of this consent software and printed matter in part or whole or in any other form is strictly prohibited.

3. Duplication of Consent software

The customer is not allowed to copy or duplicate any part or whole of the printed matter offered from our company based on this contract. If customer needs additional copy of the printed matter, should request our company for the same. As for the consent software offered from our company, the customer can take backup a whole or a part this software, only for this backup purpose. Gunze reserves all the rights to retain original and duplication of consent software including occupancy-right of copyrights and others. However, it is not this limitation about the medium itself on which consent software is recorded. A customer is given copyright to the duplication of the consent software. It agrees with giving a copyright indication of (c) Gunze, Ltd.

4. Duty after End

The customer will get intimation from our company within one month from the day of the closure of royalty based on this contract. The customer shall return the original and its duplicate copies of the consent software to our company created in relation to this royalty, or shall destroy this software and then send intimation to our company that this software is destroyed.

5. Exemption from responsibility

Our company does not offer any guarantees against accidents by using this consent software. Moreover, our company does not take responsibility about any damage produced directly or indirectly about the use of this software.

6. Re-Consent

No sub license (re-consent) of the consent software by the customer shall be accepted.

7. General Provision

Even when this contract is interpreted according to the law of Japan and one provision of this contract or its part becomes invalid with the law of Japan, this contract is effective and a part of the contract that invalid should be deleted from the contract.


Driver Overview
Overview

The Touch Panel Device Driver (TPDD) is a conceptually new pointing device driver that has been developed to meet the demands of the new generation of Windows operating systems.

TPDD  supports USB and serial interfaces of the Touch Panel Device.

The one common element for all Touch Panel Devices are that the device delivers a packet of information to the system that is used to control the system pointer. The structure of the packet of information is referred to as the protocol. The device will typically connect to the host computer via the serial port or USB (Universal Serial Bus) port.

This driver interprets the protocol information and moves the system pointer accordingly, emulating system pointer clicks when appropriate. Separate drivers are developed for serial interface and USB interface. For more information on drivers, see TPDD Functionality Overview.


Installing or Uninstalling

If you are reading these notes you have already installed the software and hopefully the installation was successful. If not or you need advice on the other subjects, read on....

Select the topic you want to read about

 Install preparation

 Testing the installation

 What did the install do to the system?

 Uninstalling the driver

 Automatic installation feature

See also:

  Language Support


Installing - Preparation
Installing or Uninstalling

Install Preparation

General

Please close all applications before starting. Ensure that any previous drivers or test drivers installed to support the Touch Panel are removed. It is important that USB devices are recognized as new hardware by the plug and play manager. If they are not then another driver has claimed responsibility for the device.

Serial Touch panel devices

The TPDD can be installed without the device connected but cannot be tested until the device is connected. The TPDD supports the default COM ports and also multi ports from a PCI based serial card.

USB Touch panel device

It is preferable for the TPDD to be installed prior to connecting the device. The plug and play manager will recognize the USB device, extract its vendor id and then look for the TPDD.

See also:

 Hardware Ports


Hardware Ports

There are two main hardware ports used to connect a Touch Panel device to a PC. These are:

Serial

The serial terminal of the touch panel device and computer serial port are connected with the serial cable

USB

USB is the abbreviation for, Universal Serial Bus. USB terminal of touch panel device and the computer USB port is connected with USB cable. It is possible to connect USB hub.


Unloading and reloading the driver
Disabling or Unloading the driver

Unloading and reloading the driver

   Rebooting the system is the simplest way to unload and reload the same driver.

      UFD:  From the CONTROL PANEL of Windows [Administrative Tool] ->[Computer management] ->[Device Manager] [mice and other pointing devices"] sequence is selected, right click on  'Gunze USB Touch Panel’ and select Disable / Enable. When [Enable] is made [Disable] then TPDD gets unloaded. When [Disable] is made [Enable] then TPDD gets reloaded.

In Gunze, AHL, Serial nothing is registered in device manager


Installing - Testing the installation
Installing or Uninstalling

Testing the installation

Following the installation of the TPDD and with the Touch Panel device connected, touching the device after you restart Windows should result in some movement of the system pointer. This confirms the installation of the TPDD. However, the device needs to be configured using the Driver Configuration Utility (DCU) for correct movement of the system pointer.

If the system pointer does not move at all, the TPDD is not communicating with the device correctly. For more information refer to the Troubleshooting Section.


Installing - What got installed
Installing or Uninstalling

What did the install do to the system?

The following system changes were made and will be reversed if the TPDD is uninstalled.

TPDD software installed

The TPDD software is stored in \system32\drivers folder.

Module	Description
UFD.SYS	Pointer port driver for USB ports on Windows 2K and XP
SFD.SYS	Pointer port driver for serial ports on Windows 2K and XP
Windows information files

These files are stored in the Windows information folder (/INF).

UFD.INF	Windows XP and 2k installation file for USB interface
SFD.INF	Windows XP and 2k installation file for serial interface

Utility software installed

This software will be stored in the following folder defined by the user during installation, default  \Program Files\Gunze\Gunze TPDD.

Module	Description
EventSelector.exe	Event Selector
TouchPanelCalibration.exe	Calibration Utility
DCUCPL.exe	Driver Control Utility
TPDDHelp.hlp	TPDD general help file

Program menu

A program menu 'Gunze TPDD’ will contain entries for the TPDD utilities and the general help file.

Registry updates

The following items are added in the registry. Use the system registry utility to view the actual keyword entries used.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Gunze

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ UFD\Parameters

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SFD\Parameters


Uninstalling the driver
Installing or Uninstalling

Uninstalling the driver

To uninstall the driver:

1 	Go to Start->Program Files->Gunze TPDD

2 	Select Uninstall

This process will delete all driver files, removes ‘Gunze TPDD’menu from start->program files menu and delete the Registry entries.


Installing - Automatic installation
Installation or Uninstalling

Automatic installation feature

You may wish to set up some different TPDD settings to the defaults or fully automate the setup procedure. To cater for this requirement, we offer an automatic installation procedure.

Once the TPDD is installed and setup as required, the TPDD configuration information can be stored in a data file that is then used for subsequent installations. The configuration file is created by selecting the Clone option on the DCU General dialog.

When the setup program is run it looks for the cloned configuration file in the local folder and if found skips the user setup dialog and uses the configuration data in the file.


Language localization

The installation procedure checks the Windows localized settings to determine the language version to be installed. If the language is not supported the English/US version is installed.

Languages supported are English and Japanese.


Disabling or Unloading the driver

It may be required to disable or unload the TPDD to free the system resources used by the driver, especially the communication ports, which can be used by only one driver or application at a time, and which are temporarily needed for other purposes. This can be achieved in two ways as described below.

Select the topic you want to read about

 Disabling TPDD

 Unloading and reloading the driver


Disabling the driver
Disabling or Unloading the driver

Disabling TPDD

If you need to temporarily prevent the TPDD from loading, you can do so using two methods. The Disabling method leaves the TPDD loaded but frees up the hardware port(s), typically the main reason for wanting to disable the TPDD. The Driver can be enabled again without the necessity of rebooting the computer.

1 	In the DCU Devices dialog select the controller to be disabled.

2 	In the DCU Advanced dialog uncheck the Enabled option.

3 	Select OK or Apply.

To re-enable the device later, use the same procedure to check the 'Enabled' checkbox.


Driver Control Utility

The Driver Control Utility (DCU) carries the settings for each of the configured devices and also communicates the new settings to the drivers as and when they are updated. . It can be invoked from the Touch Panel device Task bar utility or the Windows Control Panel.

The following dialog shows all available options.

The Driver Control Utility presents a number of specific control dialogs and general controls functions.

General Control Functions

These functions perform the following tasks:

Calibrate: Invokes the manual calibration program.

OK: Saves any changes and exits the DCU.

Cancel: Exits the DCU without saving any changes since the last Apply request.

Apply saves the changed settings and reflects it in the TPDD .

Help: Displays the help topic for the dialog on view.

TPDD Setting Screens

Each tabbed dialog handles a specific task as listed below. Select the topic for more information.

 About – TPDD version  and Gunze detailed information

 Advanced – Advanced setting of  TPDD

 Calibration – Settings related to calibration

 Devices – Serial and USB (Touch panel) device   Additions(Registration) / Updation / Deletion.

 Events – Button mode settings

 General - General settings

 Hardware – Setting of each type related to the serial communication  for Serial (Touch panel) device

 Settings – Setting related to the processing  of data from the touch panel device  and each of the button mode operations.

 Status - display communication status of serial (touch panel) device.

 Windows – Setting of double click condition


Driver Control Utility - About Box
Driver Control Utility

About Box

The About box displays the TPDD and DCU version number. TPDD support and license terms are mentioned here.


Driver Control Utility - Advanced settings
Driver Control Utility

Advanced settings

The advance screen contains the settings for touch panel device data processing, the sound for click event and TPDD enable/ disable

Selecting the 'Defaults' option will restore the settings to their default value.

Sample rate

The sample rate determines the percentage of packets that are processed and passed on to the mouse class driver. For example, 100% means pass all packets, 10% means pass one in 10.

The sampling algorithm applies the sample size intelligently to the packet stream.

For example, at 80%, 4 packets are accepted and 1 discarded.

At 50% every other packet is discarded. This technique gives a smoother response at lower sample rates.

Sample rate should generally be set to 100%. A lower value can be used if Windows, or other applications, show unacceptably degraded performance while the pointer data is processed. This is rare with modern hardware, but could occur on a heavily loaded machine with pointer intensive workload.

If a value less than 100% is used, then it should be the highest possible value conducive with correct operation.

Note that this setting sets the maximum number of position reports posted. It cannot increase the raw speed of your device.

Touchdown filter

This setting specifies a number of coordinate reports (packets) from the device to ignore before sensing a touchdown.  The default value is zero. For e.g. If the Set value is 10, the TPDD shall ignore the first 10 coordinate reports and shall process from the 11th coordinate report. This can be useful in touchdown mode, where the touchdown position is the position of the button click.  If the Touch Panel Device takes a few coordinate packets to stabilize on the correct position, this setting can be used to ignore the first few inaccurate packets.

Deglitch

This setting can be used to filter out glitches (spikes) on the pointing device and is only needed when glitches are experienced with the system pointer.  Packet co-ordinates are checked against the previous co-ordinates received and if the difference between the point and the previous point exceeds the deglitch percentage the packet is discarded.

Default value of deglitch is 0%.

For example, If a controller reports co-ordinates in the range 0 - 4095 and a setting of 10% is used, If the difference between the present co-ordinates and previous co-ordinates is greater than or equal to 409 then present packet will be discarded.

If deglitch is 100%, in an ideal case all the packets from the controller are accepted.

Enabled

The TPDD can be enabled or disabled you can disable the U-TP by un-checking the Enable check box. In this case, the U-TP shall not work even if the touch panel is touched (The mouse pointer of windows shall not work). You can enable the U-TP by checking the Enable box again. For e.g.  this can be useful if two different controllers are configured on the same hardware port and you want to switch between the two without constantly configuring the controllers. One can be shown as disabled the other as enabled and this will avoid any driver conflict.

Sound

On/off of click sound to sound when it touched a touch panel and for a click event to occur is controlled.

No Sound.

 Doesn't ring when this check list is chosen.

Wave Sound

When this check list is chosen, the Wave file specified by the touch movement by the "Wave file choice" is reproduced.

BEEP Sound

When this check list is chosen, BEEP sound rings by the touch movement.

    But, BEEP sound may not ring when sound function is mounted.

Select Wavefile

This option is used to select user defined audio file (. wav). The required Wave file can be selected from the system and for each touch of the screen, the specified wave file is played.


Driver Control Utility - Calibration
Driver Control Utility

Calibration

This dialog is used to define the calibration for each touch panel device registered in the TPDD.

�¥Calibration Screen for 9 Points

Calibration settings for

This displays and allows the selection of the device against which calibration settings are to be made.

Calibration points

This option specifies the number of calibration points.

It can be chosen from 4, 9, 25 points at the time of the "4/8 wire touch panel" choice.

It can be chosen from 9, 25 points at the time of the "5 wire touch panel", the "One Sheet Panel" choice.

Time out

This option indicates the calibration time-out value if the calibration point is not touched within the specified period and is defined in seconds.

Touch Point

This option sets the position of the outermost calibration points. The unit is %. This option is set between 1 and 5. The default value is 1. This means that the outermost calibration points is put on 1% inside of the full scales of the indication screen from the end of the indication screen.

Note:Touch Pointo becomes effective only when "Caribration points" is 9,25.

Calibration pattern

This setting graphically depicts the calibration point pattern to be used.


Driver Control Utility - Devices
Driver Control Utility

Devices

This dialog shows the configured devices.

The list of installed Touch panel devices, if any, are displayed. Each device entry displays the device number (#) automatically allocated when the device is added, the device name, and the desktop segment associated to the device and the Touch panel device type.

Select a device from the list of devices on the Device page. The selected device will now become the 'current' device and changes in any of the DCU settings will  apply for this device only.

To select a device click anywhere on the device line.
From this dialog you can Add, Modify or Remove serial/USB touch panel device.

Note: Select either "Gunze, AHL, Serial" or "Gunze, USB". Don't select more than two.

Add: By the add function you can add  serial and USB (Touch panel) devices. This function will offer a list of available touch panel device types to select from. A name is then requested for the newly added touch panel device along with the desktop segment.

Modify: The modify function allows previous assigned names and desktop segment associations to be changed.

Remove: The Remove function will remove the selected Touch panel device from the list. A confirmation is requested prior to removal.

See also

 Hardware Ports

 Windows coordinate system


Windows desktop coordinate system
Touch Panel Devices and the Desktop

Windows Coordinate System

Overview

Although, as users, we relate to the video resolution in pixels, such as 640x480(VGA), 800x600(SVGA)  or 1024x768(XGA), Windows has another view of the desktop based on the absolute coordinate resolution of 0 to 65535 in both X and Y axis.

When the TPDD receives a coordinate packet and instructs the system pointer to move to the appropriate location, it is the absolute coordinate system that is used. Different device protocols may be passing different X and Y coordinate ranges and the TPDD has to scale these up to the absolute Windows coordinate system and then calculate the new system pointer position. The TPDD also has to cater for device coordinates being either relative or absolute before calculating the new pointer position.


Driver Control Utility - Events
Driver Control Utility

Events

This screen shows both the events that can be generated by a controller and the actions associated with the event. When the event occurs on the controller either the Primary or Secondary action will be performed depending on the Event State setting.

If the mouse pointer of event selector or mouse pointer of the TPDD of the taskbar is left button state then the operation (button mode) when touch panel is touched it shall be set to primary, and in case of Right button state the operation (button mode) set to Secondary.

To change the button mode, select a different button mode from the dropdown list of Primary or Secondary.

Following are the available actions:

Touchdown Left

The system pointer is moved to the point of the touch, and then the left button is immediately pressed.  You can then slide around with the button held down.  The button is released when the stylus or finger is removed from the device.  Touching twice in quick succession in approximately the same place can generate double clicks.

Touchdown Right

The system pointer is moved to the point of the touch, and then the right button is immediately pressed.  You can then slide around with the button held down.  The button is released when the stylus or finger is removed from the device.  Touching twice in quick succession in approximately the same place can generate double clicks.

Touchdown Immediate Left

Mouse pointer moves to the touched place and a left button click is carried out. After this, even if finger or pen is not removed, it cancels the click status immediately. If finger or pen is made to slide in this status, the mouse pointer follows but it does not drag. Double click is performed by touching the same place twice quickly.

Time Left

The system pointer is moved to the point of the touch, but no button is pressed.  You can then slide around with the button not pressed.  Any time the finger or stylus is held stationary for a period of time, the left button is pressed, and a beep sounds.  You can set the Stationary time by the click time in setting screen. Once pressed, you can slide around with the button pressed, and the button is only released when the finger or stylus is removed from the device.  Double clicks are not possible in this mode.

Time/Tap Left

This is similar to Time mode, but double clicks are possible. After holding stationary to generate the first left button press, lifting the stylus off the screen and then immediately touching again will generate another button press.

Tap Left

The system pointer is moved to the point of the touch, but the button is not pressed.  You cannot slide around with the button held down. Quickly lifting the finger or stylus off the screen and then touching it again within a short time generates Button presses (left).  Double clicks are achieved by doing this twice in quick succession.

Time/Time Left

This mode is similar to time mode, but a left button double click is generated by holding the finger or stylus stationary for a further time period.

Liftoff Left

The system pointer is moved to the point of the touch, but the button is not pressed.  When the finger or stylus is removed from the device, the left button is pressed and then immediately released again.  Double clicks can be achieved by quickly touching the device and lifting off again.

Touchdown Double Click Left

A left button double click is generated when the device is touched.

Touchdown Double Click Right

A right button double click is generated when the device is touched.

Liftoff Double Click Left

When you touch the touch panel, the mouse pointer moves to the touched point but it does not generate click and double click. Lifting the finger or stylus off the device generates a left button double click.

Time Double Click Left

A left button double click is generated when the finger or stylus is held stationary for a period of time. You can set the stationary time by click time in the setting screen.

Tap Double Click Left

When you touch the touch panel, the mouse pointer moves to the touched point but it does not generate click and double click. A left button double click is generated when the finger or stylus is lifted from the device and quickly placed back down.

Quick Event Button Mode Association

The default primary event can be quickly changed using ‘Gunze TPDD settings’ Task bar icon’s  ‘Button Modes ‘ menu during device operation to allow the user to instantly switch between button modes of operation.


Driver Control Utility - General
Driver Control Utility

General

In General screen, the following functions can be carried out. Settings like  whether to display TPDD icon in Task bar  Whether to enable the calibration data after executing the calibration whether to sound the beep at the time of calibration  copy of the settings (clone)   dump function.

Copy of Settings (Clone):

This option copies the current configuration setting to file UFDClone.dat/SFDClone.dat to be used for automatic setup in subsequent installations. While installing TPDD in a different computer, if it finds UFDClone.dat/SFDClone.dat file in a optional folder, then TPDD gets installed by the settings saved in UFDClone.dat/SFDClone.dat.

Check after calibration

This option is used to show or hide the confirmation dialog after the user feeds coordinates data to the calibration utility.

Beep sound at calibration

At the time of calibration, it enables system beep when the calibration point is touched. It sounds a beep when the check box is checked and does not sound a beep when the check box is unchecked.

Show icons in Task bar:

It sets whether to show/hide TPDD and Event selector icons in the task bar. The icon appears if te check box is checked and disappears if the check box is unchecked.


Driver Control Utility - Hardware
Driver Control Utility

Hardware configuration

In Hardware screen, the connection settings for touch panel device are set.

 Sensitive

 Serial connected touch panel device

 USB connected touch panel device


Driver Control Utility - Hardware - Sensitive
Sensitive

Sensitive

Sensitive adjusts the touch sensitivity for the capacitive touch panel.

When a sensitivity level exceeds the range that it can answer.

The mouse becomes necessary for Re-establishment .

Preparation for the mouse is recommended when  sensitivity is done.

Note:This button is indicated only at the time of One Sheet Touch Panel choice.

Sensitive:

The touch sensitivity is made sensitive.

Dull:

The touch sensitivity is made insensitive.

Display Sensitivity:

The current status of the touch sensitivity is indicated by the level meter.

Auto Adjust:

The touch sensitivity is adjusted to the suitable value.

  1) Click [Auto Adjust] button.

  2) "Touch here" is indicated between [Sensitive] button and [Dull] button. Touch one position on the  touch panel. If you do not touch one position for 5 seconds, Auto Adjust program is canceled automatically.

  3) "Touch here" disappears in a few seconds. Release your finger from the touch panel.

  Wait for 5 seconds without the touching if you want to cancel Auto Adjust program.

Sensitive Data  Read,Write

Touch Panel Device holds various establishment in Controller.

Establishment in shipping can be read.

It can be written as the data to ship present establishment.

Note:This button is indicated only at the time of One Sheet Touch Panel choice.

Read

Establishment in industry shipping is read and adapted from Controller.

Write

The establishment value of present Tach Panel Device is written in Controller as an establishment in industry shipping.

The message of "Finsished" is indicated when calligraphy gets crowded and a check is done at the same time and it succeeds.

Note�FWhen Touch Panel Device  is used by Sirial connection.

Don't touch it before the message of "Finished" or an error is indicated.


Driver Control Utility - Hardware - Serial
Driver Control Utility

Serial connected Touch panel device

Advanced: For any given port setting the Advance option can be used to change the communication parameters of serial communication.

FIFO: The FIFO setting enables the buffered mode of operation for UART serial devices. This allows the UART to use an internal cache to avoid overrun errors (where the read buffer is overwritten by incoming data before the buffer data has been read) and optionally to use a single interrupt to trigger the processing of several data bytes. The values are,

0 - no FIFO processing1/4/8/14 - uses the FIFO buffer on the UART and generates an interrupt after 1/4/8/14 bytes are received. If data stops being received the UART chip will raise an interrupt for the remaining bytes to be processed. For the hardware that supports FIFO default value for FIFO is 8. Zero may be used for specialized hardware that does not have a FIFO capability. The larger value of 14 may be appropriate with slower hardware.

Port, Baud rate, Data bits, stop bits, FIFO and Advanced options are valid only for the TPDD of serial touch panel devices. All these are not valid for the TPDD of USB touch panel devices.

Sensitive  and Sensitive Data Read & Write can be carried out.


Driver Control Utility - Hardware - USB
Driver Control Utility

USB connected Touch panel device

There is no “Advanced”  in the case of USB.

Sensitive  and Sensitive Data Read & Write can be carried out.


Driver Control Utility - Settings
Driver Control Utility

Settings

The Settings dialog contains the most commonly used protocol and TPDD settings. The default settings will be defined for optimum controller performance but can be changed if required.

Selecting the 'Defaults' option will restore the settings to there default value.

Click Time

Click time is "a short time" interval that the TPDD uses in the Time button mode or Time/Tap button mode, Time/Time button mode. It is defined in units of 55ms, and the default value is 9, corresponding to about half a second.

Click time has two functions:

1 	A Time touch event that relies on a period of time to pass prior to performing a button click, such as the Time button mode, uses the value of Click Time as the period of time. So, for example, in Time button mode, Click time controls the length of time the finger or stylus needs to be held stationary to generate a button press.

2 	Click time is also the length of time used by the button emulation logic to distinguish between first, second, and subsequent clicks.  For example, after the first click has been generated in Time/Tap mode, the TPDD is expecting a tap event to generate a second click, but only if it occurs within Click time.  After Click time, a tap will be ignored since the TPDD will then be expecting a first press again, and will only respond to a time event.  Similarly, after a second click and within Click time, the TPDD will be expecting the event defined for a subsequent button press, if any. After Click time, it will again start looking for the event defined for a first button press.

3	If a second touch occurs within click time of the first touch, current averaging data is used to ensure that any touchdown movement on the second touch is minimized, to assist Windows double click processing.

Tap time

Tap time is "a short time" interval that the TPDD uses in the Tap button mode or Time/Tap button mode and uses  the same 55ms units as the Click Time option. The default value is 9, corresponding to about half a second.

Tap touch event is defined as a finger or stylus lift and re-touch within Tap time.  So, for example, in button mode Tap, Tap time defines the length of time within which you must re-touch the screen after lifting off in order to generate a button press.

Lift off time

The Liftoff Time value specifies the time interval required to register a finger or stylus lift. When the position data from touch panel device is stopped, the TPDD does not determine if the finger or stylus is removed from the touch panel but, after the passing of the time set by liftoff time, it determines that the finger or stylus is removed from the touch panel. It uses the same 20ms units as the Click Time option and the default value is 5.

For e.g if the set value is 25 (approx. 0.5 sec), the finger or stylus is lifted off from the touch panel and this state continues for more than 0.5 sec, then the TPDD shall recognize it is a “liftoff”. If the touch panel is re-touched within 0.5 sec, then the “liftoff” will be ignored and the TPDD will determine it as “Continuous press”.

Stabilization

Stabilization is a function to ignore the data if the change of the touch position data sent from Touch panel device is smaller than the value set by stabilization. The default value is 0.

For e.g. If the stabilization is set to 20 and the change in touch position data is less than 20, then the TPDD shall ignore that data and shall not process it.

Averaging

 Averaging is a function to average the value of touch position data sent from touch panel device.

The default value is 0.

Irrespective of keeping the finger or stylus stationary, when touch panel is touched and when the mouse pointer of windows moves a little (jitters) then it can be stabilized by enlarging the value of averaging.

Moreover, if you enlarge the set value, the following movement of mouse pointer when the finger or stylus is dragged might be affected.


Driver Control Utility - Status
Driver Control Utility

Status

In status screen, you can check the communication status of TPDD touch panel devices.

Each status entry shows the device name, communications errors and synchronization errors in order as described below.

Device:

This is the device name allocated by the user at the time it was added in the TPDD.

Communication errors

This shows a count of number of times communication error as occurred.

In the case of "Gunze, AHL, Serial", this shows how many errors are occurred viz.: parity error, framing error and data loss. Zero indicates no occurrence of errors in the communication.

In the case of "Gunze USB", data loss is shown as communication error.

Synchronization errors:

The number of times an unrecognized packet is received. This is valid only for serial port

Re-initialize

The Communication errors and the Synchronization errors will be reset to zero.


Driver Control Utility - Windows settings
Driver Control Utility

Windows settings

In windows screen, the double click condition of TPDD is set.

Time (Double Click Speed)

This setting changes the time period within which Windows will register two clicks as a double click.  For Touch Panel type devices, this normally needs to be set towards the high end of the scale. DoubleClickSpeed is specified in milliseconds.

Height (Double Click Height)

This is a Windows configuration parameter and specifies the number of pixels, vertically, within which Windows will recognize two clicks as a double click.  After the 1st click, if there is a 2nd click within the range and within the time set for double click, then a double click is generated.

Width (Double Click Width)

This is a Windows configuration parameter and specifies the number of pixels, horizontally, within which Windows will recognize two clicks as a double click.  After the 1st click, if there is a 2nd click within the range and within the time set for double click, then a double click is generated.

To achieve a double click using a touch device requires a number of factors to come together to produce the conditions such that Windows will produce a double click.

1 	The Windows double click settings must be such that a double click can be performed within the time and area thresholds.

2 	We have found that any movement at touchdown of the second click causes the double click settings to be ignored and treated as a drag. To overcome this problem we utilize two parameters to facilitate a more reliable double click, known as Double click time and Double click area.  The idea is that a user may make a rapid double touch within a given time and location which the TPDD will detect as being a double click request. If such a request is seen we use the current averaging data to ensure that any touchdown movement on the second touch is minimized.

Mouse Click Test

This area is used to test single and double click responses.


Calibration

Calibration Overview

Touch Panel devices require a calibration process to be performed to align the X and Y coordinates generated by the device with the position of the system pointer cursor. This is particularly true of devices that operate in an absolute mode and need to be aligned with the desktop graphics, such as a fitted Touch Panel, instead of a relative mode, such as a mouse.

Select the calibration issue you want to read about

 Manual Calibration Program


Calibration - Manual
Calibration

Manual Calibration Program

You can manually execute calibration program by the [Calibrate] button on DCU or Calibrate menu from task bar utility. When you start the Calibration program, a  mark shall appear on the screen. When you touch the middle of the  mark, it displays the next calibration point and similarly touch that  mark also.  The number of calibration points is fixed at 4 or 9, as set in the DCU Calibration dialog. If you require high precision, we recommend that you select 25 points.

The calibration procedure usually needs to be performed only once and needs to be repeated if the touch position on touch panel does not match with the mouse pointer of windows or if the alignment of the device with the visual image changes.

Calibration can be invoked from the Driver Control Utility  and the Device Manager Task bar Utility.

With the device working and correctly calibrated the system pointer should follow the coordinate movement generated by the pointing device.


Event Selector

Overview

Event Selector:

An event is an occurrence on the Touch Panel device that can be associated with a mouse click action (button mode).  The default event is implicitly associated with first (touch) and last (lift off) protocol packets. Each event can have two states known as the 'Primary' and 'Secondary'. The setting of the Event Selector indicates the current Event State such that the appropriate button mode action is performed when the controller event occurs. Clicking on the Event Selector toggles between the primary and secondary Event State. This should emulate mouse left and right clicks setting as in the control panels.

See also

 System Tray Utilities


System Tray Utilities

System Tray Utilities

A number of system tray applications can be utilized to invoke the main driver procedures. See the Troubleshooting Section, Missing System Tray Icons if the icons are not present in the system tray.

 Event Selector icon

This icon reflects the current setting of the Event Selector and can also be used to change between the primary and secondary event. On most systems the primary event is set to generate a single left mouse click and the secondary event to generate a single right mouse click, thus this icon is used to switch between left and right clicks

 Gunze TPDD Settings icon

A Right click will list the menu items as described below. Double clicking on this icon will load the Driver Control Utility.

Enabled - Indicates if the device is enabled. This entry expands to show all the configured devices. A tick�i�jindicates that the device is enabled, otherwise it is disabled.

Calibrate - Invokes the calibration procedure. If more than one device is configured a list of device names will be offered to select the target device.

Adjust settings - Invokes the Driver Control Utility

Event Selector - Invokes the Event Selector

Help - Invokes the TPDD help system

About – Displays the TPDD general information

Close - Removes the system tray icons


Device configuration

The DCU Devices dialog lists the configured devices and shows the relationship between the Touch Panel Device and the desktop.  In other words, what part of the Windows desktop is to be controlled by the specific device?  The section Touch Panel Devices and the Desktop describes the various types of relationships that can be established.

This section shows how to set up those relationships within the TPDD.

Single monitor

This will typically be a Touch Panel fitted to a single monitor.

If the Touch Panel is to control the entire desktop, the relationship established when the controller is added, will be defined as the whole screen.

However, if the Touch Panel were to only function on the left-hand side of the monitor the following setup would be applied. This would be the same setting if this were the left monitor of a two-monitor system with the desktop spread over both monitors.

Note : It becomes a choice from the "Whole Desktop", “Primary Monitor", "Secondary Monitor" at the time of “9 points or 25 points Caribration” choices.

Multi Monotor

This example is when the video card of 2 output is carried on the computer and Touch Panel Device is connected with each.

Set up Touch Panel Device in "Secondary Monotor"  and "Primary Monitor".

Note: TPDD  for Windows ME does not support the multiple display environment.

Multi Monitor  limitation item.

(1)	Turn off the power supply of two access visions touch panel monitor  when you change the resolution of the primary monitor or the secondary monitor.Turn it on for more than 10 seconds again after the progress, and carry out Calibration in the turn of Primary -> Secondary.

Or, Calibration in the turn of Primary -> Secondary after the re-start of PC.

(2)Align the surface of primary monitor and secondary monitor or the left side, and use it with property of the screen.


Troubleshooting - Overview
Troubleshooting

If the Touch Panel Device is not working correctly it is important to try and correctly determine if the problem is hardware, software or system configuration related.

Select the fault below that best describes your problem

 Device Control Utility, Status dialog shows errors

 Difficulties with calibration

 Difficulties with double clicks

 Does not perform click emulation shown in Event Selector

 Incorrect button click emulation

 Missing system tray icons

 No system pointer movement

 System pointer moves incorrectly

 System mouse stops working

 USB device difficulties

If none of the above topics help, contact Gunze Limited, Japan.


Troubleshooting - Calibration difficulties
Troubleshooting

Calibration difficulties

A number of problems can occur during calibration:

No response

Either the device will not respond when the calibration points are touched, in which case the device is not responding and you should review the troubleshooting entry No system pointer movement.

Inaccurate alignment

After calibration the system pointer is not accurately aligned in which case you should refer to the troubleshooting entry System pointer moves incorrectly

Device not found

The Touch panel device cannot be found. This indicates that in the DCU devices screen, the registered Gunze, AHL, Serial or Gunze USB (touch panel) cannot be found.

 In this instance the following error dialog will be displayed:

See DCU Status dialog for more information.


Troubleshooting - Difficulties with double clicks
Troubleshooting

Difficulties with double clicks

Windows Settings

For Windows to recognize two clicks as a double click, the following conditions must be satisfied:

•	Both clicks must occur within the Windows DoubleClickSpeed specified in the Mouse Control Panel or the DCU Windows setting dialog

•	All four click actions (first click press, first click release, second click press, and second click release) must occur within the Double Click Height and Double Click Width threshold settings as defined in the DCU Windows settings dialog

•	The second click must not move, as Windows will interpret this as a drag

Ensure that the mouse Double Click Speed is set to slow (high number >= 900) and that the Height and Width settings allow for a double click to be achieved (at least 64 x 64 with 1024 x 768 video resolution or 100 x 100 with 1280 x 1024 video resolution).

Driver settings

If a button mode relies on a time touch event, such as time/time, increasing Clicktime makes the event take longer to occur. If you have set high values for ClickTime, try reducing it.

Events

Check that the Events mode you are using supports double clicks.  For example, the predefined mode "Time" is not configured for double clicks.  Try another button mode to see if your problem is related to the definition of the current button mode.


Troubleshooting - Event Selector misunderstanding
Troubleshooting

Event Selector misunderstanding

The Event Selector is used to change the Event State and will normally show a left or right mouse button image. Therefore when viewed on screen it is only natural to assume that with the left button on show a left button click will be performed and vice versa.  However, the Events associated with these images are defined in the DCU Event dialog and it is this association that determines what click emulation is to be performed.

In the following example the settings will produce the exact opposite of that expected. You have been warned!


Troubleshooting - Incorrect button click emulation
Troubleshooting

Incorrect button click emulation

Check the events page for primary and secondary events and their actions defined in the event dialog.

See also

 Does not perform click emulation shown in Event Selector


Troubleshooting - Missing system tray icons
Troubleshooting

Missing system tray icons

These icons can be enabled through DCU General dialog
by enabling the 'Show icons in system tray' check box and clicking Apply or invoke program SysTrayIcon directly from the TPDD program folder.

To invoke the system tray icons over a system reboot enable the 'Show icons in system tray' check box in the DCU General dialog


Troubleshooting - No system pointer movement
Troubleshooting

No system pointer movement

Hardware

•	Check that the Touch Panel Device has power and that it is correctly connected to the computer

•	If possible, use another device in the same hardware port to test that the hardware port is working

•	Power off the controller to reset it. It may be in a state that is stopping it functioning correctly. If the controller is held within the monitor enclosure, resetting the computer and/or turning off the monitor will not be enough as it is powered by the monitor's power supply.  The power must be removed completely from the unit to reset it.  Remove power for about 30 seconds

If no packets are generated there is a physical fault that needs to be corrected.

Driver

•	Look at the DCU Status dialog. If the text 'N/A' appears instead of correct status values then the TPDD is not loaded

•	Determine that the TPDD is loaded and functioning

       UFD:  Windows Control Panel->Administrative tools-> Computer management->Device Manager ->mice and other pointing devices-> Gunze right click on this, select Properties and see the description under General.

SFD:  Windows Control Panel->Administrative tools-> Computer management->Device Manager ->mice and other pointing devices-> Gunze Serial Touch Screen right click on this, select Properties and see the description under General.

•	In the Device Manager page, see above, check that the port does not conflict with other devices in the system

Configuration

•	Check the hardware settings correctly match the configuration of the device

•	Check that the correct controller is selected

•	For serial connected device check that the TPDD is configured for the correct serial port number

•	Check the DCU Status dialog to see if the protocol has loaded or has any errors. For serial connected devices check that no Communication or Sync errors are occurring. If they are occurring, enable or increase the FIFO setting

System

•	If you are experiencing serial port difficulty, check that there is no conflict with the serial driver and that the serial driver (serial.sys) or multiport driver (serrsap2.sys) is loaded


Troubleshooting - System pointer moves incorrectly
Troubleshooting

System pointer moves incorrectly

Consistent movement

•	If the system pointer stays in one area or moves consistently when using the Touch Panel Device, but not accurately, try calibrating the device

•	If you have installed a new version of the TPDD or have changed the device or have changed the protocol you may need to re-calibrate

Inconsistent movement

•	If the system moves only intermittently, the hardware communications settings may be set incorrectly, or you may have selected the wrong controller for the device

•	Check the DCU Status dialog to see if the protocol has loaded or has any errors. For serial connected devices check that no Communication or Sync errors are occurring. If they are occurring, enable or increase the FIFO setting


Troubleshooting - System mouse stopped working
Troubleshooting

System mouse stopped working

Serially connected mouse

It is possible that the mouse serial port has also been configured to be used by one of the controller protocols defined in the driver. If this is the case it is unlikely that either of the devices will be working. Determine what port the system mouse is plugged into and then check the hardware settings of the Touch Panel Device in the Hardware page of the Device Control Utility.  If any of them are clashing, either change the settings to match the port used by the driver pointing device or plug the mouse into another COM port.


Troubleshooting - Incorrect button click emulation
Troubleshooting

USB device difficulties

USB device not listed in devices

The Windows platform you are running does not support USB.

Plug and Play Manager could not find the driverf

The TPDD driver is not installed. Install driver and reboot system.


Maintenance and Support

Maintenance and Support

If you need support you should first check out the problems and solutions listed in the Troubleshooting section. If you are still unable to resolve the problem, contact Gunze Limited, Japan.

Please provide the following information:

•	Details of the Supplier from where you purchased the software

•	The TPDD version number

•	The Windows operating system in use, its build number (from the System applet in the Control Panel) and the service patch status

•	The Touch Panel Device and hardware settings

•	Description of your system (Make, model, architecture, processor, speed, adapters, peripherals, etc.)

•	Description of the problem, detailed enough to enable us to reproduce it

•	The exact text of any error messages you encountered

•	The system event log

•	Details of any other processes, such as applications or communication devices that may clash with the pointing device

•	Attach to the email the file GunzeSettings.txt produced by the Dump Settings function in the DCU General dialog

Not all the above will be relevant to the problem you are reporting but the general advice is supply more information rather than less

If you have discovered a known problem or one that is easily understood the response should be swift. However, if it is a new problem or one that cannot be reproduced, resolving it may be difficult and in some circumstances may require the hardware to be sent to Gunze Limited to help with investigations.


Glossary

Absolute Mode
Touch Panel Devices deal with Absolute coordinates.

Controller
The electronic information that is responsible for converting the information from the Touch Panel Device to data that is sent to the PC. The information is delivered in 'packets' and the structures of the packets are known as the 'Protocol'.

Linearity
The accuracy of the generated coordinates from a Touch Panel device. Moving the stylus across the surface of a pointing device should produce linear coordinates, incrementing evenly. If the device generates irregular coordinates it is considered being non-linear.

Packet
The data structure generated by a controller to pass specific items of information, such as a touch coordinate data or a liftoff request. These are typically 11 bytes in length.

Protocol
A protocol defines a controller's communication configuration and packet structure.

Relative Mode
A coordinate system that passes coordinate information relative to the last position. For example, the mouse protocol passes relative information.

Touch Panels
A device, normally attached to the system monitor, that digitizes touch movement in to coordinate packets, normally specified in absolute motion.


Driver functionality overview

Select a subject for further details

Driver control utility

Enhanced hardware port support

Event processing

Installation features

Improved data throughput

System tray utilities

Technical overview


Technical Overview

Technical Overview

Written in  C/ VC++ and uses  Win32 Driver Model
There are two drivers:

1.	Serial Filter driver (SFD) for serial interface. It interacts with serial.sys or multiport serial driver and Microsoft supplied mouclass driver.

2.	    USB filter driver (UFD) for USB communication. This interacts with USB stack and Microsoft supplied mouclass driver.

3.	    Driver Configuration Utility is an Application Program used to configure the Touch Panel Device.

All TPDD support programs are Win32 based.


Windows Control Panel

The Driver Control Utility has been implemented as a Windows Control Panel extension and therefore resides in the Windows Control Panel program group. The Windows Control Panel can be accessed by selecting the Windows Start button, Settings and then Control Panel.  Select the DCU icon as displayed.


Button modes

The TPDD can be set up to perform any type of Button click emulation and by default caters for the following left and right click Button Modes:

Touchdown / Touchdown Double
Touchdown Immediate
Time / Time Double
Time and Tap
Tab / Tab Double
Time and Time
Liftoff / Liftoff Double

The above modes can be selected for Primary and Secondary action from the Event dialog.


Enhanced hardware port support

Handles Serial and USB connected controllers.


Event processing

A controller event can be associated to a button mode.  These events include the default event actioned on receipt of a standard protocol packet. Each event has a primary and alternative option selected by the Event Selector utility.


Improved data throughput

100% protocol data throughput. No measurable driver induced delays on contact/draw/release sequences.


Installation features

The installation process will automatically stop running processes, allowing successful replacement. It caters for single and multiple Touch Panel Device installation. An install "record" facility can be used to create an automatic installation setup file to allow subsequent installations to be totally automated. This setup file can control all TPDD settings and do multiple screen setup in one session.


Protocol

This is normally between 3 to 10 bytes in length and each bit holds pointer information.  This information is typically X and Y coordinates, contact status and pointer click information (left or right mouse click emulation). The X and Y coordinates are typically held in 8, 10 or 12 bits of the protocol packet. 8 bits will generate a value in the range 0 - 255, 10 gives a range of 0 - 1023 and 12 gives a range of 0 - 4095.

The current TPDD supports AHL61 controller protocol only.


System tray utilities

System tray utilities are available to invoke the main user functionality.


Win32 Driver Model

Win32 Driver Model is a device driver standard introduced by Microsoft for Windows 2000. All communication by the driver with the operating system is in the form of WDM calls.


Windows systems

This driver works in Win Xp and 2000  and  Me.

But TPDD for Winwoes Me is another installer.