90
Different Ways to Use the Script Commands
There are two methods of using the script we just created. One is to use the scripts as Trigger Scripts,
responding to contact closures and opens as previously discussed. The other involves integrating the scripts into
the Omnia-3’s daypart table. Because the processor is flexible, it allows one to use the same script for both
options.
Initiating Trigger Scripts via the Interface Connector
As we mentioned, trigger scripts give the user the ability to tie a series of commands to a simple high/low logic
change occurring on a pin of the 9-pin D-sub Interface connector on the unit’s rear panel.
The Pinout of the Omnia-3 rear-panel DB-9 Interface connector is as follows:
PIN 1 activates Trigger Script 1
PIN 6 activates Trigger Script 2
PIN 2 activates Trigger Script 3
PIN 7 activates Trigger Script 4
PIN 3 activates Trigger Script 8
PIN 8 activates Trigger Script 7
PIN 4 activates Trigger Script 6
PIN 9 activates Trigger Script 5
PIN
5
is
connected
to
ground
Each pin that is to be used must first be programmed with a trigger script for the desired Go High and Go Low
logic. To execute the Go Low script, a trigger input pin is connected via a sustained contact closure to pin 5
(ground). To execute a Go High script, the ground is removed from that pin. Each of the trigger pins (1, 2, 3, 4,
6, 7, 8, 9) is thus connected through a switch or relay to the Omnia-3’s ground on Pin 5.
Let's review what we created for the example we showed you under “Using the Script Editor”. Whenever pin 1
is held low (the contact or switch is in a closed state), the Omnia-3fm Turbo will switch to and stay in mono
mode (no Pilot and only the left input channel is used). When the pin 1 contact is subsequently opened, the
Omnia-3fm Turbo will switch back to and stay in stereo operation (pilot on and both left and right input
channels being used) as long as the contact is open.
“One Way Script” Functions
You may also create scripting functions that do NOT return to another value when the remote contacts are
opened. To do this, you use the Go LOW script only, and do not put any entries into the Go HIGH script.
Two possible uses for this very useful “Go LOW Only” Trigger Script trick are periodically setting the Omnia's
system time to an external standard, and remote re-booting of the Omnia.
To use the Omnia's command line “Time” function to reset the Omnia's System Clock to midnight based on an
external contact closure (such as from an automation system or other time reference), the Trigger Script script
syntax would be:
Time 00 00 00 Sets the Omnia time to midnight. Note that colons are not used as delimiters in this entry!
Although time is displayed by the front panel display and its controller, it is actually being kept by the Omnia
motherboard. When resetting the System Time using trigger scripts, the change takes effect immediately at the
motherboard. Because the front panel 'fetches' time synchronization from the motherboard every few seconds,
the front panel's confirmation of the time change may lag by a few seconds but the two will agree with each
other when updating takes place.
Another possible use of the one way Trigger Script script capability (although not strongly recommended) is the
remote 're-booting' of the Omnia. In that special case, there would be no Go High script entry. The Go Low
script for that function would simply read:
warmboot
