Russound CAS44 Manual
Hide thumbs Also See for CAS44:

Advertisement

Quick Links

Russound Controllers
RNET™ Protocol & Specifications
RS-232 Communication
Document version 1.00.01
1

Advertisement

Table of Contents
loading

Summary of Contents for Russound CAS44

  • Page 1 Russound Controllers RNET™ Protocol & Specifications RS-232 Communication Document version 1.00.01...
  • Page 2 Quick Reference Guide Feature CAS44 CAA66 CAM6.6 CAV6.6 Keypad Events Source Control Events Set Zone On/Off Set All Zones On Set All Zones Off Zone Source Zone Volume Bass Treble Loudness Balance Turn On Volume Background Color Do Not Disturb...
  • Page 3 INTRODUCTION............................5 OVERVIEW..............................5 COM PORT ..............................5 COM S ............................ 5 ETTINGS ......................... 5 ONNECTOR RNET™ MESSAGE PACKET FORMAT....................7 ..........................7 ESSAGE EADER 4.1.1 Start of Message Character......................7 4.1.2 Target Device ID ..........................7 4.1.2.1 Target Controller ID..........................7 4.1.2.2 Target Zone (Port) ID..........................
  • Page 4 EEDBACK ................34 EADING OURCE ROADCAST ISPLAY EEDBACK ........... 35 EADING ULTI IELD ROADCAST ISPLAY EEDBACK ESSAGES USING THE ACKNOWLEDGE MESSAGE (HANDSHAKING) ............35 ASCII CHARACTER SET TO HEX CONVERSION CHART .............. 37 RUSSOUND CONTROLLERS RS-232 HEX CODE LISTING.............. 38...
  • Page 5: Com Settings

    1 Introduction This document describes how to control and interpret data from Russound controllers. Remote access is provided through the RS-232 serial port found on the front (CAV only) or rear of the controller using the following RNET™ communications protocol. It is assumed that the reader is familiar with the features and operation of the controller being used.
  • Page 7 0x7F can be used to send messages to all devices in the system. The Russound RNET™ system provides support for up to 6 connected controllers for a maximum of 36 separate zones. When a multi-controller system is configured, each controller is given a unique controller ID through the programming procedure.
  • Page 8 All of the messages described in this document can be sent to any of the controllers in the system by simply changing the Target Controller ID to match the controller you would like to send the message to. The following examples show the Volume Up command being sent to the same zone (Zone 1) but on different controllers using Keypad Event messages: Byte # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Value F0 00 00 7F 00 01 70 05 02 02 00 00 7F 00 00 00 00 00 01 7C F7...
  • Page 9 Reserved Targets all Keypads on a particular zone or all Sources for connected Peripheral Devices A special ID used by Keypads when they are requesting an ID (Keypad ID) from the Controller This message is a Source Broadcast Display Feedback message All other keypad IDs have not been formally assigned so they can be used as needed.
  • Page 10: Message Body

    In some cases, setting parameter values can be done in two ways. A Set Data message can be sent directly to the parameter, or an Event message can be sent to trigger the Controller to set the value instead. Event messages are a little easier to use, and may trigger other desired results (such as updating Keypad displays, updating related parameters, etc…) where a Set Data message may not.
  • Page 11 End of message character 4.2.2 Event Messages Event Messages trigger a system response that may set a parameter value, update displays, etc… Event Messages are a little easier to use then Data Messages and may trigger other desired results (such as updating Keypad displays, updating related parameters, etc…) where a Set Data message may not.
  • Page 12: End Of Message Character

    Step #3 - This value is then AND-ed with the HEX value 0x007F (7F is the highest BIN value for 7 bits = 1111111). The Checksum itself and the End of Message Character are not included in the calculation. Only the low 7 bits are used so overflow is discarded: Example - 0x02D9 AND 0x007F = 0x59 = Checksum 4.3.2 End of Message Character The End of Message Character (0xF7) is the special HEX value that indicates the end of the...
  • Page 13 Buttons and Keycodes This section describes how to send various events associated with the Buttons found on the keypads and/or the IR remote The method for transmitting these button events falls into two categories: -Keypad Events: The Keypad Events are the events that the keypad is capable of sending. -Source Control Events: All others (Source Control Events) are only available via the IR Remote.
  • Page 14 Here is a break out of the Zone1, Volume Up message (using above example of Keypad Event) Value Field Description Start of Message Target Controller ID Controller 1 Target Zone ID Target Keypad ID The Controller itself Source Controller ID Source Zone ID Zone affected Source Keypad ID...
  • Page 15 “5” Button “6” Button “7” Button “8” Button “9” Button “0” Button Volume Up Volume Down Mute (for zone, not source) Channel Up Channel Down Power Enter Previous Channel TV/Video TV/VCR TV/DVD TV/LD Input TV/DSS Play Stop Search Forward Search Rewind Pause Record Menu...
  • Page 16 Disk Plus 10 Open/Close Random Track Forward Track Reverse Surround On/Off Surround Mode Surround Up Surround Down PIP Move PIP Swap Program Sleep Bright Close Open Stop 2 AM/FM Disk Up Disk Down Info...
  • Page 17 Here are some examples of some Source Control Events: Zone 1, Menu F0 00 00 7F 00 00 70 05 02 02 00 00 F1 40 00 00 00 20 00 01 4E F7 Zone 2, Mute F0 00 00 7F 00 01 70 05 02 02 00 00 F1 40 00 00 00 0D 00 01 3C F7 Zone 3, Record F0 00 00 7F 00 02 70 05 02 02 00 00 F1 40 00 00 00 1F 00 01 49 F7 Here is a break out of the Zone1, Menu message used in the above example:...
  • Page 18 6 Using Request Messages The Request Data message is used to receive parameter data from the Controller. This may be used to receive Zone Power State, Volume Level, etc. When a Request Data message is sent to the Controller, a Set Data message is generated by the Controller and sent back to the Request Message sender.
  • Page 19 7 Zones This section will provide information in regards to messages that only apply to Zone commands. This will include controlling the Zones as well as sending Request messages to “Get” the State of the Zones. Zero-based values are used for the Zone Numbers (i.e. 0 = 1, 1 = 2, and 2 = 3 etc…) 7.1 ON/OFF The simplest way to explicitly turn a Zone On or turn a Zone Off is by using the discrete Zone On/Off Event.
  • Page 20: Source Select

    the Product Manual for instructions on programming each zone for “System On Enable” or “System On Disable”. Turn All Zones ON or OFF using a discrete message (all zones enabled in programming). Byte # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 Value F0 7E 00 7F 00 00 70 05 02 02 00 00 F1 22 00 00 ## 00 00 01 xx F7 xx = checksum Byte #17 = 0x00 (all off) or 0x01(all on)
  • Page 21: Set Volume

    7.3 Volume Select The simplest way to explicitly select a Volume level per Zone is by using the discrete Volume Select Event. The Even Timestamp fields determine the Volume Level. The Event Data fields determine the Zone affected by the Volume being selected. Refer to the Buttons section for information on stepping through Volume levels (“Volume Up and Volume Down commands found under UNO Keypad Events).
  • Page 22 7.4 Bass Bass levels displayed on keypads range in value from -10 through +10. These Bess levels are represented in Decimal when using RS-232 messages ranging in value from 0 - 20. In the actual Data message the HEX value is used which would range in value from 0x00 – 0x14. This means (0x00 = 0 = -10, 0x01 = 1 = -9, 0x02 = 2 = -8 …...
  • Page 23 7.5 Treble Treble levels displayed on keypads range in value from -10 through +10. These Treble levels are represented in Decimal when using RS-232 messages ranging in value from 0 - 20. In the actual Data message the HEX value is used which would range in value from 0x00 – 0x14. This means (0x00 = 0 = -10, 0x01 = 1 = -9, 0x02 = 2 = -8 …...
  • Page 24 7.6 Loudness Loudness is displayed on keypads as “On” or “Off”. Loudness can be toggled On or Off with a Plus or Minus command. There can also be a discrete On or Off command selected. NOTE: The keypad displays will not automatically update for this change. 7.6.1 Loudness Toggle On/Off The following example shows how to toggle the Loudness “On”...
  • Page 25: Set Balance

    7.7 Balance Balance levels displayed on keypads range in value from “Left 10” to “Center” to “Right 10”. These Balance levels are represented in Decimal when using RS-232 messages ranging in value from 0 - 20. In the actual Data message the HEX value is used which would range in value from 0x00 –...
  • Page 26: Turn On Volume

    7.8 Turn On Volume Turn On Volume levels displayed on keypads range in value from 0 – 100 in steps of 2 (i.e. 0, 2, 4 … 100). These Turn On Volume levels are represented in Decimal when using RS-232 messages ranging in value from 0 - 50.
  • Page 27: Set Background Color

    7.9 Background Color Background Color is displayed on keypads as “Amber”, “Green”, or “Off”. The Background Color can be toggled through these selections with a Plus or Minus command. There can also be a discrete command selected for each choice. NOTE: The keypad displays WILL automatically update for this selection.
  • Page 28: Do Not Disturb

    7.10 Do Not Disturb Do Not Disturb is displayed on keypads as “On” or “Off”. DND can be toggled On or Off with a Plus or Minus command. There can also be a discrete On or Off command selected. 7.10.1 Do Not Disturb On/Off Toggle The following example shows how to toggle Do Not Disturb “On”...
  • Page 29: Party Mode

    7.11 Party Mode Party Mode is displayed on keypads as “On”, “Off”, or “Master”. Party Mode can be toggled to “On” or “Master” with the Plus command. The Minus command will toggle Party Mode “Off”. There can also be a discrete On, Off, or Master command sent. 7.11.1Party Mode On, Party Mode Master, and Party Mode Off NOTE: If Party Mode is Off, then Plus will issue a Master command.
  • Page 30 Byte #30 = Current Party Mode state (0x00 = OFF, 0x01 = ON, 0x02 = Master)* Byte #31 = Current Do Not Disturb state (0x00 = OFF, 0x01 = ON )* *NOTE: Unsupported Features, information not available for CAS44 and CAA66 controllers...
  • Page 31 8 Displaying a String Since the keypad contains a text display, we’ve provided a message that will allow you to send text messages to All Keypads simultaneously or a Specific Keypad individually. “Alignment” – When sending a message to display text on a Keypad the first Data byte sets your Alignment (0x00 = Centered, 0x01 = Left justified).
  • Page 33: Display Messages

    (e.g., If the current frequency of a Russound tuner is “102.7 MHz FM”, sending the “Frequency Up” command will trigger the Tuner to send a Display message back to the sender to update the frequency Display to "102.9 MHz FM").
  • Page 34 Reading Source Broadcast Display Feedback This section describes how to read Source Broadcast Display Feedback messages. These Feedback messages are sent to update all devices monitoring a given Source’s status. These messages may be sent as a direct result of a sent command or as a general update. The Display Feedback message is sent with the source number of the Source attached.
  • Page 35 This example shows sending a Frequency Up (Tune Up) event to a Russound Tuner: In this case the event priority byte is set to 0x00 (high) and the sender Keypad ID is 0x60. This means that...
  • Page 36 Byte # 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Value F0 00 7D 00 00 00 60 05 02 01 00 02 01 00 2F 00 70 00 00 00 00 0C F7 Byte #4 = Source Number - 1 (Zero-based) Byte #7 = Sender Keypad ID - 0x60 (0x60 indicates that this message requires a handshake message if the event is high priority)
  • Page 37 11 ASCII Character Set to HEX Conversion Chart...
  • Page 38 12 Russound Controllers RS-232 Hex Code Listing...

This manual is also suitable for:

Caa66Cam6.6Cav6.6

Table of Contents