en

m
CrossNET

Hybrid Intercom Matrix

CrossNET
User Manual
2.1 Version June 2016
 CrossNET

NOTES

Please read carefully before using the equipment. Keep this manual
for future references.

Before using the product, check that the equipment is in right

condition and that the packaging includes the required accessories.
Should there be any problem, please contact either AEQ-KROMA or
your supplier at your earliest convenience.

* Read and keep this manual.

* Pay attention to the bold notes in this manual.

* Follow the instructions.

* Do not use the equipment close to water.

* Use it only in a rack with chassis ground connection.

* Do not cover the grille ventilation.

* Do not use it close to a radiation source or excessive heat.

* Allow a proper space for the power supply unit; insert the power supply
unit cable into the connector at the rear back of the equipment properly.

* In order to reduce the risk of short circuits do not expose to rain or to

adverse weather conditions.

* Use a wet cloth and non-abrasive cleaning products.

* Do not press the screens, scratch or whatsoever with a sharp object that
may damage them.

* Report any problem with the equipment to Broad Service, KROMA’s

after sales support team.

AEQ-KROMA KEEPS THE RIGHT TO MODIFY THE EQUIPMENT

WITHOUT UPDATING THIS MANUAL.

CrossNET 1
 CrossNET

CONTENTS
CHAPTER 1: CHARACTERISTICS........................................................... 6
1.1 FUNCTIONALITY............................................................................. 6
1.2 TECHNICAL SPECIFICATIONS...................................................... 8
CHAPTER 2: PHYSICAL DESCRIPTION ................................................. 9
2.1 FRONT PANEL VIEW...................................................................... 9
2.1.1 FRONT USB CONNECTOR ..................................................... 9
2.1.2 POWER LED ........................................................................... 10
2.1.3 CROSSPOINT KEYS ............................................................ 10
2.1.4 LCD DISPLAY ......................................................................... 10
2.1.5 ENCODER............................................................................... 10
2.1.6 MODE KEY.............................................................................. 10
2.1.7 HW ERROR LED..................................................................... 11
2.1.8 MUTE KEY .............................................................................. 11
2.1.9 HEADSET CONNECTOR ....................................................... 11
2.1.10 LOCAL SPEAKER................................................................. 12
2.1.11 ON/OFF KEY......................................................................... 12
2.2 REAR PANEL VIEW ...................................................................... 13
2.2.1 POWER CONNECTION........................................................ 13
2.2.2 IP NETWORK PORT ........................................................... 14
2.2.3 DIGITAL PORT .................................................................... 16
2.2.4 GPIO INPUTS AND OUTPUTS .............................................. 17
2.2.5 SYNCHRONIZATION PORT................................................... 18
2.2.6 ANALOGUE PORT.................................................................. 19
CHAPTER 3: EQUIPMENT INSTALLATION .......................................... 22
3.1 SYSTEM SCHEME ........................................................................ 22
3.2 INTER-SYSTEM CONNECTION ................................................... 26
3.2.1 AES67 AoIP System ............................................................... 26
3.2.2 VoIP System............................................................................ 27

CrossNET 2
 CrossNET

3.2.3 Redundantly wired IP system .................................................. 28

3.2.4 Kroma Digital ........................................................................... 29
3.2.4 Analogue Audio ....................................................................... 30
3.3 COMPATIBLE EQUIPMENT.......................................................... 31
3.3.1 Kroma User Panels ................................................................. 31
3.3.2 High-quality: AoIP.................................................................... 31
3.3.3 Voice quality: VoIP .................................................................. 32
CHAPTER 4: DANTE CONTROLLER PRECONFIGURATION .............. 35
4.1 “Dante Controller” Installation ........................................................ 35
4.2 Using “Dante Controller” ................................................................ 36
CHAPTER 5: FRONT PANEL OPERATION ........................................... 40
5.1 MENÚS .......................................................................................... 41
5.2 AUDIO KEYS AND CROSSPOINTS ............................................. 45
CHAPTER 6: SOFTWARE ...................................................................... 47
6.1 INSTALLATION.............................................................................. 47
6.2 MENU OPTIONS ........................................................................... 51
6.2.1 Menus...................................................................................... 52
6.2.2 Tool bars.................................................................................. 59
6.3 MATRIX CONFIGURATION .......................................................... 61
6.4 PORTS CONFIGURATION............................................................ 64
6.5 GROUPS........................................................................................ 69
6.6 CONFERENCES............................................................................ 71
6.7 BP5000 BELTPACK ROLES ......................................................... 73
6.8 IFB’S .............................................................................................. 76
6.9 DIALS............................................................................................. 79
6.10 KEYS CONFIGURATION ............................................................ 81
6.11 VOLUME CONTROL ................................................................... 88
6.12 ‘ON LINE’ CONNECTION ............................................................ 91
6.13 MATRIX INTERCONNECTION.................................................. 105

CrossNET 3
 CrossNET

6.14 LIVECROSSMAPPER REAL-TIME SOFTWARE...................... 112

CHAPTER 7: QUICK START USER’S GUIDE...................................... 121
7.0. Example to develop..................................................................... 121
7.1. Equipment connections............................................................... 122
7.1.1 Power supply ......................................................................... 122
7.1.2 Audio and intercom: panels and auxiliary circuits ................. 122
7.1.2.1 AoIP ................................................................................ 122
7.1.2.2 Digital .............................................................................. 122
7.1.2.3 Analogue......................................................................... 122
7.2. Power up ..................................................................................... 123
7.3. Pre-Configuration of AoIP links using Dante Controller .............. 123
7.3.1 Dante Controller .................................................................... 123
7.4. Development and loading of a map ............................................ 126
7.5 Activating and checking the configuration.................................... 139
ANNEX .................................................................................................. 140
ANNEX A: WARRANTY..................................................................... 140
ANNEX B: DANTE BASES AEQ AoIP ETHERNET SWITCHES ...... 141
ANNEX C: DANTE CONTROLLER INSTALLATION AND
CONFIGURATION ............................................................................. 146
C.1. “Dante Controller” Description ................................................ 146
C.2. Minimum System Requirements ............................................. 147
C.3.Installing “Dante Controller” ..................................................... 149
C.3.1 Downloading “Dante Controller” .................................... 149
C.3.2 Installing “Dante Controller” on Windows.......................... 149
C.3.3 Uninstalling “Dante Controller” under Windows ................ 150
C.4 Where to find the “Dante Controller” application?.................... 150
C.5 Configuring “Dante Controller” ................................................. 151
C.6 Using “Dante Controller” .......................................................... 154
C.7 Using “Dante Controller”: “Network View”................................ 154

CrossNET 4
 CrossNET

C.7.1 “Network View” Menu Bar ................................................. 155

C.7.2 “Network View” Tool Bar ................................................... 156
C.7.3 “Network View” Status Bar ................................................ 157
C.7.4 “Network View” Tabs ......................................................... 158
C.7.5 Automatic Notification of Device Errors............................. 190
C.8. “Dante Controller” use: “Device View” .................................... 192
C.8.1 “Device View” Menu Bar ................................................... 194
C.8.2 “Device View” Tool Bar...................................................... 195
C.8.3 “Device View” Tabs ........................................................... 196
C.9. Using “Dante Controller”: Multicast Transmit Flow Configuration
........................................................................................................ 219
C.10. Presets.................................................................................. 223
C.10.1 About Device Roles......................................................... 224
C.10.2 Saving Presets ................................................................ 224
C.10.3 Applying Presets ............................................................. 226

CrossNET 5
 CrossNET

CHAPTER 1: CHARACTERISTICS
1.1 FUNCTIONALITY

CrossNET is a compact Intercom matrix with 4 software

configurable operation keys, locate at the front panel. The keys feature
LCD displays that show the functions assigned to them. It is able to
connect to different audio and intercom systems from Kroma by AEQ, as
well as to standard audio devices.

Several versions from 40 up to 168 ports are available. Among

them, 128 can be AoIP channels, connecting easily through an Ethernet
network using off-the-shelf hubs and switches by means of Dante
protocol. It also features 12 analogue, 8 digital and 20 low binary rate
VoIP ports according to Kroma Standard, that allow the connection to
Kroma wireless intercom systems and panels from the 3000, 4000 and
5000- series.

The CrossNET matrix is available in the following versions:

- CrossNET 40: 8 Kroma digital Intercom ports, 12 balanced

broadcast quality analogue audio ports y 20 ports for compressed audio
over IP
- CrossNET 72: 32 ports with DanteTM AoIP interface, 8 Kroma
digital Intercom ports, 12 balanced broadcast quality analogue audio
ports y 20 ports for compressed audio over IP
- CrossNET 104: 64 ports with DanteTM AoIP interface, 8 Kroma
digital Intercom ports, 12 balanced broadcast quality analogue audio
ports y 20 ports for compressed audio over IP
- CrossNET 136: 96 ports with DanteTM AoIP interface, 8 Kroma
digital Intercom ports, 12 balanced broadcast quality analogue audio
ports y 20 ports for compressed audio over IP
- CrossNET 168: 128 ports with DanteTM AoIP interface, 8 Kroma
digital Intercom ports, 12 balanced broadcast quality analogue audio
ports y 20 ports for compressed audio over IP

CrossNET 6
 CrossNET

We can, then, refer to 3 types of access ports to the matrix:

- IP Ports: manages high quality, low-latency audio in DANTE

format, that is compatible with AES 67 standard, or Kroma voice-quality
compressed audio. Digital connection using 4 twisted shielded pairs, FTP
CAT5 type with RJ45 connector.
- Digital Ports: for connection with Kroma Systems featuring
Kroma Digital Intercom protocol. TP7000 terminals, TM7000 matrix ports
and also TW7000 base station wireless digital ports can be connected.
Digital connection using 4 twisted shielded pairs, FTP CAT5 type with
RJ45 connector.
- Analogue Ports: to connect Analogue Intercom systems and
auxiliary audio inputs and outputs. Analogue connection using 2 twisted
shielded pairs, FTP CAT5 type with RJ45 connector.

All models also feature a micro-headphone port accessible from the

front panel with Mini-XLR connector with mute and volume controls. A
local loudspeaker is also included for audio monitoring as well as a 1 kHz
tone generator for setup and testing convenience.
System status can be monitored through the user interface with
LCD and keyboard, located at the front, including 4 user configurable
direct crosspoint keys, as in a small local panel.
Matrix configuration is performed through an Ethernet network
using CrossMapper software running on a PC within the same network.
The matrix implemented is of “full crosspoint” type between every port
created in the configuration software.
Configuration maps loading can also be performed through the
front USB connector using a memory stick, where the cross-point maps
must have been previously downloaded to from the PC.
Power is supplied by an internal power supply with front on/off
switch. Two internal power supplies can also be equipped with redundant
supplies. The device is provided by default with a single supply, and
redundancy is left to the customer, who can optionally purchase a second
unit.

CrossNET 7
 CrossNET

1.2 TECHNICAL SPECIFICATIONS

Specifications subject to change without previous notice.

Dimmensions
RACK 1RU/19”, depth 300mm

Weight 4 Kg

Range redundant power supply

90-132V, 187-264 V
Power Supply/Consumption
50/60 Hz
Total power consumption < 24 W

RJ45 Connector(2 rear AoIP PORT/DANTE LAN)

Redundant 1 Gb/100Mb IP interface

Up to 128 Dante/AES 67 channels: 24 bit

IP Interface 48 KHz sampling, 20 Hz/20 KHz
Latency: 2ms @ 48 KHz (typical, depends on network quality and
complexity)

Up to 20 Kroma system channels. 8 bit. 8,3 KHz. B=80 Kbps.

Kroma PRTP/UDP

RJ45 connector (8 rear DIGITAL PORT)

Kroma Digital Connections 16 bit audio + control data
Kroma Intercom Protocol a 2Mb/s

Sample Rate 48 KHz @ 24 bit/sample

RJ45 Connector(12 rear ANALOGUE PORT)

Broadcast quality analogue 4-wire balanced audio
Nominal Level 4 dab
Analogue Connections
Impedance 20Ω output, 24 KΩ input
Bandwidth 20 Hz – 20 KHz
SNR > 80 dB, THD < 1% at 4 dB

“Word Clock” Type with “Daisy Chain” output in order to provide

Synchronization
Synchronization to other pieces of equipment

8 GPI through DB15 connector, +(5-24)V input range

GPIO
8 GPO through DB15 connector, contact-closure type

CrossNET 8
 CrossNET

CHAPTER 2: PHYSICAL DESCRIPTION

2.1 FRONT PANEL VIEW

Figure 2.1 CrossNET front panel view

2.1.1 FRONT USB CONNECTOR

The ‘CrossMapper” management software must be installed on a

PC and used to configure the cross point maps. This software generates
a configuration file that can be downloaded to the matrix via Ethernet port
or through the front USB interface, which is located in the left area.
A memory ‘pen drive’ device can be plugged in this port. The
configuration file must have been previously downloaded there from the
PC. Also, local file operations can be performed, such as loading and
saving maps, firmware upgrades and system log downloading.
It is recommended that the used storage device has a single
partition. Otherwise, only the first one will be visible by the unit. This
partition must be formatted with the FAT file system.
Once the storage device is plugged into the USB port, a delay of
around 5 seconds takes place until the matrix is able to recognize the pen
drive and use the information saved on it.

CrossNET 9
 CrossNET

2.1.2 POWER LED

Indicates whether the system is powered or not. If it is, the LED will
illuminate in green color.

2.1.3 CROSSPOINT KEYS

Using these keys, the user can execute several different functions
associated to the predefined communication crosspoints from the matrix
front panel. They can be configured by means of the CrossMapper or
LiveCrossMapper configuration software.

2.1.4 LCD DISPLAY

Allows the user to check the system status, interact with the several
available menus and know the labels associated to the different cross
point keys.

2.1.5 ENCODER

Navigates among the different available menu options and selects

them using its push-button. The encoder is also used when adjusting the
audio level coming from the local speaker or micro-headphones.

2.1.6 MODE KEY

Using this key, several menus available in the device can be

accessed, and once in them, go back to the matrix’s main screen.
Selection of the different options is performed by rotating the encoder
clock or anti-clockwise. The selected option is confirmed by pressing the
encoder.

CrossNET 10
 CrossNET

2.1.7 HW ERROR LED

Indicates that an error has been found during the system’s boot
process.

2.1.8 MUTE KEY

Audio is muted by pressing it. Muting is indicated by a red light on

it. Pressing again, audio is unmuted and LED will turn off.

2.1.9 HEADSET CONNECTOR

CrossNET hybrid matrix features a front-located micro-headphone

port. Its usage can be configured from the matrix configuration software.
Using the cross-point keys located at both sides of the front display,
the user can individually select which ports of the matrix will establish an
audio communication. It also features two associated green and red LEDs
that signals when the command is programmed.
Male 4-pin Mini-XLR connector located at the front of the
equipment used for headset connection. The headset input is configured
to be used with ‘Electret’ 3-5V and internal pre-amplifier. This audio
output can drive a small speaker at a maximum power of 500mW at 8 Ω.

Figure 2.2 Headset front connector pinout

CrossNET 11
 CrossNET

Listened audio level can be adjusted by means of the front panel

encoder. Volume is reduced by turning it anti-clockwise while it is
increased by turning it the other way round.

2.1.10 LOCAL SPEAKER

Allows the user to directly monitor the received audio without the
need to connect a set of micro-headphones. It can also be used to listen
to the different test tones.

2.1.11 ON/OFF KEY

The system can be turned on and off with this key. It will turn ON by
taking the switch to the lower ‘ON’ position. In order to turn it off, just take
the switch to the upper ‘OFF’ position and wait several seconds as the
system has an automatically delayed turn off.

CrossNET 12
 CrossNET

2.2 REAR PANEL VIEW

Figure 2.3 CrossNET rear panel view

2.2.1 POWER CONNECTION

The power supply connector is located at the left of the unit’s back
panel. Power supply type is universal, auto range, with 90-132V 50/60 Hz
and 187-264V 50/60 Hz input. An IEC-C13/14 type mains plug is used, as
the one depicted below:

Figure 2.4 Power supply connector

Once the power supply has been connected, just press the vertical
mains switch (located at the right of the front panel), taking it to the lower
‘ON’ position. In order to turn it off, just take the switch to the upper ‘OFF’
position and wait several seconds as the system has an automatically
delayed turn off. If the system is equipped with a redundant power supply,
the second mains plug must be connected to an alternate mains network.

NB: The equipment should be unplugged during installation. Once this

process is completed proceed to plug it to the mains.

CrossNET 13
 CrossNET

2.2.2 IP NETWORK PORT

Figure 2.5 Example of IP network port connection

These ports are labeled as ‘AoIP PORT’ and ‘DANTE LAN’, and
both of them use a RJ45 connector with the standard pinout for Ethernet
1Gbps ports.

The internal CrossNET switch, and also many off-the self switches,
are compatible with both possible pin assignments found in Ethernet
cables.

The network port must be connected to an external Ethernet port, in

order to build an exclusive LAN (local area network) for the Intercom
system devices, in order to ensure their proper operation with no audio
cuts. If traffic sharing is required with other services, QoS (quality of
service) police must be implemented by using manageable switches
(check Appendix B).

Connection between network port and switch must be made pin-to-

pin.

CrossNET 14
 CrossNET

Each port includes two LED’s providing the following Information:

• Left LED (green): activity Blinks when there is network

activity, off when there is not.
• Right LED (orange): link presence ON when connected to
network, off when not.

NOTE: Once the network port has been wired, check that its orange LED
is illuminated in order to determine whether a proper connection has been
made.

The most common wire color coding scheme is explained in the

following picture:

Figure 2.6 Ethernet network port connection cable

This is the same kind of connection to be used between the switch

and Kroma AoIP panels, TP8116 and TP8416 in particular.

CrossNET 15
 CrossNET

It is recommended to use a data wire for the local network, with 4

twisted pairs and common shield, FTP CAT6 or above Type. Max cable
length between the matrix and the switch must be 100m. Note that this
wiring can be installed with standard structured wire elements.

2.2.3 DIGITAL PORT

These ports are grouped under the “DIGITAL PORTS” silkscreen

label at the back of the unit, and they are numbered from ‘1’ to ‘8’.

Figure 2.7 Example of TP4000 terminal digital connection to CrossNET

This is the type of connection used to connect TP8116, TP8416,

TP5024, TP3016, TP4016, TP4216 and TP3216 type digital intercom
panels:

Uses RJ45 connector with the following pinout:

Figure 2.8 CrossNET digital port pinout

CrossNET 16
 CrossNET

Each matrix digital port allows to connect Kroma panels featuring

digital connection. Matrix connection is done with a pin-to-pin cable, with
RJ45 connectors at both ends, as seen below:

Figure 2.9 Digital connection cable between CrossNET digital port and Kroma panel

It is recommended to use a data wire for the local network, with 4

twisted pairs and common shield, FTP CAT5 or above. Maximum cable
length is 300 m.

Connect one end of the cable to the RJ45 port of the CrossNET
matrix (any model) and the other end to the chosen port of the panel.
Note that this wiring can be installed with standard structured wire
elements.

2.2.4 GPIO INPUTS AND OUTPUTS

These ports are grouped under the “CROSSNET” silkscreen label

at the back of the unit. Each one is identified by the ‘GPI’ or ‘GPO’ just
under the connector itself. Their pins are numbered from ‘1’ to ‘15’.

GPIO port uses SUB-D15P female connector with the following

pinout:

CrossNET 17
 CrossNET

GPI SUB-D 15 GPO SUB-D 15

PIN
FEMALE FEMALE
1 GPI1 GPO1
2 GPI2 GPO2
3 GPI3 GPO3
4 GPI4 GPO4
5 GPI5 GPO5
6 GPI6 GPO6
7 GPI7 GPO7
8 GPI8 GPO8
9 GND_GPI1 GND_GPO1
10 GND_GPI1 GND_GPO1
11 GND_GPI1 GND_GPO1
12 +5VGPIO +5VGPIO
13 GND_GPI2 GND_GPO2
14 GND_GPI2 GND_GPO2
15 GND_GPI2 GND_GPO2
Table 2.1 GPIO connector pinout

2.2.5 SYNCHRONIZATION PORT

CrossNET matrix features an external synchronization port, located

at the back of the unit under the “EXT.SYNC” label. It uses a Word-clock
type synchronization signal with Daisy Chain output, in order to easily
synchronize other devices.

CrossNET 18
 CrossNET

Uses a RJ45 connector with the following pinout:

Figure 2.10 External Sync. Port pinout

2.2.6 ANALOGUE PORT

These ports are grouped under the silkscreen label ‘ANALOGUE

PORTS’ at the back of the unit, and numbered from ‘1’ to ’12. They are
used as analogue audio inputs and outputs.

Uses a RJ45 connector with the following pinout:

Figure 2.11 CrossNET analogue port pinout

CrossNET 19
 CrossNET

These ports are used as auxiliary audio connections. In this case,

transitions to standard audio connectors such as XLR can be used.
Kroma by AEQ can provide these transitions on demand.

Figure 2.12 XLR to RJ45 transition

The pinout used for this transition is as follows:

Figure 2.13 XLR to RJ45 transition pinout

CrossNET 20
 CrossNET

XLR connector pinout is as follows:

Figure 2.14 XLR connector pinout

CrossNET 21
 CrossNET

CHAPTER 3: EQUIPMENT INSTALLATION

The system must be assembled into a 19” rack (fixing screws not
provided). Long term reliability is improved by leaving some space for
ventilation above and below the unit, although this is not strictly
mandatory as it is equipped with fans sucking air from the front and
blowing it at the sides of the enclosure. Due to the size and weight of the
system, installation on rack guides is recommended, at least in mobile
units, provided that they don’t block the cooling air exits.

3.1 SYSTEM SCHEME

CrossNET range of matrixes has been designed to interoperate

with all kind of matrixes and panels from Kroma by AEQ. This determines
a mixed architecture mixing ports where terminal points (panels) can be
installed and also ports where other external Intercom matrix or even
generic devices can be connected.
That’s why any port of the hybrid matrix can operate as a terminal
in order to connect to other external matrixes, or in matrix mode, to
provide service to panels. This flexibility allows the user to realize any
configuration map with the desired properties by using the cross-point
assignment software.

It features four connection types:

- Redundant IP DanteTM interface: Up to 160 IP ports transporting
high quality audio, such as:
o 8000-series KROMA IP intercom panels.
o Audio ports of any Type received from other equipment
supporting DanteTM interface, such as AEQ digital consoles,
AEQ Netbox interfaces, AEQ BC 2000D audio matrixes,
Kroma Conexia intercom matrixes, AEQ Olympia
commentary systems, and many other third-party DanteTM
and AES 67 compatible devices available from more than
200 manufacturers

