P/N 06-237480-001

April 2018
Revision AA

ARIES®-MLX
Configuration Tool

User’s Guide

EXPORT INFORMATION (USA):

Jurisdiction: EAR
Classification: EAR99
This document contains technical data subject to the EAR.
 FOREWORD
Note: This Manual, P/N 06-237480-001, is to be used by qualified and factory-trained personnel, knowledgeable
of NFPA standards and any other applicable standards in effect.
This Manual is intended to clearly and accurately describe how to use the ARIES®-MLX Configuration Tool (ACT-
MLX).
Kidde-Fenwal assumes no responsibility for the application of any systems other than those addressed in this
manual. The technical data contained herein is provided for informational purposes only, and should not be used
as a substitute for professional judgment. Although Kidde-Fenwal, Inc. believes this information to be true and
correct, it is published and presented without any guarantee or warranty whatsoever. Kidde-Fenwal, Inc. disclaims
any liability for any use of the data other than as set out in this manual, Foreword included.
Any questions concerning the information presented in this manual should be addressed to:
Kidde-Fenwal, Inc.
400 Main Street
Ashland, MA 01721
Phone: (508) 881-2000
Toll Free: (800) 872-6527
Fax: (508) 881-8920

P/N 06-237480-001 i April 2018

 TERMS AND ABBREVIATIONS

AAM: Addressable Alarmline Module MEA: Materials and Equipment Acceptance

Division of the City of New York
AC: Alternating Current NAC: Notification Appliance Circuit
ACT8000 ARIES NETLink Configuration Tool N.C.: Normally Closed
ACT-MLX ARIES-MLX Configuration Tool NEC: National Electrical Code
ADA: Americans with Disabilities Act NFPA: National Fire Protection Association
AH: Ampere Hour N.O.: Normally Open
AHJ: Authority Having Jurisdiction PALM PEGAsys Addressable Loop Module
AI: Addressable Monitor Module PAS: Positive Alarm Sequence

AO: Addressable Relay PCB: Printed Circuit Board

ASM Addressable Signal Module pF: Pico-farads
AV: Alarm Verification PMU: Power Management Unit
AWG: American Wire Gauge P/N: Part Number
BPM: Beats per Minute RAM: Random Access Memory
CPU: Central Processing Unit RDCM: Remote Display Control Module
CSFM: California State Fire Marshal RF: Radio-Frequency
DC: Direct Current R-NAC Release/NAC
EOC: Event Output Control RRM Remote Releasing Module
EOLD: End of Line Device SLC: Signaling Line Circuit
FM/FMRC: Factory Mutual (Research Corporation) SMPS: Switching Mode Power Supply
Ft.: Feet TB: Terminal Block
GAAL: General Alarm Activation List UI User Interface
HSD High Sensitivity Detector UL/ULI: Underwriters Laboratories, Inc.
HSSD High Sensitivity Smoke Detector V: Volts
Hz: Hertz (Frequency) Vac: Volts AC
IRI: Industrial Risk Insurers Vdc: Volts DC
LAM: LED Annunciator Module VRMS: Volts Root Mean Square
LCD: Liquid Crystal Display
LED: Light Emitting Diode
ADA: Americans with Disabilities Act
AH: Ampere Hour
AHJ: Authority Having Jurisdiction

April 2018 ii P/N 06-237480-001

 SAFETY SUMMARY
This entire manual must be read and understood before installation.
Installation Precautions Adherence to the following will aid in problem-free installation with long-term
reliability:

WARNING Several different sources of power can be connected to this fire alarm control unit.
Disconnect all sources of power before servicing. Control unit and associated equipment
may be damaged by servicing while the unit is energized. Do not attempt to install,
service, or operate this control unit until this manual is read and understood.

System Re-acceptance Test after Re-Programming: To ensure proper system operation, this
system must be retested in accordance with NFPA 72 Chapter 10 after any programming
CAUTION
change. Re-acceptance testing is also required after any addition or deletion of system
components, and after any modification, repair or adjustment to system hardware or wiring.
All components, circuits and system operations known to be affected by a change must be
100% tested. In addition, to ensure that other operations are not inadvertently affected, at least
10% of initiating devices that are not directly affected by the change, up to a maximum of 50
devices, must also be tested and proper system operation verified.

CAUTIONS AND WARNINGS

A caution identifies a procedure, practice, or statement, which, if not strictly followed, could
result in programming errors, impairment of equipment operation, or equipment damage.
CAUTION

A warning identifies an operating or maintenance procedure, practice, condition or

statement, which, if not strictly followed, could result in personal injury or death.
WARNING

P/N 06-237480-001 iii April 2018

 NOTICE TO USERS, INSTALLERS, AUTHORITIES HAVING JURISDICTION AND ALL OTHER INVOLVED
PARTIES

This product incorporates field-programmable software. In order for the product to comply with the
requirements in the Standard for Control Units and Accessories for Fire Alarm Systems, UL 864, certain
programming features or options must be limited to specific values or not used at all as indicated below:

Program Feature or Option Permitted in Possible Settings Settings Permitted in

UL 864(Y/N) UL 864
Ionization Detectors reporting as N 0.5 – 1.5% per foot Report as alarm initiating
supervisory initiating devices devices only
Photoelectric Detectors reporting as No 0.5 – 3.5% per foot Report as alarm initiating
supervisory initiating devices (PSD-7152 detector) devices only
or
0.9 - 3.5% per foot
(DS-PS detector)
Delay Operator D() Yes 1 - 3600 seconds 1 - 60 seconds
Abort switches may be set up to Y (#2 only) 1 – 300 second delay 1 – 60 second delay
operate in any of the following ways:
1. Reset to initial delay setting.
Resume countdown for entire
delay period.
2. Count down to 10 seconds and
hold. Resume countdown at 10
seconds.
3. Hold at time remaining. Resume
countdown at remaining time
period.
4. Same as #2, except disable
abort function if countdown
timer has started.
5. Special New York City operation.
Delayed off premises trouble trans- Y 0 – 12 hours 0 – 3 hours
missions for AC power loss.
Monitor module acting as a silence Yes May be used as a stand Must have visible indication
switch. alone initiating device, or at monitor module that out-
may be used with visible puts have been silenced.
indication that shows when
outputs are silenced.
Monitor module acting as an Yes May be used as a stand Must have visible display at
acknowledge switch. alone initiating device, or monitor module that shows
may be used with a display what is being acknowledged.
that shows when events are
being acknowledged.
PALM reporting as supervisory No N/A Report as alarm initiating
device device only.
Configuring a control unit that is No Resettable or Non-resettable If configured for non-resetta-
part of a network system as non- via the network ble, the control unit must be
resettable via the network. (section 2-7.8) in a different group and
must be configured to not
‘log All Events’

April 2018 iv P/N 06-237480-001

 TABLE OF CONTENTS
Foreword ............................................................................................................................ i
Terms and Abbreviations ................................................................................................... ii
Safety Summary ................................................................................................................. iii
Table of Contents................................................................................................................ v
List of Figures..................................................................................................................... xi
List of Tables ...................................................................................................................... xv

CHAPTER 1 GENERAL INFORMATION

1-1 Introduction............................................................................................................ 1-1
1-2 PC Requirements .................................................................................................... 1-1
1-3 Installing the Configuration Software Launcher and the ACT-MLX Software........... 1-1
1-4 Starting ACT-MLX................................................................................................... 1-4
1-5 Installing the USB Driver for Connection to Control Unit........................................ 1-7
1-5.1 Installing USB Drivers for ACT-MLX on Microsoft Windows XP, 7, 8.1 or 10 ......... 1-7
1-5.2 Verifying the Installation of the USB Drivers ........................................................... 1-8
1-5.3 Un-installing the USB Driver................................................................................... 1-8
1-5.4 Digital Signature Check on Windows 8.1 or 10 ....................................................... 1-8

CHAPTER 2 CREATING A SYSTEM CONFIGURATION

2-1 Introduction............................................................................................................ 2-1
2-2 Before You Begin - Version Compatibility................................................................ 2-1
2-3 The Main Toolbar ................................................................................................... 2-1
2-4 The Side Toolbar .................................................................................................... 2-2
2-5 Drop-Down Menus .................................................................................................. 2-2
2-5.1 The FILE Drop-Down Menu .................................................................................... 2-3
2-5.2 The EDIT Drop-Down Menu ................................................................................... 2-4
2-5.3 The VIEW Drop-Down Menu ................................................................................... 2-4
2-5.4 The TOOLS Drop-Down Menu ................................................................................ 2-5
2-5.5 The WINDOW Drop-Down Menu ............................................................................. 2-6
2-5.6 The HELP Drop-Down Menu................................................................................... 2-6
2-6 Creating a New Configuration file............................................................................ 2-6
2-7 Opening an Existing Configuration File ................................................................... 2-6
2-8 The Configuration Editor ........................................................................................ 2-7
2-8.1 The <Apply> Button .............................................................................................. 2-7
2-8.2 The <Reset> Button............................................................................................... 2-7
2-8.3 The SUMMARY Tab ................................................................................................ 2-8
2-8.4 The SLC and EXPANSION I/O Tab.......................................................................... 2-9
2-8.5 Adding and Configuring a New Module ................................................................... 2-10
2-8.5.1 Adding and Configuring a City-Tie Module.............................................................. 2-11
2-8.5.2 Adding A Relay Module ........................................................................................... 2-12
2-8.5.2.1 Configuring a Relay Circuit ..................................................................................... 2-13
2-8.5.2.2 Relay Circuit Configuration Screen ......................................................................... 2-13
2-8.5.3 Adding and Configuring an SLC Module ................................................................. 2-14
2-8.5.4 Adding And Configuring A Network Interface Card ................................................. 2-15
2-8.5.5 Adding And Configuring A Power Management Unit (PMU) Module ........................ 2-17
2-8.5.6 Adding an R-NAC Module ....................................................................................... 2-18
2-8.5.6.1 Configuring An R-NAC Module as NAC or Release Circuit....................................... 2-19
2-8.5.6.2 Release/NAC Module (R-NAC) as a NAC (Notification Appliance Circuit)
Configuration Screen .............................................................................................. 2-20

P/N 06-237480-001 v April 2018

 TABLE OF CONTENTS (CONT.)
2-8.5.6.3 Release/NAC Module (R-NAC) as a Release Circuit Configuration Screen ................2-22
2-8.5.7 Adding And Configuring A DACT Module ................................................................2-23
2-8.5.8 Editing a Module .....................................................................................................2-24
2-8.6 The EOC (EVENT OUTPUT CONTROL) Tab ...........................................................2-25
2-8.7 The ON-BOARD Tab................................................................................................2-26
2-8.7.1 Configuring an On-Board Circuit.............................................................................2-27
2-8.7.2 Disabling a Circuit...................................................................................................2-28
2-8.7.3 Notification Appliance Circuit (NAC) Configuration Screen......................................2-28
2-8.7.4 R-NAC Circuit As A NAC Device Configuration Screen.............................................2-29
2-8.7.5 R-NAC Circuit As A Release Device Configuration Screen ........................................2-30
2-8.7.6 Relay Circuit Configuration Screen..........................................................................2-32
2-8.8 The DAY/NIGHT/WEEKEND Tab.............................................................................2-34
2-8.9 The DISPLAY Tab....................................................................................................2-35
2-8.9.1 Adding a Remote Display Control Module (RDCM)..................................................2-36
2-8.9.2 Adding an LED Annunciator Module (LAM).............................................................2-37
2-8.9.3 Adding an ATM Component ....................................................................................2-39
2-8.9.4 Deleting a Module....................................................................................................2-40
2-8.9.5 Editing Owner Location...........................................................................................2-40
2-8.9.6 Designating an RDCM Module as a Master ..............................................................2-41
2-8.9.7 Deselecting an RDCM as a Master ...........................................................................2-41
2-8.10 The IIM (INTELLIGENT INTERFACE MODULE) Tab..............................................2-42
2-8.10.1 Configuring IIM Tab Options ...................................................................................2-43
2-8.10.2 Adding an HSD........................................................................................................2-43
2-8.10.3 Deleting An HSD......................................................................................................2-44
2-8.11 The STRINGS Tab...................................................................................................2-44
2-8.12 The GLOBAL Tab ....................................................................................................2-46
2-8.12.1 Changing Timing Options ........................................................................................2-49
2-8.12.2 Creating Isolation Macros........................................................................................2-51
2-8.13 The SOFTKEYS Tab................................................................................................2-54
2-8.13.1 Programming Softkeys ............................................................................................2-55
2-8.14 The CALL FOR SERVICE Tab .................................................................................2-56
2-8.15 The RELEASE GROUP Tab.....................................................................................2-57
2-8.16 The OUTPUT GROUP Tab.......................................................................................2-58

CHAPTER 3 CONFIGURING SLC DEVICES

3-1 Introduction ............................................................................................................3-1
3-2 SLC and EXPANSION I/O Tab .................................................................................3-1
3-3 Adding an SLC Module (Circuit)..............................................................................3-2
3-4 Adding SLC Devices to an SLC Module (Circuit) .....................................................3-3
3-4.1 Editing the Configuration of an SLC Device .............................................................3-6
3-4.2 Editing the Owner Location of an SLC Device..........................................................3-6
3-4.3 Editing the Address of an SLC Device .....................................................................3-7
3-4.4 Editing the Type of an SLC Device...........................................................................3-7
3-5 Settings for SLC Devices..........................................................................................3-8
3-5.1 Addressable AlarmLine Module (AAM) Settings Screen ...........................................3-9
3-5.2 Addressable Relay Settings (AO) Screen ..................................................................3-10
3-5.3 Addressable Sounder Module (ASM) Settings Screen ..............................................3-11

April 2018 vi P/N 06-237480-001

 TABLE OF CONTENTS (CONT.)
3-5.4 Ion Smoke Detector (ION) Settings Screen.............................................................. 3-12
3-5.4.1 Application Definitions via Drop-Down Menu ......................................................... 3-13
3-5.5 Model PSD-7152 Photoelectric Smoke Detector (PHOTO) Settings Screen ............. 3-13
3-5.5.1 Application Definitions via Drop-Down Menu ......................................................... 3-14
3-5.6 Model DS-PS Photoelectric Smoke Detector (PHOTO) Settings Screen ................... 3-15
3-5.6.1 Application Definitions via Drop-Down Menu ......................................................... 3-16
3-5.7 Heat Detector (THERMAL) (Model THD-7252) Settings Screen............................... 3-17
3-5.8 Heat Detector (THERMAL) (Model DS-HFS) Settings Screen .................................. 3-18
3-5.9 Heat Detector Thermal Cycling ............................................................................... 3-19
3-5.10 PEGAsys Addressable Loop Module (PALM) Settings Screen .................................. 3-20
3-5.11 Alarm (ALARM) Settings Screen ............................................................................. 3-21
3-5.12 Abort Station (ABORT) Settings Screen .................................................................. 3-21
3-5.12.1 Abort Station Settings Definitions ........................................................................... 3-22
3-5.13 Supervisory Input (SUPV) Settings Screen .............................................................. 3-23
3-5.14 Waterflow Input (WATER) Settings Screen .............................................................. 3-24
3-5.15 Remote Releasing Module (RRM) Settings Screen ................................................... 3-24
3-5.15.1 Configuring an RRM with an Initiator Releasing Device........................................... 3-26
3-5.15.2 Configuring an RRM with a Solenoid Releasing Device............................................ 3-27
3-5.16 Configuring An Isolation Macro Input ..................................................................... 3-29
3-6 Other SLC Initiating Devices ................................................................................... 3-30

CHAPTER 4 EVENT OUTPUT CONTROL (EOC)

4-1 Introduction............................................................................................................ 4-1
4-1.1 Before You Begin..................................................................................................... 4-1
4-1.2 Event Output Control.............................................................................................. 4-1
4-2 Constructing Arguments ......................................................................................... 4-1
4-2.1 Simple Arguments .................................................................................................. 4-4
4-2.2 Compound Arguments ............................................................................................ 4-4
4-2.2.1 “And” Operator ....................................................................................................... 4-5
4-3 Outputs................................................................................................................... 4-6
4-3.1 Physical Outputs ..................................................................................................... 4-6
4-3.2 Virtual Outputs ....................................................................................................... 4-7
4-3.2.1 Counting Identifiers (Ix) .......................................................................................... 4-7
4-3.2.2 State Variable (Cx) .................................................................................................. 4-8
4-3.2.3 Incrementing Variable (Qx) ..................................................................................... 4-10
4-4 Multiple Outputs..................................................................................................... 4-11
4-5 The "NOT" Operator................................................................................................ 4-11
4-6 Functions................................................................................................................ 4-11
4-6.1 Alarm Threshold Adjustment Function (Smoke Detectors Only)............................. 4-11
4-6.2 Pre-Alarm Threshold Adjustment Function (Smoke Detectors Only) ...................... 4-12
4-6.3 Delayed Output Activation Function (without explicit Abort Interruption)............... 4-12
4-6.4 Delayed Output Activation Function (with explicit Abort Interruption).................... 4-13
4-6.5 Trouble Function for Initiating Devices ................................................................... 4-13
4-6.6 General Trouble Function....................................................................................... 4-14
4-6.7 General Supervisory Function ................................................................................ 4-14
4-6.8 General Alarm Function.......................................................................................... 4-14
4-6.9 Pre-Alarm Function for Initiating Devices ............................................................... 4-14

P/N 06-237480-001 vii April 2018

 TABLE OF CONTENTS (CONT.)
4-6.10 Warning Function for AnaLASER-II or ORION-XT Detectors Reporting via the IIM .4-15
4-6.11 Level-2 Alarm Function for AnaLASER-II or ORION-XT Detectors Reporting
via the IIM ...............................................................................................................4-15
4-6.12 Notification Appliance Pattern Change Function to 60 BPM ....................................4-15
4-6.13 Notification Appliance Pattern Change Function to 120 BPM ..................................4-16
4-6.14 Notification Appliance Pattern Change Function to Temporal Coding......................4-16
4-6.15 Notification Appliance Pattern Change Function to Continuous Output...................4-17
4-6.16 Initiating Event Counting Function ..........................................................................4-17
4-7 Constructing Arguments for Initiating Events from Remote, Networked
Control Units...........................................................................................................4-18
4-7.1 Remote-Node Simple Arguments .............................................................................4-18
4-7.2 Remote-Node Compound Arguments.......................................................................4-18
4-7.3 Remote State Variable (Fy:Cx) .................................................................................4-18
4-7.4 Releasing Service and ULC Operation .....................................................................4-19
4-8 Creating Event Output Control (EOC Tab)...............................................................4-30
4-8.1 The <Apply> Button...............................................................................................4-32
4-8.2 The <Reset> Button ...............................................................................................4-32
4-9 Structuring Event Output Control ...........................................................................4-33
4-10 Event Output Control Examples ..............................................................................4-34
4-11 Additional Event Output Control Examples.............................................................4-36
4-11.1 Limited Water Supply Example ...............................................................................4-36
4-11.2 NAC that Tracks AnaLASER-II or ORION-XT Alarm State.......................................4-37
4-11.3 External Maintenance Bypass Switch Example........................................................4-38

CHAPTER 5 COMMUNICATIONS TO THE CONTROL UNIT

5-1 Introduction ............................................................................................................5-1
5-2 Hardware Connections ............................................................................................5-2
5-3 Communication Utilities..........................................................................................5-3
5-3.1 Selecting Node and Entering Password ...................................................................5-3
5-3.2 Communications Setup ...........................................................................................5-4
5-3.3 Sending a Configuration ..........................................................................................5-5
5-3.3.1 Selecting A File To Send..........................................................................................5-5
5-3.3.2 Sending a Configuration ..........................................................................................5-6
5-3.4 Receive a Configuration ...........................................................................................5-6
5-3.4.1 Selecting the File to Receive.....................................................................................5-7
5-3.4.2 Receiving a Configuration ........................................................................................5-7
5-3.5 Online .....................................................................................................................5-8
5-3.6 Get Sensitivity Levels...............................................................................................5-9
5-3.6.1 Retrieve Sensitivity Levels .......................................................................................5-9
5-3.7 Event Log ................................................................................................................5-10
5-3.7.1 Clearing The Event Log ...........................................................................................5-11
5-3.7.2 Receiving An Event Log ...........................................................................................5-12
5-3.7.3 The Event Log .........................................................................................................5-13
5-3.7.4 View Event Log ........................................................................................................5-14
5-3.8 Receive Test Log ......................................................................................................5-14
5-3.8.1 Receiving A TEST Log .............................................................................................5-14
5-3.9 Receive Walk Test Log .............................................................................................5-15

April 2018 viii P/N 06-237480-001

 TABLE OF CONTENTS (CONT.)
5-3.9.1 Receiving A Walk Test Log ...................................................................................... 5-15
5-3.10 Receive Network Node Map..................................................................................... 5-16
5-3.11 Verify ...................................................................................................................... 5-16
5-3.12 Compare ................................................................................................................. 5-17

Appendix A— System Example........................................................................................................A-1

Appendix B— New York City Abort Sequence ..................................................................................B-1

B-1 Introduction............................................................................................................B-1
B-2 General Discussion .................................................................................................B-1
B-2.1 Sequence of Operation for 3 NAC Solution .............................................................B-1
B-2.2 System Configuration for 3 NAC Solution ...............................................................B-1
B-2.3 Sample Programs for N.Y.C. Abort Sequence..........................................................B-2
B-3 Sample Program 1 ..................................................................................................B-2
B-4 Sample Program 2 ..................................................................................................B-3
B-5 Sample Program 3 ..................................................................................................B-4
B-6 Sample Program 4 ..................................................................................................B-5

P/N 06-237480-001 ix April 2018

 LIST OF FIGURES
Figure Name Page Number
1-1 Setup Wizard Welcome Screen ................................................................................................. 1-2
1-2 Ready to Install Screen ............................................................................................................. 1-2
1-3 Installation Progress Bar .......................................................................................................... 1-3
1-4 Setup Wizard Complete Screen................................................................................................. 1-3
1-5 Optional Reboot Prompt ........................................................................................................... 1-4
1-6 Select Firmware Version Screen ............................................................................................... 1-5
1-7 Main Screen.............................................................................................................................. 1-6
1-8 Toolbar Icon Descriptions ........................................................................................................ 1-6
2-1 Main Toolbar ............................................................................................................................ 2-1
2-2 Side Toolbars (shown expanded).............................................................................................. 2-2
2-3 Drop-Down Menus.................................................................................................................... 2-2
2-4 File>Print Detailed Configuration Printout Screen ................................................................... 2-4
2-5 SUMMARY Tab ......................................................................................................................... 2-8
2-6 SLC and EXPANSION I/O Tab .................................................................................................. 2-9
2-7 Module Choices from SLC and EXPANSION I/O>Add... ........................................................... 2-10
2-8 City-Tie Module Physical Address Screen ................................................................................. 2-11
2-9 City-Tie Settings Screen ............................................................................................................ 2-11
2-10 Relay Module Physical Address Screen ..................................................................................... 2-12
2-11 Relay Module Setting Configuration Screen .............................................................................. 2-12
2-12 Relay Circuit Configuration Screen ........................................................................................... 2-13
2-13 Network Card Physical Address Screen .................................................................................... 2-15
2-14 Network Interface Card Settings Screen.................................................................................... 2-15
2-15 PMU Module Setting Configuration Screen ............................................................................... 2-17
2-16 R-NAC Module Physical Address Screen ................................................................................... 2-18
2-17 R-NAC Module Setting Configuration Screen ............................................................................ 2-18
2-18 R-NAC Configured as NAC or Release ....................................................................................... 2-19
2-19 NAC Configuration Screen ........................................................................................................ 2-20
2-20 Release Circuit Configuration Screen........................................................................................ 2-22
2-21 DACT Module Physical Address Screen .................................................................................... 2-23
2-22 DACT Module Setting Configuration Screen ............................................................................. 2-23
2-23 EVENT OUTPUT CONTROL (EOC) Tab ................................................................................... 2-25
2-24 ON-BOARD Tab ........................................................................................................................ 2-26
2-25 Update Device State Screen ...................................................................................................... 2-27
2-26 DISABLED Cautionary Message................................................................................................ 2-28
2-27 NAC Configuration Screen ........................................................................................................ 2-28
2-28 Release Circuit Configuration Screen........................................................................................ 2-30
2-29 Programmable Relay Configuration Screen............................................................................... 2-32
2-30 DAY/NIGHT/WEEKEND Tab ..................................................................................................... 2-34
2-31 DISPLAY Tab............................................................................................................................ 2-35
2-32 RDCM Range Entry Dialog Box ................................................................................................. 2-36
2-33 RDCM Setting Configuration Screen ......................................................................................... 2-36
2-34 LAM Range Entry Dialog Box .................................................................................................... 2-37
2-35 LAM Setting Configuration Screen ............................................................................................ 2-37
2-36 ATM Range Entry Dialog Box.................................................................................................... 2-39
2-37 ATM Owner Location Dialog Box .............................................................................................. 2-39
2-38 Owner Location Dialog Box....................................................................................................... 2-40
2-39 IIM Tab..................................................................................................................................... 2-42
2-40 HSD Range Entry Dialog Box.................................................................................................... 2-43
2-41 STRINGS Tab........................................................................................................................... 2-44
2-42 Enter String... Dialog Box ......................................................................................................... 2-45
2-43 GLOBAL Tab ............................................................................................................................ 2-47
2-44 Global Timers Dialog Box from Global Tab .............................................................................. 2-49
2-45 Isolation Macro Code Dialog Box .............................................................................................. 2-52

P/N 06-237480-001 xi April 2018

 LIST OF FIGURES (CONT.)
Figure Name Page Number
2-46 Select Type Dialog Box ............................................................................................................. 2-53
2-47 Range Dialog Box...................................................................................................................... 2-53
2-48 SOFTKEYS Tab ........................................................................................................................ 2-54
2-49 Softkey Dialog Box.................................................................................................................... 2-55
2-50 Softkey Type List ...................................................................................................................... 2-55
2-51 CALL FOR SERVICE Tab ......................................................................................................... 2-56
2-52 RELEASE GROUP Tab ............................................................................................................. 2-57
2-53 Output Group Tab .................................................................................................................... 2-58
3-1 SLC and EXPANSION I/O Tab List ........................................................................................... 3-1
3-2 Select Type (of Module) Screen................................................................................................. 3-2
3-3 Range Entry Dialog Box ............................................................................................................ 3-2
3-4 Signal Line Circuit (SLC) Settings Dialog Box ........................................................................... 3-3
3-5 List of Registered SLC Devices Dialog Box and List .................................................................. 3-3
3-6 SLC Device Range Entry Dialog Box ......................................................................................... 3-4
3-7 Select Type... (SLC Devices) Screen .......................................................................................... 3-5
3-8 List of Registered SLC Devices.................................................................................................. 3-5
3-9 Owner Location Dialog Box....................................................................................................... 3-6
3-10 SLC Device Address Dialog Box................................................................................................ 3-7
3-11 Select Type... (SLC Devices) Screen .......................................................................................... 3-8
3-12 Addressable AlarmLine Settings Screen ................................................................................... 3-9
3-13 Addressable Relay Settings Screen ........................................................................................... 3-10
3-14 Addressable Sounder Module Settings Screen .......................................................................... 3-11
3-15 Ion Smoke Detector Settings Screen ......................................................................................... 3-12
3-16 Model PSD-7152 Photoelectric Smoke Detector Settings Screen .............................................. 3-13
3-17 Model DS-PS Photoelectric Smoke Detector Settings Screen .................................................... 3-15
3-18 Is This A DS Series Detector? Prompt ...................................................................................... 3-16
3-19 Model THD-7252 Heat Detector Settings Screen....................................................................... 3-17
3-20 Model DS-HFS Heat Detector Screen ........................................................................................ 3-18
3-21 Thermal Cycling Settings Screen .............................................................................................. 3-19
3-22 PALM Module Settings Screen .................................................................................................. 3-20
3-23 Alarm Settings Screen .............................................................................................................. 3-21
3-24 Abort Station Settings Screen ................................................................................................... 3-21
3-25 Supervisory Input Settings Screen ............................................................................................ 3-23
3-26 Waterflow Input Settings Screen ............................................................................................... 3-24
3-27 Remote Releasing Module Settings Screen (Using an Actuator as a Releasing Device)............... 3-25
3-28 Remote Releasing Module Settings Screen (Using an Initiator as a Releasing Device) ............... 3-26
3-29 Remote Releasing Module Settings Screen (Using a Solenoid as a Releasing Device) ................ 3-27
3-30 Isolation Macro Number Menu ................................................................................................. 3-29
4-1 EOC Creation Screen................................................................................................................ 4-30
4-2 EOC Text Editor Screen ........................................................................................................... 4-30
4-3 Saved EOC Code Screen ........................................................................................................... 4-31
4-4 EOC Error and/or Warning Screen ........................................................................................... 4-32
4-5 Limited Water Supply ............................................................................................................... 4-36
4-6 Tracking NAC ........................................................................................................................... 4-37
4-7 Maintenance Bypass Switch...................................................................................................... 4-38
5-1 Tools Drop-Down Menu............................................................................................................ 5-1
5-2 ACT-MLX Main Toolbar............................................................................................................ 5-1
5-3 Hardware Connection from ARIES-MLX Control Unit to Laptop Computer.............................. 5-2
5-4 Non-Networked Panel Enter Password Screen .......................................................................... 5-3
5-5 Networked Panel Choose Node and Enter Password Screen ..................................................... 5-4
5-6 USB Communication Setting Screen......................................................................................... 5-4
5-7 RS232 Communication Setting Screen ..................................................................................... 5-5
5-8 Select A Configuration Screen................................................................................................... 5-5

April 2018 xii P/N 06-237480-001

 LIST OF FIGURES (CONT.)
Figure Name Page Number
5-9 Send Configuration Progress Screen......................................................................................... 5-6
5-10 Send Configuration Complete Screen ....................................................................................... 5-6
5-11 Select A Configuration Screen................................................................................................... 5-7
5-12 Receive Configuration Progress................................................................................................. 5-8
5-13 Receive Configuration Complete ............................................................................................... 5-8
5-14 Online Terminal-Emulation Mode ............................................................................................ 5-9
5-15 Select An SLC Module Screen................................................................................................... 5-9
5-16 Range Screen ............................................................................................................................ 5-10
5-17 Retrieving Sensitivity Levels...................................................................................................... 5-10
5-18 Event Log Query ....................................................................................................................... 5-11
5-19 Clear Event Log Progression ..................................................................................................... 5-11
5-20 Clear Event Log Complete......................................................................................................... 5-11
5-21 Clear Event Log Abort............................................................................................................... 5-12
5-22 Event Log Data Range ............................................................................................................... 5-12
5-23 Receive Event Log Progression.................................................................................................. 5-12
5-24 Event Log Received Confirmation ............................................................................................. 5-13
5-25 Event Log Screen ...................................................................................................................... 5-13
5-26 Receive Test Log Progress......................................................................................................... 5-14
5-27 Test Log Screen ........................................................................................................................ 5-14
5-28 Receive Walk Test Log Progress ................................................................................................ 5-15
5-29 Walk Test Log ........................................................................................................................... 5-15
5-30 Network Node Map ................................................................................................................... 5-16
5-31 Verification Summary............................................................................................................... 5-17
5-32 Configuration Compare Results Screen .................................................................................... 5-17
A-1 Example of Sequence of Operation ........................................................................................... A-1
B-1 New York City Installation ........................................................................................................B-6

P/N 06-237480-001 xiii April 2018

 LIST OF TABLES
Table Name Page Number
2-1 FILE Commands ...................................................................................................................... 2-3
2-2 VIEW Commands ..................................................................................................................... 2-4
2-3 TOOLS Commands .................................................................................................................. 2-5
2-4 WINDOW Commands................................................................................................................ 2-6
2-5 HELP Commands ..................................................................................................................... 2-6
2-6 SUMMARY Tab Options............................................................................................................ 2-8
2-7 SLC and EXPANSION I/O Tab Options ..................................................................................... 2-9
2-8 Relay Circuit Configuration Screen Options.............................................................................. 2-14
2-9 Network Interface Card Configuration Screen Options. ............................................................ 2-16
2-10 PMU Setting Configuration Screen Options............................................................................... 2-17
2-11 NAC Configuration Screen Options........................................................................................... 2-20
2-12 Release Circuit Configuration Screen Options .......................................................................... 2-22
2-13 DACT Setting Configuration Screen Options............................................................................. 2-24
2-14 NAC Configuration Screen Options........................................................................................... 2-29
2-15 Release Circuit Configuration Screen Options .......................................................................... 2-30
2-16 Relay Circuit Configuration Screen Options.............................................................................. 2-33
2-17 DAY/NIGHT/WEEKEND Screen Options ................................................................................... 2-34
2-18 DISPLAY Screen Options .......................................................................................................... 2-35
2-19 LAM Configuration Options ...................................................................................................... 2-38
2-20 IIM Screen Options ................................................................................................................... 2-43
2-21 GLOBAL Tab Options............................................................................................................... 2-47
2-22 Global Timers Dialog Box Options............................................................................................ 2-50
2-23 Isolation Macro Devices to be Selected ..................................................................................... 2-51
2-24 Isolation Macro Code Dialog Box Options ................................................................................. 2-52
3-1 SLC and EXPANSION I/O Tab Options ..................................................................................... 3-2
3-2 List of Registered SLC Devices Screen Options......................................................................... 3-4
3-3 Addressable AlarmLine Settings Screen Options ...................................................................... 3-9
3-4 Addressable Relay Settings Screen Options .............................................................................. 3-10
3-5 Addressable Sounder Module Settings Screen Options............................................................. 3-11
3-6 Ion Smoke Detector Settings Screen Options............................................................................ 3-12
3-7 Model CPD-7052 Ionization Smoke Detector Pre-Alarm/Alarm Ranges..................................... 3-13
3-8 Model PSD-7152 Photoelectric Smoke Detector Settings Screen Options ................................. 3-14
3-9 Model PSD-7152 Photoelectric Smoke Detector Pre-Alarm/Alarm Range.................................. 3-14
3-10 Model DS-PS Photoelectric Smoke Detector Settings Screen Options ....................................... 3-15
3-11 Model DS-PS Photoelectric Smoke Detector Pre-Alarm, Alarm, Night Ranges........................... 3-16
3-12 Model THD-7252 Heat Detector Settings Screen Options ......................................................... 3-17
3-13 THD-7252 Thermal Detector Pre-Alarm/Alarm Ranges............................................................. 3-17
3-14 PALM Interface Module Settings Screen Options ...................................................................... 3-20
3-15 Alarm Module Settings Screen Options .................................................................................... 3-21
3-16 Abort Station Module Settings Screen Options ......................................................................... 3-22
3-17 Abort Definitions ...................................................................................................................... 3-22
3-18 Supervisory Input Module Settings Screen Options .................................................................. 3-23
3-19 Waterflow Module Settings Screen Options............................................................................... 3-24
3-20 Remote Releasing Module Settings Screen (with Actuator as Releasing Device) Options ........... 3-25
3-21 Remote Releasing Module Settings Screen (with Initiator as Releasing Device) Options............ 3-26
3-22 Remote Releasing Module Settings Screen (with Solenoid as Releasing Device) Options........... 3-28
3-23 Isolation Macro Input Options .................................................................................................. 3-29
3-24 Configurable Parameters .......................................................................................................... 3-32
4-1 Initiating Devices ...................................................................................................................... 4-2
4-2 Input Symbolic Representations ............................................................................................... 4-4
4-3 Combining Operators for Initiating Arguments ......................................................................... 4-4
4-4 Control Unit-Based Outputs ..................................................................................................... 4-6
4-5 Combining Operators for Outputs ............................................................................................ 4-11

P/N 06-237480-001 xv April 2018

 LIST OF TABLES (CONT.)
Table Name Page Number
4-6 EOC Operators and Functions ..................................................................................................4-20
4-7 EOC Tab Options ......................................................................................................................4-31
4-8 EOC, Example 1........................................................................................................................4-34
4-9 EOC, Example 2........................................................................................................................4-35
5-1 Locations of Communications Utilities Descriptions in Manual.................................................5-3

April 2018 xvi P/N 06-237480-001

 General Information

CHAPTER 1
GENERAL INFORMATION

1-1 INTRODUCTION

Versions of configuration tools, Kidde® ARIES®-MLX Configuration Tool (ACT-MLX) and ARIES
NETLink Configuration Tool (ACT8000), are deployed within an application called the “Configuration
Software Launcher”. This launcher provides the user with one point of access to any version of ACT-
MLX and ACT8000.

ACT-MLX and ACT8000 are Microsoft® Windows®-based applications that are used to create specific
applications for ARIES-MLX and ARIES NETLink control units respectively. They enable the user to
create a complete system configuration, including details for initiating devices, output control and
display messages. Details on how to select the appropriate application from within the Configuration
Software Launcher are provided in section 1-4.

This manual guides the user on how to set up and configure an ARIES-MLX control unit using
ACT-MLX software.

1-2 PC REQUIREMENTS

Minimum computer requirements for ACT-MLX are listed below. System requirements vary between
operating systems. Refer to the appropriate section.

For computers with Windows 7, 8.1 or 10 installed:

• 1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor

• 1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)

