Xicom XTU-400K, Operation And Installation Manual

Page: 122 / 189

MNC-0500-002 8 of 36 Revision H
Amplifier Communication and Protocol, Octagon ISA CPU
Printable vs. Non-Printable Protocols
Printable protocol facilitates teletype-style operations where users type in
messages and view the responses. There are two drawbacks to this
method:
1) Several responses contain bit flags (example: HPA Summary Status
Query). To force the resulting byte to be printable, bit 6 is conditionally set.
However, there is no guarantee that the resulting byte will not be a start or
stop character.
2) There is no provision for Xicom responses to directly indicate the
success or failure of a given message. Rather, the length of the response
can be checked to determine the presence or absence of a message-
rejected code.
Printable protocol drawbacks are remedied by the non-printable protocol.
Because start and stop bytes are non-printable, they cannot be confused
with message parameters, which are always printable. Also, different start
bytes are used to indicate whether a message was accepted or rejected.
For nearly all implementations, the non-printable protocol should be used.
If you send a message using the printable protocol, devices will respond
using the printable protocol. If you send a message using non-printable
protocol, devices will respond using the non-printable protocol. There are
no DIP switches to set, and there is no software to configure. Xicom
devices always respond in kind:
•
Printable and non-printable protocols differ only in the characters
used for start, stop, and check bytes. Refer to Table 3.
•
The "printable" protocol uses printable start and stop characters;
check bytes are generated using a method that produces printable
ASCII characters.
•
The "non-printable" protocol uses non-printable start and stop
bytes; its check byte algorithm can yield non-printable characters.
Refer to Table 4 and examples on page 11.