Intermec Trakker Antares 2460, User Manual

Page: 76 / 291

TRAKKER Antares 246X Stationary Terminal User’s Manual nugget
39
4-18
To set up the DCS 300
•
Configure a peer-to-peer destination name for the host application. Create a
transaction ID, $NGCFGRSP, that will be routed to this destination name. The
server uses the transaction ID to route responses from the 2461 back to the host
application. $NGCFGRSP is a special transaction ID that the server uses to forward
configuration response data from a terminal.
All configuration responses will be routed with the $NGCFGRSP transaction ID.
The server cannot keep track of multiple applications sending reader or
configuration commands. If you have two host applications sending reader or
configuration commands, they must both be configured to receive the
$NGCFGRSP transactions, and therefore both will receive all responses from all
2461 terminals.
To set up the host computer
•
Verify that you can communicate with the DCS 300.
To set up the application
•
Prepare and write a host application that can communicate with the server and send
transactions to and receive transactions from the 2461 in this format:
transaction header TMF field configuration command
where:
transaction header is a 96-byte field containing the message number, date
and time, source application ID, destinations
application ID, transaction ID, and other information.
You must set the system message (SYS$MSG) flag to E
in the transaction header. For help, see the DCS 300
Technical Reference Manual.
TMF field is a 2-byte field containing one of these values:
CG
Configuration Get request sent from the host
application.
Cg
Configuration Get response sent from the 2461
to the host.
CS
Configuration Set request sent from the host
application.
Cs Configuration Set response sent from the 2461
to the host.