For computers with Windows XP installed:

• 300 MHz or faster Pentium-compatible CPU

• 128 MB (RAM) or more

Note: Administrator privileges for the PC are required in order to install the Configuration
Software Launcher and Configuration Software.

1-3 INSTALLING THE CONFIGURATION SOFTWARE LAUNCHER AND THE ACT-MLX SOFTWARE
1. Download the configuration software from the Distributor Extranet on www.kiddefiresystems.
com and save it to a location on your computer.
2. Unzip the downloaded file.
3. Run the file “setup.msi” to start the Setup Wizard.
4. After the Setup Wizard is finished processing, the Setup Wizard Welcome Screen displays.

Note that the version that is shown in Figure 1-1 (v1.0.5.4) is the version of the Configuration
Software Launcher, not the version of the ACT-MLX software.

P/N 06-237480-001 1-1 April 2018

General Information

5. Select the <Next> button to proceed to the next screen.

Figure 1-1. Setup Wizard Welcome Screen

6. The Ready to Install the Program screen displays (Figure 1-2). Setup automatically defaults to
place the program in the C: drive. Click on the <Install> button to continue with installation.

Figure 1-2. Ready to Install Screen

April 2018 1-2 P/N 06-237480-001

 General Information

A progress bar displays as the software is being installed.

Figure 1-3. Installation Progress Bar

7. The Setup Wizard Complete screen displays (Figure 1-4). Setup of ACT-MLX is complete. If you
have rebooted the computer after installing the ACT-MLX software previously, there is no need
to reboot now. You can select “Launch the Configuration Software Launcher for the ARIES-MLX
Configuration Tool (ACT-MLX)” radio button to start the software, then select <Finish>.

Figure 1-4. Setup Wizard Complete Screen

P/N 06-237480-001 1-3 April 2018

General Information

8. If you have not installed the ACT-MLX software previously, please follow the prompts to reboot.

Figure 1-5. Optional Reboot Prompt

1-4 STARTING ACT-MLX

1. From the desktop, double-click the ACT-MLX icon (the icon displays on the desktop if “Yes” was
selected during the installation process when prompted for “Create a shortcut for the program
on the desktop?”).
2. Alternatively, from the Start menu, select “All Programs”. Then, select the “Kidde Fire Systems”
folder. Select the “ARIES-MLX Configuration Tool” folder. Select “Launch ARIES-MLX
Configuration Tool”.
The following screen will display before the ACT-MLX program starts. This screen allows the
user to launch previously-released ACT software versions, enabling communication to older
versions of the panel.

• Select the desired Control Unit and associated firmware version for the Main Controller
Board (MCB) and SLC firmware on the MCB. Click <OK> to launch the configuration
tool for the specific Control Unit and MCB/SLC firmware versions. For example, selecting
ARIES-MLX MCB_300/SLC_1011 – ACT-MLX_300.exe and clicking <OK> launches the
ACT-MLX Configuration Tool for ARIES-MLX control units that have MCB firmware
version 3.0.0 and SLC firmware version 1.0.11 (for SLCs located on the MCB).

• Click <Documentation> to access technical manuals and user guides for the specific
control unit and MCB/SLC firmware versions.

April 2018 1-4 P/N 06-237480-001

 General Information

Figure 1-6. Select Firmware Version Screen

P/N 06-237480-001 1-5 April 2018

General Information

3. The ACT-MLX Main Screen will appear:

Tools Menu
View Menu
File Menu

Status Bar
Figure 1-7. Main Screen

Figure 1-8 describes each of the icons located on the tool bar on the Main Screen (Figure 1-7). The
operation of the tool bar icons is described in Chapter 2.

Print File
Save File Compare Configuration
Open File Verify Configuration
New File Receive Network Node Map

Send Configuration Clear Event Log

Receive Configuration Receive Event Log
Online

Figure 1-8. Toolbar Icon Descriptions

April 2018 1-6 P/N 06-237480-001

 General Information

1-5 INSTALLING THE USB DRIVER FOR CONNECTION TO CONTROL UNIT

The computer with ACT-MLX installed cannot communicate via USB with the control unit until a USB
driver has been installed. Instructions to install a USB driver are listed below. For proper installation,
the computer must be equipped with Microsoft Windows XP, 7, 8.1 or 10.
Note: If you've installed a prior version of the driver, perform the steps in the section entitled:
“Section 1-5.3, Un-installing the USB Driver“. Then proceed with this section below.
Note: If you're running Windows 8.1 or 10, you should perform the steps in the section entitled:
“Section 1-5.4, Digital Signature Check on Windows 8.1 or 10“, then proceed with this section
below.

1-5.1 Installing USB Drivers for ACT-MLX on Microsoft Windows XP, 7, 8.1 or 10
1. With the ACT-MLX software installed on your computer, use Windows Explorer to locate
the USB driver by browsing to the location where the ACT-MLX software was installed.
Example: C:\Kidde Fire Systems\ARIES-MLX Configuration Tool (ACT-MLX)
\Data\Drivers
2. Locate the compressed USB driver file that has a name which corresponds to your
computer hardware and operating system. For example, the “MLIC_WIN8_64” driver is
for a 64-bit computer running Windows 8.1
3. Extract the contents of the compressed driver file to a temporary folder that you create.
For example: C:\Temp\MLIC. Make a note of the folder location for later use.
Note: It is recommended that all devices attached to your computer are installed properly (i.e.
no yellow exclamation marks are next to any devices in Device Manager).
4. Power on the ARIES-MLX control unit and, after 30 seconds, connect it to your computer
using an USB A-to-B type cable.
5. Windows may attempt to automatically install the driver but will not be successful. When
it fails or, if it does not attempt to automatically install the driver, open the Device
Manager.
6. In Device Manager, locate the entry under “Other devices” entitled “Unknown device”. If
there are multiple such entries, follow the instructions in the next step to find the correct
one. Otherwise, skip the next two steps.
7. To identify the correct “Unknown device”, right-click on the device, and select
“Properties”. Click on the “Details” tab and from “Property”, select “Hardware IDs”.The
correct device will have the following value: "USB\VID_03EB&PID_6119&REV_0100"
8. If you cannot find an entry that has the proper values (specified in the prior step), then
either you have: 1) a prior version of the driver installed, or 2) you should unplug, reboot
your computer, and replug the USB cable and see if the entry shows up. If the latter
doesn't work: perform the steps in the section entitled: "Section 1-5.3, Un-installing the
USB Driver“, and then restart this section.
9. With the correct “Unknown device” identified, right-click on it, and select “Properties”.
10. Select the Driver tab, and click “Update Driver...”.
11. An “Update Driver Software” screen opens. Click “Browse my computer for driver
software”.
12. Click the <Browse> button and go to the location that the extracted USB driver file was
saved to in Step 3. Click <Next>.
13. Windows will prompt you to proceed. Click “Install this driver software anyway”.
14. At the end of the installation, you should see a prompt indicating that “Windows has
successfully updated your driver software”. Click <Close> to close Device Manager. If
installation fails, please consult Kidde Technical Support.
15. Reboot your computer after installing the driver.
16. To validate that the drivers are installed properly, perform the steps in the section
entitled: "Section 1-5.2, Verifying the Installation of the USB Drivers”.

P/N 06-237480-001 1-7 April 2018

General Information

1-5.2 Verifying the Installation of the USB Drivers

