Serial Communication Protocol
34
Communication Protocol
Serial Communication Protocol
The serial communication between a computer (host) and the M6e is based on a
synchronized command-response/master-slave mechanism. Whenever the host sends a
message to the reader, it cannot send another message until after it receives a response.
The reader never initiates a communication session; only the host initiates a
communication session.
This protocol allows for each command to have its own timeout because some
commands require more time to execute than others. The host must manage retries, if
necessary. The host must keep track of the state of the intended reader if it reissues a
command.
Host-to-Reader Communication
Host-to-reader communication is packetized according to the following diagram. The
reader can only accept one command at a time, and commands are executed serially, so
the host waits for a reader-to-host response before issuing another host-to-reader
command packet.
Header
Data Length
Command
Data
CRC-16 Checksum
Hdr
Len Cmd
CRC Hi
CRC LO
I
1 byte
1 byte
1 byte
0 to
250 bytes
2 bytes
Summary of Contents for Mercury6e M6e-30dBm
Page 1: ...M6e 31 5dBm Hardware Guide For M6e Firmware Ver 1 7 and later ...
Page 4: ...4 ...
Page 14: ...14 Mercury6e Introduction ...
Page 26: ...Assembly Information 26 Hardware Overview M6e Mechanical Drawing ...
Page 52: ...Save and Restore Configuration 52 Functionality of the Mercury6e ...
Page 78: ...Demo Application 78 Appendix B Getting Started Devkit ...