CrossNET 22
 CrossNET

- 20 IP ports on redundant interfaces containing low-bitrate

compressed audio, compatible with legacy Kroma systems such
as:
o KROMA Panels prior to the 8000-series connected through
LAN.
o WAN-connected remote Panels.
o Wireless Belt-packs and WiFi-connected virtual panels.
o EasyNET party-line systems…and more.
- 8 digital intercom ports, compatible with Kroma digital systems, that
allow for connection of the following devices:
o Legacy 8000-series Kroma Panels
o Kroma interface cards that permit integration with other
external audio sources such as pone or ISDN lines, etc.
- 12 high-quality analogue balanced ports, valid for:
o General purpose inputs and outputs to connect to broadcast
consoles, commentary systems, PA inputs/outputs, etc.…
- A local intercom port including speaker and headset connector on
the front panel of the device.

A Brooklyn II with 64 inputs and outputs is installed from model 72

on. This chip allows, under special circumstances to use 32 extra
channels. In order to make this possible, the switching matrix has been
sized to admit up to 200 inputs and outputs.

The practical implications of this expansion are:

• Model 72 can provide support to 32 additional AoIP Dante inputs

and outputs for general purpose I/O (in other words, it will be
possible to exchange analogue or digital audio through Netbox 32,
or connect to Forum, Arena, Capitol, Yamaha mixing consoles or
any other Dante-enabled device...)
• In simple installations, as an alternative, up to 32 AoIP panels can
be added (each of them connected to another nearby panel,
instead of to the matrix). Please ask commercial or technical
services at AEQ to study the viability of using this kind of expansion
in your particular installation.

CrossNET 23
 CrossNET

The audio crosspoint map between devices is internally

implemented in the matrix. A PC will be also required for its configuration
and status monitoring.

Figure 3.1 CrossNET Interconnection example

This diagram shows CrossNET flexibility for the integration of

different broadcast-quality sound sources and destinations, connection to
other broadcast-quality intercom matrixes, to cutting-edge-technology
intercom panels, conventional and wireless panels, and also to remote
links through very diverse telecommunication networks.

The crosspoint keys will be programmed for all the panels,

independently of its type, and signaling will be applied to each key’s
LEDs, according to the command configured in each case.

Terminal equipments, either 3000, 4000 or 5000 series panels,

interface cards, or wireless base station ports, can be configured, as
Kroma digital ports are featured.

CrossNET 24
 CrossNET

Wireless WiFi beltpacks can be configured so they can operate

directly without their base stations, by means of the IP network ports
using Kroma protocol. Alternatively, the matrix can be connected to the IP
network port of another remote hybrid matrix, linking both of them through
IP ports, so effectively a connection is established between the
individually created maps.

This way, local system users can establish an audio communication

with the remote users of another Intercom system.

8000-series AoIP panels are configured in the same IP ports using

Dante protocol, except for CrossNET 40 matrix that doesn’t support it.

CrossNET 25
 CrossNET

3.2 INTER-SYSTEM CONNECTION

3.2.1 AES67 AoIP System

Figure 3.2 AES67 AoIP connection example

A Dante AoIP broadcast-quality network is represented, showing

connection to several AoIP/AES 67 DanteTM 8000-series panels. A
complete Conexia Intercom System is connected to the same network, as
well as a NETBOX32 interface, receiving audio from analogue and AES
3-digital CCU’s for broadcast sound contribution.

CrossNET 26
 CrossNET

3.2.2 VoIP System

Figure 3.3 Kroma VoIP connection example

A Kroma VoIP intercom network is shown in the figure above, also

including 8000-series and older panels, connected using their IP ports.

A WiFi wireless Xplorer system can also be connected to the IP

ports. This system can incorporate physical (beltpacks) as well as virtual
panels. The WiFi connection between the matrix and the different panels
is realized by means of the different access points, supervised by a
wireless management system.

CrossNET 27
 CrossNET

3.2.3 Redundantly wired IP system

In order to implement redundancy with the panels, either if they are

connected by means of a Dante AoIP network or with Kroma VoIP
protocol, it is absolutely mandatory that the selected network routers and
switches are able to manage loops. If they don’t include this, the network
will stop working when redundant wiring is attempted.

Figure 3.4 Redundant IP network

When the main network fails, the network devices themselves will
re-route the traffic through the secondary network, so the connection will
be reestablished in only a few seconds.

Each of the access points represented in the above schematic can

be connected to one of the available switches so we can ensure that, in
case that the main network fails, at least one of the access points is still
up.

CrossNET 28
 CrossNET

3.2.4 Kroma Digital

Figure 3.5 Kroma Digital connection example

A Kroma Digital intercom network is shown in the picture above,

using point-to-point wiring for high-quality audio. It includes 8000-series
and older panels using each one their Kroma digital port. Also, a TR5000
digital interface is connected to the digital ports, allowing for connection to
ISDN, POTS and GSM circuits.

CrossNET 29
 CrossNET

3.2.4 Analogue Audio

Figure 3.6 Analogue Audio connection example

“Analogue Audio” broadcast-quality ports allows for the connection

of analogue CCUs to contribute camera sound, audio consoles in order to
incorporate and extract broadcast audio to the intercom system, or
audiocodecs to establish remote links with broadcast quality.

CrossNET 30
 CrossNET

3.3 COMPATIBLE EQUIPMENT

3.3.1 Kroma User Panels

• TP5024: Ports: 2 digital, 1 network, 1 analogue; 24 keys with

graphical LCD.
• EP5024: Expansion 24 keys with graphical LCD for TP5024.
• TP5008: Ports: 2 digital, 1 network, 1 analogue; 8 keys with
graphical LCD.
• TP4016: Ports: 2 digital, 1 network, 1 analogue, 16 keys, 2 LCD.
• TP3016: Ports: 2 digital, 1 network, 1 analogue, 16 keys.
• EP4016: Expansion 16 keys, 2 LCD for TP4016 or TP3016.
• TP4216: Ports: 2 digital, 1 network, 1 analogue; 16 keys, 2 LCD.
Tabletop mounting.
• TP3216: Ports: 2 digital, 1 network, 1 analogue; 16 keys. Tabletop
mounting.

3.3.2 High-quality: AoIP

• 8000-Series Dante user panels

o TP8016: Ports: 1 redundant Dante+Kroma, 1 digital Kroma, 1
analogue. 16 keys.
o TP8116: Ports: 1 redundant Dante+Kroma network port, 1
digital Kroma, 1 analogue. 16 keys, 2 LCD.
o EP8116: Expansion 16 keys and 2 LCD for TP8116, TP8132,
TP8016 or TP8032.
o TP8316: Ports: 1 redundant Dante+Kroma, 1 digital Kroma, 1
analogue. 16 keys. Tabletop mounting.
o TP8416: Ports: 1 redundant Dante+Kroma network port, 1
digital Kroma, 1 analogue. 16 keys, 2 LCD. Desktop version.

CrossNET 31
 CrossNET

• Other Dante-compatible systems CrossNET System can Exchange

broadcast-quality audio channels with:
o AEQ Netbox32: 32-channels analogue audio + 1 AES-EBU
dual.
o AEQ Netbox8: 8-channels analogue audio + 1 AES-
EBU/USB dual interface.
o AEQ-Netbox4: 4-channels analogue audio + 1 AES-EBU
dual + 1 AES-EBU/USB dual.
o AEQ BC 2000D: Router (to 5000x5000 crosspoints)
o AEQ Olympia: Commentary System
o Kroma Conexia: Intercom System (to 1000 ports).
o AEQ Broadcast Consoles: Arena, Forum, Forum IP, Capitol
IP
o Dante/AES 67: Other third-party devices from more than 200
different manufacturers

3.3.3 Voice quality: VoIP

• Xplorer: Wireless Intercom System

o Xbp Terminal: Wireless beltpack with 4 physical keys and 16
on screen.
o Xvirtual App: License for the Virtual Panel Applications
available for Windows or iOS. Creates a 16-keys intercom
panel in the screen.

• Wireless beltpacks
o BP5004: wireless beltpack with 4 physical keys.
o BP3004: IP wired beltpack, 4 keys

• Interface cards
o TA7000X01: 4-ports 4-wire audio card (transformer-isolated)
TA7003X01: 4-ports 2-wire audio card (transformer-isolated)
o TA7002X01: 2-ports Telephone line interface card
o TD7000X01: 2-ports ISDN line interface cards (G711
protocol)
o TD7001X01: 1-port GSM interface card

CrossNET 32
 CrossNET

• Digital Interface racks

o TR7000R01: Interface rack for up to 6 cards. 19”, 3U-height.
o TR5000R01: Interface rack for up to 2 cards. 19”, 1U-height.

• IP Audiocodecs and RDSI

o AEQ MERCURY: One channel IP.
o AEQ VENUS: Two channel IP.
o AEQ VENUS 3: Two channel IP with optional Dante AoIP
connectivity.
o AEQ STRATOS: Two channel IP or RDSI.
o AEQ STUDIO: Two channel IP or RDSI.

• IP Kroma Linkers
o IL5004R02: IP Linker, featuring 4 analogue, 4 digital and 4 IP
ports. 19” 1U-height.
o IL5008R01: IP Linker, featuring 4 analogue, 8 digital and 8 IP
ports. 19” 1U-height.
o IL5016R01: IP Linker, featuring 4 analogue, 16 digital and 16
IP ports. 19” 1U-height.

• Headphones for panels, base stations and beltpacks:

o 732-014-183: MC 7000X07 Kroma earphone
o 732-014-180: MC 7000X09 mono headphone with
microphone.
o 732-014-181: MC 7000X10 stereo headphone with
microphone.
o 732-014-182: MC 7000X011 enclosed stereo headphone
with microphone.
o 732-014-214: MC 7000X012 enclosed mono headphone with
microphone.

CrossNET 33
 CrossNET

• Headphones for virtual panels (4-pole 3.5mm minijack connection)

o 732-014-219: MC 7000X29 mono Ipod headphone with
microphone.
o 732-014-220: MC 7000X20 stereo Ipod headphone with
microphone.
o 732-014-221: MC 7000X21 enclosed Ipod stereo headphone
with microphone.
o 732-014-222: MC 7000X22 enclosed Ipod mono headphone
with microphone.

CrossNET 34
 CrossNET

CHAPTER 4: DANTE CONTROLLER

PRECONFIGURATION

In order to control the system, the “Dante Controller” must be

running on a PC.

This chapter provides some simple and concise steps for the
correct pre-configuration of the “Dante Controller” software. Please read
appendix C of the present manual to obtain a deeper explanation.

4.1 “Dante Controller” Installation

Please have in mind the minimal requirements to be met to ensure proper

application operation before starting its installation. These requirements
are specified in Appendix C of this manual. In order to get more detailed
information about the installation procedure of “Dante Controller”, please
refer to the mentioned appendix.

“Dante Controller” can be obtained in two ways:

1. Together with the system: its self-boot disc includes the

executable file that installs the software.
2. By downloading it from the Audinate web site.

Install the application following the steps detailed in Appendix C,

and perform the required preliminary configurations, also detailed in the
same appendix.

CrossNET 35
 CrossNET

4.2 Using “Dante Controller”

This application is used to pre-configure the audio connections

between matrix and panels.

We will use the following example to focus Dante Controller’s

usage explanations: a CrossNET matrix connected to two TP8116 and
one TP8416 panel.

The first step to follow is correct selection of the Word Clock, as if it

is not present or properly configured, our device won’t work adequately
and some audio information will be lost. Clock status can be checked in
the “Clock Source” tab in the program. This tab will allow us to change
what is required for a proper operation. For this example, the matrix itself
will be chosen as the clock master, and, in turn, it will sync to an external
reference clock.

We will now focus on the Routing tab, where the channels

subscriptions can be made.

Transmission channels of each device are represented in the top

row, and those with receiving channels are located along the leftmost
column. Both CrossNET and Intercom panels are transmitting and
receiving devices at the same time.

By default, devices are represented in “Dante Controller” by their

name followed by their serial number. This way, in our example, we will
see CROSSNET-81642 matrix, connected to panels TP8116-80410,
TP8116-80420 and TP8416-80480.

Each device can be unfolded so all channels can be seen. Have in

mind that intercom systems use mono communications, so for example
channel 1L is routed to a different panel than 1R. Usually, only the left
channel of each panel is connected.

CrossNET 36
 CrossNET

Transmitters

Receivers
Figure 4.1 Routing View

In order to subscribe a receiving channel to a transmitter one, a

blue box must appear in their intersection, indicating that it is possible to
establish an audio routing between them. If, on the other hand, the box is
grey, this indicates that it is impossible to establish an audio connection
there. The first receivers (names as –L) of each panel must be subscribed
to the CrossNET transmitters. The first panel’s first port (L), to
CrossNET’s first port (1L), the second panel’s first port (L) to the second
port of CrossNET (1R), and so on.

Just in the same way, channel L of each panel transmitters must be

connected to the matrix receiving ports. That is, TP8116-80410 first
channel, L, to CROSSNET-1L, TP8116-80420 L to CROSSNET_1R, and,
finally, TP8416 L to CROSSNET_2L.

It is important to insist that Intercom audios are mono, so in normal

conditions a single panel channel must be connected to a matrix channel.
The second one can be used to connect to a second matrix,
simultaneously, or to redirect a panel port (for example, the analogue
one) to the matrix, as if it was an independent auxiliary audio, if required.

CrossNET 37
 CrossNET

The subscription will be effectively made when right-clicking on the

blue square. A green tick mark will appear on that cross point. There are
another states associated to the crosspoints subscription, that can be
seen in detail in Appendix C of this manual.

Our example will be configured this way in “Dante Controller”:

Figure 4.2: View of the cross-point pre-configuration between matrix and panels

In order to cancel a subscription, just click on the cross point

formerly containing it. The tick icon will disappear and the cross point will
return to its initial state (blue box).

When the mouse pointer is on the cross-point, a hint will appear

showing information about the subscription made. The different text
messages that may appear in this window are detailed in the appendix.

CrossNET 38
 CrossNET

Figure 4.3 Port Information detail

Once all the panels’ L channels are properly connected to the

matrix, both for transmission and reception, all the connections will be
pre-configured, and they are ready to be used from the CrossMapper
software as explained in Chapter 5 of this manual.

CrossNET 39
 CrossNET

CHAPTER 5: FRONT PANEL OPERATION

The ‘CrossMapper’ software configures the audio crosspoint

maps. Once a map is created the users have different uploading
possibilities: through a USB device, through an ‘On line’ connection via
PC through an IP connection using one of the net ports.

Using the net option gives the users a more flexible approach as it
means a total control over the system without the need to use menu
options. It also allows ‘On line’ work on the maps (direct modification of
the crosspoints of an active map).

The matrix features two user interfaces at the front: a LCD display
and a key-board for system management and status checks. Also, the
interfaces allow the users to create crosspoints and to control the local
audio.

The functionalities of the menu’s keys are as follows:

- : It validates a given option or scrolls on a menu.

- : It cancels a given option or reverts to the previous menu.

CrossNET 40
 CrossNET

5.1 MENÚS

The home menu presents information on the current active map

and displays the time of the system.

Figure 5.1 First Screen shot of the LCD

The display shows in the corners, the labels of the crosspoint keys
(those crosspoints that have been previously defined with the
CrossMapper software). The second line shows the model of the matrix.
In the third line on the left there is information on the time. Following that
line, there is an ‘S’: if the local speaker is active or an ‘H’: if the active one
is the micro-headset at the front. On the right there is the name of the
current active map.

NOTA: It is possible to commute between the local speaker and the

external micro-headset from the home menu by pressing the encoder.

Press the encoder key once to access the ‘Options Menu’. The first
option: ‘Speaker On’ commutes between the local speaker and the
external micro-headset when the users press the encoder. When the
micro-headset is selected the text indicates ‘Headset On’.

Figure 5.2 Menu selections to switch between headset/speaker

The second menu: ‘Map Management’ manages the system’s

maps. The third menu: ‘System Status' offers information on the status of
the system. The forth menu: 'Time/Date' is used to set the time of the
equipment. The fifth menu: 'Engineering' is used for software updates,
modification of net parameters and events log.

CrossNET 41
 CrossNET

Figure 5.3 Operation menus

Once in the ‘Map Management’ option, the system displays the

following 4 sub-menus:

Figure 5.4 Maps management sub-menus

The Maps management allow the below actions:

• Active Map it activates a map among the 8 that can be stored in

the banks. Press the encoder and select the bank with it; finally
press the encoder again. Press the mode key to revert to the
previous sub-menu.

Figure 5.5 Bank selection

• Load Map it loads a map using a USB device. Press the

encoder, select the file to upload and the bank of destination and
press again the encoder. If there is a map already, the new bank will
replace the old one.
Erase Map it deletes a map stored in one of the 8 banks. Select
the bank with the encoder and press it to erase the map selected.
• Backup Map it saves a stored map in the disc drive of a USB.
Select the bank that has the map stored (with the encoder) and
press it. A USB device has to be plugged in.

CrossNET 42
 CrossNET

The sub-menu ‘System Status’ allows monitoring of the status of all

equipment in the system. Press the encoder to access it. It gives info on
the port number, on the label associated to that port and of the type of
terminal and current system status. It uses the below labels:

• OK port working correctly. The % informs of the quantity of

frames streaming without errors. A quantity over 95% is considered
as correct functioning, as the equipment does a time weighed
average.
• Warning this message appears when the type of panel
associated to the port (defined by software) is not the same that is
actually been detected by the matrix. If this message appears, in
order to prevent mal-functioning, the whole installation together with
the defined ports in the configuration maps, must be checked.
• Error this message appears when the defined digital port is not
connected or when there is a problem with the connecting cable. %
informs of the quantity of frames streaming without errors.

Figure 5.6 Example of the status of the digital ports

In the above example, the defined panel in the Port 1 is not

detected; it can be either off or mal-functioning.

The sub-menu ‘Time/Date’ is used to set the time and date on the
system, useful feature on the configuration maps. Select the ‘Time/Date’
option on the home menu. The values can be modified using the encoder,
and pressing it to validate new values. To go back use the mode key.

Figure 5.7 Time and date sub-menu

CrossNET 43
 CrossNET

The sub-menu ‘Engineering’ is used to modify: net parameters of

the system, firmware upgrades, and activation and saving of registers on
the system’s log events. The system will ask for a password to access
this sub-menu.

Figure 5.8 Access password to the Engineering menu

The access password to the engineering menu is “3210”. To input

the code, use the encoder and change the digits. By pressing the encoder
the new digit is validated. The mode key goes back to the previous digit.
Once the code is accepted by the system, it will display the engineering
menu.

Figure 5.9 Engineering menu

See the available options below:

• Network Config it allows changing the IP address of the matrix,

as well as changing the subnet mask and the default gateway.

Figure 5.10 Engineering menu

To change the IP address: use the encoder to change the current

value, press it to validate the new value; use the mode key to go
back to the previous value. Once the IP address is validated, the
system requests the subnet mask (IP mask) and lastly the default
gateway (change those using the above described procedure).

CrossNET 44
 CrossNET

• Firmware Update it allows firmware updates for the equipment.

Use a Pen drive or similar to upgrade the firmware version.
• O.S. Update it allows updating of the system’s operative system.
Use a USB device to update the new version.
• Master Version it shows the current firmware running on the
equipment.
• Reset it resets the equipment software, while keeping current
configuration.
• Log Events activates (ON) or deactivate the log event
• Save Log to disk it saves the system’s log events onto a USB
device (plugged to the front USB connector). This option is available
only if the Log Events option is active (see the above menu option).

5.2 AUDIO KEYS AND CROSSPOINTS

The matrix has 4 crosspoint keys located in both sides of the LCD
display. The functions of the keys are defined on the configuration map
with the CrossMapper software.

Each key has two signaling led’s that illumine the keys: one red and
one green. Those led’s indicate the status of both the key and the
associated crosspoint (following the standard Kroma by AEQ color-code).
The associated labels to the keys are represented on the display corners.

Active key fixed green light

Inactive key inactive green light
Non-established crosspoint inactive red light
Crosspoint in Listen mode flicking red light
Crosspoint in Talk mode fixed red light

CrossNET 45
 CrossNET

Figure 5.11 Crosspoint keys

The Levels of local audio are controlled with the keypad located
near the headset port.

Figure 5.12 Local audio control keys

• Encoder turns the volume up on the speaker and on the

micro-headset.
• Encoder turns the volume down on the speaker and on the
micro-headset.
• Mute key mutes the audio of the micro-headset. Mute is
indicated with the red light on the key.

CrossNET 46
 CrossNET

CHAPTER 6: SOFTWARE

CrossMapper’ application creates and edits configuration maps for

all Intercom systems offered by Kroma by AEQ. It allows the user to
configure the matrixes, register the different installed pieces of equipment
and assign the actions to perform by means of commands that will be
executed.

The user declares the type of system and matrix, together with the
terminal panel models and link interface they have, before defining the
commands that will determine which crosspoints to make.

This software is provided in a CD-ROM together with the system

hardware, and can be run in all Windows platforms.

6.1 INSTALLATION

Once the provided CD-ROM is inserted in the PC drive, find

\Software\Setup.exe (in the currently available version) and double click
on this file with the left mouse button to star the setup program.

Figure 6.1 Software installation first step

CrossNET 47
 CrossNET

After that, click on the ‘Next’ button, and select the destination
folder where you want to install the program. By default, a new folder
named .\kroma Telecom\ will be created under the ‘Program Files’
Windows folder.

Figure 6.2 Selecting the destination folder for the installation

Next step consists on selecting the name for the Start Menu folder
where the program will appear. By default a program group called ‘kroma
Telecom’ will be generated.

Figure 6.3 Naming the program group

A shortcut in the PC desktop can be created when you click on the

‘Next’ button again.

CrossNET 48
 CrossNET

Figure 6.4 Icon name

A software installation summary report will appear once validation

is provided with the ‘Next’ button. Actual installation will start when the
‘Install’ button is clicked.

Figure 6.5 Summary and Installation start

CrossNET 49
 CrossNET

Once the required files are copied to the selected folder, the
program will inform that the installation has successfully concluded, and
the software can be executed right after that.

Figure 6.6 Installation completed

If an old installation of the program is detected in the same

destination folder, the new one will overwrite it. Once installed, the
application can be run from the CrossMapper shortcut, or alternatively
going to the Start Menu and finding ‘Start → All Programs → Kroma
Telecom → CrossMapper’.

CrossNET 50
 CrossNET

6.2 MENU OPTIONS

If, once open, a password is requested by the program, just Type

