First. This driver is a member of the A/V Family. Command builder will have the command syntax.
Each Russound device in your system will appear as a unique AV Family member. This does not mean you need a serial connection to each device. You only need to specify the serial port in play for the PRIMARY RNet controller. It is assumed all the remaining RNet devices will be daisy chained to the primary controller.
You send commands to the various Russound devices using the normal AV command syntax. The driver will make sure all the commands are routed through the primary RNet controller.
Q: How do I configure my Russound Devices in Family Manager?
A: You add the AV device like all Family Devices. When you get to the column labeled "Network Address" you will enter the RNET Device number for the specific Russound device. If the device is the primary RNet controller you will specify the serial port being used in the "Port" column. If the device IS NOT the primary RNet device then set the port value to "RNET".
Please see the attached images as this will then make sense. The first image shows 3 Russound devices in play. The CAV6.6 Rnet device #2 is the primary RNet controller and it is communicating on COM3. The other 2 Russound devices are RNet slaves so their port values have been set to RNET.
Q: I've got my RNet device connected to a Global Cache serial port. How do I set that up in Family Manager?
A: See the second image. The "Network Address" field now contains two values. The IP Address of the GC device and the RNet device ID separated by a colon. i.e. 192.168.1.70:2. The "Port" then is assigned to the appropriate GC module.
Q: How are Uno Keypad Events handled?
A: The driver will automatically pick up the button presses coming from the Uno keypads. When a keypad event happens the driver will look for the existence of a system macro that handles the event. If the macro exists then the macro will automatically be fired. When the macro is executed it is passed two parameters. The first parameter is the Family Device ID for the device the keypad is attached to and the second parameter is the zone number that the keypad is located in. You can use these two values to drive conditional statements in the macros to perform the actions you need them to do. These system macros have very unique names and they cannot be changed. The following list defines the current set of event macro calls.
Code: Select all
Russound.Keypad.Setup|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Previous|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Next|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Plus|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Minus|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Source|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Power|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Stop|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Pause|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Fav1|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Fav2|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.Play|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.VolUp|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.VolUp.Pulse|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.VolDown|<<Family Device ID>>~<<Keypad Zone #>> Russound.Keypad.VolDown.Pulse|<<Family Device ID>>~<<Keypad Zone #>>
A: Yes! The MainLobby Sample Client Scenes and the sample iPad and Android web apps have all been updated to now include a sample scene that emulates a Uno keypad. The third image below shows the sample iPad scene for Russound control.
Now for the Caveats. I have a single CAV6.6 in my office so the driver has only been tested with the CAV. The driver has support for all the radio commands but I cannot test them here. This driver also replaces the V4 RussoundST2 driver that was recently released.