1. With the ARIES-MLX control unit powered on and connected to your computer with the
USB cable, open Device Manager.
2. Expand the “Ports (COM & LPT)” entry.
3. If you see a “MLIC (COM##)” entry without a yellow exclamation point, the driver is
installed properly. Skip the following steps.
4. If you don't see a “MLIC (COM##)” entry, expand the “Other devices” entry to see if there
is an “Unknown device” entry. If there is not, remove the USB cable and reboot your
computer. After rebooting, reconnect the USB cable, open Device Manager, and see if
either “MLIC (COM##)” or “Unknown device” appears. If it does not appear, you likely
have a prior version of the driver installed. Follow the instructions in the section entitled
"Section 1-5.3, Un-installing the USB Driver“.
5. If you see an “Unknown Device” entry under “Other devices,” follow the steps in the
section entitled “Section 1-5.1, Installing USB Drivers for ACT-MLX on Microsoft
Windows XP, 7, 8.1 or 10“, and then repeat this section.
6. If you see a “MLIC (COM##)” entry with a yellow exclamation mark next to it, then the
driver isn't installed properly. A yellow exclamation mark indicates an error with the
driver installation. Follow the instructions in the sections entitled: “Section 1-5.3, Un-
installing the USB Driver“, “Section 1-5.1, Installing USB Drivers for ACT-MLX on
Microsoft Windows XP, 7, 8.1 or 10", and then repeat this section.

The following steps must be followed precisely and in order. It is recommended that a
Computer Specialist perform or be available while these steps are being performed. If you
WARNING have any questions, please contact Kidde Fire Systems Technical Support.

1-5.3 Un-installing the USB Driver

1. With your computer connected to the control unit using the USB cable, open the Device
Manager.
2. Locate "Ports (COM & LPT)", and expand it.
3. Locate the "MLIC (COM##)" entry and right-click on it.
4. Select "Uninstall".
5. If you can't locate the entry, select each entry under "Ports (COM & LPT)" one at a time,
right-click each, and select "Properties".
6. Click on the "Details" tab, then select "Hardware IDs" from the Property pulldown menu.
7. The correct value for the MLIC USB driver is: "USB\VID_03EB&PID_6119&REV_0100"
8. When you find the port with the correct Hardware ID, click on the "Driver" tab, and click
the "Uninstall" button.
9. When the dialog box appears, check the box that says "Delete the driver software for this
device.", and click <OK>. The driver is now uninstalled. Close Device Manager.

1-5.4 Digital Signature Check on Windows 8.1 or 10

Note: Windows 8 is not supported. Please install the update to Windows 8.1, and then
continue with this section.
1. While holding the "Shift" key down, click "Restart".
2. Once your computer has rebooted, select "Troubleshoot", then "Advanced Options", and
"Startup Settings".
3. Finally, click on "Restart".
4. After the computer restarts, select option 7.
5. If you performed this section, after leaving another section, go back and repeat the steps
in that other section.

April 2018 1-8 P/N 06-237480-001

 Creating a System Configuration

CHAPTER 2
CREATING A SYSTEM CONFIGURATION

2-1 INTRODUCTION

The tasks required to create an ACT-MLX configuration are as follows:

• Assign an address and define the operating characteristics for each device on the SLC modules.
• Define the operating characteristics for each on-board output circuit.
• Define the operating characteristics for each expansion card.
• Identify and assign an address to all associated peripheral components such as Remote Display
Control Module (RDCM), LED Annunciator Modules (LAM), and ATM-L/-R Modules.
• Create the required initiating device to output circuit/device relationships via Event Output
Control (EOC). These relationships must be created for all initiating devices and outputs
associated with each ARIES®-MLX system. EOC configuration is described in detail in Chapter 4.
Note: All alarm events must be annunciated by public-mode notification.

2-2 BEFORE YOU BEGIN - VERSION COMPATIBILITY

The configuration software version must match the control unit software version in the first two
digits. For example, if the control unit version is 1.2.0, the configuration software version must be
1.2.x where 'x' is 0 to 9. It is possible to open files saved with an older version of the program.

Note: It is not possible to communicate with or open saved configuration

files for a control unit version that is newer than the configuration
software version.

ACT-MLX software is currently at version 3.0.0.

2-3 THE MAIN TOOLBAR

When ACT-MLX is launched, the program’s main toolbar displays (see Figure 2-1). Icons may be
selected for configuration file management and printing, sending/receiving configurations,
communicating with the ARIES-MLX control panel, and verifying/comparing configurations.

Note: The Configuration Editor launches only when a configuration file is

opened (File>Open) or created (File>New).

Figure 2-1. Main Toolbar

P/N 06-237480-001 2-1 April 2018

Creating a System Configuration

2-4 THE SIDE TOOLBAR

An optional method to view icons is to use the program’s side toolbars. The File, Tools and Help
drop-down menu commands may be accessed by placing the mouse pointer on the desired icon.

Figure 2-2. Side Toolbars (shown expanded)

2-5 DROP-DOWN MENUS

In addition to icons, menu commands may be selected via drop-down menus located at the top of the
main screen.

Figure 2-3. Drop-Down Menus

April 2018 2-2 P/N 06-237480-001

 Creating a System Configuration

2-5.1 The FILE Drop-Down Menu

Use the FILE drop-down menu (see Figure 2-3) to create, load, unload, store and print configuration
files. In addition, use the FILE drop-down menu to exit ACT-MLX.

The FILE commands from the main menu are shown in Table 2-1.

Table 2-1. FILE Commands

Command Function

New Select New or press <CTRL>-N to create a new configuration file with the extension “.xms”.
Select Open or press <CTRL>-O to open an existing configuration file with the extension
Open “.xms”. Use the standard Windows dialog box to navigate to the desired directory, and double-
click the file or select <Open> to load the file.
Select Close to close the topmost configuration file. If the file has been modified since it was
Close
last saved, a dialog box appears, requesting that the file be saved.
Save Select Save to save the topmost configuration to disk with the existing filename.
Save As Select Save As to save the topmost configuration to disk, after a filename is entered.
Select Save As Text to save the topmost configuration to an ASCII text file. When Save As Text
is selected, the screen shown below in Figure 2-4 is presented. Select the desired configuration
settings to save to a textfile and select <OK>. A dialog box will appear requesting a filename
(with filename extension “.txt”).
Save As Text
Note: If either the Save, Save As, or Exit (with file save) commands are selected, a verification
of the current configuration is performed first. If errors are found, a list will generate on the
screen and settings will not be saved. All errors must be corrected before the software will save
the configuration file. However, the file will be saved if warnings are present.
Select Print to print the current configuration (to a network or local printer). When Print is
selected, the screen shown in Figure 2-4 is presented. Select the desired configuration settings
Print
to print and select <OK>. A dialog box will appear requesting printer settings. Select the
desired printer and <OK> to print the selected topics.
Print Preview Select Print Preview to display hard copy pages of the current configuration.
Select Print Setup to display the printer settings dialog box where the desired printer may be
Print Setup
selected and configured.
Select Exit to close ACT-MLX. A message will prompt to save any unsaved configurations
Exit
before exiting.

P/N 06-237480-001 2-3 April 2018

Creating a System Configuration

Figure 2-4. File>Print Detailed Configuration Printout Screen

2-5.2 The EDIT Drop-Down Menu

Use the EDIT drop-down menu(see Figure 2-3) to navigate to the various tabs of the Configuration
Editor.

2-5.3 The VIEW Drop-Down Menu

Use the VIEW drop-down menu (see Figure 2-3) to enable or disable the use of the main toolbar and
status bar.

The VIEW commands from the Main Menu are shown in Table 2-2.

Table 2-2. VIEW Commands

Command Function

Toolbar Select Toolbar to toggle on/off display of the ACT-MLX’s main toolbar.
Select Status Bar to toggle on/off display of the ACT-MLX’s status bar, a feature which
Status Bar
describes the functionality of individual icons (located at the bottom left of the main window).

April 2018 2-4 P/N 06-237480-001

 Creating a System Configuration

2-5.4 The TOOLS Drop-Down Menu

Use the TOOLS drop-down menu (see Figure 2-3) to communicate back and forth to the ARIES-MLX
control unit. Refer to Chapter 5 for a detailed explanation of the commands available in the TOOLS
drop-down menu.

The TOOLS commands from the main menu are shown in Table 2-3.

Table 2-3. TOOLS Commands

Command Function

Communications Select Communications Setup to configure the communications parameters to enable

Setup communication with the ARIES-MLX control unit.
Send
Select Send Configuration to send the topmost configuration to the control unit.
Configuration
Receive Select Receive Configuration to receive a configuration from the control unit into the
Configuration topmost configuration.
Select On-line to connect to the ARIES-MLX control unit in a terminal-emulation mode (as if
On-line
accessing the control panel via its keypad/display).
Get Sensitivity Select Get Sensitivity Levels to retrieve and display a current list of sensitivity levels for all
Levels detectors.
• Select Event Log>Receive to receive the event log.
Event Log • Select Event Log>Clear to clear the event log.
• Select Event Log>Open Log File to open previously-saved Event Log File.
Select Receive Test Log to receive the contents of the current log of initiating device test
Receive Test Log
events.
Receive Walk Select Receive Walk Test Log to receive the contents of the current log of walk-test events to
Test Log a text file.
Receive Network Select Receive Network Node Map to view a listing of nodes networked with the local panel.
Node Map Each node occupies a unique address.
Verify Select Verify to check the entire configuration for errors or warnings.
Compare Select Compare to compare two different configuration files.

P/N 06-237480-001 2-5 April 2018

Creating a System Configuration

2-5.5 The WINDOW Drop-Down Menu

Use the WINDOW drop-down menu (see Figure 2-3) to manipulate files in the Configuration Editor.

The WINDOW commands from the main menu are shown in Table 2-4.

Table 2-4. WINDOW Commands

Command Function

Minimize All Select Minimize All to collapse all configuration files within the Configuration Editor.
Restore All Select Restore All to restore all configuration files within the Configuration Editor.
Select Configurations to create a new configuration file or switch to another previously-
Configurations
opened configuration file within the Configuration Editor.

2-5.6 The HELP Drop-Down Menu

Use the HELP drop-down menu (see Figure 2-3) to open the user manual and view the current
software version.

The HELP commands from the main menu are shown in Table 2-5.
Table 2-5. HELP Commands

Command Function

Help Topics Select Help Topics to open the user manual.

About Select About to view the version of ACT-MLX currently in use.

2-6 CREATING A NEW CONFIGURATION FILE

To create a new configuration file, select File>New or select the New File Icon on the main
toolbar ( ).

2-7 OPENING AN EXISTING CONFIGURATION FILE

To open an existing configuration file, Select File>Open or select the Open File Icon on the toolbar
( ). Select a file and click <Open>. The Configuration Editor appears.

April 2018 2-6 P/N 06-237480-001

 Creating a System Configuration

2-8 THE CONFIGURATION EDITOR

The Configuration Editor constitutes the main substructure of ACT-MLX. The user specifies all
operating characteristics and settings for each device and system component in the Configuration
Editor.

As stated in Section 2-5.2, all Configuration Editor tabs are shown in Figure 2-5. They may be
accessed by placing the mouse pointer directly on the tab name and clicking the left mouse button
(or by using the EDIT drop-down menu).

2-8.1 The <Apply> Button

Click <Apply>, located at the bottom of the Configuration Editor screen, to accept all changes made
while in the Configuration Editor. (See Figure 2-5.)

Note: Clicking <Apply> does not automatically save settings to the

configuration file. The configuration file must be saved before exiting
the program, or settings will be lost.

2-8.2 The <Reset> Button

Click <Reset>, located at the bottom of the Configuration Editor screen, to cancel all changes made
to settings while in the Configuration Editor and return to the previously-saved settings. (See
Figure 2-5.)

P/N 06-237480-001 2-7 April 2018

Creating a System Configuration

2-8.3 The SUMMARY Tab

The SUMMARY Tab includes fields for site-specific information to be entered by the end user. When
a configuration file is first created or opened, the Configuration Editor SUMMARY Tab displays by
default. (See Figure 2-5.)

Figure 2-5. SUMMARY Tab

The SUMMARY Tab options are shown in Table 2-6.

Table 2-6. SUMMARY Tab Options

Command Function

Site Name This optional field identifies the end-user site; a maximum of 40 characters is allowed.
This optional field allows additional site ID information to be entered (for example, address,
Site ID
building name, etc.); a maximum of 40 characters is allowed.
This optional field contains a message to display on the Control Unit LCD when the system
Standby Message
status is “normal.” A maximum of 40 characters is allowed.
This optional field allows the creator of the configuration file to enter his name for reference;
Author
a maximum of 40 characters is allowed.
The software version of the ARIES-MLX Control Unit is detected by the ACT-MLX and
Panel Version displayed here. Refer to Section 2-2 Before You Begin - Version Compatibility for more
information about software versions.
Time Created The date and time when the configuration was first created is displayed here.
Time Last
The date and time when the configuration was last saved to disk is displayed here.
Changed

April 2018 2-8 P/N 06-237480-001

 Creating a System Configuration

2-8.4 The SLC and EXPANSION I/O Tab

The SLC and EXPANSION I/O tab allows the user to add, edit, delete, and move expansion module
configurations and SLC loop devices. After each module is added, edited, moved, or deleted, the
module configuration data becomes stored in this Map of Registered Modules. (See Figure 2-6.) The
<Add...>, <Edit...>, <Delete>, <Move...>, and <Edit SLC Devices...> buttons are located at the
top of the screen.

Figure 2-6. SLC and EXPANSION I/O Tab

The SLC and EXPANSION I/O tab options are shown in Table 2-7.
Table 2-7. SLC and EXPANSION I/O Tab Options

Command Function

Click <Add...> to add a module. Figure 2-7 shows the module choices that appear. See
Add...
Section 2-8.5, Adding and Configuring a New Module.
Select the module to edit. Click <Edit...> or double-click a module to edit its configuration.
Edit... Depending on the module selected, different screens appear. See Section 2-8.5.8, Editing a
Module.
Delete Select the module to delete. Click <Delete> to delete the module’s configuration.
Move Select the module to move. Click <Move> to move the module’s configuration to a new slot.
Edit SLC Select the SLC module for which SLC devices will be edited. Click <Edit SLC Devices> to
Devices... open the SLC Device Editor window.

P/N 06-237480-001 2-9 April 2018

Creating a System Configuration

Figure 2-7 shows the module choices that appear.

Figure 2-7. Module Choices from SLC and EXPANSION I/O>Add...

Figure 2-7 displays the types of available modules. The configuration screens for each type of module
are described in Section 2-8.5, Adding and Configuring a New Module, and in Chapter 3,
Configuring SLC Devices. (Adding and Configuring SLC Devices are not covered in this chapter.)

2-8.5 Adding and Configuring a New Module

Each module has a different series of configuration screens. This section describes the configuration
screens for each module except the SLC Module, which is described in Chapter 3, Configuring SLC
Devices. In addition, refer to Chapter 1 of the ARIES-MLX Installation, Operation and Maintenance
Manual, P/N 06-237479-001, for complete specifications on each of the modules (also referred to as
“expansion cards”.)

Note: In the sections which follow, the Physical Address described is the
slot number where the module is installed in the control unit. The
Owner Location is user-specified text which helps identify the
location of the module or device. Logical Address is used in the Event
Output Control as a numerical identifier of the module. The logical
address does not need to change if a module needs to be moved to a
different physical slot address.

April 2018 2-10 P/N 06-237480-001

 Creating a System Configuration

2-8.5.1 ADDING AND CONFIGURING A CITY-TIE MODULE

Note: Only one (1) City-Tie Module may be selected per configuration.

To add and configure a City-Tie Module:

1. On the SLC and EXPANSION I/O tab, click <Add...>.

2. From the Select Type window, click the City-Tie Module icon, then click <OK>.
A dialog box asks you to enter the physical address (see Figure 2-8).

Figure 2-8. City-Tie Module Physical Address Screen

3. From the up/down arrows, select the physical address and click <OK>.
A dialog box asks you to enter Owner Location, Output Circuit Type, and Masterbox/City-Tie
Operation. (See Figure 2-9.)

Figure 2-9. City-Tie Settings Screen

4. From the Output Circuit Type drop-down list, select one of the 3 types:
• Local Energy Type
• Shunt Type
• Reverse Polarity Type
5. From the Masterbox/City Tie Operation drop-down list, select either of the 2 types:
• Network-wide reporting
• Local reporting only
6. Click <OK>.

For each module, this material displays on the SLC and EXPANSION I/O I/O tab in the Map of
Registered Modules.

P/N 06-237480-001 2-11 April 2018

Creating a System Configuration

2-8.5.2 ADDING A RELAY MODULE

To add a Relay Module:

1. On the SLC and EXPANSION I/O tab, click <Add...>.

2. From the Select Type window, click the Relay Module icon, then click <OK>.
The Relay Module (RELAY) Setting... dialog box asks you to enter the physical address(es) of
the range of the module(s) (see Figure 2-10).

Figure 2-10. Relay Module Physical Address Screen

3. Use the edit boxes and up/down arrows to select the range of the physical address(es) and click
<OK>.
4. The dialog box asks you to enter the Logical Address and Owner Location for each relay
module. (See Figure 2-11.) Click <OK> after entering this information for each relay module.
Logical Address is used in the Event Output Control as a numerical identifier of the module.
The logical address does not need to change if a module needs to be moved to a different physical
slot address.

Figure 2-11. Relay Module Setting Configuration Screen

5. To configure the relay circuits in the relay module, see Section 2-8.5.2.1. Or, to close the Relay
Module (RELAY) Setting... screen without accepting input, click the “X” in the upper right-hand
corner of the dialog box or click <Cancel>.

April 2018 2-12 P/N 06-237480-001

 Creating a System Configuration

2-8.5.2.1 Configuring a Relay Circuit

To configure a relay circuit:

1. Edit a circuit by double-clicking it in the Relay Module (RELAY) Setting screen (see
Figure 2-11).
The Relay Circuit #X (RELAY) Setting... configuration screen appears (see Figure 2-12).
2. Enter desired choices for each of the options in the relay circuit-configuring screen (see
Section 2-8.5.2.2), and click <OK>.
3. Close the Relay Module (RELAY) Setting... screen by clicking <OK>.
4. The SLC AND EXPANSION I/O tab list reflects the newly configured circuit information.
5. On the SLC AND EXPANSION I/O tab, click <Apply>.
6. From the main menu, click File>Save.

2-8.5.2.2 Relay Circuit Configuration Screen

This section describes each option on the Relay Circuit #X (1-4) (RELAY) Setting... Configuration
screen (see Figure 2-12).

Figure 2-12. Relay Circuit Configuration Screen

Select Relay Circuit configuration screen options as shown in Figure 2-12, then click <OK>. The
Relay Circuit configuration screen options are shown in Table 2-8.

P/N 06-237480-001 2-13 April 2018

Creating a System Configuration

Table 2-8. Relay Circuit Configuration Screen Options

Option Function

Owner Location Reference location name for the Relay circuit. Up to 40 characters can be entered.
Enabled Use this check box to enable or disable the circuit.
Activate on:
Select this check box to enter the Relay into the General Alarm Activation List.
General Alarm
Select this check box to activate the Relay circuit on AC power loss only. A relay circuit
Activate on: Loss
configured to activate on “Loss of AC Power Only” activates 150 seconds after the loss of AC
of AC Power Only
power. It de-activates immediately when AC power is restored.
Activate on:
Select this check box to activate the Relay circuit on any pre-alarm condition.
Prealarm
Activate on:
Select this check box to activate the Relay circuit on any supervisory condition.
Supervisory
Activate on:
Select this check box to activate the Relay circuit on any trouble condition.
Trouble
These times are available only when no other setting has been selected (that is, either General
Alarm, Loss of AC Power Only, PreAlarm, Supervisory, or Trouble have NOT been checked).
ITLCO Time
Select the ITLCO/CTLCO checkbox and use the edit box and the up/down arrows to configure
the ITLCO time. The range of entry is from 1 to 180 seconds or 1 to 180 minutes.
These times are available only when no other setting has been selected (that is, either General
Alarm, Loss of AC Power Only, PreAlarm, Supervisory, or Trouble have NOT been checked).
CTLCO Time
Select the ITLCO/CTLCO checkbox and use the edit box and the up/down arrows to configure
the CTLCO time. The range of entry is from 1 to 180 seconds or 1 to 180 minutes.

Notes: 1. A programmable relay is configurable for thermal cycling according to the

alarm or non-alarm states of its associated automatic heat detectors. Refer
to Section 3-5.7 for a description of thermal cycling via a Model THD-7252
Heat Detector.
2. The cyclical programmable-relay activation can be overriden by an alarm
signal from any associated alarm-initiating device other than a heat
detector configured for thermal cycling. The relay then latches into the
activated state and remains activated until it is deactivated by another
alarm condition or until the control unit is reset.

2-8.5.3 ADDING AND CONFIGURING AN SLC MODULE

Note: See Chapter 3, Configuring SLC Devices, for complete information on configuring SLC
Modules and Devices.

April 2018 2-14 P/N 06-237480-001

 Creating a System Configuration

2-8.5.4 ADDING AND CONFIGURING A NETWORK INTERFACE CARD

To add a Network Interface Card:

1. On the SLC AND EXPANSION I/O tab, click <Add>.

2. From the Select Type window, click the Network Card icon, then click <OK>.
3. Enter the physical address(es) of the modules in the dialog box (See Figure 2-13), then click
<OK>.

Figure 2-13. Network Card Physical Address Screen

4. The Network Interface Card configuration screen appears (see Figure 2-14); configuration screen
options are shown in Table 2-9.

Figure 2-14. Network Interface Card Settings Screen

P/N 06-237480-001 2-15 April 2018

Creating a System Configuration

Table 2-9. Network Interface Card Configuration Screen Options.

Option Function

Node Number Reference local node of networked control units. Up to 64 nodes per network.

Channel 1 Check this box if the network messages will be transmitted over communication
channel 1 communication. Checking only Channel 1represents a single-channel
network communication configuration. Checking both Channel 1 and Channel 2
represents dual-channel network communication configuration.

Channel 2 Check this box if the network messages will be transmitted over communication
channel 2. Checking only Channel 2 represents a single-channel network
communication configuration. Checking both Channel 1 and Channel 2
represents dual-channel network communication configuration.

Group Number Reference the autonomous sub-networks or groups that the local node belongs to.
There are 65 possible groupings, numbered 0 to 64.

Time Synch Period Specify how often the system synchronizes the clock with the other panels in the
network.

Network Reset Event Checking this box enables events from this node to be reset from a remote node.
When ULC Operation is enabled on the Global tab, this setting shall be enabled
and cannot be changed.

Network Silent Event Checking this box enables events from this node to be silenced from a remote
node. When ULC Operation is enabled on the Global tab, this setting shall be
enabled and cannot be changed.

Log All Network Checking this box enables events from the entire network to be processed and
logged by the local node regardless of group number. When ULC Operation is
Events
enabled on the Global tab, this setting shall be enabled and cannot be changed.

Process Group 0 Checking this box assigns master node privileges to the local node. When ULC
Operation is enabled on the Global tab, this setting shall be enabled and cannot
be changed.

Display and Control This parameter is only available when ULC Operation is enabled on the Global
tab. Checking this box sets this control unit as the highest priority node when
Centre Node
establishing display and control in the control unit network. The group will be
set to 0 as a result of selecting this parameter.

April 2018 2-16 P/N 06-237480-001

 Creating a System Configuration

2-8.5.5 ADDING AND CONFIGURING A POWER MANAGEMENT UNIT (PMU) MODULE

Note: Up to four (4) PMU Modules may be installed per complete system configuration for land-
based systems. One (1) PMU Module may be installed for marine systems.

To add and configure a PMU Module:

1. On the SLC AND EXPANSION I/O tab, click <Add...>.

2. From the Select Type window, click the PMU Module icon, then click <OK>. The PMU
configuration screen appears.

Figure 2-15. PMU Module Setting Configuration Screen

3. Select PMU Setting configuration screen options as described in Table 2-10, then click <OK>
(for each PMU).

The PMU Setting configuration screen options are shown in Table 2-10.

Table 2-10. PMU Setting Configuration Screen Options

Option Function

Owner Location Reference location name for PMU module.

Marine Not Currently Used. Do not select (check) this option.
When selected, this check box signals the system that the PMU contains 2 Power Supply Units
2 PSUs
(maximum number allowable).
Depending on the application, the battery-charging circuit may be shut off. Select this check
box to automatically charge batteries.
Charge Batteries
Note: Only one (1) PMU can charge batteries and charging is only available if “Supervise
Batteries” is checked in the GLOBAL tab.
Aux 1 Resettable When selected, this check box supports Auxiliary 1 power output as a resettable circuit.

Aux 2 Resettable When selected, this check box supports Auxiliary 2 power output as a resettable circuit.

P/N 06-237480-001 2-17 April 2018

Creating a System Configuration

2-8.5.6 ADDING AN R-NAC MODULE

To add an R-NAC Module:

1. On the SLC AND EXPANSION I/O tab, click <Add...>.

2. From the Select Type window, click the R-NAC Module icon, then click <OK>.
A dialog box asks you to enter the physical address(es) of the module(s) (see Figure 2-16).

Figure 2-16. R-NAC Module Physical Address Screen

3. Use the edit boxes and up/down arrows to select the range of the physical address(es) and click
<OK>.
The Release/NAC (R-NAC) Setting... configuration screen appears. A dialog box asks you to
enter the Logical Address and Owner Location for each R-NAC module. (See Figure 2-17.) Click
<OK> after entering this information for each R-NAC module.

Figure 2-17. R-NAC Module Setting Configuration Screen

April 2018 2-18 P/N 06-237480-001

 Creating a System Configuration

2-8.5.6.1 Configuring An R-NAC Module as NAC or Release Circuit

To configure the R-NAC module as NAC or Release circuit:

1. Edit a circuit by double-clicking it in the Release/NAC Module (R-NAC) Setting... configuration

screen (see Figure 2-17).
A dialog box appears to configure the R-NAC as a NAC or Release Circuit (see Figure 2-18).

Figure 2-18. R-NAC Configured as NAC or Release

2. Double-click NAC, DISABLED, or RELEASE or left-click <OK>.

The appropriate circuit-configuring screen appears for NAC or Release circuits.
3. Enter desired choices for each of the options in the circuit-configuring screen (see
Section 2-8.5.6.2 and Section 2-8.5.6.3).
Note: A circuit must be enabled by selecting the Enabled check box to be configured.
4. Click <OK>.
5. The Release/NAC Module (R-NAC) Setting... screen reflects the newly configured circuit
information.
6. Click <OK>.
7. On the SLC AND EXPANSION I/O tab, click <Apply>.
8. From the main menu, click File>Save.

P/N 06-237480-001 2-19 April 2018

Creating a System Configuration

2-8.5.6.2 Release/NAC Module (R-NAC) as a NAC (Notification Appliance Circuit) Configuration Screen

This section describes each option on the NAC Configuration screen (see Figure 2-19).

Figure 2-19. NAC Configuration Screen

Select NAC configuration screen options as shown in Figure 2-19, then click <OK>. The NAC
configuration screen options are shown in Table 2-11.

Table 2-11. NAC Configuration Screen Options

Option Function

Owner Location Reference location name for the NAC circuit. Up to 40 characters can be entered.
Enabled Use this check box to enable or disable the circuit.
General Alarm
Select this check box to enter the NAC into the General Alarm Activation List.
Activation

April 2018 2-20 P/N 06-237480-001

 Creating a System Configuration

Table 2-11. NAC Configuration Screen Options (Continued)

Option Function

From the drop-down list, select none or select Wheelock to use the built-in synchronization
features of the following series of notification appliances:
– Wheelock® MT Series Multi-Tone Horns and Horn/Strobes
– Wheelock NS Series Horn/Strobes (see Note)
– Wheelock NH Series Horns (see Note)
– Wheelock RSS(P) Series Strobes
Intelligent NAC – Wheelock Exceder Series Horns, Strobes, and Horn/Strobes (Xenon flashtube models
only)

NOTE: Wheelock NS Series Horn/Strobes and Wheelock NH Series Horns cannot be

programmed for synchronization.
Horn/strobe combination devices utilizing the appropriate synch protocol have the option to
use silenceable horns and non-silenceable strobes. Refer to the horn/strobe manufacturer’s
installation sheet for details.
From the drop-down list, select from: 60 bpm, 120 bpm, temporal per ANSI S3.41,
Code Pattern
continuous, or thermal cycling.
Silenceable Select this check box to enable the NAC to be silenceable.
Walk Test
Select this check box to enable the NAC to be Walk Tested.
Activation
Drill Activation Select this check box to enter the NAC into the Outputs List activated by Fire Drill.
Select entries in this drop-down list to make the NAC non-silenceable for the amount of time
Silence Inhibit
specified after the NAC is activated.
Select entries in this drop-down list to make the NAC automatically silence after the amount
of time specified.
Cutoff Delay
Note: A NAC configured for Cutoff Delay turns off and remains off until a new alarm event
causes it to resound.
To enable thermal cycling, select “none” from the “Intelligent NAC” drop-down list, and select
“thermal cycling” from the “Code Pattern” drop-down list. A NAC is configurable for thermal
cycling according to the alarm or non-alarm states of its associated heat detectors. Refer to
ITLCO/CTLCO Section 3-5.7 for a description of thermal cycling via Model THD-7252 Heat Detectors. The
Activation cyclical NAC activation is overridden by an alarm signal from any associated alarm-initiating
device other than a heat detector configured for thermal cycling. The NAC then latches into
the activated state, and remains activated until it is subsequently silenced, deactivated by
another alarm condition, or the control unit is reset.
Use the edit box and the up/down arrows to configure the ITLCO time. The range of entry is
ITLCO Time
from 1 to 180 seconds or 1 to 180 minutes.
Use the edit box and the up/down arrows to configure the CTLCO time. The range of entry is
CTLCO Time
from 1 to 180 seconds or 1 to 180 minutes.

P/N 06-237480-001 2-21 April 2018

Creating a System Configuration

2-8.5.6.3 Release/NAC Module (R-NAC) as a Release Circuit Configuration Screen

This section describes each option on the Release Circuit Configuration screen (see Figure 2-20).

Figure 2-20. Release Circuit Configuration Screen

Select Release Circuit configuration screen options as shown in Figure 2-20, then click <OK>. The
Release Circuit configuration screen options are shown in Table 2-12.
Table 2-12. Release Circuit Configuration Screen Options

Option Function

Owner Location Reference location name for the Release circuit. Up to 40 characters can be entered.
Enabled Use this check box to enable or disable the circuit.
Release Device From this drop-down list, select Solenoid, Actuator or Initiator.
These times apply to solenoid-activated discharge valves. From the drop-down list, select
from: 90 seconds, 10 minute soak, 15 minute soak, on until reset, thermal cycling, or
Activation Time custom time. If custom time is chosen from this drop-down list, its edit box and up/down
arrows appear immediately below “Activation Time.” Use the edit box and up/down arrows to
enter between 2 to 18,000 seconds.
Non-Power
Select this check box to disable short-circuit detection.
Limited
Use the edit box and the up/down arrows to configure the ITLCO time. The range of entry is
ITLCO Time
from 1 to 180 seconds or 1 to 180 minutes.
Use the edit box and the up/down arrows to configure the CTLCO time. The range of entry is
CTLCO Time
from 1 to 180 seconds or 1 to 180 minutes.

April 2018 2-22 P/N 06-237480-001

 Creating a System Configuration

2-8.5.7 ADDING AND CONFIGURING A DACT MODULE

Note: Only one (1) DACT Module may be selected per configuration.

To add and configure a DACT Module:

1. On the SLC AND EXPANSION I/O tab, click <Add>.

2. From the Select Type window, click the DACT Module icon, then click <OK>.
3. With the up/down arrows, select the physical address of the module(s) and click <OK>.
(See Figure 2-21).

Figure 2-21. DACT Module Physical Address Screen

4. The DACT Setting configuration screen appears. (See Figure 2-22).

Figure 2-22. DACT Module Setting Configuration Screen

5. Select DACT Setting configuration screen options as described in Table 2-13, then click <OK>.

P/N 06-237480-001 2-23 April 2018

Creating a System Configuration

Table 2-13. DACT Setting Configuration Screen Options

Option Function

Owner Location Reference location name for DACT module.

Style Select either local only communicator or network-wide communicator.
Channel 2 By selecting this check box, the DACT module will immediately attempt to dial out on the
Enabled secondary phone line if the primary phone line fails.
If Call Forwarding is used to connect to the DACR, select this checkbox to have the DACT
Call is Forwarded
module perform a test every 4 hours instead of every 24 hours, per UL requirements.
By selecting this check box, the DACT module will dial regardless of whether the it detects a
Blind Dialing
dial tone.
Point By selecting this check box, the DACT module will report individual supervisory events from
Supervision SLC devices with their individual addresses (similar to alarm reporting).
Two protocols are available from the drop-down list:
Protocol • SIA DC-05-1999.09 Ademco Contact ID
• SIA DC-03-1990.01(R2003.10)
Primary Phone # Enter the primary phone number. 20 characters are allowed.
Secondary
Enter the secondary phone number. 20 characters are allowed.
Phone #
Account Number
10 alphanumeric characters are allowed.
1
Country Code Select United States, Canada, or India.
24 hours, 12 hours, 4 hours. Use the up/down arrows to set the Periodic Test Start (H:M):
Periodic Test
time.

2-8.5.8 EDITING A MODULE

To change any of the options for any of the modules:

1. Select the desired module in the Map of Registered Modules, and click <Edit>.
The configuration screen for the selected module appears.
2. Make the desired edits in the configuration screen.
3. Click <OK>.
4. Click <Apply>.
5. From the File menu, click Save.

April 2018 2-24 P/N 06-237480-001

 Creating a System Configuration

2-8.6 The EOC (EVENT OUTPUT CONTROL) Tab

The EOC (EVENT OUTPUT CONTROL) tab (see Figure 2-23) allows the viewing and editing of the
EOC (see Figure 2-23).

Refer to Chapter 4, Event Output Control (EOC), for complete information on using the EOC tab.

Figure 2-23. EVENT OUTPUT CONTROL (EOC) Tab

P/N 06-237480-001 2-25 April 2018

Creating a System Configuration

2-8.7 The ON-BOARD Tab

The ON-BOARD tab is used to configure control unit-based outputs. It displays a list of all enabled
and disabled circuits of the following types (see Figure 2-24):

• NAC
• R-NAC as NAC
• R-NAC as Release Circuit
• Relay
• Trouble Relay (not configurable)

Figure 2-24. ON-BOARD Tab

April 2018 2-26 P/N 06-237480-001

 Creating a System Configuration

2-8.7.1 CONFIGURING AN ON-BOARD CIRCUIT

This section provides brief general configuration instructions. For detailed individual NAC, R-NAC as
NAC, R-NAC as Release Circuit, or Relay Circuit configuration information, see Section 2-8.7.3,
through Section 2-8.7.6.

To configure a circuit on the ON-BOARD tab:

1. Edit a circuit by double-clicking it in the ON-BOARD tab list.

The Update Device State screen appears. (See Figure 2-25.) A circuit must be in the ENABLED
state to be configured. If the R-NAC circuit type is selected, the second screen in Figure 2-25
appears.

Figure 2-25. Update Device State Screen

2. For the NAC and Relay circuit types, double-click ENABLED or left-click <OK>.
The appropriate circuit-configuring screen appears for NAC or Relay circuits.
3. For the R-NAC as NAC and R-NAC as Release circuit types, double-click NAC or RELEASE or
left-click <OK>.
The appropriate circuit-configuring screen appears for NAC or Release circuits.
4. Enter desired choices for each of the options in the circuit-configuring screen.
5. Click <OK>.
The ON-BOARD tab list reflects the newly configured circuit information.
6. On the ON-BOARD tab, click <Apply>.
7. From the main menu, click File>Save.

P/N 06-237480-001 2-27 April 2018

Creating a System Configuration

2-8.7.2 DISABLING A CIRCUIT

This section describes how to DISABLE a circuit. To disable a circuit on the ON-BOARD tab:

1. Edit a circuit by double-clicking it in the ON-BOARD tab list.

2. On the Update Device State Screen, double-click DISABLED or click <OK>.
The following cautionary message appears (see Figure 2-26):

Figure 2-26. DISABLED Cautionary Message

3. Click <Yes>. The ON-BOARD tab list shows the circuit as DISABLED.
4. On the ON-BOARD tab, click <Apply>.
5. From the main menu, click File>Save.

2-8.7.3 NOTIFICATION APPLIANCE CIRCUIT (NAC) CONFIGURATION SCREEN

This section describes each option on the NAC Configuration Screen (see Figure 2-27).

Figure 2-27. NAC Configuration Screen

April 2018 2-28 P/N 06-237480-001

 Creating a System Configuration

Select NAC configuration screen options as shown in Figure 2-27, then click <OK>. The NAC
configuration screen options are shown in Table 2-14.

Table 2-14. NAC Configuration Screen Options

Option Function

Owner Location Reference location name for the NAC circuit. Up to 40 characters can be entered.
In General Alarm
Select this check box to enter the NAC into the General Alarm Activation List.
Activation List
Intelligent NAC From the drop-down list, select from: none or Wheelock.
From the drop-down list, select from: 60 bpm, 120 bpm, temporal per ANSI S3.41,
Code Pattern
continuous, or thermal cycling.
Silenceable Select this check box to enable the NAC to be silenceable.
Walk Test
Select this check box to enable the NAC to be Walk Tested.
Activation
Drill Activation Select this check box to enter the NAC into the Outputs List activated by Fire Drill.
Select entries in this drop-down list to make the NAC non-silenceable for the amount of time
Silence Inhibit
specified after the NAC is activated.
Select entries in this drop-down list to make the NAC automatically silence after the amount
of time specified.
Cutoff Delay
Note: A NAC configured for Cutoff Delay turns off and remains off until a new alarm event
causes it to resound.
To enable thermal cycling, select “none” from the “Intelligent NAC” drop-down list, and select
“thermal cycling” from the “Code Pattern” drop-down list. A NAC is configurable for thermal
cycling according to the alarm or non-alarm states of its associated heat detectors. Refer to
ITLCO/CTLCO Section 3-5.7 for a description of thermal cycling via Model THD-7252 Heat Detectors. The
Activation cyclical NAC activation is overridden by an alarm signal from any associated alarm-initiating
device other than a heat detector configured for thermal cycling. The NAC then latches into
the activated state, and remains activated until it is subsequently silenced, deactivated by
another alarm condition, or the control unit is reset.
These times apply when the Code Pattern chosen is thermal cycling. Use the edit box and the
ITLCO Time up/down arrows to configure the ITLCO time. The range of entry is from 1 to 180 seconds or
1 to 180 minutes.
These times apply when the Code Pattern chosen is thermal cycling. Use the edit box and the
CTLCO Time up/down arrows to configure the CTLCO time. The range of entry is from 1 to 180 seconds or
1 to 180 minutes.

2-8.7.4 R-NAC CIRCUIT AS A NAC DEVICE CONFIGURATION SCREEN

These screen options are identical to those of the NAC configuration screen described in
Section 2-8.7.3.

P/N 06-237480-001 2-29 April 2018

Creating a System Configuration

2-8.7.5 R-NAC CIRCUIT AS A RELEASE DEVICE CONFIGURATION SCREEN

This section describes each option on the Release Circuit Configuration Screen (see Figure 2-28).

Figure 2-28. Release Circuit Configuration Screen

Select Release Circuit configuration screen options as shown in Figure 2-28, then click <OK>. The
Release Circuit configuration screen options are shown in Table 2-15.

Table 2-15. Release Circuit Configuration Screen Options

Option Function

Owner Location Reference location name for the Release circuit. Up to 40 characters can be entered.
Release Device From this drop-down list, select Solenoid, Actuator or Initiator.
These times apply to solenoid-activated discharge valves. From the drop-down list, select
from: 90 seconds, 10 minute soak, 15 minute soak, on until reset, thermal cycling, or
Activation Time custom time. If custom time is chosen from this drop-down list, its edit box and up/down
arrows appear immediately below “Activation Time.” Use the edit box and up/down arrows to
enter between 2 to 18,000 seconds.
Non-Power
Select this check box to disable short-circuit detection.
Limited

April 2018 2-30 P/N 06-237480-001

 Creating a System Configuration

Table 2-15. Release Circuit Configuration Screen Options (Continued)

Option Function

These times apply to solenoid-activated discharge valves using thermal cycling activation
ITLCO Time times. Use the edit box and the up/down arrows to configure the ITLCO time. The range of
entry is from 1 to 180 seconds or 1 to 180 minutes.
These times apply to solenoid-activated discharge valves using thermal cycling activation
CTLCO Time times. Use the edit box and the up/down arrows to configure the CTLCO time. The range of
entry is from 1 to 180 seconds or 1 to 180 minutes.

Notes: 1. Use the “Release Device” drop-down list to select either Actuators,
Initiators or solenoid-activated discharge valves. The fixed
activation times in the “Activation Time” drop-down list apply to
solenoid-activated discharge valves.
2. A release circuit is configurable for thermal cycling according to
the alarm or non-alarm states of its associated automatic heat
detectors. Refer to Section 3-5.7 for a description of thermal
cycling via a Model THD-7252 Heat Detector. A thermal-cycling
release circuit is configured by selecting thermal cycling from the
Activation Time drop-down list.
3. The cyclical release-circuit activation is overridden by an alarm
signal from any associated alarm-initiating device other than a heat
detector configured for thermal cycling. The release circuit then
latches into the activated state and remains activated until it is
deactivated by another alarm condition or until the control unit is
reset.

P/N 06-237480-001 2-31 April 2018

Creating a System Configuration

2-8.7.6 RELAY CIRCUIT CONFIGURATION SCREEN

This section describes each option on the Programmable Relay Setting... Configuration Screen (see
Figure 2-29).

Figure 2-29. Programmable Relay Configuration Screen

Select Relay Circuit configuration screen options as shown in Figure 2-29, then click <OK>.

The Relay Circuit configuration screen options are shown in Table 2-16.

April 2018 2-32 P/N 06-237480-001

 Creating a System Configuration

Table 2-16. Relay Circuit Configuration Screen Options

Option Function

Owner Location Reference location name for the Relay circuit. Up to 40 characters can be entered.
In General Alarm
Select this check box to enter the Relay into the General Alarm Activation List.
Activation List
Select this check box to activate the Relay circuit on AC power loss only. A relay circuit
Loss of AC Power
configured to activate on “Loss of AC Power Only” activates 150 seconds after the loss of AC
Only
power. It de-activates immediately when AC power is restored.
Prealarm Select this check box to activate the Relay circuit on any pre-alarm condition.
Supervisory
Select this check box to activate the Relay circuit on any supervisory condition.
Service
Trouble
Select this check box to activate the Relay circuit on any trouble condition.
Activation
These times (for thermal cycling) are available only when no other setting has been selected
(that is, either Loss of AC Power Only, PreAlarm, Supervisory Service or Trouble Activation,
ITLCO Time have NOT been checked). Select the ITLCO/CTLCO checkbox and use the edit box and the up/
down arrows to configure the ITLCO time. The range of entry is from 1 to 180 seconds or 1 to
180 minutes.
These times (for thermal cycling) are available only when no other setting has been selected
(that is, either Loss of AC Power Only, PreAlarm, Supervisory Service or Trouble Activation,
CTLCO Time have NOT been checked). Select the ITLCO/CTLCO checkbox and use the edit box and the up/
down arrows to configure the CTLCO time. The range of entry is from 1 to 180 seconds or 1
to 180 minutes.

Notes: 1. A programmable relay is configurable for thermal cycling

according to the alarm or non-alarm states of its associated
automatic heat detectors. Refer to Section 3-5.7 for a description
of thermal cycling via a Model THD-7252 Heat Detector.
2. The cyclical programmable-relay activation can be overriden by an
alarm signal from any associated alarm-initiating device other than
a heat detector configured for thermal cycling. The relay then
latches into the activated state and remains activated until it is
deactivated by another alarm condition or until the control unit is
reset.

P/N 06-237480-001 2-33 April 2018

Creating a System Configuration

2-8.8 The DAY/NIGHT/WEEKEND Tab

Use the DAY/NIGHT/WEEKEND tab to determine the times that smoke detectors configured for day/
night/weekend operation have their alarm thresholds updated (see Figure 2-30).

Figure 2-30. DAY/NIGHT/WEEKEND Tab

Select DAY/NIGHT/WEEKEND tab screen options as shown in Figure 2-30, then click <Apply>.
Click <Reset> to reject the current settings and restore the previously applied settings. The Day/
Night/Weekend screen options are shown in Table 2-17.

Table 2-17. DAY/NIGHT/WEEKEND Screen Options

Option Function

Use Night-time
Select this check box to enable night-time settings at night.
Settings at Night
Use Night-time
Settings on the Select this check box to enable night-time settings on the weekend.
Weekend
Use the up/down arrows to provide hour and minute (in military time format) to tell the
Day Start
system when the Day starts.
Use the up/down arrows to provide hour and minute (in military time format) to tell the
Day End
system when the Day ends.

April 2018 2-34 P/N 06-237480-001

 Creating a System Configuration

2-8.9 The DISPLAY Tab

Use the DISPLAY tab to configure peripheral components (see Figure 2-31).

Figure 2-31. DISPLAY Tab

To configure DISPLAY tab options:

1. Select DISPLAY tab screen options as described in Table 2-18, then click <Apply>.
2. Click <Reset> to reject the current settings and restore the previously applied settings.
The DISPLAY tab screen options are shown in Table 2-18.

Table 2-18. DISPLAY Screen Options

Option Function

Click <Add RDCM(s)> to add Remote Display Control Module components. See
Add RDCM(s)
Section 2-8.9.1, Adding a Remote Display Control Module (RDCM).
Click <Add LAM(s)> to add LED Annunciator Module components. See Section 2-8.9.2,
Add LAM(s)
Adding an LED Annunciator Module (LAM).
Click <Add ATMs(s)> to add ATM Annunciator Driver Module Component. See
Add ATM(s)
Section 2-8.9.3, Adding an ATM Component.
To delete any component in the Display tab list, highlight the desired component, then click
Delete
<Delete>. See Section 2-8.9.4, Deleting a Module.
To change the Owner Location of any component in the Display tab list, highlight the desired
Edit Owner
component, then click <Edit Owner>. See Section 2-8.9.5, Editing Owner Location.
To designate a component as a secondary master, highlight the desired RDCM, then click
Make Master
<Make Master>. See Section 2-8.9.6, Designating an RDCM Module as a Master.

P/N 06-237480-001 2-35 April 2018

Creating a System Configuration

2-8.9.1 ADDING A REMOTE DISPLAY CONTROL MODULE (RDCM)

To add an RDCM component:

1. Click <Add RDCM(s)>.

A dialog box appears, asking for the range to be entered (see Figure 2-32).

Figure 2-32. RDCM Range Entry Dialog Box

2. Use the edit boxes and the up/down arrows to enter the Range Start and Range End.
3. Click <OK>.
The RDCM Setting... configuration dialog box appears (see Figure 2-33).

Figure 2-33. RDCM Setting Configuration Screen

4. In the optional Owner Location box, enter its location.

5. Select the Master check box to designate this component as secondary master.
6. Select the PSU Supervision check box to enable this RDCM module to perform Power Supply
Unit (PSU) supervision.
7. Click <OK>.
The Display tab list reflects the newly added RDCM configuration settings.
8. On the Display tab, click <Apply>.
9. From the main menu, click File>Save.

April 2018 2-36 P/N 06-237480-001

 Creating a System Configuration

2-8.9.2 ADDING AN LED ANNUNCIATOR MODULE (LAM)

To add a LAM component:

1. Click <Add LAM(s)>.

A dialog box appears, asking for the range to be entered (see Figure 2-34).

Figure 2-34. LAM Range Entry Dialog Box

2. Use the edit boxes and the up/down arrows to enter the Range Start and Range End.
3. Click <OK>.
The LAM Setting... configuration dialog box appears (see Figure 2-35).

Figure 2-35. LAM Setting Configuration Screen

P/N 06-237480-001 2-37 April 2018

Creating a System Configuration

4. Select LAM configuration options as described in Table 2-19, then click <OK>. The Display tab
list reflects the newly configured LAM information.
5. On the Display tab, click <Apply>.
6. From the main menu, click File>Save.
The LAM configuration options are shown in Table 2-19.

Table 2-19. LAM Configuration Options

Option Function

Owner Location Reference location name for LAM module.

Select this check box to enable audible notification by the buzzer of system status. The default
Buzzer Enabled
status of this check box is enabled.
PSU Supervision Select this check box to enable this LAM component with Power Supply Unit supervision.
System Alarm
Use the edit box and up/down arrows to select the LED that will indicate System Alarm.
LED
System Pre-
Use the edit box and up/down arrows to select the LED that will indicate System Pre-Alarm.
Alarm LED
System
Use the edit box and up/down arrows to select the LED that will indicate System Supervisory.
Supervisory LED
System Abort
Use the edit box and up/down arrows to select the LED that will indicate System Abort.
LED
System Ground Use the edit box and up/down arrows to select the LED that will indicate System Ground
Fault LED Fault.
Select any of the check boxes 1-48 to set the default color for that LED to RED. If the box is
Select the not selected, the default color is YELLOW. Any LED numbers 1 through 48 selected as a
LED(s) that system LED will not be configurable. The EOC can be used to override the color or pattern of
should show in LEDs. For more information on the EOC, see Chapter 4
red
Note: The LED color for the System Alarm, System Pre-Alarm, System Supervisory, System
Abort, and System Ground Fault LEDs are predetermined and cannot be changed..

April 2018 2-38 P/N 06-237480-001

 Creating a System Configuration

2-8.9.3 ADDING AN ATM COMPONENT

To add an ATM component:

1. On the Display tab, click <Add ATM(s)>.

A dialog box appears, asking for the range to be entered (between 1-16 ATMs). See Figure 2-36.

Figure 2-36. ATM Range Entry Dialog Box

2. Use the up/down arrows to enter the Range Start and Range End.
3. Click <OK>.
The ATM Owner Location configuration dialog box appears see Figure 2-37.

Figure 2-37. ATM Owner Location Dialog Box

4. Enter the ATM Owner Location.

5. Click <OK>.
The Display tab list reflects the newly added ATM configuration settings.
6. On the Display tab, click <Apply>.
7. From the main menu, click File>Save.

P/N 06-237480-001 2-39 April 2018

Creating a System Configuration

2-8.9.4 DELETING A MODULE

To delete any module on the Display tab list:

1. Select the desired module in the Display tab list.

2. Click <Delete>.
3. Click <OK>.
The deleted module is no longer reflected on the Display tab list.
4. On the Display tab, click <Apply>.
5. From the main menu, click File>Save.

2-8.9.5 EDITING OWNER LOCATION

To change the Owner Location for any module on the Display tab list:

1. Select the desired module in the Display tab list.

2. Click <Edit Owner>.
The Owner Location dialog box appears (see Figure 2-38).

Figure 2-38. Owner Location Dialog Box

3. Enter new Owner Location.

4. Click <OK>. The Display tab list reflects the changed Owner Location (in the Owner column).
5. On the Display tab, click <Apply>.
6. From the main menu, click File>Save.

April 2018 2-40 P/N 06-237480-001

 Creating a System Configuration

2-8.9.6 DESIGNATING AN RDCM MODULE AS A MASTER

Typically, the main Keypad/Display of the ARIES-MLX is the master user interface. Operator
intervention via the Keypad/Display always takes priority over operator-control commands issued
from any other user interface (RDCM peripheral components). The ARIES-MLX allows an RDCM to
be configured as a secondary master.
Note: Operator intervention via an RDCM configured as a master always
takes priority over operator-control commands issued from any other
RDCM peripheral component, but not those issued from the Control
Unit Keypad/Display.
Whenever an operator issues commands from a user interface (Control Unit Keypad/Display or
RDCM), the system locks out all other user interfaces—other than the Control Unit Keypad/Display
and RDCM master (if configured), preventing operator intervention from any other RDCM.
To make an RDCM a master:
1. In the Display tab list, select the desired RDCM.
2. Click <Make Master>.
The Display tab list reflects the changed master (in the Setting column).
3. On the Display tab, click <Apply>.
4. From the main menu, click File>Save.

2-8.9.7 DESELECTING AN RDCM AS A MASTER

To deselect an RDCM as a master:

1. In the Display tab list, double-click the desired RDCM.
2. Uncheck the Master check box. Click <OK>.
3. On the Display tab, click <Apply>.
4. From the main menu, click File>Save.

P/N 06-237480-001 2-41 April 2018

Creating a System Configuration

2-8.10 The IIM (INTELLIGENT INTERFACE MODULE) Tab

Use the IIM tab to register High-Sensitivity Smoke Detectors (HSDs).

Figure 2-39. IIM Tab

April 2018 2-42 P/N 06-237480-001

 Creating a System Configuration

2-8.10.1 CONFIGURING IIM TAB OPTIONS

1. Select IIM tab screen options as described in Table 2-20, then click <Apply>.
2. Click <Reset> to reject the current settings and restore the previously applied settings.
3. From the main menu, click File>Save.
The IIM tab screen options are shown in Table 2-20.

Table 2-20. IIM Screen Options

Option Function

IIM Enabled Select this check box to enable the IIM to register HSDs.
Non Latching
The default is latching alarm. Select this check box to enable non-latching alarms.
Alarms
Add... Click <Add...> to add an HSD.
Delete... Click <Delete...> to delete an HSD.

2-8.10.2 ADDING AN HSD

To add an HSD component:

1. Click <Add...>.
A dialog box appears, asking for the range to be entered for between 1 to 127 HSDs.

Figure 2-40. HSD Range Entry Dialog Box

2. Use the up/down arrows to enter the Range Start and Range End.
3. Click <OK>.
The IIM tab registry reflects the newly added HSD configuration settings.
4. On the IIM tab, click <Apply>.
5. From the main menu, click File>Save.

P/N 06-237480-001 2-43 April 2018

Creating a System Configuration

2-8.10.3 DELETING AN HSD

To delete an HSD:

1. Select the desired HSD in the IIM tab registry.

2. Click <Delete...>.
The IIM tab registry reflects that the HSD has been deleted.
3. On the IIM tab, click <Apply>.

From the main menu, click File>Save.

2-8.11 The STRINGS Tab

A string displays on the second line of the control unit’s display in lieu of the normal event message
that would ordinarily be displayed as a result of the system event. The text in the string can be up to
40 alphanumeric characters in length.

A string is activated via an Event Output Control (EOC) statement (by using Sx on the right-hand side
of an EOC line). An EOC statement is also required to deactivate a string (by using NSx on the right-
hand side of an EOC line). Refer to Chapter 4 for more information on the EOC. String variables are
defined in the STRINGS tab (see Figure 2-41).

Figure 2-41. STRINGS Tab

April 2018 2-44 P/N 06-237480-001

 Creating a System Configuration

To enter a string:

1. Double-click the string name from the String Identifier column.

The Enter String... dialog box appears (see Figure 2-42).

Figure 2-42. Enter String... Dialog Box

2. Enter alphanumeric text.

3. Click <OK> to accept your entered text.
The STRINGS tab list reflects the newly entered string in the String column.
4. Enter the string in the EOC (by using Sx on the right-hand side of an EOC line). Refer to
Chapter 4 for more information on the EOC.
5. Click <Apply>.
6. From the main menu, click File>Save.

The 16 configurable strings are prioritized for display by the string’s number (i.e., String #16 is the
highest priority and String #1 is the lowest priority). The active string with the highest string number
is the one displayed.

P/N 06-237480-001 2-45 April 2018

Creating a System Configuration

2-8.12 The GLOBAL Tab

Use the GLOBAL Tab (see Figure 2-43) to access the following settings (see Table 2-21 for details):

• Selecting City of Chicago sets the Output Circuit Type of the registered City Tie module to Local
Energy.
• Selecting ULC Operation configures the control unit for Canadian operation that meets ULC-527
requirements.
• Selecting Global Acknowledge allows the Acknowledge key to acknowledge up to 30 trouble or
supervisory events with a single key press.
• Selecting Global Alarm Acknowledge allows the Acknowledge key to acknowledge up to 30
alarm and discharge events with a single key press.
• Set Expected Battery Replacement Date (Optional)
• Set Drill Notification Pattern
• Selecting Supervise Batteries determines whether or not all PMU modules can supervise
batteries.
• Select the Delay Interval between Sequential Deactivations for Addressable Relays (Use the
Timers button.)
• Set Timing Options for AC Fail Delay, Alarm Verification, and Positive Alarm Sequence (Use the
Timers button.)
• Select Port attached to Printer
• Select Modbus 1 and Modbus 2 Port and assign Modbus ID.
• Select ICM Port.
• Select IIM Port.
• Create Isolation Macros
• Select the format to display the Time and Date.
• View the General Alarm Activation (GAA) List.

April 2018 2-46 P/N 06-237480-001

 Creating a System Configuration

Figure 2-43. GLOBAL Tab

To configure GLOBAL tab options:

1. Select GLOBAL tab screen options as described in Table 2-21, then click <Apply>.
2. From the main menu, click File>Save.
The GLOBAL tab options are shown in Table 2-18.

Table 2-21. GLOBAL Tab Options

Option Function

If selected, this check box sets the Output Circuit Type of the registered City Tie module to
City of Chicago
Local Energy.
If selected, this check box selects Canadian operation for the control unit. This includes
Display and Control Centre operation and other operations that meet ULC-527
requirements. After enabling this parameter and clicking <Apply> on the Global tab, the
ULC Operation
Network Interface parameters Network Reset Event and Network Silence Event will be
enabled and prevented from being changed. The Network Interface parameters Process
Group 0 and Log All Events shall be disabled and prevented from being changed.
If selected, this check box programs the panel to allow a single press of its Acknowledge key
Global Acknowledge
to acknowledge up to 30 trouble and supervisory events.
Global Alarm If selected, this check box programs the panel to allow a single press of its Acknowledge key
Acknowledge to acknowledge up to 30 alarm and discharge events.
Expected Battery
Enter the expected standby battery replacement date in MMDDYY form.
Replacement Date

P/N 06-237480-001 2-47 April 2018

Creating a System Configuration

Table 2-21. GLOBAL Tab Options (Continued)

Option Function

From this drop-down list, select from:

• 60 beats per minute
• 120 bpm
• temporal per ANSI S3.41
Drill Notification
Pattern • continuous
All control unit-based NACs programmed for a coded drill signal utilize the pattern selected
here.
Note: The same drill notification pattern should be used for all control
units in a networked system.
Select this check box to activate battery supervision by all registered PMUs. This is a
Supervise Batteries
prerequisite to allowing one (1) PMU to charge the battery(-ies).
Click the <Timers> button to select timing options. See Section 2-8.12.1, Changing
Timers
Timing Options.
Click the General Alarm Activation List button to view all components in the GAA list. The
GAA List
GAA List consists of the set of outputs that are activated by any alarm initiating device.
Time/Date Display From this drop-down list, select either AM/PM or 24HR/MIL.
From this drop-down list, select from:
• Disabled
Printer Port
• RS-232A or RS-232B for serial printer
• USB-Host for USB printer
From this drop-down list, select from:
Modbus 1/Modbus 2 • Disabled
Port • RS-232A for Modbus RTU
• RS-232B for Modbus RTU
From this drop-down list, select from:
• Disabled
ICM Port
• RS-232A for Internet connectivity configuration
• RS-232B for Internet connectivity configuration
From this drop-down list, select from:
• Disabled
IIM Port
• RS-232A for IIM connectivity configuration
• RS-232B for IIM connectivity configuration
Modbus ID Use the up/down arrow to select the Modbus ID.
Initiating and/or output control devices can be assigned to isolation Macros 1-4. See
Isolation Macro Section 2-8.12.2, Creating Isolation Macros. Also see Chapter 3, Configuration and
Codes Programming, of the ARIES-MLX Installation, Operation and Maintenance Manual, P/N
06-237479-001 for an overview of isolation macros.

April 2018 2-48 P/N 06-237480-001

 Creating a System Configuration

2-8.12.1 CHANGING TIMING OPTIONS

To change the timing options:

1. On the GLOBAL tab, click <Timers>.

The Global Timers dialog box appears (see Figure 2-44):

Figure 2-44. Global Timers Dialog Box from Global Tab

2. Select for the options shown in Table 2-22.

P/N 06-237480-001 2-49 April 2018

Creating a System Configuration

Table 2-22. Global Timers Dialog Box Options

Option Function

The off-premises transmission of an AC-power failure to a central station via the trouble relay
can be delayed by selecting the Central Station check box on the Global tab.
AC Fail Delay Note: Setting this value to less than 60 minutes when using a DACT
or other means to connect to the central station does not meet
UL requirements.
Sequential A delay from 5 to 15 seconds can be inserted between successive deactivations of addressable
Deactivation relays (AOs) configured for Sequential Deactivation. See Section 3-5.2, Addressable Relay
Timer Settings (AO) Screen.
Note: Do not use alarm verification for special extinguishing system
applications.
Alarm The period of time (after an initial alarm report) that a smoke detector attempts to verify that
Verification (AV) the smoke signature at its location actually exceeds its alarm threshold can be programmed
to confirm that the initial alarm report was valid. The alarm verification period is
programmable from 30 to 180 seconds in one-second increments, or 0 (zero).
Note: Do not use the PAS for special extinguishing system
applications.
Positive Alarm The PAS investigation period can be programmed from 0 to 180 seconds in one-second
Sequence (PAS) increments. The initial PAS alarm report must be acknowledged within 15 seconds to activate
Timer the investigation period.
Note: Do not use alarm verification for special extinguishing system
applications.

3. Click <OK>.
4. Click <Apply> on the GLOBAL tab.
5. From the main menu, click File>Save.

April 2018 2-50 P/N 06-237480-001

 Creating a System Configuration

2-8.12.2 CREATING ISOLATION MACROS

Up to 4 lists (Isolation Macros) of initiating devices and/or output control devices/circuits can be
created, which can then be isolated or deisolated via a single menu selection. The list of inputs and/
or outputs to be isolated are assigned to Isolation Macros 1-4. The 4 macros are independent of each
other. The specific isolation commands are executed when the appropriate Soft Key is pressed, or the
menu is used to execute the macro.

Selecting the Isolation Macro for a second time will execute a de-isolation routine for all the devices
and/or circuits that were isolated by the execution of the isolation macro. The isolation macros toggle
the devices in the command lists between the isolated and non-isolated states.

The Isolation Macros can contain up to 10 commands, each of which can include the following types
of devices:

Table 2-23. Isolation Macro Devices to be Selected

Devices that are Programmable Example of an

in Isolation Macros Abbreviation

On-board NACs NAC1-2

On-board R-NACs R-NAC1-2
On-board Relays RELAY1-3
RDCMs RDCM1-15
LAMs LAM1-16
SLC Loop Devices SLC1:1-255
R-NAC Module Circuits RNAC1:1-3
Relay Module Circuits RELAY1:1-4
Power Management Units PMU1-4
RRM Groups RG1-7
City-Tie CITY
ATMs ATM1-16
DACT DACT
Network Interface Card NIC
Network Node NODE#
SLC Output Groups OG#-#

P/N 06-237480-001 2-51 April 2018

Creating a System Configuration

To create an Isolation Macro:

1. On the GLOBAL tab, in the Isolation Macro Codes window, double-click the numbered macro
that you want to assign.
The Isolation Macro Code dialog box appears (see Figure 2-45).

Figure 2-45. Isolation Macro Code Dialog Box

2. In the Description box, enter a name, up to 40 characters of any type.

This name displays when the macro is invoked.
The Isolation Macro Code dialog box options are shown in Table 2-24.

Table 2-24. Isolation Macro Code Dialog Box Options

Option Function

Add... Click <Add...> to add devices or circuits to the Isolation Macro.

Delete... Click <Delete...> after selecting desired device/circuit to delete.
Clear... Click <Clear...> to clear all entered devices/circuits from the Isolation Macro.
<OK> Click <OK> after making lists of devices/circuits to be assigned to Isolation Macros.
Cancel Click <Cancel> to negate non-saved entries and return to the previous screen.

April 2018 2-52 P/N 06-237480-001

 Creating a System Configuration

3. Click the <Add...> button.

The Select Type dialog box appears (see Figure 2-46).

Figure 2-46. Select Type Dialog Box

4. Select the devices to be assigned to the isolation macro by double-clicking, or by highlighting and
clicking <OK>.
The Range dialog box appears (see Figure 2-47).

Figure 2-47. Range Dialog Box

5. Enter the range of devices and/or circuits to be added.

6. Click <OK>.
7. Repeat steps 3-6 for each type of device/circuit to be added.
8. In the Isolation Macro Codes window, click <OK> to create the macro.
9. On the GLOBAL tab, click <Apply>.
10. From the main menu, click File>Save.

P/N 06-237480-001 2-53 April 2018

Creating a System Configuration

2-8.13 The SOFTKEYS Tab

Use the SOFTKEYS tab to program the 4 Soft Keys. (See Figure 2-48.)

The keypad/display of both the ARIES-MLX control unit and the Remote Display Control Module
(RDCM) contains 4 programmable keys. These “soft keys” can be programmed using the ARIES-MLX
menu system (from the keypad/display) or using the ACT-MLX software. (Refer to the ARIES-MLX
Installation, Operation and Maintenance Manual, P/N 06-237479-001, for more information.)

These 4 keys will execute commands programmed by the user. When a soft key is pressed, a prompt
appears, requesting a password. Access to the soft key function is subject to the privileges set up.

Figure 2-48. SOFTKEYS Tab

April 2018 2-54 P/N 06-237480-001

 Creating a System Configuration

2-8.13.1 PROGRAMMING SOFTKEYS

To program any of the 4 numbered Softkeys:

1. On the SOFTKEYS tab, double-click the number of the Softkey that you want to program.
The Softkey dialog box appears (see Figure 2-49).

Figure 2-49. Softkey Dialog Box

2. Click the Softkey Type drop-down list. The Softkey Type list appears (see Figure 2-50).

Figure 2-50. Softkey Type List

3. From the Softkey Type list, select the desired type.

4. Click <OK>.
5. The Softkeys tab list is updated to reflect the settings assigned to each Softkey.
6. On the Softkeys tab, click <Apply>.
7. From the main menu, click File>Save.

P/N 06-237480-001 2-55 April 2018

Creating a System Configuration

2-8.14 The CALL FOR SERVICE Tab

Use the CALL FOR SERVICE tab (see Figure 2-51) to record call for service telephone numbers and
email address. All of the following fields allow a maximum of 40 characters of any type:

• Line #1 is for a user-assigned label.

• Line #2 is for a telephone number.
• Line #3 is for a telephone number.
• Line #4 is for an email address.

The text entered in Lines1-4 will be applied to a Softkey if the Call for Service Softkey type is chosen
(see Section 2-8.13, The SOFTKEYS Tab).

The call for service information is displayed on the Main Display (and all user interfaces) when a
Softkey (that has been programmed as a Call for Service button) is pressed.

Figure 2-51. CALL FOR SERVICE Tab

April 2018 2-56 P/N 06-237480-001

 Creating a System Configuration

2-8.15 The RELEASE GROUP Tab

Use the RELEASE GROUP tab (see Figure 2-52) to enter the Owner Locations of Remote Release
Modules Groups 1-7. Up to 40 characters of any type are allowed in each RG# text box.

Figure 2-52. RELEASE GROUP Tab

P/N 06-237480-001 2-57 April 2018

Creating a System Configuration

2-8.16 The OUTPUT GROUP Tab

Use the OUTPUT GROUP tab (see Figure 2-10) to enter the Owner Locations of up to 7 SLC (Signaling
Line Circuit) Output Groups, which may be made up only of (up to) 20 AOs (Addressable Relay
Modules) and/or ASMs (Addressable Sounder Modules), Groups 1-7. Up to 40 alphanumeric
characters are allowed in each OG# text box.

The Owner Location text is displayed on the control unit Keypad/Display and on a Remote Display
Control Module (if applicable).

Figure 2-53. Output Group Tab

April 2018 2-58 P/N 06-237480-001

 Configuring SLC Devices

CHAPTER 3
CONFIGURING SLC DEVICES

3-1 INTRODUCTION

The ARIES®-MLX supports various Signaling Line Circuit (SLC) devices and modules in many
configurations.

For complete information on the SLC and module capacity of the ARIES-MLX, see Chapter 1, General
Information, of the ARIES-MLX Installation, Operation and Maintenance Manual, P/N 06-237479-
001.

3-2 SLC AND EXPANSION I/O TAB

The SLC and EXPANSION I/O tab allows the user to add, edit, delete, and move module
configurations. (See Chapter 2, Section 2-8.4, The SLC and EXPANSION I/O Tab, for complete
information.)

After each module is added, edited, deleted, or moved, the module configuration data is displayed
in this Map of Registered Modules on the SLC and EXPANSION I/O tab. (See Figure 3-1.) The
<Add...>, <Edit...>, <Delete>, and <Move...> buttons are located at the top of the screen.

Figure 3-1. SLC and EXPANSION I/O Tab List

P/N 06-237480-001 3-1 April 2018

Configuring SLC Devices

The SLC and EXPANSION I/O tab options are shown in Table 3-1.
Table 3-1. SLC and EXPANSION I/O Tab Options

Command Function

Click <Add...> to add a module. Figure 3-2 shows the module choices that appear. See
Add...
Section 2-8.5, Adding and Configuring a New Module.
Select the module to edit. Click <Edit...> to edit its configuration. Depending on the module
Edit...
selected, different screens appear. See Section 2-8.5.8, Editing a Module.
Delete Select the module to delete. Click <Delete> to delete the module’s configuration.
Select the module to move (from one physical address to another). Click <Move> to move the
Move
module. Note: PMU #1 and SLC #s 1 and 2 are fixed.
Select any SLC Module. Clicking this button brings up the List of Registered SLC Devices
Edit SLC Devices screen, where they may be reconfigured. (See Section 3-4, Adding SLC Devices to an SLC
Module (Circuit), for full details.)

3-3 ADDING AN SLC MODULE (CIRCUIT)

To add an SLC module:

1. On the SLC and EXPANSION I/O tab, click <Add...> to add a module.
Figure 3-2 shows the module choices that appear.

Figure 3-2. Select Type (of Module) Screen

2. Double-click the SLC Module icon, or left-click it and click <OK>.

The Range Entry dialog box appears (see Figure 3-3).

Figure 3-3. Range Entry Dialog Box

April 2018 3-2 P/N 06-237480-001

 Configuring SLC Devices

3. Enter the physical address(es) of the SLC Modules (up to 8 of them per control unit).
4. Click <OK>.
The SLC Settings dialog box appears (see Figure 3-4).

Figure 3-4. Signal Line Circuit (SLC) Settings Dialog Box

5. Select configuration settings:

a. Enter the SLC module’s logical address using the Logical Address edit box and the up/
down arrows.
b. Enter Owner Location—up to 40 characters of any type are allowed.
c. Select Wiring type—Class A or Class B.
d. Select (optional) NAC Circuit Fail Safe Activation #1 or #2.
6. Click <OK>.
The SLC and EXPANSION I/O tab list (Map of Registered Modules) reflects the newly
configured SLC circuit information.
7. On the SLC and EXPANSION I/O tab, click <Apply>.
8. From the main menu, click File>Save.

3-4 ADDING SLC DEVICES TO AN SLC MODULE (CIRCUIT)

To add an SLC device to a SLC module:

1. In the Map of Registered Modules (see Figure 3-1), double-click the SLC module to which you
want to add an SLC device.
2. On its SLC Setting screen (see Figure 3-4), click <Add/Edit/View devices>.
The List of Registered SLC Devices dialog box and list appears (see Figure 3-5).

Figure 3-5. List of Registered SLC Devices Dialog Box and List

P/N 06-237480-001 3-3 April 2018

Configuring SLC Devices

The SLC options are shown in Table 3-2.

Table 3-2. List of Registered SLC Devices Screen Options

Option Function

Accept and Close Click <Accept and Close> after all SLC devices have been selected and configured.

Click <Add Device(s)> to select the types of SLC devices to be added to a SLC module. See
Add Device(s)
Section 3-4, Adding SLC Devices to an SLC Module (Circuit).
To delete any SLC device from the Map of Registered Modules, select the SLC device, then
Delete Device(s)
click <Delete Device(s)>.
Edit To edit any SLC device, select the SLC device, then click <Edit Configuration(s)>. See
Configuration(s) Section 3-4.1, Editing the Configuration of an SLC Device.
To edit the Owner Location of any SLC device, click <Edit Owner>. See Section 3-4.2,
Edit Owner
Editing the Owner Location of an SLC Device.
To change an SLC device’s address, click <Edit Address>. See Section 3-4.3, Editing the
Edit Address
Address of an SLC Device.
To change the type of SLC device, click <Edit Type>. See Section 3-4.4, Editing the Type of
Edit Type
an SLC Device.
Reject and Close Enter <Esc> or click the “X” in the upper right corner to quit without saving changes.

3. Click <Add Device(s)> to select the type(s) of SLC device(s) to be registered to an SLC module.
The SLC Device Range Entry dialog box appears (see Figure 3-6).

Figure 3-6. SLC Device Range Entry Dialog Box

4. Enter the Range Start and Range End for the new SLC device(s), and click <OK>.

April 2018 3-4 P/N 06-237480-001

 Configuring SLC Devices

The Select Type... (SLC Devices) screen appears (see Figure 3-7).

Figure 3-7. Select Type... (SLC Devices) Screen

5. Double-click the desired SLC device icon, or left-click it and click <OK>.
The Setting... screen appears for whatever type of SLC device was chosen.
6. Fill in the Setting... screen options for the SLC device. For complete information on Settings
screens for all types of SLC devices, see Section 3-5, Settings for SLC Devices.
The SLC Device options are updated in the List of Registered SLC Devices (see Figure 3-8).

Figure 3-8. List of Registered SLC Devices

7. Click <Accept and Close>.

8. In the SLC Settings dialog box, click <OK>.
9. On the SLC and EXPANSION I/O tab, click <Apply>.
10. From the main menu, click File>Save.

P/N 06-237480-001 3-5 April 2018

Configuring SLC Devices

3-4.1 Editing the Configuration of an SLC Device

To edit the configuration of any SLC device:

1. In the SLC and EXPANSION I/O tab Map of Registered Modules, double-click the SLC module
in which the SLC device is registered.
The SLC Settings dialog box for the SLC module appears.
2. Click <Add/Edit/View devices>.
The List of Registered SLC Devices appears.
3. To edit its configuration, select the desired SLC device, and click <Edit Configuration>.
4. Make any required changes in the SLC device’s Setting.. dialog box, and click <OK>. See
Section 3-5, Settings for SLC Devices, for full information on settings (configuration) screens for
each type of SLC device.
The List of Registered SLC Devices reflects the changes just made.
5. Click <Accept and Close>.
6. In the SLC Settings dialog box, click <OK>.
7. On the SLC and EXPANSION I/O tab, click <Apply>.
8. From the main menu, click File>Save.

3-4.2 Editing the Owner Location of an SLC Device

To edit the owner location of any SLC device:

1. In the SLC and EXPANSION I/O tab Map of Registered Modules, double-click the SLC module
in which the SLC device is registered.
The SLC Settings dialog box for the SLC module appears.
2. Click <Add/Edit/View devices>.
The List of Registered SLC Devices appears.
3. To edit its owner location, select the desired SLC device, and click <Edit Owner>.
The Owner Location dialog box appears (see Figure 3-9).

Figure 3-9. Owner Location Dialog Box

4. Make any desired changes in the Owner Location dialog box, and click <OK>.
The List of Registered SLC Devices reflects the changes just made.
5. Click <Accept and Close>.
6. In the SLC Settings dialog box, click <OK>.
7. On the SLC and EXPANSION I/O tab, click <Apply>.
8. From the main menu, click File>Save.

April 2018 3-6 P/N 06-237480-001

 Configuring SLC Devices

3-4.3 Editing the Address of an SLC Device

To edit the address of any SLC device:

1. In the SLC and EXPANSION I/O tab Map of Registered Modules, double-click the SLC module
in which the SLC device is registered.
The SLC Settings dialog box for the SLC module appears.
2. Click <Add/Edit/View devices>.
The List of Registered SLC Devices appears.
3. To edit its address, select the desired SLC device, and click <Edit Address>.
The SLC Device Address dialog box appears (see Figure 3-10

Figure 3-10. SLC Device Address Dialog Box

4. Make any desired changes in the SLC Device Address dialog box, and click <OK>.
The List of Registered SLC Devices reflects the changes just made.
5. Click <Accept and Close>.
6. In the SLC Settings dialog box, click <OK>.
7. On the SLC and EXPANSION I/O tab, click <Apply>.
8. From the main menu, click File>Save.

3-4.4 Editing the Type of an SLC Device

To edit the Type of any SLC device:

1. In the SLC and EXPANSION I/O Map of Registered Modules, double-click the SLC module in
which the SLC device is registered.
The SLC Settings dialog box for the SLC module appears.
2. Click <Add/Edit/View devices>.
The List of Registered SLC Devices appears.
3. To edit its Type, select the desired SLC device, and click <Edit Type>.
The Select Type... (SLC Devices) screen appears (see Figure 3-11).

P/N 06-237480-001 3-7 April 2018

Configuring SLC Devices

Figure 3-11. Select Type... (SLC Devices) Screen

4. Double-click the desired SLC device icon, or left-click it and click <OK>.
The Setting... screen appears for whatever type of SLC device was chosen.
5. Fill in the Setting... screen options for the SLC device.
The SLC Device options are updated in the List of Registered SLC Devices (see Figure 3-8).
6. Click <Accept and Close>.
7. In the SLC Settings dialog box, click <OK>.
8. On the SLC and EXPANSION I/O tab, click <Apply>.
9. From the main menu, click File>Save.

3-5 SETTINGS FOR SLC DEVICES

This section describes the Setting... screen for each of the SLC devices that may be selected in the
List of Registered SLC Devices.

The following sections in this manual describe each SLC device setting.

April 2018 3-8 P/N 06-237480-001

 Configuring SLC Devices

3-5.1 Addressable AlarmLine Module (AAM) Settings Screen

Select Addressable AlarmLine Settings screen options as shown in Figure 3-12, then click <OK>.
The Addressable AlarmLine Settings screen options are described in Table 3-3.

Note: The AAM initiates an “Overheat” message on the control unit display when it is configured
for an “Overheat” response. The control unit buzzer sounds, but no LEDs illuminate.

Figure 3-12. Addressable AlarmLine Settings Screen

Table 3-3. Addressable AlarmLine Settings Screen Options

Option Function

Temperature
From the drop-down list, choose ºF/ft or ºC/m (English or Metric) temperature/unit.
Units
From the drop-down list, choose appropriate switch settings. Refer to the Addressable Alarm
Switch Setting
Line Installation and Operation Manual, P/N 06-235820-001.
Pre-Alarm Select this check box to enable Pre-Alarm Reporting. Also see Table 3-24, Configurable
Reporting Parameters, for more information.
Enter length of cable using up/down arrows. Unit of cable will reflect settings selected in
Cable Length
Temperature Units box.
Alarm Response From the Alarm Response drop-down list, select Alarm or Overheat Display.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

P/N 06-237480-001 3-9 April 2018

Configuring SLC Devices

3-5.2 Addressable Relay Settings (AO) Screen

Select Addressable Relay Settings screen options as shown in Figure 3-13, then click <OK>. The
Addressable Relay Settings screen options are described in Table 3-4.

Note: AOs configured for "Sequential De-Activation" have a programmable delay of between 5 and
15 seconds between successive de-activations. The delay interval is set in the Globals tab. Up
to 16 AOs can be programmed for sequential de-activation.
An AO configured for "Fan Re-Start" only de-activates after the ARIES-MLX control unit is
reset following an alarm condition and after an AI Monitor Module configured for "Fan Re-
Start" is activated.

Figure 3-13. Addressable Relay Settings Screen

Table 3-4. Addressable Relay Settings Screen Options

Option Function

Select this check box to make the AO silenceable. Also see Table 3-24, Configurable
Silenceable
Parameters, for more information.
In General Alarm Select this check box to enter the AO into the General Alarm Activation list. Also see
Activation List Table 3-24, Configurable Parameters, for more information.
Select this check box to activate the AO on Fire Drill. Also see Table 3-24, Configurable
Drill
Parameters, for more information.
Select this check box to activate the AO for initiating signals created during Walk Test. Also
Walk
see Table 3-24, Configurable Parameters, for more information.
Sequential Select this check box to configure the AO for Sequential Deactivation. Also see Table 3-24,
Deactivation Configurable Parameters, for more information.
Select this check box to configure the AO for Fan Restart. Also see Table 3-24, Configurable
Fan Restart
Parameters, for more information.

April 2018 3-10 P/N 06-237480-001

 Configuring SLC Devices

Table 3-4. Addressable Relay Settings Screen Options (Continued)

Option Function

Select the check boxes corresponding to the output groups to which this AO belongs. An AO
Output Groups can belong to none, one, some, or all 7 output groups. Each output group can contain at most
20 AO and/or ASMs.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

3-5.3 Addressable Sounder Module (ASM) Settings Screen

Select Addressable Sounder Module Settings screen options as shown in Figure 3-14, then click
<OK>. The Addressable Sounder Module Settings screen options are shown in Table 3-5.

Figure 3-14. Addressable Sounder Module Settings Screen

Table 3-5. Addressable Sounder Module Settings Screen Options

Option Function

Select this check box to make the ASM silenceable. Also see Table 3-24, Configurable
Silenceable
Parameters, for more information.
In General Alarm Select this check box to enter the ASM into the General Alarm Activation list. Also see
Activation List Table 3-24, Configurable Parameters, for more information.
Select this check box to activate the ASM on Fire Drill. Also see Table 3-24, Configurable
Drill
Parameters, for more information.
Select this check box to activate the ASM for initiating signals created during Walk Test. Also
Walk
see Table 3-24, Configurable Parameters, for more information.
Select the check boxes corresponding to the output groups to which this ASM belongs. An
Output Groups ASM can belong to none, one, some, or all 7 output groups. Each output group can contain at
most 20 AO and/or ASMs.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

P/N 06-237480-001 3-11 April 2018

Configuring SLC Devices

3-5.4 Ion Smoke Detector (ION) Settings Screen

Select Ion Smoke Detector Settings screen options as shown in Figure 3-15, then click <OK>. The
Ion Smoke Detector Settings screen options are described in Table 3-6.

Figure 3-15. Ion Smoke Detector Settings Screen

Table 3-6. Ion Smoke Detector Settings Screen Options

Option Function

The Ionization Smoke Detector can be configured as a “Non-Latching Input” only when
Non-Latching
“supervisory-service (open area)” is selected as Application type. Select this check box to
Input
enable non-latching input when the text is available (not dimmed).
Select this check box if the ion smoke detector has an Optional Relay. When this check box is
Optional Relay
selected, the further options to activate 1) on EOC, or 2) upon alarm, become available.
Select this check box to enable Day/Night/Weekend operation. Ionization detectors can be
programmed to automatically change alarm thresholds by time of day (or on the weekend) if
Day/Night/
they are configured for Day/Night/Weekend operation. When this option is selected, the “Night/
Weekend
Weekend” alarm threshold becomes available. The “Night/Weekend” alarm level must be less
than or equal to the “Day” alarm level.
Alarm Select this check box to activate Alarm Verification. Also see Table 3-24, Configurable
Verification Parameters, for more information.
Select this check box to activate PAS (Positive Alarm Sequence). Also see Table 3-24,
PAS Delay
Configurable Parameters, for more information.
This Application selection drop-down list offers 5 options: 1) open-area, 2) in-duct, 3) DH-
Application 2000, 4) supervisory service (open-area), and 5) supervisory service (DH-2000/in-duct). See
Section 3-5.4.1, Application Definitions via Drop-Down Menu (below).
Pre-Alarm Level Use the Pre-Alarm Level edit box and the up/down arrows to increase/decrease levels.
Alarm Level Use the Alarm Level edit box and the up/down arrows to increase/decrease levels.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