the default Word KROMA. This key can be modified by the user or even
voided so it is required never again.

Quick
Menu Programming
bar
Main toolbar
Editing bar

Map window
Active map Matrix connection
indicator
Figure 6.7 Initial screen

This initial screen shows a series of drop-down menus, shortcut

buttons and Information About the maps currently been realized. The next
pages detail all the available actions.

CrossNET 51
 CrossNET

6.2.1 Menus

MENU “File”

Allows for the creation of new maps, saving them, opening existing
ones, printing the current configuration together with the associated
labels, or changing the password, among other things.

Figure 6.8 ‘File’ drop-down menu

CrossNET 52
 CrossNET

The available options are:

• New creates a new map file.

• Open opens a *.kmp file corresponding to an already existing
disk file.
• Close closes the current map file.
• Save stores the current work map with the previously defined
name.
• Save As stores the current work map with a new name defined
by the user.
• Print prints all the Information corresponding to the map
currently being programmed on a text format.
• Print Labels print the panel labels selected by the user, so they
can be cut and placed in the transparent crosspoint keys.
• Print Preview preliminary view of the printing, allows the user to
display the text configuration file before sending it to a printer.
• Print Setup configures the print options and parameters of the
printer to be used.
• Options allows for the setup for the matrix IP parameters. At this
point, only the IP address is specified, but connection is not actually
made. ‘On Line’ control is explained later on. This option also
allows the modification of the initial password in another tab.

Figure 6.9 ‘Options’ submenu

CrossNET 53
 CrossNET

• Send Sends the current configuration map to an e-mail address.

• Exit closes the application.

In order to modify the password, just select 'Options' and then click
on the ‘Change Password’ tab. The current password must be typed in
the corresponding field, and then the new one must be filled in twice to
confirm. After that, the new password will be applied.

Figure 6.10 Modifying the password

NB: If only the current password is filled in but both other fields are left
blank, the current password will be voided when clicking on the 'Apply'
button so it is not required again.

CrossNET 54
 CrossNET

MENU “Edit”

Allows the user to register new ports, groups, phone numbers to

program, IFB's, properties and assign audio levels between crosspoints. It
facilitates the creation of configuration copies between similar terminals
and the activation of the quick programming function as well.

Figure 6.11 ‘Edit’ drop-down menu

CrossNET 55
 CrossNET

These are the available options:

• Undo go back, voiding the last step made.
• New Port registers a new port in the configuration.
• New Group registers a new group of ports in the current
configuration map.
• New Dial registers a new dialing number that will be used to
make calls through the interface cards
• New IFB (Interrupt FoldBack) creates a new interruptible
crosspoint. These crosspoints have a special feature that allows
them to be interrupted by software events or pressing other keys.
• New Conference creates a new Conference room where the
system users can enter for talking and/or Listening.
• New Beltpack Role creates a new key configuration for wireless
beltpacks that can be assigned later on to physical beltpacks from
their configuration in CrossMapper or the beltpacks themselves.
• New External Matrix registers a Kroma by AEQ audio matrix in
the system for the smart connection of the local matrix with the
remote one.
• Remove deletes the port currently selected by the cursor,
excluding it from the current configuration map, together with its
label in the rest of ports.
• Properties allows for the edition of the Properties of the resource
that is currently selected in the active configuration map view.
• Audio Levels allows for the configuration of the system
crosspoints’ audio Levels, as well as for each port’s inputs and
outputs (in systems supporting this function).
• Copy Configuration allows the user to make a key configuration
copy between two panels of the same type in order to speed up the
configuration of panels with similar key layouts.
• Quick Programming activates the quick Programming of
commands to keys for a quicker configuration. This is performed
from the main window.
• Matrix Interconnection Allows the user to import maps from
another Intercom system in order to subsequently interconnect
them.

CrossNET 56
 CrossNET

MENU “On Line”

By means of this option, direct connection can be established with

the intercom system, in order to manage maps, activate cross points, etc.

Figure 6.12 ‘On Line’

These are the available options:

• Connect to Matrix connects to the system matrix. This is the first
option to activate before going on with the rest of on line menus, as
those depends on the existence on active connection.
• Open Map from Matrix retrieves a map from the matrix. One
map can be loaded in the configuration software in order to be able
to modify it. This map can be in any of the several possible map
banks stored in the system.
• Save Map to Matrix once the working map has been modified, it
must be sent to the Intercom system so it is stored in one of its map
banks
• Update Current Map updates the active matrix map (if
connected). This operation not only downloads the map that is
actually in the CrossMapper on the active matrix position, but it also
activates it to become in use immediately. This option preserves
the communications already established with the matrix.
• Activate Map activates a map stored in a bank, so it is executed.
• Delete Map erases a map stored in a bank when it is no longer
need.
• System Status allows the user to monitor the whole Intercom
system programmed in the currently active configuration.

CrossNET 57
 CrossNET

• Crosspoint accesses monitoring, activation and deactivation of

crosspoints across the system. These crosspoints have higher
priority than the ones made from the panels.
• Date/Time Synchronization updates the Master current time from
the currently connected PC clock.

MENU “View”

Allows the operator to show or hide the tools and status bars.

Figure 6.13 ‘View’ drop-down menu

MENU “Window

This option permits the selection and arrangement of the

configuration map windows open in CrossMapper.

Figure 6.14 ‘Window’ drop-down menu

CrossNET 58
 CrossNET

MENU “Help”

This help provides guidance on how to use the application, and

allows the user to search among the different topics addressed. Also, the
software version of the running CrossMapper application can be
consulted in the About CrossMapper option.

Figure 6.15 ‘Help’ drop-down menu

6.2.2 Tool bars

Besides the above mentioned menus, shortcut icons implementing

some of their options can be found. The main toolbar comprises a variety
of map file operations, such as open, close, etc., as explained below.

Figure 6.16 File icons

In the editing bar, some icons associated to the creation and

configuration of ports can be found, which perform different actions.

CrossNET 59
 CrossNET

Figure 6.17 Maps icons

The function of each icon will be shown as a hint in English when

moving the mouse pointer over it.

The quick programming bar allows for the programming of panel

keys. First, choose the command to perform, source and destination of
the action and associated label, and, after that, select panel key to
program. This option must be previously activated in this bar's left icon.

Source port Label

Command type Destination port

Figure 6.18 Quick programming

CrossNET 60
 CrossNET

Quick programming can be activated only when a panel with

programmable keys is selected. Once the “Quick Programming” checkbox
is checked, selection of a new visible panel in the current document is
prevented until it is unchecked again. When the option is activated, by
only clicking the left mouse button on a key from the visible panel, this will
be automatically programmed with the command, source and destination
selected in the tool bar. A port is automatically assigned as the
destination port in the toolbar when it is selected in the current
document's resource tree view.

Besides these bars, a status bar can be found at the bottom area of
the screen showing the following pieces of information:

Connected matrix IP

Indicates the currently active Indicates the matrix connection status:

matrix bank (from the 8 existing
Red: Disconnected
ones), as well as the map
name Green: Connected
Figure 6.19 Status bar

6.3 MATRIX CONFIGURATION

The first step to perform in order to set the Intercom system up, is
to create a new map in the ‘File New’ menu, or by means of this
shortcut icon: Create new map.

‘CrossMapper’ configuration software allows you to work on

different Intercom systems, so the user must first select the actual system
to operate:

CrossNET 61
 CrossNET

Figure 6.20 Intercom system selection

Once the system is selected, next the type of crosspoint matrix must
be chosen:

• Conexia Intercom system comprising a Master control unit, plus

a number of crosspoint matrixes up to 1024 ports.
• CrossNET Hybrid Intercom System that can feature VoIP
connectivity, built on a 1U-high 19” unit, including control and
crosspoints.

CrossNET 62
 CrossNET

• TH5000 hybrid Intercom system, made from a 1U-high matrix

unit, managing both control and crosspoints.
• TB3000 low cost Intercom system, comprising a Matrix unit.
Includes 4-wire analogue ports and digital ports.
• TW5000 beltpack WiFi base station: allows for the autonomous
control of BP5004 WiFi beltpacks without the need of a matrix.
NB: The explanations in this manual will focus on the CrossNET hybrid
system, leaving the details about other kinds of systems for their
corresponding user manuals.

Once the proper system has been chosen, the matrix type must be
indicated in the bottom area, by means of the “Matrix Type” drop-down
menu. The exact family number is selected here. This decision is usually
driven by the number of ports in the system or matrix.

NB: If the system includes a matrix with ports count lower than the one
selected in CrossMapper, the configuration map may become unstable
and cause operating faults.

A descriptive text for the matrix can be typed in at the available text
field.

Configuration is validated and a new work window will show up by

clicking on the “OK” button. Once a new map is initiated, a panel or I/O
interface model can be assigned to each matrix port. These will be the
system terminal points.

CrossNET 63
 CrossNET

6.4 PORTS CONFIGURATION

Figure 6.21 New work map

The leftmost window presents the map being edited, together with a
series of associated features such as the ports and their properties. If the
ports are disclosed, the description for each one will appear in the window
at the right.

The characteristics of the shown ports are: number of the physical

port where it is connected to the matrix, mnemonic to be used in the key
assignment, a brief description (in brackets, besides the mnemonic), and
an icon where the kind of terminal (panel or interface) can be seen.

CrossNET 64
 CrossNET

Figure 6.22 Declared ports listing

These are the displayed port characteristics:

• Physical port number where the matrix is connected to.

• Easy-to-remember name to be used for the key assignment
(mnemonic)
• Short description (optional, displayed within brackets next to the
mnemonic)
• Icon where the kind of terminal (panel or interface) can be
displayed.

In order to create a new port (terminal) in the map, the user must
go to the ‘Edit New Port’ menu or click on the shortcut shown
below.

In order to unregister an existing terminal in the map, just go to the

‘Edit Remove’ menu option or click on the shortcut shown below .

CrossNET 65
 CrossNET

A descriptive name (mnemonic) must be declared for each added

element, which will be used during the command configuration. This
name can be up to 12 characters long, but it may be reduced depending
on the number of characters that each unit can represent.

We will have several different kinds of ports as a function of the

matrix family we are configuring. Each one has its own characteristics
and compatible terminals:

• Digital Ports (Digital) Digital panels, input/input ports (analogue,

digital, telephone, etc.), IP systems (via IL5000 linker) or TW5000
base stations (this is transparent to the matrix configuration, as
they are simply seen connected to the digital port) or audio link
interfaces can be connected here.

• Analogue Ports (Analogue) Analogue audio systems can be

connected here. These are generic 4-wire balanced ports to
connect any other audio system working in this format.
• AoIP network ports 8000-series panels can be connected
through high-quality, low latency Dante format audio links.
• VoIP network ports TP3000, TP4000, TP5000, TP8000 series
panels, Xplorer WiFi wireless beltpacks, Xbp and VP9000 (without
base station) can be connected here or, alternatively, connection to
another matrix can be provided via a VoIP link.
• Microphone Port (Headset) Matrix front panel configuration
where a micro-headphone with microphone input and headphone
output can be connected.

• Tone Virtual port where a 1KHz is injected, that can be routed to

