Nws Manual

Web Server
Installation and Operation Manual

Document 51990
01/15/07 Rev: A4
P/N: 51990:A4 ECN: 06-868
2 Web Server Installation and Operation Manual - P/N: 51990:Rev: A4 01/15/07
Fire Alarm System Limitations
While a fire alarm system may lower insurance rates, it is not a substitute for fire insurance!
An automatic fire alarm systemtypically made up of smoke detec-
tors, heat detectors, manual pull stations, audible warning devices,
and a fire alarm control panel with remote notification capabilitycan
provide early warning of a developing fire. Such a system, however,
does not assure protection against property damage or loss of life
resulting from a fire.
The Manufacturer recommends that smoke and/or heat detectors be
located throughout a protected premise following the recommenda-
tions of the current edition of the National Fire Protection Association
Standard 72 (NFPA 72), manufacturer's recommendations, State and
local codes, and the recommendations contained in the Guide for
Proper Use of System Smoke Detectors, which is made available at
no charge to all installing dealers. A study by the Federal Emergency
Management Agency (an agency of the United States government)
indicated that smoke detectors may not go off in as many as 35% of
all fires. While fire alarm systems are designed to provide early warn-
ing against fire, they do not guarantee warning or protection against
fire. A fire alarm system may not provide timely or adequate warning,
or simply may not function, for a variety of reasons:
Smoke detectors may not sense fire where smoke cannot reach the
detectors such as in chimneys, in or behind walls, on roofs, or on the
other side of closed doors. Smoke detectors also may not sense a
fire on another level or floor of a building. A second-floor detector, for
example, may not sense a first-floor or basement fire.
Particles of combustion or smoke from a developing fire may not
reach the sensing chambers of smoke detectors because:
Barriers such as closed or partially closed doors, walls, or chimneys
may inhibit particle or smoke flow.
Smoke particles may become cold, stratify, and not reach the ceiling
or upper walls where detectors are located.
Smoke particles may be blown away from detectors by air outlets.
Smoke particles may be drawn into air returns before reaching the
detector.
The amount of smoke present may be insufficient to alarm smoke
detectors. Smoke detectors are designed to alarm at various levels of
smoke density. If such density levels are not created by a developing
fire at the location of detectors, the detectors will not go into alarm.
Smoke detectors, even when working properly, have sensing limita-
tions. Detectors that have photoelectronic sensing chambers tend to
detect smoldering fires better than flaming fires, which have little visi-
ble smoke. Detectors that have ionizing-type sensing chambers tend
to detect fast-flaming fires better than smoldering fires. Because fires
develop in different ways and are often unpredictable in their growth,
neither type of detector is necessarily best and a given type of detec-
tor may not provide adequate warning of a fire.
Smoke detectors cannot be expected to provide adequate warning of
fires caused by arson, children playing with matches (especially in
bedrooms), smoking in bed, and violent explosions (caused by escap-
ing gas, improper storage of flammable materials, etc.).
Heat detectors do not sense particles of combustion and alarm only
when heat on their sensors increases at a predetermined rate or
reaches a predetermined level. Rate-of-rise heat detectors may be
subject to reduced sensitivity over time. For this reason, the rate-of-
rise feature of each detector should be tested at least once per year
by a qualified fire protection specialist. Heat detectors are designed
to protect property, not life.
IMPORTANT! Smoke detectors must be installed in the same room
as the control panel and in rooms used by the system for the connec-
tion of alarm transmission wiring, communications, signaling, and/or
power. If detectors are not so located, a developing fire may damage
the alarm system, crippling its ability to report a fire.
Audible warning devices such as bells may not alert people if these
devices are located on the other side of closed or partly open doors or
are located on another floor of a building. Any warning device may
fail to alert people with a disability or those who have recently con-
sumed drugs, alcohol or medication. Please note that:
Strobes can, under certain circumstances, cause seizures in people
with conditions such as epilepsy.
Studies have shown that certain people, even when they hear a fire
alarm signal, do not respond or comprehend the meaning of the signal.
It is the property owner's responsibility to conduct fire drills and other
training exercise to make people aware of fire alarm signals and
instruct them on the proper reaction to alarm signals.
In rare instances, the sounding of a warning device can cause tempo-
rary or permanent hearing loss.
A fire alarm system will not operate without any electrical power. If
AC power fails, the system will operate from standby batteries only for
a specified time and only if the batteries have been properly main-
tained and replaced regularly.
Equipment used in the system may not be technically compatible
with the control panel. It is essential to use only equipment listed for
service with your control panel.
Telephone lines needed to transmit alarm signals from a premise to
a central monitoring station may be out of service or temporarily dis-
abled. For added protection against telephone line failure, backup
radio transmission systems are recommended.
The most common cause of fire alarm malfunction is inadequate
maintenance. To keep the entire fire alarm system in excellent work-
ing order, ongoing maintenance is required per the manufacturer's
recommendations, and UL and NFPA standards. At a minimum, the
requirements of NFPA 72 shall be followed. Environments with large
amounts of dust, dirt or high air velocity require more frequent mainte-
nance. A maintenance agreement should be arranged through the
local manufacturer's representative. Maintenance should be sched-
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 the fire alarm control panel. Disconnect all sources of power
before servicing. The control unit and associated equipment may be
damaged by removing and/or inserting cards, modules, or intercon-
necting cables while the unit is energized. Do not attempt to install,
service, or operate this unit until this manual is read and understood.
CAUTION - System Reacceptance Test after Software Changes.
To ensure proper system operation, this product must be tested in
accordance with NFPA 72 after any programming operation or
change in site-specific software. Reacceptance testing is required
after any change, addition or deletion of system components, or after
any modification, repair or adjustment to system hardware or wiring.
All components, circuits, system operations, or software functions
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 sys-
tem operation verified.
This system meets NFPA requirements for operation at 0C to 49C
(32F to 120F) and at a relative humidity 93% 2% RH (noncon-
densing) at 32C 2C (90F 3F). However, the useful life of the
system's standby batteries and the electronic components may be
adversely affected by extreme temperature ranges and humidity.
Therefore, it is recommended that this system and all peripherals be
installed in an environment with a nominal room temperature of 15-
27 C/60-80 F.
Verify that wire sizes are adequate for all initiating and indicating
device loops. Most devices cannot tolerate more than a 10% I.R.
drop from the specified device voltage.
Like all solid state electronic devices, this system may operate
erratically or can be damaged when subjected to lightning-induced
transients. Although no system is completely immune from lightning
transients and interferences, proper grounding will reduce susceptibil-
ity. Overhead or outside aerial wiring is not recommended, due to an
increased susceptibility to nearby lightning strikes. Consult with the
Technical Services if any problems are anticipated or encountered.
Disconnect AC power and batteries prior to removing or inserting
circuit boards. Failure to do so can damage circuits.
Remove all electronic assemblies prior to any drilling, filing, ream-
ing, or punching of the enclosure. When possible, make all cable
entries from the sides or rear. Before making modifications, verify that
they will not interfere with battery, transformer, and printed circuit
board location.
Do not tighten screw terminals more than 9 in-lbs. Over-tightening
may damage threads, resulting in reduced terminal contact pressure
and difficulty with screw terminal removal.
Though designed to last many years, system components can fail
at any time. This system contains static-sensitive components.
Always ground yourself with a proper wrist strap before handling any
circuits so that static charges are removed from the body. Use static-
suppressive packaging to protect electronic assemblies removed from
the unit.
Follow the instructions in the installation, operating, and program-
ming manuals. These instructions must be followed to avoid damage
to the control panel and associated equipment. FACP operation and
reliability depend upon proper installation by authorized personnel.
Acclimate Plus, HARSH, NOTIFIRENET, VeriFire, NION, NOTIFER Intergrated Systems and ONYXWorks are trademarks, and ONYX, FlashScan,
UniNet, VIEW, NOTIFIER are registered trademarks of Honeywell. Simplex is registered trademark of Tyco International Ltd. Echelon is a registered trademark and
LonWorks is a trademark of Echelon Corporation. ARCNET is a registered trademark of Datapoint Corporation. Microsoft and Windows are registered trademarks of
the Microsoft Corporation. LEXAN is a registered trademark of GE Plastics, a subsidiary of General Electric Company.
Thursday, May 03, 2007 by Honeywell International Inc. All rights reserved. Unauthorized use of this document is strictly prohibited.
FCC Warning
WARNING: This equipment generates, uses, and can radi-
ate radio frequency energy and if not installed and used in
accordance with the instruction manual, may cause interfer-
ence to radio communications. It has been tested and
found to comply with the limits for class A computing device
pursuant to Subpart B of Part 15 of FCC Rules, which is
designed to provide reasonable protection against such
interference when operated in a commercial environment.
Operation of this equipment in a residential area is likely to
cause interference, in which case the user will be required
to correct the interference at his own expense.
Canadian Requirements: This digital apparatus does not
exceed the Class A limits for radiation noise emissions from
digital apparatus set out in the Radio Interference Regula-
tions of the Canadian Department of Communications.
Le present appareil numerique n'emet pas de bruits radio-
electriques depassant les limites applicables aux appareils
numeriques de la classe A prescrites dans le Reglement sur
le brouillage radioelectrique edicte par le ministere des
Communications du Canada.
Documentation Feedback
Your feedback helps us keep our documentation up-to-date and accurate. If you have any comments, you can email
us.
Please include the following information:
Product name and version number (if applicable)
Manual page number
Your comment
Send email messages to:
FireSystems.TechPubs@honeywell.com
Please note this email address is for documentation feedback only. If you have any technical issues, please contact
Technical Services.
Table of Contents
Section 1 Web Server Features ............................................................................................... 7
1.1: Product Description .......................................................................................................................................7
1.1.1: Web Server Features............................................................................................................................7
1.2: Related Documentation .................................................................................................................................8
Table 1.1 Related Documentation ..........................................................................................................8
1.3: Standards and Specifications .........................................................................................................................8
1.4: Compatibility .................................................................................................................................................9
Table 1.2 NFN Compatibility Table.......................................................................................................9
1.5: System Requirements ..................................................................................................................................10
1.6: System Architecture..................................................................................................................................... 11
1.6.1: NFN Network Architecture ...............................................................................................................11
Figure 1.1 Web Server NCM Architecture...........................................................................................11
1.6.2: Standalone Panel Architecture...........................................................................................................12
Figure 1.2 Web Server Direct Panel Architecture................................................................................12
Section 2 Web Server Hardware Installation........................................................................ 13
2.1: Required Components .................................................................................................................................13
2.2: Web Server Installation Overview...............................................................................................................14
2.2.1: Web Server PC Board Layout ...........................................................................................................14
Figure 2.1 Web Server PC Board.........................................................................................................14
2.2.2: Web Server Example Installation Diagram.......................................................................................15
Figure 2.2 Example Installation Diagram............................................................................................15
2.3: CAB3/CAB4 Cabinet Installation ...............................................................................................................16
Figure 2.3 CAB-3/CAB-4 Series Installation Document, 15330.........................................................16
2.4: Web Server Assembly Installation...............................................................................................................17
Figure 2.4 Web Server Assembly Installation Diagram.......................................................................17
2.5: Network Communication Module Installation ............................................................................................18
Figure 2.5 NCM W/F PC Board Installation Document, 51533..........................................................18
Section 3 Web Server Configuration..................................................................................... 19
3.1: Web Server Configuration ...........................................................................................................................19
3.1.1: Web Server Configuration Overview................................................................................................19
3.1.2: Web Server Power Supply Connection .............................................................................................20
Table 3.1 46175 Power Supply Specifications.....................................................................................20
Figure 3.1 Web Server Power Connection...........................................................................................20
3.1.3: Install VeriFire Tools for Configuration..........................................................................................21
3.1.4: Initial Web Server Configuration ......................................................................................................22
Figure 3.2 PC to Web Server Connection ............................................................................................22
Figure 3.3 Serial Port Configuration Utility.........................................................................................22
Figure 3.4 VeriFire Tools Local Connection Type.............................................................................23
Figure 3.5 Nodes Screen.......................................................................................................................23
Figure 3.6 Node Address Change.........................................................................................................23
Figure 3.7 IP Network Cable Connections...........................................................................................24
Figure 3.8 IP Address Entries...............................................................................................................24
3.1.5: NFN Network Connections ...............................................................................................................25
Figure 3.9 NCM-W/F Power Connection ............................................................................................25
Figure 3.10 DB-9 to NUP Connection .................................................................................................26
3.1.6: Change the Web Server Node Address Using an IP Connection......................................................27
Figure 3.11 Hardware Connections......................................................................................................27
Figure 3.12 Selecting the Connection Type .........................................................................................27
Figure 3.13 Configuring the Web Server Connection Session.............................................................28
Figure 3.14 VeriFire Tools System Password ....................................................................................28
Figure 3.15 Selecting the Connection Type .........................................................................................29
Table of Contents
Section 4 Web Server Operation........................................................................................... 31
4.1: Browser Security Settings............................................................................................................................31
4.2: Web Server Security.....................................................................................................................................32
Figure 4.1 Web Server Login Dialog ...................................................................................................32
4.3: The Web Server Interface ............................................................................................................................33
Figure 4.2 Web Server Home Page ......................................................................................................33
4.4: System Administration.................................................................................................................................33
4.4.1: Auto Detect Points on All Panels ......................................................................................................33
Figure 4.3 Auto Detect Points ..............................................................................................................34
Figure 4.4 Auto Point Detect AFP400 Message...................................................................................34
Figure 4.5 Auto Point Detect Screen....................................................................................................35
4.4.2: E-mail Notification ............................................................................................................................36
Figure 4.6 E-mail Configuration...........................................................................................................36
Figure 4.7 E-mail Profile Configuration...............................................................................................37
Figure 4.8 E-mail Configuration - Custom Messages ..........................................................................38
Figure 4.9 Sample E-mail Message......................................................................................................38
4.4.3: System Settings..................................................................................................................................39
Figure 4.10 System Settings .................................................................................................................39
4.4.4: Monitoring Profiles............................................................................................................................41
Figure 4.11 Monitoring Profiles ...........................................................................................................41
4.4.5: Node Mapping ...................................................................................................................................42
Figure 4.12 Node Mapping...................................................................................................................42
4.4.6: Password Configuration.....................................................................................................................43
Figure 4.13 User Configuration............................................................................................................43
4.4.7: Authorization Log..............................................................................................................................44
Figure 4.14 Authorization Log .............................................................................................................44
4.5: Diagnostics...................................................................................................................................................45
4.5.1: Version Information...........................................................................................................................45
Figure 4.15 Version Information..........................................................................................................45
4.5.2: Network Statistics Summary .............................................................................................................46
Figure 4.16 Network Statistics Summary.............................................................................................46
4.5.3: NUP Port Statistics Summary............................................................................................................47
Figure 4.17 NUP Port Statistics Overview...........................................................................................47
Figure 4.18 Local Node NUP Port Statistics........................................................................................47
4.6: Multiple Event List ......................................................................................................................................48
Figure 4.19 Event List Summary..........................................................................................................48
Figure 4.20 Multiple Event List Details ...............................................................................................49
Figure 4.21 Multiple Event List Details Descriptions..........................................................................49
4.7: Screen Details and Options for Specific Panels...........................................................................................50
Figure 4.22 Panel Properties Display Sample ......................................................................................50
Figure 4.23 Loop Properties Sample Screen ........................................................................................51
Figure 4.24 Module Properties Sample Screen ....................................................................................51
Figure 4.25 Detector Properties Sample Screen...................................................................................52
Index ........................................................................................................................................ 53
Section 1 Web Server Features
1.1 Product Description
The NOTIFIER Web Server (Web Server) is a web-based device that acts as an HTML server that
allows remote access to the NFN network (NFN) via the Internet or an Intranet. With the Web
Server interface, the user can view the history of a fire alarm control panel (FACP), event status,
device properties, and other information based on access permissions defined by the system
administrator. All data available on the Web Server is a snapshot of the data on the NFN network
at the time the browser requested the information. The Web Server communicates to NFN network
version 5.0 and later. The Web Server interfaces to the Internet/Intranet using an IP-based wire
Ethernet connection.
1.1.1 Web Server Features
These are some of the features of the Web Server.
Ability to access NFN network nodes, system statuses, and properties remotely using the
Internet or Intranet.
Compatible with NFN network version 5.0 and above.
One Web Server supports multiple users.
Standard IP over Ethernet connection.
Up to 128 user accounts are supported.
Built-in password security and user access record
Supports Microsoft Internet Explorer 5 and above.
Intuitive web browser user interface.
Sends up to 50 E-mails in response to any system event.
Web Server Features Related Documentation
1.2 Related Documentation
Below is a list of documentation that relates to the use of the Web Server.
1.3 Standards and Specifications
The Web Server has been designed to comply with standards set forth by the following regulatory
agencies:
Underwriters Laboratories Standard UL 864. (Other Honeywell products on the same
hardware platform may not yet be listed to this standard.)
NFPA 72 National Fire Alarm Code.
CAN/ULC - S527-M99 Standard for Control Units for Fire Alarm Systems.
UL-1076 Proprietary Burglar Alarm Units and Systems.
The contents of this manual are important and must be kept in close proximity of the hardware. If
building ownership is changed, this manual and all other testing and maintenance information must
also be passed to the current owner of the facility. A copy of this manual was shipped with the
equipment and is also available from the manufacturer.
Table 1.1 Related Documentation
For information on Refer to Part No.
Compatible Devices Device Compatibility Document 15378
Cabinets & Chassis CAB-3/CAB-4 Series Installation Document 15330
Offline Programming Utility VeriFire Tools on-line help file
VeriFire Medium Systems on-line help file
VeriFire-TCD
VeriFire-CD
VeriFire-TCDNetworking NFN Manual
NCM-W/F Installation Document
MIB Media Interface Board Manual
51584
51533
50255
Panels and Annunciators NFS-320 Installation/Operation/Programming Manual
NFS-640 Installation/Operation/Programming Manual
NFS2-640 Installation/Operation/Programming Manual
NFS-3030 Installation/Operation/Programming Manual
NFS2-3030 Installation/Operation/Programming Manual
Network Control Annunciator (NCA) Manual
Network Control Annunciator-2 (NCA-2) Manual
Network Control Station (NCS) Manual
AFP-200 Operating Instruction Manual
AFP-300/400 Installation/Operation/Programming Manual
AM2020/AFP1010 Installation, Operation, and Programming Manual
DVC Series Digital Voice Command Manual
Uninet 2000 Online Installation and Operation Manual
52745/52746/52747
52544/52545/52546
52741/52742/52743
51330/51344/51345
52544/52546/52545
51482
52482
51095
15620
50253/50260/50259
15088
52411
51994
!
WARNING:
Improper installation, maintenance, or lack of routine testing could result in system malfunction.
Compatibility Web Server Features
1.4 Compatibility
The Web Server behaves as any other node on NFN network and is compatible with the following
node types:
Table 1.2 NFN Compatibility Table
NFN Node Type Network Board Used
AFP-200 NAM
AFP-300/400 NAM
AFP-1010 MIB-WPCC
AM2020 SIB-NET
DAA NCM-W/F
DVC* NCM-W/F
NFS-320* NCM-W/F
NFS-640* NCM-W/F
NFS2-640* NCM-W/F
NFS-3030* NCM-W/F
NFS2-3030* NCM-W/F
NCA* NCM-W/F
NCA-2* NCM-W/F
NCS NCM-W/F
*Supported NOTIFIER panel or annunciator that allow direct connection
from Web Server DB-9 connector to its CPU motherboards NUP port.
NOTE: The Web Server is not intended as a primary annunciator and is ancillary in nature. No NCM
W/F PC board is required when the Web Server connects directly to a supported NOTIFIER panel or
annunciator when it is a standalone panel or annunciator.
Web Server Features System Requirements
1.5 System Requirements
Browser
Microsoft Internet Explorer version 5.0 or later.
VeriFire Tools (sold separately)
NOTE: Web Server application is only supported in Microsoft Internet Explorer.
NOTE: The Web Server is compatible with VeriFire Tools version 4.5 or later.
System Architecture Web Server Features
1.6 System Architecture
These are connections options for the Web Server architecture:
NFN network connection; a connection is made to a NCM PC board that is on the same NFN
network as the Web Server (Figure 1.1).
Direct panel connection; a connection is made directly to a supported NOTIFIER panel or
annunciator (Figure 1.2). Refer to Table 1.2 on page 9 for a list of supported panels and
annunciators.
An Internet or Intranet IP network connection is used with both architectures.
1.6.1 NFN Network Architecture
Figure 1.1 Web Server NCM Architecture
CAB3/4 cabinet with
PC Web Browser Interface
Internet
Intranet
FACP
NCS
UniNet/NFN NION
BACnet Gateway
FACP
NCS
UniNet/NFN NION
ONYXWorks
ONYXWorks
Supported Notifier FACP Supported Notifier FACP
Web Server Assembly
and NCM-W/F PC Board
NCM-W/F PC Board
NOTI FIRE NET Network
Web Server Features System Architecture
1.6.2 Standalone Panel Architecture
Figure 1.2 Web Server Direct Panel Architecture
Web Server Assembly
PC Browser Interface
Internet
Intranet
Supported Notifier FACP with
Section 2 Web Server Hardware Installation
2.1 Required Components
The Web Server requires the following:
Web Server Assembly
Web Server PC board (P/N 46173).
Power supply (P/N 46175) - used for supplying +24VDC to +5VDC to the Web Server PC
board.
Web Server/Power Supply Mounting Plate (P/N 18541).
HDD Power connector (P/N 75581) - used for supplying +24VDC to +5VDC to the Web
Server PC board.
PNET-1 surge suppressor (P/N PNET-1).
RJ45 to RJ45 standard Ethernet network cable (P/N 75585) - used to connect the Web Server
PC board to PNET-1 surge suppressor.
DB9 to NUP Cable (P/N 75554) - used to connect the Web Server PC board to an NCM-W/F
board.
NUP to +24VDC power cable (P/N 75583) - used for supply power to the NCM-W/F board.
Network Components
VeriFire Tools v4.5 or later (contact Technical Services).
RJ45 to RJ45 standard Ethernet network cable - customers internet or intranet connection to
PNET-1 surge suppressor (supplied by customer).
NFN Network - version 5.0 and above (sold separately).
Network Communication Module: NCM-W/F board - used to facilitate network
communication between the Web Server and NFN network (sold separately).
Cabinet and Hardware (sold separately)
CAB-3/CAB-4 series cabinet.
CHS-4L chassis.
Customer Supplied Equipment
PC to Web Server connector cable - connects the Web Server to a PC for configuration tasks.
NOTE: The Web Server is for ancillary use only and does not increase the burglary grade of service for
the system.
NOTE: No NCM W/F PC board is required when the Web Server connects directly to a
supported NOTIFIER panel or annunciator when it is a standalone panel or annunciator. Refer
to Table 1.2 on page 9 for a list of supported panels and annunicators.
Web Server Hardware Installation Web Server Installation Overview
2.2 Web Server Installation Overview
This is the recommend installation order:
CAB3/CAB4 Cabinet Installation on page 16
Web Server Assembly Installation on page 17.
Network Communication Module Installation on page 18 (if applicable).
2.2.1 Web Server PC Board Layout
Figure 2.1 Web Server PC Board
DB9-NUP Connector -
used for operation as
the network connection
to NFN
RJ45 Ethernet
Connector (CN2)
HDD Power
Connector (P1)
NOTE: The replacement of the lithium battery on the PC board is to be performed by a trained
technician.
Web Server Installation Overview Web Server Hardware Installation
2.2.2 Web Server Example Installation Diagram
Figure 2.2 shows the components and connections of a Web Server assembly mounted inside a
CAB-3/CAB-4 series enclosures with a direct communication connection being made to a FACP
and the power connection to the P/N 46175 power supply both in that same enclosure.
Figure 2.2 Example Installation Diagram
Z X C V B N M
A S D F G H J K L
Q W E R T Y U I O P
*
#
&
/
+
(
)
1 2 3 4 5 6 7 8 9 0
! @ = , % : / . ?
DISABLE
ENABLE
NEXT
SELECTION
PREVIOUS
SELECTION
RECALL
LAST
ENTRY
INCREMENT
NUMBER
SPACE
FIRE
ALARM
ACKNOWLEDGE
STEP DISPLAY
SILENCE
PREALARM SECURITY SUPERVISORY SYSTEM
TROUBLE
DISABLED
POINTS
ALARM
SILENCED
POWER
DRILL
HOLD 2 SECONDS
RESET LAMP
TEST
Esc
Enter
+24VDC power
Fire Alarm Control Panel (FACP)
PNET-1 connection
To Customers
Direct data connection
Mounting Plate
FACP Chassis
PC Board
Internet or Intranet
connection from
power supply to
PC board power
supply connector
between FACP NUP Port
and DB-9 Connector
NOTE: All wiring from the power supply is power limited, and a separation of at least (6.35
mm) must be maintained between power limited and non-power limited wiring
NOTE: All Web Server circuits are power limited. Route wiring per the power limited and non-
power limited constraints defined in the pertinent Fire Alarm Control Panel manual.
Web Server Hardware Installation CAB3/CAB4 Cabinet Installation
2.3 CAB3/CAB4 Cabinet Installation
Step 1. Install a new CAB-3/CAB-4 series cabinet according to the requirements of the local
authority having jurisdiction or prepare an existing CAB-3/CAB-4 series cabinet that
houses a supported NOTIFIER panel or annunciator. Refer to Table 1.2 on page 9 for
list of supported panels and annunciators.
Step 2. After the CAB3/CAB4 cabinet is prepared with the CHS-4L chassis installed, perform the
Web Server Assembly Installation on page 17.
Figure 2.3 CAB-3/CAB-4 Series Installation Document, 15330
NOTE: The CAB3/CAB4 cabinet is ordered separately. For installation details, refer to the CAB-
3/CAB-4 Series Installation Document, 15330 and or the panels or annunciators documentation.
CAB-3/CAB-4 Series Cabinets
Product Installation Document
PN 15330:G 05/23/2005 05-310
1 General
All cabinets are fabricated from 16 gauge steel. The cabinet consists of two basic components: a backbox and a locking
door.
The key-locked door is provided with a pin-type hinge, two keys, and the necessary hardware to mount the door to the
backbox. The backbox has been engineered to provide ease-of-entry for the installer. Knockouts are positioned at
numerous points to let the installer bring conduit into the enclosure easily. Doors can be mounted on the left or right-hand
side. The same hinge works in both configurations, so that this choice can be made in the field. The door opens 180.
Cabinets are available in four (4) sizes, A through D. The outside dimensions are noted on each enclosure diagram. "A"
size accommodates one chassis, a power supply, and two 26 AH batteries; "D" size accommodates four chassis, a power
supply, and two 26 AH batteries. A trim ring option is available for semi-flush mounting. The CAB-3/CAB-4 Series is
compatible with multiple chassis including the CHS-M2, CHS-M3, CHS-4, CHS-4L, CHS-4N, CHS-BH, CHS-PS, CA-1,
and CA-2. Note: CAB-4 series backboxes and doors are sold separately.
2 Before You Begin
The option of mounting doors in either a left/right hand configuration
will aid in installation and service when two control panels are
mounted in a confined area or side by side (as shown). In this manner
the doors can be opened "barn door" style, permitting an open work
space. Note that in this type of installation it is necessary to leave
enough space between cabinets to insert a key into the locks on the
door frames.
IMPORTANT: Attach the two hinges and two alignment tabs to the
backbox before any equipment is installed. With chassis installed,
space is very limited.
Display Interface Assembly Note: When the door is left-hand
mounted, the Display Interface Assembly (DIA) dress panel cannot be
opened when the door is at less than a 120 angle to the cabinet. If you are using the left-hand mounting option, be sure
that the door can open at least 120. This is especially important if the cabinet is to be mounted in a closed area, such as a
closet or utility room.
3 Door Assembly Instructions
Hinges can be either left or right hand mounted. The Illustrations and text depict a left hand mounted example. For a right
hand mounting, simply substitute right for left in the instructions.
1. Insert door hinges (A) into the top and bottom slots of the side to be hinged (in this case the LEFT side). Secure the
hinges to the studs in the backbox with the #8 hex nuts provided. Note that the small hole on the outer tab faces
outward.
2. Thread stud (B) into the BOTTOM hinge first. Thread from the bottom up. Place the grounding "star" washer on the
stud. Place the door's lower corner onto this stud. Placing the door on the lower stud first provides a place for the door
to rest while you complete the assembly.
C
A
B
d
o
o
r
L
H
.w
m
f
C
A
B
d
o
o
r R
H
.w
m
f
Web Server Assembly Installation Web Server Hardware Installation
2.4 Web Server Assembly Installation
Step 1. Install Web Server PC board onto the mounting plate.
Step 2. Install power supply onto the mounting plate.
Step 3. Install PNET-1 onto the mounting plate.
Step 4. Install the mounting plate onto the CHS-4L chassis that is already installed in the
CAB3/CAB-4 cabinet.
Step 5. Ground the PNET-1.
Step 6. You are now ready to perform theNetwork Communication Module Installation on
page 18 if its use is applicable to your installation, if not perform the Web Server
Configuration on page 19.
Figure 2.4 Web Server Assembly Installation Diagram
1
2
3
4
5
6
Web Server Hardware Installation Network Communication Module Installation
2.5 Network Communication Module Installation
Step 1. If applicable to your Web Server installation, install the type of NCM W/F PC board you
will use into the new CAB3/CAB4 cabinet or an existing panels or annunciators cabinet.
Use the Network Control Module PC board configuration that fits your installation needs.
NCM-W with twisted pair wire.
NCM-F with fiber-optic cable.
Figure 2.5 NCM W/F PC Board Installation Document, 51533
Step 2. After the installation perform Web Server Configuration on page 19.
NOTE: For installation details, refer to the NCM Installation Document (51533) or the supported
NOTIFIER panels or annunciators documentation.
12 Clintonville Road
Northford, CT 06472-1653 USA
203-484-7161 FAX 203-484-7118
www.notifier.com
NCM Installation Document
Network Communications Module NCM-W, NCM-F
y p y
PN 51533:B 11/29/2005 05-238
1 UL 864 Compliance
1.1 Products Subject to AHJ Approval
This product has been certified to comply with the requirements in the Standard for Control Units and Accessories for Fire
Alarm Systems, UL 864 9th Edition.
The following products have not received UL 864 9th Edition certification and may only be used in retrofit applications.
Operation of the NCM-W, NCM-F with products not tested for UL 864 9th Edition has not been evaluated and may not
comply with NFPA 72 and/or the latest edition of UL 864. These applications will require the approval of the local
Authority Having Jurisdiction (AHJ).
AM2020/AFP1010
MIB
NAM-232
2 Product Overview
The Network Communications Module (NCM) provides a means for connecting specific Notifier fire alarm control
products to NOTIFIRENET. There are two types of NCMs available: NCM-W for connecting nodes with
twisted-pair wire, and NCM-F for connecting nodes with fiber-optic cable.
In most applications, one NCM is required per NOTIFIRENET node (including fire alarm control panels and
network annunciators) . Even though the NCM has two NUP ports, only one may be connected to a NOTIFIRENET.
node. Except in some DVC applications, do not connect two NCMs via NUP ports (aka NUP to NUP).
For instructions on the additional capabilities available with the DVC, refer to the DVC Manual.
Input power requirements: 24 VDC , 0.11 amps, regulated, power-limited compatible power supply UL/ULC listed
for fire protective signalling use.
Communications circuit requirements: Refer to the NOTIFIRENET Manual (Network Version 4.0 and Higher)
for wiring length and threshold information.
Section 3 Web Server Configuration
3.1 Web Server Configuration
3.1.1 Web Server Configuration Overview
Perform the web server configuration in this order:
Web Server Power Supply Connection on page 20.
Initial Web Server Configuration on page 22.
NFN Network Connections on page 25.
!
CAUTION:
Different sources of power are used in conjunction with this product. Disconnect all sources of power
before servicing. This device and associated equipment may be damaged by removing and/or inserting
cards, modules or interconnecting cables while this unit is powered. This damage may adversely affect
the operation of this unit, but its effect may not be readily apparent.
Web Server Configuration Web Server Configuration
3.1.2 Web Server Power Supply Connection
The power supply for the Web Server is a +24VDC to +5VDC unit (P/N 46175). It requires
+24VDC @ 330 mA nominal and battery backup in accordance with local code requirements.
Figure 3.1 Web Server Power Connection
Table 3.1 46175 Power Supply Specifications
TYPICAL MIN MAX
Input Voltage +24VDC +19VDC +29V
Input Current @ +24VDC 360 mA without NCM
450 mA with NCM
Output Voltage +5V +4.8V +5.2V
Output Current @ +24VDC 1.2 A
+5VDC Output
Earth
+24VDC Input
24VDC REF Input
Red wire
Black wire
To NWS PC Boards
HDD Power Connector
5V REF Output
P/N 75581
3.1.3 Install VeriFire Tools for Configuration
The VeriFire Tools software application is used to configure the Web Server. Use these steps as
guideline to install the application onto the PC or laptop.
Step 1. Install VeriFire Tools software application using the instructions provided with the
product.
Step 2. After the Serial Configuration Tool is installed, perform Initial Web Server
Configuration on page 22.
NOTE: VeriFire Tools version 4.5 or later is required. Contact Technical Services if you need to
acquire a copy of VeriFire Tools version 4.5 or later.
3.1.4 Initial Web Server Configuration
PC to Web Server PC Board Connection and Configuration
Step 1. Make the cable connection between the PC with the Serial Configuration Tool installed
and the Web Server (Figure 3.2).
Figure 3.2 PC to Web Server Connection
Step 2. Start VeriFire Tools software application, select Start >Programs >VeriFire Tools >Serial
Port Configuration Utility. The NUP Serial Port Auto Configuration window displays.
Step 3. To activate communication link (connector to connector) between the PC with VeriFires
Tools installed and the NWS-2; on the NUP Serial Port Auto Configuration window, click
on the Auto Configuration button to establish communications (Figure 3.3).
Figure 3.3 Serial Port Configuration Utility
Step 4. Once the SUCCESS: message is displayed, Exit the window.
Step 5. After the "PC to Web Server PC Board Connection and Configuration" is completed,
perform NFN Network Configuration on page 23.
PC Board
To EIA-232 port on PC with VeriFire Tools Installed
To EIA-232 port on PC Board
NOTE: The DB9 to DB9 cable must be supplied by customer and it must be a null-modem cable.
NFN Network Configuration
This is a continuation of the initial configuration.
Step 1. Select Start >Programs >VeriFire Tools >VeriFire Tools. The New Session window
displays.
Figure 3.4 VeriFire Tools Local Connection Type
Step 2. Select Local as the New Session. The Nodes window displays.
Figure 3.5 Nodes Screen
Step 3. Double click on the Node Type (NFN WEB SERVER). The NTSRun Time window
displays.
Step 4. Select Panel >Node Address Change. The Node Address Change window displays.
Step 5. Type in the node address and then click Update to apply the changes.
Figure 3.6 Node Address Change
Step 6. After "PC to Web Server PC Board Connection and Configuration" is complete, perform
"IP Network Connection and Configuration".
IP Network Connection and Configuration
This is a continuation of the initial configuration.
This connection is between the Web Server and your IP network (Internet or Intranet). A PNET-1
surge suppressor must be used between the Web Server PC board and your network (Figure 3.7).
Figure 3.7 IP Network Cable Connections
Step 1. Plug one end the RJ45 cable into the Web Server PC board and the other into the square
end of the PNET-1.
Step 2. Connect your IP network RJ45 cable into the round end of PNET-1.
The Web Server can be used as a web-based communication user interface between a NFN
network and VeriFire Tools. The Ethernet port on the Web Server computer connects to
the Ethernet port on a PC with VeriFire Tools installed. For details on using VeriFire
Tools refer to the VeriFire Tools online help.
Refer to Table 1.2 on page 9 for a list of supported panels and annunciators.
Step 3. After the IP Network connection is made; on the NTSRun Time window, click the Read
Status icon. The VeriFire Tools (Read Status Report Services) window displays.
Figure 3.8 IP Address Entries
Step 4. On the VeriFire Tools (Read Status Report Services) window, enter the following:
Step 4a.Type in the IP address into the IP address for connection to Notifier field.
A Web Server user will type this IP address into their browser to connect to the
Web Server. The Web Server requires the use of TCP/IP port 8888; for example,
if the Web Server is located at 10.4.2.1, a Web Server user will type into the
browse address field: http://10.4.2.1:8888/
If the Web Server is to be used on the internet, you may need to independently set
up a router and/or fire-wall so the internet-based applications can locate and
access the Web Server. Contact your appropriate MIS personnel for details.
PNET-1 surge suppressor
Web Server to PNET-1
To Internet or Intranet or
PC Board
PC with VeriFire Tools Installed
Step 4b.Type in the values into the Subnet Mask field.
The IP subnet mask the NWS should use will determine whether a connection
came from a local network or should be routed on to another network.
All of the IP settings for the NWS must be on the same subnet for
communications to be established between the NWS and a browser.
Step 4c.Type in the values into the IP address for routing back to Internet field.
This sets the IP of a router that the NWS can use to locate the browser with which
it is communicating.
This sets a path for the NWS to use to communicate back to the connecting
browser.
Step 4d.If applicable to your application, select a NCM Threshold and Network Styles.
The NCM threshold can be set to high or low.
The network style can be set to style 4 or style 7.
Refer to the NCM documentation for more details on these fields.
Step 5. Initial configuration is complete close VeriFire Tools.
Step 6. Disconnect the DB-9 to DB-9 cable and then perform NFN Network Connections on
page 25.
3.1.5 NFN Network Connections
Power Supply Connection
When using an NCM-W/F, it can be powered by a NOTIFIER panel/annunciators power source
or the P/N 46175 power supply (Figure 3.9). If using an customer supplied external power supply,
it should be UL listed for fire protective signaling systems, power limited and regulated.
Refer to Table 3.1 on page 20 for power supply specifications.
Figure 3.9 NCM-W/F Power Connection
+5VDC Output
Earth
+24VDC Input
24VDC REF Input
To NCM NUP Port
5V REF Output
Red wire
Black wire
P/N 75583*
*The NCM-W/F cable (P/N 75583) is not required when directly connecting to a supported
NOTIFIER panel or annunciator when they act as a standalone panel or annunciator.
DB-9 to NUP Cable Connection
Connecting the Web Server to an NCM-W/F allows the web server to communicate with devices
on a NFN network.
Figure 3.10 DB-9 to NUP Connection
Step 1. A DB9 to NUP cable is used to connect a DB9 to NUP cable between the web server and
NFN network in one of these ways:
Connect the cable between to the Web Server PC boards DB9 connector and a NCM W/F PC
board NUP connector.xxx
Use a NCM-W for a twisted pair wire connection.
NCM-F for a fiber-optic cable connection.
Connect the cable between to the Web Server PC boards DB9 connector and a supported
NOTIFIER panels and annunciators CPU NUP connector.
Refer to Table 1.2 on page 9 for supported NOTIFIER panels and annunciators.
Step 2. The configuration of Web Server is complete and it should be operational. Refer to Web
Server Operation on page 31 for details.
Connect to an NCM-W/F or
NUP end - connect to outer NUP port J2
DB9 to NUP cable P/N 75554
DB-9 end - connect to EIA-232 port
a Supported NOTIFIER Panel or
on PC Board
Annunciator
PC Board
3.1.6 Change the Web Server Node Address Using an IP
Connection
This configuration can only be done after the Initial Web Server Configuration on page 22 has
been performed. Also a PC with VeriFires Tools installed on the same IP network as the Web
Server must be used to perform this procedure.
Step 1. Select Start >Programs >VeriFire Tools >VeriFire Tools. The Hardware Connection
window displays.
Figure 3.11 Hardware Connections
Step 2. In the Connection Type area of the window, select IP. A message prompt displays.
Step 3. Click on No as the answer to the prompt to connect by way of a Web Server. VeriFire
Tools will then prompt for a session name and password.
Figure 3.12 Selecting the Connection Type
Step 4. Click on New to set up a new session. The New Session window displays.
Step 5. Enter the IP address for the Web Server in the Primary Event Manager field, and click
Next>>.
Step 6. From the drop-down list, select the Site on which the Web Server will reside, and click
Next>>.
Step 7. If the system contains multiple Web Servers, select the Web Server node number from the
drop-down list, and click Next>>.
Step 8. Enter a unique description for the session you are establishing, and click Next>>. A
message prompt displays
Figure 3.13 Configuring the Web Server Connection Session
Step 9. Once the session has been created, enter the VeriFire Tools system password and click
OK.
Figure 3.14 VeriFire Tools System Password
NOTE: Refer to System Settings on page 39 for information on how to set up a Web Server for
accessing fire alarm network information over your IP.
Step 10. Once you are online, VeriFire Tools will prompt you to select the Hardware Connection,
double click on NFN WEB SERVER and the NTSRunTime-> VeriFire Tools window
displays.
Figure 3.15 Selecting the Connection Type
Step 11. Complete the IP by performing step 3 and step 4 in the "NFN Network Connections"
procedure.
Section 4 Web Server Operation
4.1 Browser Security Settings
These Microsoft Internet Explorer settings for trusted sites MUST be made before you use the
web server.
Enter your Web Servers IP address.
Un-check the Require server verification (https:) for all sites in this zone selection.
NOTE: If you started the Web Server before making the Trusted Sites settings shown above, please
shut down your browser and make the Internet Options settings from Control Panel.
Web Server Operation Web Server Security
4.2 Web Server Security
There are factory set User Name and Password entries. The system administrator should modify
these User Name and Password as soon as possible to provide the system with security. The
password must be 8 characters
When the Web Server is started, a log in must be performed. Functions assigned by the system
administrator determine what access the user will have.
Figure 4.1 Web Server Login Dialog
User Name Password
users 11111111
admin 00000000
NOTE: Passwords are case sensitive.
The Web Server Interface Web Server Operation
4.3 The Web Server Interface
The Web Server interface is an html page type format that displays information about all points
present and active on a NFN network. The only supported internet browser is Microsoft Internet
Explorer. For details on using Microsoft Internet Explorer, consult Microsofts documentation or
help file.
The home page layout consists of a:
Menu column which is an Windows Explorer-style collapsible/expandable navigation tree.
Property/Value column where data is displayed about the selection chosen in the Menu
column.
Figure 4.2 Web Server Home Page
4.4 System Administration
The System Administration setup selections will configure various Web Server settings. Changing
settings can only be done by users that have been profiled as having administration level access.
4.4.1 Auto Detect Points on All Panels
This option will auto detect AFP1010/AM2020 points on NFN network.
How Points Become Visible To The Web Server
These are the ways a point becomes visible to the Web Server:
With Onyx series panels, points are detected automatically when the Web Server is connected
to the network on which those panels reside. Therefore, point detection for ONYX series
panels requires no user action.
With AFP1010/AM2020 panels, points are only detected when a user clicks on the AutoDetect
menu item either under the individual AFP1010/AM2020 panel's menu, or under System
Administration. Although the feature is called Auto Detect, this requires the user action of
clicking on the Auto Detect command.
With AFP-300/400 panels, points are only detected when they generate an event, which can
then be seen by the Web Server; therefore, the only way to add points connected to an AFP-
300/400 panel is to manually generate an event for each point.
The Web Server
Home Page link
navigates to the main
screen (shown in this
example).
The link below the
Web Server Home
Page link navigates to
the custom defined
URL configured in
System Settings.
Web Server Operation System Administration
Events from points that have not been Auto Detected will be shown in the Multiple Events list. In
other words, events coming from a classic panel will be logged even if the points themselves did
not previously appear in the hierarchy list at the left of the Web Server screen.
Figure 4.3 Auto Detect Points
The Auto Point Detect feature does not function for the AFP-300/400 panel, as seen on the screen
message shown below.
Figure 4.4 Auto Point Detect AFP400 Message
NOTE: AFP-200 points do not get Auto Detected, and they will not be displayed in the hierarchy list on
the left. However, events from an AFP-200 panel and/or point will come into the Multiple Event List and
can generate an E-mail.
NOTE: Only administrators have security access to the auto detect feature.
Selecting this option will
navigate to the corresponding
screen at the right, the Auto
Point Detect Verification
screen. This screen requests
that the administrator verify
the auto discover command,
as the process can be time-
consuming, depending on the
size of the entire system.
System Administration Web Server Operation
Figure 4.5 Auto Point Detect Screen
Once the Auto Detect has been performed, go to the Node Mapping links and make sure that all
node numbers that read online are also mapped. See Node Mapping on page 42 for more
information.
This lets you know that the
Auto Detect task is currently
being performed.
This line denotes the current
progress of the Auto Detect
task.
This option allows you to
cancel out of Auto Detect if
necessary.
NOTE: Make sure the nodes are online BEFORE performing the auto-detect operation,
otherwise the auto detect cant find the nodes.
4.4.2 E-mail Notification
Summary
The e-mail notification feature enables the administrator to configure the Web Server to
automatically send event information via e-mail to a select group of users. E-mail recipients receive
events according to the profiles they have been assigned. The Web Server can support a maximum
of ten profiles, and an e-mail recipient can be assigned to all ten profiles. Each of the ten profiles
support a maximum of five e-mail addresses.
E-Mail Configuration
You will need the following information from your Internet Service Provider (ISP) or Local Area
Network (LAN) administrator. The Web Server does not provide authentication information.
Outgoing Mail IP Address (SMTP) This is the mail servers IP address. The Web Server does
not support DNS; therefore, you will need the address in dotted decimal form
(XXX.XXX.XXX.XXX).
From Address (optional) Enter an e-mail address if you want responses to be sent to if you set
up an E-Mail Profile and select Send Test Message. Also this is entry may not be optional for cell
phone service provider systems that support e-mail.
Mail User This is an SMTP server setting. Leave this field blank unless your network
administrator indicates otherwise.
Figure 4.6 E-mail Configuration
E-Mail Notification Features
The following lists some of the benefits that the e-mail notification feature provides:
Ten Profiles
Send up to 50 e-mails in response to any system event.
Quickly Enable and Disable E-mail feature.
Create your own custom messages that will be included with the e-mailed system event.
Configuring E-mail Profiles
Profiles define the e-mail addresses of the recipients assigned that profile, along with the nodes and
event types that will initiate an e-mail message. Profiles filter e-mail notification by event type. The
six event types are Fire Alarms, Pre-Alarms, Securities, Supervisors, Troubles, and Other.
To Setup E-mail Profiles
Step 1. Click on System Administration.
Step 2. Click on E-mail Profiles to expand the selection to display the ten profiles.
Step 3. Click on the Profile to define.
Step 4. Enter the e-mail addresses to be included in the profile for notification.
Step 5. Choose the node (panel type) to be included for E-mail notification.
Step 6. Choose the event types to be included for E-mail notification. Note that these are set on a
per-node basis.
Step 7. Configure custom messages (see Figure 4.8 on page 38).
Step 8. After making all settings for the profile, click on Save Profile to save the E-Mail Profile.
Step 9. To verify your E-mail Profile setup; click on Send Test Message to send the following
message to E-Mail Profile recipients (software embedded test message; content can not be
edited).
The Fire Alarm Web Server at site "NFN Web Server" generated this message in response
to an operator test of e-mail profile #1.
Your e-mail address has been listed in the web server to be notified in the case of an event
of the type listed above.
Please contact your system administrator if you have been inadvertently notified.
Disable Profile Checking the Disable Profile option will prevent e-mails from being sent for this
profile until the box is un-checked. Profiles are enabled by default.
Figure 4.7 E-mail Profile Configuration
Each profile can define up to ten nodes that will
be included in e-mail notification. This includes
an all nodes setting as well.
Each profile can define up to
five e-mail addresses to
which the profile will apply.
Check the Cell Phone Format
if you want an abbreviated
message that will be
accepted by a cell phone.
Custom Messages
The administrator can define a 50-character max. custom message corresponding to the event
types. These messages will be included in the body of any e-mails sent to specified recipients.
Figure 4.8 E-mail Configuration - Custom Messages
In the example illustrated in Figure 4.8, custom messages have been defined for various event
types. Above the Custom Messages area, network nodes can be configured for E-mail notification
according to various event types. The general appearance of the E-mail notification message will
vary depending on the E-mail application used, individual PC font settings, and other factors. A
sample message, however, can be seen in the following figure.
Figure 4.9 Sample E-mail Message
Custom
messages are
defined
according to
event type and
have a 50-
character
maximum.
Site Name denotes
where the Web Server
is located. The Site
Name is configured
under System
Administration,
System Settings.
Panel Label displays
name enter into
system for entered
panel
Event displays
detailed event
information in the
same format as that
of the panel or
annunciator.
Custom Message was
not defined for this
event type.
Notification message
(software embedded,
can not be edited).
4.4.3 System Settings
Selecting System Administration, System Settings allows you to make Web Server browser
configuration settings.
Figure 4.10 System Settings
Site Settings
Site Name This is a user defined field designed to facilitate a unique descriptive name for the
NFN Web Browser.
Site Link This is a user defined field that allows you to add a shortcut to the link list at the left of
the NFN Web Browser window. This link can be to a graphic image of the network site or a
company homepage.
Site Link Name This is the name that will be displayed in the browser header when the Site Link
address is accessed.
NOTE: Only alphanumeric characters are supported for the Site Settings fields, with the exception
of the colon, forward slash and period.
General Settings
Non-Admin User Access This setting defines whether or not operators will have access to the
Web Server.
Network Update Select Yes to have the Web Server auto detect points daily according to the
Network Update Time.
Network Update Time If the Web Server is configured to auto detect points daily, this field is
used to select the time you want the Web Server to perform this action.
Trouble Reminder If there is an active trouble on the network, every 24 hours at 11:00 AM, a
trouble reminder message will be generated across the network.
Event Refresh Time This field is used to specify a refresh rate (between 3 and 90 seconds) for
the Multiple Event List. The Web Server will automatically refresh itself at the specified interval.
Any new system event will be displayed in the Multiple Event List. To disable this feature, set the
time to 0.
Unacknowledged Beep Check this option to enable an audible reminder of unacknowledged
events. When this is checked, the Web Server will beep at 3-second intervals and will continue until
no unacknowledged events are shown in the Multiple Events List.
Display Labels Select Yes to show then panel node labels in the left-hand pane, instead of
showing the node numbers and panel types.
Verifire Access Select Yes to allow access to Web Server from VeriFire Tools through an IP
connection.
Verifire Password Enter the password that will be used in conjuncture with Verifire Access
Yes setting.
NCM Settings
Node Address The node where the NCM is located on the NFN network.
Channel A/B Threshold Threshold settings are used according to the amount of network noise
present; changing the threshold settings will initialize the NCM board.
Style 7 Select Yes if style 7 is being used.
NOTE: The displayed label will update only when Web Server is rebooted (commissioning purposes) or
when the Network Update field is set to Yes and the Network Update Time field time settings is reached.
4.4.4 Monitoring Profiles
Selecting System Administration, Monitoring Profiles allows you to select the event types to be
displayed in the NFN Web Browser. Select No to disable NFN Web Browser viewing of the
specified event type. The default value for all event types is Yes.
Figure 4.11 Monitoring Profiles
4.4.5 Node Mapping
Selecting System Administration, Node Mapping allows the user to map nodes that are active on
the NFN network.
Figure 4.12 Node Mapping
Auto Detect selection will list all online nodes on the network as Mapped and all offline nodes on
the network as Unmapped. When Auto Detect or Change Settings are clicked network data will
be accessed to populate a nodes field, therefore, the display will refresh collapsing the Menu
navigation tree.
Change Settings is used to make individual node changes. Do so by selecting the drop-down menu,
making a choice, and then clicking on Change Settings to save the modifications. Consider making
all the individual node mapping decisions on the page before selecting Change Settings because
each time you select Change Settings you will have to expand the Menu navigation tree to return to
a node page.
If a node is Unmapped, the Web Server will not display events from that node. If a new node is
installed; you must auto detect or individually map it before its properties or events will be
displayed.
Node Status Values:
Online - The node was auto detected by the NFN Web Browser, but it will not show up in the
Menu at the left, nor will events be displayed, until it is mapped.
Offline - There is no device detected at that node address. No events will be reported.
Mapped - If the node is online, it will show up in the Menu, and events will be displayed in the
browser.
Unmapped - The default value; the node is either online with no event reporting, or there is no
device detected at that node address. No events or properties will be displayed for unmapped
nodes.
NOTE: The default value for node status is Unmapped.
Node Mapping Links
4.4.6 Password Configuration
Selecting System Administration, Password Configuration allows you to create, modify, and delete
system users and their access profiles. The system will support up to 128 total IDs. The username
must be between 3 and 15 characters. The password must be 8 characters.
Figure 4.13 User Configuration
NOTE: Users cannot access the System Administration menu. Only administrators have access to this
configuration function.
NOTE: To ensure system security, when finished with the Web Server, exit completely out of your
internet browser.
This is where users and
their corresponding
passwords are created.
Once a user has been
created, his/her name is
added to the drop-down
selection box in the
Characteristics section.
This is where users are
assigned access levels.
Admin allows System
Administration access.
4.4.7 Authorization Log
The Authorization Log displays a history of the last 50 users to access the Web Server and includes
the date and time of access.
.
Figure 4.14 Authorization Log
NOTE: The history does not include failed or denied accesses. The Web Server does not keep a
record of any failed attempts to access the Web Server
Diagnostics Web Server Operation
4.5 Diagnostics
4.5.1 Version Information
This link navigates to a screen that contains a list of panels, annunciators and related monitoring
devices and the corresponding version information for them and their related network interfaces.
Figure 4.15 Version Information
NOTE: Only these NOTIFIER panels and annunciators will have version information displayed: NFS-
320, NFS-640, NFS2-640, NFS-3030, NFS2-3030, NCA, or NCA-2.
Web Server Operation Diagnostics
4.5.2 Network Statistics Summary
Figure 4.16 Network Statistics Summary
NOTE: Network statistics display for NOTIFIER panels and annunciators.
Diagnostics Web Server Operation
4.5.3 NUP Port Statistics Summary
These are the NUP Port Statistics pages:
From the link menu at the left, select NUP Port Statistics Summary, and the Web Server will
display a status overview of all nodes and NCMs on the NFN network (see Figure 4.17).
Individual node statistics can be displayed by clicking on a node in the link menu, then
selecting NUP Port Statistics from its menu (see Figure 4.18).
Figure 4.17 NUP Port Statistics Overview
Figure 4.18 Local Node NUP Port Statistics
NOTE: Only these NOTIFIER panels and annunciators will have NUP Port Statistics information
displayed: NFS-320, NFS-640, NFS2-640, NFS-3030, NFS2-3030, NCA, or NCA-2.
Web Server Operation Multiple Event List
4.6 Multiple Event List
The Multiple Event List screen displays an event count, sorted by event type. Below is an example
showing multiple Fire Alarms and Troubles. To view event details, click on a specific event type
from the menu list.
Figure 4.19 Event List Summary
Once an event type is selected, details are displayed on the resulting screen. If there are no events
for a chosen event type, the screen will display a message saying No events exist in this category.
NOTE: The Web Server automatically extracts custom labels from panels when displaying events on an
as-needed basis. When there are many classic panel events (i.e. AM2020/AFP1010), this process may
take 30-40 seconds per page. The Web Server will remember the extracted labels once it has detected
them.
Multiple Event List Web Server Operation
Figure 4.20 Multiple Event List Details
Figure 4.21 Multiple Event List Details Descriptions
The Previous hyperlink will display the previous
ten events in the list.
The Next hyperlink will display the next
ten events in the list.
Event Number
Event Name
Zone
Device Type, if applicable
Custom Label Extended Custom label
Event details, including the
date/time the event occurred
Address where the event occurred (In this
example, the Fire Alarm entry provides the
exact device address)
Web Server Operation Screen Details and Options for Specific Panels
4.7 Screen Details and Options for Specific Panels
For any panel or device that is on the network, there will be a corresponding hyperlink option in the
Web Server menu list. These screens are for viewing panel/network device status and property
settings. In addition to fire alarm control panels, the NFN Web Browser also allows you to view
network devices such as the Network Control Station (NCS), Network Control Annunciator
(NCA), and the UniNet Gateway.
Figure 4.22 Panel Properties Display Sample
NOTE: Reference the pertinent control panel user manual for property details.
Screen Details and Options for Specific Panels Web Server Operation
Figure 4.23 Loop Properties Sample Screen
Figure 4.24 Module Properties Sample Screen
Web Server Operation Screen Details and Options for Specific Panels
Figure 4.25 Detector Properties Sample Screen
Index
A
annunciator compatibility 9
Authorization Log 44
Auto Detect Points 33
Auto Discover Points on all Panels 34
C
cabinet installation 16
Configure
E-mail Profiles 37
Connection 20
D
DB9 to DB9 cable 22
DB9 to NUP Cable 13
device
property settings 50
status 50
Device Compatibility 8
Direct panel connection 11
Display Labels 40
E
E-mail
configuration 36
notification 36
profiles 37
E-mail Notification 36
Ethernet network cable 13
Event Refresh Time 40
G
General Settings 40
H
HDD Power connector 13
I
Internet Explorer version 7
IP Network Configuration 24
IP Network Connection 24
L
lithium battery 14
Login 32
M
Monitoring Profiles 41
Multiple Event List 48
N
NCM
Channel Threshold 40
node address 40
Style 7 40
NCM installation 18
NCM Settings 40
Network Interface Card 13
Network Statistics 46
Network Update 40
Network Update Time 40
NFN Network
architecture 11
NFN Network Configuration 23
NFN network connection 11
NFN Network Connections
cable 26
power 25
NFN Network version 7
NFPA 72 8
Node Address Change 23
Node Mapping 35, 42
Non-Admin User Access 40
NUP port connection
support products 9
NUP Port Statistics 47
NUP to +24VDC power cable 13
P
panel
version information 45
panel compatibility 9
Password Configuration 43
passwords 32
PC to NWS PC Board Connection 22
PNET-1 13
Power Connections 25
power supply
mounting plate 13
part number 13
Product Description 7
R
Regulatory Standards 8
Related Documentation 8
S
Security 32
Serial Port Configuration Utility 22
Index
Site Link 39
Site Link Name 39
Site Name 39
Site Settings 39
SMTP 36
Standalone Panel Architecture 12
System Administration
Monitoring Profiles 41
Node Mapping 42
System Architecture 11
System Settings 39
General Settings 40
NCM Settings 40
Site Settings 39
T
Trouble Reminder 40
trusted sites 31
U
UL 864 8
ULC 8
Unacknowledged Beep 40
User Name 32
V
Verifire Access 40
Verifire Password 40
VeriFire Tools
installation 21
version 13
W
web server
browser interface 33
configuration overview 19
diagnostics 45
example installation diagram 15
installation overview 14
installation procedure 17
node address change 27
password 32
password configuration 43
PC board layout 14
PC board part number 13
security 32
Wiring
Power 25
55 NOTIFIER Web Server - Installation and Operation Manual - P/N: 51990:Rev: A4 01/15/07
Limited Warranty
Honeywell International Inc. warrants products manufactured by
it to be free from defects in materials and workmanship for
eighteen (18) months from the date of manufacture, under normal
use and service. Products are date stamped at time of
manufacture. The sole and exclusive obligation of Honeywell
International Inc. is to repair or replace, at its option, free of charge
for parts and labor, any part that is defective in materials or
workmanship under normal use and service. All returns for credit
are subject to inspection and testing at the factory before actual
determination is made to allow credit. Honeywell International
Inc. does not warrant products not manufactured by it, but assigns
to the purchaser any warranty extended by the manufacturer of
such products. This warranty is void if the product is altered or
repaired by anyone other than Honeywell International Inc. or as
expressly authorized by Honeywell International Inc. in writing, or
is serviced by anyone other than Honeywell International Inc. or
its authorized distributors. This warranty is also void if there is a
failure to maintain the products and systems in which they operate
in a proper and workable manner. In case of defect, secure a
Return Material Authorization form from our Return Authorization
Department.
This writing constitutes the only warranty made by Honeywell
International Inc., with respect to its products. Honeywell
International Inc., does not represent that its products will prevent
any loss by fire or otherwise, or that its products will in all cases
provide the protection for which they are installed or intended.
Buyer acknowledges that Honeywell International Inc., is not an
insurer and assumes no risk for loss or damages or the cost of any
inconvenience, transportation damage, misuse, abuse, accident or
similar incident.
HONEYWELL INTERNATIONAL INC. GIVES NO WARRANTY,
EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR
ANY PARTICULAR PURPOSE, OR OTHERWISE WHICH
EXTENDS BEYOND THE DESCRIPTION ON THE FACE
HEREOF. UNDER NO CIRCUMSTANCES SHALL HONEYWELL
INTERNATIONAL INC. BE LIABLE FOR ANY LOSS OF OR
DAMAGE TO PROPERTY, DIRECT, INCIDENTAL OR
CONSEQUENTIAL, ARISING OUT OF THE USE OF, OR
INABILITY TO USE HONEYWELL INTERNATIONAL INC.S
PRODUCTS. FURTHERMORE, HONEYWELL INTERNATIONAL
INC. SHALL NOT BE LIABLE FOR ANY PERSONAL INJURY OR
DEATH WHICH MAY ARISE IN THE COURSE OF, OR AS A
RESULT OF, PERSONAL, COMMERCIAL OR INDUSTRIAL USE
OF ITS PRODUCTS.
World Headquarters
12 Clintonville Road
Northford, CT 06472-1610 USA
203-484-7161
fax 203-484-7118
www.notifier.com

Nws Manual

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Nws Manual

Enviado por

Direitos autorais:

Formatos disponíveis

Web Server

Installation and Operation Manual

Você também pode gostar