April 2018 3-12 P/N 06-237480-001

 Configuring SLC Devices

3-5.4.1 APPLICATION DEFINITIONS VIA DROP-DOWN MENU

Table 3-7. Model CPD-7052 Ionization Smoke Detector Pre-Alarm/Alarm Ranges

Application Pre-Alarm Range (%/foot) Alarm Range (%/foot Night Range (%/foot

Open Area 0.5 - 1.4 0.6 - 1.5 0.6 - 1.4

In-Duct 0.5 - 0.9 0.6 - 1.0 0.6 - 0.9
DH-2000 0.5 - 0.9 0.6 - 1.0 0.6 - 0.9
Supervisory Service
N/A 0.6 - 1.5 0.5 - 1.4
(Open-Area)
Supervisory Service
N/A 0.6 - 1.0 0.5 - 0.9
(DH-2000/In-Duct)

3-5.5 Model PSD-7152 Photoelectric Smoke Detector (PHOTO) Settings Screen

Select PSD-7152 Photoelectric Smoke Detector Settings screen options as shown in Figure 3-16,
then click <OK>. The PSD-7152 Photoelectric Smoke Detector Settings screen options are
described in Table 3-8.

Figure 3-16. Model PSD-7152 Photoelectric Smoke Detector Settings Screen

P/N 06-237480-001 3-13 April 2018

Configuring SLC Devices

Table 3-8. Model PSD-7152 Photoelectric Smoke Detector Settings Screen Options

Option Function

The PSD-7152 Photoelectric Smoke Detector can be configured as a “Non-Latching Input”

Non-Latching
only when “supervisory-service (open area)” is selected as Application type. Select this check
Input
box to enable non-latching input when the text is available (not dimmed).
Select this check box if the photoelectric smoke detector has an Optional Relay. When this
Optional Relay check box is selected, the further options to activate 1) on EOC, or 2) upon alarm become
available.
Select this check box to enable Day/Night/Weekend operation. Photoelectric detectors can be
programmed to automatically change alarm thresholds by time of day (or on the weekend) if
Day/Night/
they are configured for Day/Night/Weekend operation. When this option is selected, the “Night/
Weekend
Weekend” alarm threshold becomes available. The “Night/Weekend” alarm level must be less
than or equal to the “Day” alarm level.
Alarm Select this check box to activate Alarm Verification. Also see Table 3-24, Configurable
Verification Parameters, for more information.
Select this check box to activate PAS (Positive Alarm Sequence). Also see Table 3-24,
PAS Delay
Configurable Parameters, for more information.
This Application selection drop-down list offers 5 options: 1) open-area, 2) in-duct, 3) DH-
Application 2000, 4) supervisory service (open-area), and 5) supervisory service (DH-2000/in-duct). See
Section 3-5.5.1, Application Definitions via Drop-Down Menu (below).
Pre-Alarm Level Use the Pre-Alarm Level edit box and the up/down arrows to increase/decrease levels.
Alarm Level Use the Alarm Level edit box and the up/down arrows to increase/decrease levels.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

3-5.5.1 APPLICATION DEFINITIONS VIA DROP-DOWN MENU

Table 3-9. Model PSD-7152 Photoelectric Smoke Detector Pre-Alarm/Alarm Range

Application Pre-Alarm Range (%/foot) Alarm Range (%/foot) Night Range (%/foot)

Open Area 0.2 - 3.4 0.5 - 3.5 0.5 - 3.4

In-Duct 0.2 -1.9 0.5 - 2.0 0.5 - 1.9
DH-2000 0.2 -1.9 0.5 - 2.0 0.5 - 1.9
Supervisory Service
N/A 0.5 - 3.5 0.5 - 3.4
(Open-Area)
Supervisory Service
N/A 0.5 - 2.0 0.5 - 1.9
(DH-2000/In-Duct)

April 2018 3-14 P/N 06-237480-001

 Configuring SLC Devices

3-5.6 Model DS-PS Photoelectric Smoke Detector (PHOTO) Settings Screen

Select DS-PS Photoelectric Smoke Detector Settings screen options as shown in Figure 3-17, then
click <OK>. The DS-PS Photoelectric Smoke Detector Settings screen options are described in
Table 3-10.

Figure 3-17. Model DS-PS Photoelectric Smoke Detector Settings Screen

Table 3-10. Model DS-PS Photoelectric Smoke Detector Settings Screen Options

Option Function

The DS-PS Photoelectric Smoke Detector can be configured as a “Non-Latching Input” only
Non-Latching
when “supervisory-service (open area)” is selected as Application type. Select this check box
Input
to enable non-latching input when the text is available (not dimmed).
Select this check box if the photoelectric smoke detector has an Optional Relay. When this
Optional Relay check box is selected, the further options to activate 1) on EOC, or 2) upon alarm become
available.
Select this check box to enable Day/Night/Weekend operation. Photoelectric detectors can be
programmed to automatically change alarm thresholds by time of day (or on the weekend) if
Day/Night/
they are configured for Day/Night/Weekend operation. When this option is selected, the “Night/
Weekend
Weekend” alarm threshold becomes available. The “Night/Weekend” alarm level must be less
than or equal to the “Day” alarm level.
Alarm Select this check box to activate Alarm Verification. Also see Table 3-24, Configurable
Verification Parameters, for more information.
Select this check box to activate PAS (Positive Alarm Sequence). Also see Table 3-24,
PAS Delay
Configurable Parameters, for more information.

P/N 06-237480-001 3-15 April 2018

Configuring SLC Devices

Table 3-10. Model DS-PS Photoelectric Smoke Detector Settings Screen Options (Continued)

Option Function

This Application selection drop-down list offers 5 options: 1) open-area, 2) in-duct,

Application 3) supervisory service (open-area), and 4) supervisory service (in-duct). See Section 3-5.5.1,
Application Definitions via Drop-Down Menu (below).
Pre-Alarm Level Use the Pre-Alarm Level edit box and the up/down arrows to increase/decrease levels.
Alarm Level Use the Alarm Level edit box and the up/down arrows to increase/decrease levels.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

3-5.6.1 APPLICATION DEFINITIONS VIA DROP-DOWN MENU

Table 3-11. Model DS-PS Photoelectric Smoke Detector Pre-Alarm, Alarm, Night Ranges

Application Pre-Alarm Range (%/foot) Alarm Range (%/foot) Night Range (%/foot)

Open Area 0.7 to 3.4 0.9 to 3.5 0.9 to 3.5

In-Duct 0.7 to 1.9 0.9 to 2.0 0.9 to 2.0
Supervisory Service
0.7 to 3.4 0.9 to 3.5 0.9 to 3.5
(Open-Area)
Supervisory Service
0.7 to 1.9 0.9 to 2.0 0.9 to 2.0
(In-Duct)

Note: If an installer enters a pre-alarm below 0.7% or alarm below 0.9%, the following prompt appears.

Figure 3-18. Is This A DS Series Detector? Prompt

• Answering <Yes> cancels the edit dialog and sets the threshold to the lowest possible setting (for DS Series
detector use).
• Answering <No> allows the setting and keeps the configuration edit dialog box open (for legacy detector use).

April 2018 3-16 P/N 06-237480-001

 Configuring SLC Devices

3-5.7 Heat Detector (THERMAL) (Model THD-7252) Settings Screen

Select Heat Detector Settings screen options as shown in Figure 3-19, then click <OK>. The Heat
Detector Settings screen options are described in Table 3-12.

Figure 3-19. Model THD-7252 Heat Detector Settings Screen

Table 3-12. Model THD-7252 Heat Detector Settings Screen Options

Option Function

DS Series This check box should NOT be selected if the heat detector is a Model THD-7252 detector.
Select this check box if the heat detector has an Optional Relay. When this check box is
Optional Relay
selected, the further options to activate 1) on EOC, or 2) upon alarm become available.
Spacing From this drop-down list, select 50-ft or 70-ft.
Pre-Alarm Level Use the Pre-Alarm Level up/down arrows to increase/decrease levels.
Alarm Level Use the Alarm Level up/down arrows to increase/decrease levels.
ITLCO/CTLCO
Select this check box to use this heat detector for Thermal Cycling.
Activation
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

The pre-alarm/alarm ranges for the thermal detectors are listed in Table 3-13.

Table 3-13. THD-7252 Thermal Detector Pre-Alarm/Alarm Ranges

Spacing (ft.) Pre-Alarm Range (°F) Alarm Range (°F)

50 80-135 135-155
70 80-135 135-145

P/N 06-237480-001 3-17 April 2018

Configuring SLC Devices

3-5.8 Heat Detector (THERMAL) (Model DS-HFS) Settings Screen

Figure 3-20. Model DS-HFS Heat Detector Screen

NOTE:

The DS-HFS thermal detector is UL Listed and FM Approved for alarm reporting at 135°F. The
DS-HFS does NOT have a configurable Alarm threshold. The Alarm value is 135°F at 50 feet
spacing. Spacing at 70 feet is not permitted for a DS-HFS detector.

