RS232 Protocol
1
Rotel RCD-1572
RS232 ASCII Controller Command List
The RCD-1572 supports an ASCII based RS232 protocol. The RS232 hardware
does not support flow control so care needs to be take when sending and receiving data
to avoid packet loss.
All commands sent to the attached Rotel device must have a terminating “!” character.
Example Command: power_on!
Note: Do not include any spaces in the command, and do not include a carriage return
or line feed after the command, only the “!” terminating character.
Status information from the attached Rotel product with either have a terminating “!” or
“$” character, depending on the protocol revision (see update below), or a byte count
for variable length text data that may include a “!” in the returned message. It is up to
the sending/receiving control application to properly parse and process the packets.
Note: The byte count only includes the text data and not the length or “,” character.
Important Protocol Revision
As of software V2.33, the RS232 protocol was updated with changes to some
commands as well as all feedback strings. This change will impact existing control
systems so any connected control systems should be updated to utilize the new protocol
before updating the software in the RCD-1572.
The current commands and feedback strings are documented in Sections 1 & 2, while
the legacy commands for older software is documented in Sections 3 & 4. A summary
and list of specific changes is also provided in Appendix A.
Connection Settings
Baud Rate
Parity
Valid Data Bits
Stop Bit Value
Handshaking
Data Type
57600
N
8
1
None
String
Communication Protocol
Command and response messages are included on the following pages.
Automatic display update information can be enabled/disabled using the
“display_update_auto” and “display_update_manual” commands.
In automatic mode each time the display changes the new display line(s) will be sent.
In manual mode the display updates must be requested each time a refresh of the
display information is desired.
Date
Version
Update Description
July 19, 2017
1.00
Original Specification
January 6, 2019
2.00
Add V2.0 specification and details on change