Académique Documents
Professionnel Documents
Culture Documents
A4
Document 51990
01/15/07 Rev:
P/N: 51990:A4 ECN: 06-868
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 system—typically made up of smoke detec- bedrooms), smoking in bed, and violent explosions (caused by escap-
tors, heat detectors, manual pull stations, audible warning devices, ing gas, improper storage of flammable materials, etc.).
and a fire alarm control panel with remote notification capability—can Heat detectors do not sense particles of combustion and alarm only
provide early warning of a developing fire. Such a system, however, when heat on their sensors increases at a predetermined rate or
does not assure protection against property damage or loss of life reaches a predetermined level. Rate-of-rise heat detectors may be
resulting from a fire. subject to reduced sensitivity over time. For this reason, the rate-of-
The Manufacturer recommends that smoke and/or heat detectors be rise feature of each detector should be tested at least once per year
located throughout a protected premise following the recommenda- by a qualified fire protection specialist. Heat detectors are designed
tions of the current edition of the National Fire Protection Association to protect property, not life.
Standard 72 (NFPA 72), manufacturer's recommendations, State and IMPORTANT! Smoke detectors must be installed in the same room
local codes, and the recommendations contained in the Guide for as the control panel and in rooms used by the system for the connec-
Proper Use of System Smoke Detectors, which is made available at tion of alarm transmission wiring, communications, signaling, and/or
no charge to all installing dealers. A study by the Federal Emergency power. If detectors are not so located, a developing fire may damage
Management Agency (an agency of the United States government) the alarm system, crippling its ability to report a fire.
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- Audible warning devices such as bells may not alert people if these
ing against fire, they do not guarantee warning or protection against devices are located on the other side of closed or partly open doors or
fire. A fire alarm system may not provide timely or adequate warning, are located on another floor of a building. Any warning device may
or simply may not function, for a variety of reasons: fail to alert people with a disability or those who have recently con-
sumed drugs, alcohol or medication. Please note that:
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 • Strobes can, under certain circumstances, cause seizures in people
other side of closed doors. Smoke detectors also may not sense a with conditions such as epilepsy.
fire on another level or floor of a building. A second-floor detector, for • Studies have shown that certain people, even when they hear a fire
example, may not sense a first-floor or basement 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
Particles of combustion or “smoke” from a developing fire may not training exercise to make people aware of fire alarm signals and
reach the sensing chambers of smoke detectors because: instruct them on the proper reaction to alarm signals.
• Barriers such as closed or partially closed doors, walls, or chimneys • In rare instances, the sounding of a warning device can cause tempo-
may inhibit particle or smoke flow. rary or permanent hearing loss.
• Smoke particles may become “cold,” stratify, and not reach the ceiling A fire alarm system will not operate without any electrical power. If
or upper walls where detectors are located.
AC power fails, the system will operate from standby batteries only for
• Smoke particles may be blown away from detectors by air outlets. a specified time and only if the batteries have been properly main-
• Smoke particles may be drawn into air returns before reaching the tained and replaced regularly.
detector. Equipment used in the system may not be technically compatible
The amount of “smoke” present may be insufficient to alarm smoke with the control panel. It is essential to use only equipment listed for
detectors. Smoke detectors are designed to alarm at various levels of service with your control panel.
smoke density. If such density levels are not created by a developing Telephone lines needed to transmit alarm signals from a premise to
fire at the location of detectors, the detectors will not go into alarm. a central monitoring station may be out of service or temporarily dis-
Smoke detectors, even when working properly, have sensing limita- abled. For added protection against telephone line failure, backup
tions. Detectors that have photoelectronic sensing chambers tend to radio transmission systems are recommended.
detect smoldering fires better than flaming fires, which have little visi- The most common cause of fire alarm malfunction is inadequate
ble smoke. Detectors that have ionizing-type sensing chambers tend maintenance. To keep the entire fire alarm system in excellent work-
to detect fast-flaming fires better than smoldering fires. Because fires ing order, ongoing maintenance is required per the manufacturer's
develop in different ways and are often unpredictable in their growth, recommendations, and UL and NFPA standards. At a minimum, the
neither type of detector is necessarily best and a given type of detec- requirements of NFPA 72 shall be followed. Environments with large
tor may not provide adequate warning of a fire. amounts of dust, dirt or high air velocity require more frequent mainte-
Smoke detectors cannot be expected to provide adequate warning of nance. A maintenance agreement should be arranged through the
fires caused by arson, children playing with matches (especially in local manufacturer's representative. Maintenance should be sched-
FCC Warning
WARNING: This equipment generates, uses, and can radi- Canadian Requirements: This digital apparatus does not
ate radio frequency energy and if not installed and used in exceed the Class A limits for radiation noise emissions from
accordance with the instruction manual, may cause interfer- digital apparatus set out in the Radio Interference Regula-
ence to radio communications. It has been tested and tions of the Canadian Department of Communications.
found to comply with the limits for class A computing device Le present appareil numerique n'emet pas de bruits radio-
pursuant to Subpart B of Part 15 of FCC Rules, which is electriques depassant les limites applicables aux appareils
designed to provide reasonable protection against such numeriques de la classe A prescrites dans le Reglement sur
interference when operated in a commercial environment. le brouillage radioelectrique edicte par le ministere des
Operation of this equipment in a residential area is likely to Communications du Canada.
cause interference, in which case the user will be required
to correct the interference at his own expense.
Acclimate Plus™, HARSH™, NOTI•FIRE•NET™, 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.
WARNING:
! Improper installation, maintenance, or lack of routine testing could result in system malfunction.
1.4 Compatibility
The Web Server behaves as any other node on NFN network and is compatible with the following
node types:
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
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.
NOTE: The Web Server is compatible with Veri•Fire Tools version 4.5 or later.
Internet
Intranet
FACP
FACP
NCS
NCS
UniNet®/NFN NION
UniNet®/NFN NION
BACnet Gateway
ONYXWorks
ONYXWorks
PC Browser Interface
Internet
Intranet Supported Notifier FACP with
Web Server Assembly
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.
DB9-NUP Connector -
used for operation as
the network connection
to NFN
HDD Power
Connector (P1)
RJ45 Ethernet
Connector (CN2)
NOTE: The replacement of the lithium battery on the PC board is to be performed by a trained
technician.
+24VDC power
connection from
power supply to
POWER FIRE
ALARM
PREALARM SECURITY SUPERVISORY SYSTEM
TROUBLE
DISABLED
POINTS
ALARM
SILENCED PC board power
supply connector
ACKNOWLEDGE SILENCE DRILL RESET LAMP
STEP DISPLAY HOLD 2 SECONDS TEST
1
!
2@ 3
=
4, 5
%
6
:
7
/
8
.
9 0? DISABLE
ENABLE
*
NEXT
SELECTION +
Q W E R T Y U I O P # PREVIOUS
SELECTION
–
A S D F G H J K L Esc
&
RECALL
LAST (
ENTRY
PC Board
PNET-1 connection
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.
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 panel’s or annunciator’s documentation.
Step 2. After the CAB3/CAB4 cabinet is prepared with the CHS-4L chassis installed, perform the
“Web Server Assembly Installation” on page 17.
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.
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.
2 1
3
4
6
NOTE: For installation details, refer to the NCM Installation Document (51533) or the supported
NOTIFIER® panel’s or annunciator’s documentation.
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.
y p y
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
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 NOTI•FIRE•NET™. 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 NOTI•FIRE•NET™ node (including fire alarm control panels and
network annunciators) . Even though the NCM has two NUP ports, only one may be connected to a NOTI•FIRE•NET™.
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 NOTI•FIRE•NET™ Manual (Network Version 4.0 and Higher)
for wiring length and threshold information.
Step 2. After the installation perform “Web Server Configuration” on page 19.
Earth
+5VDC Output
5V REF Output
Red wire
The Veri•Fire 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 Veri•Fire 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.
PC Board
To EIA-232 port on PC with Veri•Fire Tools Installed
NOTE: The DB9 to DB9 cable must be supplied by customer and it must be a null-modem cable.
Step 2. Start Veri•Fire 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 Veri•Fire’s
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).
Step 2. Select Local as the New Session. The Nodes window displays.
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.
Step 6. After "PC to Web Server PC Board Connection and Configuration" is complete, perform
"IP Network Connection and Configuration".
To Internet or Intranet or
PC with VeriFire Tools Installed PNET-1 surge suppressor
PC Board
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.
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.
Earth
+5VDC Output
5V REF Output Black wire
*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.
Connect to an NCM-W/F or
a Supported NOTIFIER Panel or
Annunciator DB9 to NUP cable P/N 75554
PC Board
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 board’s 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 board’s DB9 connector and a supported
NOTIFIER® panel’s and annunciator’s 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.
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. Veri•Fire
Tools will then prompt for a session name and password.
Step 4. Click on New to set up a new session. The New Session window displays.
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 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
Step 9. Once the session has been created, enter the Veri•Fire Tools system password and click
OK.
Step 10. Once you are online, Veri•Fire Tools will prompt you to select the Hardware Connection,
double click on NFN WEB SERVER and the NTSRunTime-> VeriFire Tools window
displays.
Step 11. Complete the IP by performing step 3 and step 4 in the "NFN Network Connections"
procedure.
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.
users 11111111
admin 00000000
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.
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.
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.
The Auto Point Detect feature does not function for the AFP-300/400 panel, as seen on the screen
message shown below.
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.
NOTE: Make sure the nodes are online BEFORE performing the auto-detect operation,
otherwise the auto detect can’t find the nodes.
Each profile can define up to ten nodes that will Check the Cell Phone Format Each profile can define up to
be included in e-mail notification. This includes if you want an abbreviated five e-mail addresses to
an “all nodes” setting as well. message that will be which the profile will apply.
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.
Custom
messages are
defined
according to
event type and
have a 50-
character
maximum.
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.
Event displays
detailed event
information in the
same format as that
of the panel or
annunciator.
Notification message
(software embedded,
can not be edited).
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.
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.
Verifire Access Select Yes to allow access to Web Server from Veri•Fire 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.
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 node’s 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 it’s 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: 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.
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
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.
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.
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.
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.
The Previous hyperlink will display the previous The Next hyperlink will display the next
ten events in the list. ten events in the list.
Event details, including the Address where the event occurred (In this
date/time the event occurred example, the Fire Alarm entry provides the
exact device address)
NOTE: Reference the pertinent control panel user manual for property details.
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
NOTIFIER® Web Server - Installation and Operation Manual - P/N: 51990:Rev: A4 01/15/07 55
World Headquarters
12 Clintonville Road
Northford, CT 06472-1610 USA
203-484-7161
fax 203-484-7118
www.notifier.com