Option Function

DS Series This check box should be selected if the heat detector is a Model DS-HFS detector.
Select this check box if the heat detector has an Optional Relay. When this check box is
Optional Relay
selected, the further options to activate 1) on EOC, or 2) upon alarm become available.
Pre-Alarm Level If Pre-Alarm is checked, the Pre-Alarm value is fixed at 110°F.
Alarm Level The Alarm Level is fixed at 135°F always.
ITLCO/CTLCO
Select this check box to use this heat detector for Thermal Cycling.
Activation
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

April 2018 3-18 P/N 06-237480-001

 Configuring SLC Devices

3-5.9 Heat Detector Thermal Cycling

A heat detector is configurable for thermal cycling as shown in Figure 3-21. The first alarm signal
from a heat detector is used to activate control unit-based outputs for a user-configurable period of
time known as the Initial Time Limit Cutoff Interval (ITLCO). The outputs silence or de-energize upon
expiration of the ITLCO interval. The outputs reactivate using the ITLCO time cycle if the system has
not been reset and at least one heat detector remains in the alarm state. If no heat detectors are in
the alarm state when the ITLCO time expires, the programmed outputs shall deactivate. If a heat
detector subsequently registers a temperature in excess of its alarm-threshold and the system has
not yet been reset, the outputs reactivate. The reactivated outputs silence or deactivate again after the
expiration of a second user-configurable period of time known as the Cyclical Time Limit Cutoff
(CTLCO)

The outputs only cycle and reactivate if the temperature at a heat detector subsequently exceeds the
detector's alarm threshold after the outputs silence or de-activate. All subsequent reactivation occur
for the CTLCO duration.

Valid entries for the ITLCO and CTLCO time periods are 0 to 180 seconds or 0 to 180 minutes,
configurable in either 1-second or 1-minute increments, respectively. These time periods are
specified in the screens that configure the various control unit-based outputs.

ITLCO CTLCO CTLCO CTLCO CTLCO

0
Ext. Sys & Outputs Ext. Sys &
Ext. Sys & Outputs Subsequent Shutoff Out. Shutoff
Subseq. Shutoff
Heat Detector Heat Detector
Heat Detector Subsequent Alarm Subsequent Alarm
Subsequent Alarm
Ext. System &
Outputs Initial Shutoff Ext. System & Outputs
Subsequent Shutoff
Heat Detector
Heat Detector System Reset
Initial Alarm
Subsequent Alarm

Time

Figure 3-21. Thermal Cycling Settings Screen

P/N 06-237480-001 3-19 April 2018

Configuring SLC Devices

3-5.10 PEGAsys Addressable Loop Module (PALM) Settings Screen

Select PALM Module Settings screen options as shown in Figure 3-22, then click <OK>. The PALM
Module Settings screen options are described in Table 3-14.

Figure 3-22. PALM Module Settings Screen

Table 3-14. PALM Interface Module Settings Screen Options

Option Function

The PALM can be configured as a “Non-Latching Input” only when “Supervisory Initiating
Non-Latching
Device” is selected as Reporting Device Type. Select this check box to enable non-latching
Input
input when the text is available (not dimmed).
Alarm Initiating Select this option to configure the PALM to create an alarm condition in the system when it
Device activates. Also see Table 3-24, Configurable Parameters, for more information.
Supervisory Select this option to configure the PALM for Supervisory Reporting (Not UL Listed or FM
Initiating Device Approved). Non-Latching Input is then available as a selectable option.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

April 2018 3-20 P/N 06-237480-001

 Configuring SLC Devices

3-5.11 Alarm (ALARM) Settings Screen

Select Alarm (ALARM) Module Settings screen options as shown in Figure 3-23, then click <OK>.
The Alarm Module Settings screen options are described in Table 3-15.

Note: The unpowered alarm contact can be either normally-open or normally-closed. Use
P/N 70-4X70X8-001 for normally-open contacts and P/N 70-4X7018-002 for normally-
closed contacts.

Figure 3-23. Alarm Settings Screen

Table 3-15. Alarm Module Settings Screen Options

Option Function

ITLCO/CTLCO
Select this check box to use this alarm module for Thermal Cycling.
Activation
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

3-5.12 Abort Station (ABORT) Settings Screen

Select Abort Station (ABORT) Module Settings screen options as shown in Figure 3-24, then click
<OK>. The Abort Station Module Settings screen options are described in Table 3-16.

Note: Address all abort stations within the range of 1 to 32 (if possible).
The unpowered abort switch can be either normally-open or normally-closed. Use P/N
70-4X70X8-001 for normally-open contacts and P/N 70-4X7018-002 for normally-
closed contacts.

Figure 3-24. Abort Station Settings Screen

P/N 06-237480-001 3-21 April 2018

Configuring SLC Devices

Table 3-16. Abort Station Module Settings Screen Options

Option Function

Device Operation Settings. See Section 3-5.12.1, Abort Station Settings Definitions,
Setting
below, for complete information.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

3-5.12.1 ABORT STATION SETTINGS DEFINITIONS

An AI Monitor Module configured as an abort station can be programmed to operate in any of the
following ways:

Table 3-17. Abort Definitions

Abort Type Definition

Reset to Full Time The countdown timer restores to the full delay period after the abort station is
Delay (Non-UL Listed) activated. The timer resumes the full countdown if the abort station is de-activated.
The timer restores to the full delay period if the abort station is re-activated with
any time remaining in the countdown. A system reset is required to clear the
countdown timer.
NOTE: The following abort-station operations are available, and are to be utilized at
the discretion of, and with the approval of, the applicable Authority Having
Jurisdiction.
Underwriters The countdown timer continues to count down after the abort station is activated,
Laboratories Style and halts with 10-seconds remaining. The timer resumes the countdown from 10
seconds if the abort station is de-activated. The timer restores to 10 seconds if the
abort station is activated or re-activated with less than 10 seconds remaining in the
countdown. A system reset is required to clear the countdown timer.
New York City (Not UL The countdown timer restores to the full delay period, plus 90 seconds, after the
Listed) abort station is activated. The timer resumes the countdown from the full delay
period, plus the 90 seconds, if the abort station is de-activated. The timer restores
to the full delay period plus 90 seconds if the abort station is re-activated with any
time remaining in the countdown. A system reset is required to clear the countdown
timer.
NOTE: EOC programming is required to implement the New York City abort station
operation. Refer to Appendix B.
Freeze and Hold at The countdown timer halts at the time remaining to expiration after the abort
Time Remaining (Non- station is activated. The timer resumes the countdown at the time remaining to
UL Listed) expiration if the abort station is de-activated. The timer again halts at the time
remaining to expiration if the abort station is re-activated with any time remaining
in the countdown. A system reset is required to clear the countdown timer.
Industrial Risk Insurers This option functions in a similar manner to the Underwriters Laboratories style,
(Non-UL Listed) except that countdown timer interruption is not allowed after the countdown timer
has begun to count down.

April 2018 3-22 P/N 06-237480-001

 Configuring SLC Devices

3-5.13 Supervisory Input (SUPV) Settings Screen

Select Supervisory (SUPV) Module Settings screen options as shown in Figure 3-25, then click
<OK>. The Supervisory Module Settings screen options are described in Table 3-18.

Note: The unpowered supervisory switch can be either normally-open or normally-closed. Use
P/N 70-4X70X8-001 for normally-open contacts and P/N 70-4X7018-002 for normally-
closed contacts.

Figure 3-25. Supervisory Input Settings Screen

Table 3-18. Supervisory Input Module Settings Screen Options

Option Function

Non-Latching Select this check box to enable non-latching input. Also see Table 3-24, Configurable
Input Parameters, for more information.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

P/N 06-237480-001 3-23 April 2018

Configuring SLC Devices

3-5.14 Waterflow Input (WATER) Settings Screen

Select Waterflow (WATER) Module Settings screen options as shown in Figure 3-26, then click
<OK>. The Waterflow Module Settings screen options are described in Table 3-19.

Note: The unpowered waterflow contact can be either normally-open or normally-closed. Use
P/N 70-4X70X8-001 for normally-open contacts and P/N 70-4X7018-002 for normally-
closed contacts.

Figure 3-26. Waterflow Input Settings Screen

Table 3-19. Waterflow Module Settings Screen Options

Option Function

Select this check box to enable Silenceable operation. Also see Table 3-24, Configurable
Silenceable
Parameters, for more information.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

3-5.15 Remote Releasing Module (RRM) Settings Screen

This section is divided into three parts:

• Configuring an RRM with an Actuator releasing device

• Configuring an RRM with an Initiator releasing device
• Configuring an RRM with a Solenoid releasing device

Select Remote Releasing Module (RRM) Settings screen options as shown in Figure 3-27, then click
<OK>.

April 2018 3-24 P/N 06-237480-001

 Configuring SLC Devices

The Remote Releasing Module Settings screen (with Actuator as Release Device) options are
described in Table 3-20.

Figure 3-27. Remote Releasing Module Settings Screen

(Using an Actuator as a Releasing Device)

Table 3-20. Remote Releasing Module Settings Screen (with Actuator as Releasing Device) Options

Option Function

Release Device From the drop-down list, select Actuator.

Releasing Use the edit boxes and the up/down arrows to configure the RRM to be in none, some, or all of
Group(s) the 7 release groups. Each release group can contain only 20 RRMs.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

P/N 06-237480-001 3-25 April 2018

Configuring SLC Devices

3-5.15.1 CONFIGURING AN RRM WITH AN INITIATOR RELEASING DEVICE

Select Remote Releasing Module (RRM) Settings screen options as shown in Figure 3-28, then click
<OK>. The Remote Releasing Module Settings screen (with Initiator as Release Device) options are
described in Table 3-21.

Figure 3-28. Remote Releasing Module Settings Screen

(Using an Initiator as a Releasing Device)

Table 3-21. Remote Releasing Module Settings Screen (with Initiator as Releasing Device) Options

Option Function

Release Device From the drop-down list, select Initiator.

Releasing Use the edit boxes and the up/down arrows to configure the RRM to be in none, some, or all of
Group(s) the 7 release groups. Each release group can contain only 20 RRMs.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to negate entered Settings and return to previous screen.

April 2018 3-26 P/N 06-237480-001

 Configuring SLC Devices

3-5.15.2 CONFIGURING AN RRM WITH A SOLENOID RELEASING DEVICE

Select Remote Releasing Module (RRM) Settings screen options as shown in Figure 3-29, then click
<OK>. The Remote Releasing Module Settings screen (with Solenoid as Release Device) options
are described in Table 3-22.

Figure 3-29. Remote Releasing Module Settings Screen

(Using a Solenoid as a Releasing Device)

P/N 06-237480-001 3-27 April 2018

Configuring SLC Devices

Table 3-22. Remote Releasing Module Settings Screen (with Solenoid as Releasing Device) Options

Option Function

Release Device From the drop-down list, select Solenoid.

These times apply to solenoid-activated discharge valves. From the drop-down list, select
from: 90 seconds, 10 minute soak, 15 minute soak, on until reset, thermal cycling, or
custom time. These times apply to solenoid-activated discharge valves. If custom time is
Activation Time
chosen from this drop-down list, its edit box and up/down arrows appear immediately below
“Activation Time.” Use the edit box and up/down arrows to enter between 2 to 18,000
seconds.
Non-Power
Select this check box to disable short-circuit detection.
Limited
2 Solenoids
Select the 2 Solenoids Connected check box if two solenoids are connected for releasing.
Connected
A Squirt Device is a manually-operated, dead-man-type switch that is used to reactivate an
extinguishing system after it is automatically deactivated following the expiration of the initial-
Squirt time-limit-cutoff interval (ITLCO). The extinguishing system will reactivate when the squirt
Reactivation/ switch is operated and remain active as long as the user maintains the squirt switch in the
Spurt active position. The extinguishing system will de-energize when the operation of the squirt
Activation device ceases. A Spurt Device is a normally-open, dead-man-type switch. It is similar in
functionality to a manual-release station with the exception that its associated extinguishing
system will de-energize when the Spurt Device is released.
Releasing Use the edit boxes and the up/down arrows to configure the RRM to be in none, some, or all of
Group(s) the 7 release groups. Each release group can contain only 20 RRMs.
If applicable, the release circuit is configurable for thermal cycling according to the alarm or
non-alarm states of its associated automatic heat detectors. Refer to Section 3-5.7, Heat
Detector (THERMAL) (Model THD-7252) Settings Screen, for a description of thermal cycling
via a Model THD-7252 Heat Detector. A thermal-cycling release circuit is configured by
selecting “Thermal Cycling” from the Activation Time drop-down menu.
ITLCO Time/
CTLCO Time Note: The cyclical release-circuit activation is overridden by an
alarm signal from any associated alarm-initiating device
other than a heat detector configured for thermal cycling.
The release circuit then latches into the activated state and
remains activated until it is deactivated by another alarm
condition or until the control unit is reset.
OK After Settings are completed, click <OK> to apply Settings to device.
Cancel Click <Cancel> to abandon changes and return to previous screen.

April 2018 3-28 P/N 06-237480-001

 Configuring SLC Devices

3-5.16 Configuring An Isolation Macro Input

Select Isolation Macro icon and select the desired Macro number from the settings dialog as shown
in Figure 3-30. Click OK and the device address is assigned to the Isolation Macro.

When activated, an Isolation Macro input causes the control unit to execute the isolations defined by
the macro. Deactivating the Isolation Macro Input will deisolate all circuits isolated by the macro. A
'switch fault' is indicated if the Isolation Macro Input is left active and the keypad is used to execute
the macro de-isolation. The unpowered Isolation Macro input can be either normally-open or
normally closed. Use P/N 70-4X70X8-001 for normally-open contacts and P/N 70-4X7018-002 for
normally-closed contacts.

Figure 3-30. Isolation Macro Number Menu

Table 3-23. Isolation Macro Input Options

Option Function

Isolation Macro Select the macro number (1-4) executed by activating this device. To be assigned, the macro
Number must exist.
OK Click to apply settings to the selected device.
Cancel Click to cancel and return to the previous screen.

P/N 06-237480-001 3-29 April 2018

Configuring SLC Devices

3-6 OTHER SLC INITIATING DEVICES

The following SLC initiating devices do not have specific screens to further define functionality. They
are all represented by an AI Monitor Module that is monitoring an unpowered switch.

• Manual Alarm. A manual alarm station initiates an alarm when pulled. Address all manual
alarm stations within the range of 1 to 32 (if possible).
• Manual Release. A manual release switch is used to initiate release circuits.
• Normal Input. A normal is a Non-Latching initiating device. Point-specific outputs can be
assigned to a normal device in the EOC section of the configuration program. The unpowered
normal device can be either normally-open or normally-closed. Use P/N 70-4X70X8-001 for
normally-open contacts and P/N 70-4X7018-002 for normally-closed contacts.
• Trouble Input. A trouble input creates a trouble condition and is a Non-Latching initiating
device. Point-specific outputs can be assigned to the trouble input in the EOC section of the
configuration program. The unpowered trouble input can be either normally-open or normally-
closed. Use P/N 70-4X70X8-001 for normally-open contacts and P/N 70-4X70X8-002 for
normally-closed contacts.
• Fan Restart. A fan-restart point is used to de-activate specific addressable relays (i.e., AOs) after
the control unit has been reset. The AOs must be configured for fan-restart operation. The
unpowered fan-restart switch must be a Non-Latching normally-open contact. Use P/N
70-4X70X8-001 to monitor the fan-restart switch.
• Drill. A drill switch is used to initiate a fire drill via an external, field-installed switch. The fire
drill begins when the drill switch is activated, and stops when the drill switch is de-activated. The
Drill process can also be canceled using the Silence or Reset buttons. A 'switch fault' will be
indicated if the Drill Input is left active after a silence or reset operation. The unpowered drill
input can be either normally-open or normally closed. Use P/N 70-4X70X8-001 for normally-
open contacts and P/N 70-4X7018-002 for normally-closed contacts.
• Alarm Silence. An alarm silence switch is used to duplicate the functionality of the control unit's
alarm silence switch via an external, field installed switch. The alarm silence switch de-activates
silenceable outputs when the alarm silence switch is activated. The input should be a momentary
switch and a “switch fault” will be indicated if the Silence Input is left active. The unpowered
silence input can be either normally-open or normally closed. Use P/N 70-4X70X8-001 for
normally-open contacts and P/N 70-4X7018-002 for normally-closed contacts.
Note: For control units configured for ULC Operation, this device cannot be used for
Releasing Service Signal Silence applications. Refer to the Releasing Service Signal
Silence bullet which follows.
• Spurt. The unpowered spurt device must be a normally-open, dead-man type switch. Use
Normally Open (N.O.) Addressable Input Module listed in ARIES-MLX Control Unit Installation,
Operation and Maintenance Manual.
• Squirt. The unpowered squirt device must be a normally-open, dead-man type switch. Use
Normally Open (N.O.) Addressable Input Module listed in ARIES-MLX Control Unit Installation,
Operation and Maintenance Manual.

April 2018 3-30 P/N 06-237480-001

 Configuring SLC Devices

• Releasing Service Signal Silence (RSSS). A Releasing Service Signal Silence station is used in
combination with EOC to silence signal outputs associated with pre-release and discharge. The
station is an external, field-installed switch mounted within 18 in (46 cm) from the control unit.
The Releasing Service Signal Silence station, P/N 76-800600-101, includes a key switch input
that remains in the “ON” state while the Release Service Signal outputs are silenced. Switching
to the “OFF” state will resound silenced outputs. A ‘switch fault’ will be indicated if the input is
activated during a non-alarm state. The device when unpowered is normally-open.
Note: Additional Configuration Requirements for Releasing Service Signal Silence:
Use of the Release Service Signal Silence input requires additional EOC programming
and an LED Annunciator Module LED dedicated to Release Service Signal Silence
indication. Refer to Section F-7 of Appendix F, Canadian Applications in the ARIES-
MLX Control Unit Installation, Operation and Maintenance Manual, P/N 06-237479-
001, for additional explanation.
An EOC example for silencing releasing service signal outputs on a Canadian-
application control unit is presented here. This EOC program is presented for
instructional purposes only and will need to be customized for the control unit in use.
In this example, the following configuration applies:
• Release Silence AI on SLC 1 at address 20 to be used for silencing release service
signal outputs.
• Alarm devices on SLC 1 at addresses 1 through 10 used to initiate a release.
• LAM with address 1 configured with LED 30 to be yellow in color.

001 L1:20=I2 $ RELEASE SERVICE SIGNAL SILENCE SWITCH

002 I2*C2=LED1:30,NSG2 $ SILENCE SG2, THE RELEASE SIGNAL
003 $ FIRST ALARM
004 L1:1#10=I1 $ FIRST ALARM
005 I1*NC2*NC3=SG1 $ FIRST ALARM SIGNAL OUTPUT
006 $ SECOND ALARM, PRE-DISCHARGE
007 I1>1=SG2/60,NSG1,C2 $ SECOND ALARM, START COUNTDOWN
008 $ DISCHARGE COUNTDOWN
009 D(C2,30)=AR1,SG2/C,C3 $ DISCHARGE – AR1
010 $ RESOUNDING
011 I1*C2*NC3=SG2/60,NSG1,NLED1:30 $ PRERELEASE STATE, AFTER SILENCE
012 I1*C3=SG2/C,NLED1:30 $ DISCHARGE STATE, AFTER SILENCE
013 C2*NI2*NC3=SG2/60,NLED1:30 $SILENCE OFF, TURN SG2 BACK ON
014 C3*NI2=SG2/C,NLED1:30 $ SILENCE OFF, TURN SG2 BACK ON

P/N 06-237480-001 3-31 April 2018

Configuring SLC Devices

• Reset. A reset switch is used to duplicate the functionality of the control unit's reset switch via
an external, field installed switch. A 'switch fault' will be indicated if the Reset Input is left active.
The unpowered reset input can be either normally-open or normally closed. Use P/N 70-4X70X8-
001 for normally-open contacts and P/N 70-4X7018-002 for normally-closed contacts.
• Acknowledge. An acknowledge switch is used to duplicate the functionality of the control unit's
acknowledge switch via an external, field installed switch. A 'switch fault' will be indicated if the
ACK Input is left active. The unpowered ACK input can be either normally-open or normally
closed. Use P/N 70-4X70X8-001 for normally-open contacts and P/N 70-4X7018-002 for
normally-closed contacts.
Note: This feature does not meet UL requirements unless there is a visible display at the
acknowledge switch that indicates what is being acknowledged.

Table 3-24. Configurable Parameters

CONFIGURABLE
EXPLANATION
PARAMETER

A device such as a smoke detector or manual station configured to

create an alarm condition in the system when it activates. Input
devices that can cause an alarm include: 1) Ion Smoke Detector (not
configured for “Supervisory Service”); 2) Photo Smoke Detector (not
Alarm Initiating Device configured for “Supervisory Service”); 3) Heat Detector (also referred
to as a Thermal Detector); 4) Alarm; 5) Manual Alarm; 6) Manual
Release; 7) Waterflow; 8) Addressable Alarm-Line Module (not
configured for “Overheat Display”); and 9) AIM or PALM Module (not
configured as a “Supervisory Initiating Device”).
Alarm verification allows a fire alarm system to delay an evacuation
signal from being generated as the result of an alarm report from a
smoke detector. The fire alarm system waits for a second alarm report
from the smoke detector that issued the initial alarm report or from
Alarm Verification any other alarm-initiating device before it generates the evacuation
signal. The fire alarm system resumes normal operations if it does not
receive a second alarm report within the alarm configuration time
period. See Chapter 6 of NFPA 72, National Fire Alarm Code, 2002
Edition, for details.
The periods of time during which smoke detector sensitivities can be
Day/Night/Weekend automatically adjusted by the control unit. Day and night periods are
defined in the Globals Tab.
A switch connected to a monitor module designed to de-energize
control modules that do not resume normal operation after a system
Fan Restart reset. The monitor module and control modules must be configured
for fan-restart operation. The control modules only de-energize and
resume normal operation after the fan restart switch is activated.
General Alarm List The set of outputs that are activated by any alarm initiating device.

April 2018 3-32 P/N 06-237480-001

 Configuring SLC Devices

Table 3-24. Configurable Parameters (Continued)

CONFIGURABLE
EXPLANATION
PARAMETER

Some SmartOne alarm initiating devices can be configured for Non-

Latching operation. Non-Latching operation refers to the special way
that “Alarm-Off” messages from initiating devices are processed by the
ARIES-MLX Control Unit. Each SmartOne alarm initiating device
transmits an “Alarm-On” message when, in the case of an automatic
initiating device, it detects a fire signature in excess of its configured
threshold value, and, in the case of an AI Monitor Module for a
normally-open contact, it detects a contact closure from the switch
that it is monitoring. The SmartOne automatic alarm-initiating devices
Non-Latching Input and monitor modules also transmit “Alarm-Off” messages when the
detected fire signature drops below the configured threshold value
and when the contact closure is removed, respectively. The ARIES-
MLX Control Unit always displays every “Alarm-On” message, but
does not display an “Alarm-Off” message unless the alarm-initiating
device is configured for Non-Latching operation.

Note: Only inputs configured for supervisory service have the option
of being configured for Non-Latching. Inputs configured for
Thermal Cycling are automatically configured for Non-Latching.
Positive Alarm Sequence (i.e., PAS) allows a fire-alarm system to delay
an evacuation signal from being generated as the result of an alarm
report from a smoke detector. The operator must acknowledge the
initial alarm report within 15 seconds of its receipt, or the normal
evacuation signals activate. Personnel have a user-programmable
period of up to 3 minutes to investigate the nature of the alarm and
reset the system if they acknowledge the initial alarm within 15
PAS seconds. The evacuation signal activate if the system is not reset
during the investigation period. The fire-alarm system also generates
the evacuation signal if a second smoke detector configured for PAS or
any other initiating device transmits an alarm signal during either the
initial-acknowledgement period or the investigation period. The fire-
alarm system resumes normal operations if it is reset within the
investigation period. See Chapter 6 of NFPA 72, National Fire Alarm
Code, 2002 Edition, for details.
The Pre-Alarm State occurs when a SmartOne automatic initiating
device such as a smoke detector senses a fire signature that is below
Pre-Alarm Reporting
its configured alarm threshold value but above a lower threshold value
called the “pre-alarm” threshold.
A method of scheduling the de-activations of control modules that
have been activated as the result of an alarm condition. The system
can be programmed to insert a delay of up to 15 seconds between the
de-activation times of control modules that resume normal operations
Sequential Deactivation
following either a system reset or a fan-restart command. The control
modules must be configured for sequential deactivation and the delay
period is defined in the Globals Tab. Up to 16 control modules can be
programmed for sequential deactivation.
An output that changes its state of activation upon commands issued
by the control unit's SILENCE Switch. The output de-energizes if an
Silenceable alarm condition exists and if it is activated when the SILENCE Switch
is pressed, and re-activates if the alarm condition still exists and it is
de-energized when the SILENCE Switch is pressed.

P/N 06-237480-001 3-33 April 2018

Configuring SLC Devices

Table 3-24. Configurable Parameters (Continued)

CONFIGURABLE
EXPLANATION
PARAMETER

A Squirt Device is a manually-operated, dead-man-type switch that is

used to reactivate an extinguishing system after it is automatically
deactivated following the expiration of the initial-time-limit-cutoff
Squirt Device interval (ITLCO). The extinguishing system will reactivate when the
squirt switch is operated and remain active as long as the user
maintains the squirt switch in the active position. The extinguishing
system will de-energize when the operation of the squirt device ceases.
A Spurt Device is a normally-open, dead-man-type switch. It is similar
in functionality to a manual-release station with the exception that its
Spurt Device
associated extinguishing system will de-energize when the Spurt
Device is released.
A test mode in which the control unit responds to alarm-initiating
signals by pulsing designated notification-appliance circuits for one
second and recording the alarm-initiating device's alarm report in the
Walk Test Log. This is referred to as a normal walk test. The alarm-
Walk Test initiating devices must be activated for Walk Test via the control unit's
Test sub-menu, and the NACs must be configured for Walk Test
activation. A Silence Walk Test does not activate the NACs, but
records each alarm-initiating device's alarm report in the Walk Test
Log.

April 2018 3-34 P/N 06-237480-001

 Event Output Control (EOC)

CHAPTER 4
EVENT OUTPUT CONTROL (EOC)

4-1 INTRODUCTION

The procedures in Chapter 2 discussed defining the scope of a specific application and assigning
operating characteristics and functionality to SLC-based initiating and control devices and to control
unit-based output circuits. This chapter discusses how to create the operating sequence (i.e., the
relationships between the output device(s) and the initiating point(s) for an ARIES®-MLX system).

4-1.1 Before You Begin

Before reading the pages which follow, refer to Table 4-6 to familiarize yourself with the look of Event
Output Control (EOC) operators and lines of code. Every operator and associated concepts involved
in building an EOC program are explained in logical order in the next paragraphs.

Note: In many examples of EOC code throughout this chapter, comments are preceded by a “$”.
For example: “$ necessary to set C1 to zero when I1 goes to zero.” Regular use of embedded
comments in EOC code is highly recommended for ease of programming.

4-1.2 Event Output Control

Event Output Control (EOC) is the set of instructions that are be executed in response to point-
specific alarm, supervisory, or trouble events. The objective is to trigger physical outputs (i.e.,
notification appliance circuits, release circuits and control modules) as the result of one or more
initiating event(s) in accordance with the approved sequence of operations.

The general form of an EOC instruction is “expression=designated outputs”. An expression can be

a simple argument (see Section 4-2.1) or an compound argument (see Section 4-2.2).

“Designated outputs” activate whenever:

• the “expression” becomes True (when it had been False);

• whenever the “expression” becomes non-Zero (when it had been Zero);
• whenever the “expression” becomes greater than its value on the previous pass through the EOC
program (a pass is made whenever an event happens on the system).

If the expression satisfies the above rules, then activate “designated outputs”.

4-2 CONSTRUCTING ARGUMENTS

The constituents (i.e., variables) of the "expression" are of two general types:

• Independent variables that consist of physical initiating devices (automatic detectors or

monitor modules). The types of physical initiating devices that are supported were
discussed in Chapter 2.
• Dependent variables (i.e., Counting Identifiers, State Variables, and Incrementing Variables)
assume values during program execution. Dependent variables are incremented or change state
as the result of some prior independent variable activation, or their initial state. They are
placeholders either for the arguments that changed them, or for the execution of a specific EOC
command.

P/N 06-237480-001 4-1 April 2018

Event Output Control (EOC)

Table 4-1 summarizes the types of initiating devices and their effects on the system's physical
and virtual outputs.
Table 4-1. Initiating Devices

Initiating Device Physical Outputs Virtual Outputs

Latching Counting State Incrementing

Non-
Device Type Event Created Initiating Latching* Logical Variable* Variable
Latching**
Device Identifier** (Cx) (Qx)

Ion. Det. Pre-Alarm No No Yes Yes Yes Yes

Ion. Det. Alarm Yes Yes No Yes Yes Yes
Ion. Det. Supervisory Prog (Y/N) No Yes Yes Yes Yes
Photo. Det. Pre-Alarm No No Yes Yes Yes Yes
Photo. Det. Alarm Yes Yes No Yes Yes Yes
Photo. Det. Supervisory Prog (Y/N) No Yes Yes Yes Yes
Heat Det. Pre-Alarm No No Yes Yes Yes Yes
Heat Det. Alarm Prog (Y/N)*** Yes No Yes Yes Yes
Heat Det. Cycling No No Yes Yes Yes Yes
CPDI Duct Det. Pre-Alarm No No Yes Yes Yes Yes
CPDI Duct Det. Alarm Yes Yes No Yes Yes Yes
CPDI Duct Det. Supervisory Prog (Y/N) No Yes Yes Yes Yes
PSDI Duct Det. Pre-Alarm No No Yes Yes Yes Yes
PSDI Duct Det. Alarm Yes Yes No Yes Yes Yes
PSDI Duct Det. Supervisory Prog (Y/N) No Yes Yes Yes Yes
HSD with PALM/ Pre-Alarm No No Yes Yes Yes Yes
AIM
HSD with PALM/ Alarm Prog (Y/N) Yes No Yes Yes Yes
AIM
HSD with PALM/ Supervisory Prog (Y/N) No Yes Yes Yes Yes
AIM
HSD (Level 1) Pre-Alarm No No Yes Yes Yes Yes
via IIM
HSD (Level 2) Pre-Alarm No No Yes Yes Yes Yes
via IIM
HSD (Level 3) Alarm Prog (Y/N) Yes No Yes Yes Yes
via IIM
HSD (Level 4) Alarm Prog (Y/N) Yes No Yes Yes Yes
via IIM
Manual Station Alarm Yes Yes No Yes Yes Yes
Manual Release Alarm Yes Yes No Yes Yes Yes
Alarm Contact Alarm Prog (Y/N)*** Yes No Yes Yes Yes
Abort Station Abort No No Yes Yes Yes Yes
Waterflow Switch Alarm Yes Yes No Yes Yes Yes
Supv. Switch Supervisory Prog (Y/N) No Yes Yes Yes Yes
Normal None No No Yes Yes Yes Yes
Trouble Trouble No No Yes Yes Yes Yes

April 2018 4-2 P/N 06-237480-001

 Event Output Control (EOC)

Table 4-1. Initiating Devices

Initiating Device Physical Outputs Virtual Outputs

Latching Counting State Incrementing

Non-
Device Type Event Created Initiating Latching* Logical Variable* Variable
Latching**
Device Identifier** (Cx) (Qx)

AAM Pre-Alarm No No Yes Yes Yes Yes

AAM Alarm Yes Yes No Yes Yes Yes
AAM Overheat. No No Yes Yes Yes Yes
* Does not track initiating devices. ** Tracks initiating devices.
*** Heat Detectors and AI’s configured for “Thermal Cycling” are automatically configured as
“Non- Latching Input.”

P/N 06-237480-001 4-3 April 2018

Event Output Control (EOC)

Table 4-2. Input Symbolic Representations

SLC Initiating Device Lx:y where x = SLC Loop number (1-8) and y is the SLC
Device address (1-255)
State Variables Cx where x = variable number (1-255)
Incrementing Variables Ix where x = variable number (1-255)
Counting Variables Qx where x = variable number (1-255)

4-2.1 Simple Arguments

A simple argument consists of a single independent or dependent variable. The physical initiating
devices are represented by their SLC addresses or IIM address. The designator “HSD” prefixes HSSD
addresses when an IIM Card is used to network AnaLASER-II or ORION-XT smoke detectors.

4-2.2 Compound Arguments

A compound argument consists of a combination of two or more simple arguments. Both

independent and dependent variables can be combined in a compound argument. The combining
operators used to create compound arguments are shown in Table 4-3.

Table 4-3. Combining Operators for Initiating Arguments

Operator Symbol

And *
Or +
THRU #

Each simple argument component of a compound argument constructed with "OR" or the
"THRU" Operators, is capable of causing execution (or re-execution) of a particular EOC
instruction. The 'OR' and '#' operators actually perform addition operations with the result
being the sum of all terms that are active. This type of EOC instruction is executable or re-
executable until all the simple argument components become true if the initiating devices are
programmed for latching operation. Virtual outputs are capable of triggering the activation of
physical outputs in another EOC statement when their value is changed. They are also capable
of continuously reactivating these outputs when their value subsequently changes again if the
outputs have been reactivated or silenced.

All simple argument components of a compound argument constructed with the "AND" Operators
must be true for the compound argument to be true.

The truth or falsehood of a compound argument follows the rules of ordinary Algebra. More than one
type of combining operator can be used to construct a particular compound argument. The hierarchy
for operator execution is as follows:

