NCR RealScan 7802, User Manual

Page: 80 / 94

NCR RealScan 7802 Price Verifier User Guide
06/03 497-0425530 Release E 80 of 94
Event
A client can support up to 32 application specific events and can report the beginning
and end of each event with a 100
th
second timer (which need not be supported).
Events are mapped into a 32-bit word, in standard network order. Clients may permit
the host to enable and disable individual events, or to select reports only for starting
or ending events. The packet header for events from UnitID “Unit1” is:
0 1 2 3 4 5 6 7
Byte #
0 0 0 26 E V N T
Immediately following the header is: the 32-bit map of events that have started since
the last report, the 32-bit map of events that have ended since the last report, a 32-bit
timer value and a NUL terminated string that is the sending unit’s UnitID. The bytes
following the header if event zero started and event one ended at time 5 from UNIT1
would be:
0 0 0 1 0 0 0 2 0 0 0 5 85 78 73 84 49 0.
Client Requirements
Capabilities
The following capabilities must be supported by a client:
Timeout
Changing the client’s protocol timeout value is supported.
SendUnitID
Sending the unit’s ID can be enabled and disabled.
TrivialComm
Controls the default communication method used for queries.
Modes
The following modes must be supported:
Timeout
Hundredths of a second represented in a 32-bit value. This specifies the amount of
time that a client waits, after sending an initial query, before it terminates the
connection to the server and displays an error message (if no other response has been
received). The default is 300 (3 seconds).
TrivialComm
Controls the communication method used for queries. The default is TRUE. The
response to a trivial–mode query need not be in trivial–mode.
SendUnitID
Controls the inclusion of the Unit ID in a trivial mode query. The default is TRUE.
SendError
Controls the sending of error reports. The default is FALSE.
SendResponse
Controls the sending of responses to mode set commands. The default is FALSE.