Wheatstone Corporation WheatNet-IP BLADE3, Техническое руководство

Страница: 318 / 366

page A – 89
WheatNet-IP BLADE 3 / Jan 2016
A P P E N D I C E S
If you want to undefine a device, simply click the Delete # X button that corresponds
to the device you no longer need.
You can commit your changes at any time by clicking Apply ; the form will remain open.
If you have made some changes but want to cancel your changes, you can click Cancel to
revert any uncommitted changes back to what they were. Cancel will not affect changes
that have been committed.
When you are done defining devices click the Close button to commit your changes
and close the form. You will be prompted to restart the program before the new device
data will actually be used. Click Yes or No as desired.
Signals
Signals are an integral part of Connect and Disconnect events. Although you can schedule
one of these events without specifying signals, the event will do nothing when fired.
Signals are operated upon within the WheatNet-IP system according to their Signal ID,
and you can, in fact, specify signals by referring to the ID. However, the signal IDs are
somewhat cryptic, and signals can be given names that we humans will find much more
meaningful.
Further, it makes sense from a human standpoint to have items with similar functions
named with similar names. For an example relative to the project at hand, we may find
it convenient to have a signal named “Fred” feeding an input on a BLADE 3 located in
Studio 1, and a signal of the same name feeding a BLADE 3 in Studio 2, because Fred
sometimes works from one studio and sometimes from the other. And so we allow the
name to be extended by appending a Location to the name. In this example we would have
Fred – Studio 1 and Fred – Studio 2. In this way we can easily distinguish the two signals
even when they share a common name.
Signal names and locations are generally configured with the WheatNet-IP Navigator
GUI. We just use the same names here, getting them from the fetched signal set.
If your signal names (and locations) have come from a connected BLADE 3, the
signals that that BLADE 3 is aware of will be the same signals that you will have access
to when creating and editing events. As an alternative you can load a set of signals that
was previously saved to file, and the signals in that file will be the ones you have access to
when working with events. If you are not connected to a BLADE 3 and choose to cancel
the loading of signals from a file you will not have any signals to work with. Sure, you
can still create and edit events, but the results will be pretty meaningless.
Request Signals From Connected BLADE 3
To request signals from the connected BLADE 3 while at the main screen, select
File>Request Config from the menu. Or, if you are on the Event Properties screen (see
below “Create Events” section) you can click the Request Config button. Either method
will start the signal fetch process already described.
Load Signals From File
If you have previously save a signal set, or if you want to view the sample signal set
that is provided for you during product installation, select Signals>Open Signal File...
from the main menu. This will open a Windows file open dialog, which will point to the
default location for event and signal files the first time the program is run, or the location
loaded from or saved to the last time the program was run. Navigate to the desired location,
select the file, and click OK .