oyvindskaaden/glados.no
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add files

Browse Source
This commit is contained in:
Øyvind Skaaden
2020-08-16 15:32:44 +02:00
parent 0bd406c224
commit f8dccc95bc
1411 changed files with 79926 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

459
_files/sound/bss/london/manual/MAIN/BLU_link.html Normal file
View File

@@ -0,0 +1,459 @@
<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="generator" content="Adobe RoboHelp 9">
<title>BLU link</title>
<link rel="StyleSheet" href="HtmlHelp.css" type="text/css">
<style title="hcp" type="text/css">
<!--
img.hcp1 { border-width:2px;
border-style:solid;
margin-top:0px;
margin-bottom:0px;
margin-left:0px;
margin-right:0px; }
p.hcp2 { font-weight:bold; }
span.hcp3 { font-weight:bold; }
p.hcp4 { margin-bottom:0; }
p.hcp5 { margin-left:40px; }
img.hcp6 { border:none; }
-->
</style>
</head>
<body class="ns-0 ltr">
<div id="globalWrapper">
<div id="column-content">
<div id="content">
<p><a name="top" id="top"></a></p>
<h1 class="firstHeading">BLU link</h1>
<div id="bodyContent">
<p id="siteSub">&#160;<script type="text/javascript" language="JavaScript1.2">//<![CDATA[
if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); }
//]]></script></p>
<div class="editsection" style="float: right; margin-left: 5px;">
<p>&#160;</p>
</div>
<p><a name="Overview" id="Overview"></a></p>
<h2>Overview</h2>
<p>BLU link is an audio bus found on all BLU-800/BLU-805,
BLU-160, BLU-320/BLU-325 and BLU-120, BLU-100, BLU-101
and BLU-102 devices. It carries 256 channels of audio
at 48kHz, and 128 channels at 96kHz, both at 24bit (note
that BLU-100, BLU-101 and BLU-102 are restricted to 48
channels at 48kHz). When connected in a loop, it has redundancy,
allowing any one BLU link cable to break while still maintaining
audio.</p>
<p>&#160;</p>
<div class="editsection" style="float: right; margin-left: 5px;">
<p>&#160;</p>
</div>
<p><a name="Hardware_Configuration" id="Hardware_Configuration"></a></p>
<h2>Hardware Configuration</h2>
<p>On the rear of the BLU link devices there are two BLU
link ports. One is the BLU link In, and the other BLU
link Out. Devices are connected together by wiring out
to in on all of the devices within your BLU link network,
making sure that the loop is complete so that there are
no empty BLU link ports. This is how three BLU-800 devices
should be wired together:</p>
<p><img src="BLU_linked.jpg" alt="Image:BLU linked.jpg" title="Image:BLU linked.jpg" width="614" height="258" border="2" class="hcp1"></p>
<p>&#160;<br>
You should not connect the BLU link ports to anything else
other than BLU link ports. BLU link will not function
if you tried to connect the BLU link to an Ethernet switch
for example.</p>
<p class="hcp2">Fault Tolerance</p>
<p>The network is capable of a degree of fault tolerance
due to the fact that each device receives the same audio
from 2 other devices. If a cable is broken the devices
which are no longer connected will detect the cable break.
One device will detect that its 'In' port is unconnected
and the other will detect that its 'Out' port is undetected.</p>
<p>In the diagram above, if there was a break in the cable
between U3 and U1, U1 will detect that its 'In' port is
no longer connected. Therefore the audio it sends to the
DSPs must now come from its 'Out' port. In addition, its
default behaviour of passing audio from 'In' to 'Out'
and vice versa is no longer applicable. Instead it must
route incoming audio from its 'Out' port back out of the
same port.</p>
<p>U3 will detect that its 'Out' port is no longer connected.
Since its default behaviour is to receive audio from its
'In' port, it can continue doing that. However, its default
behaviour of passing audio from 'In' to 'Out' and vice
versa is no longer applicable. Instead it must route incoming
audio from its 'In' back out of the same port.</p>
<p>The two devices in the middle of the ring do not know
that the ring has been broken and continue to forward
audio between their 'In' and 'Out' ports. They will also
continue to take their audio from their 'In' port to send
to the DSPs.</p>
<p>In this broken network a signal transmitted by U3 will
travel back along the ring until it reaches U1. There
the audio does a U-turn and heads around the ring the
other way and is then received by all the devices on the
network since it will be present at their 'In' port inputs.</p>
<p>Note that when the cable is broken, the audio takes
longer to reach its destination than before. This added
delay is not compensated for in any way, but is a side-effect
of the way the fault tolerance works.</p>
<p class="hcp2"><a name="Mastership"></a>Mastership</p>
<p>The BLU link network requires one device on the ring
to act as master for the whole ring. The master will provide
the clock for all the other devices on the ring. This
means that the whole ring is synchronised to a single
audio clock.</p>
<p>If a device has a CM1 card installed i.e. BLU-800 or
BLU-320, and the device is connected to a valid CobraNet
network, then that device will receive its clock from
the CM1 card by default. Therefore, if you connect a BLU-800
or BLU-320 to a CobraNet network, you must ensure that
devices on a particular BLU link ring are only connected
to a single CobraNet network.</p>
<p>If a device has an AVBX card installed i.e. a BLU-805
or a BLU-325, and that device is connected to a valid
AVB network, then that device will receive its clock from
the AVB card by default. &#160;Therefore, if you connect
a BLU-805 or a BLU-325 to an AVB network, you must ensure
that devices on a particular BLU link ring are only connected
to a single AVB network. </p>
<p>If a device has a DANTE card installed i.e. a BLU-806
or a BLU-326, and that device is connected to a valid
DANTE network, then that device will receive its clock
from the DANTE card by default. &#160;Therefore, if you
connect a BLU-806 or a BLU-326 to a DANTE network, you
must ensure that devices on a particular BLU link ring
are only connected to a single DANTE network. </p>
<p>It is not possible to connect multiple devices on one
BLU link ring to different CobraNet or to different AVB
or DANTE networks. Neither is it possible to connect multiple
devices to a mix of Cobranet and AVB networks. &#160;This
is because each CobraNet or AVB network will have a conductor
to provide the clock. The BLU link ring would then have
multiple clocks present on one network, and this is not
permitted.</p>
<p>If a BLU-800, BLU-320, BLU-805, BLU-325, BLU-806 or
a BLU-326 is set in <a href="Device&#32;Properties&#32;Pane.html">properties</a>
to <a href="BNC_Sync.htm">Sync to BNC</a> then that device
will take its clock from the BNC input on its rear panel.
<span class="hcp3">&#160;</span><span style="mso-fareast-font-family: Calibri;
mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman';
mso-ansi-language: EN-GB; mso-fareast-language: EN-GB;
mso-bidi-language: AR-SA; font-family: Arial, sans-serif;
font-size: 10pt;">Priority for these units should be set
higher than other units to ensure the BLU link master
is a unit with a BNC connection. London Architect will
warn of errors in priority settings before going online.</span>
In this case it is recommended that the CobraNet or AVB
network should not be used since CobraNet / AVB audio
will be compromised as it is synchronising from a different
clock source. The DANTE network can be used as the DANTE
card will sync from an external clock.</p>
<p>Mastership is negotiated between all the devices on
the ring, and a change to the ring will trigger the negotiation
to be started. There are various rules for determining
which device on the ring becomes clock master&#160;:-</p>
<ul>
<li class="p"><p class="hcp4">If there
is only one device (BLU-800, BLU-805, BLU-806, BLU-320,
BLU-325 or BLU-326) synchronised to BNC then that
is the master.</p></li>
<li class="p"><p class="hcp4">If there
are multiple devices synchronised to BNC then they
compare mastership priorities.</p></li>
<li class="p"><p class="hcp4">If there
are multiple devices synchronised to BNC with the
same highest priority, then they use MAC address to
decide which is master.</p></li>
<li class="p"><p class="hcp4">If no devices
are set to synchronise to BNC and there is only one
device connected to CobraNet (or AVB in the case of
BLU-805 and BLU-325, or DANTE in the case of the BLU-806
and BLU-326) then that is master.</p></li>
<li class="p"><p class="hcp4">If no devices
are set to synchronise to BNC and there are multiple
devices connected to CobraNet (or AVB or DANTE), then
they compare master priorities.</p></li>
<li class="p"><p class="hcp4">If no devices
are set to synchronise to BNC and there are multiple
devices on CobraNet (or AVB or DANTE) with the same
highest priority, then they use MAC address to decide
which is master.</p></li>
<li>If no devices are set to synchronise to BNC and
no devices are connected to CobraNet (or AVB or DANTE),
then they first compare master priorities. Next, if
the priorities are the same, they compare MAC addresses.</li>
</ul>
<span class="hcp3">BLU-link LED indicators</span>
<br>&#160;
<br><span>These are found on the Blu link
ports on the back panel of the device and indicate the
following:</span>
<ul type="disc">
<li><span class="hcp3">Green LEDs &#160;</span></li>
</ul>
<p class="hcp5"><span>The green LED will
indicate a link on that particular port</span></p>
<ul type="disc">
<li><span class="hcp3">Orange LEDs</span></li>
</ul>
<p class="hcp5">Both on: The box is the master.
(No green LEDs will be on if no cables are connected).</p>
<p class="hcp5">Only one on: The box is locked
to the data coming in on that particular port</p>
<p class="hcp5">Both off: The box is locked
to CobraNet</p>
&#160;
<br>&#160;
<p><span class="hcp3">Control Panel</span></p>
<p>The default control panel is accessed by right clicking
on the device in the <a href="Main&#32;Window.html">Main Window</a>
and selecting 'Show Default Control Panel'. The default
control panels for a BLU-800 and a BLU-805 are shown below.</p>
<p><img src="800_Panel.png" alt="" border="0" class="hcp6"> &#160;&#160;&#160;&#160;&#160;&#160;<img src="AVB&#32;Files/805_DefaultPanel.bmp" alt="" border="0" class="hcp6"></p>
<p>The <a href="Device&#32;Control&#32;Panels.html">BLU-800/BLU-320/BLU-160/BLU-120/BLU-100/BLU-101/BLU-102/BLU-805/BLU-325</a>
control panels are like the control panels for the <a
href="Device&#32;Control&#32;Panels.html">BLU-80/BLU-32/BLU-16</a>
devices but with some extra features as outlined below.</p>
<ul>
<li class="p"><p class="hcp4">BLU link
V2 indicator - On if <span style="font-weight: bold;
font-style: italic;">all</span>
devices connected via BLU link have BLU link version
2. &#160;BLU link version 2 has fixed latency.</p></li>
<li class="p"><p class="hcp4">Mastership
Priority - 0 to 254 (254 is highest priority)</p></li>
<li class="p"><p class="hcp4">Sync LEDs
- One of the following LEDs will be lit to show how
this device is synchronized:-</p></li>
<li style="list-style: none; display: inline;"><ul>
<li class="p"><p class="hcp4">Master
- This device is clock master</p></li>
<li class="p"><p class="hcp4">BLU
link In - This device is receiving clock from
the BLU link 'In' connection</p></li>
<li class="p"><p class="hcp4">BLU
link Out - This device is receiving clock from
the BLU link 'Out' connection</p></li>
<li class="p"><p class="hcp4">CobraNet
- This device is receiving clock from the CobraNet
network</p></li>
<li class="p"><p class="hcp4">AVB
- This device is receiving clock from the AVB
network.</p></li>
<li class="p"><p class="hcp4">DANTE
- This device is receiving clock from the Dante
network.</p></li>
<li class="p"><p class="hcp4">BNC
- This device is receiving clock from the BNC
IN connection.</p></li>
<li class="p"><p class="hcp4">Error
- This BLU link network is connected to multiple
CobraNet/AVB networks</p></li>
<li class="p"><p class="hcp4">BNC
and Error - This device is set to sync from BNC
but no BNC clock is connected.</p></li>
</ul></li>
<li class="p"><p class="hcp4">Link In
- On if a valid ethernet link is present on the 'In'
port</p></li>
<li class="p"><p class="hcp4">Link Out
- On if a valid ethernet link is present on the 'Out'
port</p></li>
<li class="p"><p class="hcp4">Valid In
- On if valid BLU link audio is present on the 'In'
port</p></li>
<li class="p"><p class="hcp4">Valid Out
- On if valid BLU link audio is present on the 'Out'
port</p></li>
<li class="p"><p class="hcp4">Corrected
Counters - The corrected counters show the number
of <span class="hcp3">recoverable</span>
bit errors that have occurred</p></li>
<li class="p"><p class="hcp4">Error Counters
- The error counters show the number of <span class="hcp3">unrecoverable</span>
bit errors that have occurred</p></li>
<li class="p"><p class="hcp4">Threshold
- The BLU link IN and OUT ports will be disabled when
the number of errors on the error counter reaches
the value set by Threshold. &#160;A setting of 0 means
that the Threshold is OFF and the ports will not be
disabled.</p></li>
<li class="p"><p class="hcp4">Status -
Shows the status of the BLU link IN and OUT ports
as Enabled or Disabled. &#160;When the port is disabled
no BLU link audio will pass.</p></li>
<li class="p"><p class="hcp4">Reset -
resets the error counters and sets the status of the
IN and OUT ports to Enabled.</p></li>
</ul>
<div class="editsection" style="float: right; margin-left: 5px;">
<p>&#160;</p>
</div>
<p><a name="Software_Configuration" id="Software_Configuration"></a></p>
<h2>Software Configuration</h2>
<p>The BLU link devices placed in the <a href="Main&#32;Window.html">Main
Window</a> show the BLU link In and Out ports which allow
you to wire the devices together, as shown in the diagram
above. Note: It is not necessary to wire the BLU link
ports together within HiQnet London Architect in order
for BLU link to function.</p>
<p>&#160;<span class="hcp3"><br>
Editing BLU link Networks</span></p>
<p>Multiple BLU link networks can exist within a London
Architect design file. By default, each device belongs
to BLU link 1. Every BLU link device must be part of one
BLU link network. The <a href="Device&#32;Properties&#32;Pane.html">device
properties</a> show which BLU link network the device
is part of. Click on the ... icon to edit.</p>
<p><img src="BLU_link_network.jpg" alt="Image:BLU link network.jpg" title="Image:BLU link network.jpg" width="379" height="368" border="2" class="hcp1"></p>
<p>This property can be edited to add, delete, edit the
name of, and assign the device to a BLU link network.
The diagram above shows that four BLU link networks exist
in this design file, and that the device belongs to BLU
link 1 which is shown highlighted.</p>
<p>&#160;<a name="Configurin_A_Device" id="Configurin_A_Device"></a><span class="hcp3"><br>
Configuring a Device</span></p>
<p>In the <a href="MAINConfiguration_Window.htm">Configuration
Window</a> of a BLU-800 and a BLU-160, by default, there
is one BLU link Input and one BLU link Output processing
object. Initially they have no nodes on them.</p>
<p><img src="BLU_link_Input.jpg" alt="Image:BLU link Input.jpg" title="Image:BLU link Input.jpg" width="129" height="107" border="2" class="hcp1"></p>
<p>You can add and remove as many BLU link processing objects
as you wish inside a BLU-800 and BLU-160. The BLU-320
by default contains 2 BLU link Inputs and 2 BLU link Outputs
and the BLU-120, BLU-100, BLU-101 and BLU-102 by default
contain 1 BLU link Input and 1 BLU link Output. You cannot
add or delete BLU link processing objects in the BLU-320
or BLU-120.</p>
<p>Each BLU link processing object supports a maximum of
32 channels. To edit the channels on a BLU link processing
object, select the BLU link input and click on channel
assignment in the 'BLU link Channels' property of the
object. This brings up the BLU link channel dialog.</p>
<p><img src="BLU_link_Channels2.jpg" alt="Image:BLU link Channels.jpg" title="Image:BLU link Channels.jpg" width="824" height="461" border="2" class="hcp1"></p>
<p>The left pane shows all the BLU link channels in the
network (which the device is part of). The channels can
be sorted by clicking on the column headers. Channels
can also be grouped by dragging and dropping the column
headers in to the space above the column headers. The
columns in the list are:</p>
<ul>
<li class="p"><p class="hcp4">Channel
- The BLU link channel number. &#160;This column can
include the DIP switch settings for the <a href="BLU-BOB.htm">BLU-BOB</a>.
&#160;Enable the 'Show BLU-BOB DIP switch settings'
preference at the bottom of the dialog.</p></li>
<li class="p"><p class="hcp4">Name - The
signal name of the channel. This is the name of the
signal which feeds the BLU link Output processing
object for this channel.</p></li>
<li class="p"><p class="hcp4">Tx Object
- This is the name of the BLU link Output processing
object which is transmitting this channel.</p></li>
<li class="p"><p class="hcp4">Tx Device
- This is the name of the BLU-XX0 device which is
transmitting this channel.</p></li>
<li class="p"><p class="hcp4">Rx Object
- This is the name of the BLU link Input processing
object which is currently receiving this channel.</p></li>
<li>Rx Device - This is the name of the BLU-XX0 device
which is receiving this channel.</li>
</ul>
<p>The Tx and Rx columns may contain more than one entry
if multiple objects are sending/receiving the same channel.
Channels shown in bold are channels which are not being
transmitted by the current configuration. When configuring
a BLU link Output, only channels in bold can be added
to the pane on the right.</p>
<p>Show BLU-BOB DIP switch settings' - When enabled, displays
the BLU-BOB DIP switch values (1 to 6) and the channel
within that group. For example, 010001,4 is channel 140
(fourth channel in group 17).</p>
<p>The right pane shows the channels selected for that
BLU link processing object. You can use the 'Move Up'
and 'Move Down' buttons to change the order in which the
channels appear on the object. To add a channel to the
BLU link processing object, select one or more channels
in the left pane, and press the 'Add -&gt;' button. To
remove channels from the processing object, select one
or more channels in the right pane, and press the 'Remove'
button.</p>
<p>Channels which have been partly or fully configured
are in one of three states.</p>
<ul>
<li class="p"><p class="hcp4">Valid. These
channels are shown highlighted in blue. The channels
have valid transmitters and receivers.</p></li>
<li>Warning. These channels are shown highlighted in
amber. There are three scenarios where a channel shows
a warning:</li>
</ul>
<p>1.No receiver. The channel is transmitting but is not
being received by any device.</p>
<p>2.No transmitter. The channel is being received, but
no device is sending the channel.</p>
<p>3.Possible clash. This happens when multiple configurations
of different devices are transmitting on the same channel.
Though it is possible to never have two configs active
at the same time transmitting on the same channel, the
possibility exists of two devices transmitting on the
same channel. It is up to you to configure presets correctly
to avoid multiple transmitters on the same channel.</p>
<ul>
<li class="p"><p>Error. These channels are shown highlighted
in pink. An error is shown where there is more than
one device transmitting on the same BLU link channel.</p></li>
</ul>
<p>You can hover your cursor over a channel to see a tool
tip describing the state of the channel.</p>
<p>All devices on the same BLU link network must be running
at the same sample rate, all at 48kHz, or all at 96kHz.
If any devices are running at different sample rates,
you will be warned about this when entering the channel
assignment dialog. If any channels are in error (highlighted
pink), or have different sample rates, then you will be
prevented from going online to the devices. The BLU link
channel assignments will have to be corrected.</p>
<div class="editsection" style="float: right; margin-left: 5px;">
<p>&#160;</p>
</div>
<p><a name="BLU_link_Specification" id="BLU_link_Specification"></a></p>
<h2>BLU link Specification</h2>
<ul>
<li class="p"><p class="hcp4">Based on
Gigabit Ethernet technology</p></li>
<li class="p"><p class="hcp4">100m over
CAT5e cable.</p></li>
<li class="p"><p class="hcp4">&gt;100m
using fibre converters.</p></li>
<li class="p"><p class="hcp4">256 Channels
at 48KHz (<a href="BLU-100.htm">BLU-100</a>, BLU-101
and BLU-102 are restricted to 48 channels at 48kHz)</p></li>
<li class="p"><p class="hcp4">128 Channels
at 96KHz (<a href="BLU-100.htm">BLU-100</a>, BLU-101
and BLU-102 do not operate at 96kHz)</p></li>
<li class="p"><p class="hcp4">Bus-like
architecture. Audio transmitted on a channel is available
at all other devices on the network automatically.</p></li>
<li class="p"><p class="hcp4">Wired in
a loop for redundancy</p></li>
<li>Recovers from a single cable break</li>
</ul>
<p><!-- Saved in parser cache with key bugs:pcache:idhash:2873-0!1!0!0!!en!2 and timestamp 20080311165015 --></p>
</div>
</div>
</div>
</div>
<p class="hcp4">&#160;</p>
</body>
</html>