G P - 8 P / G P - 1 6 P S O F T W A R E
page 2 – 9
GPC-3 / Jan 2006
LIO Settings
We use the LIO settings to map a button or its LED to a logic port in
the system. These logic ports may be real (as are the one that we deal with
in this section) or virtual (as are the ones used in the example in the help
file).
First we need to use the XPoint GUI application to set up the logic port
that we will be using to light the button 6 LED. Let’s use the first green box
in the Source area of the XPoint program to set up a logic input to monitor
an external event, such as a switch or other closure. Right-click on the box
and select Modify Signal Definition from the popup menu. On the Signal
Definitions form you will see that the signal Id is 1. Give the signal a
Name, such as ‘Tally 6’ (without the single quotes). Select Logic I/O Only
and put a check in the box after the LIO number 1 on the Logic I/O (1-6)
tab. Set Tier, Rack, and Card to point to an existing LIO card, and select
an unused input Port # — we use an input because we are monitoring an
external event, such as a switch closure, and getting that event into the LIO.
So set Direction to In. You can use pretty much any Function selection;
I will use OnTally because it describes how the button’s LED will be
acting. Apply your changes in XPoint.
Back in the GP-16P Configuration tool, open the Device Properties
form and highlight Output LIOs 1 – 8. We are going to map our just-
defined LIO to Output LIO 6 so we can light the button 6 LED as earlier
advertised. Put a check in the checkbox after Output LIO 6: and select a
Signal Type of Source (since we set up the LIO in XPoint as a source), a
Signal ID of 1 (since that’s the signal id of the Tally 6 source we created),
and an LIO of 1 (since that’s the LIO number we used to point to the logic
port). Click OK and the properties will be sent to the panel.
Finishing the Script
Now add any other code you might need to the script, compile it, and
send it to the panel. Start the script and verify the functions you’ve
programmed. Let me make just one more point to end this discussion.
Since we set up button 1 to fire a salvo, you’ll notice that the BTN_1_PRESS
action has been defined in the auto generated section of the script. If you
want to do some additional thing when button 1 is pressed, you can’t just
write another BTN_1_PRESS action in the user portion of the script,
because the script can only have one instance of any action. If you really
wanted button 1 to serve multiple purposes, you would need to leave it set
to None / Custom in the Script Wizard, then write your own
BTN_1_PRESS action, as was covered in an earlier section.