NFS2-3030 Operations Manual — P/N 52546:N1 06/20//2014 43
Mass Notification Alarm Event Operation of the Control Panel
2.8.3 Interpreting Type ID Codes
The Type ID code that displays in a CO pre-alarm message is related to the type and function of the
detector point that initiates the CO pre-alarm. For example, a detector with a P
HOTO/CO Type ID
code means that the detector is a photo/CO type detector. If the Type ID code is unfamiliar, refer to
Appendix A, “Software Type ID Codes”, on page 78. This appendix is an alphabetical list of Type
ID codes and an explanation of each.
2.9 Mass Notification Alarm Event
2.9.1 How the Control Panel Indicates a Mass Notification Alarm
When an Mass Notification initiating device (monitor module) activates, the control panel does the
following:
• Produces a steady audible tone (if the piezo is enabled)
• Does not activate the System Alarm relay(s) (TB4, or TB1 and TB2 if set as Alarm).
• Flashes the
OTHER LED
•Displays
MN ALARM in the upper left corner of the display, a Type Code that indicates the type
of device that activated the fire alarm, and other information specific to the device. The
message occupies the top four lines of the screen, replacing the System Normal message as
shown in Figure 2.10 below. Refer to “Mass Notification Events” on page 16 for a full
description of each message field
• Sends an MN Alarm message to the History buffer and installed printer and annunciators
• Latches the control panel in MN alarm. (You cannot return the control panel to normal
operation until you correct the alarm condition and reset the control panel). If a fire condition
is present on the control panel, a second system reset may be required to clear the MN alarm,
depending on MN Priority programming. Refer to the NFS2-3030 Programming Manual.
• Activates any devices programmed as General Pending
• Activates special zone ZF20.
• Initiates any Control-By-Event actions
• Does not activates the general alarm zone (Z000) or any devices programmed as General
Alarm or Alarm Pending
• Does not cause any devices programmed as “Resound on Fire” to resound.
• Does not send an MN Alarm message to the proprietary receiver via the network, if applicable.
Figure 2.10 Mass Notification Alarm Message Display Example
MN ALARM
SECURITY OFFICE EAST BLDG
FIRST FLOOR ZF20 MN MON
11:58:45A TUE JAN 22, 2013 L03M052
EVENT COUNTS
FIRE ALARMS:000 PREALARM:000 TROUBLE:000
SUPERVISORY:000 SECURITY:000 OTHER: 001
11:59:35A TUE JAN 22, 2013
ACKNOWLEDGE SIGNAL SILENCE
MORE INFORMATION SYSTEM RESET
PROGRAM/ALTER STATUS MAIN MENU
To Next Page
Loading...
Need help?
General