any system port (very useful during deployment and testing of the
system

The terminal equipment model to be connected can be selected for

each port from the available list. The user must identify the system that
will be attached to that port and give it a descriptive name. From then on,
it will be part of the map.

CrossNET 66
 CrossNET

By clicking on the ‘Panels’ upper button in the new port window,

terminal panels that are compatible with the selected port will be listed.
The lower ‘I/O Ports’ button, on the other hand, shows the compatible
audio interfaces. Using the ‘Matrix Interconnection’ button, the matrix
interconnection smart devices appear.

NB: It is mandatory to register in the software exactly the same model of

terminal that is physically connected to the matrix port, otherwise an
anomalous operation of the crosspoint assignments will occur.

Figure 6.23 Available ports for connection

CrossNET 67
 CrossNET

The parameters that can be configured for each piece of equipment

are:

• Type: we will be presented a listing of the available panel types

that can be connected to our system in the present port by
selecting the “Panels” drop-down menu. If the “I/O ports menu is
deployed, we will see a listing of the interface cards that can be
connected, and in “Matrix Interconnection” we will see a list of the
available matrix-interconnecting ports.
• Name: the mnemonic that will identify the equipment in the system.
This name is up to 12 characters long and will appear on the
panels' programmable keys labels.
• Short Description: short description (12 characters long) that will
appear in brackets in the CrossMapper tree view to help in the
identification of the equipment.
• Full Description: Description or commentary about the equipment.
• Port: physical port where the equipment is connected. It can be
analogue, digital, network, microphone or tone generator
depending on the matrix family we are configuring.
• IP Address: IP address of the equipment (only for network ports).
• Full BW: allows the user to enable or disable the continuous
sending of audio. If this option is unchecked, the port and matrix
will only send voice data when the audio is above a certain fixed
threshold. If it is checked, on the other hand, audio will be sent
continuously (only for network ports).
• Remote Connection: enables remote connection of ports with
gateway equipment such as IP IL7004 linker (obsolete) or ISDN
bridge by means of TD7004 cards. When the corresponding option
is enabled, the matrix-side and terminal side ISDN numbers can be
configured, or IP addresses in the case of TD7004 links.

CrossNET 68
 CrossNET

6.5 GROUPS

The software allows the user to group several ports in a single

group, so it is possible to establish communication with all at a time or
even change their audio levels, by associating that group to a key. In
order to do that, the group must be first registered and, then, the ports
that it is composed of should be defined.

A new group is defined in the ‘Edit New Group’ menu or by

means of this shortcut icon . A descriptive name must be given to the
group.

Figure 6.24 New group assignment

CrossNET 69
 CrossNET

Next, the parts composing that group must be assigned. In order to

do that, the group resource created must be edited, then the group name
must be selected at the left window. After that, find the ‘Edit
Properties’.

Figure 6.25 Group members editing

The name of the group being modified appears in the group

members editing screen, together with two separate ports lists in two
columns. The available ports that can become part of the group are
presented at the left, while the current members are listed at the right.

In order to add a member to the group, the port must be selected in

the left window and then validate it with the ‘Add’ button. In order to delete
a port from the group, just select it in the right window and click on the
‘Remove’ button. Once all the desired changes are made, close the
dialog with the ‘Close’ button.

CrossNET 70
 CrossNET

When a key is configured as a command to talk to a group, all that

group members will listen to this user when the key is pressed, in a ‘party
line’ fashion. Groups prove very useful when one wants to talk to several
people at the same time by pressing only one key.

6.6 CONFERENCES

Conferences, which will behave as dynamic ports that have no

initially associated members, can be defined. Keys can be programmed in
the panels to talk and listen to the conference, so that when making talk
to a conference, all pieces of equipment performing a listen to it will hear.

A new Conference is defined in the ‘Edit New Conference’

menu, or by means of the shortcut icon . The conference must be given
an identifying name.

Figure 6.26 New Conference assignment

CrossNET 71
 CrossNET

Next, a name must be given to the Conference. This name can be

modified later on by editing the create resource, selecting the conference
name and going to the ‘Edit Properties’ menu

Figure 6.27 Editing a conference’s name

Conferences are available as destinations during the programming

of panel keys. Audio commands with conference destination can be
programmed (Talk, Listen, Dual Talk & Listen and Talk & Listen).

Once the conference has been defined, let’s program the panels
that will access to it. We must open the configuration of the key that we
want to program towards the conference, and we will be able to define for
it a talk, listen, talk & listen or dual talk & listen command, with the
conference being the destination.

6.28 Assigning a Dual Talk and Listen command to a conference

CrossNET 72
 CrossNET

6.7 BP5000 BELTPACK ROLES

BP5004 wireless beltpacks can be defined in the system in two

different ways:

• As normal terminal equipment, bonded to a matrix physical port,

which keys are programmed normally.
• As a system without initial configuration, so the configuration can
be assigned from a list of pre-configurations (roles) when starting
the beltpack up.

Working with roles allows the operator to substitute a beltpack by

another one in case that the battery is drained, the beltpack develops a
fault, etc., without the need to change the configuration or IP address of
the new system in the configuration map.

In order to define a Beltpack Role, chose the “New Beltpack Role”

option from the Edit menu, or click on this shortcut icon in the editing
bar: .

Figure 6.29 New beltpack role

CrossNET 73
 CrossNET

A name must be assigned, that will identify the new role. This name
can be changed later on by selecting the resource and opening its
properties:

Figure 6.30 Assigning a role name

The newly defined role will appear in the resource tree of the map
window. Clicking on it, we will see the role configuration in the right
window area, and now the keys can be programmed as if it was a normal
beltpack assigned to a port.

Figure 6.31 Role configuration

Last, we need to define the real beltpacks that could be connected

to the system, defining its port and IP address (if required).

CrossNET 74
 CrossNET

When configuring a real beltpack in a system, we can select the

mode it will work in with respect to the roles. Three operating modes can
be defined:

• FREE: the beltpack won’t work with roles. Its key configuration
must be performed in the system itself, as with any other panel.
• UNASSIGNED: the beltpack has no role assigned by configuration
map. When it starts up, a listing of free roles will be shown so the
user can choose which one the beltpack will work with.
• DEFINED ROLE: the beltpack will always have the role selected in
the map.

Figure 6.32 Defining the beltpack operating mode

CrossNET 75
 CrossNET

6.8 IFB’S

IFB’s (Interrupted Foldback) can also be programmed. They are

crosspoints assigned between a source and a destination that are
interrupted by an event, with the possibility of having its level changed.
There are two different types:

Direct IFB’s These are the IFB’s assigned between several

sources and a single destination, which are interrupted when a call from a
different source enters to the same destination. It could be said that
inputs assigned with Direct IFB are temporarily cut to that output. When
that last incoming communication is released, the IFB input crosspoints to
that destination that was busy are restored.

Figure 6.33 Direct IFB’s example

The example depicted in figure 6.33 shows several direct IFB’s

assigned between several inputs and an output. If output 1 is carefully
observed, you can check that, during the normal operating mode, this
output listens to inputs 0 and 2 (left image), as they have direct IFBs
assigned. But, when input 3 wants to talk to output 1, inputs 0 and 2 are
temporarily interrupted (right image), and this output will listen to input 3
only, until communication with this input ends and initial status is returned
(left figure). At that point, output 1 will listen to inputs 0 and 2 again

CrossNET 76
 CrossNET

Inverse IFB’s These are the IFB’s between a source and

several destinations, which are interrupted when a call is answered by
any destination to that source. We could say that outputs assigned with
inverse IFB are temporarily cut with that input, except for the output that
called that source. When this last communication is released, the IFB
input crosspoints to all outputs are restored.

Figure 6.34 Inverse IFB’s example

The example of figure 6.34 depicts a situation where several

inverse IFBs are assigned between an input and several outputs. If input
1 is carefully observed, we can check that, during the normal operating
state, outputs 0, 2 and 3 listen to input 1 (left image), as they have and
inverse IFB assigned. However, when input 2 wants to talk to output 1 (a
call is forced, for instance), outputs 0 and 3 become temporarily
interrupted (right image), listening only to inputs 1 and 2, until input 2
communication is released and the system returns to the normal
operating state, where the outputs start listening input 1 again (left figure).

A new IFB can be added in the ‘Edit New IFB’ menu or by

means of the following shortcut icon

Next, a dialog box will appear in order to make the desired

assignment between a source and a destination port.

CrossNET 77
 CrossNET

Figure 6.35 IFB assignment

For each IFB created the user must specify whether it is inverse
and/or direct, according to the criterion explained above, although in the
cases Fix and Clear this distinction is not made, as they are crosspoints
that are permanently locked or forbidden.

These are the available IFB types:

• Fix Fixed crosspoints that are established from the start and
remain always active between a source and a destination. They
cannot be interrupted by any call.
• Cut They are crosspoints that are temporarily interrupted when a
call enters that affects that crosspoints. Direct IFBs of this kind are
also known as ‘standby’, as inputs are temporarily cut to an output.
Inverse IFBs are however called ‘inverse standby’, as the outputs
are temporarily cut from a same input.
• Cut attenuate Its function is the same as the above explained
Cut, but the communication is not completely cut, but attenuated by
a selected dB amount.

CrossNET 78
 CrossNET

• Clear Forbidden crosspoints that are established from the start

and always remain inactive between the source and destination.
They are crosspoints which will never be realized.

A name that identifies the IFB in the system can be given to it, or
assigned to a panel key so that, when it is pressed, the programmed
action will be executed on the IFB assigned destination.

The source and destination can be left as UNASSIGNED, so that

they can be assigned later on in real-time from the LiveCrossMapper
software.

In order to remove an existing IFB from the map, the IFB section
must be selected in the left column. Then, mark the IFB to be removed in
the list at the right, and, after that, just click on the shortcut icon shown
below under the ‘Edit Remove’ menu .

6.9 DIALS

Dials are the phone numbers, URIs or IP’s assigned to labels that
will take part in the system configuration, either in order to make outgoing
calls to that numbers, or to allow them to enter as external incoming calls
to the intercom system. It is a sort of agenda with phone numbers that will
be used during the assignation of commands to the keys.

A new dial can be added under the ‘Edit New Dial’ menu or
using the following shortcut icon

CrossNET 79
 CrossNET

Figure 6.36 Creating a new dial

The phone number, Uri or IP, an identifying name and kind of used
protocol to be used in the communications with that number must be
declared in this dialog box:

Figure 6.37 Assigning a new Dial

CrossNET 80
 CrossNET

As a rule of thumb, the following protocols must be assigned to the

different system interfaces:
G.711 G.722
PLAN TELEPHONY Yes No
GSM Yes No
ISDN Yes Yes
IP Yes Yes
Table 6.1 Selecting the proper Codec type

That is, the G.711 codec should be configured by default, and only
when a connection using ISDN or IP is required, the second protocol
option (G.722) will be used.

6.10 KEYS CONFIGURATION

Once all the ports are defined, with the different models of panels
and interface cards comprising the system, the actions to be performed
by each key in the panels needs to be configured. This assignment of
commands to keys can be performed in two ways:

• Normal Mode The panel key to be programmed is selected with

the Mouse cursor, double ‘click’ is made, and the dialog box is filled
in. Several advanced properties can be assigned.
• Quick Mode Assigns user-chosen actions to the keys from the
main window. This is the best option to start configuring the panels
if no special properties are to be declared.

Next, the normal configuration mode will be detailed, and after that,
we will briefly comment about the quick programming mode.

CrossNET 81
 CrossNET

Figure 6.38 Panel selection

From all ports shown at the left window, we must select the panel
whose keys we want to configure. It is selected by a ‘click’, and the
corresponding keyboard panel representation will appear at the right side
of the screen.

The cursor must be moved to the desired key. Make double ‘click’
when the cursor is over it. A dialog box will appear each time this action is
carried out.

Figure 6.39 Assigning commands to a key

CrossNET 82
 CrossNET

The different available options are:

• Command Action to be executed when the key is pressed. More
than one command (up to 128, actually) can be assigned to the same
key, having in mind that only the first one in the list is signaled. The
available commands are:

• Talk Audio is sent from the panel to a selected destination (one

direction only). This is the basic command allowing the user to
make a call to a destination.
• Talk & Listen Audio is sent from the panel and received into it
to/from a destination. It allows a bidirectional communication.
• Listen Audio comes from a source to the panel, but only in that
direction.
• Dual Talk & Listen Allows the user to program two different
actions depending on the way the key is pressed. If it is briefly
pressed, the panel will listen from the panel selected in the “Listen
from” field, and the key will remain latched. If, on the other hand, the
key is pressed for a longer time, a talk action will be performed to
the panel defined in the “Talk to” field, and the key will then operate
in push-to-talk mode.
• Remote One Way Remote crosspoint between a source and a
destination. Audio is sent from the source and routed to the
destination (unidirectionally). This is a remote switching function
between two locations by means of a key in a third panel, which is
the one being edited.
• Remote Both Ways Remote crosspoint between a source and a
destination. Audio is sent and received to/from the destination. This
allows a bidirectional remote connection between two locations, by
means of a key in a third panel, which is the one being edited.
• Remote Volume Allows to remotely vary the audio level of a
signal between a source and a destination, in a range from –12dB
to +12dB (crosspoint variation). This is a remote switching function
between two locations by means of a key in a third panel. Actually,
both “volume+” and “volume-” keys must be added in order to
control this variation on the crosspoint.
• Dial Call This function establishes a call through a chosen
destination telephone and the desired number. It allows making
calls to a destination number, through an interface available in the
system. Note that this function doesn’t open any cross point, only
establishes or releases the call in the interface.

CrossNET 83
 CrossNET

• Volume + in panels not including the crosspoint level adjustment

function, this allows to directly turn the volume of an individual
crosspoint up. By pressing this key, the “volume up” macro is
activated and, after that, by pressing the destination key, its
listening level is increased. The volume increases up to +12dB in
+1dB steps for the incoming audio level.
• Volume - In panels not including the crosspoint level adjustment
function, this allows to directly turn the volume of an individual
crosspoint down. By pressing this key, the “volume down” macro is
activated and, after that, by pressing the destination key, its
listening level is decreased. The volume decreases down to -12dB
in 1dB steps for the incoming audio level
• Mic/Headphone This command switches from headset to the
panel microphone-speaker in panels without a dedicated switching
key.
• Programming This command allows for the local programming of
the panel keys in panels that don’t have a dedicated key for this
function. It also gives the option to save to a map in a permanent
way (subsequent reconfiguration of panel crosspoints).
• Page This command allows the creation of virtual crosspoint key
pages for panels that don’t have dedicated key for this function, so
that many more virtual configuration keys become available. In
order to be able to write to pages different to page 0, this command
must be previously assigned to a key.
• GP Out selects the switching and activation of the GPO (general
purpose output) incorporated in the equipment.
• Hot Key Defines the key as a Hot Key, that is, a key that is
initially unprogrammed, but a command, origin and destination can
be assigned to it, eliminated or modified during the operation of the
system in real time from the LiveCrossMapper software.
• Reply When an incoming call is received in the panel, and there
are no dedicated keys for answering, the call is not signaled by
default. However, with the Reply command, incoming calls that
have no direct answer key will be signaled on this one, showing the
mnemonic of the calling panel in the panel display. When an
incoming call is being signaled, pressing a key equals to make a
talk to the calling port. If there are several incoming calls without
answer key, the last received call will be signaled.

CrossNET 84
 CrossNET

• Source Source port of the command to execute.

• Target Destination port of the command to execute.
• Label Label that the user can determine in order to indicate, in the
clearest possible way, the action that will be executed when pressing
this key. If not filled in, the software will assign it automatically. This
label will be shown to the user in each assigned key.
The naming conventions for all the crosspoints is as follows:
• Talk & Listen All characters in capitals.
• Talk First character in capitals, rest in lower case.
• Listen All 4 characters in lower case.

Panels not including dynamic LCD labels, will have another

symbolic representation at the bottom of the key that should help the user
identifying the type of command associated to it:

Figure 6.40 Graphical naming of the key labels

• Key function Determines the real operation of the key in the panel.
Three different names can be exclusively chosen for each panel key:

• Latch A short press of the key activates the action. Another

pressing disables the command action.
• PTT (Push To Talk) The key programmed action is executed only
while the key is being pressed.
• Normal Comprises the two above. If the key is pressed and then
released, the action will be executed, but if it is continuously
pressed, it will be executed until it is released. This is the default
operating mode.

CrossNET 85
 CrossNET

• Interlock Allows a key to be defined in Interlock mode and

assigning it to a group of up to 8 keys. When a key that is
programmed in Interlock mode is activated in a panel, the rest of
keys of the same group are deactivated, as only one key in the
group can be active at a given moment.

• Private Privacy of the crosspoints. If the command assigned to a

key is marked as private, when this key is pressed the rest of actions
made to other destinations will be removed, in order to establish a
private conversation with only that destination.

Example: A Talk is programmed from a source to a destination, and it

is marked as private. The source user can have several established
communications, but when he presses this Talk key, the source user
will not be heard by the rest of destinations that are open, except the
one that was programmed for that key. This way, he can talk privately
with a location without anybody else listening to him.

• Audio Levels Allows for the variation of the audio level of the
selected crosspoint between–12dB and +12dB. The default level is
0dB.

Once the command or commands is/are assigned to the key, it is

validated with the ‘Add’ button. Up to 16 commands can be added to a
same key. Once all the actions are finished, the dialog box must be
closed with the ‘Close’ button. This procedure must be repeated for every
key to be configured.

The above described method corresponds to the ‘normal mode’.

There is another easier mode of ‘quick programming’ that provides a
higher performance.

In order to Access this method, the panel to be configured must be

selected in the left window. Then, go to the ‘Edit Quick Programming’
menu, or check the following checkbox

CrossNET 86
 CrossNET

Figure 6.41 Accessing quick programming

In order to assign the desired function to a key, the command,

destination and associated label to the key must be chosen. Next, the
mouse cursor must be placed on the key to program, clicking on it. The
key will become automatically programmed with the selected command.

Source cannot be modified, as it is associated to the open panel

that is being programmed. If we had a different source, it would be
necessary to change the panel by deactivating the quick programming
function, choosing another panel and activating the function again by
using the icon.

CrossNET 87
 CrossNET

Another available function offers the possibility to copy the keys

from an already programmed panel to another that is already not,
provided that they are of the same type in order to speed up the
programming task for similar configurations. This function can be
activated with the following shortcut icon , and then selecting the
source panel for the copy and the destination panel where the commands
will be copied to

NB: A command assignation can be moved from a key to another, by

clicking on the already programmed key with the left mouse button, and
then dragging that assignation to the desired key. When the mouse
button is released, the new key will become programmed.

6.11 VOLUME CONTROL

The Intercom system supports independent control of each

crosspoint between a source and a destination within a range from -12dB
to +12dB.

Besides, depending on the matrix family, the volume of each

individual input and output port can be varied.

The differences between these three volume controls are:

• Variation at the crosspoint affects the communication between

the selected source and destination only.
• Variation at the crosspoint levels at the matrix input port are
varied, so it affects any communication that uses this port as the
source.
• Variation at the destination values are varied at the output port,
so it affects any communication that uses that port as the
destination.

CrossNET 88
 CrossNET

Something to have in mind is that the maximum level supported by

the analogue interfaces is 12 dBu. That means that if we have a signal
originally entering the source at 7 dBu and we raise it +8 dB to a
destination, its level when reaching the destination would be 15 dBu, so it
will be clipped at 12 dBu, reaching the maximum saturation level.

It is also worth noting that TA7000/TA70003 analogue interface

cards support control of gain at the input and output, what’s very useful to
adapt levels at the previous stage, without the need to modify the
destination crosspoint levels afterwards.

Any crosspoint volume level can be changed from the ‘Edit

Audio Levels’ menu or using the shortcut icon shown below

Figure 6.42 Accessing audio level configuration

CrossNET 89
 CrossNET

A dialog box like this will show up:

Figure 6.43 Assigning audio levels

The ports drop-down menu at the left (‘source’) allows for the
selection of the source, and the one at the right (‘target’), the destination.
The audio level between that selected source and destination will be fixed
by the control in the middle, labeled as “Crosspoint”. It can be adjusted
up and down with 1dB resolution.

Each crosspoint has a default level of 0dB, the range being

between -12dB and +12dB. For example, if a source signal comes with
1dBv level and we want it to reach the destination at 6dBv, then a gain of
5dB should be set in the ‘Crosspoint’ text box.

If the selected source is a group, and the destination is a panel,

then the volume variation will be established for all the source users
within that group to that destination. If, on the other hand, the source is a
panel and destination is a group, the volume variation will be applied from
the source panel to all the destinations in that group.

All system levels can be reset to the default value (0dB), by simply
clicking on the “Reset all XPT levels to default” button.

CrossNET 90
 CrossNET

An access to the audio level control between source and

destination ports has also been provided from the configuration of the
panel keys.

Variation of audio level at the source or destination is similar to

doing it at the crosspoint, with the difference that both input and output
levels can be selected for each one.

6.12 ‘ON LINE’ CONNECTION

The software allows for an interactive connection with the matrix

through the network in order to operate with the generated maps. Up to 8
configuration maps can be stored in its memory, which can be handled at
any moment when the user needs it (load, activation, elimination, etc.)
while observing the operational status of the system.

An IP address for the matrix that will be connected to the cable

must be specified. In order to do that, just open the ‘File Options’
menu, where a dialog box will appear that allows the user to define the IP
address of the matrix used in the connection.

CrossNET 91
 CrossNET

Figure 6.44 Matrix connection selection

In order to establish a connection to the matrix, select the ‘On Line

Connect to Matrix’ menu option or click on the shortcut icon shown
below

Figure 6.45 Activate connection to Matrix.

The current status of the connection is displayed in the bottom right

area of the main screen. If the software is unable to connect to the matrix,
an informative dialog will show up, together with the connection status at
the bottom right area

CrossNET 92
 CrossNET

Figure 6.46 Error connecting to Matrix

If there is no problem with the connection, its status must appear as

active, showing the IP address of the controller we are connected to, and
the name of the configuration map and active maps in that moment. The
send and retrieve map options, as well as the connection icon will
become enabled in the ‘Online’ shortcuts menu.

When performing the retrieve, download, activation or deletion

actions for configuration maps, the following window will appear in order
to select the bank to work with:

Figure 6.47 Bank selection

CrossNET 93
 CrossNET

NB: The bank is currently active in the controller will appear highlighted
by default.

The available options for interactive operation are:

• Open Map from Matrix Downloads to the PC a map that is

stored into a matrix bank, and loads it in a software edition window.
The bank of the map to be edited must be selected in the dialog
box.

• Save Map to Matrix This option is used to save the

currently editing map into a matrix bank so it is permanently stored.
The bank where the map will be stored must be selected in the
dialog box. If an already occupied bank is selected, the old map will
be overwritten.
• Update Current Map Updates the current map. Performs an
update of the matrix active map (provided that it is connected). This
update downloads the map currently in CrossMapper on its position
in the matrix. Besides downloading it, this option also activates the
map so it becomes operational immediately. This option preserves
the communications currently established with the matrix.
• Activate Map Activates one among the 8 maps stored in the
Matrix. A map stored in a bank must be activated before it starts
operating. The name of the map bank to activate must be selected
in the dialog box. When a map is activated in the controller, the user
will be prompted whether he wants to keep the current
communications:

Figure 6.48 Bank selection

CrossNET 94
 CrossNET

If the user decides not to keep the current communications, the

system configuration will be reset, starting from the scratch, that is, all
previously established communications with the system during its
execution (key pressings, hot crosspoints, telephone calls, audio
levels, etc.) will be eliminated. If, on the other hand, the user decides to
keep current communications, the system will continue operating,
keeping all changes made during normal operation of the system, and
updating only the changes that are new in the configuration that will be
loaded. If by chance the new configuration tries to reprogram a panel
key that is active at that moment, this key will keep the former
configuration until the operator releases it. From that moment on, it will
operate according to the configuration established in the new map.

• Delete Map Deletes one of the available map, leaving the bank
free. When a bank is deleted, it will appear as ‘<EMPTY>’.
• Date/Time Synchronization Allows synchronization with the
date and time of the PC connected to the matrix. An informative
window will appear warning the user.

Figure 6.49 Time assignment

• System Status Shows the real time system status, by means of

a summary of the connections with the registered equipment.

CrossNET 95
 CrossNET

Figure 6.50 Example of the system status view

The status window is divided in two areas. On one hand, we have

the status of the matrix and other elements comprising its core. On the
other hand, we have the status of the terminals and input/output
equipment connected to the matrix.

• Matrix status:
The status of the Intercom controller can be seen in the
Matrix window, together with the units composing the matrix
(it may be a single unit for hybrid matrixes, linkers and base
stations)

Figure 6.51 Matrix Information detail

CrossNET 96
 CrossNET

In figure 5.52 we can see an example of the status of a

CrossNET, system, comprising a TP8000 panel and a
CrossNET router. If there is a communications failure
between the controller and some of the other components, it
will be shown in red with ERROR status. If, on the other
hand, there is some problem in some of the matrix
components, it will be shown yellow with WARNING status.
These are the possible cases that would lead to a WARNING
status

• Ports status:
When operating correctly, the name of the equipment
will appear, with ‘OK’ status written next to its descriptive
features.

If the terminal model declared by the user in the map

doesn’t match the physical system connected to the matrix, a
‘Warning’ will be shown, and the unit in particular will be
displayed with a yellow border.

If it is not known whether some element is connected

to that port, it will be marked as ‘UNKNOWN’, as is the case
for front panel microphone ports.

The main status window also shows detailed

information about each port. Just select one and click on the
‘Details’ button and a window like this will show up:

CrossNET 97
 CrossNET

Figure 6.52 Detail of a port with no issues

Figure 6.53 Detail with a port with an error

• Crosspoints Allows the user to display and modify in real time the
status of all crosspoints in the system, by means of an interactive
window where the user can manually activate or deactivate
crosspoints between the different port inputs and outputs. The audio
level for a given crosspoint can also be modified in real time.

CrossNET 98
 CrossNET

In order to activate this function, just go to the ‘On line Crosspoints’

menu. A window will appear presenting all the ports in the system, listed
as a row at the top of the window as inputs and as a column at the left as
outputs.

The port that the user is currently selecting with the mouse is signaled
by means of a yellow zone both in the input and the output, as depicted
below

Figure 6.54 Crosspoint activation window

The desired crosspoints can be activated by clicking on the

input/outputs.

This graphic panel can be very useful to know, in real time, which
crosspoints are being made by the system at any given moment, as a
general view of the operation. Each crosspoints can be in any of the
following status:

CrossNET 99
 CrossNET

• Inactive crosspoint a White box between an input and an output

port indicates that the corresponding crosspoint is not activated, that
is, that input’s audio is not routed to that output.
• Active crosspoint a blue box indicates that the input
corresponding to that column is routed to the audio port in that row,
that is, the crosspoint is made. They will be panel-made crosspoints,
or standby-type IFB’s that are not attenuated.
• Software-made crosspoint a purple box indicates that the
corresponding crosspoint is active, but it has been made from a piece
of software such as CrossMapper or LiveCrossMapper. These are the
crosspoints that can be activated or deactivated from the application.
• Attenuated crosspoint a light-blue box indicates that the
crosspoint is a cut-type IFB, and is currently attenuated according to
its programming (from -2dB to total cut)
• Forced crosspoint a red box informs that the corresponding input
is routed to the selected output (active crosspoint), but it is forced by
the user from this same view, from a smart panel, or simply because it
is an IFB.
• Forbidden crosspoint a black box indicates that the crosspoint is
defined by an IFB clear, and, therefore, the connection of that input
with that output is forbidden by the system and no action can connect
them

If what the user wants is to make crosspoints manually, all what’s

required is to select the input and output ports (locating them by name),
and left-clicking on the box defined by the intersection of the input column
with the output row. At that very moment, the crosspoint will change to
purple color, indicating that it has been made by software.

In order to disconnect an already made crosspoint, move the cursor

to its box and left-click on it. That box will change to white color, indicating
that it has been released

CrossNET 100
 CrossNET

An unidirectional communication is established between an input

and an output by following this procedure, but if what’s required is to
establish a bidirectional channel between two ports, then the procedure
consists on placing the mouse cursor on the crosspoint between the
desired input and output, and right-clicking on it. A window will appear
that offers the option to connect “both ways”. This will actually create two
crosspoints, one for each direction. In order to release them, just right-
click on it again, or release each one with the left button as explained
before.

The drop-down menu appearing when right-clicking on a crosspoint

contains the “Audio level” option. When selecting this option, a window
will appear that allows the user to vary the crosspoint level (only for
compatible matrix families). Note that this volume control affects that
crosspoint only (it is unidirectional).

Figure 6.55 Crosspoint level adjustment window

It is also possible to adjust the input and output level of a port (only
in compatible matrixes) by selecting the input or output mnemonic, right
clicking on it and selecting “Audio Level” in the drop-down menu.

Figure 6.56 Input port audio level adjustment window

CrossNET 101
 CrossNET

System crosspoint audio levels can be visually represented by

checking the “Show audio levels” checkbox in the crosspoint window. At
that precise moment, the crosspoint status will not be represented, but
the level of each point will, according to the same naming:

• 0 dB crosspoint white box

• +12 dB crosspoint red box
• Crosspoint with level between 1 and 11 dB red gradient,
the higher the level, the deeper the red.
• -12 dB crosspoint blue box
• Crosspoint with level between -1 dB and -11 dB blue
gradient, the lower the level, the deeper the blue.

Figure 6.57 Graphical representation of audio levels

Due to the large quantity of ports that a system can have (up to
1024 in some cases), port selection filters have become necessary for an
efficient management of the crosspoints.

A filter is a selection of ports to be displayed in the screen. This

way, a filter for ports susceptible of becoming connected can be created.
As many filters as required can be created.

CrossNET 102
 CrossNET

Figure 6.58 Filter example

The filtering functions appear at the top area of the crosspoints

window.

Add new filter

Filter selector Delete
selected filter Edit selected
filter

Figure 6.59 Crosspoint filters bar

In order to create a filter, just click on the “Add Filter” button. A

window will appear where the user can add the ports he wants to see,
both for inputs and for outputs.

CrossNET 103
 CrossNET

In order to delete a filter, first select it in the drop-down menu. Once

selected, click on the “Remove Filter” button to eliminate it.

In order to edit a filter, first select it and then click on the “Edit Filter”
button. The editing window is very similar to the filter creation window.

Selected
Filter name input ports
All input ports in
the system

All output Selected output

ports in the Ports can be added or
ports
system removed to the filter by
means of the centre
buttons

Figure 6.60 Creating or editing filters

CrossNET 104
 CrossNET

6.13 MATRIX INTERCONNECTION

Several intercom systems can be connected together so they can

share a number of trunking channels that both controllers will manage in
a seamless way for the user, in order for both systems to establish
communications between pieces of equipment in a similar way as they
would if they were local to the matrix.

In order to define an external matrix that our system will connect

with, open the Edit menu and select the “New External Matrix” option.
This can also be done by clicking on the corresponding toolbar button:

Figure 6.61 New external matrix

A dialog box will show up in order to be able to define the remote

matrix parameters. Here we can specify a description of the matrix so it
can be identified in our system, and the IP address of the remote
intercom controller.

CrossNET 105
 CrossNET

Figure 6.62 External matrix definition

Once the external matrix is defined, it will appear in our

configuration resource tree. The parameters can be modified later on by
selecting the external matrix properties.

Figure 6.63 External matrix representation

Three new configuration items appear under the external matrix:

• Trunking: allows for the definition of the audio ports that the
system will dynamically use to establish links with the remote
matrix. These ports can be defined by clicking in Properties in this
window, o in the trunking icon. This dialog will be presented:

CrossNET 106
 CrossNET

Figure 6.64 Trunking ports definition

The ports used for trunking will be audio ports (for example,
analogue, HSAL, MADI, AoIP… ports) connected to a remote matrix. It is
mandatory that audio channels defined for trunking between both
systems are in the same port addresses. For example, if the local matrix
is configured so ports 30 to 40 are defined to connect with the remote
matrix, the remote matrix configuration also needs to have ports 30 to 40
mapped for trunking ports with our local matrix local.
• Exports: Allows the user to define the local ports visible for the
remote matrix. Only ports in our matrix that are granted visibility
can be configured for communications in the external system. A
window for configuration of the exported ports is presented when
clicking on the Export properties:

Figure 6.65 Exported ports definition

CrossNET 107
 CrossNET

• Imports: this is a non-editable option and a list of the ports

exported by the remote matrix, hence visible to us, is presented
here.

Figure 6.66 Imported ports list

Once the external matrix is defined, loaded and configuration

is activated in our system, our controller will establish a control
communication with the remote controller. If communication is
correct, the ports exported by each system will be exchanged and if
imported ports in our configuration don’t match those exported by
the remote matrix, a dialog box will appear asking whether we want
to update the imported ports list (provided that the active map is
open in the system).

When CrossMapper is open, the currently active

configuration map will be signaled in the file window title bar with an
“ACTIVE MAP” label.

CrossNET 108
 CrossNET

Figure 6.67 Several maps open, active one signaled

When the active map is open and changes are produced in any
ports exported by external matrixes, the following dialog box will show up
so the user can choose whether to update external matrix exported ports
in the current configuration file.

Figure 6.68 Imported ports update confirmation prompt

CrossNET 109
 CrossNET

If changes are not accepted, this confirmation will not be asked for
again until the active map file is updated or closed and open again. On
the other hand, if changes are accepted, a new configuration will be
requested to the controller so the exported and imported ports are
synchronized between the controller and CrossMapper.

Figure 6.69 Controller configuration update confirmation prompt

Once the existing external matrixes imported ports are

synchronized, the destinations being visible by those external matrixes
will become available when programming keys in the local panels.
Imported panels will appear together with a number representing the
remote matrix identifier, followed by colon ‘:’ and the mnemonic of the
remote matrix panel.

CrossNET 110
 CrossNET

Figure 6.70 Remote destinations when programming keys

In order for two panels in different matrix to be able to

communicate, each panel must be exported to the remote matrix. When a
port is no longer exported, keys with commands in the remote matrix that
established communications with that port will be eliminated.

CrossNET 111
 CrossNET

6.14 LIVECROSSMAPPER REAL-TIME SOFTWARE

LiveCrossmapper is a real-time operation application that allows

simultaneous connection to up to 10 work stations, refreshing in real time
(every 1 second) every change made either from Crossmapper or the rest
of LiveCrossmapper clients.

Figure 6.71 General view of LiveCrossMapper application

All windows’ position and size, as well as which ones are visible
and which not are saved when closing the application, so when it is
restarted the layout will be preserved.

Changes to the Intercom system remain active no matter if the

application is closed, until another map change is made from
CrossMapper without respecting the communications (or due to a system
reboot).

CrossNET 112
 CrossNET

The Only required configuration consists on the definition of the

master system controller’s IP address (or the cluster IP address if the
system has redundancy), in the ‘File Options’ menu.

Figure 6.72 Master IP configuration

Once the connection is established, the required information to start

operating is downloaded from the controller by clicking on the toolbar
“Connect” button. The active map name (or “----” if there none is) will be
shown in the title bar.

These are the working windows:

Filters:

Figure 6.73 Filters window

Allows the user to define the filters for system ports, which will be
applied to the rest of work windows. Filters are local to the station where
LiveCrossMapper is run and are stored in the system registry.

CrossNET 113
 CrossNET

A filter name can be defined, and the names of the ports that are
visible when that port is active in the different work windows can be
selected.

Filters are general, and not associated to any particular map. Active
map ports identifiers apply in the filter selection list. If there are undefined
ports in the map, or the application is not currently connected, they will
appear as “Port XXX”, in shaded grey

XPT Manager:

Figure 6.74 XPT Manager window

This window allows the user to make crosspoints and delete

existing ones.

CrossNET 114
 CrossNET

The two first lists show the system defined ports, in order to select,
respectively, a source and a destination for the crosspoint (they can be
filtered by means of the filters defined in the application, and selected in
the combos placed above the lists). The third list shows all crosspoints in
the system made by CrossMapper or made in real time with
LiveCrossMapper.

By selecting a source, a destination and a command from the

combo box (Talk, Listen or Talk&Listen), an “Add” button is enabled that
will make the indicated crosspoint. This crosspoint will be added to the list
at the right (with green background until the system confirms that it is
actually applied). It is also possible to activate crosspoints by double-
clicking on the ports in the source or destination lists, provided that both
lists have a selected port.

The “Remove” button is enabled by selecting an already

active crosspoint in the list at the right. This button removes the selected
crosspoint (it is displayed with red background until the system confirms
that it is actually removed). A crosspoint can also be removed by double-
clicking on it.

All crosspoints made from CrossMapper or, in real time, by

LiveCrossMapper, are removed by clicking on the “Remove All” button.

A tool tip indicating the crosspoint audio level in dB appears when

placing the mouse on the central arrow of an existing crosspoint.

CrossNET 115
 CrossNET

XPT Viewer:

Figure 6.75 XPT Viewer window

This window shows all system active crosspoint in real-time. Both

the crosspoints made from CrossMapper and LiveCrossMapper
applications, and those made as a consequence of commands issued by
the panel keys, IFBs and rest of events causing crosspoints, are
displayed.

A list with the system ports is presented, together with the input and
output level for each port, and a list of communications established with
the selected port. Each communication “box” shows destination port
name and communication direction (red arrow means TALK to
destination, while blue arrow means LISTEN to destination and bi-color
arrow means TALK&LISTEN to destination).

• Destination TALK
• Destination LISTEN
• Destination TALK & LISTEN

CrossNET 116
 CrossNET

Ports displayed can be filtered by the combo located above the list.

HotKeys:

Figure 6.76 HotKeys window

Commands on keys already defined as HotKeys in CrossMapper

are programmed here.

The first list shows all keys programmed as “hotkey” in the port that
is selected by the combo above the list (this list includes ports with any
hotkey only). It there is already a command assigned to the key, a check
will be displayed at it its right.

The second list shows a filtered list (using the combo above it) with
all system ports to be assigned as destination of a new key command.

The last list shows all the currently assigned keys.

CrossNET 117
 CrossNET

By selecting a key from the first list, a destination port and the
command to program from the combo (Talk, Listen or Talk&Listen) the
“Assign” button will become enabled, that will program the key. The new
assignment is shown in the Hotkeys list (with green background until it is
confirmed). The assignation can also be made by double-clicking on a
key or destination port.

A HotKey programming is removed by selecting a hotkey

assignment and clicking on “Unassign” (it will be displayed with red
background until its release is confirmed). The release can also be
initiated by double-clicking on the desired hotkey:

Deleting or re-assigning a currently active panel HotKey from

LiveCrossMapper implies that the key is remotely released in that panel
and the corresponding crosspoint deactivation.

CrossNET 118
 CrossNET

IFB’s:

Figure 6.77 IFB’s windows

Allows for the reprogramming of the system IFBs, and also

assignation of source and destination to that unassigned IFBs in the
configuration map.

The list at the left shows all IFBs that have been defined in the
configuration map, with their mnemonic, current source and destination,
and an icon indicating the IFB type. If the IFB source or destination are
not assigned, “---” is shown in the corresponding column.

The two last lists show all the available ports to select the IFB
source and destination, respectively. The first element in each list is
always “UNASSIGNED” what allows the user to leave the IFB source or
destination still undefined. The listed ports can be filtered by both combos
located above the lists.

CrossNET 119
 CrossNET

The IFB to be modified is selected from the first list. The other two
ones indicate source and destination, and the IFB type to be made is
selected from the combo below (Fix, Cut, attenuated or Clear). It can also
be selected whether the IFB is direct or inverse (if applicable), and the
IFB is finally reprogrammed by clicking on the “Modify” button (the IFB will
be shown in green until the matrix confirms the action). An IFB can be
modified by double-clicking on the source or destination ports, if it is
selected in the first list. If double-click is made on an IFB, both origin and
destination are unassigned from it.

It is not possible to program IFBs with same source and

destination, as they would act over the same crosspoint. Therefore, IFBs
that, when being modified, become associated to already assigned origin
+ destination pairs, won’t be executed.

CrossNET 120
 CrossNET

CHAPTER 7: QUICK START USER’S GUIDE

7.0. Example to develop

In order to focus the explanations complied in this quick start user’s

guide, we will concentrate on the configuration and start up of a particular
example, detailed next.

The following diagram will be configured and implemented:

Figure 7.1 Example scheme

The architecture described above comprised the following pieces of

equipment:

• 12 TP8000 panels, using Dante AoIP.

• 4 Kroma Digital panels, connected with Kroma Digital
protocol.
• 1 Xplorer with 4 Xbp wireless virtual panels.
• A control PC with CrossMapper and “Dante Controller”
applications installed.

CrossNET 121
 CrossNET

7.1. Equipment connections

7.1.1 Power supply

Please refer to section 1.2.1. in this manual in order to properly

connect the system’s power supply.

7.1.2 Audio and intercom: panels and auxiliary circuits

7.1.2.1 AoIP

Please read section 2.2.2. in this manual in order to correctly

connect all panels and auxiliary devices working with AoIP. Also, if
you want to know a list of devices compatible with CrossNET using
this kind of connection, please check section 3.3.2. in this manual.

7.1.2.2 Digital

Please refer to section 2.2.3. in this manual in order to know

how to correctly connect all panels and auxiliary devices working
with Kroma Digital protocol or VoIP quality. Also, if you want to
know a list of devices compatible with CrossNET allowing for this
kind of connection, please check sections 3.3.1. and 3.3.3. in this
manual.

7.1.2.3 Analogue

Please read section 2.2.6. in this manual to know all the

details in order to properly connect all the analogue panels and
auxiliary devices.

CrossNET 122
 CrossNET

7.2. Power up

Once the equipment has been connected to the mains, just take the
front panel located power switch to the lower ‘ON’ position, and the
system will turn on. Once this operation is performed, please check that
the POWER LED is illuminated. See sections 2.1.2 and 2.1.11 for further
detail

The unit is ready to be used.

7.3. Pre-Configuration of AoIP links using Dante Controller

7.3.1 Dante Controller

In order to access AoIP panels pre-configuration, Dante Controller

application must be open in a PC.

“Dante Controller” application is provided with each system, as an

application running on Microsoft Windows systems, version 7 SP1 and
later.

The auto run disk provided includes an executable file that installs
the software. The software modules to be installed are:
- Dante Controller Windows (version 3.5.6.2)
- Dante Firmware Update Manager (version 1.4.13.2)

The PC must be set up so it automatically obtains an IP

configuration form the network (DHCP Enabled).

Once installed, the application is run from the start menu:

CrossNET 123
 CrossNET

Referring to the 12 panels using Dante AoIP, first of all it will be

necessary to subscribe each panel’s inputs and outputs to the
adequate transmitters and receivers, using Dante Controller
application.

Subscription of the matrix Dante transmitter channels to the

receiving channels of the panels, and of the receiving L channels of
the panels to the matrix transmitters is performed by following the
steps indicated in paragraph 3 of Annex C and in Section 4 of this
manual.

In order to know the operating procedure in more detail, please

check paragraph 7.4.1 of Appendix C or Section 4.2 in this manual.

We will see a screen like this in “Dante Controller” when all panels
are connected:

Figure 7.2a: Pre-configuration of AoIP connections between panels and CrossNET using Dante Controller

CrossNET 124
 CrossNET

Figure 7.2b Pre-Configuration of AoIP connections between panels and CrossNET

Please read section 4 of Appendix C in this manual for more

details.

CrossNET 125
 CrossNET

7.4. Development and loading of a map

A Matrix operating map is developed in order to configure the

matrix itself, the links, and other operative details of the panels and other
related auxiliary devices.

The steps to be followed to develop the above example related

operation map are explained next:

1. Open the “CrossMapper” map setup and management software.

2. Click on the “New” icon and select CrossNET matrix from the
list of available devices. In this case, we will work with a CrossNET
72 matrix, which allows us to work with Dante.

Figure 7.3 CrossMapper Matrix selection

CrossNET 126
 CrossNET

3. By clicking on the “New Port” icon, ports are added, with a type
according to the devices forming our system.

a. 12 8000-Series Dante user panels

Figure 7.4 Port configuration for panels using Dante AoIP

Matrix ports to be used are AoIP from 0 to 11, selectable

from the drop-down menu located at the right of the port’s
name. They are identified by the AoIPXX name, with XX from
00 to 11, in the example we are working on.

The panel’s control IP address must be configured under the

section “Control IP Address”.

CrossNET 127
 CrossNET

The panels will have the following names, according to the

name they are given in “Dante Controller”:
• AoIP00 TP8116-80410
• AoIP01 TP8116-80421
• AoIP02 TP8116-80435
• AoIP03 TP8116-80457
• AoIP04 TP8116-80469
• AoIP05 TP8116-80477
• AoIP06 TP8116-80480
• AoIP07 TP8116-80493
• AoIP08 TP8116-80522
• AoIP09 TP8116-80534
• AoIP10 TP8116-80566
• AoIP11 TP8116-80572

b. 4 Kroma digital panels

Figure 7.5 Port configuration for panels using Kroma digital protocol

CrossNET 128
 CrossNET

Ports to be used in the matrix are DIG from 0 to 3. The

panels will have the following names, according the naming
convention used before:
• DIG0 TP8416-80415
• DIG1 TP8416-80547
• DIG2 TP8416-80444
• DIG3 TP8416-80553
c. 1 Xplorer with 2 Xbp virtual wireless panels

Figure 7.6 Port configuration for Xplorer system

In this case, the ports to be used in the matrix are

NETXX, where XX ranges from 00 to 03. The names
given to the panels, according to the convention name
adopted before, will be:

CrossNET 129
 CrossNET

• NET00 XBP-80408
• NET01 XBP-80438
• NET02 XBP-80501
• NET03 XBP-80522
The panel’s control IP address must be configured under the
section “Control IP Address”.

In order to ease ports identification, as well as the devices

connected to them, it is useful to indicate information about the type
of port used and the device connected to it in the “Short
Description” and “Full Description” fields. Just in the same way, the
matrix port names should be labeled using the same naming
convention as “Dante Controller”. Next, some naming examples are
provided. From left to right: AoIP Dante, Kroma Digital and Xplorer
panels:

Figure 7.7 Port description

CrossNET 130
 CrossNET

This operation must be repeated until the whole number of devices

is completed. The complete list of ports is as follows:

Figure 7.8 Complete list of configured ports

4. Ports groups can be created if desired. As an example, we will

create the “Estudio A” group, comprising 6 of the 12 panels using
AoIP. In order to create a group, just click on the “New Group”
icon. The first piece of information required is a name for the group,
“Estudio A” in this case:

Figure 7.9 Group name

CrossNET 131
 CrossNET

Once the name is accepted, we need to include the group

participants. We can access “Properties” by right-clicking on the
group’s name. There we can add group members. When all the
members have been selected, just click on the “ADD” button
located in the center of the window, and they will be added.

Figure 7.10 Group members selection

5. We can define a conference in just the same way as we did with

groups. As an example, we will create a conference called
“Reunión”. In order to do that, just click on the “New
Conference” icon. First, we must provide it a name, “Reunión” in
this case:

Figure 7.11 Conference name

At the time when the crosspoints are configured, it is possible to

select one of them can be chosen to interact with the conference.

CrossNET 132
 CrossNET

6. Next, we will proceed to the configuration of the crosspoints

themselves. They can be configured as IFB’s or directly on the
panel keys. Continuing with our examples, we will configure a direct
IFB between of the AoIP panels and one of the digital ones; and
one of the keys of the virtual panel will be used to listen to “Estudio
A” group.

a. IFB:
Place the mouse cursor on and right-click. Select
the parameters in the window that appears, and then click on
Add This way, our IFB will become configured.

Figure 7.12 IFB’s creation

b. Virtual Panel:
We must choose the port were our virtual panel is connected
to from the list of ports. The following view will appear:

CrossNET 133
 CrossNET

Figure 7.13 Virtual panel View

First, click on the first available button. This button will

change its color once selected. In order to easily set it up,
check “Quick Programming” in the tools bar and configure
this button for a previously specified function.

Figure 7.14 Key configuration

We must click on a key before it becomes correctly

configured. Then, it will look like this:

CrossNET 134
 CrossNET

Figure 7.15 Configured key

c. Virtual Panel (alternative method):

We can also configure the virtual panel key by right-clicking
on it. This will give pass to the following dialog:

Figure 7.16 Key Configuration Window

CrossNET 135
 CrossNET

A Talk towards the “Estudio A” group has been configured in

this case. The command can be defined as private or public
in this window, by clicking on the checkbox next to the
“Private” legend. Also, the functionality of the key and its
associated crosspoint audio level can be configured. Last, it
is necessary to click on the “Add” button once the
configuration is done in order to apply it.

7. Another potentially useful functionality is the control of crosspoints

volume. Click on the “Audio Levels” icon in order to modify this
parameter. The following window will appear:

Figure 7.17 Audio level assignment

It will only be necessary to choose the source and destination ports,

and from the window shown above we will be able to control the
audio levels at the input and at the output of the source and/or
destination ports, as well as the level of the crosspoint between
them. If more information is required about this functionality, please
read chapter 5.11 of this manual.

8. In order to finish the configuration, we will now load the map into
the matrix remotely, using the tools provided by CrossMapper. First
thing to ensure is that we are connected to our matrix, so its IP
must have been correctly configured. We can do this from
‘File Options’, where the following dialog will appear:

CrossNET 136
 CrossNET

Figure 7.18 Matrix IP configuration

Once the equipment’s IP address have been entered, we will

connect to it by clicking on the “Connect to Matrix” icon. If the IP
has been correctly configured, the connection status should now
appear as active:

Otherwise, CrossMapper will warn us by means of this message:

Figure 7.19 Matrix connection failure

When the connection is completed, a map loading window will

appear that allows us to send it to the matrix. We will look for a free
map, or if there isn’t one, just overwrite one of the existing maps.

CrossNET 137
 CrossNET

Figure 7.20 Bank selection

After this window, we will be prompted whether we want to activate

the map or not. In this case, we will accept, so we can start
operating on it right now. When asked whether we want to initiate
communications, it is recommended to choose the “Yes” option
unless this is the first loaded map or the matrix is still off line
(outside the working network), in order to avoid potential errors.
After doing this, the application will indicate that the map has been
activated and we can start working with it.
Please check section 6.12 of this manual in order to gain a deeper
knowledge about this function.

If more detailed information is required about any of the above

described steps, please check chapter 6 of this manual

CrossNET 138
 CrossNET

7.5 Activating and checking the configuration

After all the above described steps have been completed, we will
now proceed to check that the system configuration is correct.

First thing to check is that the work map described in the above
example is loaded and active. In order to do that, just check whether the
map name is displayed in the matrix display. If so, then the map is
correctly loaded into the system and there shouldn’t be any problem in
order to work with it. If precise instructions are required about how to
activate or load a map into the matrix, please check section 5.1. in this
manual.

Once this has been ensured, we need to test all the different
devices described in the architecture, in order to double-check that the
cross points and rest of defined parameters are correct. If any of them
doesn’t respond as expected, you only need to re-configure it using
CrossMapper, or if not available, using LiveCrossMapper in order to do
that in real-time. All the information related to LiveCrossMapper software
can be found in section 6.14 of this manual.

CrossNET 139
 CrossNET

ANNEX
ANNEX A: WARRANTY

AEQ S.A. guarantees that the equipment (at purchasing time)

complies with the purchase order’s specification and that it is in faultless
conditions.

The warranty period is one year from date of purchase for

equipment and accessories. The warranty covers repairing costs, labor
and updates. This warranty does not cover freight costs, final installation
or components substitution when the components’ failure is due to normal
use wear-out.

AEQ-KROMA or BROAD SERVICE purchase technical service will

repair the defects found in the material, provided that they have not been
caused by accident, loss or damage caused by the customer or during
transportation.

Damages or faults produced by a misuse of the unit or by

manipulation of personnel outside AEQ-KROMA technical service are
also excluded from this warranty.

In order to ease the procedure, contact your dealer before sending

any faulty equipment to the technical team.

For maintenance or support contact our technical team at BROAD

SERVICE (telephone or email). For more detailed information check our
web www.aeq.es

CrossNET 140
 CrossNET

ANNEX B: DANTE BASES AEQ AoIP ETHERNET SWITCHES

1. General configuration of Dante bases AEQ AoIP Ethernet Switches

The vast majority of AEQ AoIP systems will re

This document will provide Information which will help the decision of
which switch to purchase and provides data for its correct configuration.

Requirements:
• Switch must be Gigabit rated (1000Mbps)
• Quality of service (QoS) with four queues.
• DiffServ (DSCP) QoS with strict priority.
• A managed switch is required to allow custom configuration as well
as detailed operation information.
• Switches prioritize packets using DSCP/DiffServ Values. The
packet priority values used for Dante have been chosen to make it
simple to configure QoS with a wide range of switches. Some
switches require additional configuration to recognize and prioritize
specific DSCP values. The table below shows the various DiffServ
Code Points (DSCP) packet priority values:

DSCP
Priority Usage Hex Decimal Binary
Label
Time critical
High CS7 0x38 56 111000
PTP Events
Medium Audio PTP EF 0x2E 46 101110
Low (reserved) CS1 0x08 8 001000
None Other traffic BestEffort 0x00 0 000000

CrossNET 141
 CrossNET

Whilst most switches support DSCP they may default to either not using
it, or having the priorities incorrectly mapped for AEQ AoIP / Dante. For
this reason, managed switches must be used in an AEQ AoIP system.
Managed switches allow the user to interrogate and, if necessary, change
the settings of the switch, usually via a web interface. Some switches
came with EF (Audio) prioritized over CS7 (Clocking). If Audio packets
are prioritized above PTP (sample clock timing) packets, it can lead to
higher clock jitter and longer lock times. In extreme situations (high audio
traffic), it could lead to a network node loosing sync and dropping audio
packets because the sample timing has become skewed.

Please refer to the user documentation of your specific switch for more
information regarding configuring QoS.

Whilst not an exhaustive list, the following switches were found to be

suitable for RedNet after the aforementioned setup was carried out:

• Cisco SG300
• Cisco SG200
• NetGear GS724T

2. Configuration of CISCO SG 200 family of switches for Dante-based

AEQ AoIP

AEQ can provide properly configured CISCO SG200 switches on

demand. If the switch from a third party, you must set it up according to
the following procedure:

CrossNET 142
 CrossNET

Configuration procedure for the Cisco SG 200 family of switches for use
with DANTE technology:

1. Change the IP address of the computer used to configure the

switch, so it falls in the 192.168.1.xxx range.

2. Using an Internet browser, Type the address 192.168.1.254 in the

URL bar and then Type:
User: cisco
Password: cisco

You will be asked to change the password the first time you access
the switch configuration.

CrossNET 143
 CrossNET

3. Go to section Quality of Service DSCP to Queue:

We will see some decimal values and a priority:

Ingress DSCP = valor decimal
Output Queue = Priority (1 corresponds to the lowest priority, 4 is the
highest)

4. Change the following priorities in the corresponding decimal

numbers:
56(CS7=4)
46(EF=3)
8(CS1=2)

CrossNET 144
 CrossNET

5. Apply the changes, and a Save button will appear in the top area of
the screen:

6. By clicking on the Save button, you will be redirected to another

page to save the values in the switch. Click on Apply.

CrossNET 145
 CrossNET

ANNEX C: DANTE CONTROLLER INSTALLATION AND

CONFIGURATION

C.1. “Dante Controller” Description

NB: The information included in this manual is valid for software version
3.5.6.2 (or higher versions).

“Dante Controller” is a software application provided by Audinate which

allows users to configure and route audio around Dante networks. It is
available for PCs running Windows 7, 8 and 8.1, and Apple Macs running
OS X 10.7.5, 10.8.5, 10.9.5 and 10.10.

Once you install “Dante Controller” on your PC or Mac and connect it to a

Dante network, you can use “Dante Controller” to:

• View all Dante-enabled audio devices and their channels on the

network.
• View Dante-enabled device clock and network settings.
• Route audio on these devices, and view the state of existing audio
routes.
• Change the labels of audio channels.
• Customize the receive latency (latency before play out).
• Save audio routing presets.
• Apply previously saved presets.
• View and set per device configuration options including:
o Changing the device name.
o Changing simple rate and clock settings.
o Viewing detailed network information.
o Access the device web page to upgrade firmware and license
information (where supported).
o Identify a device for example by flashing LED’s (where
supported)

CrossNET 146
 CrossNET

• View network status information, including:

o Multicast bandwidth across the network.
o Transmit and receive bandwidth for each device.
• View device performance information, including latency statistics
and packet errors.
• View clock status information for each device, including frequency
offset history and clock event logs.

C.2. Minimum System Requirements

Below we list the minimum system specifications for your computer to be

able to use “Dante Controller”.

NB: It is possible that your computer may meet the requirements below,
but suffer from some other individual performance limitation related to its
particular hardware. Please seek the advice of your computer support
administrator.

General:

Recommended Minimum Requirements:

• Processor 1 GHz or better
• Memory 512 MBytes of RAM
• Network Standard wired Ethernet network interface (100 Mbps or
Gigabit). Wireless LAN (WiFi) Ethernet interfaces are not supported

Windows:

Recommended Minimum Requirements:

• Windows 7, 8 and 8.1 (32-bit and 64-bit)

It may work on Windows XP SP3 (32 bits), but we don’t provide support
for this OS.

CrossNET 147
 CrossNET

NB: Both UTF-8 and Unicode are supported EXCEPT for host or device
names; the DNS standard does not support Unicode for these.

Operating System Updates:

Ensure your PC has the latest Windows updates installed.

Firewall Configuration:

Firewall configuration for Windows Firewall is automatically handled

during installation. “Dante Controller” communicates over UDP over the
following ports:

• Dante Control and Monitoring: 8700-8705, 8800

If you are using a third-party firewall product, use the port information
provided above to configure it accordingly.

Monitor requirements:

A display resolution of at least 1024 x 768, with a screen size of at least

19” is recommended for “Dante Controller”.

CrossNET 148
 CrossNET

C.3.Installing “Dante Controller”

C.3.1 Downloading “Dante Controller”

“Dante Controller” is available for download from Audinate’s website. It’s

also available in the auto run disk furnished with AEQ equipment.

To download a copy of “Dante Controller”:

1. Go to Audinate website: www.audinate.com

2. Navigate to Products Dante Controller.
3. Under “Download”, choose your operating system.
4. Click the red Download button.

This will take you to the appropriate Dante Controller release page for
your operating system. Click the link under “File downloads “to download
the Dante Controller installer.

C.3.2 Installing “Dante Controller” on Windows

Once you have downloaded the self-installing “Dante Controller” file,

navigate to the directory where you have downloaded it (e.g. Desktop).

To install “Dante Controller”:

1. Ensure you are logged on to your PC as an administrator.

2. Navigate and double-click the “Dante Controller” installer file.
3. Read the license agreement. If you agree to the terms, select the ‘I
agree’ checkbox and click Install. If you do not agree to the terms,
click ‘Close’
4. Confirm/acknowledge any Windows security prompts that are
displayed.

“Dante Controller” will then be installed. “Dante Controller” will be added

to the start menu, under “Audinate”.

CrossNET 149
 CrossNET

C.3.3 Uninstalling “Dante Controller” under Windows

You should not need to uninstall “Dante Controller” before installing a

new version. However, if you do wish to uninstall “Dante Controller”.
Navigate to Control Panel Programs and Features, select “Dante
Controller” and click Uninstall.

NB: Two other Dante features, 'Dante Control and Monitoring' and
'Dante Discovery', may still be present in the programs list after
uninstalling “Dante Controller”. Do not uninstall these features if they are
present - they are required by other Dante software applications (for
example, “Dante Virtual Soundcard”, Firmware Update Manager, and
third-party Dante control applications). They will be removed
automatically if they are no longer required.

C.4 Where to find the “Dante Controller” application?

By default “Dante Controller” will be installed in

C:\Program Files\Audinate\Dante Controller\

It can be started in several ways:

- From the Start menu: Start Programs Audinate Dante

Controller Dante Controller.
- Run by going to Start Run and entering in the dialog box:
C:\Program Files\Audinate\Dante Controller\DanteController.exe
- Navigate to the directory where it is installed, and
double-click the “Dante Controller” icon

CrossNET 150
 CrossNET

C.5 Configuring “Dante Controller”

“Dante Controller” can communicate with other Dante devices on the

primary network, or the
secondary network, or both.
“Dante Controller” needs to
know which of the network
interfaces of the host computer
is connected to each Dante
network.

The first time “Dante

Controller” is run, you may be
presented with the Configure
Dante Interfaces dialog box
(shown below), providing a list
of interfaces from which to select the primary and secondary Dante
interfaces. Once interfaces have been selected, they are remembered for
future use, and this dialog box will not be shown when “Dante Controller”
is run subsequently.

To display this dialog at any other time, click the button in the main
toolbar

Network Interface Configuration Guidelines:

Primary Only (non-redundant) Dante network

If you only have a primary network, you can only connect one interface to
the Dante network. In the example below, the laptop (running “Dante
Controller”) and the two Dante devices (a console and a Netbox) are
connected to the
switch via their
primary interfaces.
This is a typical non-
redundant Dante
network.

If the laptop has two

network interfaces,
either can be used

CrossNET 151
 CrossNET

Primary and secondary Dante networks (redundant configuration), only

one network interface on the host computer

If you have primary and secondary (redundant) networks, but only one
network interface on your computer, you should set your computer's
network interface as the primary interface. This ensures that you can
control any non-redundant devices, and see full connection information
for any redundant devices that are connected to non-redundant devices.

If a problem does occur, and you lose connectivity on the primary

network, you can connect instead to the secondary network, to maintain
control over your devices. This entails changing the physical connection
(i.e. physically connecting your computer to a switch on the secondary
network), and changing the interface selection in the Configure Dante
Interfaces dialog.

In the example below, the laptop (running “Dante Controller”) is

connected to the switch via one
interface only, which is set as the
primary Dante interface.

The two Dante devices (the

console and the Netbox) are
connected to the primary switch
via their primary interfaces, and to
the secondary switch via their
secondary interfaces. The two switches are not connected to each other.
This is a typical redundant network configuration for computers with only
one network interface.

NB: When connected to the secondary network, you will not have control
over devices that are only connected to the primary network (i.e. non-
redundant devices, or “Dante Virtual Soundcard”). You will see the device
names in the Network view, and in subscription dialogs (for example, the
Device View Receive and Transmit tabs) but you will not be able to
view or edit device configuration for those devices. Also, if the master
clock is only connected to the primary network, its name will not resolve in
the 'Master Clocks' section of the main window tool bar, it will be shown
as a MAC address string.

CrossNET 152
 CrossNET

Primary and secondary networks (redundant configuration), two network

interfaces on the host computer.

If you have primary and secondary networks, and two network interfaces
available on the host computer, you should connect one interface to each
network. This means that you will always have full control of all redundant
devices, even if the primary network fails.

In the example below, the laptop (running “Dante Controller”) and the two
Dante devices are connected to the primary switch via their primary
interfaces, and to the secondary switch via their secondary interfaces.

The two switches are

not connected to each
other. This is a typical
redundant network
configuration for
computers with two (or
more) network interfaces.

NB 1: You must be connected to a standard wired Ethernet network in

order to use “Dante Controller”. Wireless and other non-standard wired
Ethernet interfaces will not appear in the Configure Dante Interfaces
dialog.

NB 2: All Dante applications on the same computer have a shared

understanding of which interface is the primary Dante interface. For
example, if you have installed “Dante Virtual Soundcard” on the same PC
as “Dante Controller”, and d a new primary interface is selected from
within “Dante Virtual Soundcard”, “Dante Controller” will automatically
switch to the newly selected interface, and begin operating on that
interface.

CrossNET 153
 CrossNET

NB 3: Series-8000 panels don’t have Dante redundancy implemented, so

using the Dante Primary and Secondary networks can be adequate to link
matrixes, but not to provide redundancy to the panels. In order to achieve
this, we recommend that the procedure described in paragraph 2.2.3 of
this manual is followed.

C.6 Using “Dante Controller”

“Dante Controller” presents two main types of view: Network View and
Device View.

IMPORTANT NOTE: After making changes to Dante network routing (e.g.

subscriptions, device names, channel labels etc.) please wait at least 5
seconds before disconnecting or powering down any affected devices.
This ensures that the new information has been properly saved to the
devices. Device configuration (e.g. sample rates, latency, clock settings)
is saved instantly.

C.7 Using “Dante Controller”: “Network View”

When “Dante
Controller” is
launched, the
“Network View”
screen always
appears in the
“Routing” tab,
showing the
connections status
in XY format.

CrossNET 154
 CrossNET

C.7.1 “Network View” Menu Bar

The menu bar in the Network View includes four menus: File, Device,
View and Help. The options available for each of the menus are the
following ones:
“File”:
- “Load Preset” (Ctrl+L): loads a
configuration from a file.
- “Save Preset” (Ctrl+S): saves
configuration for currently displayed
devices to a file
- “Exit” (Alt+F4): exits “Dante
Controller”
Presets” operation is described in more detail in section 10 of this annex.

“Device”:

- “Refresh” (F5): refreshes the

displayed network/device data.
- “Device View” (Ctrl+D): opens a new
“Device View” window

“View”:

Allows for the activation/deactivation of channel groups (Ctrl+Mayus+G).

CrossNET 155
 CrossNET

“Help”:

- “About”: shows the “Dante

Controller” version, and current
event log file location.
- “License”: displays the license
key.
- “Contents” (Mayusculas+F1):
opens a help window and displays help contents.

C.7.2 “Network View” Tool Bar

Below the menu bar there is a tool

bar, containing six buttons:

Reload Device Information: Updates the current view with the latest
device information from the network. This is useful when a recent change
to the network has not yet propagated automatically through to “Dante
Controller” (for example, a new device has been added to the network).

Load Preset: Loads a previously saved audio routing configuration.

For more information, check section 10.

Save Preset: Saves the current audio routing configuration. For

more information, check section 10.

Choose a Dante Interface: Opens the Configure Dante Interfaces

dialog. For more information, check section 5.

CrossNET 156
 CrossNET

Clock Status Monitoring: Activates the Clock Status Monitoring

function. For more information, check section 7.4.3.

Channel Groups: Allows the activation of the display of audio

channels for each device in groups of 16. For more information, check
section 7.4.1.

To the right of the toolbar, “Dante Controller” displays the current master
clock (or clocks, in the case of redundant networks).

C.7.3 “Network View” Status Bar

The Status Bar, in the bottom area of the screen, displays notifications for
network status, general device events, and clock status events, plus the
current Dante audio multicast bandwidth on the network.

The Status Bar displays the following information:

- P: The current status of the Primary network. Green indicates that

“Dante Controller” is currently connected to the primary Dante
network. Red indicates a problem with the connection.
- S: The current status of the Secondary Dante network. Only
displayed where a secondary network is connected.
- Multicast Bandwidth: The current Dante audio multicast
bandwidth on the connected networks. Note that there may be
network traffic from other sources that is not included in the
multicast bandwidth reading.

CrossNET 157
 CrossNET

- Event Log: Indicates the current status of the event log. Click the
icon to open the Events View.
- Clock Status Monitor: Indicates the current status of the Clock
Status Monitor. Click the icon to open the Clock Status Monitor.

C.7.4 “Network View” Tabs

There are five sub-views within “Network View” that can be selected by
clicking on the tabs located under the tool bar:

Each of these options is described below

C.7.4.1 “Routing”

When “Dante Controller” is started, it always displays the Routing

Tab within the Network View. In this view the network is shown in
the form of a grid. Devices with Tx channels are displayed along
the top row of the grid, and those with Rx channels are displayed
along the left-hand column of the grid. Initially a collapsed view is
presented; individual channels cannot be seen.

NB: If a device name is shown in red, it means “Dante Controller”

has automatically detected an error condition. Double-click the
device name to see more information. For more information, check
section 7.5.

CrossNET 158
 CrossNET

Device Channels:

A Dante device has a number of channels associated with it. These

are either transmit (Tx) or receive (Rx) channels. Receive channels
and devices are listed down the left side of the grid. Transmit
channels and devices are listed along the top of the grid.

Transmit channels are advertised on the network. A receiver uses

this advertisement to establish a subscription to the channel. A
transmit channel can be sent to multiple receivers using unicast or
multicast.

Receive channels are connected to transmit channels via a

subscription. Each receive channel will receive audio over the
network from at most one transmit channel.

Subscribing to Audio Channels:

In the Routing View, a blue square at the intersection of an Rx and

a Tx channel indicates that is it possible to create an audio route
between those channels. A grey square indicates that it is not
possible to create a route between those channels. This may be
because of a mismatch in sample rate between the transmitter and
receiver, or because a device cannot route to itself.

When you click a blue square at the cross-point between a transmit

channel and a receive channel, a subscription will be created, and

a green tick will appear in the matrix cross point. You may

initially see a grey hourglass icon (usually very briefly) to

indicate that the subscription is in progress.
If there is a problem with the subscription, either a warning
or an error icon may appear. If many devices have been
subscribed at the same time, a yellow pending icon may
appear temporarily.

CrossNET 159
 CrossNET

NB: Subscriptions can also be created in the Device View. This is

covered in the Device View Section.

Subscribing to Multiple Audio Channels at once:

To subscribe multiple channels at the same time, hold down the

Ctrl key and click the [-] symbol at the top left corner of the
intersection between the two devices. All the possible channels will
be subscribed at the same time (see image in next page) in
diagonal arrangement (the first channel of the transmitting device
connected to the first channel of the receiver device, second
channel to second channel and so on) This multiple-subscription
tool subscribes channel by channel (for example, 4 transmitters to 4
receivers), that is, a receiver can receive audio from one transmitter
only.

Unsubscribing Audio Channels:

To unsubscribe an audio channel, click on the cross-point

containing a subscription. The subscription icon will be removed
and revert to a plain blue square.

CrossNET 160
 CrossNET

Subscription Status:

The symbol displayed at the intersection of the Tx channel and the

Rx channel in the Routing View provides information on the status
of the subscription or connection, as follows:

In progress: The subscription is in progress.

Subscribed: Connection is established and fully functional.

Warning: The subscription is unresolved, typically because

the transmitting device is not visible on the network (for example,
because it has been removed, or switched off).).

