MSR110D Programmer’s Manual UDN PM008 Rev. D
Section 3 -- Technical Specification 2002/3/19
Page 10
Uniform Industrial Corp.
Proprietary and Confidential
Total 44 pages
Protocol 0
In Protocol 0, all characters are transmitted and received using exactly the characters listed in section 4. There are
no headers and Block Check Characters (BCC). Protocol 0 presumes no transmission errors. If the host detects an
error, it may request a retransmission.
Table 3-3. Example for Protocol 0
Protocol 1
In Protocol 1, all messages are preceded by the ASCII character <STX> and terminated with the ASCII character
<ETX>, followed by a one byte <BCC>. <BCC> is an XOR of the 7 data bits, excluding parity, of each character
in the entire message, including <STX>.
Format: <STX><MESSAGE><ETX><BCC>
where STX=02Hex and ETX=03Hex.
Table 3-4. Example for Protocol 1
Protocol 2
In Protocol 2, all messages are preceded by the ASCII character <SOH>, followed by a one byte reader address,
one byte character count and terminated with a one byte <BCC>. The <BCC> is an XOR of the characters (8 bits)
in the entire message, including <SOH>.
Format: <SOH><ADDRESS><00Hex><COUNT><MESSAGE><BCC>
or
<SOH><ADDRESS><00Hex><00Hex><MESSAGE><EOT><BCC>
where STX=02Hex and ETX=03Hex.
Table 3-5. Example for Protocol 2
Host Command
Reader Response
Comment
01h 00h 00h 01h 50h 50h
Ready to read
01h 00h 00h 01h 5Eh 5Eh
Reader ACK
The <ADDRESS> field is for a multi-reader system. This function is not currently supported. The recommended
value for this field is NULL (00Hex), however, any value will work.
Host Command Reader Response
Comment
P
Ready to read
^
Reader
ACK
Host Command Reader Response
Comment
02h 50h 03h 51h
Ready to read
02h 5Eh 03h 5Fh
Reader ACK