User's Manual
Table Of Contents
- Health Limits
- Contents
- Before You Begin
- Developing the Installation Site Plan
- Installing and Configuring the MPI 6000
- Lane Tuning Guidelines
- Optimizing MPI 6000 Reader System Performance
- General Software Information
- Configuration Commands and Responses
- Configuring the MPI 6000
- Required Commands to Set Up MPI 6000 Reader
- System Interface Command Group Commands
- System Identify
- Set Communications Baud Rate
- Get Communications Baud Rate
- Set Time and Date
- Get Time and Date
- Firmware Download
- Reset Reader
- Get Stored Tag Response Message
- Get Number of Stored Tag Response Messages
- Delete All Stored Tag Response Messages
- Get System Startup Status
- Get Lane Controller Interface Status
- Get System Interface Status
- Get DigBrd Hdwr Remote Inventory
- Get DigBrd CPU Boot Fmwr Remote Inventory
- Get DigBrd CPU Appl Fmwr Remote Inventory
- Get DigBrd FPGA UDP/IP Core Fmwr Remote Inventory
- Get UDP/IP Core Lane Controller Parameters
- Set UDP/IP Core IP Address
- Get UDP/IP Core IP Address
- Get UDP/IP Core Port Number
- Configuring the MPI 6000
- Tag Command Processing
- System Diagnostics and Preventive Maintenance
- Acronyms and Glossary
- Block Diagrams
- System Technical Specifications
- Hardware Interfaces

MPI 6000 Multi-Protocol Reader System Guide
6-10
Software Flow Control Message
The MPI 6000 after receiving command request messages from the host optionally
sends software flow control messages to the host as required for system operation.
The host optionally sends software flow control messages to the MPI 6000 as required
for host operation.
The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications
software flow control message shown here:
<len> <msgSeqNum> <cmd> <cmdSeqNum> <resp> <checksum>
where
<len> = length, a word that specifies the number of bytes in the entire message.
<msgSeqNum> = message sequence number, a byte that specifies the message
sequence number of the message. See the software communication sequence number
controls section for details.
<cmd> = command, a word that specifies the system command. See the command
sections for details.
<cmdSeqNum> - command sequence number, a byte that specifies the command
sequence number of the message. See the software communication sequence number
controls section for details.
<resp> = response, a word that specifies the system response. See the response sec-
tions for details.
<checksum> = checksum, a byte that specifies the checksum of the message.
Unsolicited Status Message
The MPI 6000 sends unsolicited status messages to the host as required for system
operation.
The host and the MPI 6000 uses the following UDP/IP fast Ethernet communications
unsolicited status message shown here:
<len> <msgSeqNum> <cmd> <cmdSeqNum> <status> [<data>] <checksum>
where
<len> = length, a word that specifies the number of bytes in the entire message.
<msgSeqNum> = message sequence number, a byte that specifies the message
sequence number of the message. See the software communication sequence number
controls section for details.
<cmd> = command, a word that specifies the system command. See the command
sections for details.
<cmdSeqNum> = command sequence number, a byte that specifies the command
sequence number of the message. See the software communication sequence number
controls section for details.