• “THRU” operators
• Compound arguments in parenthesis
• “NOT” operators
• “AND” operators
• “OR” operators
Note: The "THRU" operator is the most tightly bound, even more than parentheses (i.e., one
cannot code 3#(…) or (…)#4 in an EOC line). Compound arguments are evaluated
sequentially from left to right on an EOC statement when all operators are of equal
hierarchy.

April 2018 4-4 P/N 06-237480-001

 Event Output Control (EOC)

4-2.2.1 “AND” OPERATOR

In versions of some previous control units, the ‘*’ “AND” operator was strictly a logical operator
resulting in a TRUE (1) or FALSE (0) value.

The “AND” operator has been modified and enhanced to provide support for resounding. The result
of the ‘X*Y’ operation shall be the value of the greater of the two factors as long as both factors are
non-zero. If more than two factors are involved, the factors are read and processed from left to right.
For example,

L1:1#10=I1
L1:20#30=C2
L1: 50#60=C3
I1*C2*C3=SG1,I4
If detector 1 activates, and detectors 25 and 26 activate and device 52 activates, then SG1
turns ON and I4 is set to 2. I2 is the greatest of the 3 non-zero variables.
Subsequently if detector 5 alarms, only the outputs of line 1 are processed, and I1 is set to
2. The result of line 4 remains equal to 2, so SG1 does not reactivate once it has been
silenced.
If an additional device from the range L1: 50#60 activates, the C3 variable remains TRUE
(equal to 1), so the right hand side of line 4 again does not get processed.
Should another detector from L1:1#10 or L1:20#30 alarm, then line 4 result, and I4,
becomes 3 and SG1 re-activates if it had been silenced.
When there’s no change in state on the left hand side of the equation, the right hand side
does not get processed. In order to assure processing of every change of state, additional
‘C’ variables or ‘Q’ variables are necessary, and extra lines of EOC are necessary.
The ‘C’ variables are limited to being set to the values of 0(FALSE) or 1(TRUE), while ‘I’
variables are set to values representing the result of evaluating the left hand side. The ‘Q’
variables are incremented, when on the right hand side, whenever the left hand side
evaluates to a value that is greater than the value to which it had evaluated for any of the
previous passes on the EOC program. These concepts along with the new “AND” definition
are used to provide support for resounding crossed-zone applications.
Refer to the following example, using non-latching initiating devices.
1. L1:1#10=I1,C1
2. L1:20#30=I2,C2
3. L1:50#60=I3,C3
4. NI1=NC1 $ necessary to set C1 to zero when I1 goes to zero
5. NI2=NC2 $ necessary to set C2 to zero when I2 goes to zero
6. NI3=NC3 $ necessary to set C3 to zero when I3 goes to zero
7. I1*C2*C3=SG1,I4
8. C1*I2*C3=SG1,I5
9. C1*C2*I3=SG1,I6
Since the ’C1’ & ‘C2’ & ‘C3’ variables can only be 0 or 1, lines 7, 8 and 9 result in the value
of I1, I2 and I3 respectively, when all three ‘C’ variables are non-zero. Therefore, any
changes of state in the three ranges are processed and SG1 resounded whenever necessary,
once at least one detector in each zone has become active, at some time.

P/N 06-237480-001 4-5 April 2018

Event Output Control (EOC)

4-3 OUTPUTS

An output can be a physical output or a virtual output. Refer to Table 4-1 for how physical outputs
track or do not track the activation states of their associated initiating devices.

4-3.1 Physical Outputs

Physical outputs can be any of the following types:

1. Control Unit-Based Circuits. The types of outputs that are supported, with symbolic
representations, are listed in Table 4-4 below.

Table 4-4. Control Unit-Based Outputs

Output Type Symbolic Representation

NAC No. 1 SG1

NAC No. 2 SG2
Combo Number 1:
Release Circuit AR1
NAC SG3
Combo Number 2:
Release Circuit AR2
NAC SG4
Programmable Relay No. 1 RY1
Programmable Relay No. 2 RY2
Programmable Relay No. 3 RY3
Expansion RNAC Circuits configured as NACs SGx:y where x = the RNAC module Logical address
(1-24) and y = the RNAC circuit number (1-3)
Expansion RNAC Circuits Configured for Release ARx:y where x = the RNAC module Logical address
(1-24) and y = the RNAC circuit number (1-3)
Expansion Relay Circuits RYx:y where x = the Relay module Logical address (1-24)
and y = the Relay circuit number (1-4)
SLC Output Device Lx:y where x = SLC Loop number (1-8) and y is the SLC
Device address (1-255)
LAM Output LEDx:y where x = the LAM address (1-16) and y = the
LED output (1-48)
State Variables Cx where x = variable number (1-255)
Incrementing Variables Ix where x = variable number (1-255)
Counting Variables Qx where x = variable number (1-255)

2. SLC-Based Modules. The types of modules that are supported are as follows:
– Addressable Control Modules (AOs)
– Addressable Signal Modules (ASMs)
– Remote Releasing Modules (RRMs)
Note: Each SLC-based module is referenced by its signaling line circuit address.

April 2018 4-6 P/N 06-237480-001

 Event Output Control (EOC)

3. Remote LAM Modules. A specific LAM output is referenced as follows:

LEDy:z where:
y is the module address, 1 to 16
z is the specific LED output circuit, 1 to 48.

4. Remote ATM-LED/ATM-Relay Modules. A specific ATM output is referenced as follows:

AMy:z where:
y is the module address, 1 to 16
z is the specific LED or Relay output circuit, 1 to 32.

4-3.2 Virtual Outputs

Virtual outputs consist of:

– State Variables
– Incrementing Variables
– Counting Identifiers

Counting Identifiers (Ix) follow the result of evaluating the left hand side of the EOC equation which
can include being set to zero. Saved State Variables (Cx) and saved Incrementing Variables (Qx) are
zeroed ONLY at reset and system initialization or when a subsequent “NOT” operation is executed to
reset them (i.e., such as “...=NCx”, or “...=NQx”).

4-3.2.1 COUNTING IDENTIFIERS (IX)

A Counting Identifier, symbolized by Ix, is initially activated by the execution of a specific EOC
statement. The Counting Identifier becomes a placeholder for the expression that activated it. They
can then be used as a substitute for the triggering argument in a subsequent EOC statement to
activate additional physical outputs or to operate on other dependent variables. Each can also be
used as a substitute for its triggering parameter in an EOC function (see Section 4-6). Counting
Identifiers assume the initiating device type identities in the expressions that activated them and track
the activation or non-activation states of their associated initiating device type arguments as shown
in Table 4-1.

The values assigned to a Counting Identifier depend upon the type of argument that activated it. They
assume the value of a counter when it is associated with a compound argument constructed with "OR"
or "THRU" Operators. They assume the value of “One” (“TRUE) or “Zero” (“FALSE”) when they are
associated with a simple argument, with an argument constructed exclusively with a saved State
Variable (see Section 4-3.2.2) or a saved Incrementing Variable (see Section 4-3.2.3), or with an
argument constructed exclusively with the Initiating Event Counting Function (see Section 4-6.16).

Consider the following example of the use of a Counting Identifier as a substitute for a set of 100
alarm initiating devices addressed from 1 to 100, and therefore used as a counter:

L2:1#100=I1 $ Equation (4-1)

The value of I1 could range anywhere from 0 to 100 depending upon the number of concurrent and
active alarm initiating events that occur within the set of 100 alarm initiating devices. Equation 4-1
represents a common application for a Counting Identifier where it triggers the initial activation and
subsequent resounding of a notification appliance circuit via a statement like the following upon the
receipt of one or more alarm initiating events:

I1=SG1 $ Equation (4-2)

P/N 06-237480-001 4-7 April 2018

Event Output Control (EOC)

Any subsequent alarm increments the Counting Identifier, which creates the ability to resound
notification appliance circuit SG1 if silenced.

Now consider the following example of the use of a Counting Identifier as a substitute for the activation of
two groups of alarm initiating devices, one in the address range 1 to 50 and the other in the address range
51 to 100:

L1:1#50*L1:51#100=I1 $ Equation (4-3)

The value of I1 shall be “zero”’, “one”, or more depending on how may detectors in the ranges of
L1:1#50 and L1:51#100 are in alarm. This equation is not sufficient to handle resounding. Refer to
section 4-2.2.1 for proper programming. Equation 4-3 represents a common application for a
Counting Identifier where it triggers the activation of a Delay Function (see Section 4-6.3 or
Section 4-6.4) for subsequent activation of outputs:
D(I1,30)=AR1 $ Equation (4-4)

The output AR1 is not activated by the Delay Function in Equation 4-4 if I1 becomes "Zero" prior to
the expiration of the 30-second delay period. I1 returns to “Zero” if and when there are no longer
detectors in alarm in the range L1:1#50 or the range L1:51#100.

It is good practice to use a separate Counting Identifier as a substitute for one and only one
expression. A Counting Identifier being used as a counter and activated and incremented by multiple
expressions is separately and independently incremented by each expression, which can be
confusing.

Increments for the Counting Identifier that are triggered by different expressions are not cumulative.
A Counting Identifier’s current value is determined by the value assigned to it on the most recently
executed EOC command line, in the EOC program. Likewise, the truth or falsehood assigned to a
Counting Identifier is the value assigned to it on the most recently executed EOC command. It is a
dangerous practice to use a Counting Identifier as a logic variable (True or False variable) for two or
more expressions, particularly where fire extinguishing systems and critical process control
interlocks are concerned.

All Counting Identifiers are re-initialized either to zero or "FALSE" upon a system reset.

4-3.2.2 STATE VARIABLE (CX)

A State Variable, symbolized by Cx, is a binary, True or False, variable that is initialized to the
"FALSE" (= 0) value upon EOC file upload. It can be subsequently set to the "TRUE" (= 1) value by
the execution of a particular EOC statement. Like the Counting Identifier, the State Variable becomes
a placeholder for the argument that activated it. Accordingly, it can then be used as a substitute for
the triggering argument in a subsequent EOC statement to activate additional physical outputs or to
operate on other dependent variables. It can also be used as a substitute for its triggering argument
in an EOC function (see Section 4-6).

State Variables assume the initiating device type identities of the arguments that activated them, but
do not track the activation or non-activation states of their associated initiating device type arguments
as shown in Table 4-1. A State Variable, once activated and assigned a "TRUE" value, can only be re-
assigned to its initial "FALSE" value by the subsequent execution of another EOC statement that re-
initializes it to "FALSE" via the “NOT” Operator (see Section 4-5) or a successful system reset
operation.

Do not use State Variables as counters to be associated with a compound argument constructed with
"OR" or "THRU" Operators. They do not count, but only become “TRUE” (1).

April 2018 4-8 P/N 06-237480-001

 Event Output Control (EOC)

Consider the following example of the use of a State Variable as a substitute for the activation of two
alarm initiating devices anywhere in the address range 1 to 100 (see Section 4-6.16 for a description
of the Initiating Event Counting Function):

(L3:1#100)>1=C1 $ Equation (4-5)

The value of C1 is either "TRUE" or "FALSE" depending upon the truth or falsehood of the left hand
side of Equation 4-5. The equation represents a common application for a State Variable where it
triggers the activation of a Delay Function (see Section 4-6.3 or Section 4-6.4) for subsequent
activation of outputs:

D(C1,30)=AR1 $ Equation (4-6)

The output AR1 is activated unconditionally by the Delay Function in Equation 4-6 unless the State
Variable C1 is re-initialized to "FALSE" by the execution of a subsequent EOC statement with an
output "NC1" prior to the expiration of the 30-second delay period. See Section 4-5 for a description
of the "NOT" Operator.

All State Variables are re-initialized to "FALSE" upon a system reset.

The “C” state variable cannot be used for activating silenceable outputs. The “C” state
variable is not a counting variable and, therefore, will not reactivate or resound
WARNING silenceable outputs on subsequent alarms after the control unit or system has been
silenced.

The following examples show correct and incorrect methods for activating silenceable outputs on a
single node and a networked system:

Single Node Silenceable Output Activation:

Correct Method: Incorrect Method:

L1:1#10=I1 L1:1#10=C1

I1=SG1 C1=SG1

Remote Node Silenceable Output Activation:

Correct Method: Incorrect Method:

Node 1 EOC Code: Node 1 EOC Code:

L1:1#10=SG1 L1:1#10=SG1,C1

Node 2 EOC Code: Node 2 EOC Code:

F1:1#10=SG1 F1:C1=SG1

P/N 06-237480-001 4-9 April 2018

Event Output Control (EOC)

4-3.2.3 INCREMENTING VARIABLE (QX)

An Incrementing Variable, symbolized by Qx, is a variable that is initialized to the value Zero upon
EOC file upload. It can be subsequently incremented by One (new value = old value + 1) by the
execution of a particular EOC statement. Like the Counting Identifier, the Incrementing Variable
becomes a placeholder for the argument that activated it. Accordingly, it can then be used as a
substitute for the triggering argument in a subsequent EOC statement to activate additional physical
outputs or to operate on other dependent variables. It can also be used as a substitute for the
triggering argument in an EOC function (see Section 4-6). It is most useful in counting the number of
times that something happens.

Incrementing Variables assume the initiating device type identities of the arguments that activated
them, but do not track the activation or non-activation states of their associated initiating device type
arguments as shown in Table 4-1. An Incrementing Variable, once activated and assigned a non-Zero
value, can only be reassigned to its initial Zero value by the subsequent execution of another EOC
statement that re-initializes it to Zero via the “NOT” Operator (see Section 4-5) or a successful system
reset operation.

Do not use Incrementing Variables as counters to be associated with a compound argument

constructed with “OR” or “THRU” Operators. They do not count, in the same manner as do Counting
Identifiers, but only increments (counts by one more).

Consider the following example of the use of a Incrementing Variable to count the number of cycles
of alternating a period of Releasing followed by a period of non-Releasing:

(L8:1#10>1)*NC4=C1 $ Equation (4-7) The State Variable C1 goes True when at least two
detectors are in alarm, and when C4 is False.

C1=NC2 $ Equation (4-8) The State Variable C2 goes False when C1 goes True

D(C1,20)=C2 $ Equation (4-9) C2 goes True after a delay of 20 seconds after C1 goes
True

C2=NC3 $ Equation (4-10) The State Variable C3 goes False when C2 goes True

C2=AR1 $ Equation (4-11) Release starts when C2 goes True

D(C2,90)=C3 $ Equation (4-12) C3 goes True after a delay of 90 seconds after C2 goes
True

C3=NC1 $ Equation (4-13) The State Variable C1 goes False when C3 goes True

C3=NAR1 $ Equation (4-14) Release stops when C3 goes True

C3=Q1 $ Equation (4-15) The Incrementing Variable Q1 increments by One when

C3 goes True

Q1>4=C4 $ Equation (4-16) The State Variable C4 goes True when Q1 reaches the
value of 5

$ The State Variable C4 going True stops any further execution of this
EOC program

The value of Q1 increments by one every time the 90-second Release stops. After five cycles, the
system quits cycling by setting the State Variable C4 to True, which prevents C1 from ever going True
again.

All Incrementing Variables are re-initialized to Zero upon a system reset.

April 2018 4-10 P/N 06-237480-001

 Event Output Control (EOC)

4-4 MULTIPLE OUTPUTS

A simple output consists of the activation or de-activation of one physical or virtual output. A
compound output consists of the activation or de-activation (or some combination of both operations)
of two or more physical or virtual outputs. The operators used to create compound outputs are listed
in Table 4-5.

Table 4-5. Combining Operators for Outputs

Operator Symbol

THRU #

Outputs activated by alarm events latch into the activated state regardless of whether the initiating
device is configured for Latching or Non-Latching operation, except when they are programmed for
thermal cycling or time limit cutout operation. Outputs activated by either supervisory or trouble
events follow the activation state of the initiating device or fault condition that activated them (i.e.,
they de-activate when the initiating device restores or the fault condition is corrected).

Exception: Cyclical alarm outputs can only be activated for the ITLCO and CTLCO periods as
discussed in Chapter 3.

4-5 THE "NOT" OPERATOR

Physical outputs can be deactivated with the "NOT" (N) Operator triggered subsequently by the
execution of another EOC statement. An activated (i.e., set to "TRUE") State Variable (Cx) can also be
de-activated (i.e., re-initialized to "FALSE") by the "NOT" (N) Operator. An Incrementing Variable (Qx),
can be re-initialized to Zero by the “NOT” Operator. A Counting Identifier (Ix)cannot be preceded on
the right hand side with the “NOT” Operator as a negated virtual output. It is re-initialized at Reset
only. It can however, be set to Zero, if that is what the value on the left hand side evaluates to.

The "NOT" Operator can be used in an argument where it checks for the absence of an initiating signal
from a physical device or for the falsehood of a Counting Identifier (Ix) or a State Variable (Cx), as
shown in the following: “N4 = designated outputs”, or “N1#100 = designated outputs”.

4-6 FUNCTIONS

An EOC Function activates outputs for a particular set of initiating conditions, delays execution of
outputs for a certain period of time, modifies automatic initiating device thresholds, or alters outputs
in a specific way when an argument activates. The following EOC functions are available:

4-6.1 Alarm Threshold Adjustment Function (Smoke Detectors Only)

The Alarm Threshold Adjustment Function changes the alarm thresholds of one group (argument2)
of smoke detectors as the result of an alarm signal from any smoke detector in a second group
(expression) of detectors. The format of this function is:

“expression=x.y=A argument2” $, or
“expression=x.y=A argument2” $ (spaces are not required)
where:
x.y is the new alarm threshold in percent per foot obscuration
“argument2” is the range of smoke detectors whose alarm thresholds are to be
adjusted

The adjusted alarm thresholds revert to programmed, standby thresholds upon system reset, or
when ”expression” is a Non-Latching initiating device(s) or a Counting Identifier that subsequently
goes false.

P/N 06-237480-001 4-11 April 2018

Event Output Control (EOC)

4-6.2 Pre-Alarm Threshold Adjustment Function (Smoke Detectors Only)

The Pre-Alarm Threshold Adjustment Function changes the pre-alarm thresholds of one group
(argument2) of smoke detectors as the result of a pre-alarm signal from any smoke detector in a
second group (expression) of detectors. The format of this function is:

“expression=x.y=P argument2” $, or
“expression=x.y=P argument2” $ (spaces are not required)
where:

x.y is the new pre-alarm threshold in percent-per-foot obscuration

“argument2” is the range of smoke detectors whose pre-alarm thresholds are to be
adjusted

The adjusted pre-alarm thresholds revert to programmed, standby thresholds upon system reset or
when ”expression” subsequently goes false.

4-6.3 Delayed Output Activation Function (without explicit Abort Interruption)

The Delayed Output Activation Function delays the activation of outputs being activated by an
alarm initiating condition (“expression”) for a specified period of time (delay). The format of
this function is:

“D(expression,delay)= outputs $ (repeatable)

where:
“expression” is an initiating event or a combination of initiating events
“delay” is the delay in seconds before outputs are activated
Note: The control unit automatically adds 3 seconds to the period of time
specified in the delay parameter.
“outputs” are SLC-based modules, control unit-based circuits, a string or
virtual outputs.

The Delayed Output Activation Function tracks the validity of the “expression” and interrupts its
countdown, resets the “delay” period, and performs no actions if the ”expression becomes either
“Zero” or “FALSE” .

An alarm argument latches the physical outputs associated with the Delayed Output Activation
Function when the time delay period expires. Virtual Outputs and all other physical outputs not
activated by alarm initiating events track the validity of the “expression”, and either are “Zero”
or "FALSE" in the case of Virtual Outputs or de-energize in the case of physical outputs if the
argument becomes either non-incremental (e.g., in the case of tracking non-latching
supervisory events) or "FALSE" (e.g., in the case of an explicit simple or compound trouble
argument).

April 2018 4-12 P/N 06-237480-001

 Event Output Control (EOC)

4-6.4 Delayed Output Activation Function (with explicit Abort Interruption)

The Delayed Output Activation Function with Abort Interruption delays the activation of outputs
being activated by an alarm initiating condition (exp) for a specified period of time (delay). The
activation of any abort switch (abort addresses) interrupts the countdown delay and prevent outputs
activation while the abort switch is active (see Section 3-5.12.1 for exception when IRI Abort Option
is selected). The format of this function is:

“D(expression, delay, abort address, abort address, ... , abort address)=outputs”

$ (non-repeatable)
where:
“expression” is an initiating event or a combination of initiating events
“delay” is the delay in seconds before outputs are activated
“abort address” is an SLC-based module
Note: The control unit automatically adds 3 seconds to the period of time
specified in the delay parameter.
“outputs” are SLC-based modules, control unit-based circuits, a string or
virtual outputs.

The Delayed Output Activation Function (with Abort Interruption) tracks the validity of the
“expression” and interrupts its countdown, resets the “delay” period, and performs no actions if the
“expression” becomes either “ZERO” or "FALSE".

An alarm argument latches the physical outputs associated with the Delayed Output Activation
Function when the time delay period expires. Virtual Outputs and all other physical outputs not
activated by alarm initiating events track the validity of the “expression”, and either are “Zero” or
“False” in the case of Virtual Outputs or de-energize in the case of physical outputs if the argument
becomes either non-incremental (e.g., in the case of tracking non-latching supervisory events) or
“False” (e.g., in the case of an explicit simple or compound trouble “expression”).

The activation of any abort switch in the abort switch list prior to the expiration of the
countdown timer interrupts the countdown of the timer in accordance with the operating
characteristics of the abort switch. Refer to Section 3-5.12.1 for abort switch operating
instructions.

Note: Countdown timer interruption is not allowed after the countdown timer has begun to count
down if the IRI option is selected.

All outputs associated with the Delayed Output Activation Function (with Abort Interruption) latch
upon expiration of the time delay period.

4-6.5 Trouble Function for Initiating Devices

The Trouble Function for Initiating Devices activates outputs when a trouble condition occurs as
defined in exp.

“T(expression)=outputs”
where:
“expression” is a trouble report from an initiating device or a combination of
trouble reports from initiating devices
“outputs” are SLC-based modules, control unit-based circuits, a string or virtual
outputs.

The Trouble Function for Initiating Devices tracks the validity of the expression (“expression”) and
de-energizes its associated outputs if the expression becomes either “ZERO” or "FALSE".

P/N 06-237480-001 4-13 April 2018

Event Output Control (EOC)

4-6.6 General Trouble Function

The General Trouble Function activates outputs when any system trouble condition occurs.

“GT=outputs”
where:
“outputs” are SLC-based modules, control unit-based circuits, a string or
virtual outputs.

The General Trouble Function tracks the Trouble State of the control unit and de-energizes its
associated outputs when the Trouble State clears.

4-6.7 General Supervisory Function

The General Supervisory Function activates outputs when any system supervisory condition
occurs.

“GS=outputs”
where:
“outputs” are SLC-based modules, control unit-based circuits, a string or
virtual outputs.

The General Supervisory Function tracks the Supervisory State of the control unit and de-energizes
its associated outputs when the Supervisory State clears.

4-6.8 General Alarm Function

The General Alarm Function activates outputs when any system alarm condition occurs.

“GA=outputs”
where:
“outputs” are SLC-based modules, control unit-based circuits, a string or
virtual outputs.

The General Alarm Function tracks the Alarm State of the control unit and de-energizes its associated
outputs when the Alarm State clears.

4-6.9 Pre-Alarm Function for Initiating Devices

The Pre-Alarm Function for Initiating Devices activates outputs when a pre-alarm condition occurs
as defined in expression.

“P(expression)=outputs”
where:
“expression” is a pre-alarm initiating event or a combination of pre-alarm initiating
events.
“outputs” are SLC-based modules, control unit-based circuits, a string or
virtual outputs.

The Pre-Alarm Function for Initiating Devices tracks the validity of the expression (“expression”) and
de-energizes its associated outputs if the expression becomes either “ZERO” or "FALSE".

April 2018 4-14 P/N 06-237480-001

 Event Output Control (EOC)

4-6.10 Warning Function for AnaLASER-II or ORION-XT Detectors Reporting via the IIM

The Warning Function for AnaLASER-II or ORION-XT detectors reporting via the IIM activates
outputs when a Level-1 Pre-Alarm condition occurs as defined in expression.

W(expression)=outputs
where:
expression is an AnaLASER-II or ORION-XT Level-1 Pre-Alarm initiating event or a
combination of AnaLASER-II or ORION-XT Level-1 Pre-Alarm initiating events
outputs are SLC-based modules, control unit-based circuits or virtual outputs.

The Warning Function for AnaLASER-II or ORION-XT detectors reporting via the IIM tracks the
validity of the expression (expression) and de-energizes its associated outputs if the expression
becomes either non-incremental (e.g, in the case of tracking warning signals from HSSDs via a
counting identifier) or "FALSE" (e.g., in the case of an explicit compound argument representing an
HSSD warning event).

4-6.11 Level-2 Alarm Function for AnaLASER-II or ORION-XT Detectors Reporting via the IIM

The Level-2 Alarm Function for AnaLASER-II or ORION-XT detectors reporting via the IIM activates
outputs when a Level-2 Alarm condition occurs as defined in expression.

X(expression)=outputs
where:
expression is an AnaLASER-II or ORION-XT Level-2 Alarm initiating event or a
combination of AnaLASER-II or ORION-XT Level-2 Alarm initiating events
outputs are SLC-based modules, control unit-based circuits or virtual outputs.

The Level-2 Alarm Function for AnaLASER-II or ORION-XT detectors reporting via the IIM latches
the physical outputs associated it. Virtual outputs track the validity of the expression and is non-
incremental or "FALSE" in the case of Non-Latching Identifiers if the expression becomes either non-
incremental (e.g., in the case of tracking non-latching HSSDs) or "FALSE" (e.g., in the case of an
explicit simple or compound expression or a Non-Latching Identifier substituting for a non-latching,
compound HSSD Level-2 alarm event).

4-6.12 Notification Appliance Pattern Change Function to 60 BPM

This function changes a NAC's signal pattern to 60 beats per minute.

SGx/60
where:
SGx is a control unit-based notification appliance circuit.

An alarm event or an irrevocable event such as the expiration of a delayed-alarm output activation
function (with abort interruption) latches the associated notification appliance circuit to 60 BPM via
the Notification Appliance Pattern Change Function. The NAC in all other cases tracks the validity of
the argument and de-energizes if the argument becomes either non-incremental (e.g., in the case of
tracking non-latching supervisory events) or "FALSE" (e.g., in the case of an explicit simple or
compound argument or a Virtual Output substituting for a compound trouble argument).

Exception: Cyclical alarm outputs activate only for the ITLCO and CTLCO periods as discussed in
Chapter 3.

Note: Do NOT use this function for Intelligent NACs.

P/N 06-237480-001 4-15 April 2018

Event Output Control (EOC)

4-6.13 Notification Appliance Pattern Change Function to 120 BPM

This function changes a NAC's signal pattern to 120 beats per minute.

SGx/120
where:
SGx is a control unit-based notification appliance circuit.

An alarm event or an irrevocable event such as the expiration of a delayed-alarm output activation
function (with abort interruption) latches the associated notification appliance circuit to 120 BPM via
the Notification Appliance Pattern Change Function. The NAC in all other cases tracks the validity of
the argument and de-energizes if the argument becomes either non-incremental (e.g., in the case of
tracking non-latching supervisory events) or "FALSE" (e.g., in the case of an explicit simple or
compound argument or a Virtual Output substituting for a compound trouble argument).

Exception: Cyclical alarm outputs are activated only for the ITLCO and CTLCO periods as discussed
in Chapter 3.

Note: Do NOT use this function for Intelligent NACs.

4-6.14 Notification Appliance Pattern Change Function to Temporal Coding

This function changes a NAC's signal pattern to the temporal code.

SGx/T
where:
SGx is a control unit-based notification appliance circuit.

An alarm event or an irrevocable event such as the expiration of a delayed-alarm output activation
function (with abort interruption) latches the associated notification appliance circuit to temporal
coding via the Notification Appliance Pattern Change Function. The NAC in all other cases tracks the
validity of the argument and de-energizes if the argument becomes either non-incremental (e.g., in
the case of tracking non-latching supervisory events) or "FALSE" (e.g., in the case of an explicit
simple or compound argument or a Virtual Output substituting for a compound trouble
argument).

Exception: Cyclical alarm outputs are activated only for the ITLCO and CTLCO periods as discussed
in Chapter 3.

Note: Do Not use this function for Intelligent NACs.

April 2018 4-16 P/N 06-237480-001

 Event Output Control (EOC)

4-6.15 Notification Appliance Pattern Change Function to Continuous Output

This function changes a NAC's signal pattern to a steady (i.e., non-coded) output.

SGx/C
where:
SGx is a control unit-based notification appliance circuit.

An alarm event or an irrevocable event such as the expiration of a delayed-alarm output activation
function (with abort interruption) latches the associated notification appliance circuit to continuous
output via the Notification Appliance Pattern Change Function. The NAC in all other cases tracks the
validity of the argument and de-energize if the argument becomes either non-incremental (e.g., in
the case of tracking non-latching supervisory events) or "FALSE" (e.g., in the case of an explicit
simple or compound argument or a Virtual Output substituting for a compound trouble
argument).

Exception: Cyclical alarm outputs are activated only for the ITLCO and CTLCO periods as discussed
in Chapter 3.

Note: Do NOT use this function for Intelligent NACs.

4-6.16 Initiating Event Counting Function

A special EOC Function is the Counting Function for Initiating Devices and Counting Variables (>n)
whose general form is illustrated below. Outputs activate when the number of single or combinations
of alarm initiating events as defined in “expression” exceeds Ix, Qx, or “n”.

“(expression)>Ix = outputs”, or
“(expression)>Qx = outputs”, or
“(expression)>n = outputs”
where:
“expression” is an initiating event, a combination of initiating events or a virtual
output.
Ix, Qx, or “n” is the number of initiating events required to activate the outputs.
“outputs” are SLC-based modules, control unit-based circuits, a string or virtual
outputs.
Note: The above initiating expression, (i.e., (expression)>Ix, (expression)>Qx, or (expression)>n),
can be used with other simple arguments and the “OR” and “AND” Operators discussed in
Section 4-2.2 to create compound arguments.

It can also be used as all or part of the arguments described in Section 4-6.1 through 4-6.15. Refer
to Table 4-5 for special requirements when creating compound arguments with the Initiating Event
Counting Function.

An alarm argument latches the physical outputs associated with the Initiating Event Counting
Function when the designated count is exceeded.

P/N 06-237480-001 4-17 April 2018

Event Output Control (EOC)

4-7 CONSTRUCTING ARGUMENTS FOR INITIATING EVENTS FROM REMOTE, NETWORKED

CONTROL UNITS

Arguments that consist of initiating events from remote, networked control units must be prefixed
with the letter F, the network node number, and a colon (i.e., :).

4-7.1 Remote-Node Simple Arguments

A remote-node simple argument consists of the network-node prefix and the SLC address of the
initiating device on the remote node. For example, a simple argument using the initiating device at
Address 21 on Node 3 would be referenced in any other node as follows:

• F3:L1:021

4-7.2 Remote-Node Compound Arguments

A remote-node compound argument consists of a combination of two or more simple arguments.

However, there is one instance where it is not necessary to prefix all the simple arguments with the
letter F, the network node number, and a colon. The "THRU" Combining Operator should be used as
follows to reference all initiating points at addresses 1 through 20 on Node 2 in any other node:

• F2:L1:1#20

All other compound arguments that reference remote-node initiating devices require that all the
remote-node initiating devices be prefixed with the letter F, the network node number, and a colon.
For example, references to initiating points 8, 12, and 15 on Node 1 would be entered in any other
node as follows:

• F1:L1:8+F1:L3:12+F1:L5:15
• F1:L1:8*F1:L3:12*F1:L5:15

A complete summary of EOC operators and functions, with specific examples of usage, is presented
in Table 4-6.

4-7.3 Remote State Variable (Fy:Cx)

The Cx State Variables described above can be used across networked control units. The proper
usage of this feature is an operator ‘Fy:Cx’, where ‘y’ is a valid node number and ‘x’ is a valid ‘C’
variable number used on the ‘y’ node. These network state variables are processed the same way non-
networked state variables are processed by the control unit. Whenever the state variable changes on
the originating node, a network message is generated with the new value, “TRUE” or “FALSE”, of the
variable. When control units receive the C variable network messages, the local EOC is processed.

‘Fy:Cx’ cannot be used on the right hand side of EOC equations. Control units cannot change state
variables originating on other nodes. Networked state variables are read only.

Note: There is no verification between control unit configurations, so it is

imperative that the EOC programs for different nodes sharing state
variables are manually and thoroughly reviewed to be sure there are
no errors.

The “C” state variable cannot be used for activating silenceable outputs across a network.
WARNING Refer to Section 4-3.2.2 for further information and EOC code examples.

April 2018 4-18 P/N 06-237480-001

 Event Output Control (EOC)

4-7.4 Releasing Service and ULC Operation

Where networked control units configured for ULC Operation are utilized for a releasing device
service application, the input circuits and output circuits (e.g. abort stations, solenoid valves) shall
be served by the same control unit. The network operator cannot be used when activating releasing
outputs as shown in the following EOC line example:

• F2:L1:1=AR1

This type of EOC line will give a syntax error in configurations where ULC Operation is enabled.

P/N 06-237480-001 4-19 April 2018

Event Output Control (EOC)

Table 4-6. EOC Operators and Functions

Symbol or General
Operator or Function Typical Examples Description
Form

Execution = L1:45=SG1 Turn on SG1 if initiating device

45 activates.
(i.e., "equal" symbol)

"AND" for Outputs , L1:4=AR1,SG1 Turn on AR1 and SG1 if initiating device
4 activates.
(i.e., comma)

"AND" for Initiating * L1:1*L1:3 1 and 3

Devices and/or Initiating
(i.e., "multiplication" Note: Arguments may be enclosed
Conditions
symbol) within parentheses if used with other
operators (e.g., "+" or "#") in a
compound conditional activation
statement. Arguments in parenthesis are
evaluated first.
For example:
(L1:1*L1:3)+L1:10=SG1
This statement translates to "Turn on SG1
if 1 and 3 activate or if 10 activates".
"OR" for Initiating + L1:10+L1:12 10 or 12
Devices and/or Initiating
(i.e., "addition" symbol) Note: Arguments may be enclosed
Conditions
within parentheses if used with other
operators (e.g., "*" or "#") in a
compound conditional activation
statement. Arguments in parenthesis are
evaluated first.
For example:
(L1:1+L1:3)*L1:10=SG1
This statement translates to "Turn on
SG1 if 1 or 3 activates and if 10 also
activates".
"THRU" for Initiating # L1:1#20 Any initiating device 1 through 20.
Devices, Counting
(i.e., "pound" symbol) Note: Arguments for initiating devices
Identifiers and Outputs
may be enclosed within parentheses if
used with other operators (e.g., "*" or
"+") in a compound conditional
activation statement. Arguments in
parenthesis are evaluated first.
For example:
(L1:1#20)+L1:50=SG1,SG4
This statement translates to "Turn on
SG1 and SG4 if any address 1 through
20 activates or if address 50 activates".

April 2018 4-20 P/N 06-237480-001

 Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

Alarm Threshold exp1=x.y=Aarg2 L1:1#20=1.0=AL1:21#40 Change the alarm threshold to 1.0% per
Adjustment foot for each detector in the address
range 21 through 40 if any detector in
(smoke detectors only)
where: the address range 1 through 20 reports
an alarm.
exp1 is an alarm
initiating event or Note: The alarm initiating condition (i.e.,
combination of alarm exp1) and the adjusted smoke detector
initiating events range (i.e., arg2) can be any valid simple or
compound arguments using multiple
x.y is the new alarm operators or types of operators. Commas
threshold for each are required to delimit the simple or
detector in arg2. compound outputs for alarm threshold
arg2 is the range of adjustment.
smoke detectors whose For example:
alarm thresholds are to
be adjusted. L1:1+L1:10#20=1.0=AL1:2,1.0=
AL1:21#30
This statement translates to "Change the
alarm threshold to 1.0% per foot for the
detector at address 2 and for each
detector in the address range 21
through 30 if the detector at address 1
or any detector in the address range 10
through 20 reports an alarm".
Delayed Output D(exp,delay)= outputs D(L1:2*L1:3,30)=RY1 Turn on RY1 after a 30-second delay
Activation if both initiating devices 2 and 3
activate.
where:
Note: Parentheses as shown are
exp is an initiating required. The initiating condition
event or combination of (i.e., exp) for the delay operator can
initiating events be any valid simple or compound
argument using one or more operator
delay is the delay is types such as "+", "#", or ">n". EOC
seconds before outputs continuously loops back to the initial
are activated (max. program statement and rerun entirely
3600 seconds) until the last activated delayed output
outputs are SLC-based activation statement has successfully
modules, control unit- executed.
based circuits, a string
or virtual outputs

P/N 06-237480-001 4-21 April 2018

Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

Counting Identifier Ix L1:5#10=I1 Counting Identifier I1 increments its

(Max. 255 identifiers) current value and cause execution or re-
I1=RY1,RY3
execution of any subsequent statement
where: using it as a conditional input trigger if
any initiating device 5 through 10
x is any number from 1 activates. Counting Identifiers must be
to 255 assigned to specific initiating
expressions before they can trigger
outputs in subsequent execution
statements. Relay 1 and Relay 3 activate
if any initiating device in the address
range 5 to 10 activates.
Note: Use one Counting Identifier for
each unique initiating expression.
Counting Identifiers cannot be used with
the NOT Operator on the output side of
an EOC statement.
NOT N L1:1*N2=SG1 (1) Checks for the absence of an initiating
signal in a conditional execution
L1:5=NSG1,SG4 (2)
statement as in Example (1). Turns off
previously activated outputs in a
conditional execution statement as in
Example (2).
Note: The negated initiating condition
can be any valid simple or compound
argument using multiple operators or
types of operators. Parentheses are
required to delimit the argument.
For example on the left input side:
N(1+5) is equivalent to N1+N5.

April 2018 4-22 P/N 06-237480-001

 Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

Pre-Alarm Threshold exp1=x.y=P arg2 L1:1#20=1.0=P L1:21#40 Change the pre-alarm threshold to 1.0%
Adjustment per foot for each detector in the address
(smoke detectors only) range 21 through 40 if any detector in
where: the address range 1 through 20 reports
a pre-alarm condition.
exp1 is a pre-alarm
initiating event or Note: The initiating condition (i.e.,
combination of pre- exp1) and the adjusted smoke detector
alarm initiating events range (i.e., arg2) can be any valid
expression using multiple operators or
x.y is the new pre- types of operators. Commas are
alarm threshold for required to delimit the simple or
each detector in arg2 compound outputs for pre-alarm
arg2 is the range of threshold adjustment.
smoke detectors whose For example:
pre-alarm thresholds
are to be adjusted L1:1+L1:10#20=1.0=P L1:2,1.0
=P L1:21#30
This statement translates to "Change the
pre-alarm threshold to 1.0% per foot for
the detector at address 2 and for each
detector in the address range 21
through 30 if the detector at address 1
or any detector in the address range 10
through 20 reports a pre-alarm
condition".
State Variable Cx L1:5#10=C1 State Variable C1 is "TRUE" and causes
(Max. 255 Variables) execution of any subsequent statement
C1=RY1,RY3,NC1
using it as a conditional input trigger if
where: any initiating device 5 through 10
activates. All State Variables are initially
x is any number from "FALSE" until changed to "TRUE" by the
1 to 255 execution of a program statement. A
State Variable can be re-initialized to
"FALSE" by the NOT Operator during
the execution of a subsequent program
statement. Relays 1 and 3 activate and
C1 is re-initialized to “FALSE” in this
example.
Note: Use one State Variable for each
unique system state condition.

P/N 06-237480-001 4-23 April 2018

Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

Delayed Output D(exp,delay,abort D(L1:2*L1:3,30,L1:9,L1:10) Turn on AR1 and SG1 after a 30-second
Activation addresses)=outputs = AR1,SG1 delay if both initiating devices 2 and 3
(with Abort activate. Interrupt the countdown if
Interruption) either 9 or 10 activate before the
where: expiration of the time delay.
exp is an alarm
initiating event or a
Note: Parentheses as shown are
combination of alarm
required. Counting Identifiers, State
initiating events
Variables and Saved Incrementing
delay is the delay is Variables can be used for the delay
seconds before outputs function's initiating condition. The
are activated (max. 300 initiating condition (i.e., exp) for the
seconds) delay function can be a compound
argument using the "+", "#", or ">n"
addresses is the Operators. Do not use the "+" or "#"
comma delimited list of Operators in the Abort Field. EOC
abort switch addresses continuously loops back to the initial
(including remote) program statement and rerun entirely
outputs are SLC-based until the last activated delayed output
modules, control unit- activation statement has successfully
based circuits, a string executed.
or virtual outputs
Counting Zone for (exp)>n=outputs (L1:5#15)>1=SG1 Turn on SG1 if more than one of the
Initiating Devices alarm initiating devices in the address
range 5 through 15 activates.
where:
Note: Parentheses as shown are
exp is an initiating required. The alarm initiating condition
event or a combination (i.e., exp) for the Counting Zone
of initiating events Function can be any valid simple or
compound argument using one or more
outputs are SLC-based operator types such as "+" or "*". The
modules, control unit- Counting Zone Function can be
based circuits, a string combined with other operators (e.g., "+"
or virtual outputs or "#") to create a compound conditional
N is the threshold activation statement.
above which the For example:
function activates.
I1+(L1:5#15)>1=AR1
Counting Zone operations should be
enclosed in parenthesis, for clarity, but
it is not necessary.
For example:
((L1:5#15)>1)+I1=AR1
The above statements are equivalent,
and translate to "Turn on AR1 if
Counting Identifier I1 becomes “TRUE”
or if any two initiating devices in the
address range 5 through 15 activate".

April 2018 4-24 P/N 06-237480-001

 Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

Notification Appliance SGx/60 L1:1#20=SG1/60 Turn on SG1 with a 60 BPM pattern

Pattern Change to 60 (and override the current pattern, if
BPM activated) when any device in the
where: address range 1 through 20 activates.
SGx is a control unit- Note: Do Not use this function for
based notification Intelligent NACs.
appliance circuit.
Notification Appliance SGx/120 L1:1#20=SG1/120 Turn on SG1 with a 120 BPM pattern
Pattern Change to 120 (and override the current pattern, if
BPM activated) when any device in the
where: address range 1 through 20 activates.
SGx is a control unit- Note: Do Not use this function for
based notification Intelligent NACs.
appliance circuit.
Notification Appliance SGx/T L1:1#20=SG1/T Turn on SG1 with the temporal pattern
Pattern Change to (and override the current pattern, if
Temporal Coding activated) when any device in the
where: address range 1 through 20 activates.
SGx is a control unit- Note: Do Not use this function for
based notification Intelligent NACs
appliance circuit.
Notification Appliance SGx/C L1:1#20=SG1/C Turn on SG1 with a continuous output
Pattern Change to (and override the current pattern, if
Continuous Output activated) when any device in the
where: address range 1 through 20 activates.
SGx is a control unit- Note: Do Not use this function for
based notification Intelligent NACs
appliance circuit.
Trouble for Initiating T(exp)=outputs T(L1:1#20)=L1:100 Activate Addressable Output (AO) 100 if
Devices any initiating device in the address
range 1 through 20 issues a trouble
where: report.
exp is a trouble report Note: Parentheses as shown are
or a combination of required. The initiating condition (i.e.,
trouble reports from exp) for the Trouble Operator can be
initiating devices any valid simple or compound argument
using one or more operator types such
outputs are SLC-based as "+", "#", or "*"
modules, control unit-
based circuits, a string Do not use the Trouble for Initiating
or virtual outputs Devices Function for an AI Monitor
Module programmed as a trouble
initiating device.
General Trouble GT=outputs GT=L1:100 Activate Addressable Output (AO) 100 if
any system trouble event occurs.

where:
outputs are SLC-based
modules, control unit-
based circuits, a string
or virtual outputs

P/N 06-237480-001 4-25 April 2018

Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

General Supervisory GS=outputs GS=L1:100 Activate Addressable Output (AO) 100 if

any system supervisory event occurs.

where:
outputs are SLC-based
modules, control unit-
based circuits, a string
or virtual outputs
Pre-Alarm P(exp)=outputs P(L1:1#20)=SG1 Activate SG1 if any initiating device in
the address range 1 through 20 issues a
pre-alarm report.
where:
Note: Parentheses as shown are
exp is a pre-alarm required. The initiating condition (i.e.,
initiating event or a exp1) for the Pre-Alarm Function can be
combination of pre- any valid simple or compound argument
alarm initiating events using one or more operator types such
as "+", "#", or "*".
outputs are SLC-based
modules, control unit-
based circuits, a string
or virtual outputs
Activating a Single LAM LEDx:y (1) GT=LED2:3 (1) Annunciator circuit #3 on LAM
LED LED/Bx:y (2) GS=NLED16:43 module #2 becomes active when the
LED/Sx:y General Trouble activates.
(3) GT=LED1:1,LED/B1:2,
LED/Rx:y
LED/S1:3,LED/R1:4,LED/ (2) Annunciator circuit #43 on LAM
LED/Yx:y
Y1:5 module #16 deactivates when the
General Supervisory activates.
(4) GT=LED/B/R1:6,
LED/R/B1:7,LED/B/Y1:8, For lines (3), (4), and (5), when the
LED/Y/B1:9 General Trouble activates, then on LAM
module #1:
(5) GT=LED/S/R1:14,
LED/R/S1:15,LED/S/Y1:16, (3) Annunciator circuit #1 goes on as
LED/Y/S1:17 configured; circuit #2 goes on Blinking
(color as configured); circuit #3 goes on
Note: 44 thru 48 are
Steady (color as configured); circuit #4
Reserved.
goes on Red (pattern as configured);
circuit #5 goes on Yellow (pattern as
configured).
(4)Annunciator circuits #6 and #7 go
on Blinking Red; circuits #8 and #9 go
on Blinking Yellow.
(5) Annunciator circuits #14 and #15
go on Steady Red; circuits #16 and #17
go on Steady Yellow.
Mapping Multiple LAM MLP list= MLP C2,GT,L1:1#3= Maps C2 to LED2:10, GT to LED2:1,
LEDs LEDw:x#y:z, LED2:10#2:14 inputs1 to LED2:12, 2 to LED2:13, and
LEDs:t#u:v 3 to LED2:14. These mapping lines
would normally be at the end of an EOC
program, but could appear anywhere,
especially if one wanted to find out the
intermediate value of a Counting
Identifier or State Variable (possibly for
EOC debugging purposes).

April 2018 4-26 P/N 06-237480-001

 Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

Activating a Single AMx:y (1) GT=AM2:3 (1) Annunciator circuit #3 on ATM

ATM-L (LED) AM/Bx:y module #2 becomes active when the
or ATM-R (Relay) AM/Sx:y General Trouble activates.
(2) Annunciator circuit #43 on ATM
(2) GS=NAM16:43 module #16 deactivates when the
General Supervisory activates.
For line (3), when the General Trouble
(3) GT=AM1:1,AM/B1:2, activates, then on ATM module #1:
AM/S1:3,
Annunciator circuit #1 goes on as
configured; circuit #2 goes on blinking
(ATM-L only).
Mapping Multiple MAP list= MAP C2,GT,L1:1#3= Maps C2 to ATM2:10, GT to ATM2:1,
ATM-L (LEDs) AMw:x#y:z, AM2:10#2:14 inputs1 to ATM2:12, 2 to ATM2:13, and
or ATM-R (Relays) AMs:t#u:v 3 to ATM2:14. These mapping lines
would normally be at the end of an EOC
program, but could appear anywhere,
especially if one wanted to find out the
intermediate value of a Counting
Identifier or State Variable (possibly for
EOC debugging purposes).
Warning for AnaLASER- W(exp)=outputs W(HSD1#5)=SG1 Activate SG1 if any AnaLASER-II or
II or ORION-XT ORION-XT in the address range 1
Detectors Reporting via through 5 issues a warning report. This
IIM where: is a Pre-Alarm Level 1 for AnaLASER-
IIs).
exp is an AnaLASER-II
or ORION-XT Level-1 Note: Parentheses as shown are
Pre-Alarm initiating required. The initiating condition (i.e.,
event or a combination exp) for the Warning Function can be
of AnaLASER-II or any valid simple or compound argument
ORION-XT Level-1 pre- using one or more operator types such
alarm initiating events as "+", "#", or "*".
outputs are SLC-based
modules, control unit-
based circuits or
virtual outputs
Alarm Level 2 for X(exp)=outputs X(HSD1#5)=SG1 Activate SG1 if any AnaLASER-II or
AnaLASER-II or ORION- ORION-XT in the address range 1
XT Detectors Reporting through 5 issues a high-level-alarm
via IIM where: report. This is an Alarm Level 2 for
AnaLASER-IIs).
exp is an AnaLASER-II
or ORION-XT Level-2 Note: Parentheses as shown are
Alarm initiating event required. The initiating condition (i.e.,
or a combination of exp) for the Level-2 Alarm Function can
AnaLASER-II or be any valid simple or compound
ORION-XT Level-2 argument using one or more operator
Alarm initiating events types such as "+", "#", or "*".

outputs are SLC-based

modules, control unit-
based circuits or
virtual outputs

P/N 06-237480-001 4-27 April 2018

Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

Remote Control Unit Fx:Ly:arg=outputs F5:L1:1#50=SG1 Activate SG1 if any initiating device in
Initiating Event the address range 1 through 50 on SLC
where:
1 of Node No. 5 issues an alarm report.
x is the remote control
unit node number from
F3:L1:7*F2:L1:10=AR1
1 to 64
Activate AR1 if initiating device 7 on
y is the SLC Loop SLC 1 of Node No. 3 AND initiating
number from 1 to 8 device 10 on SLC 1 of Node No. 2 issue
alarm reports.
arg is an alarm-
initiating event or a
combination of alarm- Activate RY1 if initiating device 1 on
initiating events from F5:L1:1+F3:L1:7=RY1 SLC 1 of Node No. 5 OR initiating device
the remote control unit 7 on SLC 1 of Node No. 3 issue an alarm
of the following report.
generalized types:
start address#end
address
or,
The "OR" Operator (+)
and the “AND”
Operator (*) cannot be
used to construct a
compound argument.
The "OR" Operator (+)
and the “AND”
Operator (*) create
separate terms that
must be prefixed with
Fx:.
outputs are outputs
activated by the control
unit that received the
remote initiating
event(s)
Networked Saved State Fy:Cx F15:C1=RY1,RY3 If the State Variable C1 defined on node
Variable (Max. 255 15 becomes "TRUE", then RY1 and RY2
Where:
Variables for each node) shall activate.
x is any number from
Note: A networked State Variable cannot
1 to 255 and y is any
be changed and as such cannot be used
number from 1 to 64
on the right hand side of EOC equations.
RRM Grouping RGx L1:100*L1:200=RG1 Activate Release Group 1 when
Activation addresses 100 and 200 report an alarm
Where:
condition.
RG is the release group
in which RRMs are
assigned to via the
configuration software
x is the group number
between 1 and 7

April 2018 4-28 P/N 06-237480-001

 Event Output Control (EOC)

Table 4-6. EOC Operators and Functions (Continued)

Symbol or General
Operator or Function Typical Examples Description
Form

SLC Output Grouping OGx L1:1#50=OG5 Activate Output Group 5 when any
Activation device in the Address range of 1 to 50 on
Where:
SLC 1 report an alarm condition.
x is the SLC Output
group in which AO and
ASM devices are
assigned to via the
configuration software
x is the group number
between 1 and 7
Comment $ $ General Alarm Condition Used to indicate a non-operational
program line or end of statement on a
or
line.
(any of the above) $ comment
Note: Use the minimum number of
comment lines to properly document the
flow and logic of the EOC application.
Each comment line counts toward the
limit of 256 EOC lines, and negligibly
extends the time required to execute the
specific application.

P/N 06-237480-001 4-29 April 2018

Event Output Control (EOC)

4-8 CREATING EVENT OUTPUT CONTROL (EOC TAB)

The section of the program that stores EOC execution statements is invoked when the EOC Tab is
selected. Figure 4-1 shows the EOC Tab. Use the <Edit> button to enter EOC code.

Figure 4-1. EOC Creation Screen

Figure 4-2 shows lines of EOC code that have been entered via the program's free-form text editor.

Figure 4-2. EOC Text Editor Screen

April 2018 4-30 P/N 06-237480-001

 Event Output Control (EOC)

The EOC Tab Text Editor screen options are shown in Table 4-7.
Table 4-7. EOC Tab Options

Command Function

EOC Toolbar Save, Print, Cut, Copy, Paste, Find and Verify Icons
File Menu Save As Text, Print, Exit
Edit Menu Undo, Cut, Copy, Paste and Delete
Find Menu Searches EOC Code
Verify Menu Verifies EOC Code
Help Menu Opens PDF file of ACT-MLX User’s Guide and shows the application version.

Follow these steps to create an EOC file:

5. Enter EOC execution statements in free-form format just as if using a standard word processing
program. Note that it is not necessary to create line numbers for EOC statements.
6. Select <OK> when done.
7. Edit the EOC code as necessary to remove all errors and warnings.
8. Select <Apply> to apply changes.
9. Save your configuration file.

Figure 4-3 shows the saved EOC code in the EOC Summary Window. Click <Edit...> to edit the
EOC Code.

Figure 4-3. Saved EOC Code Screen

P/N 06-237480-001 4-31 April 2018

Event Output Control (EOC)

If the program detects an undefined SLC device or a syntax error, the Error and/or Warning Screen
appears (see Figure 4-4) after exiting the text editor.

Figure 4-4. EOC Error and/or Warning Screen

4-8.1 The <Apply> Button

Click <Apply>, located at the bottom of the EOC tab, to accept all changes made. (See Figure 4-1.)

Note: Clicking <Apply> does not automatically save settings to the

configuration file. The configuration file must be saved before
exiting the program, or settings will be lost.

4-8.2 The <Reset> Button

Click <Reset>, located at the bottom of the EOC tab, to cancel all changes made to settings while in
the EOC tab and return to the previously-saved settings. (See Figure 4-1.)

April 2018 4-32 P/N 06-237480-001

 Event Output Control (EOC)

4-9 STRUCTURING EVENT OUTPUT CONTROL

In general, one EOC statement needs to be written for each input-to-output operating sequence
required for the specific application. Up to 256 EOC statements can be used for any application, and
an EOC statement can have up to 128 characters. Use the following guidelines to construct an EOC
application:

1. Arrange the sequence of EOC statements from the start to the end of the application according
to the following event priority:
– Alarm
– Supervisory
– Trouble
Note: All alarm events must be annunciated by public mode notification.
2. Put the most likely to be executed statements at the start of the prioritized segments above. This
means that statements with simple arguments or compound arguments constructed with either
"OR" ( + ) or "THRU" ( # ) Operators should be entered first in each prioritized segment.
3. Use a separate Counting Identifier or State Variable for each compound argument that is used
on more than one EOC statement.
4. Never use a Counting Identifier to trigger outputs unless it has been defined first in a prior EOC
statement.
5. If possible, activate physical and virtual outputs in the same EOC statement to keep the number
of statements to as few as possible.
6. Write the pre-release, release, and post-release EOC statements on consecutive lines for each
special extinguishing system. A separate pre-release statement is typically required because
release outputs are not activated until after the expiration of a time delay. Enter these statements
in ascending order according to the more progressively serious alarm condition (i.e., write the
pre-alarm statement first, the pre-release statement second, and the release statement third).
Note: The following requirements apply to special extinguishing systems:
– The pre-alarm state must be annunciated by distinctive public mode notification.
– The pre-release state must be annunciated by public mode notification different from the
pre-alarm state public notification mode.
– The release state must be annunciated by public mode notification different from both
the pre-alarm state and pre-release state public notification modes.
7. The manual release station(s) for a special extinguishing system must appear in the arguments
of the pre-alarm, pre-release, and release statements for the system if required interlocks such
as door closures, airflow shutoff, and power down procedures are distributed throughout these
three alarm stages.
8. Place the least likely to be executed statements at the end of the prioritized segments in guideline
1). For example, open area smoke detectors are more likely to activate before duct detectors
because of the high smoke dilution factors associated with duct detection. Therefore statements
associated with duct detectors should be entered after the statements associated with open area
detectors and after any special extinguishing system execution statements.
9. Add in remote alarm-initiating events from other networked control units according to the
guidelines 2) through 7), but add them after the control unit's local events. Arrange remote alarm-
initiating events in ascending order by network node number.
10. It is recommended that the terms involved in contiguous "ANDing" be limited to only one term
that can have a value of more than 1, and the rest limited to logical “TRUE” or “FALSE” only.
For example, 'I1 * NI2 * N(L1:10#40)' is good because only I1 can have a value greater than 1
(NI2 and N(L1:10#40) is always “TRUE” or “FALSE). However, 'L1:10#40 * I3' is not acceptable
because both factors can be greater than 1. Refer to Section 4-2.2.1 for more information.
11. Outputs should be dedicated to a single notification or function type and should, therefore, not
be shared by alarm and non-alarm notifications.

P/N 06-237480-001 4-33 April 2018

Event Output Control (EOC)

12. When configuring a system for ITLCO/CTLCO cycling, program the ITLCO/CTLCO inputs and
outputs on a dedicated line(s) of EOC. Do not include other non-ITLCO/CTLCO inputs or outputs
on the same line of EOC.
13. When using the “AND” operator with ITLCO/CTLCO inputs, the “AND” condition is required to
get the cycling started— both conditions of the “AND” must be true. However, the cycling will
continue if either of the “AND” conditions becomes false and at least one ITLCO/CTLCO input
remains active.
14. Squirt and Spurt inputs and outputs should always be programmed on a dedicated line(s) of
EOC code. Do not include other non-Squirt/Spurt inputs or outputs on the same line of EOC.

4-10 EVENT OUTPUT CONTROL EXAMPLES

Table 4-8 illustrates specific example of event output control. This is a two-zone waterless
suppression system with associated pre-action sprinkler systems. Refer to Appendix A for the
sequence of operation and device/circuit configuration associated with this application.

Table 4-8. EOC, Example 1

$ Head End Room Pre-Alarm

L1:1#3=SG1,LED1:1,I1, C1
NI1=NC1
L1:1#3=1.5=A4#6
L1:4#6=SG1,LED1:1,I2, C2
NI2=NC2
L1:4#6=3.0=L1:A1#3
$ Power Room Pre-Alarm
L1:14#15=SG3,LED1:4,I3, C3
NI3=NC3
L1:14#15=1.5=L1:A16#17
L1:16#17=SG3,LED1:4,I4, C4
NI4=NC4
L1:16#17=3.0=AL1:14#15
$ Head End Room Waterflow
L1:11=SG2,LED1:6,RY3
$ Power Room Waterflow
L1:20=SG4,LED1:12,RY3
$ Head Room Tamper
L1:12=LED1:5,L1:25
$ Power Room Tamper
L1:21=LED1:11,L1:25
$ Head End Room Low Pressure
L1:13=LED1:4
$ Power Room Low Pressure
L1:22=LED1:10

April 2018 4-34 P/N 06-237480-001

 Event Output Control (EOC)

Table 4-8. EOC, Example 1 (Continued)

$ Pre-Action System Low Air

L1:26=LED1:13
$ Head End Room Pre-Release
I1*C2 + L1:7 + L1:8= SG1/120,23
C1*I2 + L1:7 + L1:8=SG1/120,23
$ Head End Room Release
D(I1*I2,30,L1:9,L1:10)+L1:7+L1:8=NSG1,NLED1:1,AR1,SG2,24,RY2,LED1:3
L1:9+10=LED1:2
$ Power Room Pre-Release
I3*C4+L1:18= SG3/120, 23
C3 * I4+L1:18=SG3/120, 23
$ Power Room Release
D(I3*I4,30,L1:19)+L1:18=NSG3,NLED1:7,AR2,SG4,24,RY2,LED1:8
L1:19=LED1:8
Table 4-9 is an example of a networked fire-alarm system monitoring three school buildings. The
sequence of operations for all three buildings is shown in Appendix A. The details are shown in
Table 4-8 and Table 4-9 for the first building. The specifics for Buildings No. 2 and 3 are similar.

Table 4-9. EOC, Example 2

$ Building No. 2 Smoke Detectors

F2:L1:1#15=SG4,S1
$ Building No. 2 Manual Stations
F2:L1:16#23=SG4,S2
$ Building No. 2 Waterflow
F2:L1:24#27=SG4,S2
$ Building No. 2 Kitchen Hood
F2:L1:28=SG4,S4
$ Building No. 3 Smoke Detectors
F3:L1:1#15=SG4,S6
$ Building No. 3 Manual Stations
F3:L1:16#23=SG4,S7
$ Building No. 3 Waterflow
F3:L1:24#27=SG4,S8
$ Building No. 3 Kitchen Hood
F3:L1:28=SG4,S9
$ Building No. 2 Supervisory
F2:L1:29#32=S5
$ Building No. 3 Supervisory
F3:L1:29#32=S1

P/N 06-237480-001 4-35 April 2018

Event Output Control (EOC)

4-11 ADDITIONAL EVENT OUTPUT CONTROL EXAMPLES

The examples in this section illustrate special EOC topics of interest.

4-11.1 Limited Water Supply Example

A four-zone deluge sprinkler system is being designed according to the following water supply
constraints:

Active Zone Allowable Subsequent Zone Activation Disallowable Subsequent Zone Activation

1 2 3 and 4
2 1 or 3 4
3 2 or 4 1
4 3 1 and 2

Note: In order to cover 4 zones, there must be an expansion RNAC with

2 circuits configured for release.

No more than two deluge sprinkler zones can be active concurrently. Figure 4-5 illustrates the
application.

Sprinkler Zone 1 Sprinkler Zone 2

HD1 HD2

Sprinkler Zone 3 Sprinkler Zone 4

HD3 HD4

Figure 4-5. Limited Water Supply

State Variables are used in the code that follows to signify the activation of each zone and to apply the
required constraints:

“(Zone 1)”*NC3*NC4*NC5=AR1,C1
“(Zone 2)”*NC4*NC5=AR2,C2
“(Zone 3)”*NC1*NC5=AR1:1,C3
“(Zone 4)”*NC1*NC2*NC5=AR1:2,C4
C1*(C2+C3+C4)=C5
C2*(C1+C3+C4)=C5
C3*(C1+C2+C4)=C5
C4*(C1+C2+C3)=C5

April 2018 4-36 P/N 06-237480-001

 Event Output Control (EOC)

4-11.2 NAC that Tracks AnaLASER-II or ORION-XT Alarm State

The system shown in Figure 4-6 is to be designed according to the following criteria:

• Activate NAC if either one of AnaLASER-II/ORION-XT detectors alarm

• Deactivate NAC if all alarmed HSSDs issue alarm off reports
• Latch the NAC into the active state if any spot type smoke detector alarms.

SD1 SD2 SD3

AIM20

SG1

SD4 SD5 SD6

AIM21

Figure 4-6. Tracking NAC

The EOC code required to accomplish this design requirement is shown below:

L1:20+L1:21=SG1
L1:1#6=SG1,C1
NL1:20*NL1:21*NC1=NSG1

P/N 06-237480-001 4-37 April 2018

Event Output Control (EOC)

4-11.3 External Maintenance Bypass Switch Example

An end user wants to provide service personnel with a simplistic way to prevent the activation of
notification appliances during facility maintenance periods. The user wants to use an externally
mounted switch to accomplish this requirement. The necessary sequence of operation is as follows:

• The NAC shall activate if an automatic detector alarms and the maintenance bypass switch has
not been activated
• The NAC shall not activate if an automatic detector alarms subsequently to the activation of the
maintenance bypass switch
• The NAC shall deactivate if the maintenance bypass switch is activated subsequently to an
automatic detector alarm.

The AI monitor module for the maintenance bypass switch is configured as a non-latching
supervisory initiating device. Figure 4-7 illustrates the application.

SD1

SG1

Keyed Maintenance Bypass with AI 2

Figure 4-7. Maintenance Bypass Switch

The required lines of EOC code are as follows:

L1:1*NL1:2=SG1
L1:2=NSG1

April 2018 4-38 P/N 06-237480-001

 Communications to the Control Unit

CHAPTER 5
COMMUNICATIONS TO THE CONTROL UNIT

5-1 INTRODUCTION

A configuration created as described in Chapters 2 through 4 must lastly be uploaded to the ARIES®-
MLX control unit to establish a working fire protection system. The utilities provided in the Tools
drop-down menu (refer to Section 5-2 and Section 5-3) are used to upload the configuration and
communicate with the ARIES-MLX control unit.

Figure 5-1. Tools Drop-Down Menu

Most of the utilities in the Tools drop-down menu can also be accessed via the main or side toolbars.
The icons in the main toolbar are identified in Figure 5-2.

Print File
Save File Compare Configuration
Open File Verify Configuration
New File Receive Network Node Map

Send Configuration Clear Event Log

Receive Configuration Receive Event Log
Online

Figure 5-2. ACT-MLX Main Toolbar

P/N 06-237480-001 5-1 April 2018

Communications to the Control Unit

5-2 HARDWARE CONNECTIONS

Use either a laptop or desktop computer to upload the applications program to the ARIES-MLX
control unit. The computer must have a USB or RS-232 communications port:

• Set the serial-port baud rate to 38400, and use communications cable P/N 74-100016-003 to
communicate with the ARIES-MLX control unit via the computer's serial port.
• Use a standard USB communications cable to connect to the ARIES-MLX control unit via the
computer's USB port.
Note: When using the USB port, the ground fault circuitry is not functional. The USB port is to
be used to download configurations and operating system software only. It is not
intended to be used on a permanent basis. Do not connect or disconnect the USB cable
while the control unit is powering up on system startup or initializing after a new
configuration upload.

A USB Isolator must be used in series with the USB cable when connecting to port J6 as shown
in Figure 5-3. This connection is typically used when sending or receiving information between
the panel and a PC running the panel configuration software.

Kidde Fire Systems has tested and recommends the USB Isolator P/N 10000071.

Note: See Section 5-3.2 for full Communications Setup information.

Figure 5-3 illustrates a typical control unit-to-laptop configuration.

To USB printer
(optional)

J11 J6

To serial printer
RS232 A (optional)

RS232 B

Printer
Main Controller Board
Standard USB Communications Cable

RS-232 Serial Communications Cable To laptop USB port

USB Isolator, P/N 10000071

To laptop serial port

Laptop Computer

Figure 5-3. Hardware Connection from ARIES-MLX Control Unit to Laptop Computer

April 2018 5-2 P/N 06-237480-001

 Communications to the Control Unit

5-3 COMMUNICATION UTILITIES

This section describes the various communication operations available in the Tools drop-down
menu. Each one is listed in Table 5-1 with its descriptive info location in the manual.

Table 5-1. Locations of Communications Utilities Descriptions in Manual

Communication Utility Description Location

Communications Setup Section 5-3.2

Send Configuration Section 5-3.3
Receive Configuration Section 5-3.4
On-Line Section 5-3.5
Get Sensitivity Levels Section 5-3.6
Event Log Section 5-3.7
Receive Test Log Section 5-3.8
Receive Walk Test Log Section 5-3.9
Receive Network Node Map Section 5-3.10
Verify Section 5-3.11
Compare Section 5-3.12

5-3.1 Selecting Node and Entering Password

When communicating with the panel, a password is required. The options presented for entering a
password depend on whether accessing a non-networked panel or a networked system with multiple
nodes. A non-networked panel only requires a password. A networked system requires choosing the
node and entering the password.

For a non-networked panel, the Enter Password screen is similar to Figure 5-4. Enter the password
and press OK.

Figure 5-4. Non-Networked Panel Enter Password Screen

For a networked panel, the Choose Node and Enter Password screen is similar to Figure 5-5. Choose
either the Local Node connected to the PC or select Network Node and pick the specific node. Next,
enter the password and press OK.

P/N 06-237480-001 5-3 April 2018

Communications to the Control Unit

Figure 5-5. Networked Panel Choose Node and Enter Password Screen

5-3.2 Communications Setup

Select Tools>Communication Setup from the main screen to select the communication port
and define options. Do this to set up the computer to transfer data to the ARIES-MLX Control
Unit. Alternatively, you may select the Communication Setup Icon ( ).

In response, the communication settings screen is displayed (see Figure 5-6 and Figure 5-7).

Figure 5-6. USB Communication Setting Screen

April 2018 5-4 P/N 06-237480-001

 Communications to the Control Unit

Figure 5-7. RS232 Communication Setting Screen

5-3.3 Sending a Configuration

Select Tools>Send Configuration to send one particular configuration (created via the methodology
described in Chapters 2 through 4) to a ARIES-MLX control unit. The ARIES-MLX control unit then
assumes the responsibility of monitoring the SLC and other peripheral devices that have been
specified in the configuration file, and carries out the instructions that are encoded in the EOC
statements. Alternatively, you may select the Send Configuration Icon ( ).

5-3.3.1 SELECTING A FILE TO SEND

If only one configuration file is open, the software assumes that this is the configuration to be sent
to the ARIES-MLX control unit. If more than one configuration file is open, the Select Configuration
dialog box (see Figure 5-8) is displayed when Tools>Send Configuration is selected. The
appropriate configuration file must be selected in this screen before proceeding.

Note: A configuration file must be open before the process can proceed.

Figure 5-8. Select A Configuration Screen

With the desired configuration file selected, ACT-MLX will attempt to send the configuration to the
USB or RS-232 connected panel.

P/N 06-237480-001 5-5 April 2018

Communications to the Control Unit

5-3.3.2 SENDING A CONFIGURATION

To send a configuration after specify which configuration to send:

Note: When sending a configuration to a remote networked node, the time to complete the
operation is considerably longer than sending to the local control node. When a
networked node is executing a local upload of the configuration, the node does not
communicate on the network.
1. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1. Refer to the ARIES-MLX Installation, Operation
and Maintenance Manual, P/N 06-237479-001, for an explanation on setting passwords.
2. Select <OK>. In response, a status bar showing the progression of the configuration upload to
the control unit is displayed (see Figure 5-9). After the upload is complete, the Send
Configuration Complete screen appears (see Figure 5-10).

Figure 5-9. Send Configuration Progress Screen

Figure 5-10. Send Configuration Complete Screen

After sending the configuration to the control unit, the control unit will restart, in order to begin using
the new settings. The USB cable should be disconnected upon completion of an upload to the control
unit.

5-3.4 Receive a Configuration

Select Tools>Receive Configuration to retrieve the configuration from a ARIES-MLX control unit
for review, analysis and/or modification as necessary. Alternatively, select the Receive Configuration
Icon ( ). In response, the prompt shown in Figure 5-9 is displayed.

April 2018 5-6 P/N 06-237480-001

 Communications to the Control Unit

5-3.4.1 SELECTING THE FILE TO RECEIVE

The process of receiving a configuration is similar to sending one. You must have at least one
configuration open when receiving a configuration. If more than one configuration is open when
Receive Configuration is selected, a prompt appears requesting a file in which to store the
downloaded configuration data (see Figure 5-11).

Note: A configuration file must be open before the process can proceed.

Figure 5-11. Select A Configuration Screen

With the configuration file selected, ACT-MLX will attempt to receive the configuration of the selected
panel.

5-3.4.2 RECEIVING A CONFIGURATION

To receive a configuration after specify which configuration to receive:

Note: When receiving a configuration to a remote networked node, the time to complete the
operation is considerably longer than receiving the local control node configuration.
When a networked node is executing a download of the configuration, the node does not
communicate on the network.
1. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1. Refer to the ARIES-MLX Installation, Operation
and Maintenance Manual, P/N 06-237479-001, for an explanation on setting passwords.
2. Select <OK>. In response, a status bar showing the progression of the configuration download
(see Figure 5-12). After the download has finished, a notification (see Figure 5-13).

P/N 06-237480-001 5-7 April 2018

Communications to the Control Unit

Figure 5-12. Receive Configuration Progress

Figure 5-13. Receive Configuration Complete

5-3.5 Online

Select Tools>Online to connect ACT-MLX to a control unit via a terminal-emulation mode. This
allows the software to run the control unit as if it were being accessed via its front panel keypad/
display. To enter terminal emulation mode:

1. Select the Online Icon ( ).

2. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1. Refer to the ARIES-MLX Installation, Operation
and Maintenance Manual, P/N 06-237479-001, for an explanation on setting passwords.
3. Select <OK>. The Online window displays (see Figure 5-14).

April 2018 5-8 P/N 06-237480-001

 Communications to the Control Unit

Figure 5-14. Online Terminal-Emulation Mode

Refer to the ARIES-MLX Installation, Operation and Maintenance Manual (P/N 06-237479-001) for
a complete explanation of display messages and for guidance in navigating through the control unit
system menus.

5-3.6 Get Sensitivity Levels

Select Tools>Get Sensitivity Levels to retrieve the current readings of photoelectric, ionization,
thermal, and other types of detectors from the control unit. The results are populated in the
Sensitivity Levels dialog box.

5-3.6.1 RETRIEVE SENSITIVITY LEVELS

1. Select Tools>Get Sensitivity Levels.
2. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1.
3. Click <OK>. The Select A SLC Module screen appears (see Figure 5-15).

Figure 5-15. Select An SLC Module Screen

P/N 06-237480-001 5-9 April 2018

Communications to the Control Unit

4. Enter the password and click <OK>.

5. Select the desired SLC module, and click <OK>. The Range screen appears (see Figure 5-16).

Figure 5-16. Range Screen

6. Enter the range of sensitivity desired.

7. Select <OK>. The following Sensitivity Levels screen appears.

Figure 5-17. Retrieving Sensitivity Levels

Within the Sensitivity Levels Print menu, there are two menu options: Save As and Print.
– Select Save As to save the test log as a .txt file.
– Select Print to send the test log to a printer.

5-3.7 Event Log

Select Tools>Event Log to transfer the contents of the log of system events to a text file. There are
three options: Clear, Receive and Open Log File.

April 2018 5-10 P/N 06-237480-001

 Communications to the Control Unit

5-3.7.1 CLEARING THE EVENT LOG

1. Select Tools>Event Log>Clear to remove all currently-recorded events from the system event
log. Alternatively, you may select the Clear Event Log Icon ( ). In response, a dialog box asks
to continue or not (see Figure 5-18).

Figure 5-18. Event Log Query

2. Click <Yes> to continue.

3. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1.
4. Click <OK>.
The progression of the event log clearance is displayed (see Figure 5-19).

Figure 5-19. Clear Event Log Progression

After the event log has been cleared, a notification is displayed (see Figure 5-20).

Figure 5-20. Clear Event Log Complete

Note: If the control unit is in alarm, trouble or supervisory condition,

clearing the event log is aborted and a notification (see Figure 5-21) is
displayed.

P/N 06-237480-001 5-11 April 2018

Communications to the Control Unit

Figure 5-21. Clear Event Log Abort

5-3.7.2 RECEIVING AN EVENT LOG

1. Select Tools>Event Log>Receive to copy the entire contents of the system event log to a
text file or copy a range of system events within the log based on occurrence dates.
Alternatively, you may select the Receive Event Log Icon ( ). In response, the prompt
shown in Figure 5-22 is displayed.

Figure 5-22. Event Log Data Range

2. Select either the All or Range radio button. If Range is selected, enter the range of dates to receive.
Select <OK>.
3. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1.
4. Select <OK> to download the event log from that node. In response, the progression of the
download (Figure 5-23) is displayed.

Figure 5-23. Receive Event Log Progression

April 2018 5-12 P/N 06-237480-001

 Communications to the Control Unit

When it is complete, the Event Log Retrieved Confirmation Screen displays (see Figure 5-24).

Figure 5-24. Event Log Received Confirmation

5. Select <OK>. In response, the event log (see Figure 5-25) is displayed.

5-3.7.3 THE EVENT LOG

Within the Event Log Screen, there are four menu options: Open, Save, Save As Text, Print, and
Close.

• Select Open to open an existing saved event log.

Note: Because the current event log will be overwritten, do not select Open
to retrieve an existing event log before saving or printing the current
retrieved event log.
• Select Save to save the event log as a .log file.
• Select Save As Text to save the event log as a .txt file.
• Select Print to send the event log to a printer.
• Select Close to close the Event Log screen.

Figure 5-25. Event Log Screen

P/N 06-237480-001 5-13 April 2018

Communications to the Control Unit

5-3.7.4 VIEW EVENT LOG

Select Tools>Event Log>Open Log File to view a previously-downloaded event log offline. Enter the name
of the log file and select <OK>. All event log options in the Event Log Screen are available when viewing
event logs offline.

5-3.8 Receive Test Log

Select Tools>Receive Test Log to copy the contents of the most recent log of initiating device
test events to a text file.

5-3.8.1 RECEIVING A TEST LOG

1. Select Tools>Receive Test Log.
2. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1.
3. Select <OK>. In response, the progression of the test log download (see Figure 5-26) is
displayed.

Figure 5-26. Receive Test Log Progress

4. When the download is complete, the test log is displayed (see Figure 5-27).

Figure 5-27. Test Log Screen

5. Within the Test Log Screen, there are two menu options: Save As Text, Print, and Close.
• Select Save As Text to save the test log as a .txt file.
• Select Print to send the test log to a printer.
• Select Close to close the Test Log screen.

April 2018 5-14 P/N 06-237480-001

 Communications to the Control Unit

5-3.9 Receive Walk Test Log

Select Tools>Receive Walk Test Log to copy the contents of the log of walk-test events created via
the "Walk-Test" procedure in the Test Menu to a text file.

5-3.9.1 RECEIVING A WALK TEST LOG

1. Select Tools>Receive Walk Test Log.
2. Select the node if applicable and enter the password. For details on choosing the node and
entering the password, refer to Section 5-3.1.
3. Select <OK>. In response, the progression of the test log download is displayed (see
Figure 5-28).

Figure 5-28. Receive Walk Test Log Progress

4. When the download is complete, the test log is displayed (see Figure 5-29).

Figure 5-29. Walk Test Log

5. Within the Walk Test Log Screen, there are three menu options: Save As Text, Print, and Close.
• Select Save As Text to save the test log as a .txt file.
• Select Print to send the test log to a printer.
• Select Close to close the Walk Test Log screen.

P/N 06-237480-001 5-15 April 2018

Communications to the Control Unit

5-3.10 Receive Network Node Map

Select Tools> Receive Network Node Map to view a listing of nodes networked with the local panel.
Each node occupies a unique address.

Note: When receiving a network node map, the software does not actively
communicate to each node on the map. It is possible for a listed node
to no longer be connected or communicating. Nodes must be added or
removed manually from the panels.

Figure 5-30. Network Node Map

5-3.11 Verify

Select Tools>Verify to check the syntax of EOC code and verify that the device and circuit addresses
are used properly. Alternatively, select the Verify Icon from the toolbar ( ). In response, the
verification summary (see Figure 5-31) is displayed.

April 2018 5-16 P/N 06-237480-001

 Communications to the Control Unit

Figure 5-31. Verification Summary

Remove errors and warnings where possible. For assistance in removing as many as possible, contact
Kidde Technical Support.

Note: ACT-MLX will not allow the configuration file to be saved if it contains
EOC verification errors, although warnings are permissible.

5-3.12 Compare

Select Tools>Compare to compare two different configuration files. Note that both files must
be open to compare them. Alternatively, select the Compare Icon ( ) from the toolbar. An
example of the comparison results is shown in Figure 5-32.

Figure 5-32. Configuration Compare Results Screen

P/N 06-237480-001 5-17 April 2018

Communications to the Control Unit

THIS PAGE INTENTIONALLY LEFT BLANK.

April 2018 5-18 P/N 06-237480-001

 System Example

APPENDIX A
SYSTEM EXAMPLE

A-1 INTRODUCTION

This appendix is intended to provide an example of a typical system and sequence of operation.

Sequence of Operation

Activate / De-Activate Low-

Activate / De-Activate Low-

Interrupt Impending Water-

Open Pre-Action-Sprinkler
Temporal-Coded Horns

less System Discharge

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate

Activate / De-Activate
Extinguishing System

Smoke-Detector LED

Facility Equipment
Horns @ 120 BPM

Activate Waterless

Abort-Station LED
Horns @ 60 BPM
Room-of-Origin

HVAC Shutdown
Alarms/Actions

Waterflow LED

Power Shutoff
Pressure LED
Release LED

Trouble LED
Tamper LED

Interlocks

Air LED
Strobes

Valve
Waterflow Switch
Head-End Room (Zone 1) A
Power Room (Zone 2) A A A
Sprinkler Tamper Switch
Head-End Room (Zone 1) A
Power Room (Zone 2) A
One Area Smoke Detector
Head-End Room (Zone 1) A A
Power Room (Zone 2) A A
Two Area Smoke Detectors Alarm
(Immediate Response)
Head-End Room (Zone 1) D A A
Power Room (Zone 2) D A A
Two Area Smoke Detectors (30-
Sec. Delayed Response)
Head-End Room (Zone 1) D A A A A D D A
Power Room (Zone 2) D A A A A D D A
Manual Station (Immediate
Response)
Head-End Room (Zone 1) D D A A A A D D A A A
Power Room (Zone 2) D D A A A A D D A A A
Abort Station
Head-End Room (Zone 1) A A
Power Room (Zone 2) A A
Auxiliary Supervisory
Low FM-200 Pressure Sw.
Head-End Room (Zone 1) A
Power Room (Zone 2) A
Low Air (Pre-Action Sys) A
Trouble
Any Condition A

Control-Unit Outputs
NAC 1 Z-1 Z-1
NAC 2 Z-1 Z-1
Combo 1 Z-2 Z-2
Combo 2 Z-2 Z-2
Release 1 Z-1 Z-1
Release 2 Z-2 Z-2
Relay 1
Relay 2
Relay 3
Trouble Relay

SLC Outputs
AO X X

ATM Outputs
Output No. 1 Z-1
Output No. 2 Z-1
Output No. 3 Z-1
Output No. 4 Z-1
Output No. 5 Z-1
Output No. 6 Z-1
Output No. 7 Z-2
Output No. 8 Z-2
Output No. 9 Z-2
Output No. 10 Z-2
Output No. 11 Z-2
Output No. 12 Z-2
Output No. 13 X

A = Activate Output
D = De-Activate Output Note: Central Station reporting is handled by the DACT or City Tie modules.
Z = Zone Defined Below
X = Output Activated

Figure A-1. Example of Sequence of Operation

P/N 06-237480-001 A-1 April 2018

System Example

THIS PAGE INTENTIONALLY LEFT BLANK.

April 2018 A-2 P/N 06-237480-001

 System Operations

System Outline
Signaling-Line-Circuit Configuration

Application Initiating and Control Points Alarm / Supervisory / Trouble Outputs Associated Releasing-Zone Execution Statements

N A ddr. Owne r Location Type App'n Pre-Alm Pre-Al m Alarm Alarm Verify PA S D /N L/N- L I TLCO CTLCO Drill Silence Walk Seq. Fa n G roup Pt . Sp. Gr. Sp. Gen. Gen. Iden. Release Rel. Zn. Rel. Zn. Counting C rossed Iden. Rel. Zn. I den. Concurrent $ Head-End-Room Pre-Alarm

(Leve l 1) (Level 2) (Leve l 1) (Leve l 2) (sec/min) (sec/min) De-Ac t R e-S tart Alm/Sup/Tr Outputs Outputs Tbl. Supv. Zone Pre-Al m P re-Rel Grou p Release Rel . Z n. L1:1#3=SG1,AM1:1,C1

L1:1#3=1.5=AL1:4#6

L1:4#6=SG1,AM1:1,C2

--- 1 Head-End-Room Photo Photo Open-Area ----- 1.5 2.0 3.0 No No No L ----- ----- ----- ----- ----- ----- ----- AI-1A ----- ATM-1 ----- ----- C1 1 Yes Ye s No AI-1B ----- Ye s ----- Z-1 P re-Action L1:4#6=3.0=AL1:1#3

--- 2 Head-End-Room Photo Photo Open-Area ----- 1.5 2.0 3.0 No No No L ----- ----- ----- ----- ----- ----- ----- AI-1A ----- ATM-1 ----- ----- C1 1 Yes Ye s No AI-1B ----- Ye s ----- Z-1 P re-Action $ Power-Room Pre-Alarm

--- 3 Head-End-Room Photo Photo Open-Area ----- 1.5 2.0 3.0 No No No L ----- ----- ----- ----- ----- ----- ----- AI-1A ----- ATM-1 ----- ----- C1 1 Yes Ye s No AI-1B ----- Ye s ----- Z-1 P re-Action L1:14#15=SG3,AM1:7,C3

--- 4 Head-End-Room Ion Ion Open-Area ----- 0.8 1.0 1.5 No No No L ----- ----- ----- ----- ----- ----- ----- AI-1B ----- ATM-1 ----- ----- C2 1 Yes Ye s No AI-1A ----- Ye s ----- Z-1 P re-Action L1:14#15=1.5=AL1:16#17

--- 5 Head-End-Room Ion Ion Open-Area ----- 0.8 1.0 1.5 No No No L ----- ----- ----- ----- ----- ----- ----- AI-1B ----- ATM-1 ----- ----- C2 1 Yes Ye s No AI-1A ----- Ye s ----- Z-1 P re-Action L1:16#17=SG3,AM1:7,C4

--- 6 Head-End-Room Ion Ion Open-Area ----- 0.8 1.0 1.5 No No No L ----- ----- ----- ----- ----- ----- ----- AI-1B ----- ATM-1 ----- ----- C2 1 Yes Ye s No AI-1A ----- Ye s ----- Z-1 P re-Action L1:16#17=3.0=AL1:14#15

--- 7 Head-End-Room Man Rel AI Man. Rel ----- ----- ----- ----- ----- ----- ----- L ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- 1 No No ----- ----- ----- Ye s ----- Z-1 P re-Action $ Head-End-Room Waterflow

--- 8 Head-End-Room Man Rel AI Man. Rel ----- ----- ----- ----- ----- ----- ----- L ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- 1 No No ----- ----- ----- Ye s ----- Z-1 P re-Action L1:11=SG2,AM1:6,RY3

--- 9 Head-End-Room Abort AI Abort/UL/30 s ec ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ----- ATM-2 ----- ----- ----- 1 ----- ----- ----- ----- ----- ----- ----- ----- $ Power-Room Waterflow

--- 10 Head-End-Room Abort AI Abort/UL/30 s ec ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ----- ATM-2 ----- ----- ----- 1 ----- ----- ----- ----- ----- ----- ----- ----- L1:20=SG4,AM1:12,RY3

--- 11 Head-End-Room Waterflow AI Wa terflow ----- ----- ----- ----- ----- ----- ----- L ----- ----- ----- ----- ----- ----- ----- ----- ATM- 6 ----- ----- ----- ----- 1 ----- ----- ----- ----- ----- ----- ----- ----- $ Head-End-Room Tamper

--- 12 Head-End-Room Tamper AI Supervisory ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ATM-5 ----- ----- Y ----- 1 ----- ----- ----- ----- ----- ----- ----- ----- L1:12=AM1:5,L1:25

--- 13 Head-End-Room Low Press AI Tr ouble ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ATM-4 ----- Y ----- ----- 1 ----- ----- ----- ----- ----- ----- ----- ----- $ Power-Room Tamper

--- 14 Power-Room Photo Photo Open-Area ----- 1.5 2.0 3.0 No No No L ----- ----- ----- ----- ----- ----- ----- AI-2A ----- ATM-7 ----- ----- I3 2 Yes Ye s No AI-2B ----- Ye s ----- Z-2 P re-Action L1:21=AM1:11,L1:25

--- 15 Power-Room Photo Photo Open-Area ----- 1.5 2.0 3.0 No No No L ----- ----- ----- ----- ----- ----- ----- AI-2A ----- ATM-7 ----- ----- I3 2 Yes Ye s No AI-2B ----- Ye s ----- Z-2 P re-Action $ Head-End-Room Low Pressure

--- 16 Power-Room Ion Ion Open-Area ----- 0.8 1.0 1.5 No No No L ----- ----- ----- ----- ----- ----- ----- AI-2B ----- ATM-7 ----- ----- I4 2 Yes Ye s No AI-2A ----- Ye s ----- Z-2 P re-Action L1:13=AM1:4

--- 17 Power-Room Ion Ion Open-Area ----- 0.8 1.0 1.5 No No No L ----- ----- ----- ----- ----- ----- ----- AI-2B ----- ATM-7 ----- ----- I4 2 Yes Ye s No AI-2A ----- Ye s ----- Z-2 P re-Action $ Power-Room Low Pressure

--- 18 Power-Room Man Rel AI Man. Rel ----- ----- ----- ----- ----- ----- ----- L ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- 2 No No ----- ----- ----- Ye s ----- Z-2 P re-Action L1:22=AM1:10

--- 19 Power-Room Abort AI Abort/UL/30 s ec ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ----- ATM-8 ----- ----- ----- 2 No No ----- ----- ----- ----- ----- ----- $ Pre-Action-System Low Air

--- 20 Power-Room Waterflow AI Waterflow ----- ----- ----- ----- ----- ----- ----- L ----- ----- ----- ----- ----- ----- ----- ----- ATM-12 ------ ----- ----- ----- 2 ----- ----- ----- ----- ----- ----- ----- ----- L1:26=AM1:13

--- 21 Power-Room Tamper AI Supervisory ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ATM- 11 ----- ----- Y ----- 2 ----- ----- ----- ----- ----- ----- ----- ----- $ Head-End-Room Pre-Release

--- 22 Power-Room Low Press AI Tr ouble ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ATM-10 ----- Y ----- ----- 2 ----- ----- ----- ----- ----- ----- ----- ----- (C1*C2)+L1:7+L1:8=SG1/120,L1:23 $cross-zone or manual pull

--- 23 HVAC Shutdown AO ----- ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- 1 a nd 2 ----- ----- Ye s ----- ----- ----- ----- ----- $ Head-End-Room Release

24 D(C1*C2,30,L1:9,L1:10)+L1:7+L1:8=NSG1,NAM1:1,AR1,SG2,L1:24,RY2,AM1:3
--- Power Shutdown AO ----- ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ---- - 1 and 2 ----- ----- ----- ----- ----- Ye s ----- -----
25 AI Trouble ----- ----- ----- ----- ----- ----- ----- N-L ----- ----- ----- ----- ----- ----- ----- ----- ATM-13 ----- Y ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- L1:9+L1:10=AM1:2 $aborts
--- Pre-Action Low Air
$ Power-Room Pre-Release
(C3*C4)+L1:18=SG3/120,L1:23 $cross-zone or manual pull

$ Power-Room Release

D(C3*C4,30,L1:19)+L1:18=NSG3,NAM1:7,AR2,SG4,L1:24,RY2,AM1:8
L1:19=AM1:8 $abort

P/N 06-237480-001 A-3 (Page A-4 blank) March 2018

 New York City Abort Sequence

APPENDIX B
NEW YORK CITY ABORT SEQUENCE

B-1 INTRODUCTION

The following EOC program example demonstrates a typical method of supporting the unique N.Y.C.
suppression system abort sequence. Use of this program negates the need for any external equipment
to control the notification appliances.

B-2 GENERAL DISCUSSION

This discussion is based on a typical single suppression zone, as illustrated in Figure B-1. The room
contains: six smoke detectors, one manual release station, one abort station, one power shutdown
and one HVAC shutdown.

B-2.1 Sequence of Operation for 3 NAC Solution

• Any detector–Activate the bell.
• Second smoke detector alarm–Turn off bell, turn on horn (pulsing), turn on strobe (steady),
begin (30 second) discharge delay, shut down power, shut down HVAC.
• When timer counts down–Discharge agent, turn on strobes (steady) and horn/strobe (steady).
• Abort Active–Turn off horn, turn off strobe, turn on bell and add 90 seconds to initial time
delay.

B-2.2 System Configuration for 3 NAC Solution

The configuration of the system depicted in Figure B-1 contains the following hardware with assigned
addresses:

• Six Smoke Detectors (1 through 6)

• One Abort Station (7)
• One Manual Release Station (8)
• One Bell (SG1)
• One Horn Circuit (SG2)
• Two Strobes on one circuit (SG3)
• Two Release Devices on one circuit (AR1)

P/N 06-237480-001 B-1 April 2018

New York City Abort Sequence

B-2.3 Sample Programs for N.Y.C. Abort Sequence

Note: When using N.Y.C. Abort, all initiating devices must be set to the default of latching. Non-
Latching must not be used or improper operation of this sequence results.

B-3 SAMPLE PROGRAM 1

$ EOC program for NYC Abort, using one NAC (SG2, a Horn)

L1:1+L1:2+L1:3#4=I3 $ check for any NYC Aborts going Active (make your changes to
the left of the equals sign)

L1:12+L1:13#14=C5 $ check Manual Release Pulls going Active (make your changes to
the left of the equals sign)

L1:102+L1:103#255=C1,I1 $ First Alarm: check for any alarms going Active (make your
changes to the left of the equals sign)
$ also on any of the above 3 lines, possibly set any Output(s), at the end, if desired
$ Copy the following lines exactly as is, with no modifications:

NC5*I1>1=C2,NC1 $ Second Alarm State reached; stop signaling the First Alarm

NC5*I3=C3,C6 $ start the Aborting State (if any Abort is Active)

NI3=NC3 $ stop the Aborting State (if all Aborts are Inactive)

C5=NC3 $ stop the Aborting State (if Release has happened)

C6*NC3*NI1=NC6 $ if stopping the Aborting State and NO Alarms are Active, then
same as Abort has never happened

D(NC5*NC6*C2,30)+C5=C5,AR2 $ Release in 30 seconds, if an Abort has never happened

D(NC5*C6*C2*NC3,90)=C4 $ after 90 seconds, then Re-signal the Second Alarm State (Pre-
Release)

C3=NC4 $ stop signaling the First Alarm State or Second Alarm State, if
presently aborting

D(NC5*C6*C2*NC3,120)+C5=C5,AR2 $ Release in 120 seconds, as long as no more Aborts go Active

$ now handle the NAC signaling

NC5*C3=NSG2 $ stop signaling the First Alarm State and/or Second Alarm State,
if presently aborting

NC5*NC6*NC2*C1=SG2/60 $ signal First Alarm, if an Abort has never happened

NC5*NC3*NC4*C6=SG2/60 $ signal First Alarm, if not presently aborting, but if an Abort has
previously happened

NC5*NC6*C2=SG2/120 $ signal Second Alarm (Pre-Release), while doing 30 second

countdown, if an Abort has never happened

NC5*C4=SG2/120 $ signal Second Alarm (Pre-Release), after the 90 second

countdown, if an Abort previously happened

C5=AR2,SG2/C $ signal that the Release has happened

$
April 2018 B-2 P/N 06-237480-001
 New York City Abort Sequence

B-4 SAMPLE PROGRAM 2

$ EOC program for NYC Abort, using two NACs (SG1, a Bell; and SG2, a Horn)

L1:1+L1:2+L1:3#4=I3 $ check for any NYC Aborts going Active (make your changes to the left
of the equals sign)

L1:12+L1:13#14=C5 $ check Manual Release Pulls going Active (make your changes to the
left of the equals sign)

L1:102+L1:103#255=C1,I1 $ First Alarm: check for any alarms going Active (make your changes to
the left of the equals sign)

$ also on any of the above 3 lines, possibly set any Output(s), at the end, if desired

$ Copy the following lines exactly as is, with no modifications:

NC5*I1>1=C2,NC1 $ Second Alarm State reached; stop signaling the First Alarm

NC5*I3=C3,C6 $ start the Aborting State (if any Abort is Active)

NI3=NC3 $ stop the Aborting State (if all Aborts are Inactive)

C5=NC3 $ stop the Aborting State (if Release has happened)

C6*NC3*NI1=NC6 $ if stopping the Aborting State and NO Alarms are Active, then same as
Abort has never happened

D(NC5*NC6*C2,30)+C5=C5,AR2 $ Release in 30 seconds, if an Abort has never happened

D(NC5*C6*C2*NC3,90)=C4 $ after 90 seconds, then Re-signal the Second Alarm State (Pre-Release)

C3=NC4 $ stop signaling the First Alarm State or Second Alarm State, if
presently aborting

D(NC5*C6*C2*NC3,120)+C5=C5,AR2 $ Release in 120 seconds, as long as no more Aborts go Active

$ now handle the NAC signaling

NC5*C3=NSG1,NSG2 $ stop signaling the First Alarm State and/or Second Alarm State, if
presently aborting

NC5*NC6*NC2*C1=SG1/C $ signal First Alarm, if an Abort has never happened

NC5*NC3*NC4*C6=SG1/C $ signal First Alarm, if not presently aborting, but if an Abort has
previously happened

NC5*NC6*C2=NSG1,SG2/60 $ signal Second Alarm (Pre-Release), while doing 30 second

countdown, if an Abort has never happened

NC5*C4=NSG1,SG2/60 $ signal Second Alarm (Pre-Release), after the 90 second countdown, if

an Abort previously happened

C5=AR2,NSG1,SG2/C $ signal that the Release has happened

P/N 06-237480-001 B-3 April 2018

New York City Abort Sequence

B-5 SAMPLE PROGRAM 3

$ EOC program for NYC Abort, using two NACs (SG2, a Horn; and SG3 a Strobe)

L1:1+L1:2+L1:3#4=I3 $ check for any NYC Aborts going Active (make your changes to
the left of the equals sign)

L1:12+L1:13#14=C5 $ check Manual Release Pulls going Active (make your changes to
the left of the equals sign)

L1:102+L1:103#255=C1,I1 $ First Alarm: check for any alarms going Active (make your
changes to the left of the equals sign)

