151 lines
6.6 KiB
HTML
151 lines
6.6 KiB
HTML
|
|
||
|
|
<!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>Devices</title>
|
||
|
|
<link rel="StyleSheet" href="HtmlHelp.css" type="text/css">
|
||
|
|
|
||
|
|
<style title="hcp" type="text/css">
|
||
|
|
<!--
|
||
|
|
li.hcp1 { list-style:none;
|
||
|
|
display:inline; }
|
||
|
|
span.hcp2 { font-weight:bold; }
|
||
|
|
img.hcp3 { border-width:2px;
|
||
|
|
border-style:solid;
|
||
|
|
margin-top:0px;
|
||
|
|
margin-bottom:0px;
|
||
|
|
margin-left:0px;
|
||
|
|
margin-right:0px; }
|
||
|
|
p.hcp4 { font-weight:bold; }
|
||
|
|
img.hcp5 { border:none; }
|
||
|
|
-->
|
||
|
|
</style>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body class="ns-0 ltr">
|
||
|
|
<div id="globalWrapper">
|
||
|
|
<div id="column-content">
|
||
|
|
<div id="content">
|
||
|
|
<h1 class="firstHeading">Devices</h1>
|
||
|
|
<div id="bodyContent">
|
||
|
|
<p><a name="Device_Names" id="Device_Names"></a></p>
|
||
|
|
<h2>Device Names</h2>
|
||
|
|
<p>Each device in your system must have a unique name:
|
||
|
|
this enables the Soundweb network to distinguish one device
|
||
|
|
from another. When you create a device, London Architect
|
||
|
|
will allocate a default name for it (the first device
|
||
|
|
defaults to"U1", the second to "U2"
|
||
|
|
and so on. It is a good idea to replace these names with
|
||
|
|
names of your own, such as "Conference room 1"
|
||
|
|
or "Main paging mixer", in order to help clarify
|
||
|
|
your design. These names will also appear in the system
|
||
|
|
rack in the Configuration window making selection of the
|
||
|
|
correct "zone" processor in multi device systems
|
||
|
|
much easier.</p>
|
||
|
|
<p> <br>
|
||
|
|
To change the name of a device:</p>
|
||
|
|
<p>Select the device and in the Properties window type
|
||
|
|
a new name in the "Object Name" box. Make sure
|
||
|
|
that the "Show Object Name" is set as "Yes".</p>
|
||
|
|
<div class="editsection" style="float: right; margin-left: 5px;">
|
||
|
|
<p> </p>
|
||
|
|
</div>
|
||
|
|
<p><a name="Deleting_a_Device" id="Deleting_a_Device"></a></p>
|
||
|
|
<h2>Deleting a Device</h2>
|
||
|
|
<p>To delete a device:</p>
|
||
|
|
<ol>
|
||
|
|
<li class="hcp1"><ol>
|
||
|
|
<li class="hcp1"><ul>
|
||
|
|
<li class="p"><p>Select it and press <span class="hcp2">Del/Backspace</span></p></li>
|
||
|
|
</ul></li>
|
||
|
|
</ol></li>
|
||
|
|
</ol>
|
||
|
|
<p>Or</p>
|
||
|
|
<ol>
|
||
|
|
<li class="hcp1"><ol>
|
||
|
|
<li class="hcp1"><ul>
|
||
|
|
<li class="p"><p>Select <span class="hcp2">Delete</span>
|
||
|
|
from the device's right-click menu.</p></li>
|
||
|
|
</ul></li>
|
||
|
|
</ol></li>
|
||
|
|
</ol>
|
||
|
|
<div class="editsection" style="float: right; margin-left: 5px;">
|
||
|
|
<p> </p>
|
||
|
|
</div>
|
||
|
|
<p><a name="Representation_of_Device_interface_ports" id="Representation_of_Device_interface_ports"></a></p>
|
||
|
|
<h2>Representation of Device interface ports</h2>
|
||
|
|
<p>In each Configuration window there are blocks that represent
|
||
|
|
the input and output capabilities of the particular processor
|
||
|
|
selected. Input blocks are displayed on the left of the
|
||
|
|
design space and output blocks on the right by default.
|
||
|
|
These blocks can be moved around to suit the design but
|
||
|
|
they cannot be deleted as they represent physical hardware.
|
||
|
|
If an input block is connected to certain source objects,
|
||
|
|
icons will appear in the block, e.g. CD player or mic,
|
||
|
|
the names of devices will follow through onto these blocks
|
||
|
|
too. Double clicking the blocks will open their default
|
||
|
|
control panels.</p>
|
||
|
|
<p>There will be one block each for the fitted cards (analogue,
|
||
|
|
digital, AEC or Telephone Hybrid), one block represents
|
||
|
|
4 ports (inputs or outputs), i.e. four blocks in total
|
||
|
|
for the four possible card installs.</p>
|
||
|
|
<dl>
|
||
|
|
<dt class="mvd-P" style="font-weight: bold;">Analogue
|
||
|
|
Blocks</dt>
|
||
|
|
</dl>
|
||
|
|
<p><img src="Analogueblocks.jpg" alt="Image:analogueblocks.png" title="Image:analogueblocks.png" width="141" height="114" border="2" class="hcp3"></p>
|
||
|
|
<p>These are coloured gold.  Clicking on the arrows
|
||
|
|
in these blocks will return the user to the design space
|
||
|
|
highlighting the node and/or object that is connected
|
||
|
|
to this port - useful for tracing the signal path from
|
||
|
|
processor to source input or output destination.</p>
|
||
|
|
<p><img src="Digital Input Card.jpg" alt="" style="border-width: 2px;" width="126" height="102" border="0"></p>
|
||
|
|
<p>These are coloured blue.</p>
|
||
|
|
<p class="hcp4">AEC Blocks</p>
|
||
|
|
<p><img src="AEC Input Card.jpg" alt="" width="276" height="195" border="0" class="hcp5"></p>
|
||
|
|
<p style="font-weight: normal;">These are coloured green.
|
||
|
|
 Since the card can be used as either an AEC card
|
||
|
|
or a straight through analogue card, any device connected
|
||
|
|
to an input will be represented on both the AEC input
|
||
|
|
and on the analogue input.  The internal <span class="hcp2">Input
|
||
|
|
Reference Return</span> is also represented.  Clicking
|
||
|
|
on the arrows in the block has the same effect as for
|
||
|
|
the analogue input and output cards.</p>
|
||
|
|
<p class="hcp4">Telephone Hybrid Cards</p>
|
||
|
|
<p><img src="Hybrid Card.jpg" alt="" width="281" height="96" border="0" class="hcp5"></p>
|
||
|
|
<p class="hcp4"><span style="font-weight: normal;">The
|
||
|
|
orange coloured telephone hybrid blocks show the 2 analogue
|
||
|
|
inputs and the Hybrid input and Output</span></p>
|
||
|
|
<p class="hcp4">CobraNet Blocks</p>
|
||
|
|
<p><img src="Cobranetblocks.jpg" alt="Image:cobranetblocks.png" title="Image:cobranetblocks.png" width="140" height="122" border="2" class="hcp3"></p>
|
||
|
|
<p>For devices with CobraNet there will be 8 CobraNet blocks
|
||
|
|
shown (4 input, 4 output), these represent the 'bundles'
|
||
|
|
and route 8 channels each. These are coloured silver by
|
||
|
|
default but change colour when activated to transmit or
|
||
|
|
receive in either Unicast (green) or Multicast mode (purple).
|
||
|
|
Connection arrows are not shown until CobraNet is configured
|
||
|
|
in the Properties.</p>
|
||
|
|
<dl>
|
||
|
|
<dt class="mvd-P" style="font-weight: bold;">BLU link
|
||
|
|
Blocks</dt>
|
||
|
|
</dl>
|
||
|
|
<p><img src="BLU_link_Input.jpg" alt="Image:London Bus Input.jpg " title="Image:London Bus Input.jpg " width="129" height="107" border="2" class="hcp3"></p>
|
||
|
|
<p>For devices with BLU link, each configuration will have
|
||
|
|
a default pair of BLU Link processing objects. For devices
|
||
|
|
which have configurable DSP, more BLU Link objects can
|
||
|
|
be added, in the same way processing objects are added.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<p style="margin-bottom: 0;"><!-- Served by hproukweb01.hprouk.ad.harman.com in 3.17 secs. --></p>
|
||
|
|
</body>
|
||
|
|
</html>
|