104 lines
5.3 KiB
HTML
104 lines
5.3 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>The Logic System</title>
|
||
|
|
<link rel="StyleSheet" href="HtmlHelp.css" type="text/css">
|
||
|
|
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body class="ns-0 ltr">
|
||
|
|
<div id="globalWrapper">
|
||
|
|
<div id="column-content">
|
||
|
|
<div id="content">
|
||
|
|
<h1 class="firstHeading">The Logic System</h1>
|
||
|
|
<div id="bodyContent">
|
||
|
|
<p id="siteSub">Each of the DSP configurable Soundweb London
|
||
|
|
devices also contains a configurable logic system. You
|
||
|
|
can toggle between the audio configuration and logic configuration
|
||
|
|
using the audio and logic buttons in the <a href="MAINConfiguration_Window.htm">Configuration
|
||
|
|
Window</a>.</p>
|
||
|
|
<p>The Soundweb London processor contains several processing
|
||
|
|
chips including a CPU (Central Processing Unit) and 2
|
||
|
|
or more DSPs (Digital Signal Processors). The CPU handles
|
||
|
|
all communication (Ethernet, serial etc.), parameter linking,
|
||
|
|
display, led's etc. The DSPs are for audio signal processing.
|
||
|
|
The logic runs on the Soundweb London CPU, not the DSP.
|
||
|
|
This means it will not use any DSP resources. However,
|
||
|
|
it will use CPU resources which will be explained in more
|
||
|
|
detail below.</p>
|
||
|
|
<p><a href="Logic Objects.html">Logic Objects</a> are placed
|
||
|
|
and wired up in the same way as in the audio configuration.
|
||
|
|
Many of the logic objects have properties which allow
|
||
|
|
you to add and/or remove input or output ports. Each logic
|
||
|
|
object is quite basic, but when added together they can
|
||
|
|
perform very complex operations, e.g. a priority paging
|
||
|
|
system. Each logic object has a run order which can be
|
||
|
|
displayed by enabling the option in the <a href="Logic Menu.html">Logic
|
||
|
|
Menu</a>. The run order is the order in which the logic
|
||
|
|
object will be processed. Attention must be paid to the
|
||
|
|
run order if logic signals are looped back to previous
|
||
|
|
logic objects (like a feedback loop) since the objects
|
||
|
|
may then have a different run order to what you might
|
||
|
|
expect.</p>
|
||
|
|
<p>Many logic objects have default control panels and parameters
|
||
|
|
which can be controlled. These parameters allow you to
|
||
|
|
interact with the logic system and also facilitate the
|
||
|
|
logic system to interact with the audio system. You can
|
||
|
|
for example <a href="Links.html">link</a> a logic end
|
||
|
|
to a mute. The logic allows a quick method of creating
|
||
|
|
these links. For example, you can drag and drop the mute
|
||
|
|
control from a panel directly on to the logic end object
|
||
|
|
in the logic configuration window. This will automatically
|
||
|
|
create an exact link between the mute parameter and the
|
||
|
|
logic end parameter. The link will appear in the <a href="MAINDesign_tree.htm">Design
|
||
|
|
Tree</a> under 'Logic Links'.</p>
|
||
|
|
<div class="editsection" style="float: right; margin-left: 5px;">
|
||
|
|
<p> </p>
|
||
|
|
</div>
|
||
|
|
<p><a name="Resource_Meter" id="Resource_Meter"></a></p>
|
||
|
|
<h2>Resource Meter</h2>
|
||
|
|
<p>At the top of the logic configuration window is a <span
|
||
|
|
style="font-weight: bold;">logic resource meter</span>
|
||
|
|
which gives an indication of resource usage. Each logic
|
||
|
|
object has an <span style="font-style: italic;">approximate</span>
|
||
|
|
host processor usage. It is approximate because it is
|
||
|
|
impossible to calculate an exact figure. The resource
|
||
|
|
meter is the total of these approximate values. 100% logic
|
||
|
|
resource usage equates to approximately 50% host CPU usage.
|
||
|
|
However, it is unlikely that you will see this amount
|
||
|
|
of CPU usage being used. This is because there are optimisations
|
||
|
|
in the logic which means that most logic objects will
|
||
|
|
not be processed if no change is made to the inputs, in
|
||
|
|
which case the logic object will not consume any host
|
||
|
|
CPU usage. Other logic objects such as the <a href="MAINCalendar.htm">Calendar</a>
|
||
|
|
object are processed every logic tick (100ms) and so can
|
||
|
|
consume lots of host CPU usage. The logic resource meter
|
||
|
|
therefore gives a worst case figure, based on every logic
|
||
|
|
object being processed every tick. However, you should
|
||
|
|
still not rely on this figure when determining if the
|
||
|
|
logic will run successfully in the device. This is because
|
||
|
|
the host processor which runs the logic also performs
|
||
|
|
many other tasks which cannot be estimated by London Architect.
|
||
|
|
Examples of items which affect host CPU usage are:- number
|
||
|
|
of devices on the network, number of open control panels
|
||
|
|
in London Architect, and cross-device linking.</p>
|
||
|
|
<p>The only way to determine if the device will successfully
|
||
|
|
run the logic system is to go online with your design
|
||
|
|
file and observe the CPU meter in the <a href="Device Control Panels.html">device
|
||
|
|
default control panel</a>. This will be required for every
|
||
|
|
device running logic. If the figure is above 90% then
|
||
|
|
there may be occasions where the logic will run slower
|
||
|
|
than every 100ms, and meters will appear to slow down.
|
||
|
|
In extreme cases, controls will grey out on control panels.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<p style="margin-bottom: 0;"> </p>
|
||
|
|
</body>
|
||
|
|
</html>
|