Error: An error has occurred - for example, there is

insufficient bandwidth to establish the subscription.

Pending: Device is part-way through setting up subscription.

Most commonly seen when subscribing many channels at a time.

NB: The status of a subscription can change after it has been

initially established, due to changes in the network or changes in
other devices.

CrossNET 161
 CrossNET

Expanding the Routing View:

The Rx channels associated with any device can be displayed by

clicking on the [+] to the left of the device name in the left-hand
column of the grid. The Tx channels associated with any device can
be displayed by clicking on the [+] above the device name on the
top row of the grid. When this action is performed the grid view
expands to show each channel of the device, and the [+] becomes
a [-]. Clicking on [-] collapses the view. You can also group
channels into sets of 16 (see next page).

CrossNET 162
 CrossNET

The Rx channels associated with all devices can be simultaneously

expanded by clicking on the [+] of “[+] [-] Dante Receivers” at the
top of the left-hand column. Similarly, the Tx channels associated
with all devices can be simultaneously expanded by clicking on the
[+] of “[+] [-] Dante Transmitters” at the left of the top row. Clicking
on [-] will collapse the view.

Device List Filtering:

The device lists in the Routing

view can be filtered using the
“Filter Transmitters” and “Filter
Receivers” boxes, below the
Dante logo in the top left-hand
corner. Any text string typed into
the box will filter the view to only display devices that contain that
text string, in either a device name, or channel name.

