Owner's Manual
Table Of Contents
- Getting Started
- Introduction - Networking the RAVE 522ua
- Why CobraNet Needs Special Treatment:
- Notes on Network Systems Design:
- Example #1 - QSControl.net X-over mode:
- RS-232 Communications Procedure:
- Example #2 - CobraNet X-over mode:
- Telnet Access
- QSControl Port
- CobraNet Port
- CobraNet Channel Density
- CobraNet Channel Resolution
- CobraNet Terms and Conditions
- 1 Minute Autosave Timer and Power Cycling
- Example #3 - Single Wire Interface:
- Network
- Configuration Memories
- Safe Mode Switch
- RS-232 Serial Port I/O Interface
- AC Power Cord
- CobraNet
- QSControl
- Analog Universal Audio Inputs
- Analog Outputs
- Omni In
- Logic Out
- To Install QSControl.net:
- To Uninstall QSControl.net:
- Front Panel Password Lockout
- Relay Out
- RS-232
- Example #4 - Two-Wire Interface (shared network hardware):
- Example #5 - Two-Wire Interface (separate network hardware):
- Rack Mounting
8
Example #3 - Single Wire Interface:
Here all QSControl.net and CobraNet traffic shares the same single CAT-5 cable between the RAVE 522ua and an unmanaged Ethernet
switch. The QSControl.net system manages traffic flow efficiently and reliably so that all audio and control data is delivered to its
appropriate destination anywhere on the network. This configuration works well when CobraNet audio deliveries are point to point.
Though the example shows only two RAVE/BASIS units, as many devices may be connected as there are available switch ports. All
units will be able to communicate simultaneously with the computer. All will have access to CobraNet audio. Switches can be con-
nected to other switches to build larger networks; all of the normal networking principles apply. (Note: there must be at least two
CobraNet devices, one source and one destination, online for any data to come out of the CobraNet port.)