AR1000 SERIES RESISTIVE TOUCH SCREEN CONTROLLER
9.0 COMMANDS
9.1 Sending Commands
9.1.1 COMMAND SEND FORMAT
The controller supports application-specific
configuration commands as shown in Table 9-1, below.
TABLE 9-1: COMMAND SEND FORMAT
Byte #
Name
Value
1
Header
2
Size
3
Command
4
Data
:
Data
0x55
0x<>
0x<>
0x<>
0x<>
To ensure command communication is not interrupted
by touch activity, it is recommended that the controller
touch is disabled, prior to other commands. This can be
done as follows:
1. Send DISABLE_TOUCH command
2. Wait 50 ms
3. Send desired commands
4. Send ENABLE_TOUCH command
Description
Header (mark beginning of command packet)
Size, # of bytes following this byte
Command ID
Data, if applicable for the command
Data, if applicable for the command
9.1.2 COMMAND RESPONSE
A received command will be responded to as seen in
Table 9-2 below.
TABLE 9-2: COMMAND RESPONSE FORMAT
Byte #
Name
Value
Description
1
Header
2
Size
3
Status
4
Command
5
Data
:
Data
0x55
0x<>
0x<>
0x<>
0x<>
0x<>
Header (mark beginning of command packet)
Size, # of bytes following this byte
Status
Command ID
Data, if applicable for the command
Data, if applicable for the command
The “Status” value within the response packet should
be one of the following (See Table 9-3):
TABLE 9-3: COMMAND RESPONSE
STATUS VALUES
Status Value
Description
0x00
0x01
0x03
0x04
0xFC
Success
Command Unrecognized
Header Unrecognized
Command Time Out (exceeded ~100
ms)
Cancel Calibration mode
2009-2012 Microchip Technology Inc.
Preliminary
DS41393B-page 35