This article includes information for custom controller setups on Elo controllers.

Sending SmartSet Commands to Alter the Touch Data Format
Modern controllers can be programmed through a serial connection to a PC's RS232 serial interface (COM port) by sending simple alpha-numeric command strings. Doing so will change the format of the touch data. Other changes can also be made, such as reversing one or both of the touch axes. The command strings must be ASCII text. Hyper Terminal, a relatively simple, widely available Windows accessory program, can be used to send the commands.

A set of ASCII text command files is available to perform setup, older data format emulations and other changes that are most commonly requested. Commands are sent one at a time. Note that the Save_to_NVRAM command must be sent after all other commands have been sent. Sending commands changes the present configuration of the controller, but the changes are only permanently saved in the controller when the Save command is sent. Failure to send the Save command will result in all changes being lost when power is removed from the controller.

Limitations and Requirements
•    This document applies only to Elo AccuTouch, IntelliTouch and Surface Capacitive SmartSet touch controllers that have a serial interface. The 2216, 2700, 2701 and 5020 controllers run 9600 baud ONLY – the baud rate cannot be changed.
•    This information is intended as development information for use by trained professionals, and is not a procedure or statement of work. Elo does not warrant or support this information and cannot be held liable for accidental or intentional misuse of this information. Use this information at your own risk.
•    Hyper Terminal must have an available COM port to send commands, so the Elo Windows driver must be removed or disabled in order to release the COM port.
•    To remove the Elo driver:

•    Controllers that have been set to emulate older data formats will no longer work with the Elo Windows drivers, as these drivers only support the SmartSet data format.
•    In order to send commands to the touchcontroller, the touchmonitor's serial (9 pin female) output must be connected to a PC's serial (COM) port (9 pin male) and the COM port number must be known so you can specify it in Hyper Terminal.

Altering the Touch Data Format: Procedure
If you are not familiar enough with computers to follow the procedure steps below, you should find or engage the services of someone who has familiarity with Windows-based computers.

•    First, download the commands zip file: CustomControllerCommands.zip
•    Next, unzip the file to a known location
o    To determine which commands you need, see section: Identifying Data Formats and Operating Modes.
•    Next, start Hyper Terminal.
•    Click Start, All Programs, Accessories, Communications, Hyper Terminal.
o    In the "New Connection" dialog box, type Elo or a name of your choice in the Name box and click OK.

•    Next, select the COM port from the "Connect using" drop-down at the bottom of the Connect To window, then OK.
•    Select 9600 from the bits per second drop-down in the Port Settings window, then OK.
•    The Hyper Terminal window opens.
•    Click Transfer in the top menu, then select Send Text File (NOTE: "send TEXT file", not "send file").
•    Use the Look In drop-down to navigate to the location of the previously saved command text files, then double-click the command file to send.
•    A short character string should appear at the top of the window; it will be cryptic and meaningless, but will indicate a response from the controller.

•    Additional commands may be sent by selecting Send Text File from the Transfer menu (it may be necessary to restart Hyper Terminal for each command), then double-clicking the command file to send.
•    Be sure to send the Save command last, to save the new settings in the controller.
NOTE: If the Save command is not sent, all changes will be lost when power is removed from the controller.

Identifying Data Formats and Operating Modes
Comdump.exe, available on the Driver and File Downloads page , may be used to view the touch data stream. The appearance of the data stream gives clues to the format of the data. Comdump may be used with an existing older controller to determine its data format and characteristics, and thus to determine which command text files need to be sent to a more modern controller to get it to emulate the older data format. Comdump may also be used to check the format of a modern controller that has been sent commands, to see if the desired format has been achieved.

Important Notes
• Comdump is a DOS application, which means it has to be run from a command line. Because of DOS navigation logistics, it is important that comdump.exe be saved to the root of the hard drive (in Windows, save to the icon of the C: drive, not one of the folders on the drive).
• In order to use comdump, the COM port that the touchmonitor is connected to must be available for use. That means that the Elo driver needs to be removed or disabled and any Hyper Terminal session must be disconnected or closed.
• Comdump needs to use either COM1 or COM2.

If you are running a Hyper Terminal session you can click the Disconnect icon (icon of a phone with the receiver off the hook) to allow use of the comdump program. To use the Hyper Terminal session again after running comdump, hit the Esc key on the keyboard to terminate comdump, then Alt-Tab to Hyper Terminal, then select Send Text File from the Hyper Terminal Transfer menu (no need to reconnect – it will be done automatically).

Running comdump.exe
Get to a command prompt
• Start, All Programs, Accessories, Command Prompt.

Get to the root directory
• Type cd\ and hit the Enter key.

Start comdump
• For a COM1 connection, type comdump 1 and hit the Enter key.
• For a COM2 connection, type comdump 2 and hit the Enter key.

The comdump window should open. When you touch the screen, data should scroll in the data area. You will then examine the data to look for a repeating pattern, indicating packets of data. The data packets should fit one of the formats below:

SmartSet binary data packet:
• the first two bytes are always [55] [54].
• data repeats every 10 bytes.
• this format is very distinctive and should be easy to see.
• this is the Elo modern data format.
• 4002 binary data packet:
• Data repeats every 6 bytes.
• Early 1990's data format.
• 140 binary data packet:
• Data repeats every 4 bytes.
• 1980's data format.

If the data does not fit any of the above formats (11, 13 or 16 byte data packets), hit the M key on the keyboard to toggle to ASCII data display, then touch the screen again.
• SmartSet ASCII data packet (16 bytes if viewed in hex format):
• three columns of 4-digit coordinates.
• third column does not exceed 255.
• 4002 ASCII data packet (16 bytes if viewed in hex format):
• three columns of 4-digit coordinates.
• third column does not exceed 15.
• 140 ASCII data packet (11 bytes if viewed in hex format):
• two columns of 4-digit coordinates.
• 140 ASCII data with touch flags packet (13 bytes if viewed in hex format):
• Should display two columns of 4-digit coordinates plus one with T or U.
• T = touch, U = untouch.

In general, data that does not fit any of the formats above is an indication of a non-Elo touch controller.