$ also on any of the above 3 lines, possibly set any Output(s), at the end, if desired

$ Copy the following lines exactly as is, with no modifications:

NC5*I1>1=C2,NC1 $ Second Alarm State reached; stop signaling the First Alarm

NC5*I3=C3,C6 $ start the Aborting State (if any Abort is Active)

NI3=NC3 $ stop the Aborting State (if all Aborts are Inactive)

C5=NC3 $ stop the Aborting State (if Release has happened)

C6*NC3*NI1=NC6 $ if stopping the Aborting State and NO Alarms are Active, then
same as Abort has never happened

D(NC5*NC6*C2,30)+C5=C5,AR2 $ Release in 30 seconds, if an Abort has never happened

D(NC5*C6*C2*NC3,90)=C4 $ after 90 seconds, then Re-signal the Second Alarm State

(Pre-Release)

C3=NC4 $ stop signaling the First Alarm State or Second Alarm State, if
presently aborting

D(NC5*C6*C2*NC3,120)+C5=C5,AR2 $ Release in 120 seconds, as long as no more Aborts go Active

$ now handle the NAC signaling

NC5*C3=NSG2,NSG3 $ stop signaling the First Alarm State and/or Second Alarm State,
if presently aborting

NC5*NC6*NC2*C1=SG2/60 $ signal First Alarm, if an Abort has never happened

