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
10
Example #5 - Two-Wire Interface (separate network hardware):
Example #5 is conceptually similar to example #4. The difference here is that separate networks are created by providing each local
area network (LAN) with its own network switch. Therefore, traffic segmentation is physical rather than logical. Example #5 also pro-
vides an additional level of fault tolerance, although at the expense of additional network hardware. The figure shows a separate net-
work switch for QSControl.net traffic and a separate network switch for CobraNet audio traffic. All of the previous comments regarding
network expansion still apply.