128 lines
5.5 KiB
HTML
128 lines
5.5 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>BLU-8 Hardware</title>
|
||
|
<link rel="StyleSheet" href="HtmlHelp.css" type="text/css">
|
||
|
<style title="hcp" type="text/css">
|
||
|
<!--
|
||
|
p.hcp1 { margin-bottom:0; }
|
||
|
span.hcp2 { font-weight:bold; }
|
||
|
-->
|
||
|
</style>
|
||
|
</head>
|
||
|
|
||
|
<body class="ns-0 ltr">
|
||
|
<div id="globalWrapper">
|
||
|
<div id="column-content">
|
||
|
<div id="content">
|
||
|
<h1 class="firstHeading">BLU-8 Programmable Controller</h1>
|
||
|
<div id="bodyContent">
|
||
|
<p id="siteSub"><a name="What_is_the_BLU-8.3F" id="What_is_the_BLU-8.3F"></a></p>
|
||
|
<h2>What is the BLU-8?</h2>
|
||
|
<p>The BLU-8 sits in the product range between the <a href="BLU-3-BLU-6.html">BLU-3</a>
|
||
|
and <a href="BLU-3-BLU-6.html">BLU-6</a>, both simple
|
||
|
wall-mounted controllers that connect to the control ports
|
||
|
of a <a href="BLU-80.html" title="BLU-80">BLU-80</a> /
|
||
|
<a href="BLU-32.html">BLU-32</a> / <a href="BLU-16-BLU-16A.html">BLU-16</a>,
|
||
|
and the <a href="MAINBLU10_Programmable_Controller.htm">BLU-10</a>
|
||
|
which is a networked touchscreen wall controller.</p>
|
||
|
<p> </p>
|
||
|
<div class="editsection" style="float: right; margin-left: 5px;">
|
||
|
<p> </p>
|
||
|
</div>
|
||
|
<p><a name="Features_of_a_BLU-8" id="Features_of_a_BLU-8"></a></p>
|
||
|
<h2>Features of a BLU-8</h2>
|
||
|
<p><img src="MAINBLU8_Hardware_files/Blu8_hardware.jpg" alt="Image:blu8_hardware.jpg" longdesc="/wiki/index.php?title=Image:Blu8_hardware.jpg" title="Image:blu8_hardware.jpg" style="border-width: 2px;
|
||
|
border-style: solid; margin-top: 0px; margin-bottom: 0px;
|
||
|
margin-left: 0px; margin-right: 0px;" width="656" height="476" border="2"></p>
|
||
|
<p> </p>
|
||
|
<ul>
|
||
|
<li class="p"><p class="hcp1">Two rotary
|
||
|
encoders</p></li>
|
||
|
<li class="p"><p class="hcp1">One 9-segment
|
||
|
bargraph meter</p></li>
|
||
|
<li>Five pushbuttons</li>
|
||
|
</ul>
|
||
|
<p>This is supported by the following aspects</p>
|
||
|
<ul>
|
||
|
<li class="p"><p class="hcp1">IEEE 802.3af
|
||
|
Power over Ethernet</p></li>
|
||
|
<li class="p"><p class="hcp1">12-48V DC
|
||
|
power</p></li>
|
||
|
<li>100 Mbit Ethernet interface</li>
|
||
|
</ul>
|
||
|
<p> </p>
|
||
|
<div class="editsection" style="float: right; margin-left: 5px;">
|
||
|
<p> </p>
|
||
|
</div>
|
||
|
<p><a name="BLU-8_Network_operation" id="BLU-8_Network_operation"></a></p>
|
||
|
<h2>BLU-8 Network operation</h2>
|
||
|
<p>The BLU-8 is <span class="hcp2">not</span>
|
||
|
designed to work on a network with CobraNet traffic. BSS
|
||
|
recommends that CobraNet traffic is transferred on a separate
|
||
|
network to the HiQNet control network.</p>
|
||
|
<p>The BLU-8 is capable of handling the following simultaneous
|
||
|
communications :</p>
|
||
|
<ul>
|
||
|
<li class="p"><p class="hcp1">Communication
|
||
|
with a maximum of 8 HiQNet devices from all the pages
|
||
|
configured on the BLU-8, PLUS</p></li>
|
||
|
<li>Communication with one programming device (London
|
||
|
Architect).</li>
|
||
|
</ul>
|
||
|
<p> <br>
|
||
|
For optimum performance, the BLU-8 should be used on a
|
||
|
dedicated Soundweb London control network with only one
|
||
|
instance of HiQnet London Architect present. In this condition
|
||
|
the BLU-8 can be used to control the parameters of up
|
||
|
to a maximum of 8 other HiQNet devices. It should be noted
|
||
|
that as the network on which the BLU-8 resides becomes
|
||
|
large, the responsiveness of the BLU-8 can be adversely
|
||
|
affected by the volume of network traffic and as such,
|
||
|
controls may become slower to respond.</p>
|
||
|
<p>If responsiveness is an issue then please follow the
|
||
|
recommendations below to improve the situation :</p>
|
||
|
<p> <span class="hcp2"><br>
|
||
|
RECOMMENDATIONS :-</span></p>
|
||
|
<ul>
|
||
|
<li class="p"><p>No CobraNet traffic on the part of
|
||
|
the network with the BLU-8. (CobraNet traffic swamping
|
||
|
the network WILL affect the responsiveness of the
|
||
|
BLU-8).</p></li>
|
||
|
<li class="p"><p>Use switches rather than hubs in your
|
||
|
network implementation.</p></li>
|
||
|
<li class="p"><p>One London Architect PC active on
|
||
|
the network at a time.</p></li>
|
||
|
<li class="p"><p class="hcp1">Minimise
|
||
|
unnecessary 'broadcast' traffic reaching the BLU-8,
|
||
|
the following two steps are aimed at reducing this
|
||
|
traffic :</p></li>
|
||
|
<li style="list-style: none; display: inline;"><ul>
|
||
|
<li class="p"><p class="hcp1">Ensure
|
||
|
that all the HiQNet devices on the network are
|
||
|
included in the London Architect design. If they
|
||
|
are not part of the design then they can be powered
|
||
|
off to reduce unnecessary traffic on the network.</p></li>
|
||
|
<li>If there are many devices on the network which
|
||
|
the BLU-8 does not need to communicate with, then
|
||
|
consider placing these devices on a different
|
||
|
sub-net to the BLU-8 (on the other side of a network
|
||
|
router). The <a href="Using HiQnet London Architect Across a VPN.html">Static
|
||
|
Routes</a> feature in London Architect can be
|
||
|
used to ensure that the BLU-8 is discovered by
|
||
|
London Architect even if the London Architect
|
||
|
PC is on a different sub-net to the BLU-8.</li>
|
||
|
</ul></li>
|
||
|
</ul>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<p class="hcp1"> </p>
|
||
|
</body>
|
||
|
</html>
|