NC5*NC3*NC4*C6=SG2/60 $ signal First Alarm, if not presently aborting, but if an Abort has
previously happened

NC5*NC6*C2=SG2/120,SG3/C $ signal Second Alarm (Pre-Release), while doing 30 second

countdown, if an Abort has never happened

NC5*C4=SG2/120,SG3/C $ signal Second Alarm (Pre-Release), after the 90 second

countdown, if an Abort previously happened

C5=AR2,SG2/C,SG3/C $ signal that the Release has happened

April 2018 B-4 P/N 06-237480-001

 New York City Abort Sequence

B-6 SAMPLE PROGRAM 4

$ EOC program for NYC Abort, using three NACs (SG1, a Bell; SG2, a Horn; and SG3 a Strobe)

L1:1+L1:2+L1:3#4=I3 $ check for any NYC Aborts going Active (make your changes to the left
of the equals sign)

L1:12+L1:13#14=C5 $ check Manual Release Pulls going Active (make your changes to the
left of the equals sign)

L1:102+L1:103#255=C1,I1 $ First Alarm: check for any alarms going Active (make your changes to
the left of the equals sign)

$ also on any of the above 3 lines, possibly set any Output(s), at the end, if desired

$ Copy the following lines exactly as is, with no modifications:

NC5*I1>1=C2,NC1 $ Second Alarm State reached; stop signaling the First Alarm

NC5*I3=C3,C6 $ start the Aborting State (if any Abort is Active)

NI3=NC3 $ stop the Aborting State (if all Aborts are Inactive)

C5=NC3 $ stop the Aborting State (if Release has happened)

C6*NC3*NI1=NC6 $ if stopping the Aborting State and NO Alarms are Active, then same
as Abort has never happened

D(NC5*NC6*C2,30)+C5=C5,AR2 $ Release in 30 seconds, if an Abort has never happened

D(NC5*C6*C2*NC3,90)=C4 $ after 90 seconds, then Re-signal the Second Alarm State (Pre-Release)

C3=NC4 $ stop signaling the First Alarm State or Second Alarm State, if
presently aborting

D(NC5*C6*C2*NC3,120)+C5=C5,AR2 $ Release in 120 seconds, as long as no more Aborts go Active

$ now handle the NAC signaling

NC5*C3=NSG1,NSG2,NSG3 $ stop signaling the First Alarm State and/or Second Alarm State, if
presently aborting

NC5*NC6*NC2*C1=SG1/C $ signal First Alarm, if an Abort has never happened

NC5*NC3*NC4*C6=SG1/C $ signal First Alarm, if not presently aborting, but if an Abort has
previously happened

NC5*NC6*C2=NSG1,SG2/60,SG3/C $ signal Second Alarm (Pre-Release), while doing 30 second countdown,

if an Abort has never happened

NC5*C4=NSG1,SG2/60,SG3/C $ signal Second Alarm (Pre-Release), after the 90 second countdown, if

an Abort previously happened

C5=AR2,NSG1,SG2/C,SG3/C $ signal that the Release has happened

P/N 06-237480-001 B-5 April 2018

New York City Abort Sequence

AGENT STORAGE
CONTAINER
AR1

ABORT STATION
STROBE Address
Address 7
SG3
INTELLIGENT
SMOKE
DETECTORS
Address POWER
1 SHUTDOWN
Address
10
MANUAL RELEASE
STATION Address HVAC CONTROL
Address 2 Address
8
9

BELL
Address Address
3 SG1

ARIES-MLX
CONTROL UNIT

Address
4

HORN
Address
SG2
Address
5

STROBE
AGENT STORAGE Address
CONTAINER SG3
AR1 Address
6

Figure B-1. New York City Installation

April 2018 B-6 P/N 06-237480-001

Kidde, ARIES, SmartOne and AnaLASER are registered trademarks of Kidde-Fenwal.
Microsoft and Windows are registered trademarks of Microsoft Corporation.
All trademarks are the properties of their respective owners.

This literature is provided for informational purposes only. KIDDE-FENWAL, INC. believes
this data to be accurate, but it is published and presented without any guarantee or war-
ranty whatsoever. KIDDE-FENWAL, INC. assumes no responsibility for the product's suit-
ability for a particular application. The product must be properly applied to work correctly.
400 Main Street If you need more information on this product, or if you have a particular problem or ques-
tion, contact KIDDE-FENWAL, INC., Ashland, MA 01721 USA. Telephone: (508) 881-2000.
Ashland, MA 01721
Ph: 508.881.2000 P/N 06-237480-001 Rev. AA Copyright© 2018 Kidde-Fenwal, Inc. All Rights Reserved.
Fax: 508.881.8920
www.kiddefiresystems.com