Touch Controllers Reference Guide
The information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of MicroTouch Systems, Inc. MicroTouch may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.
Contents About This Manual What You Need to Know.............................................................8 MicroTouch Support Services......................................................8 MicroTouch Technical Support...............................................8 MicroTouch on the World Wide Web.....................................9 MicroTouch Bulletin Board System ........................................9 MicroTouch Corporate Headquarters and Worldwide Offices.....
Touch Controllers Reference Guide Communicating with the Controller............................................ 20 Sending Commands to the Controller ................................... 20 Receiving Responses from the Controller ............................. 21 CHAPTER 2 Firmware Commands Summary of Firmware Commands ............................................. 24 AutoBaud Disable...................................................................... 26 AutoBaud Enable..................................
Contents 5 Output Identity...........................................................................66 Output Status.............................................................................67 Parameter Lock..........................................................................68 Parameter Set.............................................................................69 Pen Only ....................................................................................71 Pen or Finger ...................
Touch Controllers Reference Guide Setting the Communication Port........................................... 98 Setting the Interrupt Request ............................................... 99 Setting the JP2 Jumper for Proper Operation...................... 100 APPENDIX C TouchPen Controllers TouchPen Controller Mechanical ............................................. 102 Technical Specifications........................................................... 102 TouchPen Diagnostics .......................
About This Manual This reference manual, which is intended for developers of touch systems, provides information about the MicroTouch touchscreen controllers and available firmware commands. The description of each command includes the command syntax, the default value, how the command works, and the response from the controller. Developers may use this information when writing touch applications, developing a custom driver or touch configuration, or testing their touch systems.
Touch Controllers Reference Guide What You Need to Know This document assumes you are familiar with firmware commands and how to use them. Executing some commands may alter the performance of your touch product. You should be aware of the results of using these commands before executing them. MicroTouch Support Services MicroTouch provides extensive support services through our technical support organization, web site, and bulletin board system (BBS).
About This Manual 9 You can contact MicroTouch Technical Support by calling the hot line, sending a fax, or sending electronic mail. x Technical Support Hot Line: 978-659-9200 x Technical Support Fax: 978-659-9400 x Technical Support E-Mail: support@microtouch.com MicroTouch on the World Wide Web You can visit the MicroTouch web site at the following address: http://www.microtouch.
Touch Controllers Reference Guide MicroTouch Corporate Headquarters and Worldwide Offices United States MicroTouch Systems, Inc. 300 Griffin Brook Park Drive Methuen, MA 01844 Main Phone: 978-659-9000 Main Fax: 978-659-9100 Web Site: http://www.microtouch.com E-Mail: touch@microtouch.com Tech Support Hot Line: 978-659-9200 Tech Support Fax: 978-659-9400 Tech Support E-Mail: support@microtouch.com Australia MicroTouch Australia, Pty Ltd.
C H A P T E R 1 MicroTouch Touchscreen Controllers MicroTouch offers several advanced low-power, surface-mount controllers that are designed for reliability and easy installation. Each controller provides superior performance and delivers unparalleled sensitivity, accuracy, and fast response.
Touch Controllers Reference Guide Overview of Touchscreen Controllers MicroTouch offers controllers for both capacitive touchscreens and resistive touchscreens. Table 1 lists the MicroTouch touchscreen controllers, including name, part number, technology supported, and mounting options. Table 1.
Chapter 1 MicroTouch Touchscreen Controllers 13 Serial/SMT Controllers The Serial/SMT controllers are compact (3.5 x 2.25 x 0.3 inches), RS-232 serial controllers. The controller can be internally mounted in your monitor, or enclosed in a molded plastic case (3.75 x 2.5 x 0.9 inches) and mounted to the back or side of your monitor. Daughterboard Controllers The Daughterboard controller is a CMOS serial add-on board (3.5 x 2.25 x 0.3 inches) that you mount onto your CPU board.
Touch Controllers Reference Guide MousePort Controller The MousePort controller has an attached 8-foot, 6-pin mini-din PS/2 connector. You can connect this controller to a PS/2 mouse port, leaving your serial communication and bus slots available for other peripherals. Chip Set Controllers Chip sets are available to those developers who want to integrate a MicroTouch touchscreen controller directly into their own circuitry.
Chapter 1 MicroTouch Touchscreen Controllers 15 Controller Default Settings Table 2 lists the default settings for each controller. The sections that follow provide more information on each setting. Table 2.
Touch Controllers Reference Guide MicroTouch recommends that you use N, 8, 1 (no parity, 8 data bits, and 1 stop bit) and 9600 baud for most touch applications. All MicroTouch touchscreen drivers communicate with the controller at N, 8, 1, 9600. For the TouchPen controller, MicroTouch recommends 19200 baud for use with character recognition systems that require high pen data rates. Systems that cannot handle the higher data rates seen from the pen may result in degraded pen performance.
Chapter 1 MicroTouch Touchscreen Controllers 17 Data Formats Data format refers to the type of packet the controller uses to send the X, Y touch coordinate to the host system. As listed in Table 2, the default data format for your controller may be Format Decimal or Format Tablet. However, MicroTouch recommends that you use Format Tablet for the following reasons: x Format Tablet uses only 5 bytes per point and provides the most rapid response time to a touch.
Touch Controllers Reference Guide Operating Modes The operating mode specifies the conditions under which the controller sends the X, Y touch coordinates (input data packet) to the host system. Mode Stream is the default operating mode for all MicroTouch touchscreen controllers. In Mode Stream, the controller sends a continuous stream of data packets. The controller sends the data as long as the touch device (finger or pen) continues to touch the screen.
Chapter 1 MicroTouch Touchscreen Controllers 19 Controller Initialization To achieve optimal touchscreen performance, MicroTouch recommends that you initialize your controller. The initialization commands vary depending on your controller. Table 3 lists the firmware commands you should send to the controller during your factory configuration. Additionally, if your controller supports the Output Status command, the controller automatically sends the output status information to the host on power-up.
Touch Controllers Reference Guide Communicating with the Controller This section provides information on sending firmware commands to and receiving commands from the MicroTouch controller. Commands to the controller are provided on signal Receive Data (RXD) as a serial data stream. Responses are data sent from the controller to the host system in response to the commands received by the controller.
Chapter 1 MicroTouch Touchscreen Controllers 21 Receiving Responses from the Controller After executing a command, the controller returns a response or acknowledgment to the host system. Each controller response consists of a header, the command response, and a terminator in the following format: Command Response Note: The following descriptions of header, response, and terminator, use MicroTouch’s terminal emulator key sequences.
Touch Controllers Reference Guide Note: There are exceptions to the meaning of these responses. For details on each command response, refer to Chapter 2. The terminator is the last character of each response string and is an ASCII carriage return . An ASCII represents 0D hexadecimal. The value returned in the response will be the ASCII key sequence Ctrl M (^M).
C H A P T E R 2 Firmware Commands Developers can use firmware commands to control the operation of the touchscreen controller. The firmware commands, which are usually issued by a driver or utility program on the host system, control the operation of the touchscreen controller.
Touch Controllers Reference Guide Summary of Firmware Commands To optimize the performance of the touchscreen controllers and simplify the development of custom drivers, MicroTouch recommends you use the commands listed in Table 4. Additionally, MicroTouch recommends that developers writing drivers or applications that communicate directly with our controllers use the commands listed in Table 4 regardless of their controller type.
Chapter 2 Firmware Commands 25 Table 5.
Touch Controllers Reference Guide AutoBaud Disable Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: AD Description: Turns off the automatic baud rate detection feature. When you disable AutoBaud, the controller maintains the communication rate currently set in non-volatile RAM (NOVRAM).
Chapter 2 Firmware Commands 27 AutoBaud Enable Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: AE Description: Turns on the automatic baud rate detection feature. When you enable AutoBaud, the controller changes its communication rate to that of the next command from the host system.
Touch Controllers Reference Guide Calibrate Extended Syntax: CX Description: Initiates an interactive, two-point calibration. During the calibration process, you define the active area of the touchscreen by mapping locations to an absolute X, Y coordinate system. You touch two target areas on the screen. Touching the target areas sends the X, Y coordinates for those touch points to the controller. The controller calculates all other touch points based on these two points.
Chapter 2 Firmware Commands (0, 0) 29 (639, 0) (560, 60) Upper right calibration target. X coordinate: 640 - (640 x 1/8) = 640 - 80 Y coordinate: 0 + (480 x 1/8) = 0 + 60 (80, 420) (0, 479) Lower left calibration target. X coordinate: 0 + (640 x 1/8) = 0 + 80 Y coordinate: 480 - (480 x 1/8) = 480 - 60 For some controllers, you can adjust the default calibration points using the Set Parameter Block command. For more information, contact MicroTouch.
Touch Controllers Reference Guide Calibrate Extended Procedure ¾ To use the CX command: 1. Enter the Calibrate Extended (CX) command. The controller sends an acknowledgment of 0. 2. Touch the screen at a lower left target, which is located 12.5% (1/8) in from the corner of the video image. The controller returns an acknowledgment of 1. This is a positive response. If you receive a negative response, try touching the screen again. 3.
Chapter 2 Firmware Commands Response: 31 1 Positive response. Indicates that the controller received a valid touch coordinate (point) when the target was touched. Two valid touch points indicate a successful calibration. 0 Negative response. Indicates that the touch point is out of range of the expected target area. If you receive a negative response, try touching the target area again.
Touch Controllers Reference Guide Calibrate Interactive Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: CI Description: Initiates an interactive, two-point edge calibration.
Chapter 2 Firmware Commands 33 Calibrate New Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: CN Description: Initiates an interactive, two-point edge calibration.
Touch Controllers Reference Guide Calibrate New Procedure ¾ To use the CN command: 1. Enter the Calibrate New (CN) command. The controller sends an acknowledgment of 0. 2. Touch the screen at a lower left target, which is located at the corner of the video image. The controller returns an acknowledgment. Refer to Table 7 for the acknowledgment values for the format you are using. If the acknowledgment is positive, continue to the next step.
Chapter 2 Firmware Commands 35 The value of the positive response for the upper right touch point varies depending on whether you are using Format Binary, Format Tablet, Format Decimal, or Format Hexadecimal. In general, the positive response is 1 and the negative response is 0. There are, however, two exceptions to this rule. If you are using Format Decimal or Format Hexadecimal, the positive response is 0 and the negative response is 1.
Touch Controllers Reference Guide Calibrate Raw Syntax: CR Description: Allows the collection of raw (signed) X and Y coordinates prior to the normal scaling, linearization, and filtering processes. The controller sends the coordinates whenever a touch is detected and continues to send a stream of data as long as a finger or pen remains in contact with the touchscreen. The Calibrate Raw data is a 5-byte packet that includes 1 status byte and 4 bytes of binary X, Y coordinate data.
Chapter 2 Firmware Commands MSB* Bits 37 LSB* Data Sequence 7 6 5 4 3 2 1 0 S - Byte 1 1 S6 S5 S4 S3 S2 S1 S0 X - Byte 2 0 X3 X2 X1 X0 x - Byte 3 0 Xs** X9 X8 X7 Y - Byte 4 0 Y3 Y2 Y1 Y0 y - Byte 5 0 Ys** Y9 Y8 Y7 Reserved X6 X5 X4 Reserved Y6 Y5 Y4 * MSB = Most Significant Bit, LSB = Least Significant Bit ** s = sign bit Table 8 describes the meaning of the bits in the status byte (Byte 1). Table 8.
Touch Controllers Reference Guide Filter Number Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: FNnn where: nn = Two ASCII characters ranging from 10 to 99.
Chapter 2 Firmware Commands 39 x For cursor applications The cursor first moves to a point near the finger and then moves to the true touchdown point. The cursor follows the finger appropriately while drawing, but produces inaccurate cursor movement when the screen is initially touched. Response: 0 Positive response.
Touch Controllers Reference Guide Finger Only Syntax: FO Description: Sets the mode of operation of a TouchPen controller to accept only finger input. The TouchPen controller ignores pen input. There are three modes available: x Finger Only mode detects finger contact only and processes finger coordinate data. x Pen Only mode detects pen contact only and processes pen coordinate data.
Chapter 2 Firmware Commands 41 Format Binary Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: FB Description: Outputs the X, Y touch coordinate data as a 5-byte packet in a binary format.
Touch Controllers Reference Guide Response: 0 Positive response. After the controller is in Format Binary mode, the host must issue a Ctrl Q (^Q) before the controller sends the touch coordinate.
Chapter 2 Firmware Commands 43 Format Binary Stream Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: FBS Description: Functions exactly like the Format Binary command, except the Format Binary Stream command initializes the operating mode to Mode Stream instead of Mode Polled.
Touch Controllers Reference Guide Format Decimal Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: FD Description: Outputs the X, Y touch coordinate data as a 9-byte packet in a decimal format (using the hexadecimal representation of decimal values).
Chapter 2 Firmware Commands Response: 45 0 After the controller is in Format Decimal mode, touching the screen causes the controller to return a response in the following format: Xxx,Yyy where: = Start-of-header (Hex 01). If you send a Mode Status command after a Format Decimal command, this first byte becomes a status byte.
Touch Controllers Reference Guide Format Hexadecimal Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: FH Description: Outputs the X, Y touch coordinate data as a 9-byte packet in a hexadecimal format.
Chapter 2 Firmware Commands Response: 47 0 After the controller is in Format Hexadecimal mode, touching the screen causes the controller to return a response in following format: Xxx,Yyy where: = Start-of-header (Hex 01). If you send a Mode Status command after a Format Hexadecimal command, this first byte becomes a status byte.
Touch Controllers Reference Guide Format Raw Syntax: FR Description: Returns the signal level (amount of touch) of each of the four touchscreen corners in digital format. The returned values are not corrected for offset and stray values. However, you can obtain the offset and stray values using the Get Parameter Block command. For more information, refer to the description of the Get Parameter Block command later in this chapter.
Chapter 2 Firmware Commands Response: 0 49 Positive response. After the controller is in Format Raw mode, the controller returns a response in the following format: <7-byte-packet><7-byte-packet>...<7-byte-packet>...
Touch Controllers Reference Guide Format Tablet Syntax: FT Description: Outputs the X, Y touch coordinate data in a 5-byte packet. The packet includes 1 status byte and 4 bytes of binary X, Y coordinate data. The protocol also establishes the X and Y coordinate output as 14 binary bits providing a range of 0 to 16,383.
Chapter 2 Firmware Commands MSB* Bits 51 LSB* Data Sequence 7 6 5 4 3 2 1 0 S - Byte 1 1 S6 S5 S4 S3 S2 S1 S0 X - Byte 2 0 X6 X5 X4 X3 X2 X1 X0 x - Byte 3 0 X13 X12 X11 X10 X9 X8 X7 Y - Byte 4 0 Y6 Y5 Y4 Y3 Y2 Y1 Y0 y - Byte 5 0 Y13 Y12 Y11 Y10 Y9 Y8 Y7 * MSB = Most Significant Bit, LSB = Least Significant Bit Table 9 defines the status bits (Byte 1) for the Format Tablet data. Table 9.
Touch Controllers Reference Guide Format Zone Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: FZ Description: Outputs the X, Y touch coordinate data as a 5-byte packet and indicates whether the touch occurred inside or outside the calibration area.
Chapter 2 Firmware Commands MSB* Bits 53 LSB* Data Sequence 7 6 5 4 3 2 1 0 Zone - Byte 1 S7 S6 S5 S4 S3 S2 S1 S0 X - Byte 2 0 0 1 X9 X8 X7 X6 X5 x - Byte 3 0 0 1 X4 X3 X2 X1 X0 Y - Byte 4 0 0 1 Y9 Y8 Y7 Y6 Y5 y - Byte 5 0 0 1 Y4 Y3 Y2 Y1 Y0 * MSB = Most Significant Bit, LSB = Least Significant Bit If you send a Format Zone command and then send a Mode Status command, the Format Zone command no longer reports whether the the touch point is within t
Touch Controllers Reference Guide Frequency Adjust Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: Fnn where: nn = Two ASCII characters that define the frequency setting. Refer to Table 10 for values.
Chapter 2 Firmware Commands Table 10. Frequency Settings (in Hz) Response: nn Serial/SMT2 Frequency Serial/SMT3 Frequency 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 39 40 41 42 43 44 45 25000.00 (default) 22727.27 22727.27 20833.33 19230.77 19230.77 17857.14 16666.67 16666.67 15625.00 14705.88 14705.88 13888.89 13157.89 13157.89 11904.76 11904.76 11363.64 10869.57 10869.57 10416.67 10000.00 9615.38 9259.26 9259.26 8928.57 8620.69 8620.69 8333.33 33500.00 34600.00 35400.
Touch Controllers Reference Guide Get Parameter Block Description: Allows access to all power-up and run time parameters used by the controller. The Get Parameter Block (GP) command works in conjunction with the Set Parameter Block (SP) command. You use this pair of commands for configuration and diagnostic purposes. You use the Get Parameter Block command to retrieve the parameters. You then use the Set Parameter Block command to modify the data and write the data back to the controller.
Chapter 2 Firmware Commands 57 Mode Down/Up Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: MDU Description: Send one X, Y coordinate for each touchdown and each liftoff on the touchscreen.
Touch Controllers Reference Guide Mode Inactive Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: MI Description: Sends no X, Y coordinates when the screen is touched.
Chapter 2 Firmware Commands 59 Mode Point Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: MP Description: Sends a single X, Y coordinate for each touchdown. In Mode Point, the controller sends one X, Y coordinate when the screen is touched.
Touch Controllers Reference Guide Mode Polled Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: MQ Description: Sends an X, Y coordinate only when requested by the host system and only when a user touches the screen.
Chapter 2 Firmware Commands 61 x The controller stores only one set of touchdown and liftoff points. If the screen is touched more than once before the controller receives a ^Q, the controller reports the most recent touchdown point only. If a touchdown is reported, it will report the last liftoff point regardless of how many times liftoff has happened before the second ^Q is received. Note that the controller does not send any data in response to the ^Q request if a user does not touch the screen.
Touch Controllers Reference Guide Mode Status Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: MT Description: Sends a touch status byte preceding the X, Y coordinate data sent in response to a Format Decimal or Format Hexadecimal command.
Chapter 2 Firmware Commands Response: 0 63 Positive response. If the controller is in Format Decimal or Format Hexadecimal mode and you receive a positive response to Mode Status, touching the screen causes the controller to return the following response: Xxx,Yyy where: = Defines how the X, Y coordinates are generated, where: ^Y (Hex 19) is a touchdown (first position of finger on the screen). ^\ (Hex 1C) is a continued touch (position of finger remains on the screen).
Touch Controllers Reference Guide Mode Stream Syntax: MS Description: Sends a continuous stream of X, Y coordinate data when you touch the screen. The controller continues to send data as long as you touch the screen. The controller sends the data even if the touch is stationary and unchanging. The format of the coordinate data depends on the last format command received by the controller.
Chapter 2 Firmware Commands 65 Null Command Syntax: Z Description: Queries the controller and waits for a response. Use Z to determine that you are communicating with the controller or to make sure that a utility is communicating with the controller. Using this command does not affect the controller’s current operating parameters. Response: 0 Positive response.
Touch Controllers Reference Guide Output Identity Syntax: OI Description: Returns a 6-character identifier, which describes the controller type and the firmware version number. Response: CcXxxx where: Cc = Two ASCII characters that describe the type of controller.
Chapter 2 Firmware Commands 67 Output Status Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: OS Description: Causes the controller to report the status of its hardware. On power-up, the controller automatically sends the output status information to the host.
Touch Controllers Reference Guide Parameter Lock Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: PL Description: Writes and stores the data format and operating mode of the controller into non-volatile memory (NOVRAM).
Chapter 2 Firmware Commands 69 Parameter Set Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: Ppds[b] where: Description: p = Parity type. N = No parity O = Odd parity E = Even parity d = Number of data bits (7 or 8). s = Number of stop bits (1 or 2). b = Communication rate.
Touch Controllers Reference Guide x The Parameter Set command is issued with the new parameters to the controller. The new settings take effect immediately. x The host system must be changed to the new parameters in order to communicate with the controller again. Examples: PN813 Sets the serial line to no parity, eight data bits, one stop bit, and 4800 baud. PN81 Sets the parity, data bits, and stop bits; leaves the baud at its previous value.
Chapter 2 Firmware Commands 71 Pen Only Syntax: PO Description: Sets the operational mode of a TouchPen controller to accept only pen input. The controller ignores finger data. There are three pen modes available: x Pen Only mode detects pen contact only and processes pen coordinate data. x Pen or Finger mode detects pen and finger contact, giving priority to pen contact when both are detected. Pen or Finger mode is the default mode for TouchPen controllers.
Touch Controllers Reference Guide Pen or Finger Syntax: PF Description: Sets the operational mode of a TouchPen controller to accept both pen and finger input. Pen or Finger mode is also called automatic mode. In Pen or Finger mode, the controller gives higher priority to the pen. x If the controller detects both pen and finger touches at the same time, pen contact has higher priority. The controller acknowledges only the pen touches and sends pen coordinate data to the host system.
Chapter 2 Firmware Commands 73 There are three pen modes available: x Pen or Finger mode detects pen and finger contact, giving priority to pen contact when both are detected. Pen or Finger mode is the default mode for TouchPen controllers. x Finger Only mode detects finger contact only and processes finger coordinate data. x Pen Only mode detects pen contact only and processes pen coordinate data. The pen mode changes back to the default setting at power-up, or if you issue a Restore Defaults command.
Touch Controllers Reference Guide Reset Syntax: R Description: Initializes the hardware and the firmware, causes the controller to stop sending data, and recalculates the environmental conditions (for example, stray and offset values). The Reset command also cancels the Format Raw and Calibrate Raw commands and returns the controller to normal operation.
Chapter 2 Firmware Commands 75 Restore Defaults Syntax: RD Description: Returns to the factory default operating parameters. The Restore Defaults command copies the MicroTouch factory default parameters from ROM to the non-volatile memory (NOVRAM) and then executes a Reset command. Table 11 lists the factory defaults for each touchscreen controller. The Restore Defaults command is useful in situations where inadvertent commands to the controller have rendered the touchscreen inoperative.
Touch Controllers Reference Guide Note the serial communication settings restored by this command. Application programs operating at other communication settings that issue this command must change to the default settings to receive the command response and re-establish communication with the controller. Note: After you issue a Restore Defaults command, calibrate your touchscreen using the Calibrate Extended command.
Chapter 2 Firmware Commands 77 Sensitivity Set Note: MicroTouch provides this command for compatibility with older touchscreen controllers. To ensure compatibility with all existing and future MicroTouch controllers, do not use this command when developing your touch drivers and applications. Syntax: SEn where: n = Sensitivity level.
Touch Controllers Reference Guide Set Parameter Block Description: Sets power-up and run time parameters used by the controller. The Set Parameter Block (SP) command works in conjunction with the Get Parameter Block (SP) command. You use this pair of commands for configuration and diagnostic purposes. You use the Get Parameter Block command to retrieve the parameters. You then use the Set Parameter Block command to modify the data and write the data back to the controller.
Chapter 2 Firmware Commands 79 Unit Type Syntax: UT Description: Responds with an 8-character identity string. This string identifies the type of controller currently attached to the system, lists the features supported by the controller, and outputs the status of the controller hardware (a self-test code). Response: Returns an identification code up to 8 ASCII characters in the following format: TtFfffSs where: Tt = Two ASCII characters that identify the controller type.
Touch Controllers Reference Guide Note: If your controller does not support the Unit Type command, you can use the Unit Type Verify command or the Output Identity and Output Status commands to obtain information about the controller type, the firmware revision, and the hardware status. Table 12. Bit Definition for the Unit Type Command Bit Serial/SMT3 Status TouchPen Status 0 Reserved. RAM error. Hardware malfunction. 1 ROM error. Firmware checksum verification error. Same. 2 PWM error.
Chapter 2 Firmware Commands 81 Unit Type Verify Syntax: UV Description: Responds with an 8-character identity string. This string identifies the type of controller currently attached to the system, lists the features supported by the controller, and outputs the status of the controller hardware (a self-test code). Refer to the Unit Type command for a description of the 8-character identity string. The Unit Type command and the Unit Type Verify command return the exact same information.
C H A P T E R 3 Controller LED Diagnostics MicroTouch controllers are highly reliable units; however, there may be occasions when the controller does not perform exactly as you expected. Serial/SMT controllers provide visual feedback via an LED indicator on the controller. When you power-up the unit, the LED is bright until the controller start-up sequence completes. Following start-up, the LED becomes dim and remains dim as long as you do not touch the touchscreen.
Touch Controllers Reference Guide Serial/SMT2 LED Codes Table 13 decribes the meaning of a blinking status light (LED) for all controllers that use Serial/SMT2 hardware. The SMT2 series includes the following controllers: x Serial/SMT2 controller x Serial/SMT2 Daughterboard x PC Bus SMT2 controller Table 13. LED Diagnostic Codes for SMT2 Series of Controllers LED Flashes (per 10 seconds) Error Description 1 RAM error. Hardware malfunction. 2 ROM error. Firmware checksum verification error.
Chapter 3 Controller LED Diagnostics 85 For controllers in the SMT3 series, you can use the Unit Type command or the Unit Type Verify command to obtain the result of the self-test. You can interpret the result using the self-test bit described in Table 14. Table 14. LED Diagnostic Codes for SMT3 Series of Controllers LED Flashes (per 10 seconds) Error Description Self-Test Bit (Unit Type or Unit Type Verify Commands) 1 0 Reserved. 2 1 ROM error. Firmware checksum verification error.
Touch Controllers Reference Guide TouchPen Diagnostics TouchPen controllers do not have an LED. You can, however, use the Unit Type command to obtain status information on the controller hardware.
A P P E N D I X A Serial/SMT Controllers The Serial/SMT controllers are compact (3.5 x 2.25 x 0.3 inches), RS-232 serial controllers. The controller can be internally mounted in your monitor, or enclosed in a molded plastic case (3.75 x 2.5 x 0.9 inches) and mounted to the back or side of your monitor. This appendix provides controller specifications such as power requirements, environmental requirements, and cable connectors.
Touch Controllers Reference Guide Serial/SMT2 Controller Mechanical Figure 1 shows the overall dimensions of the Serial/SMT2 controller and the locations of the mounting holes and connectors. Figure 1.
Appendix A Serial/SMT Controllers Serial/SMT3 Controller Mechanical Figure 2 shows the overall dimensions of the Serial/SMT3 controller and the locations of the mounting holes and connectors. Figure 2.
Touch Controllers Reference Guide Technical Specifications Power: Serial/SMT2 Series of Controllers +5V Input: +5 VDC (70 mA typical, 85 mA maximum), r5% regulation, 100 mV maximum ripple and noise. +12V Input: 8 – 15 VDC (80 mA typical, 100 mA maximum), 400 mV maximum ripple. Serial/SMT3 Series of Controllers +5V Input: +5 VDC (47 mA typical, 60 mA maximum), r5% regulation, 100 mV maximum ripple and noise. +12V Input: 8 – 15 VDC (47 mA typical, 60 mA maximum), 400 mV maximum ripple.
Appendix A Serial/SMT Controllers 91 Female Connector on the Touchscreen Cable The touchscreen (sensor) cable has a 12-pin (2 x 6) dual row female connector that plugs into the controller. Table 15 describes the pins on this connector. Table 15.
Touch Controllers Reference Guide Communication Connector All Serial/SMT controllers have an attached RS-232 communication cable with a 9-pin D female connector. Table 16 describes the pins for this cable, which connects to a serial communication (COM) port on the PC. A 9-pin to 25-pin adapter is available. Table 16. COM Connector (9-pin D, RS-232) for Serial/SMT Controllers 9-pin D 7-pin Molex Wire Color Description 1 No connection ——— Data Carrier Detect (DCD). Connected to DTR and DSR.
A P P E N D I X B PC Bus Controllers The PC Bus controller is a half-slot, bus card that you install in your system. It has its own serial communication (COM) port, enabling you to use your existing COM ports for other peripherals. To use the PC Bus controller, your computer must have an available 16-bit ISA (Industry Standard Architecture) expansion slot. The touchscreen cable connects to the port on the controller.
Touch Controllers Reference Guide PC Bus Controller Mechanical Figure 3 shows the overall dimensions of the PC Bus controller. Figure 3.
Appendix B PC Bus Controllers 95 Technical Specifications Power: +5 VDC (200 mA typical, 300 mA maximum), r5% regulation. +12 VDC (70 mA typical, 100 mA maximum), r10% regulation. -12 VDC (50 mA, typical, 70 mA maximum), r10% regulation. 100 mV maximum ripple and noise. Operating Temperature: 0 to 55 degrees C. Relative Humidity: 0 to 95% noncondensing. Circuit Board Size: PC expansion bus half card. Cable: Shielded cable with a 9-pin D connector to attach the touchscreen to the PC Bus controller.
Touch Controllers Reference Guide Connectors and Cabling Table 17 describes the pins on the PC Bus cable. 9-pin D connector 2 12 1 11 2 x 6 male connector Table 17.
Appendix B PC Bus Controllers 97 Jumpers on the PC Bus Controller The PC Bus controller communicates with the computer through an asynchronous serial port on the controller. Every serial device in your PC must use a unique serial communication (COM) port and a unique interrupt request (IRQ). The PC Bus controller uses the following default settings: x Communication Port: COM3 x Interrupt Request: IRQ4 By default, most PC configurations use IRQ4 for COM1 or COM3.
Touch Controllers Reference Guide Setting the Communication Port The pins labeled A1 – A6 on JP1 define the serial communication (COM) port for the PC Bus controller. x Valid ports are COM1 through COM8. Refer to Table 18. x The default is COM3. In most PC configurations, the mouse uses COM1. However, if you are using a touchscreen and a mouse, both devices cannot use the same COM port. You must be sure there are no device conflicts. Note: The PC Bus controller does support COM8.
Appendix B PC Bus Controllers 99 Setting the Interrupt Request The pins labeled I2 – I15 on JP1 define the interrupt request (IRQ) for the PC Bus touchscreen controller. x Valid IRQs are 2, 3, 4, 5, 10, 11, 12, and 15. Refer to Table 19. x The default is IRQ4. You can use any IRQ for the PC Bus controller as long as another device in your system configuration is not using the same IRQ. The PC Bus controller cannot share an IRQ with another device.
Touch Controllers Reference Guide Table 19.
A P P E N D I X C TouchPen Controllers The TouchPen controller offers the same features as the Serial/SMT capacitive controller, with the addition of pen support. The controller can accept touch input from both a finger and the touch pen. TouchPen controller mounted internally Touchscreen cable Touch pen This RS-232 serial controller, which measures a trim 1.35 x 4.8 x 0.3 inches, is designed to easily fit inside flat panel displays and CRTs. The TouchPen controller is always mounted internally.
Touch Controllers Reference Guide TouchPen Controller Mechanical Figure 4 shows the overall dimensions of the TouchPen controller and the locations of the mounting holes and connectors. Figure 4. TouchPen Touchscreen Controller Technical Specifications Power: +12V Input: 12 – 16 VDC (100 mA typical, 120 mA maximum), r5% regulation, 100 mV maximum ripple and noise. Operating Temperature: 0 to 55 degrees C. Relative Humidity: 0 to 95% noncondensing. Circuit Board Size: 1.35 x 4.8 inches, 0.
Appendix C TouchPen Controllers 103 TouchPen Diagnostics TouchPen controllers do not have an LED. You can, however, use the Unit Type command to obtain status information on the controller hardware. Connectors and Cabling Figure 5 shows the layout of the TouchPen controller and connectors. Table 20 describes the pins on each connector. Table 20.
Touch Controllers Reference Guide The pen cable is a 6-wire cable with shield. One-to-one connections; shield is tied to Pin 6. 8-pin standard telephone jack for connecting pen. Pin 1 Pin 6 (ground) not usually used. Instead, supply ground to the controller by mounting through the mounting holes to the chassis. Pin 1 Microcontroller COM & Power Connector 2.70 in 4.80 in Sensor Connector .60 in Pen Connector 1.35 in Pin 1 Notes: 1. Diameter of mounting holes is 0.175 inches. 2.
A P P E N D I X D Daughterboard Controllers MicroTouch has two models of the Daughterboard controller: x SMT2 Daughterboard (Part Number: 14-73) x SMT3V Daughterboard (Part Number: 14-89) This chapter describes how to integrate a MicroTouch Daughterboard controller onto a system board.
Touch Controllers Reference Guide Overview of the Daughterboard Controller The Daughterboard controller is a low power, miniaturized board that is easily integrated onto a system board. The daughterboard design eliminates the more complicated layout and design issues of a chip set and interfaces directly with the touchscreen through CMOS asynchronous serial communication. The controller supports CMOS communication rather than RS-232 communication.
Appendix D Daughterboard Controllers 107 Daughterboard Controller Mechanical Figure 6 shows the overall dimensions of the Daughterboard controller, the locations of the mounting holes and connectors, and the maximum component height. Notes: 1. All holes are plated thru and tied to ground. 2. All measurements are in inches. 3. .xxx = r.005 Figure 6. Daughterboard Controller Technical Specifications Power: Power is supplied by the host system.
Touch Controllers Reference Guide Status Light (LED) Diagnostics The LED status light on the Daughterboard controller provides information on power-up, screen touches, and hardware problems. For more information on the status light, refer to Chapter 3. Serial Interface The serial interface for the touchscreen connects the microcontroller and the host system. The communication interface uses a universal asynchronous communication protocol and the communication levels are CMOS compatible.
Appendix D Daughterboard Controllers 109 Female Connector on the Touchscreen Cable The touchscreen cable has five wires that terminate into a molded 12-pin dual row female connector. It also contains a 1K bit nonvolatile memory chip that stores screen linearization coefficients. Table 21 shows the pin out for the female connector on the touchscreen cable. The Molex part number for this connector is 70182-15-45-0906. Table 21.
Touch Controllers Reference Guide Male Connector on the Daughterboard Controller The Daughterboard controller has a 14-pin dual row male connector soldered to the component side of the PCB. This connector provides all sensor signals as well as TXD, RXD, and reset connections to the controller. Table 22 shows the pin out for the male connector on the Daughterboard controller. The Molex part number for this connector is 8624-10-88-1141. Table 22.
Appendix D Daughterboard Controllers 111 Supplying Power to the Daughterboard Controller The host system provides the power to the Daughterboard controller. The controller requires 70 mA (typical), 85 mA (maximum supply current), at +5 volts DC, +5% regulation, and 100 mV maximum ripple and noise. Electrical Specifications for Transmit and Receive Table 23 lists the D.C. characteristics for the universal asynchronous receiver transmitter (UART).
Touch Controllers Reference Guide Layout of the System Board Figure 7 shows some typical techniques for two layer boards. The same techniques apply to four layer boards except that the various planes may be put on inner layers. To design the Daughterboard controller onto the system board and to ensure optimal operation, follow these guidelines: A. Route the shield signal (Pin 8) and the corner drive lines (Pin 9-UR, Pin 10-LR, Pin 11-UL, Pin 12-LL) on the component side.
Appendix D Daughterboard Controllers 113 Inset A-A VCC (+5 V) 2 2 2 2 2 3 3 3 3 3 1 1 1 1 1 8 10 9 12 11 MMBD7000 Diodes (or equivalent) Quantity = 5 Chassis Ground E Refer to Inset A-A ` 2 Touchscreen connector 12 Pin 1 11 A, D LED Pin 1 13 2 14 Daughterboard (Component side down) +8 to 15 VDC (Pin 7) Signal Ground (Pins 5, 6) Figure 7.
Touch Controllers Reference Guide Electrostatic Discharge (ESD) Considerations You should test your completed board layout for general design as well as ESD in accordance with the IEC 801-2 specification. In general, ESD characteristics are different for each design. Disclaimer: This chapter describes a means by which you can make the connections. It does not guarantee that your board design will pass ESD testing. MicroTouch is not liable for design problems.
Index ^ ^CF (Frequency Adjust) command 54 blocks getting parameters from 56 setting parameters in 78 bulletin board system (BBS) 9 A acknowledgments to a command 21 AD (AutoBaud Disable) command 26 AE (AutoBaud Enable) command 27 ASIC, definition of 80 AutoBaud Disable command 26 AutoBaud Enable command 27 automatic mode See Pen or Finger command B baud rate setting 69 turning off auto detection 26 turning on auto detection 27 binary format 41, 43 bits setting data and stop 69 touch state (proximity) 37
Touch Controllers Reference Guide communication connector 92 communication port, defining for PC Bus controller 98 communication rate setting 69 turning off auto detection 26 turning on auto detection 27 communication settings defaults 15 defining with Parameter Set command 69 connector Daughterboard controller 108 PC Bus cable 96 Serial/SMT communication 92 Serial/SMT touchscreen cable 91 TouchPen controllers 103 controllers default settings 15 description of 12 diagnostics 83 identifying type of 66,
Index F G factory defaults 15, 75 factory initialization 19 failed command response 21 FB (Format Binary) command 41 FBS (Format Binary Stream) command 43 FD (Format Decimal) command 44 feel of touch, adjusting 77 FH (Format Hexadecimal) command 46 Filter Number command 38 Finger Only command 40 firmware commands receiving responses to 21 recommendations for using 24 sending 20 summary of 25 syntax 20 firmware version, identifying 66 FN (Filter Number) command 38 FO (Finger Only) command 40 Format Binary
Touch Controllers Reference Guide M MDU (Mode Down/Up) command 57 MI (Mode Inactive) command 58 Mode Down/Up command 57 Mode Inactive command 58 Mode Point command 59 Mode Polled command 60 Mode Status command 62 Mode Stream command 64 modes operating 18 pen 40, 71, 72 status 62 MP (Mode Point) command 59 MQ (Mode Polled) command 60 MS (Mode Stream) command 64 MT (Mode Status) command 62 N negative response 21 Null command 65 number, filter 38 O OI (Output Identity) command 66 operating modes defini
Index Serial/SMT touchscreen cable connector 91 TouchPen connectors 103 PL (Parameter Lock) command 68 PO (Pen Only) command 71 point mode 59 polled mode 60 positive response 21 power requirements Daughterboard controller 107, 111 PC Bus controller 95 Serial/SMT controller 90 TouchPen controller 102 power-up sequence 19 Ppdsb (Parameter Set) command 69 proximity bit 37, 51 Q query mode 60 R R (Reset) command 74 rate See communication rate raw data calibration 36 format 48 RD (Restore Defaults) command 75
Touch Controllers Reference Guide T tablet format 50 targets, calibration 28 technical specifications See specifications technical support 8 telephone support 8 temperature Daughterboard controller 107 PC Bus controller 95 Serial/SMT controller 90 TouchPen controller 102 terminator character 20 touch feel, adjusting 77 touch pen See pen touch state bit 37, 51 TouchPen controller component layout 104 connectors and I/0 signals 103 diagnostics 103 specifications 102 touchscreen cable 91, 96 transmit da
MicroTouch Systems, Inc. Corporate Headquarters UNITED STATES 978-659-9000, Fax 978-659-9100 World Wide Web: http://www.microtouch.com E-Mail: touch@microtouch.com FACTURA KIOSKS, a division of MicroTouch Systems, Inc.
