EST EST3 v3.0 Programming Manual
EST EST3 v3.0 Programming Manual
Programming Manual
P/N 270381 Rev 3.0 21OCT99
DEVELOPED BY
COPYRIGHT NOTICE
TRADEMARKS
CREDITS
DOCUMENT HISTORY
Revision
Date
1.0
18JUL96
Initial release.
1.11.4
N/A
1.5
9MAY97
1.61.9
N/A
2.0
14DEC98
3.0
21OCT99
Content
Important information iv
About this manual v
The EST3 library vi
Related documentation vii
Chapter 1
Overview 1.1
About the Systems Definition Utility 1.2
Programming using rules and objects 1.4
Creating a rules file 1.9
Compiling the rules file 1.12
Developing a labeling plan 1.13
Identifying objects in the system 1.18
Priorities 1.21
Advanced programming techniques 1.25
Programming using logic groups 1.28
Programming using time controls 1.35
Chapter 2
Content
Supervisory (SUP) 2.34
Switch (SW) 2.35
TimeControl (TIME) 2.36
Trouble (TRB) 2.37
TwoStageTimerActivation (2STAGEA) 2.38
TwoStageTimerExpiration (2STAGETO) 2.39
Chapter 3
ii
Content
On 3.50
OnGuard 3.51
Open 3.52
ReleaseDoor (RELEASE) 3.53
RemoteAltSensitivityOff (RASOFF) 3.54
RemoteAltSensitivityOn (RASON) 3.55
Reset 3.56
SlowBlink (SLOW) 3.57
Steady 3.58
TroubleSilence (TS) 3.59
Appendix A
iii
Content
Important information
Limitation of liability
This product has been designed to meet the requirements of
NFPA Standard 72, 1996 Edition; Underwriters Laboratories,
Inc., Standard 864, 7th Edition; and Underwriters Laboratories
of Canada, Inc., Standard ULC S527. Installation in accordance
with this manual, applicable codes, and the instructions of the
Authority Having Jurisdiction is mandatory. EST shall not under
any circumstances be liable for any incidental or consequential
damages arising from loss of property or other damages or losses
owing to the failure of EST products beyond the cost of repair or
replacement of any defective products. EST reserves the right to
make product improvements and change product specifications
at any time.
While every precaution has been taken during the preparation of
this manual to ensure the accuracy of its contents, EST assumes
no responsibility for errors or omissions.
FCC warning
This equipment can generate and radiate radio frequency energy.
If this equipment is not installed in accordance with this manual,
it may cause interference to radio communications. This
equipment has been tested and found to comply within the limits
for Class A computing devices pursuant to Subpart B of Part 15
of the FCC Rules. These rules are designed to provide
reasonable protection against such interference when this
equipment is operated in a commercial environment. Operation
of this equipment is likely to cause interference, in which case
the user at his own expense, will be required to take whatever
measures may be required to correct the interference.
iv
Content
Intended audience
This manual and the information it contains is intended to be
used by persons who have working knowledge of Windows and
have successfully completed:
Organization
This manual is organized as described below:
Chapter 1 provides a general overview of basic concepts that the
system programmer should understand before attempting to
program system functions.
Chapter 2 provides an alphabetical reference of the input event
types used in the programming language.
Chapter 3 provides an alphabetical reference of the output
commands used in the programming language.
Appendix A provides a quick reference to the information
contained in chapters 2 and 3.
Content
vi
Content
Related documentation
NFPA
NFPA 70
NFPA 72
UL
R
UL 38
UL217
UL 228
UL 268
UL 268A
UL 346
UL 464
UL 521
UL 864
UL 1481
UL 1638
UL 1971
ULC S527
ULC S524
ULC S536
ULC S537
PLUS
vii
Content
viii
Chapter 1
Overview
Summary
1.1
Overview
Note: The
1.2
Overview
Model
Creative Technology
Diamond Sound
MT9ATC931
AT&T
Ultra
Model
Zebra Technologies
VTI, Inc.
SCANONE
Zebra Technologies
VTI, Inc.
1.3
Overview
Rules
Events
Device types
Objects
Labels
Rules
A rule is a programming statement that specifies which
commands to execute when a certain event takes place. A rule
consists of a label, an input statement, and an output statement
or statements.
The basic syntax for a rule is:
[Rule_label]
Input_statement:
Output_statement_1, {comments}
Output_statement_2, {comments}
Output_statement_3; {comments}
1.4
Overview
device_type
'object_label'
1.5
Overview
priority
device_type
delay_value
'object_label'
1.6
Overview
'asu_label'
'guard_label'
route_id
Events
An event is the outcome produced by a panel's CPU module
when an addressable point on the panel changes state. The
information contained in an event includes the logical address of
the point that changed state, the event type, and the event
message.
Device types
A device type is the classification given to objects created in the
database that defines the operating characteristics of the
corresponding device. For example, the PULL device type is
assigned to objects created for manual pull stations.
Refer to Appendix A: Quick Reference for a list of device types
and their use.
Objects
An object is a database entity that represents an addressable
point in the system, such as rail modules, smoke detectors,
switches, and light emitting diodes (LEDs).
Objects can also be:
Voice messages
1.7
Overview
Labels
A label is a descriptive word or words to identify a specific
object in the project database in order to simplify programming.
Labels are also used to identify a rule in the rules file. Typically,
object labels describe the physical location of the device that the
object represents.
Tip: Excessively long labels are generally harder to read.
User sees
space
underscore
<
>
1.8
Overview
before exiting the editor. It's also a good practice to save your
file before compiling and before saving the project.
Tip: Always look for instances where advanced programming
Order is important
When you have more than one rule that uses the same input
requirements to trigger separate output responses, the order in
which the rules appear in the rules file affects how the rules are
executed. The compiler takes multiple rules with like input
statements and executes them as though they were a single rule
containing multiple output statements. The output statements are
executed in the same order that they appear in the rules file.
Say you have a rules file containing the following rules:
[Rule 1]
ALARM SMOKE 'LVL5_SMK1' :
DELAY 30,
FANON 'STAIRWELL_PRESSURE_2';
[Rule 2]
ALARM SMOKE 'LVL5_SMK1' :
FAST 'CAB1_PNL1_LED1';
[Rule 3]
ALARM SMOKE 'LVL5_SMK1' :
ON AUDIBLE 'LVL5_HORN';
1.9
Overview
If any smoke detector on level 5 goes into trouble, the panel will
activate Rule 1 and turn the specified LED on, wait 5 minutes
(300 seconds), and then flash the LED at a slow rate. If during
the delay period another smoke detector on level 5 goes into
alarm, the panel will activate Rule 2 and flash the LED at a fast
rate, and turn on the specified horn.
The panel does not wait for the trouble response (Rule 1) to
finish before running the alarm response (Rule 2). In this
example however, once the delay period has ended and the
trouble has not been restored, the LED will be set to flash at the
slow rate.
Tip: When adding rules to a previously compiled rules file, place
1.10
Overview
1.11
Overview
1.12
Overview
Label format
Label content
Using common label modifiers
Label numbering
Using labels as messages
Formatting labels
To make your labels more readable, and more understandable,
your labeling plan should include how labels will be formatted.
You should take into consideration that labels will be viewed
online, on printed reports and on the system display panel.
Formatting considerations may include:
BLDG1_CAB
Bldg1Cab
The first label may be hard to read because it uses all uppercase
characters and there is no separation between the label modifiers
BLDG1 and CAB. The second label is easier to read because of
the space, represented by an underscore, between the two
modifiers. The third label uses upper and lowercase characters to
differentiate between label modifiers.
Always remember to be consistent and find a comfortable
balance between readability and length when formatting labels.
Consistency is the most important factor in making your labels
easy to use and understand. Notice in the example above that
each label abbreviates Building the same way. You want to
avoid using B1, Bldg_1, and Bldg1 as label modifiers to
reference the same building. Adding extra spaces to separate
1.13
Overview
ROOM_101
EAST_WING
SUTTON_HALL
ADMIN_BLDG
Description
DMPR_CNTRL
AMP_LEVEL7
LEDPANEL
1.14
Overview
Label
Description
SMK
Smoke detectors
PULL
Pull stations
LED
SW
1.15
Overview
Penthouse
Level 11
7th Floor
Level 10
6th Floor
Level 9
5th Floor
Level 8
4th Floor
Level 7
3rd Floor
Level 6
2nd Floor
Level 5
Mezzanine
Level 4
Lobby
Level 3
Basement
Level 2
Sub-basement
Level 1
[LEVELS2.CDR]
Stairwell
V2
[LEVELS3.CDR]
1.16
Overview
1.17
Overview
1.18
Overview
Ge
ne
ral
ala
No
rm
tify
ce
ntr
Ele
al
va
sta
tor
tio
c
n
ap
Alt
tur
.e
e
lev
ato
Ba
rc
se
ap
me
tur
nt
e
1s
HV
t fl
AC
oo
rH
2n
VA
df
C
loo
r
HV
3rd
AC
flo
or
HV
Co
AC
mp
ute
rs
1-3
hu
flo
tdo
or
wn
ex
Sta
h
a
irw
u
st
ell
do
or
loc
ks
Output functions
Input functions
3rd floor pull station
X X
X X
X X
X X
X X X
X X
X X
X X
X X X
X X X
X
X X
X X
X X
X X
X X
X X
X X
X X X
X X
X
X
[LEVELS1.CDR]
is one possible label for the 2ND floor elevator lobby smoke
detector.
The keyword ELEVLOBBY will be incorporated in the
elevator capture rule. Any detector having ELEVLOBBY as
part of its label will activate the elevator capture function.
The next object group is the Computer Shutdown function.
Inspection of the inputs that initiate the computer shutdown
1.19
Overview
function reveals that they are all devices located on the 2ND
floor. This should signal the designer that a label modifier such
as FLOOR2 or LEVEL2 should be included as part of the
device label for every device on the second floor. This also
implies that the floor number should be included in the labels of
all devices.
The keyword FLOOR2 will be incorporated in the computer
shutdown rule. Any device having FLOOR2 as part of its label
will activate the computer shutdown function. Note that the
elevator lobby detector labeled in the previous example will also
shutdown the second floor computer.
The final object group identified is the 1-3 Floor Exhaust
function. Examination of the inputs that initiate the 1-3 exhaust
function reveals that they are all duct smoke detectors. A label
modifier such as DUCT should be included as part of the
device label for all duct detectors. Notice that the input/output
matrix requires that the basement duct detector does not activate
the 1-3 Exhaust function. This should not affect the choice of
DUCT as a label modifier in the device label, as it is useful to
the designer in determining the device's function.
The keyword DUCT will be incorporated in the 1-3 Exhaust
rule. Because not all detectors with the keyword DUCT in
their labels are required to activate the 1-3 exhaust function, the
additional keywords FLOOR1, FLOOR2, and FLOOR3
will be added to the 1-3 exhaust function rule.
Notice that there are a few matrix entries that are not part of any
group. These functions are activated by a specific device. The
rules used to activate these outputs are written for the specific
function, rather than use by multiple objects.
The matrix for a major project would be very large and detailed.
Many inputs will have only one or two output correlations. The
experienced system designer will quickly recognize the patterns
that develop.
In Figure 1-3, notice that the first, second and third floors are
basically copies of each other. This is typical of high rise
buildings. This duplication of functions permits a designer to
recognize that the floor number will be an important label
modifier when creating labels for devices.
Our example also reveals the importance of well-planned label
modifiers. The proper selection of device labels permits the
designer to account for the common functions throughout the
building by writing only a few rules.
1.20
Overview
Priorities
The output priority parameter specifies the relative importance
of the output with respect to other rules activating the same
output and is an optional parameter.
Rules and objects programming has the ability to prioritize
output commands. There are two output priority levels, HIGH
and LOW. A high priority command will override a low priority
command. A low priority command can not override a high
priority command. A special priority called LATCH is discussed
later in this section.
Because an output device may be affected by any number of
input devices, each output has two software counters associated
with it to keep track of the output's status. The High priority
counter reflects the number of high priority set and reset
commands issued to the output, and the resulting high priority
status. The low priority counter reflects the number of low
priority set and reset commands issued to the output, and the
resulting low priority status.
An output's status is the result of both the high and low priority
counters as governed by the rules below.
A. Every set command increments the appropriate counter by
one; restoring a set command decrements the appropriate
counter by one.
B. Every reset command decrements the appropriate counter by
one; restoring a reset command increments the appropriate
counter by one.
C. When the high priority counter is equal to or less than
negative one (-1), the output is off.
D. When the high priority counter is equal to or greater than
one (+1), the output is on.
E. When the high priority counter is zero (0) and the low
priority counter is equal to zero (0), the output is off.
F. When the high priority counter is zero (0) and the low
priority counter is equal to or greater than one (+1), the
output is on.
When the input (left) side of a rule references the alarm event
type, the High priority level is the default value automatically
assigned to all output commands on the right side of the rule.
The output priority can be changed for the special cases where
low output priority is required in command to an alarm input.
When the input (left) side of a rule references any event type
except the alarm state, the Low priority level is the default value
1.21
Overview
All counters initially start out at zero. The output is off, per
rule E.
Input IN1 sets the output with a low priority. The Low
Priority Counter (LPC) increments to 1 per rule A. Output is
on, per rule F.
Input IN2 sets the output with a low priority. The LPC
increments to 2 per rule A. The output is still on, per rule F.
Input IN3 resets the output with a high priority. The High
Priority Counter (HPC) decrements to -1 per rule B. The
output is now off, per rule C.
Input IN5 sets the output with a low priority. The LPC
increments to 2 per rule A. The output is still off per rule C.
Input IN6 sets the output with a low priority. The LPC
increments to 3 per rule A. The output is still off per rule C.
Input IN7 sets the output with a low priority. The LPC
increments to 4 per rule A. The output is still off per rule C.
Input IN8 sets the output with a low priority. The LPC
increments to 5 per rule A. The output is still off per rule C.
Input IN9 resets the output with a high priority. The HPC
decrements to -2 per rule B. The output is still off per rule C.
1.22
Overview
1.23
Overview
Low Priority
Counter
0 = Off
>1 = On,
Step
Event
INx = Input
Quiescent
OFF
ON
ON
-1
OFF
-1
OFF
-1
OFF
-1
OFF
-1
OFF
-1
OFF
-2
OFF
10
-1
OFF
11
ON
12
ON
13
ON
14
ON
15
ON
16
ON
17
ON
18
OFF
1.24
Output
State
Overview
Wildcards
N-variables
Mathematical operators
Wildcards
The asterisk (*) can be used in a rule as a wildcard character to
conditionally select devices based on character patterns. The
asterisk may be substituted for any single character or group of
characters anywhere in the label.
Example
Selects
'LVL*'
'*_SMK'
'LVL*_SMK'
'*_SMK_*'
'*'
N-variable
The N-variable can be used in a rule to conditionally select
devices based on the numerical indexing used in their object
labels. When using the N-variable, the numbers required to make
the conditional true are specified in the input statement. When
the input statement becomes true, the number is substituted for
the variable N in the output statement.
Example
Selects
<N : #>
<N : # - #>
A range of numbers
<N : #, #, # - #,
# - #>
1.25
Overview
Notes:
Mathematical operators
Mathematical operators can be used in conjunction with the Nvariable in the rule output statement to conditionally select
devices based on the numerical indexing used in their object
labels.
When using mathematical operators, the numbers required to
make the conditional true are specified by the N-variable in the
input statement. When the input statement becomes true, the
number is substituted for the variable N in the output statement
and then increased or decreased by the number specified by the
# parameter.
Example
Selects
<N + #>
<N - #>
Notes:
1.26
Overview
1.27
Overview
Check-In groups
Service groups
In general:
Matrix
Instruction Text
Zones
Check-In
Guard Patrol
Service
1.28
Overview
1.29
Overview
Matrix groups
No
Yes
[2] Is devices in
alarm > or = to the
activation number?
Yes
No
Yes
No
Stop
[MTRXACT.CDR]
1.30
Overview
In the illustration above, the detector at location 3,3 was the first
detector to go into alarm, as indicated by the dark gray box. The
Matrix group creates a search radius around the first active
device, as indicated by the light gray box. Should any additional
detector in the light gray box go into alarm, the Matrix group
will activate its output response.
The following rule activates a device labeled 'HALON' when the
matrix group labeled 'MATRIX_GROUP_A' changes to the
active state and produces an alarm event.
[SampleRule]
Alarm Matrix 'MATRIX_GROUP_A':
ON 'HALON';
Note: The input event type used in rules written for And and
1.31
Overview
Matrix Group B
Radius = 2
Activation No. = 3
1,1 2,1 3,1 4,1 5,1 6,1
1,2 2,2 3,2 4,2 5,2 6,2
First detector in alarm
Search radius
Zone groups
Zone groups are a collection of input devices that are grouped
together to provide a unique response separate from their
individual device responses. For all the devices in the group that
go into alarm, only a single Zone Active event is sent to the
Alarm queue on the 3-LCD. To determine which devices in the
zone are active, select the Zone Active event in the Alarm queue
and press the Details switch.
Zone groups can consist of any of the following device types:
1.32
Overview
Setting the Zone Group Inhibit option prevents the zone group's
response from re-activating when subsequent members of the
group go active after the outputs have been silenced.
Check-In groups
Check-in groups are a collection of Emergency device types that
are grouped together to provide a unique response when
members of the group fail to check in during a prescribed time
period. If one or more devices do not check in during the allotted
time, a Check-In Active response is generated, indicating those
devices which have failed to check in. Check-in groups are
typically used in senior citizen housing to monitor the wellness
of occupants.
Note: Devices that do not check in are removed from the check-
1.33
Overview
Service groups
Service groups are a collection of devices that are grouped
together for testing purposes. When enabled, the Service group
automatically disables the member device's normal alarm
response, and provides a common alternate test response.
Service groups can consist of any of the following device types:
Audible, CommonAlarmOutput, CommonMonitorOutput,
CommonSupervisoryOutput, CommonTroubleOutput,
DamperControl, DamperFeedback, DoorControl, DoorFeedback,
Emergency, FanControl, FanFeedback, Firephone, Gatevalve,
GenAlarm, Guard, Heat, Monitor, Power, Pull, Security, Smoke,
SmokeVfy, StageOne, StageTwo, SupervisedOutput,
Supervisory, Tamper, Temperature, Visible, Waterflow
1.34
Overview
then select
Once a year
Once a month
Once a week
Once a day
1.35
Overview
1.36
Chapter 2
2.1
Acknowledge (ACK)
Use the Acknowledge event to activate a rule when an operator
acknowledges an event displayed on the 3-LCD module.
The Acknowledge event requires that you specify a device type
or an object label, or both.
Acknowledge device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Note: The Acknowledge input event can only be used when the
2.2
Alarm
Use the Alarm event to activate a rule when any point on a panel
or any panel in the same network routing group changes to the
alarm state.
The Alarm event requires that you specify a device type or an
object label, or both.
Alarm device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Turn on fan relay when any lobby smoke detector
goes into alarm}
[FAN_ON]
ALARM SMK 'LVL*_LOBBY*':
FANON -HIGH 'FAN_RELAY';
Tip: Use the GenSmoke device type when you want to write a
single rule that applies to devices that can have either Smoke or
SmokeVfy device types.
2.3
AlarmSilence (AS)
Use the AlarmSilence event to activate a rule when an operator
presses a switch that starts a panel's Alarm Silence function. The
switch can be the Alarm Silence switch on the 3-LCD module or
a control/display module switch programmed to execute the
AlarmSilence command. Typically, you use the AlarmSilence
event to silence device types in addition to those automatically
silenced by the Alarm Silence function.
The AlarmSilence event does not require a that you specify a
device type or an object label.
AlarmSilence :
Note: Project configuration settings determine if the Alarm
2.4
AlarmVerify (AVER)
Use the AlarmVerify event to activate a rule when a smoke
detector starts its smoke verification cycle. Typically, the
AlarmVerify event is used to provide an indication of potential
alarm or pre-alarm conditions.
The AlarmVerify event requires that you specify a device type
or an object label, or both.
AlarmVerify device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Flash LED on control/display module when any
smoke detector is in its smoke verification
process}
[VERIFY_ON]
AVER GENSMOKE 'SMK_*':
SLOW -LOW 'DISPLAY_1_LED_1';
2.5
AllCall
Use the AllCall event to activate a rule when an operator presses
the All Call or All Call Minus switch on the 3-ASU.
The AllCall event does not require that you specify a device type
or an object label.
AllCall :
Example
{Flash LED on control/display module when All
Call in process}
[ALL_CALL_ON]
ALLCALL:
FAST -LOW 'DISPLAY_1_LED_1';
2.6
CallIn (CI)
Use the CallIn event to activate a rule when a fire safety
professional plugs a handset into a firefighter's telephone jack.
The CallIn event requires that you specify a device type or an
object label, or both.
CallIn device_type 'object_label':
Parameter
Description
device_type
'object_label'
Example
{Flash LED on control/display module when
connection made to firefighter's telephone
circuit}
[CALLIN_ON]
CI FP 'FP_LVL_<N:1-10>':
FAST -LOW 'DISPLAY_1_LED_<N>';
2.7
Drill
Use the Drill event to activate a rule when an operator presses a
switch that starts a panel's Drill function. The switch can be the
Drill switch on the 3-LCD module or a control/display module
switch programmed to execute the Drill command. Typically,
you use the Drill event to activate devices in addition to those
automatically activated by the Drill function.
The Drill event does not require that you specify a device type
or an object label.
Drill :
Note: Project configuration settings determine if the Drill
2.8
Emergency (EMER)
Use the Emergency event to activate a rule when a member of a
Check-in group activates their check-in device anytime outside
of their check-in period or a second time during their check-in
period.
The Emergency event requires that you specify a device type or
an object label, or both.
Emergency device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Turn on the common distress relay}
[DISTRESS]
EMER '*':
ON SUP 'DISTRESS_RELAY';
2.9
Evacuation (EVAC)
Use the Evacuation event to activate a rule when an operator
presses a control/display module switch programmed to execute
a panel's Evacuation function. Typically, you use the Evacuation
event to activate devices in addition to those automatically
activated by the Evacuation function.
The Evacuation event does not require that you specify a device
type or an object label.
Evacuation :
Example
{Flash LED on control/display module when an
Evacuation has been initiated}
[EVACUATION_RESPONSE]
EVAC:
FAST -LOW 'DISPLAY_1_LED_1';
2.10
FirstAlarm (FA)
Use the FirstAlarm event to activate a rule the first time that any
point on a panel or any panel in the same network routing group
changes to the alarm state.
The FirstAlarm event does not require that you specify a device
type or an object label.
FirstAlarm :
Example
{Light LED on control/display module when the
first alarm event occurs}
[FIRST_ALARM_ON]
FA :
STEADY -LOW 'FIRST_ALARM_LED';
2.11
FirstDisable (FD)
Use the FirstDisable event to activate a rule the first time that
any point on a panel or any panel in the same network routing
group changes to the disabled state.
The FirstDisable event does not require that you specify a device
type or an object label.
FirstDisable :
Example
{Flash LED on control/display module when the
first disable event occurs}
[FIRST_DISABLE_ON]
FD:
SLOW -LOW 'FIRST_DISABLE_LED';
2.12
FirstMonitor (FM)
Use the FirstMonitor event to activate a rule the first time that
any point on a panel or any panel in the same network routing
group changes to the monitor state.
The FirstMonitor event does not require that you specify a
device type or an object label.
FirstMonitor :
Example
{Flash LED on control/display module when the
first monitor event occurs}
[FIRST_MONITOR_ON]
FM:
SLOW -LOW 'FIRST_MONITOR_LED';
2.13
FirstSupervisory (FS)
Use the FirstSupervisory event to activate a rule the first time
that any point on a panel or any panel in the same network
routing group changes to the supervisory state.
The FirstSupervisory event does not require that you specify a
device type or an object label.
FirstSupervisory :
Example
{Flash LED on control/display module when the
first supervisory event occurs}
[FIRST_SUPERVISORY_ON]
FS:
FAST -LOW 'FIRST_SUPR_LED';
2.14
FirstTrouble (FT)
Use the FirstTrouble event to activate a rule the first time that
any point on a panel or any panel in the same network routing
group changes to the trouble state.
The FirstTrouble event does not require that you specify a
device type or an object label.
FirstTrouble :
Example
{Flash LED on control/display module when the
first trouble event occurs}
[FIRST_TROUBLE_ON]
FT:
FAST -LOW 'FIRST_TROUBLE_LED';
2.15
GroundFault (GNDF)
Use the GroundFault event to activate a rule when a rail module
detects a ground fault on its field wiring.
The GroundFault event requires that you specify a device type or
an object label, or both.
GroundFault device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Flash LED on control/display module to indicate
a ground fault}
[GROUNDFAULT_RESPONSE]
GNDF 'Grnd_Fault_Data_Card_1_01_05':
FAST -LOW 'GROUND_FAULT_LED';
2.16
GuardPatrol (GPG)
Use the GuardPatrol event to activate a rule when a patrol guard
fails to activate a patrol tour station at the proper time.
Typically, you use the GuardPatrol event to create an output
response for the entire Guard Patrol group.
The GuardPatrol event requires that you specify a device type or
an object label, or both.
GuardPatrol device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Turn on the guard patrol late/out of sequence
horn}
[GUARDPATROL_RESPONSE]
GPG 'GUARD_PATROL_Group1':
ON -HIGH AUD 'GUARD_HORN';
2.17
LocalAlarm (LALM)
Use the LocalAlarm event to activate a rule when a rail module's
LocalAlarm pseudo point goes active.
The LocalAlarm event requires that you specify a device type or
an object label, or both.
LocalAlarm device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Light LED on control/display module when
unprogrammed device detected on Signature
controller module}
[LOCAL_ALARM_ACTIVE]
LALM 'Unprogrammed_Device_Data_Card_1_01_05':
STEADY -LOW 'DISPLAY_1_LED_1';
2.18
LocalMonitor (LMON)
Use the LocalMonitor event to activate a rule when a rail
module's LocalMonitor pseudo point goes active.
The LocalMonitor event requires that you specify a device type
or an object label, or both.
LocalMonitor device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Flash LED on control/display module when the
Signature controller is identifying the devices
on the loop}
[LOCAL_MONITOR_ACTIVE]
LMON 'Reconstct_Line_Data_Card_1_01_05':
SLOW -LOW 'DISPLAY_1_LED_1';
2.19
LocalTrouble (LTRB)
Use the LocalTrouble event to activate a rule when a rail
module's LocalTrouble pseudo point goes active.
The LocalTrouble event requires that you specify a device type
or an object label, or both.
LocalTrouble device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Flash LED on control/display module when a map
fault occurs on the Signature controller module}
[LOCAL_TROUBLE_ACTIVE]
LTRB 'Map_Fault_Data_Card_1_01_05':
FAST -LOW 'DISPLAY_1_LED_1';
2.20
Monitor (MON)
Use the Monitor event to activate a rule when any point on a
panel or any panel in the same network routing group changes to
the monitor state.
The Monitor event requires that you specify a device type or an
object label, or both.
Monitor device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Turn on fan status LEDs 1-10}
[FAN_LED]
MON FANFB 'FAN<N:1-10>_STATUS':
STEADY -LOW 'FAN<N>_ON';
2.21
R1
Use the R1 event to activate a rule when the first phase of the 3phase reset cycle starts after an operator presses the Reset switch
on the 3-LCD.
The R1 event does not require that you specify a device type or
an object label.
R1 :
Note: The R1 event is self-restoring. Any outputs activated by
2.22
R2
Use the R2 event to activate a rule when the second phase of the
3-phase reset cycle starts. The second phase starts after the first
phase finishes.
The R2 event does not require that you specify a device type or
an object label.
R2 :
Note: The R2 event is self-restoring. Any outputs activated by
2.23
R3
Use the R3 event to activate a rule when the third phase of the 3phase reset cycle starts. The third phase starts after the second
phase finishes.
The R3 event does not require that you specify a device type or
an object label.
R3 :
Note: The R3 event is self-restoring. Any outputs activated by
2.24
RelayConfirmation (RLYCFG)
Use the RelayConfirmation event to activate a rule when a
control relay indicates that its electrical contacts have switched
positions. Typically, you use the RelayConfirmation event in
applications that require verifying the proper operation of
remote controlled functions.
The RelayConfirmation event requires that you specify a device
type or an object label, or both.
RelayConfirmation device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Light LED on control/display module when relay
confirmation occurs}
[RELAY_OK]
RLYCFG DOOR 'DOOR_CONTROL_RELAY':
STEADY -LOW 'DOOR_RELAY_LED';
2.25
Reset
Use the Reset event to activate a rule when an operator presses a
switch that starts a panel's Reset function. The switch can be the
Reset switch on the 3-LCD module or a control/display module
switch programmed to execute the Reset command. Typically,
you use the Drill event to activate output responses in addition
to those automatically activated by the Reset function.
The Reset event does not require that you specify a device type
or an object label.
Reset :
Example
{Flash LED on control/display module during
reset cycle}
[SYSTEM_RESET_ON]
RESET:
FAST -LOW 'RESET_LED';
Note: See also R1, R2, and R3 input event types.
2.26
Security (SEC)
Use the Security event to activate a rule when the open input to a
device or circuit that monitors a supervisory or tamper switch
closes.
The Security event requires that you specify a device type or an
object label, or both.
Security device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Light LED on control/display module when relay
confirmation occurs}
[RELAY_OK]
SEC SEC 'CAB1_TAMPER_SW':
STEADY -LOW 'TAMPER_SW_LED';
2.27
ServiceDevice (SERV)
Use the ServiceDevice event to activate a rule when an
authorized service technician activates a device in a Service
group under test. The ServiceDevice event is used to program
individual responses for each device in the Service group.
The ServiceDevice event requires that you specify a device type
or an object label, or both.
ServiceDevice device_type 'object_label' :
Parameter
Description
device_type
'object_label'
2.28
ServiceGroup (SG)
Use the ServiceGroup event to activate a rule when an
authorized service technician activates any device in a Service
group under test. The ServiceGroup event is used to program a
single response for the entire Service group in order to perform a
one-man test.
The ServiceDevice event requires that you specify a device type
or an object label, or both.
ServiceGroup device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Notes
2.29
ServiceGroupActive (SGA)
Use the ServiceGroupActive event to activate a rule when an
authorized service technician starts a test on a service group
from the 3-LCD module.
The ServiceGroupActive event does not require that you
specifya device type or an object label.
ServiceGroupActive :
Example
{Light LED on control/display module when any
service group is in test mode}
[SERVICE_GROUP_ACTIVE_RESPONSE]
SGA:
STEADY 'CDM_1_LED1';
2.30
SprinklerSupervisory (SPSUP)
Use the SprinklerSupervisory event to activate a rule when the
open input to a device or circuit that supervises a component of
the sprinkler system closes. Typically, you use the
SprinklerSupervisory event to provide local and off-premises
notification of sprinkler system status.
The SprinklerSupervisory event requires that you specify a
device type or an object label, or both.
SprinklerSupervisory device_type 'object_label' :
Parameter
Description
device_type
'object_label'
2.31
Startup (STUP)
Use the Startup event to activate a rule when the panel is
initially powered up or when an operator initiates the Restart
command from the 3-LCD module. Typically, you use the
Startup event to program the initial operating state of system
components or functions.
The Startup event does not require that you specify a device type
or an object label.
Startup :
Example
{Disable HVAC switches on startup}
[STARTUP]
STUP:
DISABLE -LOW SW '*HVAC*';
2.32
StationActivation (STACT)
Use the StationActivation event to activate a rule when a patrol
guard activates a patrol tour station. Typically, you use the
StationActivation event to monitor a patrol guard's progress
through the tour.
The StationActivation event requires that you specify a device
type or an object label, or both.
StationActivation device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Light LED on control/display module when any
tamper guard station is activated}
[GUARD_STATION_OK]
STACT 'STATION<N:1-10>':
STEADY -LOW 'STATION<N>_OK';
2.33
Supervisory (SUP)
Use the Supervisory event to activate a rule when any point on a
panel or any panel in the same network routing group changes to
the supervisory state.
The Supervisory event requires that you specify a device type or
an object label, or both.
Supervisory device_type 'object_label' :
Parameter
Description
device_type
'object_label'
2.34
Switch (SW)
Use the Switch event to activate a rule when an operator presses
a control/display module switch.
The Switch event requires that you specify a device type or an
object label, or both.
Switch device_type 'object_label' :
Parameter
Description
device_type
'object_label'
2.35
TimeControl (TIME)
Use the TimeControl event to activate a rule when a specific
combination of days, dates, and/or time of day occurs. Typically,
you use the TimeControl event to program output responses that
hold and release doors or change smoke detector sensitivity.
The TimeControl event requires that you specify a device type
or an object label, or both.
TimeControl device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Hold all doors at 6:30 PM}
[DOOR_LOCK]
TIME 'LOCKDOORS':
HOLD -LOW DOOR '*DOORLOCKS*';
2.36
Trouble (TRB)
Use the Trouble event to activate a rule when any point on a
panel or any panel in the same network routing group changes to
the trouble state.
The Trouble event requires that you specify a device type or an
object label, or both.
Trouble device_type 'object_label' :
Parameter
Description
device_type
'object_label'
Example
{Energize the remote common trouble relay}
[TROUBLE_LED]
TRB '*':
ON SUP 'TROUBLE_RELAY';
2.37
TwoStageTimerActivation (2STAGEA)
Use the TwoStageTimerActivation event to activate a rule when
a panel's two-stage alarm timer starts counting down. Typically,
you use the TwoStageTimerActivation event in jurisdictions that
require some time delay in order to verify the source of the
alarm before sounding a general alarm.
The TwoStageTimerActivation event does not require that you
specify a device type or an object label.
TwoStageTimerActivation :
Note: The project parameters' setting determines the two-stage
2.38
TwoStageTimerExpiration (2STAGETO)
Use the TwoStageTimerExpiration event to activate a rule when
a panel's two-stage alarm timer expires. Typically, you use the
TwoStageTimerExpiration event to sound a general alarm in
jurisdictions that require some time delay to verify of the source
of the alarm.
The TwoStageTimerExpiration event does not require that you
specify a device type or an object label.
TwoStageTimerExpiration :
Note: The project parameters setting determines the two-stage
2.39
2.40
Chapter 3
Output commands
Summary
3.1
Output commands
NSCommonMonitorOff (NSCMOFF) 3.42
NSCommonMonitorOn (NSCMON) 3.43
NSCommonSupervisoryOff (NSCSOFF) 3.44
NSCommonSupervisoryOn (NSCSON) 3.45
NSCommonTroubleOff (NSCTOFF) 3.46
NSCommonTroubleOn (NSCTON) 3.47
Off 3.48
OffGuard 3.49
On 3.50
OnGuard 3.51
Open 3.52
ReleaseDoor (RELEASE) 3.53
RemoteAltSensitivityOff (RASOFF) 3.54
RemoteAltSensitivityOn (RASON) 3.55
Reset 3.56
SlowBlink (SLOW) 3.57
Steady 3.58
TroubleSilence (TS) 3.59
3.2
Output commands
AlarmSilence (AS)
Use the AlarmSilence command to activate a panel's Alarm
Silence function from a control/display module switch. By
programming a control/display module switch to execute the
AlarmSilence command, an operator can silence alarm
notification signals from panels that do not contain a 3-LCD
module.
The AlarmSilence command only requires that you specify a
cabinet label or a routing label.
AlarmSilence 'cabinet_label' ;
or
AlarmSilence 'routing_label' ;
Parameter
Description
Notes
3.3
Output commands
AlternateLanguage (ALTL)
Use the AlternateLanguage command to change the language
that the 3-LCD module uses to display text from a
control/display module switch. By programming a
control/display module switch to execute the AlternateLanguage
command, an operator can control bilingual operation of the
panel. You can also use to a time control to automatically switch
between the primary and secondary language.
The AlternateLanguage command does not require that you
specify a device type or an object label.
AlternateLanguage ;
Notes
3.4
Output commands
AlternateMsgOff (ALTMOFF)
Use the AlternateMsgOff command to activate the primary
routing settings that a panel uses for routing device event
messages.
The AlternateMsgOff command only requires that you specify a
cabinet label or a routing label.
AlternateMsgOff 'cabinet_label' ;
or
AlternateMsgOff 'routing_label' ;
Parameter
Description
Note: Wildcards may be used in the cabinet label but not in the
routing label.
Example
{Change message routing from control/display
module to primary}
[PRIMARY_MSG_ON]
SW 'B1_C1_PRI_MSGON':
ALTMOFF 'All_Cabinets';
3.5
Output commands
AlternateMsgOn (ALTMON)
Use the AlternateMsgOn command to activate the alternate
routing settings that a panel uses for routing device event
messages.
The AlternateMsgOn command only requires that you specify a
cabinet label or a routing label.
AlternateMsgOn 'cabinet_label' ;
or
AlternateMsgOn 'routing_label' ;
Parameter
Description
Note: Wildcards may be used in the cabinet label but not in the
routing label.
Example
{Switch to alternate message routing
configuration during non-regular work hours}
[ALTERNATE_MSG_ON]
TIME 'MON_FRI_NONREG_HOURS':
ALTMON 'All_Cabinets';
3.6
Output commands
AlternateSensitivityOff (ALTSOFF)
Use the AlternateSensitivityOff command to load the primary
sensitivity and alarm verification settings into every smoke
detector in the system. Typically, the primary settings are used
during normal business hours when the protected premises is
occupied.
The AlternateSensitivityOff command does not require that you
specify a device type or an object label.
AlternateSensitivityOff ;
Example
{Switch smoke detectors to primary sensitivity
level during regular work hours}
[ALT_SENS_OFF]
TIME 'MON_FRI_REGULAR_HOURS':
ALTSOFF;
Tip: Use the RemoteAltSensitivityOff command for greater
3.7
Output commands
AlternateSensitivityOn (ALTSON)
Use the AlternateSensitivityOn command to load the alternate
sensitivity and alarm verification settings into every smoke
detector in the system. Typically, the alternate settings are used
during off-normal business hours when the protected premises is
unoccupied.
The AlternateSensitivityOn command does not require that you
specify a device type or an object label.
AlternateSensitivityOn ;
Example
{Switch smoke detectors to alternate sensitivity
level setting during non-regular work hours}
[ALT_SENS_ON]
TIME 'MON_FRI_AFTER_HOURS':
ALTSON;
Tip: Use the RemoteAltSensitivityOn command for greater
3.8
Output commands
AmpOff
Use the AmpOff command to turn off an amplifier's audio
output and remove the connected audio channel from its input.
The AmpOff command contains two parts. The first part of the
command (AmpOff) identifies the amplifier and the second part
(to) identifies the audio channel.
The AmpOff command only works on devices with the Amp
device type. You are required to specify the amplifier label and
the channel label. Specifying a priority value is optional.
AmpOff priority 'amp_label' to 'channel_label' ;
Parameter
Description
priority
'amp_label'
3.9
Output commands
AmpOn
Use the AmpOn command to turn on an amplifier's audio output
and connect an audio channel to its input. The AmpOn command
contains two parts. The first part of the command (AmpOn)
identifies the amplifier and the second part (to) identifies the
audio channel.
The AmpOn command only works on devices with the Amp
device type. You are required to specify the amplifier label and
the channel label. Specifying a priority value is optional.
AmpOn priority 'amp_label' to 'channel_label' ;
Parameter
Description
priority
'amp_label'
3.10
Output commands
Close
Use the Close command to turn off an output circuit or relay that
connects to the control mechanism used to close a damper.
The Close command only works on devices with the
DamperControl device type. You are required to specify the
object label. Specifying a priority value is optional.
Close priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.11
Output commands
CommonAlarmOff (CAOFF)
Use the CommonAlarmOff command to turn off a supervised
notification signal output circuit that a panel automatically
activates when the FirstAlarm event occurs.
The CommonAlarmOff command only works on devices with
the CommonAlarmOutput device type. You are required to
specify the object label. Specifying a priority value is optional.
CommonAlarmOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
Note: Active common alarm outputs can not be turned off using
3.12
Output commands
CommonAlarmOn (CAON)
Use the CommonAlarmOn command to turn on a supervised
notification signal output circuit that a panel automatically
activates when the FirstAlarm event occurs.
The CommonAlarmOn command only works on devices with
the CommonAlarmOutput device type. You are required to
specify the object label. Specifying a priority value is optional.
CommonAlarmOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
[COMMON_ALARM_ON_SWITCHES]
SW 'COM_ALARM_ON_LVL<N:1-10>':
CAON -LOW 'LVL<N>_COM_ALARM_CKT*';
3.13
Output commands
CommonMonitorOff (CMOFF)
Use the CommonMonitorOff command to turn off a supervised
notification signal output circuit that a panel automatically
activates when the FirstMonitor event occurs.
The CommonMonitorOff command only works on devices with
the CommonMonitorOutput device type. You are required to
specify the object label. Specifying a priority value is optional.
CommonMonitorOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
Notes
Active common monitor outputs can not be turned off using the
CommonMonitorOff command.
You can not use any device to turn off a common monitor output
that upon activation produces a monitor event. For example, you
can not use a control/display module switch.
Example
[COMMON_MON_OFF_RESPONSE]
ALARM GENALARM:
CMOFF -LOW 'EVAC_DOOR';
3.14
Output commands
CommonMonitorOn (CMON)
Use the CommonMonitorOn command to turn on a supervised
notification signal output circuit that a panel automatically
activates when the FirstMonitor event occurs.
The CommonMonitorOn command only works on devices with
the CommonMonitorOutput device type. You are required to
specify the object label. Specifying a priority value is optional.
CommonMonitorOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
[COMMON_MON_ON_RESPONSE]
ALARM GENALARM:
CMON -LOW 'COM_MON_CKT_LVL*';
3.15
Output commands
CommonSupervisoryOff (CSOFF)
Use the CommonSupervisoryOff command to turn off a
supervised notification signal output circuit that a panel
automatically activates when the FirstSupervisory event occurs.
The CommonSupervisoryOff command works on devices with
the CommonSupervisoryOutput device type. You are required to
specify the object label. Specifying a priority value is optional.
CommonSupervisoryOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.16
Output commands
CommonSupervisoryOn (CSON)
Use the CommonSupervisoryOn command to turn on a
supervised notification signal output circuit that a panel
automatically activates when the FirstSupervisory event occurs.
The CommonSupervisoryOn command works on devices with
the CommonSupervisoryOutput device type. You are required to
specify the object label. Specifying a priority value is optional.
CommonSupervisoryOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
[COMMON_SUP_ON_SWITCHES]
SW 'COM_SUP_ON_LVL<N:1-10>':
CSON -LOW 'LVL<N>_COM_SUP_CKT*';
3.17
Output commands
Delay (DLY)
Use the Delay command to insert a time delay between rule
output command statements when a rule activates and restores.
The Delay command only requires that you specify the delay
value.
Delay delay_value ;
Parameter
Description
delay_value
Example
{Turn amps on at startup to accept the General
channel}
[STARTUP_AMPS]
STUP:
AMPON 'LVL_5_AMP' TO 'CH_GEN_01_08',
DLY 10,
AMPON 'LVL_6_AMP' TO 'CH_GEN_01_08';
3.18
Output commands
DelayActivate (DLYA)
Use the DelayActivate command to insert a time delay between
rule output command statements only when the rule activates.
The delay is not inserted when the rule restores.
The DelayActivate command only requires that you specify the
delay value.
DelayActivate delay_value ;
Parameter
Description
delay_value
Example
{Supply and pressure fan alarm response}
[ALARM_FAN]
ALARM GENSMOKE:
FANOFF 'SUPPLY_FAN',
DLYA 15,
FANON 'PRESSURE_FAN1';
3.19
Output commands
DelayRestore (DLYR)
Use the DelayRestore command to insert a time delay between
rule output command statements only when the rule restores.
The delay is not inserted when the rule activates.
The DelayRestore command only requires that you specify the
delay value.
DelayRestore delay_value ;
Parameter
Description
delay_value
Example
{Supply and pressure fan alarm response}
[ALARMFAN]
ALARM GENSMOKE:
FANON 'PRESSURE_FAN1',
DLYR 15,
FANON 'PRESSURE_FAN2';
3.20
Output commands
Disable
Use the Disable command to inhibit the automatic or manual
control of a system hardware component, circuit, or logic group.
The Disable command requires that you specify a device type or
an object label, or both.
Disable device_type 'object_label' ;
Parameter
Description
device_type
'object_label'
Note: Disabling a Zone group disables the group and all the
3.21
Output commands
Drill
Use the Drill command to activate a panel's Drill function from a
control/display module switch. By programming a
control/display module switch to execute the Drill command, an
operator can turn on alarm notification signals from panels that
do not contain a 3-LCD module.
The Drill command only requires that you specify a cabinet label
or routing label.
Drill 'cabinet_label' ;
or
Drill 'routing_label' ;
Parameter
Description
Notes
3.22
Output commands
Enable
Use the Enable command to allow automatic or manual control
of a system hardware component, circuit, or logic group.
The Enable command requires that you specify a device type or
an object label, or both.
Enable device_type 'object_label' ;
Parameter
Description
device_type
'object_label'
Example
[CIRCUIT_ENABLE]
SW 'PANEL_1_SW1':
ENABLE 3-DSDC 'SIGA_CIRCUIT_1';
3.23
Output commands
Evacuation (EVAC)
Use the Evacuation command to activate a panel's Evacuation
function from a control/display module switch. By programming
a control/display module switch to execute the Evacuation
command, an operator can put a panel into alarm and force the
panel to activate its programmed alarm responses from panels
that do not contain a 3-LCD module..
The Evacuation command only requires that you specify a
cabinet label or routing label.
Evacuation 'cabinet_label' ;
or
Evacuation 'routing_label' ;
Parameter
Description
Note: Wildcards may be used in the cabinet label but not in the
routing label.
Example
[REM_EVAC_CNTRL]
SW 'DISPLAY_1_SW1':
EVAC 'All_Cabinets';
3.24
Output commands
FanOff
Use the FanOff command to turn off an output circuit or relay
that connects to the control mechanism used to turn off a fan.
The FanOff command only works on devices with the
FanControl device type. You are required to specify the object
label. Specifying a priority value is optional.
FanOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.25
Output commands
FanOn
Use the FanOn command to turn on an output circuit or relay
that connects to the control mechanism used to turn on a fan.
The FanOn command only works on devices with the
FanControl device type. You are required to specify the object
label. Specifying a priority value is optional.
FanOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.26
Output commands
FastBlink (FAST)
Use the FastBlink command to turn a light-emitting diode on a
control/display module on and off at a fast interval.
The FastBlink command only works on devices with the LED
device type. You are required to specify the object label.
Specifying a priority value is optional.
FastBlink priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
{Flash LED on control/display module when second
phase of the system reset process occurs}
[ANN_RESET_2ND_PHASE]
R2:
FAST -LOW 'R2_LED';
3.27
Output commands
GAInhibit (GAIN)
Use the GAInhibit command to stop a panel's two-stage timer
from a control/display module switch. By programming a
control/display module switch to execute the GAInhibit
command, an operator can stop a panel's two-stage alarm timer
before it expires and prevent the panel from sounding a general
alarm.
The GAInhibit command only requires that you specify the
cabinet label or the routing label.
GainInhibit 'cabinet_label' ;
or
GainInhibit 'routing_label' ;
Parameter
Description
Notes
3.28
Output commands
HoldDoor (HOLD)
Use the HoldDoor command to turn on an output circuit or relay
that connects to the control mechanism used to hold a door.
The HoldDoor command only works with devices assigned the
DoorControl device type. You are required to specify the object
label. Specifying a priority value is optional.
HoldDoor priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.29
Output commands
LampTest (LAMP)
Use the LampTest command to activate the lamp test function
from a control/display module switch. By programming a
control/display module switch to execute the LampTest
command, an operator can perform a lamp test on panels that do
not contain a 3-LCD module.
The LampTest command does not require that you specify a
device type or an object label.
LampTest ;
Notes
3.30
Output commands
LEDOff
Use the LEDOff command to turn a light-emitting diode on a
control/display module off.
The LEDOff command only works on devices with the LED
device type. You are required to specify the object label.
Specifying a priority value is optional.
LEDOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
{Turn Damper Open LEDs Off when closed limit
switch is activated}
[DAMPER_LIMIT_LED_OFF]
MON DAMPERFB 'FAN<N:1-5>_DAMP_CLIMIT':
LEDOFF -LOW 'DMPR<N>_OPEN_LED';
3.31
Output commands
MsgOff
Use the MsgOff command to stop broadcasting a voice message
over the selected audio channel. The MsgOff command contains
two parts. The first part of the command (MsgOff) identifies the
message and the second part (to) identifies the audio channel.
The MsgOff command only works on devices with the Msg
device type. You are required to specify the message label and
the channel label. Specifying an ASU label or priority value is
optional.
MsgOff priority 'msg_label' from 'asu_label' to
'channel_label' ;
Parameter
Description
priority
'msg_label'
'asu_label'
3.32
Output commands
MsgOn
Use the MsgOn command to start broadcasting a voice message
over a selected audio channel. The MsgOn command contains
two parts. The first part of the command (MsgOn) identifies the
message and the second part (to) identifies the audio channel.
The MsgOn command only works on devices with the Msg
device type. You are required to specify the message label and
the channel label. Specifying an ASU label or priority value is
optional.
MsgOn priority 'msg_label' from 'asu_label' to
'channel_label' ;
Parameter
Description
priority
'msg_label'
'asu_label'
3.33
Output commands
NCClose
Use the NCClose command to turn on an output circuit or relay
that connects to the control mechanism used to close a damper.
The NCClose command only works on devices with the
DamperControl device type. You are required to specify the
object label. Specifying a priority value is optional.
NCClose priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.34
Output commands
NCFanOff
Use the NCFanOff command to turn on an output circuit or relay
that connects to the control mechanism used to turn off a fan.
The NCFanOff command only works on devices with the
FanControl device type. You are required to specify the object
label. Specifying a priority value is optional.
NCFanOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.35
Output commands
NCFanOn
Use the NCFanOn command to turn off an output circuit or relay
that connects to the control mechanism used to turn on a fan.
The NCFanOn command only works on devices with the
FanControl device type. You are required to specify the object
label. Specifying a priority value is optional.
NCFanOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.36
Output commands
NCHoldDoor (NCHOLD)
Use the NCHoldDoor command to turn off an output circuit or
relay that connects to the control mechanism used to hold a
door.
The NCHoldDoor command only works with devices with the
DoorControl device type. You are required to specify the object
label. Specifying a priority value is optional.
NCHoldDoor priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.37
Output commands
NCOpen
Use the NCOpen command to turn off an output circuit or relay
that connects to the control mechanism used to open a damper.
The NCOpen command only works on devices with the
DamperControl device type. You are required to specify the
object label. Specifying a priority value is optional.
NCOpen priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.38
Output commands
NCReleaseDoor (NCRELEASE)
Use the NCReleaseDoor command to turn on an output circuit or
relay that connects to the control mechanism used to release a
door.
The NCReleaseDoor command only works on devices with the
DoorControl device type. You are required to specify the object
label. Specifying a priority value is optional.
NCReleaseDoor priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.39
Output commands
NSCommonAlarmOff (NSCAOFF)
Use the NSCommonAlarmOff command to turn off a
nonsupervised output relay that a panel automatically activates
when the FirstAlarm event occurs.
The NSCommonAlarmOff command only works on devices
with the NSCommonAlarmOutput device type. You are required
to specify the object label. Specifying a priority value is
optional.
NSCommonAlarmOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
Notes
3.40
Output commands
NSCommonAlarmOn (NSCAON)
Use the NSCommonAlarmOn command to turn on a
nonsupervised output relay that a panel automatically activates
when the FirstAlarm event occurs.
The NSCommonAlarmOn command only works on devices with
the NSCommonAlarmOutput device type. You are required to
specify the object label. Specifying a priority value is optional.
NSCommonAlarmOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
[NSCOMMON_ALARM_ON_SWITCHES]
SW 'NSCOM_ALARM_ON_LVL<N:1-10>':
NSCAON -LOW 'LVL<N>_NSCOM_ALARM_CKT*';
3.41
Output commands
NSCommonMonitorOff (NSCMOFF)
Use the NSCommonMonitorOff command to turn off a
nonsupervised output relay that a panel automatically activates
when the FirstMonitor event occurs.
The NSCommonMonitorOff command only works on devices
with the NSCommonMonitorOutput device type. You are
required to specify the object label. Specifying a priority value is
optional.
NSCommonMonitorOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
Notes
3.42
Output commands
NSCommonMonitorOn (NSCMON)
Use the NSCommonMonitorOn command to turn on a
nonsupervised output relay that a panel automatically activates
when the FirstMonitor event occurs.
The NSCommonMonitorOn command only works on devices
with the NSCommonMonitorOutput device type. You are
required to specify the object label. Specifying a priority value is
optional.
NSCommonMonitorOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
[COMMON_MON_ON_RESPONSE]
ALARM GENALARM:
CMON -LOW 'COM_MON_CKT_LVL*';
3.43
Output commands
NSCommonSupervisoryOff (NSCSOFF)
Use the NSCommonSupervisoryOff command to turn off a
nonsupervised output relay that a panel automatically activates
when the FirstSupervisory event occurs.
The NSCommonSupervisoryOff command only works on
devices with the NSCommonSupervisoryOutput device type.
You are required to specify the object label. Specifying a
priority value is optional.
NSCommonSupervisoryOff priority 'object_label';
Parameter
Description
priority
'object_label'
Notes
3.44
Output commands
NSCommonSupervisoryOn (NSCSON)
Use the NSCommonSupervisoryOn command to turn on a
nonsupervised output relay that a panel automatically activates
when the FirstSupervisory event occurs.
The NSCommonSupervisoryOn command only works on
devices with the NSCommonSupervisoryOutput device type.
You are required to specify the object label. Specifying a
priority value is optional.
NSCommonSupervisoryOn priority 'object_label';
Parameter
Description
priority
'object_label'
Example
[NSCOMMON_SUP_ON_SWITCHES]
SW 'NSCOM_SUP_ON_LVL<N:1-10>':
NSCSON -LOW 'LVL<N>_NSCOM_SUP_CKT*';
3.45
Output commands
NSCommonTroubleOff (NSCTOFF)
Use the NSCommonTroubleOff command to turn off a
nonsupervised output relay that a panel automatically activates
when the FirstTrouble event occurs.
The NSCommonTroubleOff command only works on devices
with the NSCommonTroubleOutput device type. You are
required to specify the object label. Specifying a priority value is
optional.
NSCommonTroubleOff priority 'object_label' ;
Parameter
Description
priority
'object_label'
Notes
3.46
Output commands
NSCommonTroubleOn (NSCTON)
Use the NSCommonTroubleOn command to turn on a
nonsupervised output relay that a panel automatically activates
when the FirstTrouble event occurs.
The NSCommonTroubleOn command only works on devices
with the NSCommonTroubleOutput device type. You are
required to specify the object label. Specifying a priority value is
optional.
NSCommonTroubleOn priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
[NSCOMMON_TRB_ON_SWITCHES]
SW 'NSCOM_TRB_ON_LVL<N:1-10>':
NSCTON -LOW 'LVL<N>_NSCOM_TRB_CKT*';
3.47
Output commands
Off
Use the Off command to turn a system hardware component,
circuit, or logic group off.
The Off command requires that you specify a device type or an
object label, or both. Specifying a priority value is optional.
Off priority device_type 'object_label' ;
Parameter
Description
priority
device_type
'object_label'
Example
{Turn off all horns in the building from
control/display module}
[REMOTE_HORN_OFF]
SW 'PANEL_1_SW1':
OFF -LOW AUD 'HORN*';
3.48
Output commands
OffGuard
Use the OffGuard command to cancel a specific guard patrol
tour. The OffGuard command contains two parts. The first part
of the command (OffGuard) identifies the GuardPatrol group
and the second part (Route) identifies the route number.
The OffGuard command only works on devices with the
GuardPatrol device type. You are required to specify the guard
label and the route identifier number.
OffGuard 'guard_label' Route route_id
Parameter
Description
'guard_label'
route_id
Example
{Deactivate individual guard patrol route from
remote panel toggle switch}
[GUARDPATROL_ROUTE_OFF]
SW 'PANEL_2_SW1':
OFFGUARD 'GUARD_PATROL_GROUP1' ROUTE 1;
3.49
Output commands
On
Use the On command to turn a system hardware component,
circuit, or logic group on.
The On command requires that you specify a device type or an
object label, or both. Specifying a priority value is optional.
On priority device_type 'object_label' ;
Parameter
Description
priority
device_type
'object_label'
Example
{Turn on all horns in the building from
control/display module}
[REMOTE_HORN_ON]
SW 'PANEL_1_SW2':
ON -HIGH AUD 'HORN*';
3.50
Output commands
OnGuard
Use the OnGuard command to start a specific guard patrol tour.
The OnGuard command contains two parts. The first part of the
command (OnGuard) identifies the GuardPatrol group and the
second part (Route) identifies the route number.
The OnGuard command only works on devices with the
GuardPatrol device type. You are required to specify the guard
label and the route identifier number.
OnGuard 'guard_label' Route route_id
Parameter
Description
'guard_label'
route_id
Example
{Activate guard patrol route from
control/display module switch }
[Group1GuardPatrolRoutesOn]
SW 'Panel_1_SW1':
OnGuard 'GUARD_PATROL_Group1' Route 1;
3.51
Output commands
Open
Use the Open command to turn on an output circuit or relay that
connects to the control mechanism used to open a damper.
The Open command only works on devices with the
DamperControl device type. You are required to specify the
object label. Specifying a priority value is optional.
Open priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.52
Output commands
ReleaseDoor (RELEASE)
Use the ReleaseDoor command to turn off an output circuit or
relay that connects to the control mechanism used to release a
door.
The ReleaseDoor command only works on devices with the
DoorControl device type. You are required to specify the object
label. Specifying a priority value is optional.
ReleaseDoor priority 'object_label' ;
Parameter
Description
priority
'object_label'
3.53
Output commands
RemoteAltSensitivityOff (RASOFF)
Use the RemoteAltSensitivityOff command to load the primary
sensitivity and alarm verification settings into every smoke
detector on selected panels or on a group of panels. Typically,
the primary settings are used during normal business hours when
the protected premises is occupied.
The RemoteAltSensitivityOff command only requires that you
specify a cabinet label or a routing label.
RemoteAltSensitivityOff 'cabinet_label' ;
or
RemoteAltSensitivityOff 'routing_label' ;
Parameter
Description
Note: Wildcards may be used in the cabinet label but not in the
routing label.
Example
{Automatically switch smoke detectors only on
Cab2 to primary sensitivity level during regular
work hours}
[PRIMARY_SENSITIVITY_CAB2]
TIME 'MON-FRI_REGULAR_HOURS':
RASOFF 'CAB_2';
3.54
Output commands
RemoteAltSensitivityOn (RASON)
Use the RemoteAltSensitivityOn command to load the alternate
sensitivity and alarm verification settings into every smoke
detector on selected panels or on a group of panels. Typically,
the alternate settings are used during normal business hours
when the protected premises is unoccupied.
The RemoteAltSensitivityOn command only requires that you
specify a cabinet label or a routing label.
RemoteAltSensitivityOn 'cabinet_label' ;
or
RemoteAltSensitivityOn 'routing_label' ;
Parameter
Description
Note: Wildcards may be used in the cabinet label but not in the
routing label.
Example
{Automatically switch smoke detectors to
alternate sensitivity level only on Cab2 during
non-regular work hours}
[ALTERNATE_SENSITIVITY_CAB2]
TIME 'MON-FRI_AFTER_HOURS':
RASON 'CAB_2';
3.55
Output commands
Reset
Use the Reset command to activate a panel's Reset function from
a control/display module switch. By programming a
control/display module switch to execute the Reset command, an
operator can reset the system from panels that do not contain a
3-LCD module.
The Reset command only requires that you specify a cabinet
label or a routing label.
Reset 'cabinet_label' ;
or
Reset 'routing_label' ;
Parameter
Description
Notes
3.56
Output commands
SlowBlink (SLOW)
Use the SlowBlink command to turn a light-emitting diode on a
control/display module on and off at a slow interval.
The SlowBlink command only works on devices with the LED
device type. You are required to specify the object label.
Specifying a priority value is optional.
SlowBlink priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
{Flash LED on control/display module to indicate
FirePhone device type is activated}
[ANN_RESET_2ND_PHASE]
R2:
SLOW -LOW 'R2_LED';
3.57
Output commands
Steady
Use the Steady command to turn a light-emitting diode on a
control/display module LED on and have it remain on.
The Steady command only works on devices with the LED
device type. You are required to specify the object label.
Specifying a priority value is optional.
Steady priority 'object_label' ;
Parameter
Description
priority
'object_label'
Example
{Light LED on control/display module to indicate
Firephone device type is activated}
[PHONE_CONNECT_REQ]
CALLIN:
STEADY -LOW 'DISPLAY_1_LED_1';
3.58
Output commands
TroubleSilence (TS)
Use the TroubleSilence command to activate a panel's Trouble
Silence function from a control/display module switch. By
programming a control/display module switch to execute the
TroubleSilence command, an operator can turn off a panel's
trouble buzzer from panels that do not contain a 3-LCD module.
The TroubleSilence command only requires that you specify a
cabinet label or a routing label.
TroubleSilence 'cabinet_label' ;
or
TroubleSilence 'routing_label' ;
Parameter
Description
3.59
Output commands
3.60
Appendix A
Quick reference
Summary
A.1
Quick reference
Acknowledge
Alarm
AlarmSilence
AlarmVerify
AllCall
An operator presses the All Call or All Call Minus switch on the
3-ASU
CallIn
Drill
Emergency
Evacuation
FirstAlarm
The first time that any point on a panel or any panel in the same
network routing group changes to the alarm state
FirstDisable
The first time that any point on a panel or any panel in the same
network routing group changes to the disabled state
FirstMonitor
The first time that any point on a panel or any panel in the same
network routing group changes to the monitor state
FirstSupervisory
The first time that any point on a panel or any panel in the same
network routing group changes to the supervisory state
FirstTrouble
The first time that any point on a panel or any panel in the same
network routing group changes to the trouble state
GroundFault
GuardPatrol
LocalAlarm
LocalMonitor
LocalTrouble
Monitor
R1
A.2
Quick reference
R2
R3
RelayConfirmation
Reset
Security
Service
ServiceGroup
ServiceGroupActive
SprinklerSupervisory
Startup
StationActivation
Supervisory
Switch
TimeControl
Trouble
TwoStageTimerActivation
TwoStageTimerExpiration
A.3
Quick reference
To do this
AlarmSilence
AlternateLanguage
Change the language that the 3-LCD uses to display text from a
control/display module momentary switch
AlternateMsgOff
AlternateMsgOn
AlternateSensitivityOff
AlternateSensitivityOn
AmpOff
AmpOn
Close
CommonAlarmOff
CommonAlarmOn
CommonMonitorOff
CommonMonitorOn
CommonSupervisoryOff
CommonSupervisoryOn
Delay
DelayActivate
A.4
Quick reference
To do this
DelayRestore
Disable
Drill
Enable
Evacuation
FanOff
FanOn
FastBlink
GAInhibit
HoldDoor
LampTest
LEDOff
MsgOff
MsgOn
NCClose
NCFanOff
NCFanOn
NCHoldDoor
A.5
Quick reference
To do this
NCOpen
NCReleaseDoor
NSCommonAlarmOff
NSCommonAlarmOn
NSCommonMonitorOff
NSCommonMonitorOn
NSCommonSupervisoryOff
NSCommonSupervisoryOn
NSCommonTroubleOff
NSCommonTroubleOn
Off
OffGuard
On
OnGuard
Open
ReleaseDoor
RemoteAltSensitivityOff
RemoteAltSensitivityOn
Reset
SlowBlink
A.6
Quick reference
To do this
Steady
TroubleSilence
12SW/12LED
(12S12L)
none
Disable, Enable
12SW/24LED
(12S24L)
none
Disable, Enable
24LED
(24L)
none
Disable, Enable
3-AADC
(AADC)
none
Disable, Enable
3-ASU
(ASU)
none
Disable, Enable
3-DSDC
(DSDC)
none
Disable, Enable
3-FTCU
(FTCU)
none
Disable, Enable
3-IDC8/4
(IDC)
none
Disable, Enable
3-OPS
(OPS)
none
Disable, Enable
3SW/3LEDX6
(3S3L6)
none
Disable, Enable
AlarmSilence
(AS)
none
none
AlternateLanguage
(ALTL)
none
none
AlternateMsg
(ALTM)
none
none
AlternateSensitivity
(ALTS)
none
none
Amp
none
A.7
Quick reference
And
Acknowledge, Alarm,
Monitor, Supervisory, Trouble
Disable, Enable
Audible
(AUD)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
CheckIn
(CIG)
none
CommFailure
(CFAIL)
Acknowledge, Trouble
none
CommonAlarmOutput
(CAO)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
CommonMonitorOutput
(CMO)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
CommonSupervisoryOutput
(CSO)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
DamperControl
(DAMP)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
DamperFeedback
(DAMPFB)
Acknowledge, Monitor,
ServiceDevice, Trouble
Disable, Enable
DoorControl
(DOOR)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
DoorFeedback
(DOORFB)
Acknowledge, Monitor,
ServiceDevice, Trouble
Disable, Enable
Drill
none
none
Emergency
(EMER)
Acknowledge, Emergency,
ServiceDevice, Trouble
Disable, Enable
Evacuation
(EVAC)
none
none
ExtDBIncompatibility
(EXTDBIN)
Acknowledge, Trouble
none
Failsafe
(FSAFE)
none
A.8
Quick reference
FanControl
(FAN)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
FanFeedback
(FANFB)
Acknowledge, Monitor,
ServiceDevice, Trouble
Disable, Enable
Firephone
(FP)
Acknowledge, CallIn,
RelayConfirmation,
ServiceDevice, Trouble
GAInhibit
(GAIN)
none
none
Gatevalve
(GATE)
Acknowledge, ServiceDevice,
SprinklerSupervisory,
Supervisory, Trouble
Disable, Enable
GenAlarm
(GENA)
Acknowledge, Alarm,
MaintenanceAlert,
ServiceDevice, Trouble
Disable, Enable
GenSmoke
(GENS)
Acknowledge, Alarm,
AlarmVerify,
MaintenanceAlert,
ServiceDevice, Trouble
Disable, Enable
GroundFault
(GNDF)
Acknowledge, GroundFault
none
Guard
Acknowledge, ServiceDevice,
StationActivation, Trouble
Disable, Enable
GuardPatrol
(GPG)
Acknowledge, GuardPatrol
Heat
Acknowledge, Alarm,
ServiceDevice, Trouble
Disable, Enable
LampTest
(LAMP)
none
none
LED
none
LocalAlarm
(LALM)
Acknowledge, LocalAlarm
Disable, Enable
LocalMonitor
(LMON)
Acknowledge, LocalMonitor
Disable, Enable
LocalRelay
(LRLY)
Acknowledge,
RelayConfirmation
Disable, Enable
A.9
Quick reference
LocalTrouble
(LTRB)
Acknowledge, LocalTrouble
Disable, Enable
LoopControllerResetExt
(LCREXT)
Acknowledge, Trouble
none
Matrix
Acknowledge, Alarm,
Monitor, Supervisory, Trouble
Disable, Enable
Monitor
(MON)
Acknowledge, Monitor,
ServiceDevice, Trouble
Disable, Enable
MSG
none
none
NonsupervisedOutput
(NSO)
Acknowledge,
RelayConfirmation
NSCommonAlarmOutput
(NSCAO)
Acknowledge, Trouble
NSCommonMonitorOutput
(NSCMO)
Acknowledge, Trouble
NSCommonSupervisoryOutput
(NSCSO)
Acknowledge, Trouble
NSCommonTroubleOutput
(NSCTO)
Acknowledge, Trouble
PanelCommFault
(PCF)
Acknowledge, Trouble
none
Power
Acknowledge, ServiceDevice,
SprinklerSupervisory,
Supervisory, Trouble
none
POWER
(POFF)
none
Disable, Enable
Pull
Acknowledge, Alarm,
ServiceDevice, Trouble
Disable, Enable
RebootFault
(RBF)
Acknowledge, Trouble
none
Security
(SEC)
Acknowledge, Security,
ServiceDevice, Trouble
Disable, Enable
A.10
Quick reference
ServiceDeviceSupervision
(SERVSUP)
Acknowledge, Trouble
none
ServiceGroup
(SG)
Acknowledge, ServiceGroup
Off, On
ServiceGroupActive
(SGA)
Acknowledge,
ServiceGroupActive
none
Smoke
(SMK)
Acknowledge, Alarm,
MaintenanceAlert,
ServiceDevice, Trouble
Disable, Enable
SmokeVfy
(VFY)
Acknowledge, Alarm,
AlarmVerify,
MaintenanceAlert,
ServiceDevice, Trouble
Disable, Enable
SprinklerSupervisory
(SPSUP)
Acknowledge, ServiceDevice,
SprinklerSupervisory,
Supervisory, Trouble
Disable, Enable
StageOne
(STAGE1)
Acknowledge, Alarm,
ServiceDevice, Trouble
Disable, Enable
StageTwo
(STAGE2)
Acknowledge, Alarm,
ServiceDevice, Trouble
Disable, Enable
SupervisedOutput
(SUP)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
Supervisory
(SUP)
Acknowledge, ServiceDevice,
Supervisory, Trouble
Disable, Enable
Switch
(SW)
Acknowledge, Switch
Disable, Enable
Tamper
(TAMP)
Acknowledge, ServiceDevice,
SprinklerSupervisory,
Supervisory, Trouble
Disable, Enable
TaskFailure
(TFAIL)
Acknowledge, Trouble
none
Temperature
(TEMP)
Acknowledge, ServiceDevice,
SprinklerSupervisory,
Supervisory, Trouble
Disable, Enable
Text
none
Disable, Enable
TimeControl
(TIME)
TimeControl
Disable, Enable
TroubleSilence
(TS)
none
none
A.11
Quick reference
TwoStageTimerActive
(2STAGEA)
Acknowledge,
TwoStageTimerActive
none
TwoStageTimerExpiration
(2STAGETO)
Acknowledge,
TwoStageTimerExpiration
none
UserTrouble
(USRTRB)
Acknowledge, Trouble
none
Visible
(VIS)
Acknowledge,
RelayConfirmation,
ServiceDevice, Trouble
Waterflow
(FLOW)
Acknowledge, Alarm,
ServiceDevice, Trouble
Disable, Enable
Zone
Disable, Enable
A.12
Glossary
12SW/12LED device type
Classification used for a control/display module with 24 lightemitting diodes. Abbreviation: 24L.
Acknowledge event
activation number
active state
active project
Alarm event
AlarmSilence command
AlarmSilence event
AlarmVerify event
Y.1
Glossary
AllCall event
AlternateLanguage
command
AlternateMsgOff command
AlternateMsgOn command
AlternateSensitivityOff
command
AlternateSensitivityOn
command
AmpOff command
AmpOn command
And group
application code
Program file that controls the way a rail module performs firerelated functions.
bootloader code
bus
cabinet number
CallIn event
CardDBIncompat device
type
Y.2
Glossary
Close command
COM port
CommonAlarmOff command
CommonAlarmOn command
CommonAlarmOutput device
type
CommonMonitorOff
command
CommonMonitorOn
command
CommonMonitorOutput
device type
CommonSupervisoryOff
command
CommonSupervisoryOn
command
CommonSupervisoryOutput
device type
DamperFeedback device
type
Y.3
Glossary
deenergize
Delay command
DelayActivate command
DelayRestore command
device type
Disable command
download
Drill command
Drill event
Emergency event
Enable command
Y.4
Glossary
energize
Evacuation command
Evacuation event
event
ExtDBIncompatibility
FanOff command
FanOn command
FastBlink command
FirstAlarm event
Y.5
Glossary
FirstDisable event
FirstMonitor event
FirstSupervisory event
FirstTrouble event
GAInhibit command
GenSmoke
GroundFault event
GuardPatrol event
Y.6
Glossary
HoldDoor command
label
LampTest command
LED
LEDOff command
local
local panel
LocalAlarm event
LocalMonitor event
LocalTrouble event
logic group
LoopControllerResetExt
device type
mechanism
Y.7
Glossary
Monitor event
MsgOff command
MsgOn command
NCClose command
NCFanOff command
NCFanOn command
NCHoldDoor command
NCOpen command
NCReleaseDoor command
NonsupervisedOutput
device type
nonactive
normal state
notification appliance
NSCommonAlarmOff
command
NSCommonAlarmOn
command
NSCommonAlarmOutput
device type
NSCommonMonitorOff
command
Y.8
Glossary
NSCommonMonitorOn
command
NSCommonMonitorOutput
device type
NSCommonSupervisoryOff
command
NSCommonSupervisoryOn
NSCommonSupervisoryOutp
ut device type
NSCommonTroubleOff
command
NSCommonTroubleOn
command
NSCommonTroubleOutput
device type
n-variable
object
Off command
OffGuard command
On command
OnGuard command
Open command
pseudo point
Y.9
Glossary
R1 device type
R1 event
Event produced when the first phase of the 3-phase reset cycle
starts.
R2 device type
R2 event
R3 device type
R3 event
rail location
rail-slot position
RelayConfirmation event
ReleaseDoor command
remote panel
RemoteAltSensitivityOff
command
RemoteAltSensitivityOn
command
Reset command
Reset event
Y.10
Glossary
rule
SDU database
search radius
Specific area within a matrix grid that the system looks for a
second detector to go into alarm before generating a group
response. The search radius is centered around the first
detector to go into alarm and its size is determined by a radius
number setting.
Security event
ServiceDevice event
ServiceDeviceSupervision
device type
ServiceGroup event
ServiceGroupActive device
type
ServiceGroupActive event
SlowBlink command
SprinklerSupervisory device
type
SprinklerSupervisory event
Y.11
Glossary
Classification used for the second address (alarm stage) of a 2stage pull station. Abbreviation: STAGE2.
Startup event
StationActivation event
Steady command
SupervisedOutput device
type
Supervisory event
Switch event
TimeControl event
Trouble event
TroubleSilence command
Y.12
Glossary
TwoStageTimerActivation
event
TwoStageTimerActive device
type
TwoStageTimerExpiration
device type
TwoStageTimerExpiration
event
upload
Y.13
Glossary
Y.14
Index
2
24LED device type 3.21, 3.23
3
3-AADC device type 3.21, 3.23
3-ASU device type 3.21, 3.23
3-DSDC device type 3.21, 3.23
3-FTCU device type 3.21, 3.23
3-IDC8/4 device type 3.21, 3.23
3-OPS device type 3.21, 3.23
3SW/3LEDX6 device type 3.21, 3.23
A
About the Systems Definition Utility 1.2
Acknowledge event 2.2
Alarm event 2.3
Alarm logic groups 1.28
AlarmSilence command 3.3
AlarmSilence event 2.4
AlarmVerify event 2.5
AllCall event 2.6
AlternateLanguage command 3.4
AlternateMsgOff command 3.5
AlternateMsgOn command 3.6
AlternateSensitivityOff command 3.7
AlternateSensitivityOn command 3.8
Amp device type 3.21, 3.23
AmpOff command 3.9
AmpOn command 3.10
And device type 2.2, 2.3, 2.21, 2.34, 2.37,
3.21, 3.23
AND Group description 1.29
Audible device type 2.2, 2.25, 2.28, 2.37,
3.21, 3.23, 3.48, 3.50
B
Bar code readers 1.3
D
DamperControl device type 2.2, 2.25, 2.28,
2.37, 3.21, 3.23, 3.48, 3.50
DamperFeedback device type 2.2, 2.21,
2.28, 2.37, 3.21, 3.23
Delay command 3.18
DelayActivate command 3.19
DelayRestore command 3.20
Device types 1.7
used with And groups 1.29
used with Instruction Text groups 1.32
used with Service groups 1.34
used with Zone groups 1.32
Disable command 3.21
DoorControl device type 2.2, 2.25, 2.28,
2.37, 3.21, 3.23, 3.48, 3.50
DoorFeedback device type 2.2, 2.21, 2.28,
2.37, 3.21, 3.23
Drill command 3.22
Drill event 2.8
Z.1
Index
F
Failsafe device type 2.2, 2.3, 2.37
FanControl device type 2.2, 2.25, 2.28,
2.37, 3.21, 3.23, 3.48, 3.50
FanFeedback device type 2.2, 2.21, 2.28,
2.37, 3.21, 3.23
FanOff command 3.25
FanOn command 3.26
FastBlink command 3.27
FCC warning iv
Firephone device type 2.2, 2.7, 2.25, 2.28,
2.37, 3.21, 3.23, 3.48, 3.50
FirstAlarm event 2.11
FirstDisable event 2.12
FirstMonitor event 2.13
FirstSupervisory event 2.14
FirstTrouble event 2.15
G
GAInhibit command 3.28
Gatevalve device type 2.2, 2.28, 2.31, 2.34,
2.37, 3.21, 3.23
GenAlarm device type 2.2, 2.3, 2.28, 2.37,
3.21, 3.23
GenSmoke device type 2.2, 2.3, 2.5, 2.28,
2.37, 3.21, 3.23
GroundFault device type 2.2, 2.16
GroundFault event 2.16
Guard device type 2.2, 2.28, 2.33, 2.37,
3.21, 3.23
Guard Patrol Group description 1.33
Guard Patrol logic groups 1.28
GuardPatrol device type 2.2, 2.17, 3.21,
3.23
GuardPatrol event 2.17
H
Heat device type 2.2, 2.3, 2.28, 2.37, 3.21,
3.23
HoldDoor command 3.29
L
Label modifiers
used in numberless floors 1.15
used in vertical applications 1.16
used to describe device type 1.14
used to describe function 1.14
used to describe location 1.14
using as message 1.17
using numbers to make unique 1.17
Labeling plan
developing 1.13
important considerations 1.13
Labels
characteristics of 1.8
formatting 1.13
making descriptive 1.14
using as the message 1.17
using common modifiers 1.15
using numbers in 1.17
LampTest command 3.30
Latch priority description 1.22
LED device type 3.21, 3.23, 3.48, 3.50
LEDOff command 3.31
Limitation of liability iv
LocalAlarm device type 2.2, 2.18, 3.21,
3.23
LocalAlarm event 2.18
LocalMonitor device type 2.2, 2.19, 3.21,
3.23
LocalMonitor event 2.19
LocalRelay device type 2.2, 2.25, 3.21,
3.23
LocalTrouble device type 2.2, 2.20, 3.21,
3.23
LocalTrouble event 2.20
Logic group parameters 1.28
Logic group types 1.28
LoopControllerResetExt device type 2.2,
2.37
M
Mathematical operators 1.26
Matrix device type 2.2, 2.3, 2.21, 2.34,
2.37, 3.21, 3.23
Matrix group
activation number setting 1.31
radius setting 1.31
Z.2
Index
Matrix Group description 1.30
Minimum equipment required 1.2
Monitor device type 2.2, 2.21, 2.28, 2.37,
3.21, 3.23
Monitor event 2.21
MsgOff command 3.32
MsgOn command 3.33
N
National Fire Protection Association vii
NCClose command 3.34
NCFanOff command 3.35
NCFanOn command 3.36
NCHoldDoor command 3.37
NCOpen command 3.38
NCReleaseDoor command 3.39
Nonalarm logic groups 1.28
NonsupervisedOutput device type 2.25,
3.21, 3.23, 3.48, 3.50
NSCommonAlarmOff command 3.40
NSCommonAlarmOn command 3.41
NSCommonAlarmOutput device type 2.2,
2.37, 3.21, 3.23, 3.48, 3.50
NSCommonMonitorOff command 3.42
NSCommonMonitorOn command 3.43
NSCommonMonitorOutput device type 2.2,
2.37, 3.21, 3.23, 3.48, 3.50
NSCommonSupervisoryOff command 3.44
NSCommonSupervisoryOn command 3.45
NSCommonSupervisoryOutput device type
2.2, 2.37, 3.21, 3.23, 3.48, 3.50
NSCommonTroubleOff command 3.46
NSCommonTroubleOn command 3.47
NSCommonTroubleOutput device type 2.2,
2.37, 3.21, 3.23, 3.48, 3.50
N-variables 1.25
O
Objects 1.7
identifying functions in a system 1.18
Off command 3.48
OffGuard command 3.49
On command 3.50
OnGuard command 3.51
Open command 3.52
Optional equipment 1.3
Output statement syntax 1.5
P
PanelCommFault device type 2.2, 2.37
Power device type 2.2, 2.28, 2.31, 2.34,
2.37, 3.21, 3.23
Priorities 1.21
Programming
advanced techniques 1.25
Pull device type 2.2, 2.3, 2.28, 2.37, 3.21,
3.23
R
R1 event 2.22
R2 event 2.23
R3 event 2.24
RebootFault device type 2.37
RelayConfirmation event 2.25
ReleaseDoor command 3.53
RemoteAltSensitivityOff command 3.54
RemoteAltSensitivityOn command 3.55
Reset command 3.56
Reset event 2.26
Rule syntax 1.4
Rules
32K limit 1.9
factors affecting compile speed 1.12
S
Security device type 2.2, 2.27, 2.28, 2.37,
3.21, 3.23
Security event 2.27
Service Group description 1.34
Service logic groups 1.28
ServiceDevice event 2.28
ServiceDeviceSupervision device type 2.2,
2.37
ServiceGroup device type 2.2, 2.29, 3.48,
3.50
ServiceGroup event 2.29
ServiceGroupActive device type 2.2
ServiceGroupActive event 2.30
SlowBlink command 3.57
Smoke device type 2.2, 2.3, 2.28, 2.37,
3.21, 3.23
SmokeVfy device type 2.2, 2.3, 2.5, 2.28,
2.37, 3.21, 3.23
Sound cards 1.3
SprinklerSupervisory device type 2.2, 2.28,
2.31, 2.34, 2.37, 3.21, 3.23
SprinklerSupervisory event 2.31
StageOne device type 2.2, 2.3, 2.28, 2.37,
3.21, 3.23
StageTwo device type 2.2, 2.3, 2.28, 2.37,
3.21, 3.23
Startup event 2.32
StationActivation event 2.33
Steady command 3.58
SupervisedOutput device type 2.25, 2.28,
2.37, 3.21, 3.23, 3.48, 3.50
Z.3
Index
Supervisory device type 2.28, 2.34, 2.37,
3.21, 3.23
Supervisory event 2.34
Switch device type 2.35, 3.21, 3.23
Switch event 2.35
W
Waterflow device type 2.2, 2.3, 2.28, 2.37,
3.21, 3.23
Wildcards 1.10, 1.25
Z
Zone device type 2.2, 2.3, 2.37, 3.21, 3.23
Zone Group description 1.32
Z.4