Specifications

365
Protocol
If the message string is longer than can be fit into one 256 character block the following
method is used.
-
Logoff
M2x00 sends:
(Displayed) AED sends:
Notes
— <STX><pager#><CR>
<first portion of message>
<US><checksum><CR>
The page starts off similar to the above example. As
the entire message can not be fit within the block it is
“broken” at some point that will fit. No <CR> is
appended at that point, as the message field is not
done, and a <US> byte is used instead of <ETX>.
The <US> byte indicates that there is more of the
message field to come.
reply — The M2x00 will respond with one of the four replies
described earlier. These are <ACK>, <NAK>,
<RS>, or <ESC><EOT>
—<STX>
<remainder of message><CR>
<ETX><checksum><CR>
If the remainder of the message will fit within a
block this form is used. The remainder of the
message must be 250 characters or less to fit within a
continuation block. Note the end of the message is
marked with a <CR>, and that there is no pager#
field after the <STX> byte.
If the remainder of the message would not fit in a
single block then the following sequence is used.
—<STX>
<message fragment>
<US><checksum><CR>
This block will contain up to 250 characters of the
message. This may be repeated as much as needed
until the remainder of the message will fit within a
single block.
Note that the M2x00 currently will not accept a
message longer than 500 characters.
—<STX>
<remainder of message><CR>
<ETX><checksum><CR>
Once again the message is terminated with a <CR>,
and the <ETX> byte is used to indicate that this is
the last block of the message.
reply — The M2x00 will respond with one of the four replies
described earlier. These are <ACK>, <NAK>,
<RS>, or <ESC><EOT>