13
associated with a microphone source. In a discrete hardwired system these signals would typically
come from a button on the announcer’s desk then be fed into an input logic line on an LIO card in
your audio router.
Custom scripts for your GP-16P can drive input LIOs using the
lio_set()
function.
Output LIOs correspond to Logic I/O values which are fed OUT of the router matrix. Typical
types of output LIOs would be machine start, machine stop, and ON and OFF tally logic signals
to drive remote panel switch LED’s associated with a microphone source. In a discrete hardwired
system these signals would
typically come from an output logic line on an LIO card in your
audio router then feed to a logic line on your automation system or to a switch’s LED.
In your GP-16P you can read output LIOs using the lio_get() function.
The first input LIO corresponds to LIO id "1" in the lio_set() function, the second to LIO id "2",
etc.. The first output LIO corresponds to LIO id "1" in the lio_get() function, the second to LIO id
"2", etc..
Note: The controls will be disabled if you are not connected to the GP-16P device. In this
situation you are looking at the device properties which are stored on your PC's hard drive. These
properties may not truly reflect the properties of your device, if the device has been more recently
configured from another PC.
4.5 - Design Philosophy
During the design of the GP-16P we went back and forth on the merits of making the LIO
definitions a device property and using property table indexes in the script function calls vs.
specifying the LIO definitions directly in the script functions. We felt that the first approach
would provide greater value in that if your installation contains several GP-16P panels with
similar functionality, you can use one script for all of the GP-16P button panels and just modify
the device properties of each GP-16P.
Note: When you specify input LIOs for the GP-16P, you will typically select a logic line which is
also configured as an input LIO in the XP GUI program. You can point one of the GP-16P input
LIOs at a logic line which is configured as an output LIO in the XP GUI, and the GP-16P will
happily drive it. The negative side of doing this is, there might also be another GP-16P or a
physical logic card driving the same output LIO. The router has very extensive rules to arbitrate
who is driving output logic. These rules are basically bypassed, if you adopt the mixed direction
approach. It's much safer to define a new signal which has an input logic line, drive the new
signal's input logic line with the GP-16P, then connect the new signal to the signal which has the
output logic and let the router apply it's rules to the signal routing.
Note: When you specify output LIOs for the GP-16P, you will typically select a logic line which
is also configured as an output LIO in the XP GUI program. You can point one of the GP-16P
output LIOs at a logic line which is configured as an input LIO in the XP GUI, and the GP-16P
will happily read it.