The filtering is case-insensitive. For example, in the “Dante

Controller” Network view shown here, entering the string “foh” in
either of the Filter fields would display only the FOH-Amp and FOH-
Console devices, and their channels.

CrossNET 163
 CrossNET

Channel Groups:

When Channel Groups is active, device channels in the

Network View
Routing tab are
grouped into
sets of 16. The
button changes
its color to
green when this
option is
activated.

This makes it
easier to view
and make
channel
subscriptions
for devices with
large numbers
of channels.

The groups are named “1…16”, “17…32” etc.

To expand a channel group, click the plus [+] icon. To collapse a

channel group, click the minus [-] icon.

NB: Grouping channels does not affect routing or device behavior.

CrossNET 164
 CrossNET

Subscription Tooltips:

Hovering the mouse over a subscription icon in the Routing tab

displays a tooltip containing information about the subscription.

If there is no problem
with the subscription, the
tooltip will display the Rx
channel and device
name, plus the Tx
channel and device
name (for example, “CAPITOL_4” Rx channel of “CAPITOL-IP”
device subscribed to “FORUM_4” Tx channel of “FORUM-IP2”
device).

Other messages are displayed if the subscription is in any other

state:

• “Incorrect channel format: source and destination channels

do not match”: The receiver and transmitter are set to
different sample rates.
• “Mismatched clock domains: The transmitter and receiver are
not part of the same clock domain”: One of the devices is
configured with sample rate pull-up/down that does not
match the other device.
• “Tx scheduler failure”: This is typically because you are trying
to use sub-millisecond latency over a 100 Mbps network link
(1 msec is the minimum supported latency over 100 Mbps
links).
• “No Receive flows: receiver cannot support any more flows”:
This will be seen if the receiver is subscribed to too many
devices (devices typically do not support the same number of
flows as they do channels).
• “No more flows (TX): This will be seen if too many devices
are subscribed to the transmitter.

CrossNET 165
 CrossNET

C.7.4.2 “Device Info” (status of the device):

The Device Info tab provides a network-wide overview of device

configuration and operating information. The tabular view presents
the following information, in columns from the left:

• “Device Name”: The device name currently associated with

the device.
• “Product Type”: The type of Dante module in the device.
• “Product Version”: The product version, as defined by the
manufacturer.
• “Primary Address”: The IP address assigned to the primary
interface. IP addresses are currently assigned via DHCP, or
automatically self-assigned. Self-assigned addresses on the
primary interface will be in the 169.254.X.Y range.
• “Primary Link Speed”: The Ethernet link speed of the primary
interface.
• “Secondary Address”: The IP address assigned to the
secondary interface. Self-assigned addresses on the
secondary interface will be in the 172.31.X.Y range. 'N/A'
indicates that the device does not support a secondary
interface. 'Link down' indicates that the device supports a
secondary Dante interface, but it is not currently connected.
• “Secondary Link Speed”: The Ethernet link speed of the
secondary interface. Other values are possible (as per
Secondary Address).

CrossNET 166
 CrossNET

NB 1: A Dante interface may have a preferred link speed. Where it

does, and an interface is not operating at that preferred link speed,
the values in the Link Speed columns will be shown in red.

NB 2: If no device information is displayed for a device, it can

indicate a ConMon (Dante control and monitoring service) failure
on the device. The device may need to be reset or restored.

C.7.4.3 “Clock Status”

The Clock Status tab provides a network-wide overview of the

clocking state within the network.

This view provides a convenient way of quickly scanning the

network for clock information. The tabular view presents the
following information, in columns from the left:

• “Device Name”: The device name currently associated with

the device.
• “Sync”: Indicates the clock sync status for the device.
- A green light indicates that the device is currently
synced to (or is driving) the network clock.
- A red light indicates that the device is not currently
synced.

CrossNET 167
 CrossNET

• “Mute”: Indicates the mute status for the device.

- A red mute icon indicates that the device is currently
muted (usually due to loss of clock sync).
- No icon in the mute column means that the device is
not muted (audio should be flowing normally).

• “Clock Source”: Indicates the clock source for the device.

- Dante: The device is deriving its clock from the Dante
network, or is acting as master clock (but not deriving
its clock from an external source).
- External: The device is deriving its clock from an
external Word Clock source.
• “Primary Status/Secondary Status”: Indicates the state of
the PTP clock for the primary and secondary network
interfaces.
- Master: Device is the current PTP Master Clock on the
primary Dante network.
- Slave: Device is a PTP Slave on the primary Dante
network.
- Passive: Device is not using clock synchronization
information from this interface.
- Link Down: The interface is not connected to the
network.
- N/A: Indicates that the device does not support clock
status reporting. In the Secondary Status column, can
also indicate that the device is non-redundant.
- Listening: Usually transient. When persistent, it
indicates that the device cannot operate as a clock
master (slave only), and is waiting for a clock master to
appear on the network.

CrossNET 168
 CrossNET

Devices that are configured with sample rate pull-up/down

(this is not the case with AEQ equipment) are shown with
the relevant pull-up/down value against their Clock Status.
For example, a device acting as master clock with +0.1%
pull-up will be shown as Master (+0.1%). See “About
Clock Domains” section for more information.

Other transient clock states exist, which are not listed

above.

• “Preferred Master”: Raises the priority of the

device in the master clock election. If only one
device on a particular clock domain has this
checkbox ticked, it ensures that the selected device
becomes master clock (for that clock domain).
When multiple devices have their Preferred Master
checkbox ticked, the master will be elected
automatically from within that group.
If 'Slave Only' is shown instead of a checkbox, it
indicates that the device is not capable of acting as
a master clock.
• “Enable Sync To External”: Forces the Dante
module to derive its clock from an external source -
either from a host device word clock, or from an
auxiliary device. This will also ensure that this
Dante device becomes master clock for the relevant
clock domain (unless another device has 'Preferred
Master' selected). It is not normal practice to
configure more than one device per clock domain
with an external clock source. In this case, the user
is assumed to have synchronized external word
clock sources (e.g. house clock).

CrossNET 169
 CrossNET

Where the checkbox is present but greyed-out (and

inactive), it means that the Dante device can be
slaved to an external word clock, but it cannot be
set directly from “Dante Controller” - it must be done
via the host device user interface, or via some other
method (e.g. third-party control software). If the
checkbox is greyed out and populated, it means
that the Dante device is currently slaved to the
external clock.

If N/A is displayed, it means that the device does

not support slaving to an external word clock.

NB: If no clock status information is displayed for a particular

device, it can indicate a ConMon (Dante control and
monitoring service) failure on the device. The device may
need to be reset or restored.

The way to configure DANTE synchronism of an AEQ device

will change depending on if the unit will work in master or
slave mode and, in the case of FORUM and BC2000D Matrix
or ARENA), if there is one or more DANTE boards (FR14 for
FORUM and BC2214/BC2224 for BC2000D).

Keep it in mind that only one system device will work as

master, the rest of devices will work as slaves.

• Device NETBOX 8, NETBOX 32, CAPITOL,

FORUM with 1 module FR14 or BC2000D with 1
module BC2214 or BC2224:
- Master mode: in “Clock Status” tab of Dante
Controller mark the “Preferred Master” and
“Enable Sync To External” checkboxes.
- Slave mode: in “Clock Status” tab of Dante
Controller don't mark the “Preferred Master”
and “Enable Sync To External” checkboxes.

CrossNET 170
 CrossNET

Example 1

