AVM500-ES User Manual
AVM500-ES User Manual
2. IMPORTANT: When connecting this product to In the case of radio or TV interference, relocate/reorient
accessories and/or another product use only high quality the antenna. If the antenna lead-in is 300 ohm ribbon
shielded cables. Cable/s supplied with this product MUST lead, change the lead-in to co-axial type cable.
be used. Follow all installation instructions. Failure to
follow instructions could void your FCC authorization to If these corrective measures do not produce satisfactory
use this product in the USA. results, please contact the local retailer authorized to
distribute this type of product. If you cannot locate the
3. NOTE: This product has been tested and found to appropriate retailer, please contact Yamaha Commercial
comply with the limits for a Class B Digital device, Audio Systems, Inc., Electronic Service Division, 6600
pursuant to Part 15 of the FCC Rules. These limits are Orangethorpe Ave, Buena Park, CA90620.
designed to provide reasonable protection against
harmful interference in a residential environment. This The above statements apply ONLY to those products
equipment generates, uses and can radiate radio distributed by Yamaha Commercial Audio Systems, Inc.
frequency energy and, if not installed and used according or its subsidiaries.
Always follow the basic precautions listed below to avoid the possibility of serious injury or even death from
electrical shock, short-circuiting, damages, fire or other hazards. These precautions include, but are not limited
to, the following:
PRECAUTIONS
Do not modify, open or disassemble the Product. The NO: "Apparatet må tilkoples jordet stikkontakt"
guarantee shall be null and void in that case.
Do not apply excessive pressure on connectors or SE: "Apparaten skall anslutas till jordat uttag"
any other part of the board. Do not touch the metallic
sharp parts (pins) of the product. This product is designed to be rack-mounted. Be sure
to observe following installation rules of this kind of
This product is electrostatic sensitive; make sure you equipment:
check this before touching or using it. Elevated Operating Ambient - If installed in a
closed or multi-unit rack assembly, the operating
The disconnect devices of the unit are the appliance ambient temperature of the rack environment may be
inlet of the auxiliary power supply and the appliance greater than room ambient. Therefore, consideration
inlet on the rear side of the unit. These must be easily should be given to installing the equipment in an
reachable. environment compatible with the maximum ambient
temperature (Tma) specified by the manufacturer.
Conformity of this product is subject to proper Reduced Air Flow - Installation of the equipment in a
electrical wiring, regarding CEI364 (NFC15-100). rack should be such that the amount of air flow
Installation must be equipped with differential required for safe operation of the equipment is not
protection. compromised.
Mechanical Loading - Mounting of the equipment in
To prevent electric shock, do not remove the cover. the rack should be such that a hazardous condition is
No user-serviceable parts inside. This unit contains not achieved due to uneven mechanical loading.
hazardous voltages and should only be opened by a Circuit Overloading - Consideration should be given
trained and qualified technician. Both power supply to the connection of the equipment to the supply
sources must be disconnected before servicing. circuit and the effect that overloading of the circuits
might have on over current protection and supply
Each connection must be Safety Extra Low Voltage wiring. Appropriate consideration of equipment
kind (SELV), and must stay inside buildings. nameplate ratings should be used when addressing
this concern.
FI: "Laite on liitettävä suojamaadoituskoskettimilla Reliable Earthing - Reliable earthing of rack-
mounted equipment should be maintained. Particular
varustettuun pistorasiaan"
attention should be given to supply connections other
than direct connections to the branch circuit (e.g. use
of power strips).
This Product uses high frequency digital circuits that Always use shielded cables and connectors (serial
might interfere with electrical or electronic devices placed port, word clock and EtherSound ports). In the other
in your working environment. Please make sure this kind case, AuviTran will not guarantee the proper behavior
of device (television, radio device, cell phones) is of the product.
removed in order to ensure a proper functioning of each
device. Serial port cable must be length < 1m to ensure
proper EMC and interferences behavior.
LIMITATION OF LIABILITY
In no case and in no way, the provider of this Product Please note that graphics given in this manual (drawings
(AuviTran, the distributor or reseller, or any other party and schemes) are only examples and shall not be taken
acting as provider) shall be liable and sued to court for for a real vision of your own equipment configuration.
damage, either direct or indirect, caused by and to the
user of the board and which would result from an AuviTran is constantly working on the improvement of the
improper installation or misuse of the Product. “Misuse” products. For that purpose, the products functionalities
and “improper installation” mean installation and use not are bound to change and be upgraded without notice.
corresponding to the instructions of this manual. Please read carefully the User’s manual as the new
functionalities will be described therein.
All trademarks listed in this manual are the exclusive property of their respective owners. They are respected “as is” by
AuviTran. Any use of these trademarks must receive prior approval of their respective owners. For any question, please
contact the trademark’s owner directly.
COPYRIGHT
The information in this manual is protected by copyright. Therefore, reproduction, distribution of whole or part of this manual
is strictly forbidden without the prior written agreement of AuviTran.
Please visit our website for any question of further inquiry concerning our product range. Updates will also be posted when
available.
http://www.auvitran.com
PACKAGE CONTAINS
1 AVM500-ES
1 Power Cord
1 Safety Instructions Manual
Cord-set with proper plug configuration must be used, depending on country in which the product is used
1 WELCOME!............................................................................................................. 8
2 WHAT’S NEW? ....................................................................................................... 8
3 TECHNICAL SPECIFICATIONS ............................................................................. 9
4 REAR PANEL DESCRIPTION .............................................................................. 10
5 TYPICAL ARCHITECTURE USING AVM500-ES ................................................. 10
6 POWERING AN AVM500-ES FOR THE FIRST TIME........................................... 11
6.1 Definition of Mono Network Mode ..................................................................... 11
6.2 How to build a simple Star Architecture ............................................................. 12
6.2.1 Example #1 - NAI48-ES {ch1-16} to AVY16-ES100 {ch1-16} .............15
6.2.2 Example #2 – AVY16-ES100 {ch13-16} to NXAmp {ch1-4} ................17
6.3 Why using Star Architecture instead of basic Dasy-Chain? .................................... 19
6.4 Limitations of the Mono Network Mode .............................................................. 21
6.4.1 Port {Aout} inactive .......................................................................21
6.4.2 Remote control through 3rd Port – ES100/ESV2 ..................................21
Thank you for purchasing AuviTran’s AVM500-ES. We hope you will enjoy using it. This product will help you in expanding
your current EtherSound networks.
As AVM500-ES acts as an EtherSound matrix router, you will be able to handle up to 320 EtherSound channels linked to 5
physical ports, build ring redundancy topology, and many others architectures. AVM500-ES is able to aggregate separated
ES V2 and ES100 networks.
You will find herewith the necessary instructions to use your product. Please read them carefully as misuse of this device
might cause serious damage to you and your environment.
2 WHAT’S NEW?
This version of the manual refers to the last firmware of the AVM500-ES, i.e. version 0x110E / 0x118E. You are invited to
check the version of your device, and perform a firmware update if necessary.
Thanks to this new firmware, AVM500-ES has the following extended functionality:
- AVM500-ES is now available in AVM500-ES/3ports, with all the advantages of AVM500-ES, limited to 3
EtherSound ports, at a very attractive cost. AVM500-ES/3ports stays upgradable to regular AVM500-ES.
- Serial Port embedded a command interpreter that allows you to patch the whole matrix through a simple RS232
protocol. Please refer to dedicated paragraph for more information.
- Device ports C, D and E can be swapped from EtherSound to ASIO protocol. ASIO computer-based application
will be able to play/record up to 64 channels on each port. Matrix patch allows choosing which channel is to be
played or recorded. You will find more information in the dedicated paragraph.
General
Size 483 x 253 x 44mm (19’ rack / 1U Height)
Power Consumption <50 Watts
Main Power Supply 100-240VAC 50/60Hz 1.5A Max
DC supply (Auxiliary) 5Vdc 5A max – 12Vdc 2A max
Auxiliary Power Supply 100-240V~ 47-63Hz 1.35A / +5Vdc 5A ; +12Vdc 2A
Storage: Temp/Humidity - 5°C to 70°C / Max 95% (non-condensing)
Operating: Temp/Humidity 5°C to 40°C / 5% to 90% (non-condensing)
Front Panel Networks and links Rx and Tx Activities; Active synch running ; Power Main, Aux and On Display
Rear Panel 1 IEC Power inlet; 7 Neutrik EtherCon RJ45; 1x6 poles Euroblock Connector for Aux power supply; 1 BNC for word
clock synch in; 1 DB9 connector for Serial Port
AVM500-ES Features
EtherSound Network Segment 5 EtherSound Network Segments interconnections : A (In, Out), B, C, D, E
EtherSound IN Port 1 EtherSound IN Port: AIN
EtherSound OUT Port 5 EtherSound OUT Ports: AOUT, B, C, D and E
ES-100 to ES-100 Latency 6 samples (125µs at 48 kHz)
Digital Audio Channels 320 (5 x 64) Input Audio channels and 320 (5 x 64) Output Audio channels
Matrix / Patch size 320x320 full cross matrix with remote control patch via EtherSound
Any individual output audio channel can be muted or patched to any of the 320 available Input audio channels
Remote control Via EtherSound of from Ethernet PC remote link
Other I/O RS232 serial port
Clock Synchronisation mode 48 kHz local clock (when Primary Master) or EtherSound Network (When not PM)
Word clock In used for synchronisation
Temp / Fan monitoring
Temp Monitoring Network Monitoring of Temperature inside the Box
PSU Monitoring Network Monitoring of PSU Failure for Main and Aux power supply
2 Fan Control modes Automatically Controlled by internal Temperature
Off
EtherSound
Power Switch AC In Serial Port Word Clock
Ports
Please always check that rear-panel dip-switch #1 is set to “OFF” for proper device operation.
“ON” position is reserved for firmware update only (see chapter 13).
This is an example of the AVM500-ES capability: each cluster of EtherSound devices can share up to 64 audio channels with
each others, in bidirectional configuration. With ES100 networks, control PC can be plugged directly to AVM500-ES “3rd port”
to control the whole network.
AVM500-ES is a dedicated and versatile EtherSound network router and matrix. Many configurations and parameters are
available to best fit each kind of architecture you want to build. When powering an AVM500-ES for the first time, it will boot in
the factory configuration. This mode is called “Mono network mode”. This is the simplest way to use an AVM500-ES.
To sum-up theses points, we can compare AVM500-ES to an EtherSound device with one input port and four output ports.
These four ports are always synchronized to the input port. Each port can share its audio channels with each other.
This mode allows you to build bidirectional star architecture that was absolutely impossible to do before, with a regular
switch.
Fig. 3 illustrates what we call a star architecture. In few words, a star architecture has a “node” that acts as a splitter. This is
a point where a network is divided in multiple branches. This vision is true for the downstream. For the upstream, this is the
opposite. The node “concentrates” multiple branches in a single one. The AVM500-ES is this node.
In the following example, you will learn how to build a real EtherSound network using an AVM500-ES, and how to use the
Netpatch to route audio channels. Let’s have a look to the schematic:
In this network, the AVY16-ES100 in the LS9 mixing console is the Primary Master (PM). Indeed, there is no EtherSound
network plugged on its In port, but only the control PC. The Out port of the AVY16-ES100 is connected to port {Ain} of the
AVM500-ES. Ports {B, C, D}, that are Outputs ports, are connected respectively to port In of DME4io, NAI48-ES and NXAmp
4x4. Port {E} is unused.
Remember that in this example, the AVY16-ES100 is PM, so it generates the audio clock. This clock is transmitted to the
AVM500-ES port {Ain} through EtherSound. As described in the previous paragraph, AVM500-ES propagates the clock from
{Ain} to {B, C, D, E}, so the three third-party devices are properly feed with clock.
When running AuviTran AVS-Monitor software on the control PC, the Tree View of this network will be the following:
The AVY16-ES100 is obviously the Primary Master, followed by port {Ain} of the AVM500-ES. Ports {B, C, D, E} are on the
same hierarchy level, as expected. And behind each port, we can find our three EtherSound devices.
The following description of Netpatch is based on “Display full AVM500 in NetPatch” option
enabled (see AVS-Control Panel documentation for further information). This is for didactic
purpose only. Disable this option to hide AVM500 Matrix in NetPatch and simplify use of
EtherSound network patch.
Let’s have a look to the Netpatch now. We can see four different colours in it:
- White, means you can make a direct connection between source and destination.
- Gray, means there is no way to make a direct connection.
- Pink, means this is the matrix internal patch of an AVM500-ES.
- Yellow, means that there is a possible path through an AVM500-ES.
In this example, you will learn how to make the following patch:
(1) NAI48-ES {ch1-16} to AVY16-ES100 {ch1-16}
(2) AVY16-ES100 {ch13-16} to NXAmp {ch1-4}
Since version 3.9.4 of AVS-Monitor software, such a path is now extremely easy using net patch. It is a “one click” process.
If you want to route NAI48-ES channels directly to AVY16-ES100 inputs, you will see that you are facing a yellow cell. This
means that Netpatch found a connection between theses two devices through an AVM500-ES. As patch grid is collapsed 16
by 16 in this example, all you have to do is to click the yellow cell between NAI48 {ch1-16} and AVY16 {ch1-16}. The
software will do everything automatically!
The patch you’ve just made in yellow cell is represented by a star. This is the symbolic view for a patch through an AVM500-
ES. At the same time, Netpatch added the real path of audio channels:
- One cross (direct connection) between NAI48 and AVM500-ES Port C.
- One circle (AVM500 internal patch) between Port C and Port A.
- One cross (direct connection) between Port A and AVY16-ES100.
Now, if you select AVM500-ES port {Ain}, and then you go to the “Matrix” tab, you will notice that internal digital audio matrix
was effectively patched as expected.
Final step, and one more time the same logic. Just expand Netpatch to have access to desired channels. Then, drag and
drop (with “Shift” button) the four desired channels, i.e. AVY16-ES100 {ch13-16} to NXAmp {ch1-4} available one more time
in yellow cells.
Apply selection, and you will see the whole path patched automatically. Notice patch between AVY16-ES100 and AVM500-
ES Port A, between Port A and Port D (pink cells), and between Port D and NXAmp.
More information, tips and tricks regarding Netpatch is available in AVS-Monitor User’s Manual. Please directly refer to it
learn how to handle it perfectly.
If this kind of architecture would have perfectly worked, it has also a big drawback:
- if the cable between NAI48-ES and DME4io fails,
- if the NAI48-ES fails or is switched-off,
- if the DME4io fails or is switched-off,
in all of theses cases, audio channels will never reach the NXAmp, and diffusion will be lost.
Big advantage of the star architecture is to bypass this issue. Indeed, if a branch of the star fails, the rest of the network
continue to work. For example, if DME4io fails, you will only loose its channels, but NAI48-ES channels and AVY16-ES100
channels can still be played on the NXAmp. Of course this is the same idea for all other branches of the network.
A classic example is a recording studio, with multiple recording rooms. If each room is a branch of the star, then you don’t
have to bother of the state of the other rooms (devices on or off) when you want to record one.
Looking back to Fig. 1, we can see that the output port of port A is already used to communicate with the four other devices
via the internal switch. Doing so, the back-panel port {Aout} is unwired in this mode. Plugging an EtherSound compatible
device on this port has no effect.
Back-panel port {3rd} is the computer local access point of the device, regarding to ES100 technology. Please refer to the
proper EtherSound manual if you are not used with ES100 standard and especially 3 rd port access. This port accepts only
a computer for remote control. No EtherSound compatible device should be plugged on it (Fig. 15).
Connecting a computer on this port allows you to remote control the whole network directly from this point. Plugging the
control PC on the Primary Master input port is no more mandatory.
Nevertheless, the limitation of Mono Network Mode is that all EtherSound compatible devices of the network must be ES100
compatible (Fig. 13). If an old ES-V2 device is inside the network, you will not be able to control and monitor the network
through the 3rd port (Fig. 14).
Fig. 14: Improper wiring of port {3rd} in Mono Network Mode (ES-V2 inside)
Fig. 15: Improper wiring of port {3rd} (EtherSound stream on the port)
In order to expand capacities of AVM500-ES, and to bypass the limitations described above, the user can configure the
device in different modes. Configurations are fully software selectable thanks to AVS-monitor software.
In chapter 6.1, Fig. 1 illustrates a very simplified view of the AVM500-ES behavior. It is in fact a little bit more complicated.
Let’s look at Fig. 19 below.
Compared to Fig. 1, some switches have appeared. These are controlled via AVS-Monitor software, in AVM500-ES Control
Page (Fig. 21). When activating a switch, the related port is dissociated. No more EtherSound stream can reach it, and so
becomes a virtual Primary Master. When all {B, C, D, E} ports are dissociated, you can notice that the internal switch
becomes useless. That’s why the switch named [CAout] automatically switches on, and connects the port {Aout} on the rear
panel.
The goal of the dissociation is the same than before, i.e. merge ES100 and ES-V2 networks and build multiple tunneling
communications. When port {Aout} is activated, you will also be able to build ring architecture. This will be described in the
next paragraph.
As no EtherSound stream can reach the ports when they are dissociated, you will need to plug the control PC to the port {3rd}
if you want to remote control your network.
Please note that port dissociation has absolutely no effect on the clock propagation through the devices, neither on the audio
communication with the Digital Audio Matrix. You can always route audio channels between ports even if they are
dissociated from the main network.
The following Fig. 22 represents an example of network architecture, using AVM500-ES with some ports dissociated.
Fig. 22: Example of mixed ES100 / ES-V2 network with dissociated ports
FOH is a Yamaha console with two AVY16-ES100 cards. The cards are daisy-chained with port {Ain} of AVM500-ES. This
branch of the network is fully ES100.
Port {B} is connected to a NAI48-ES that is ES100 compatible, and then to two AVY16-ES inside another Yamaha console.
Because of the AVY16-ES, this branch of the network is not fully ES100.
Ports {C} and {D} receive NXAmp 4x4, that are ES100 compatible.
Port {E} receives an AVB32-ES that is only ES-V2.
The goal is to remote control AD8HRs from network 3 with the FOH console, and AD8HRs from network 2 with the Monitor
console. The only way to have multiple tunneling is to dissociate ports of AVM500-ES to create sub-networks with virtual
Primary Master. As AVM500-ES is not PM in this example, we cannot use the dip-switch #1 on the rear-panel. The
dissociation of ports {B} and {E} is done thanks to AVS-Monitor software (Fig. 24). List and Tree view from AVS-Monitor
software is available Fig. 23. We can clearly see three different networks, as expected.
We can now build a tunneling communication on port {B}, between AVY16-ES and NAI48-ES. Another tunneling (inter-port
tunneling this time) is also build between AVY16-ES100 on port {Ain} and AVB32-ES on port {E}.
In order to control and monitor the entire network, control PC is plugged on port {3 rd} of the AVM500-ES. Indeed, if this
computer was plugged on the PM of the network, i.e. the AVY16-ES100 in the FOH console, control and monitoring of
network #2 and #3 would have been impossible because of the dissociation.
All necessary instruction regarding the tunneling configuration will be detailed in the appropriate paragraph of this manual.
To build ring architecture with an AVM500-ES, you will need to use the dedicated pair of ports {Ain/Aout} (Fig. 25). To do so,
it is mandatory to activate port {Aout} using AVS-Monitor control page, that means dissociate all other {B, C, D, E} ports. As
{Ain} and {Aout} will be used by the ring, you will need to connect the control PC to the port {3rd}.
This solution brings a redundant network of 64 audio channels that can be shared with the four other networks. In order to
configure your network as a ring redundant network, please refer to AVS-Monitor software user’s manual.
Below is an example of ring architecture between four AVM500-ES. Each 3rd port is connected to the control PC via a regular
Ethernet switch. Doing so, all devices are remotely controllable. Thanks to the digital audio matrix of each AVM500-ES, each
device can share its audio channels with every other device in the whole network. Also, the system will continue to work
perfectly even if a red cable (but only one) is defective.
This mode requires good knowledge of AVM500-ES capabilities and EtherSound networks. It has been
designed to take the maximum of AVM500-ES possibilities. This mode is for very specific architectures, and
majority of AVM500-ES users can ignore it.
Aim of this mode is to choose if ports {B, C, D, E}, when dissociated, will individually act as EtherSound input ports or
EtherSound output ports.
Without any special configuration, ports {B, C, D, E} are EtherSound output ports regarding previous paragraphs. When
dissociated, the input port becomes useless (see Fig. 19). In this case, an internal switch allows the user to choose if the
physical port must be tied to the EtherSound input port, or to the EtherSound output port.
Important note: please remember that ports {B, C, D, E} are always synchronized with port {A}. If you configure a
port as an input port, it will NOT receive the clock from the EtherSound stream, but still from the {A} port. It is you to
ensure that all devices tied to this port will be properly synchronized with the others networks, for example using a word clock
cable.
Some EtherSound compatible devices need to be Primary Master in order to have remote control capabilities (for example
SY80 control surface with DIO core). The input port configuration on AVM500-ES allows having multiple Primary Masters, to
have multiple remote controls, but with word clock synchronization restriction.
Note the Word Clock link between the two Primary Masters, to ensure proper clocking of the whole network.
Configuration in AVS-Monitor:
You are now ready for installation. Refer to the AVS-Monitor documentation for installation.
When AVS-Monitor is installed on your PC, you can run AVS-Monitor and manage any AVM500-ES devices connected to an
EtherSound network. Refer to AVS-Monitor documentation for generic EtherSound device management such as
Enumeration of EtherSound devices.
After running the AVS-Monitor, Select an AVM500-ES device on the device list or tree list.
The following description is based on version 4.2.0 of AVS-Monitor software, which is the
official released version at the time where this manual is written.
The control PC is plugged to the port {Ain}. AVM500-ES is so Primary Master. All ports {A, B, C, D, E} are on the same
hierarchic level, as it will be with an Ethernet switch.
You can find in the “EtherSound module properties” box the port currently selected, that can helps you to create your own
device alias (name).
This is the patch matrix of the 320 EtherSound channels. Each port can handle 64 channels. This is the synthetic view of the
matrix, so channels are grouped 16 by 16. You can click on each row or column to expand it, to handle channels one by one.
You can also click on icon in the “receivers” row and “sources” column to expand / collapse in one time the whole
matrix.
Click on the icon to remove the whole patch you may have previously entered.
Click on the icon to resize the matrix by a factor 2. This is really useful if your computer screen is not large enough.
You will find below two screenshots of the matrix illustrating the possibilities:
Each row will display the name of the port / channel that is patched to it. This helps you to remember quickly your patch,
even if the whole matrix cannot be displayed on the computer screen.
If you click on a couple of collapsed row / column, this will create a diagonal on the 16 channels.
You can also use the “Shift” key of your keyboard to draw a diagonal or a column with the mouse, like a drag and drop.
The Status box shows temperature in the box and fan speed.
Fan speed is automatic, depending on box temperature. Thresholds were optimized regarding fan noise and maximum
working temperature. For noise-critical environment, fan can be turn-off. To do so, please click on the AVM500-ES Rear
panel picture, to open the Setup Box. Device Control box can also set the Front Panel LEDs brightness.
Please note that if internal temperature becomes too high, AVM500-ES will override the “Stop Fan” command to ensure
proper cooling of the box.
You can dissociate ports by clicking in corresponding check-box. As mentioned before, when {B, C, D, E} are disconnected,
port {Aout} automatically becomes active. In other means, clicking on “Activate A Out” check-box will automatically
disconnect the four other ports.
When you dissociate a port from the main switch, the corresponding In/Out radio button becomes active. This enables you to
configure your ports as described in paragraph 7.2 Advanced Users: Multi Network Mode – Input configuration. Please
read carefully this paragraph before using this function.
Check-box “3rd Port” allows you to disable the 3rd Port remote control of the selected Port (see 3rd port architecture in Fig.
20). When this box is un-checked, you will no longer be able to control the Port if your computer is plugged to “3 rd Port”. This
can be useful in some special configuration where more than one computer is used in the network (particularly when the port
is set to act as an Input Port).
When port {Aout} is active, you can choose if the audio insertion and extraction must be done upstream or downstream (for
the whole 64 channels). E.g., to build a ring architecture*, you must insert audio downstream and extract audio upstream
(done automatically in this case to simplify use of AVM500-ES).
AVM500-ES has multiple possible sources of audio clock. The Clock Control box helps you choosing the best for your
application. When the device is primary master (i.e. at the beginning of an EtherSound daisy chain), you can choose if the
clock must be generated by AVM500-ES itself (Local 48kHz), or synchronized from the external source (Word Clock). If it is
not a primary master, AVM500-ES will automatically recover clock from EtherSound network.
Please note that if you choose the Word Clock synchronization mode, and no proper clock is brought on word clock
connector, AVM500-ES will generate an emergency 48kHz clock in order to not loose control of the device. This emergency
clock is turned-off as soon as there is a valid clock on the Word Clock connector.
This box helps you to create a tunneling communication between remote modules (unicast) using “Inter-Port” tunneling
feature.
The way the interface is done helps you understanding the path of incoming and outgoing tunneling data, regarding selected
port.
The next chapter of this manual will fully detail how to build tunneling communications between two devices in few illustrated
examples.
The physical Serial Port of AVM500-ES is internally connected to port {B}. The control page of this port will so display an
additional box:
This box will helps you to configure properly the physical parameters of the serial port, in association with the Tunneling
Setup box.
Since version 0x110B / 0x118B of AVM500-ES firmware, multiple tunneling communications can be built, depending on the
network architecture. This chapter will illustrate the more common cases that you can face when using an AVM500-ES.
Remember that port B is the port that owns the physical serial port. In this example, the whole configuration will be made in
AVM500-ES Port B control page. What we want to do here is to redirect the Serial port stream to the AVY16-ES100 in LS9,
and the AVY16-ES100 stream back to the Serial port.
Let’s see how to handle the control page:
- The “Incoming Tunneling Data” is the data from the remote device, i.e. AVY16-ES100 in our example. It goes in port
B (because AVY16-ES100 is plugged on port B). We want this stream goes to AVM500-ES Serial port. That’s why
we choose “Serial Port” in “Egress Port for Tunneling” combo box.
- The “Incoming Port Data” is the “internal” AVM500-ES data coming from any Port from A to E, or from Serial Port. If it
is coming from another port, the configuration is made in the corresponding port (we will see an example just after).
In our case, this data is coming from Serial Port. That’s why we can see in “Serial Port Configuration” box that the
physical Serial port is redirected to “Port B”. We want to send this stream to the AVY16-ES100, that why we choose
“LS9-1” in “Tunneling Destination” combo box.
- Of course, to finish this configuration, we must go to AVY16-ES100 control page, and configure a Unicast up to
AVM500-ES Port B.
Let’s just see quickly what would be the configuration if AVY16-ES100 is plugged on port E, for example. This time, we will
have to go to both Port B and Port E control page. Let’s begin with Port E control page.
There is no Incoming Tunneling Data on this port. “Egress Port for Tunneling” is useless, so leave it to “Port B” that is default
setting. There is neither Outgoing data on this port, so leave “Tunneling Destination” to “Off”. The only thing to do, is to
redirect the Serial port to “Port E” in the “Serial Port Destination” combo box, that’s it!
All ports of the AVM500-ES are dissociated. The goal here is to make a path between LS9 #1 and SB168 #1 and another
between LS9 #2 and SB168 #2. Let’s proceed step by step:
1. On LS9 #1 control page, create a unicast path (Tunneling Destination) to”AVM500 B”, Serial Mode set to “LS9
Mode”.
2. On AVM500-ES Port B, open a path between LS9 #1 coming stream and distant port C.
4. On AVM500-ES Port C, open a path between SB168 #1 coming stream and distant port B.
Of course, the configuration is exactly the same for the other couple of LS9 #2/SB168 #2 with their respective AVM500-ES
ports (D and E).
Since AVM500-ES firmware version 0x110C/0x118C, back panel Serial Port embedded a command interpreter that allows
user to patch the matrix without using AVS-Monitor. This feature was typically designed for remote control with Crestron ®
control panels. Of course, any distant interface that is design to complies with interpreter protocol will suites.
Now, in Port A control page, select “Serial Port” in “Egress Port for Tunneling” combo box. And finaly, turn-on interpreter by
checking “Serial Port Remote Ctrl” check-box. That’s it! Don’t forget to use a crossed RS232 cable between AVM500-ES and
your remote control device.
Five commands are defined today from the serial port patch:
If an unknown command is sent, interpreter will return the ten first characters of the command, followed by « ? » character.
At end of each response, prompt character “>” is added after <CR>.
For instance:
Command send: V?
Answer received: V=1.0
Where:
<Dest_Port> is a letter in {A, B, C, D, or E} that represents the destination port.
<Dest_I/O > is a 2 decimal digit that represents the destination output number.
<Source_Port> is a letter in {A, B, C, D, or E} that represents the source port.
<Source_I/O > is a 2 decimal digit that represents the source output number.
For instance:
Patch Output 12 of port A from input 5 of Port E:
Command send: A12=E05
Answer received: A12=E05
Patch Output 64 of port D from input 12 of Port C:
Command send: D64=C12
Answer received: D64=C12
Where:
<Dest_Port> is a letter in {A, B, C, D, or E} that represents the destination port.
<Dest_I/O > is a 2 decimal digit that represents the destination output number.
For instance:
Mute Output 03 of port B:
Command send: B03=M
Answer received: B03=M
Mute Output 60 of port C:
Command send: C60=M
Answer received: C60=M
Where:
<Dest_Port> is a letter in {A, B, C, D, or E} that represents the destination port.
<Dest_I/O > is a 2 decimal digit that represents the destination output number.
<Source_Port> is a letter in {A, B, C, D, or E} that represents the source port.
<Source_I/O > is a 2 decimal digit that represents the source output number.
M is a letter to defined Muted output (i.e. Not Patched)
For instance:
UnMute Output 03 of port B:
Command send: B03=U
Answer received: B03=M
UnMute Output 60 of port C:
Command send: C60=U
Answer received: C60=D03
Where:
<Dest_Port> is a letter in {A, B, C, D, or E} that represents the destination port.
<Dest_I/O > is a 2 decimal digit that represents the destination output number.
<Source_Port> is a letter in {A, B, C, D, or E} that represents the source port.
<Source_I/O > is a 2 decimal digit that represents the source output number.
M is a letter to defined Muted output (i.e. Not Patched)
For instance:
Get Patch information for Output 12 of port A:
Command send: A12?
Answer received: A12=E05
Get Patch information for Output 64 of port D
Command send: D64?
Answer received: D64=C12
Get Patch information for Output 03 of port B:
Command send: B03?
Answer received: B03=M
Get Patch information for Output 60 of port C:
Command send: C60?
Answer received: C60=M
This screenshot is made on an AVM500-ES with interpreter activated, and a serial cable plugged between AVM500-ES and
computer serial port. Tera Term ® software is used to send characters on computer serial port.
11 ASIO CONFIGURATION
Since AVM500-ES firmware version 0x110C/0x118C, Ports C, D and E can be swapped from EtherSound to ASIO stream.
When performing such a swap, the port is no longer an EtherSound Output or Input, but a regular Ethernet port. Plugging an
EtherSound compatible device on an ASIO port will have no effect, and EtherSound compatible device will NOT be
controllable through AVS-Monitor.
An ASIO port is waiting for a computer connection. It can be a direct connection through a regular Cat5 cable, or it can go
through an Ethernet switch. A Gigabit switch may be recommended rather than a 100Mbits one, to be sure to not have
bandwidth limitation. For further information regarding ASIO technical configuration, please refer to “AuviTran Network ASIO
Streamer User’s Manual”.
1. Dissociate the port and configure it as an ‘In’ port (this is in Port A control tab):
The port will then disappear from the network displayed in AVS-ESMonitor.
2. Connect the port to the PC (use a switch to connect both the ASIO port and the 3 rd port of the AVM500-ES to the
PC). The port is visible again in AVS-ESMonitor.
3. In the port’s control tab you can now enable the ASIO streaming mode:
Make sure to set the port to ‘In’ mode before connecting it to the host PC or to a switch. Failure to do so will
cause EtherSound traffic to be broadcasted and will have a severe impact on the network’s performance and
stability.
2. Disconnect the port from the control PC. The port disappears from the network displayed in AVS-ESMonitor.
3. Associate the port with the port A. The port is visible again.
In this architecture, we have an AVA4-ES100 that brings its analogue audio inputs on port B, an AVP4-ES100 that can play
up to 4 channels on port D, and a computer with an ASIO based application plugged on port E. This port has been
configured as an ASIO port in its control page. Control PC is plugged on AVM500-ES 3rd Port. As you can see in this tree
view, the computer that plays/record is not visible, because there is no longer EtherSound stream on port E.
If you wan to record audio from AVA4-ES100, all you have to do is to patch its channels to port E.
If you want to play audio from computer to AVP4-ES100, all you have to do is to patch port E down to AVP4-ES100.
Here is the NetPatch view of this architecture. You can see that AVA4-ES100 inputs are routed up to AVM500-B. Then,
channels from B are redirected to AVM500-E where recording computer is plugged.
In the other way, channels played from computer on port E are redirected to AVM500-C. Then AVP4-ES100 is patched to
listen to port C.
For further information regarding ASIO technical configuration, please refer to “AuviTran Network ASIO Streamer User’s
Manual”.
AVM500-ES provides another source of power supply, to improve the reliability of the system. It allows you to have two
distinct power supply sources, for redundancy solutions. When both power supply units (PSU) are plugged, AVM500-ES
compare them, and always choose the best. In case of failure of one PSU (or associated electrical network), AVM500-ES will
so continue to work.
Auxiliary PSU (ref. AVPSAUX-E45/EB) is validated and provided by AuviTran only. Please contact us if you want to integrate
the redundant PSU in your system.
http://www.auvitran.com
13 FIRMWARE UPDATE
To upgrade your AVM500-ES with new firmware release, please download the AVS-Firmware Updater software on
AuviTran’s web site. You can also check periodically on the web site for new firmware release.
Please follow the steps below to put your device into a coherent mode for firmware upgrade.
- First of all, unplug all devices that may be connected to the AVM500-ES, and plug your computer on port
{Ain}.
- Then, ensure that all {B, C, D, E} ports are not dissociated (via AVS-Monitor). In this case, the firmware
updater won’t be able to access to the devices. If needed, re-associate ports. For AVM500-ES/3Ports,
only ensure that ports B and C are not dissociated.
- Save to non-volatile memory by clicking the icon in AVS-Monitor. You will have to re-set your
previous configuration after the update, and save it again with the same icon.
You are now ready to upgrade the device properly and at a maximum speed. Please read the AVS-Firmware Updater
manual to handle it properly.
At the end of the update, please set back dip switch #1 to “OFF” to ensure proper operation of the device.