page A – 65
WheatNet-IP
/ Mar 2014
A P P E N D I C E S
WheatNet-IP
/ Mar 2015
WheatNet-IP Scheduler
Introduction To WheatNet-IP Scheduler
The WheatNet‑IP Scheduler program is designed to fire Events in a WheatNet ‑IP
system at pre-arranged times.
In order to integrate the software into a WheatNet-IP system, you will need to run
it on a computer having a unique IP address on the same subnet as the WheatNet‑IP
system (typically 192.168.87.xxx). You will also need to know the IP address of at least
one Blade in the system, since the software will need to directly address a Blade.
What are events? Simply put, they are actions that will occur within a WheatNet-IP
system. The software supports Connect, Disconnect, Salvo, and ACI (Automation Control
Interface) events. Events are configured within the software, and are also fired by the
software. Events act on system
signals
(Connect and Disconnect events) and
salvos
(Salvo events). ACI events direct automation‑specific commands to various devices in
the WheatNet‑IP system. Events may be saved to a file, and the saved event files may
be loaded into the program. This allows you to create a schedule on one computer, then
load and run the schedule on a different computer.
Since a scheduler by its very nature performs tasks at specific times, it is important
to note that the WheatNet-IP Scheduler depends on the clock on the PC that the program
is running on to know precisely when to fire an event. Thus the PC clock needs to be
set to the correct time and date to match its location. Otherwise, events will not fire as
expected.
Events And Signals
As stated above, the software utilizes various event types, signals, salvo definitions,
and commands to compose the events necessary to effect the desired actions within the
system at the appropriate times. These items will be discussed briefly here.
As previously stated, an event is an occurrence within the system that can be caused to
take place at a specified time according to a schedule. Four types of events are supported
in the software.
Connect Event
A
Connect
event is one that causes a particular source (input) in the system to feed
a particular destination (output) in the system at the scheduled time. Both sources and
destinations can be specified by signal Name and Location (which are assigned by the
system administrator via the WheatNet‑IP Navigator program) or signal ID (which is
automatically assigned within the WheatNet‑IP system based on the rules the system
imposes to define signals).
It should be noted here that only one source can be connected to a given destination
at a time. For this reason, an event that causes a source to be connected to a destination
which already has a different source connected will cause the original source to be
disconnected prior to making the new connection.
Also worthy of note is that connections in the system may be locked, and that the
Scheduler software will not override signal locks.