In addition, the device must be also configured as master or

slave (depending on the configuration that will be applied by
Dante Controller) by means of the specific software of the
device (NetBox Tool, CAPITOL Setup, FORUM Setup, Matrix
Setup or Console Setup).

• Device FORUM with 2 modules FR14 or BC2000D

with 2 or more modules BC2214 or BC2224
- Master mode: in “Clock Status” tab of Dante
Controller mark the “Preferred Master” and
“Enable Sync To External” checkboxes of all the
modules FR14 or BC2214/BC2224.

Example 2

Example 3

CrossNET 171
 CrossNET

- Slave mode for FORUM: in “Clock Status” tab of

Dante Controller mark only the “Enable Sync To
External” checkbox of the FR14 module placed in
slot 13.

Example 4

- Slave mode for BC2000D: in “Clock Status” tab of

Dante Controller mark the “Enable Sync To
External” checkbox of all the modules
BC2214/BC2224 except of the one that will extract
synchronism from the link:

o In the case of Matrix you can prioritize from

Matrix Setup the synchronism extraction in
the boards configured as sync slaves in order
to fix beforehand which one will have higher
priority for that extraction function.
o In the case of Arena, it's not possible to
configure that priority, all the boards will have
the same probability of being the one that will
extract synchronism: you'll have to check
which board will make that function by means
of Status Information application (it will
indicate "REMOTE SYNC ENABLED") or by
checking the LED signaling of the board (fast
blinking with momentary interruptions)

CrossNET 172
 CrossNET

Example 5

In addition, the device must be also configured as master or

slave (depending on the configuration that will be applied by
Dante Controller) by means of the specific software of the
device (FORUM Setup, Matrix Setup or Console Setup).

About Clock Domains

Dante Devices that are not configured with sample rate pull-
up/down operate on the default clock domain, using the
default clock. Devices that are configured with sample rate
pull-up/down operate on separate 'clock domains', which
have their own dedicated PTP clocks, adjusted to account for
the pulled up/down sample rates.

Clock domains are not physically separated; they all exist on

the network simultaneously. Devices with pull-up/down
synchronize to the appropriate clock for their pull-up/down
setting, and ignore other clocks. Those devices are shown
with the relevant pull-up/down value against their Clock
Status in the Clock Status tab.

Dante devices can only transmit audio to, and receive audio
from other devices on the same clock domain. For example,
a device with zero sample rate pull-up/down operates on the
default clock domain, and cannot transmit audio to, or receive
audio from any devices on the +4.1667% clock domain, or
the -1% clock domain, etc.

CrossNET 173
 CrossNET

Up to 5 separate clock domains can be supported at any one

time. All clock domains have their own master clock.

About “Master Clocks”

The Dante network master clock (often also referred to as the

'Grand Master'), is displayed at all times in the center of the
toolbar of the Network View. This is the device that is
providing the time sync source for all devices on the network.

If multiple clock domains are in use, the master clock for

each domain is shown, in a comma-separated list.

The master clock is chosen automatically through an election

process, though there are user configurable parameters that
allow prioritization of some devices in the master clock
election. Configuring a device to have an external word clock
source will force that device to become master clock, unless
another device has 'Preferred Master' set.

Checking the 'Preferred Master' flag will always result in that

device (or the device with the lowest MAC address, if more
than one device has been checked) becoming master clock
for that domain.

CrossNET 174
 CrossNET

NB: If the master clock device is not directly visible to “Dante

Controller” (for example, if the master clock device is for
some reason only connected to the secondary network, and
“Dante Controller” is only connected to the primary network),
the 'Master Clock' display in the toolbar may show a MAC
address string, instead of the device name.

Clock Status Monitoring

Dante devices are monitored by “Dante Controller” to

establish the status of their clock synchronization with the
Dante network master clock.

There are two levels of monitoring: 'passive' and 'active':

- In passive mode, “Dante Controller” will report if a

clock loses sync (or regains sync) with the master
clock.
- In active mode, “Dante Controller” will also report if
a clock is showing signs of instability. If a device
clock is significantly unstable, it can lose sync with
the master clock, which will result in the device
being automatically muted.

CrossNET 175
 CrossNET

Why would a device clock be unstable?

There are a range of network conditions that can interfere

with a device’s clock stability. These include:

- A switch on the network is configured to use Energy

Efficient Ethernet ('Green Ethernet') functionality.
- A 100 Mb switch or link is present where a Gigabit
connection is required.
- One or more switches are incorrectly configured.
- A 'problematic' external word clock is being used as
the master clock.

Passive monitoring

Passive monitoring is on all the time. If a Dante device

loses sync with the master clock, or regains sync with the
master clock, it reports the event to “Dante Controller”.
“Dante Controller” records these events in a log file, and
also will display an alert: the Clock Status Monitor icon (at
the bottom right corner of the main window) will light up
red.

Clicking the icon opens the Clock Status Monitor, which

includes 2 tabs:

- “Log”: clock
status event log
- “History”: clock
status histogram.

CrossNET 176
 CrossNET

Active Monitoring

When active monitoring is switched on, “Dante Controller”

begins actively monitoring the behavior of supported
devices to identify signs of clock instability. If a clock
exhibits significant instability, the Clock Status Monitor
icon will light up amber, and a warning event will be
recorded in the clock status event log.

Click the icon to open the “Clock Status Monitor” window.

Active monitoring is off by default. To activate it, click the

Clock Status Monitoring button on the main toolbar:

When Active Clock Status

Monitoring is active, the
button is shown in green.

To switch it off, click the button again.

NB: Active monitoring does not affect passive monitoring.

CrossNET 177
 CrossNET

Devices including an active supervision DANTE support

module are:

- "Brooklyn II” module, incorporated in all AEQ

systems described in the present manual.
- Dante PCIe cards.
- Dante-MY16-AUD cards.
- Ultimo devices.

If the device includes a Brooklyn II module, this is

displayed in the “Product Type” in the “Device Info” tab
and also in the sections “Device Information” and “Dante
Information” in the “Status” tab within the corresponding
“Device View” window.

“Clock Status Monitor”

The Clock Status Monitor
window includes two
tabs: “Log” and “History”.

“Log”

The Clock Status log shows time-stamped clock status

events for each device that has been identified as
unstable, or has lost or regained sync with the master
clock.

CrossNET 178
 CrossNET

The event types are:

Clock Sync Warning: Indicates that a clock has been

identified as unstable, and is at risk of losing sync with the
master clock.

Clock Sync
Unlocked:
Indicates that a
device has lost
sync with the
master clock.
This will result
in the device
being automatically muted until it regains sync.

Clock Sync Locked: Indicates that a device has regained

sync with the master clock.

To delete all Clock Status log entries, click Clear. This will
reset the Clock Status Monitor icon to green.

NB: This will also clear all other event log entries (the
Clock Status log is a filtered view of the main event log).

“Dante Controller” will then resume monitoring (unless the

Clock Status Monitoring button is switched off).

To save the event log as an XML file, click on Save.

CrossNET 179
 CrossNET

“History”

The History tab can be used

to establish the stability of
device clocks. It shows a
histogram of clock frequency
offset for the selected device,
and the current frequency
offset value, updated in real
time.

The following information is

also displayed:

• Mute status.
• Sync status.
• External word clock.
• Preferred Master status.

About Clock Offset

Hardware clocks are based on a vibrating (piezoelectric)

quartz crystal. All crystals are slightly different, and vibrate
at slightly different frequencies. When a device ('slave')
clock wants to sync to a master network clock, its
frequency must be 'pulled' up or down to match the
frequency of the master clock. The amount that the clock's
frequency is pulled is referred to as 'offset'.

CrossNET 180
 CrossNET

Hardware clocks can only support a certain amount of

offset, referred to as 'pull range'. If the pull range is
exceeded, the slave clock will lose sync with the master
clock, and the device will be automatically muted.

Software clocks typically use an algorithm to derive a

clock from an internal counter. Software clocks can
support any amount of offset.

Rapidly-changing offset can also cause a slave clock to

lose sync with the master clock.

Various factors can destabilize slave clocks by affecting

their offset, such as:

• Overloaded network links.

• Poorly-implemented EEE (Energy Efficient
Ethernet).
• A master clock that is derived from an inaccurate
external word clock (one that does not run at its
nominal frequency).

CrossNET 181
 CrossNET

About the Histogram

The horizontal axis of the histogram shows the distribution

of clock frequency offset measurements against the
nominal frequency of the clock, in parts per million (ppm).
The zero
point of the
horizontal
axis
correspond
s to the
clock's
nominal
frequency
(i.e. the
frequency
that the
clock is
intended to
run at, for
example, 48 kHz).

The vertical axis shows the number of measurements

recorded at each data point, on a logarithmic scale.

The histogram is continually updated, with measurements

taken roughly once per second.

• To select devices, click the drop-down menu at the

top.
• To clear the histogram, click Clear.
• To save a png format screenshot of the current
data, click Save.

CrossNET 182
 CrossNET

Interpreting the histogram

The histogram can be seen as an indication of how much

work a slave clock is doing to stay in sync with the master
clock.

Generally, a stable and accurate clock will show

consistently very low offset (in the
order of a few ppm). It means that
the clock's nominal frequency
closely matches the master clock,
and it is not having to change its
offset very much to stay in sync.

A histogram that shows a

distributed range of offsets
indicates an unstable clock - it is
having to change its offset
significantly, and often, to stay in
sync with the master clock. This
can be due to overloaded network
links, or poorly-implemented EEE.

A histogram that shows

measurements in amber and/or
red indicates a clock that might be
currently stable, but has little room
for maneuver; its offset could
easily move outside its pull range,
at which point it will lose sync
completely. This can result when
the master clock is derived from
an inaccurate external word clock.

C.7.4.4 “Network Status”

CrossNET 183
 CrossNET

The Network Status tab provides a range of network-related

information across all devices in the network.

This view includes subscription status, bandwidth and latency

information, and can be used to quickly identify any potential
network traffic issues.

The tabular view presents the following information, in columns

from the left:

• Device Name”: The device name currently associated with

the device.
• “Subscription Status”: The icon in the Subscription Status
column displays a summary of subscription states for the
device. If any of the device's channels are not successfully
subscribed, the relevant icon will be displayed here.
Check the section “Subscription to audio channels” in section
4.7.4.1 for information about the various icons that can be
displayed in the Subscription Status column.
• “Primary Status”: The Primary Status column indicates the
link speed of the primary Dante network interface for the
device.

• “Secondary Status”: The Secondary Status column

indicates the link speed and status of the secondary Dante

CrossNET 184
 CrossNET

network interface for the device (if applicable). 'N/A' indicates

that the device does not have a secondary interface 'Link
Down' indicates that the device has a secondary interface,
but it is not currently connected.

• Bandwidth Columns: Use the bandwidth columns to see an

approximation of transmit and receive traffic over individual
device interfaces. (Indicated in Mbps = Megabits per
second):

o “Primary Tx B/W”: It displays an approximation of the

current transmit bandwidth on the primary Dante
network interface for the device.
o “Secondary Tx B/W”: It displays an approximation of
the current transmit bandwidth on the secondary Dante
network interface for the device.
o “Primary Rx B/W”: It displays an approximation of the
current receive bandwidth on the primary Dante
network interface for the device.
o “Secondary Rx B/W”: It displays an approximation of
the current receive bandwidth on the secondary Dante
network interface for the device.
• “Latency Setting”: Shows the current latency setting for the.
AEQ equipment is usually configured to 1ms and “Dante
Virtual Soundcard” to 4-6 ms.
• “Latency Status”: The Latency Status column displays icons
representing the recent latency performance of the device.

o A green light indicates that the device is

subscribed, and there are no latency problems - i.e. all
audio packets are arriving well within the device's
latency setting.

o An amber light indicates that audio packets for

one or more channels are arriving at or near the limit of

CrossNET 185
 CrossNET

the device's latency setting. You may need to increase

the device's latency, or reconfigure the network to
prevent audio glitches due to packet loss from late-
arriving audio packets

o A red light indicates that one or more audio

packets have arrived outside the device's latency
setting. This will result in audio glitches. The device's
latency setting should be increased, or the network
reconfigured (for example, by reducing the number of
network nodes in between the transmitter and the
receiver).

o A grey light indicates that the device is not

currently subscribed.
• “Packet Errors”: A red light in the Packet Errors column
indicates that one or more audio packets have been
corrupted in between the switch and the receiver. This is
usually due to a faulty Ethernet cable.

C.7.4.5 “Events”

The “Events” tab in “Network View” provides information on

significant changes and failures in the
network.

“Dante Controller” continually monitors Dante devices and the

network as a whole. It is able to watch for problematic
configurations, unexpected problems and communication failures

CrossNET 186
 CrossNET

between itself and Dante network devices. Events are displayed

and stored in an event log.

Events fall into one of three categories (depending on the severity,

from lower to higher):

• “Information”
• “Warning”
• “Error”

Filtering the Events List

Use the drop-down menu at the bottom left of the view to filter the
events list.

• When set to Information, all events are

shown.
• When set to Warning, only warning and
error events are shown.
• When set to Error, only error events are
shown.

Clearing the Events List

CrossNET 187
 CrossNET

To clear the events list, click the Clear button. When new events
are detected that match the current filter setting, they are displayed
in the event list.

If you have switched to another Network View tab, new events in

the event list will also be indicated by a red Event Log LED icon in
the Status Bar. Clicking the LED icon will take you straight to the
Events tab and will clear the Event Log LED.

NB: The Event Log LED icon will always remain green while the
Events tab is open.

Saving the Events log

To save the events list, click the Save button. The list is saved as a
text file with file extension “.log”. All events in the list are saved (the
filter does not apply to saved events logs).

Automatic Events logging

Events are also continuously written to a log file. Each time “Dante
Controller” is started, it creates a new log file (with a time-stamped
filename, to avoid overwriting previous logs).

You can find the path to these log files under Help About. To
delete log files more than seven days old, click the Delete old Log
files button.

Events Classification

CrossNET 188
 CrossNET

The following events are classified as Errors:

• Invalid link local Address.
• Subnet mismatch on Dante interface.
• Subnet match with non-Dante interface.
• Multiple addresses with matching subnets.
• Subnet conflict of Dante interface on primary.
• Subnet conflict of Dante interface on secondary.
• Unknown address error.
• Fail Safe Mode.
• Unknown device issue.
• Elevation to Clock Master.
• Fanout Configuration detected.
• Mismatched clock pull up subdomain.
• Wrong subdomain for pull up.
• Unknown subdomain.
• Audio mute / Audio unmute.
• Clock Sync lock / unlocked

The following events are classified as Warnings:

CrossNET 189
 CrossNET

• Resolution failed.
• Elevation to Grand Master.
• Multiple external clock sources.
• Cannot elevate to Clock Master.
• Clock Sync Warning.

The following events are classified as Information:

• Request Timeout Error.

• Response Timeout Error.
• Demotion from Clock Master.
• Demotion from Grand Master.
• Reboot requiered.

C.7.5 Automatic Notification of Device Errors

“Dante Controller” is able to identify several types of problems that a

Dante device may experience. A device that is found to have problems
will have its device name displayed in red. Additional information about
the problem can be found by double-clicking on the device.

A device displayed in red will either have entered failsafe mode or have
an identified issue with its IP configuration. These states are described in
more detail below.

Incorrect IP address configuration

CrossNET 190
 CrossNET

Dante networks use IP Addressing to communicate. Incorrect address

configuration can make it hard or impossible for a Dante device to
communicate. “Dante Controller” attempts to identify and report several
types of incorrect IP address configuration, including:

• Having multiple DHCP servers on the same network.

• Incorrectly configured static IP addresses.
• Connecting the secondary interface of a Dante device to the
primary network.
• Different interfaces on the same device using the same IP address
subnet.

Failsafe mode

A device will enter failsafe mode when the firmware image stored on the
board has become corrupted. Although rare, this can occur when:

• The firmware update process is interrupted by power loss or

network failure.
• The firmware image itself that was used in an upgrade is corrupt.

If your device enters failsafe mode, please use the Failsafe Recovery
function in the Firmware Update Manager application (if available) or
contact the AEQ Technical Support.

Other Event Notifications

CrossNET 191
 CrossNET

“Dante Controller” will also notify you of network status, general device
events and clock status events, via the LED icons in the Status Bar.

C.8. “Dante Controller” use: “Device View”

The Device View is used to view and modify detailed information and
settings for a specific device. Device view can be activated by double-
clicking a device name in any of the Network View tabs (except Events),
or by selecting Device View from the Device menu (Ctrl + D, or Command
+ D) in the Network View window. The Device View opens in a new
window. Multiple device views can be open simultaneously.

The label of the device being viewed is displayed in the middle of the
toolbar. In the screenshot above, “CAPITOL-74623” is the device being
displayed d in the drop-down list box.

The device viewed can be changed by selecting another device from the
drop-down list.

CrossNET 192
 CrossNET

Multiple Device View windows may be opened from the Network View, so
that several devices can be examined simultaneously.

CrossNET 193
 CrossNET

The Device View has up to six tabs, allowing you to see different
information relating to a specific Dante device:

• “Receive”: display and configure device’s receive (Rx) channels.

• “Transmit”: display and configure device’s transmit (Tx) channels
including multicast
• “Status”: device software, clock and network status information.
• “Latency”: view latency histograms (supported devices only).
• “Device Config”: rename device, change sample rate and set
other attributes (as relevant to device type).
• “Network Config”: view and edit network configuration.

C.8.1 “Device View” Menu Bar

The menu bar of the

“Device View” screen
includes 4 sub menus.
“File“, “Device“, “View
“and “Help”. The list of options included in each of them is described
below:
• “File”:
- “Close Window” (Alt + F4).

• “Device”:
- “Refresh” (F5): Refreshes the displayed network / device
data.
- “Create Multicast Flow" (Ctrl + M).

CrossNET 194
 CrossNET

• “View”:
- “Show/Hide Channel Groups” (Ctrl + Mayus + G)
• “Help”:
- “About”: shows “Dante Controller” version and current log file.
- “License”: displays the license text.
- “Contents” (Mayus + F1): opens a help window and displays
help contents

C.8.2 “Device View” Tool Bar

There is a tool bar below the Menu bar including six buttons:

• Refresh: Re-load routing and configuration information for the

current device.

• Web Config: Some Dante devices can be configured via a web

interface. This button opens a web browser window which can be
used to perform functions such as firmware upgrades. This feature
is not supported on AEQ and most of Dante devices.

• Identify: Identify the current device by, for example, causing its
LEDs to flash. Note that this feature is not supported on AEQ and
most of Dante devices.

• Multicast: Configure multicast transmit flows on the current

device.

• Channel Groups: Activates / deactivates Channel Groups.

• Help: Opens a help window.

CrossNET 195
 CrossNET

The toolbar also provides a drop down list of all available devices on the
network, which allows you to switch the Device View to a different device.

C.8.3 “Device View” Tabs

There are 6 tabs below the tool bar that we describe in detail below:

CrossNET 196
 CrossNET

C.8.3.1 “Receive”

The “Receive” tab shows a list with all the subscribed and standby
receive channels included in the current device, as well as
information about the subscribed channels only. It also permits the
creation of subscriptions from the available channels list.

The tab is split into two panes: Receive Channels, and Available
Channels.

CrossNET 197
 CrossNET

• “Receive Channels”: The receive channels area, shown in

the left area of the screen, contains 4 fields:

- “Channel”: It is an editable field showing the labels of

the current device receive channels. These labels can
be edited to rename the channels by double-clicking
on the channel’s name and typing a new text in
-

- “Signal”: Supported devices will also show the following

channel metering icons, indicating the presence of
audio on subscribed channels:

: Channel is either muted, or receiving audio

at less than -61dBFS.

: Channel is receiving audio between -61

dBFS and 0 dBFS.

: Channel is clipping.
Currently, Brooklyn II (featured in AEQ multichannel
devices) and PCIe devices support channel metering
in “Dante Controller”. You can check your device type
in the “Device Info” tab included in “Network View”.
“Connected to”: muestra el canal de Tx al que el canal
de recepción está suscrito actualmente.

CrossNET 198
 CrossNET

- “Status”: shows the status of both primary and

secondary subscriptions, using the following icons:

: Subscription is OK and audio should be

flowing.

: Subscription is unresolved - usually

because the transmitting device has been
removed from the network, or is switched off.

: No subscription, or a subscription error.

: Subscription is via unicast connection.

: Subscription is via multicast connection.

Subscriptions can show several symbols in the Status

column. Common status icon combinations and their
meanings are as follows:

: Unicast device successfully

subscribed to a transmitter.

: Redundant device successfully

subscribed on both primary and secondary via
unicast.

: Redundant device successfully

subscribed on both primary and secondary via
multicast.

: Redundant device successfully

subscribed on primary only via unicast. This is
typically seen when the secondary interface is
not connected

CrossNET 199
 CrossNET

• “Available Channels”: The Available Channels pane, at the

right side of the screen, lists the devices and advertised
channels available on the network. Devices that are greyed
out indicate that this receiver cannot subscribe to those
channels or devices. This is typically because of a mismatch
in parameters (e.g. sample rate incompatibility etc.), or
because a device cannot route audio to itself.

Creating Subscriptions:

Subscriptions are created by selecting a channel from the

Available Channels list in the right-hand pane of the Receive
Tab, then dragging and dropping it onto the appropriate
receive channel in the left-hand pane of the Receive Tab.

Multiple channels can be selected and then dragged and

dropped onto the Receive Channels pane, to make several
subscriptions simultaneously.

CrossNET 200
 CrossNET

Cancelling subscriptions:

It is also possible to cancel subscriptions from the “Receive

Channels” area. In order to do so, the subscription to be
cancelled must be selected within the “Connected to” column,
and then click on the “Unsubscribe” button located in the
bottom area of the screen (this can also be done by pressing
the keyboard’s “Del” key).

It is possible to cancel more than one subscription at once,

by selecting several at the same time (by holding the Ctrl key
down) and then clicking on the “Unsubscribe” button (or “Del”
key).

CrossNET 201
 CrossNET

C.8.3.2 “Transmit”

The “Transmit” tab is used to inspect and modify the transmit

configuration of a device.

CrossNET 202
 CrossNET

The Transmit Tab is arranged in two areas:

• “Transmit Channels”: The area on the left pane of the tab

shows the Tx channels for the device, and any user-defined
channel label. It allows you to create labels (or editing them
by double-clicking on the channel’s name and typing a new
text in) for transmit channels. Input to the table is filtered to
prevent illegal characters from being used in channel labels.
Tx channel labels must be unique within a device (the same
name cannot be used for two different channels).

Supported devices will also show the following channel

