What is WNIP Event Scheduler?

This program works in conjunction with Blade logic and automation to allow for automated and timed control of Wheatnet-IP functionality, up to and including remote machine control, on air lights, tallies, transmitter remote control, and Salvos. You can also connect or disconnect signals, send commands for turning channels on or off and basically any other Wheatnet-IP function at any programmed time.

Often called the "Event Scheduler," it works with automation and satellite control to trigger GPI closures, or programmed salvos and events by hour, day, or week.

What do I need to know?

The Scheduler uses Events and Schedules to facilitate your automation needs. Using events you can define connections, disconnections, salvos, and ACI. Create a schedule around when you would like to execute specific events or combinations of events. Load your signals into the scheduler and dial the operation events and as the old infomercial would say, just set it and forget it.

In Windows 10 and 11, you must run this program as Administrator in order for any events to be saved. Otherwise, Windows will block permissions that are needed for the program to function. We recommend right-clicking on the program shortcut icon and setting the program to always be Run as Administrator so you don't forget.

Q. I need to move my Scheduler to a new computer. Where are the files I need to copy over?

A. The default location for event and signal files is:
C:\Users\\AppData\Roaming\Wheatstone\WheatNetIPScheduler\
Signal files in this location have the file extension .sigtab, while event files use .evt as the file extension.
There is also a WheatNetIPScheduler.ini file in that same location. It has the usual .ini stuff, including directory path information which can be useful if they were using file locations other than the defaults.

Q. When I load an Event file there are lots of special characters instead of source and destination names. I am running Scheduler v 2.1.2 on a Win 7 PC.

A. This appears to be a bug in v 2.1.2, so download the previous version v 2.1.0 (here's a link to the 2.1.0 installer: https://wheatstone.box.com/s/zw8c95murksunvv5dvx56yqvhqtcmybm) and install it over v 2.1.2. That should resolve the issue, however, Event files saved in v 2.1.2 do not load properly in v 2.1.0, so you'll need to recreate your Event files.

Q. I want to control a Comrex Access via IP Scheduler. I have an output wired to the Access unit and have setup the connection I want. When I test the Logic Output on the blade it works. But I can’t figure out how to configure the Logic in Navigator so I can Schedule a Source – Destination Connection.

A. If you're making and breaking a connection to implement logic, as indicated below, then you have to have what I call an "always on" logic trigger to setup one one signal and then the receiving logic set up on a second signal.

I like to program the "always on" as a source. In that way I can use it for more than one logic triggering if necessary. In Navigator go to the Blade you want to set up the "always on" logic on. This will sometimes be an obvious choice, sometimes not, but if you have more than one Blade it is a choice you have to make. On the Sources tab, click the Add… button to bring up the add signal dialog. Name the signal AlwaysOn (name is not critical but this is the name I like to use) and define it as a logic only signal. Go to the signal definition LIO Info tab and add an LIO. Select an unused SLIO in the Wire column and highlight it. Choose Input for Direction and User 1 as the Function. Here the function is not critical but I like to use one of the User xx functions to let me know it's not a predefined function I'm working with. Click Apply, then Close, then Finish.

On the Blade with the logic port you are using to command the Comrex Access, create a logic only destination. Give it a memorable name, such as Access, and set up an LIO using the port you have wired to the Access. Make it's direction: Output and use the same function name used on the AlwaysOn source (for example: User 1). Exit the dialog with Apply > Close > Finish.

At this point if you make a crosspoint between AlwaysON and Access it should activate the Access logic. Now add a couple of events to the scheduler to control the crosspoint. If you need a constant closure to the Access you would schedule an event to make the connection when the closure should start and another event to break the connection when the closure should stop. If the Access logic needs to be momentary then you would schedule an event to make the connection at the appropriate time and another to break the connection a second later.