Reader Response; No Checksum; Last Byte Before Footer Is Xor Of Bytes - Cognex DataMan Communications And Programming Manual

Commands
Short names specifying an action. A commonly used command is GET or SET followed by a Parameter and Value.
Parameters
Short names specifying a device setting. Parameter names are organized with a group of similar commands with one
level of structural organization separated by a period ('.').
Arguments
Boolean: ON or OFF
Integer: 123456
String: ASCII text string enclosed by quotes (").The string content is passed to a function to translate the string to the final
format. The following characters must be backslash escaped: quote (\"), backslash (\\), pipe (\|), tab (\t), CR(\r), LF (\n).
Footer
The footer is a carriage return and linefeed (noted as \CR\LF or \r\n).

Reader Response

The reader will have one of several response formats. The choice of response format is configured using the SET
COM.DMCC-RESPONSE command.
Silent: (0, Default) No response will be sent from the reader. Invalid commands are ignored without feedback. Command
responses are sent in space delimited ASCII text without a header or footer.
Extended: (1) The reader responds with a header data footer block similar to the command format.
Note: While the reader can process a stream of DMCC commands, it is typically more robust to either wait for a
response, or insert a delay between consecutive commands.
||checksum:command-id[status]
checksum
The response uses the same checksum format as the command sent to the reader.

0: no checksum

1: last byte before footer is XOR of bytes

command-id
The command-id sent to the reader is returned in the response header.
status
An integer in ASCII text format.
0: no error
1: reader initiated read-string
100: unidentified error
101: command invalid
102: parameter invalid
103: checksum incorrect
104: parameter rejected/altered due to reader state
105: reader unavailable (offline)
Examples
Command Silent Response Extended Response
DataMan Application Development
Description
19