NCR RealScan 7802, User Manual

Page: 78 / 94

NCR RealScan 7802 Price Verifier User Guide
06/03 497-0425530 Release E 78 of 94
Mode Set/Query
The name of the mode and its value are in a token/value string following the header.
If the mode name alone is in the string, it is a query. Mode names are case–
insensitive. The header for a SendUnitID query would be:
0 1 2 3 4 5 6 7
Byte #
0 0 0 19 M D S Q
The query string “SENDUNITID” and a terminating <NUL> immediately follow the
header. To set SendUnitID, the string would be (e.g.) “SENDUNITID = ON”, and
byte 3 would be 22 instead of 19.
Mode Response
If the mode being queried of set is known, a response is sent. The name of the mode
and its value is a string in token/value format following the header. The header for a
SendUnitID response might be:
0 1 2 3 4 5 6 7
Byte #
0 0 0 22 M O D R
The response string “SENDUNITID = ON” and a terminating <NUL> immediately
follow the header. There can be white space on either or both sides of the equals sign.
If the mode query is a zero–length string, the RealScan 7802 responds with a
<CR><LF> separated list of all supported modes and their types in the form
“MODENAME = TYPE,SIZE” where TYPE is BOOLEAN, NUMBER, or STRING, and
SIZE is the number of bytes in the STRING and only appears for STRING. If the
mode query is the single–character string “*”, the RealScan 7802 responds with a
<CR><LF> separated list of all supported modes and their current values.
Error Report
Error reports are primarily intended for debugging purposes. If enabled, error
reports are sent if, for example, the host queries a capability that the client does not
accept. Such error strings are in the format of a number possibly followed by white
space and explanatory text. There is no assignment of numbers to specific errors, but
the value zero should be reserved for non-error conditions. An “OK” error response
could be:
0 1 2 3 4 5 6 7
Byte #
0 0 0 13 E R R _
The response string “0 OK” and a terminating <NUL> immediately follow the
header.