RAVE 520uz
8 input CobraNet Enabled Signal Processor
Hardware Manual
*TD-000201-00*
TD-000201-00 rev.A
Don’t want to read the entire manual? Just
want to dig right in? Go to page 18....
Introduction
The RAVE 520uz provides the digital audio transport and
The QSControl.net network can also be managed from a sin-
gle computer running both the client and the server. Once all
RAVE devices in a system are configured, a computer is no
longer required on that system’s network. All basic func-
tions of the RAVE 520uz continue to operate with or without
a control computer connected to the network.
signal processing needed to distribute audio throughout an
integrated functioning system. In conjunction with QSCon-
trol.net software, the RAVE 520uz enables the user to
design, test and deploy professional audio reinforcement
and distribution systems ranging in size from one to hun-
dreds of channels.
The configurable DSP engine provides all of the functions
necessary to handle the input portion of a signal chain, such
as delays, equalization, compression/limiting, etc. Audio
output is exclusively via CobraNet .
A standard Windows computer is the principle user-inter-
face for controlling the overall RAVE/QSControl system.
However, the RAVE 520uz also offers a front panel interface
for accessing critical functions.
Audio enters a RAVE 520uz either through analog universal
inputs (mic to line level with software-selectable +48V
phantom power) or from CobraNet source devices such as
QSC's line of RAVE digital audio routers. Any combination of
16 CobraNet channels (selected from up to 4 bundles of 32
channels) can be routed into the 24 x 24 DSP engine. Any or
all of the 24 DSP channels can also be routed to up to 32
CobraNet channels on the network.
A single QSControl.net server computer can support several
clients running QSC's latest Venue Manager software. Thus,
the sound system can be operated via several computers,
roaming wireless laptops, tablets, etc., all at the same time,
from anywhere a connection to the QSControl.net network
is available.
1- Power indicator
9- Mic/lineinputs
2- Diagnostic indicator
10- Relay outputs
3- Network status indicators
4- Signal presence/clip indicators
5- Multi-function push buttons
6- Display
7- Rotary select/accept knob
8- Safe Mode switch (recessed)
11- Logic outputs
12- Omni inputs
13- RS-232 port
14- Network status indicators
15- QSControl 10BaseT receptacle
16- CobraNet 100BaseTx receptacle
17- IEC power inlet
See page 14 for detailed descriptions.
3
Introduction (continued)
Unlike other configurable DSP boxes, the intrinsic process-
to visit us there.
ing latency of the RAVE 520uz is both short and fixed at
0.396 milliseconds. The delay does not change regardless of
the DSP configuration, unless the configuration intention-
ally adds more delay.
We've applied our many years of experience in supporting
high-end installed sound with our previous system-building
products such as RAVE, QSControl, CM16a, DSP-3, DSP-4,
and DSP-30. The RAVE 520uz brings all that technology
together in one compact, powerful, easy to use system. We
are confident that your new RAVE 520uz will provide years
of dependable service and we hope it will help you, the sys-
tem designer and implementer, to express your creative
audio system ideas.
The RAVE 520uz also supports the new optional low-latency
CobraNet feature that provides transport at only 2.66 milli-
seconds delay.
Both software and firmware can be easily updated over the
network. In the future, QSC will be adding new capabilities
to both RAVE and QSControl.net. Our latest code releases
and access to up-to-date information on RAVE and QSCon-
Block Diagram
4
Introduction - Networking the RAVE 520uz
The RAVE 520uz has two RJ-45 network connection ports on the rear panel. One port is labeled "QSControl" and supports standard
10BASE-T Ethernet. The other port is labeled "CobraNet" and supports 100BASE-TX, also known as "Fast Ethernet". In the following
sections we describe the use of these ports and show example network connection schemes.
The RAVE 520uz supports two distinct kinds of network activity; the first is audio transport via CobraNet, and the second is DSP setup
via QSControl.net. The user can choose to install one network for CobraNet traffic and a second separate network for QSControl.net
traffic. We call this the "Two Wire Interface". Alternately, it is possible to run both DSP setup data and audio traffic over CobraNet via
the CobraNet port. In this case the QSControl port is unused. We call this the "Single Wire Interface".
Under the most demanding real-time control conditions and when using the lowest latency CobraNet settings, users may experience
better QSControl.net performance using separate networks, especially when displaying a great many real-time meters. For most appli-
cations, separate networks won't provide any discernible benefits and will cost more. We therefore recommend using the Single Wire
Interface when running CobraNet.
Why CobraNet Needs Special Treatment:
Ordinary Ethernet traffic has no guaranteed time of delivery. Packets of information may arrive at their destination out of order and
some may be delayed more than others. This is fine for E-mail and even for downloading MP3 files over the Internet. Everything ends up
properly reassembled at the destination, but how long this takes will vary according to network loading, span, etc. In contrast, Cobra-
Net is "real time" - it delivers audio with a minimal, consistent transmission delay. CobraNet is designed to use as much of conventional
networking technology as possible while providing both guaranteed time of delivery and isochronicity - maintaining a phase-locked
sample-accurate clock across the entire network. These requirements mean that ordinary unregulated Ethernet data cannot be freely
mixed with CobraNet information. The two can coexist on the same wire, but only by adhering to the proper rules.
Notes on Network Systems Design:
As with any communications system, the reliability and performance of a local area network is intimately related to the designer's skill
and knowledge in implementing a topology that is robust, efficient and standards-compliant. Proper network design is even more criti-
cal in distributed multimedia systems. Therefore, it is important for the system designer to realize that some conventional network
practices must be avoided. Although each network design is unique and may carry its own performance requirements, compliance to
the following three points will assist in building an audio network that is trouble free and efficient.
First, audio and conventional data communications deliveries should not exist on the same LAN or VLAN. The exception to this is the
RAVE 520uz Single Wire Interface, which offers a solution for converging audio and QSControl.net onto the same LAN or VLAN. How-
ever, conventional communications, such as corporate networks, print services, e-mail and Internet access, should not exist alongside
CobraNet audio and QSControl.net on the same LAN or VLAN. Further, CobraNet audio and QSControl.net data should not exist
together on the same LAN or VLAN when implementing the Two Wire Interface. This is not to say that conventional communications
cannot share the same network hardware with a RAVE 520uz. In fact, common network hardware, such as managed Ethernet switches
and media converters, can service both RAVE 520uz products and conventional data communications equipment so long as the man-
aged switch or media converter are partitioned into separate network domains. This is normally done by configuring a separate VLAN
for each data type. (Some switches may allow individual port assignments or support partitions through DIP switch selection.)
Second, CobraNet audio must traverse either a repeater domain or a network switch domain. The point here is that the CobraNet port
on a RAVE 520uz must connect directly to, and only to, either a repeater LAN or a switched Ethernet LAN. Hybrid networks containing
both repeaters and switches are not permitted on the audio segment. Connecting the CobraNet port to a repeater that is in turn con-
nected to a network switch poses an illegal and non-compliant condition. We recommend always connecting the QSControl and/or
CobraNet port(s) directly to network switch ports.
5
Third, the RAVE 520uz and QSControl.net system are targeted at network switch deployments. The consumer costs of Ethernet
switches have continued to fall over the last several years and are now comparable with repeaters on a per port basis. In addition, the
sophistication and scalability of network switches make them ideal for new installations. However, we do realize that designers may
wish to add RAVE products to existing audio network installations that are built on repeater LAN topologies. This applies primarily to
existing CM16a and RAVE networks. For this very reason we continue to support connectivity to network repeater hardware with the
RAVE 520uz. Support for network repeaters exists only with the Two Wire Interface. That is to say that the QSControl port and the
CobraNet port must be connected to separate repeater LANs. Even when properly configured, audio channel capacity is severely lim-
ited and both audio and control network expansion is limited by the respective capacity of each segment. In other words, scalability
ceases to exist when bandwidth demands on the QSControl.net segment approach 10 Mbps and demand on the CobraNet segment
approaches 100 Mbps. Obviously, we recommend taking advantage of switch network technology whenever possible.
It should be noted here that while the CobraNet port on a RAVE 520uz is restricted to repeater LAN or switch LAN deployments, QSCon-
trol.net is a TCP/IP standards-compliant network system and therefore supports operation on network repeaters, switches and routers.
When implementing the Two Wire Interface, the QSControl.net segment does not require a single topology data path and therefore
repeaters, switches and routers may be assembled on the LAN in a hybrid fashion.
products/network/resources.htm. To learn more about CobraNet design requirements and to obtain the CobraCAD system design utility
All of this may seem daunting if you are new to networking. However, it all boils down to connecting a few simple cables between var-
ious networking devices. Most of the time it "just works". QSC helped pioneer CobraNet with our RAVE ™ products and there are hun-
dreds of installations all over the world, in theme parks, hotels, stadiums - everywhere. They run hum-free, sound great and are very
reliable.
The following examples will help get you started, but they just scratch the surface of what can be achieved with advanced network-
ing…
Example #1 - QSControl.net X-over mode:
This is the simplest connection you can make between the RAVE 520uz and your computer. Use a CAT-5 crossover cable connected
between the RAVE ‘s QSControl port and your computer's Network Interface Card, (NIC). No network switch is required. With QSCon-
trol.net server and client software installed and running on your computer, you will be able to completely set up your RAVE 520uz.
6
Example #2 - CobraNet X-over mode:
This is the simplest connection you can make between a RAVE 520uz and a “destination” product such as the BASIS 922az/902zz/904zz
or the RAVE 522aa.The RAVE 520uz is the audio “source” in this example. Use a CAT-5 crossover cable connected between the Cobra-
Net ports of each unit. No network switch is required. This connection allows audio to pass from the RAVE 520uz to the BASIS/RAVE
unit over CobraNet.
Combining example 1 and 2 lets you setup one unit at a time, much as you would have to do using a point-to-point RS232 connection,
while passing audio between them, all without a network switch. However, you would have to physically connect your computer first
to one unit and then to the other. With this elementary connection you don't have a true network. It is like making RS-232 connec-
tions - except that performance is much better.
All the other examples are of proper networks and all require a network switch. On a proper network, you have direct access to all
RAVE/BASIS units all of the time without having to physically switch between them. You still get the great performance of TCP/IP
over Ethernet. (And we believe QSC's advanced networking software provides the best performance of any networked audio control
system available today, including Ethernet based systems from competitors.)
7
Example #3 - Single Wire Interface:
Here all QSControl.net and CobraNet traffic shares the same single CAT-5 cable between the RAVE 520uz 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 one RAVE 520uz and one “audio destination” product (such as the BASIS 922az) as many devices may
be connected as there are available switch ports. All RAVE/BASIS units will be able to communicate simultaneously with the computer.
All will have CobraNet audio output capability, with the exception of source-only devices like the 520uz. Switches can be connected to
other switches to build larger networks; all of the normal networking principles apply. (Note: there must be at least two CobraNet
devices online (one source and one destination) for any data to come out of the CobraNet port.)
8
|