Table of Contents
Advertisement
GENERAL NOTES
The RS-485 protocol for third-party software control is text-based (ASCII string).
Commands are sent as simple character strings with terms separated by spaces and
completed with a carriage return character <CR> (ASCII code decimal 13 or hex 0x0D).
The general command form is:
<COMMAND> <PARAMETER> ... <PARAMETER><CR>
A single white space character must be included between a command name and each
parameter. However, it is allowed to add an arbitrary number of extra white spaces in-
between each field if desired (to get a better readability).
Furthermore, both command and string parameters parsing is case-insensitive.
When the device accepts a given command, it will respond with a string as the following:
ACK <COMMAND> <PARAMETER> ... <PARAMETER> <DATA><CR>
On the contrary, when a command is not accepted or if its execution fails for any reason
(e.g. the specified controller type does not exist or a given parameter value is out of
range), the device will respond with a string as the following:
NACK <COMMAND> <PARAMETER> ... <PARAMETER><CR>
In general, reply strings will be always formed by an acknowledge/not-acknowledge
string followed by an echo of the original command (comprising command parameters
too) plus an ending (optional) data field. This last field used to return some information
to the caller (e.g. the mute state of a channel) will commonly appear in reaction to "get"
commands while will not in reaction to "set" commands.
RS 485 CONTROL PORT SETUP
RS-485 control is generally made by using 3rd-party controllers such as certain AMX or
CRESTRON models or any RS-485 equipped remote controller device that can be adapted
to this protocol.
For experimental purposes, a terminal emulation software such as PUTTY or TERATERM
can be run on a PC instead.
In any case, set up the remote controller for:
Baud
Data Bits
Stop Bits
Parity
RS 485 SERIAL PORT PROTOCOL
38400
8
1
None
43
Advertisement
Table of Contents
