Specifications

CARROLL TOUCH Chapter 5 - Smart-Frame Protocol II
Touch System Programmer’s Guide 5-13
The touch system responds with the following report:
E0 05 FF 94 01 02 03 FF
The first FF byte is Cmderr and indicates that there is no command
defined with an opcode value of 94H. Note that the parameters that
were sent with the invalid command packet (01 02 03) are returned
along with the invalid command number.
Invalid Parameter Value
When the parameter number is out of range, an SFP-II report packet is
sent with Cmderr containing a number that points to the first byte of the
parameter that was in error. If there were multiple parameters with
errors, only the first one is indicated.
If the host sends the SetTouchModes (20H) command as follows:
66 04 20 01 04 03 FF
The touch system responds with the following report:
E0 05 02 20 01 04 03 FF
The 02 byte is Cmderr and indicates that the second parameter is out of
range. (The value of 04 for TouchStateReportType is not among the
valid values of 01, 02, or 03.) Since the 04 byte is out of range, the error
results and is reported in Cmderr. The third parameter is also out of
range. This parameter is the TouchReportingMode parameter, which
has valid values of 00, 01, and 02. The 03 byte is out of range.
However, this is not reported to the host because Cmderr only reports
the first invalid parameter if multiple parameters are invalid.
Unsupported Feature
When a parameter value requests an option that the particular firmware
implementation does not support, an SFP-II report packet is sent with
Cmderr containing a number that points to the first byte of the
parameter that was in error. If there were multiple parameters with
errors, only the first one is indicated.
Suppose the host sends the SetTouchModes (20H) command as follows
to (1) enable touch detection; (2) set the TouchStateReportType to the
Multi Touch State Report; and (3) set the Touch Reporting Mode to
Continuous: