Various ethersound™ devices description, Mono-directional, non es100 devices, Bi-directional, non es100 devices – Nexo NUAR User Manual
Page 79: Es100 devices, Arious, Thersound, Devices description, Directional, Es100, Devices
NXES104 EXPANSION BOARD, REMOTE CONTROL AND ASIO DRIVER
connected, the right one (Activity) meaning that Ethernet frames are received.
Various Ethersound™ devices description
Here is a short reminder about various Ethersound™ devices.
Mono-directional, non ES100 devices
Simplest Ethersound™ devices are mono-directional, non ES100: These devices features
two ports (ES IN and ES OUT) and can be only connected to mono-directional networks
(64 channels of 24bits/48 KHz). Do not use them in a bidirectional part of an Ethersound
network or in a network where ES100 functions are used.
Bi-directional, non ES100 devices
More sophisticated Ethersound™ devices are bi-directional, non ES100. These devices
features two ports (ES IN and ES OUT) and can be connected to both mono and bi-
directional networks (2 x 64 channels of 24 bits/48 KHz). Do not use them in a network
where ES100 functions are used.
NB: The NEXO NX242-ES4 Digital TDcontroller is a bi-directional, non ES100 device.
ES100 devices
These devices compatible with the ES100 variant of the Ethersound™ network are bi-
directional devices (compatible with both mono and bi-directional networks) that offer new
functionalities (we called them the ES100 functions). Here is a list of the new ES100
functions:
• Device to device communication: With classical Ethersound implementation,
only the remote control computer can communicate with the various devices or the
network, and only audio data can be exchanged between devices. With ES100,
devices can send non-audio data between them without passing through the remote
control computer.
• Ring topology: Instead of the classical daisy-chain Ethersound™ network, you
can now connect the last OUT port of the network to the IN port of the primary
master, that has to be defined as the Preferred Primary Master through ESmonitor™
(every other device should be set as a loop back device). See ESmonitor™ User
Manual included with this software for details. Thus one of the network cables can fail
without any lost on the network integrity. To control the network, at least one of the
ES100 devices inside the network should have a “Remote ES100 port” (see bellow).
• 3
rd
communication port: Optionally, a 3
rd
Ethernet port can be added on the
ES100 device (this is the “Remote ES100 port” that you can find on the NXES104).
From this port you can take control over the connected device, but also over the
whole Ethersound™ network. To do so, connect a computer running the ESmonitor™
software, just like you were connecting to the IN port of the Primary Master device of
the network.
N.B.: You can easily recognize the ES100 devices thanks to this logo
PAGE 79 OF 140