84 SCS Series Manual — P/N 15712:L 7/18/16
The SCS⁄SCE Programming
Software Type Identification
After installation of the modules required for smoke control, software type IDs must be programmed for all control and monitor modules.
The appropriate software type IDs for control and monitor modules are listed in Table 3.14:
Programming of the software type IDs for control and monitor modules can be accomplished using Partial Point Programming, as shown in
Section 2.4.2, or Full Point Programming, as shown in Section 2.4.4. The following display illustrates the assignment of the software type ID
FRCM to control module 24 control module on SLC loop 5 using partial point programming:
PRESS@1=TYPID,2=CBE,3=LBL,4=OPTNS,5=AMAP,6=CCBE@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@:@1
ENTER@LXX(D/M)YY,@ZXXX@OR@AXXPYY@FOR@PT.@CHANGE@(BCKSPC@TO@ABORT)@@@@@@@:@L5M24
ENTER@TYPE@ID@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@:@FRCM@
Full Point Programming can also be used to program software type IDs and is recommended when programming modules for the first time.
For more information on software type IDs, refer to Chapter 3, Section 1.3.1 Type ID, and Section 3 Software Type IDs, of The
AM2020/AFP1010 Manual.
Control-By-Event
Each control module must be programmed with Control-By-Event (CBE) equations. Each monitor module can be programmed with CBE
lists, but is not required for smoke control. CBE is used to provide a variety of responses based on various combinations of events or initiat-
ing conditions. For FSCS Applications with AM2020/AFP1010 Revision 4.0 software or later, Zone 240 is used to activate FSCS mode pri-
ority. Once this zone is activated, subsequent automatic events will be locked out. Smoke control operation can only be overridden manually.
Each smoke detector input that will lock out the system must be mapped to Z240. Inputs that are not to activate lockout, such as pull stations,
should not be mapped to Zone 240. The CBE equations differ based on the application that the SCS⁄SCE is used for, building type, and build-
ing occupancy. For detailed examples of CBE equations and lists specific to smoke control applications, refer to Section 3.10 “Building-Spe-
cific Operation and Programming Examples”. After the first fire alarm or initiating condition, subsequent fire alarms will not initiate any
further CBE functions for smoke control elements within the system. Additional control after the first fire alarm requires manual intervention
at the SCS⁄SCE.
Programming of CBE for all control modules can be accomplished through Partial Point Programming. After entering the programming
mode, select option 3, partial point programming, of the Main Programming Menu by pressing the following keys at the prompt:
3 [
3=PPRG
Option 3 from the Programming Menu allows the programmer to change the operational parameters of SLC Loop devices, software-defined
zones, and EIA-485 protocol points.
Table 3.14 Module Software Type IDs
Module
Type
Software
Type ID
Type of Device
CM CMXC CM Control Module configured as a Form-C relay. This device is deactivated
when system reset occurs.
CMXS CM Control Module configured as a Notification Appliance Circuit.
FRCM CM Control Module configured as a Form-C relay. This device is not
deactivated when system reset occurs.
MM NOA MM Monitor Module used to monitor contact closure or shorting-type non-alarm
devices.
NOTE:
1. When using the software type ID NOA for smoke control applications, the tracking option for the respective monitor module must be
enabled (see Section 3.9.1, the paragraph entitled “Optional Feature Programming for Control and Monitor Modules” for information on
how to enable tracking).
2. When using software type ID FRCM for a control module, the software type ID for the appropriate CON
ON⁄OP
or CON
OFF⁄CL
protocol
point must be AFCM.
To Next Page
Loading...
Need help?
General