metering icons in the Signal column, indicating the presence
of audio on subscribed channels:

: Channel is either muted, or receiving audio at less

than -61 dBFS

: Channel is receiving audio between -61 dBFS

and 0 dBFS.

: Channel is clipping.

• “Transmit Flows”: The area on the right pane of the tab

indicates how many unicast flows are currently in use, as well
as the multicast transmit flows that have been configured on
the device. Multicast flows are listed in ID order, including the
channels contained within the flow. Unicast flow details are
not displayed in the transmit flow window.

CrossNET 203
 CrossNET

C.8.3.3 “Status”

The “Status” tab is used to obtain current information about a Dante

device.

The tab is divided into four sections. The information presented on

this tab can be very useful when investigating networking or

clocking issues in the system. The Refresh button can be

used to update this information if required.

CrossNET 204
 CrossNET

NB: Not all Dante devices support the display of all of this
information.

The available sections are as follows:

• “Device Information”: This provides the following general

information about the device:
- “Manufacturer”: The name of the device manufacturer.
- “Product Type”: The type of device.
- “Product Version”: The product version.
- “Software Version”: The version of the manufacturer
software running on the device.
- “Firmware Version”: The version of the manufacturer
firmware running on the device.
• “Dante Information”: This provides Dante-specific
information about the device:
- “Model”: The Dante device type.
- “Software Version”: The version of the Dante software
running on the device.
- “Firmware Version”: The version of the Dante firmware
running on the device.
• “Clock Synchronization”: This provides the following
information about device clocking:
- “Mute Status”: 'Muted' indicates that the device is has
been automatically muted (due to a clock
synchronization problem, or because the external word
clock is invalid). 'Unmuted' indicates that the device is
not muted, and audio is flowing normally.
- “Sync Status”: 'Locked' indicates that the device is
locked to the network PTP clock. 'Not Locked'
indicates that the interface has not achieved lock with
the network PTP clock

CrossNET 205
 CrossNET

- “External Word Clock”: 'No' indicates that the device

has been configured to use the internal clock source.
'Yes' indicates that the device has been configured to
accept an external word clock source NB If the Dante
device is configured to accept an external word clock
source, it is important to make sure that the host
equipment has been configured to provide its word
clock to the Dante device. Check your product manual
for more information.
- “Preferred”: 'No' indicates that the card has not been
set to preferred master mode. 'Yes' indicates that the
card is set to preferred master mode.
- “Frequency Offset”: Indicates the offset from the
network clock master measured in parts-per-billion.
• “Interfaces”: Provides the following information about the
primary network interface (P) and the secondary network
interface (S):
- “IP Address”: The IP address currently assigned to the
interface.
- “MAC Address”: The Media Access Control address of
the interface, associated with the Ethernet layer.
- “Tx Utilization”: Shows the current total transmit
bandwidth in use.
- “Errors” (on the same line as Tx utilization): shows the
number of transmit Cyclic Redundancy Check (CRC)
or packet errors detected since the device was last
started.
- “Rx Utilization”: Shows the current total reception
bandwidth in use.
- “Errors” (on the same line as Rx utilization): shows the
number of receive Cyclic Redundancy Check (CRC) or
packet errors detected since the device was last
started.

CrossNET 206
 CrossNET

NB 1: The “Rx Utilization” includes not only network traffic destined

for the Dante device, but any other multicast or broadcast traffic
received at this network interface.
NB 2: As a rule of thumb neither the “Rx Utilization” nor the “Tx
Utilization” should exceed about 85% of the link speed in order to
guarantee good clock synchronization performance (links are full
duplex).

The graphic also indicates the speed and connected state of the
interface as follows:

Indicates that the link is operating at 1 Gbps.

Indicates that the link is operating at 100 Mbps.

Indicates that the link is not connected, or that

there is an error. The IP address will read N/A, and Tx and
Rx utilization will be 0 kbps.

The information about the secondary network interface will only be

displayed if the device supports redundancy and it’s configured as
redundant.

C.8.3.4 “Latency”

For supported devices, the “Latency” tab displays histograms of

audio packet latency for each transmitter that the device is
subscribed to.

Newer Brooklyn II (featured in AEQ multichannel devices) and PCIe

devices support latency monitoring in “Dante Controller”. You can
check your device type in the “Device Info” tab under “Network
View”.

CrossNET 207
 CrossNET

About Latency and Packet Loss:

Latency is used to account for the delay between an audio packet

leaving the transmitter, traversing the network (potentially through
multiple switches) and reaching the receiver.

If a receiver's latency setting is too low, audio packets will not have
time to get from the transmitter to the receiver before they are
supposed to be played out. When this happens, the receiver will
drop packets (i.e. it will throw packets away, because they are 'late
to the party').

Packet loss results in audio glitches, so it is very important to

ensure that all receivers have their latency set high enough to
prevent packet loss.

Setting device latency too high, however, can interfere with low-
latency applications (for example, real-time monitoring when
recording vocals), so it is sometimes important to find a balance
between low latency and guaranteed audio integrity.

The “Latency” tab can be used to identify devices that are dropping
packets because their latency is set too low, and also devices that
could potentially have their latency reduced (if required; generally,
the default Dante latency of 1ms is more than adequate for low-
latency applications).

CrossNET 208
 CrossNET

About the Histogram:

The transmitter's name is displayed at the top of the histogram,

along with the latency value against which the histogram is
reporting.

The horizontal axis shows the distribution of audio packet latency

measurements from the transmitter. The vertical axis shows the
number of measurements recorded at each data point, on a
logarithmic scale.

Measurements are taken at roughly 1 second intervals, from when

“Dante Controller” is started.

CrossNET 209
 CrossNET

To clear the histogram, click Clear. Latency measuring will then

restart.

To save the histogram as a png image, click Save.

NB: If any subscriptions are via multicast flows, there may be two
histograms displayed for one transmitter: one histogram for the
unicast flows, and one for multicast. This is because multicast flows
always use a latency of 1ms. If the receiver is set to a latency other
than 1ms, two histograms will be displayed.

The following information is also displayed:

• “Setting”: indicates the latency setting for the histogram. In

most cases, this will be the same as the latency setting on
the receiver. However, for some subscriptions, Dante will
automatically apply a different latency. For example:
o Multicast flows are automatically set to a minimum of
1ms
o If a transmitter does not support the latency set on the
receiver (i.e. it can't guarantee delivery within the
required latency), Dante will increase the latency to the
lowest setting supported by the transmitter.

• “Peak”: indicates the peak latency since measuring started.

• “Average”: indicates the average latency since measuring
started.
• “Late”: indicates the number of measurements taken that
included one or more late packets (note that each
measurement typically includes many packets).
• “Duration”: indicates the running time since measuring
started.

CrossNET 210
 CrossNET

Interpreting the Histogram:

If all bars are green and falling well

within the limit of the histogram (i.e.
towards the left or middle of the
histogram), it indicates that the latency
setting for the receiver is set high
enough to prevent packet loss

If any bars are amber, it means that

some packets are arriving near the
limit of the latency setting. Network
traffic fluctuations could potentially
lead to extra delay which could cause
packets to arrive late. A histogram of
this type indicates that the receiver
latency should be increased if
possible.

If any bars are red, it indicates lost

packets, and audio loss. The receiver
latency should be increased, or the
network reconfigured.

CrossNET 211
 CrossNET

C.8.3.5 “Device Config”

This tab on the Device View window allows you to configure device
specific parameters. The specific options available will depend on
the capabilities of the device. In the case where a device does not
support configuration via “Dante Controller”, the tab will be
disabled.

NB: In the case of “Dante Virtual Soundcard” the configurable

parameters available from this tab are "Rename Device", "Sample
Rate" and "Encoding". The remaining parameters are configured
from its own user interface on the PC or Mac.

CrossNET 212
 CrossNET

These are the configurable parameters:

• “Rename Device”: Allows you to enter a new Dante 'friendly

name' for the device. The text field displays the current
name. To change the device name, enter a new name in the
text field and press “Apply”.

IMPORTANT NOTE: This action will delete the existing audio

routings from this device to others. When you click on
“Apply”, a confirmation window will appear:

CrossNET 213
 CrossNET

• “Sample Rate”: Shows the current sample rate of the device,

and allows you to change the operating sample rate of the
Dante device. This may require the device to be rebooted to
take effect. All sample rates supported by the device are
shown in the drop down menu.

IMPORTANT NOTE: When working with AEQ equipment,

this sampling frequency must be set to 48 kHz.

• “Pull-up/down”: Shows the current pull-up/down setting for

the device, and allows you to change the pull-up/down
setting. The pull-up/down setting can be used to adjust the
sample rate of the device to synchronize audio with video
that has undergone frame rate conversion. For example, to
synchronize Dante audio with video that has been converted
from 24 fps to 25 fps, set the sample rate pull-up/down for
any relevant Dante audio devices to +4.1667%.

NB: Changing the sample rate pull-up/down for a device

places that device in a dedicated clock domain. Dante
devices can only transmit audio to, or receive audio from
other devices on the same clock domain. See “Clock Status
View” for more information.

IMPORTANT NOTE: This configuration is not suitable for

AEQ equipment.

CrossNET 214
 CrossNET

• “Encoding”: Show and allows to change the current audio bit

depth. This parameter is only available for “Dante Virtual
Soundcard”. Select a value and click “Yes” to modify it.
• “Device Latency”: Shows the current device latency setting,
and allows you to change the operating receive latency for
the selected device. Select a value and click “Yes” to apply
the latency to all flows that the device is receiving.

IMPORTANT NOTE: changing the latency value will cause

disruption in the audio while the flows are re-established at
the new latency setting, as indicated in the confirmation
window:

NB: DANTE networks feature an extremely low latency. The

0.15 ms. option won’t be available for devices including an
internal switch, as happens with all AEQ AoIP devices.
Taking into account these internal switches, connecting two
pieces of equipment together using a simple straight cable,
we already have two switches, and if one more is connected
in between, we now have three. The maximum latency value
setting recommended by AEQ is 1 ms. still allowing for
network topologies of certain complexity. 5 ms. latency is still
unnoticeable, so in case that audio cut-offs appear, it can be
increased to 2 or 5ms. The “Dante Virtual Soundcard” must
be configured from its own PC window to 4, 6 or up to even
10 ms.

On the other hand, the audio network is usually critical-

mission and should be isolated from any other Ethernet
service to avoid unnecessary or variable latencies.

CrossNET 215
 CrossNET

• “Reset Device”: allows you to remotely “Reboot” the Dante

interface, and also to reapply factory settings (“Factory
Reset”). Rebooting the Dante device may also require a reset
of the AEQ host audio equipment containing the device.
“Factory Reset” (available in some Dante devices) wipes the
following device configuration settings:
o User-defined device name.
o User-defined channel labels.
o Clock configuration (clock master / external clock
master setting).
o Static IP addresses.
o Redundancy configuration.
o Sample rate setting (including pull-up/down).
o Latency setting.
o Any existing audio routes.

Supported devices allow you to 'Clear Config' instead of

Factory Reset. Clear Config wipes the same configuration
settings listed above, but allows you to optionally keep the IP
settings (i.e. retain the Dante Redundancy settings, and any
static IP addresses currently configured in the Network
Config tab).

A reboot is required after clearing the configuration for the

changes to take effect. Some
devices will allow you to
automatically reboot after
clearing the configuration. If this
option is not available, a manual
reboot is required.

CrossNET 216
 CrossNET

C.8.3.6 “Network Config”

Use the “Network Config” tab to toggle supported (among them, all
AEQ devices feature two AoIP Ethernet ports), between Redundant
and Switched modes, and to specify static IP addresses for a
device's Ethernet ports.

CrossNET 217
 CrossNET

The available sections are:

• “Dante Redundancy”: Depending on the manufacturer's

configuration of a device, it may be possible to toggle the
device between Redundant and Switched modes, or to select
a Switch Configuration.
o “Redundant”: When a device
is set to Redundant, the
device will duplicate Dante
audio traffic to both Ethernet
ports, allowing the
implementation of a redundant network via the
secondary port. Not all devices support redundancy.
All AEQ devices covered by this manual include two
Ethernet AoIP ports and support this feature.

IMPORTANT NOTE: When there is a redundant

network, device primary and secondary interfaces
must be connected to separate networks.

o “Switched”: When a device is set to Switched, the

secondary Ethernet port will behave as a standard
switch port, allowing daisy-chaining through the device.
All AEQ devices covered by this manual include two
Ethernet AoIP ports and support this feature.
• “Addresses”: Dante devices obtain IP addresses
automatically by default, and in the vast majority of
circumstances there is no need to change the Addresses
settings. However, static IP addresses can be assigned if
necessary.

CrossNET 218
 CrossNET

To assign a static IP address:

1. Select 'manually configure an IP Address' for the

appropriate Ethernet port.
2. Enter the IP Address and Netmask.
3. Click Apply.

The DNS Server and Gateway settings are optional - the

device will use network defaults if they are not specified.

Click “Revert” to revert back to the previous settings.

NB: Assigning static IP addresses requires a device reboot.

C.9. Using “Dante Controller”: Multicast Transmit Flow Configuration

When clicking on the Multicast Setup button within Device View (no
matter what tag is selected), a Create
Multicast Flow dialog box will appear that
allows the user to aggregate several
channels to a new multicast flow.

CrossNET 219
 CrossNET

This window shows a list of the Tx channels for the device, and allows
you to add them to the new multicast flow that is being created, by
checking the tick box next to each channel name. Once you have
selected all the channels required, create the multicast flow by clicking
the Create button at the bottom of the dialog box. To abandon creating a
new multicast flow, click Cancel.

CrossNET 220
 CrossNET

A single multicast flow can contain up to the maximum supported

channels per flow for this device. This is displayed at the top of this
window, and is 8 channels for this device. If you select more than the
maximum allowed channels per flow, multiple flows will be created. Once
a flow has been created, it will appear in the list of flows in the transmit
pane, along with the channels contained within that flow. Channels
cannot be added to or removed from existing flows. Each time the dialog
is used to select additional channels, a new multicast flow will be created.

CrossNET 221
 CrossNET

By default, Dante devices 'prefer' multicast over unicast. When you click a
transmit channel to make a subscription, the receiver will automatically
connect to the channel via a multicast flow, if one exists. Likewise, when
a channel that did not form part of an existing multicast flow is added to a
new multicast flow, any existing unicast subscriptions to that channel will
automatically switch over to use the new multicast flow.

Care should be
taken when
deleting a
multicast flow, as
the existing
subscriptions will
convert back to
unicast. This has
the potential to
result in
exceeding the link capacity or maximum number of flows at the transmit
device, as multiple unicast flows will be established between the
transmitter and its receivers. It may be advisable to remove some or all of
the audio routes prior to deleting the multicast flow.

A good rule of thumb is to use multicast when there are more than two
receivers for a specific audio channel. You should also assume that the
flow will flood throughout the entire network, and therefore consume
bandwidth on all network links.

NB: Certain Ethernet switches support IGMP (Internet Group

Management Protocol), a protocol that provides the ability to 'prune'
multicast traffic, so that it travels only to those end destinations that
require that traffic. If this is the case, and IGMP is correctly configured on
all the Ethernet switches, then multicast audio will not flood throughout
the network, but will instead be sent only over the links required to deliver
it to subscribed devices. Appendix 1 provides information about
requirements and offers recommendations in this respect, and also
regarding the use of properly configured bridges or routers that can avoid
overflow produced by multicast audio streams in network areas not
related to audio.

CrossNET 222
 CrossNET

C.10. Presets

Dante Controller” supports the saving and loading of Dante network

routing and device configurations, known as 'presets'. A preset file
contains configuration and routing parameters for some or all of the
devices in the network.

Preset files are saved as xml, and can be edited offline. They are also
'device-agnostic' - they can be shared between networks with different
physical components.

You can use presets to:

• Backup and restore network configurations

• Quickly switch between saved network configurations
• Copy a Dante network configuration from a 'lab' or test network to a
live or production network

WARNING: danger of severe system misconfiguration. The Presets tool

is extremely powerful and allows the user to quickly make deep
modifications in the network, as well as the fast configuration of a
complex network by cutting and pasting characteristics of their individual
elements. For this reason it shouldn’t be used on real operating networks
until enough skills have been acquired, as any detail that is not properly
configured can cause dropouts or noises in the audio

CrossNET 223
 CrossNET

C.10.1 About Device Roles

Presets introduce the concept of 'device roles'. When a preset is saved,

the configuration and routing for each selected device is saved into the
preset as a device role, with the same name as the device from which it
was created.

The role is not 'tied' to its originating device. When a preset is loaded into
“Dante Controller”, each role can be applied to its originating device or to
another device (even if it does not support exactly the same functionality).
It is a transferable set of device configuration and routing parameters.

If a role is applied to a device that is different from the role's originating

device - for example, a role for console model A is applied to console
model B - “Dante Controller” will identify any issues that might arise (such
as unsupported sample rates) and will display those issues so they can
be addressed - or ignored, if they are not important.

C.10.2 Saving Presets

To save a Preset that includes all device parameters:

1. Click the button in the “Network

View” toolbar
“Save Preset” (Ctrl + S) can also be
selected in “File” option through the “Network
View” toolbar.

2.Select the devices that you wish to include in the preset. By default,
all available devices are selected; you can clear that selection by
pressing “None” button and select all devices again by pressing
“All” button.
3.Click “Save”.

CrossNET 224
 CrossNET

To save a Preset that includes a selection of device parameters:

1. Click the button in

the “Network View”
toolbar or select “Save
Preset” (Ctrl + S) in “File”
option through the
“Network View” toolbar.
2.Click “Advanced” button.
3.Select the devices that
you wish to include in
the preset.
4.Select the parameters
that you want to save for
the selected devices.
5.Click “Save” button.

The ‘Save a Preset File’ dialog

box will appear, allowing the
user to select a folder a file
name for the Preset files that will be created.

The preset is saved as an XML file, which can be manually edited if

required, using a text editor.

CrossNET 225
 CrossNET

C.10.3 Applying Presets

To load and apply a previously saved

preset, click the button in the “Network

View” toolbar”.

“Load Preset” (Ctrl + L) can also be selected in “File”

option through the “Network View” toolbar.

The “Apply Preset” dialogue is shown then, arranged in 4 columns,

representing the logical steps in applying a preset (from left to right).

CrossNET 226
 CrossNET

The 4 columns are:

• “Preset Elements”: Use the Preset Elements column to select the
parameters that you wish to apply from the preset to the target
network.
If the target network is not identical to the original network (from
which the preset was saved), some parameters might not be
applied successfully. For example, if some devices on the target
network do not support the same range of sample rates as the
devices on the original network, you could choose not to apply the
'Device Sample Rate' parameter, and change the sample rates
manually instead, once the preset has been applied.
Some preset parameters are not applicable to the current device
and so they are represented in light grey.

• “Preset Roles”: The Preset Roles column lists the roles or variants
of the device with different functions that were saved in the preset.
You can apply a role to the same physical device from which it was
created (if it exists in the target network), or to a different device in
the same network, or to another device in a new network.
When a role is applied to the same physical device, or a device of
the exact same model, the configuration and routing should be
replicated perfectly (although some subscriptions may be 'broken',
if the relevant transmitters are not also present on the target
network).

NB: This makes presets an ideal way to backup and restore

configurations for relatively static networks.

If a role is applied to a different device model or a different type of

device, the configuration and routing may not be replicated exactly
- the success of the role assignment will vary depending on the
functionality and channel support of the target device.

CrossNET 227
 CrossNET

Applying a role to a fundamentally different type of device may not

be very successful. For example, applying a role for a fully-
subscribed 32-channel mixing console configured at 96kHz to a 2-
channel amplifier that only supports 48kHz will be problematic -
only two channels can be subscribed (assuming the transmitters
are also present), and the sample rate will be rejected.

You can apply a role to multiple devices. You cannot apply multiple
roles to one device.

To see which devices a role has been assigned to, click the role.
The assigned device/s will be highlighted in the 'Target Devices'
column.

CrossNET 228
 CrossNET

Automatic Assignments: “Dante Controller” will automatically

assign roles to devices, based on the following rules:

- If there is a perfect device match (i.e. the physical device in

the original network from which the role was created is also
found in the target network), the role is assigned
automatically.
- If there is a device name match, the role is assigned
automatically.
- If a perfect match or a device name match cannot be made,
the role will be assigned automatically to a device of the
same manufacturer and model, assuming there is an
unassigned device of that type.

Removing Assignments: In order to delete a role, just select that

role in Target Devices and click on Clear (or press the keyboard’s
Del key), or select another role for it from the Preset Roles column
and then click on Apply Role.

Manual Assignments: To manually apply a role to a device:

- Drag the role onto the device, or

- Select the role and the target device/s in the 'Target Devices'
column, and click Apply Role.

CrossNET 229
 CrossNET

The LED icons against each role indicate the assignment status of
the role:

A grey icon indicates that the role has not been assigned
to any target devices.

A green icon indicates that the role has been successfully

assigned to one or more target devices.

An amber icon indicates that the role has been assigned

to one or more target devices, but there is a warning
condition associated with one or more of the assignments

A red icon indicates that the role has been assigned to

one or more target devices, but there is an error condition
associated with one or more of the assignments.

A black icon indicates that the role has been assigned to

a target device, but the assignment will have a potentially
terminal effect on the operation of the network.

• “Target Devices”: This column lists the device names of devices on

the currently connected Dante network and the roles that have been
assigned to them (if applicable).

The LED icons against each device indicate the assignment status of
the device:

A grey icon indicates that the role has not been assigned
to any target devices.

A green icon indicates that the role has been successfully

assigned to one or more target devices.

An amber icon indicates that the role has been assigned

to one or more target devices, but there is a warning
condition associated with one or more of the assignments

CrossNET 230
 CrossNET

A red icon indicates that the role has been assigned to

one or more target devices, but there is an error condition
associated with one or more of the assignments.

A black icon indicates that the role has been assigned to

a target device, but the assignment will have a potentially
terminal effect on the operation of the network.

• “Issues”: The Issues column lists all issues identified by “Dante

Controller”. Clicking a role or a target device will highlight the issues
associated with that role or role assignment.

The following are 'fatal' issues that could render the network unusable
(identified by a black LED icon):

- You cannot apply the same device name to multiple devices.

- You cannot apply the same static IP address to multiple
devices.
- You cannot apply a redundant configuration to a device that
does not support redundancy.

CrossNET 231
 CrossNET

Otras situaciones pueden generar o no un problema, dependiendo de

las necesidades de la red.

Applying presets:

To apply the preset, click “Ok”. This process will take around one
minute. Click “Cancel” to abandon the operation.

CrossNET 232