BACnet Gateway

Installation and Operation Manual

A7
Document 51659
2/10/09 Rev:
P/N: 51659:A7 ECN: 08-717
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. These documents can be found at power. If detectors are not so located, a developing fire may damage
http://www.systemsensor.com/html/applicat.html. the alarm system, crippling its ability to report a fire.
A study by the Federal Emergency Management Agency (an agency Audible warning devices such as bells may not alert people if these
of the United States government) indicated that smoke detectors may devices are located on the other side of closed or partly open doors or
not go off in as many as 35% of all fires. While fire alarm systems are are located on another floor of a building. Any warning device may
designed to provide early warning against fire, they do not guarantee fail to alert people with a disability or those who have recently con-
warning or protection against fire. A fire alarm system may not pro- sumed drugs, alcohol or medication. Please note that:
vide timely or adequate warning, or simply may not function, for a
variety of reasons: • Strobes can, under certain circumstances, cause seizures in people
with conditions such as epilepsy.
Smoke detectors may not sense fire where smoke cannot reach the
• Studies have shown that certain people, even when they hear a fire
detectors such as in chimneys, in or behind walls, on roofs, or on the
alarm signal, do not respond or comprehend the meaning of the signal.
other side of closed doors. Smoke detectors also may not sense a
It is the property owner's responsibility to conduct fire drills and other
fire on another level or floor of a building. A second-floor detector, for training exercise to make people aware of fire alarm signals and
example, may not sense a first-floor or basement fire. instruct them on the proper reaction to alarm signals.
Particles of combustion or “smoke” from a developing fire may not • In rare instances, the sounding of a warning device can cause tempo-
reach the sensing chambers of smoke detectors because: rary or permanent hearing loss.
• Barriers such as closed or partially closed doors, walls, or chimneys A fire alarm system will not operate without any electrical power. If
may inhibit particle or smoke flow. AC power fails, the system will operate from standby batteries only for
• Smoke particles may become “cold,” stratify, and not reach the ceiling a specified time and only if the batteries have been properly main-
or upper walls where detectors are located. tained and replaced regularly.
• Smoke particles may be blown away from detectors by air outlets. Equipment used in the system may not be technically compatible
• Smoke particles may be drawn into air returns before reaching the with the control panel. It is essential to use only equipment listed for
detector. service with your control panel.
The amount of “smoke” present may be insufficient to alarm smoke Telephone lines needed to transmit alarm signals from a premise to a
detectors. Smoke detectors are designed to alarm at various levels of central monitoring station may be out of service or temporarily dis-
smoke density. If such density levels are not created by a developing abled. For added protection against telephone line failure, backup
fire at the location of detectors, the detectors will not go into alarm. radio transmission systems are recommended.
Smoke detectors, even when working properly, have sensing limita- The most common cause of fire alarm malfunction is inadequate
tions. Detectors that have photo-electronic sensing chambers tend to maintenance. To keep the entire fire alarm system in excellent work-
detect smoldering fires better than flaming fires, which have little visi- ing order, ongoing maintenance is required per the manufacturer's
ble smoke. Detectors that have ionizing-type sensing chambers tend recommendations, and UL and NFPA standards. At a minimum, the
to detect fast-flaming fires better than smoldering fires. Because fires requirements of NFPA 72 shall be followed. Environments with large
develop in different ways and are often unpredictable in their growth, amounts of dust, dirt or high air velocity require more frequent mainte-
neither type of detector is necessarily best and a given type of detec- nance. A maintenance agreement should be arranged through the
tor may not provide adequate warning of a fire. local manufacturer's representative. Maintenance should be sched-
uled monthly or as required by National and/or local fire codes and
Smoke detectors cannot be expected to provide adequate warning of should be performed by authorized professional fire alarm installers
fires caused by arson, children playing with matches (especially in

2 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

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 Like all solid state electronic devices this system may operate errati-
the fire alarm control panel. Disconnect all sources of power before cally or can be damaged when subjected to lightning-induced tran-
servicing. The control unit and associated equipment may be dam- sients. Although no system is completely immune from lightning
aged by removing and/or inserting cards, modules, or interconnecting transients and interferences, proper grounding will reduce susceptibil-
cables while the unit is energized. Do not attempt to install, service, ity. Overhead or outside aerial wiring is not recommended, due to an
or operate this unit until this manual is read and understood. increased susceptibility to nearby lightning strikes. Consult with the
CAUTION - System Reacceptance Test after Software Changes. To Technical Services if any problems are anticipated or encountered.
ensure proper system operation, this product must be tested in accor- Disconnect AC power and batteries prior to removing or inserting cir-
dance with NFPA 72 after any programming operation or change in cuit boards. Failure to do so can damage circuits.
site-specific software. Reacceptance testing is required after any Remove all electronic assemblies prior to any drilling, filing, reaming,
change, addition or deletion of system components, or after any mod- or punching of the enclosure. When possible, make all cable entries
ification, repair or adjustment to system hardware or wiring. from the sides or rear. Before making modifications, verify that they
All components, circuits, system operations, or software functions will not interfere with battery, transformer, and printed circuit board
known to be affected by a change must be 100% tested. In addition, location.
to ensure that other operations are not inadvertently affected, at least Do not tighten screw terminals more than 9 in-lbs. Over-tightening
10% of initiating devices that are not directly affected by the change, may damage threads, resulting in reduced terminal contact pressure
up to a maximum of 50 devices, must also be tested and proper sys- and difficulty with screw terminal removal.
tem operation verified.
Though designed to last many years, system components can fail at
This system meets NFPA requirements for operation at 0°C to 49°C any time. This system contains static-sensitive components. Always
(32°F to 120°F) and at a relative humidity 93% ± 2% RH (non-con- ground yourself with a proper wrist strap before handling any circuits
densing) at 32°C ± 2°C (90°F ± 3°F). However, the useful life of the so that static charges are removed from the body. Use static-sup-
system's standby batteries and the electronic components may be pressive packaging to protect electronic assemblies removed from
adversely affected by extreme temperature ranges and humidity. the unit.
Therefore, it is recommended that this system and all peripherals be
installed in an environment with a nominal room temperature of 15- Follow the instructions in the installation, operating, and program-
27° C/60-80° F. ming manuals. These instructions must be followed to avoid damage
to the control panel and associated equipment. FACP operation and
Verify that wire sizes are adequate for all initiating and indicating reliability depend upon proper installation by authorized personnel.
device loops. Most devices cannot tolerate more than a 10% I.R.
drop from the specified device voltage.

FCC Warning
WARNING: This equipment generates, uses, and can radi- likely to cause interference, in which case the user will be
ate radio frequency energy and if not installed and used in required to correct the interference at his own expense.
accordance with the instruction manual, may cause inter- Canadian Requirements: This digital apparatus does not
ference to radio communications. It has been tested and exceed the Class A limits for radiation noise emissions
found to comply with the limits for class A computing from digital apparatus set out in the Radio Interference
device pursuant to Subpart B of Part 15 of FCC Rules, Regulations of the Canadian Department of Communica-
which is designed to provide reasonable protection against tions.
such interference when operated in a commercial environ-
ment. Operation of this equipment in a residential area is 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
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.
©2006 by Honeywell International Inc. All rights reserved. Unauthorized use of this document is strictly prohibited.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 3

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:
[email protected]
Please note this email address is for documentation feedback only. If you have any technical issues, please contact
Technical Services.

4 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Table of Contents
Section 1 NOTIFIER® BACnet Gateway Features.................................................................. 7
1.1: Product Description .......................................................................................................................................7
1.1.1: BACnet Gateway Features ..................................................................................................................7
1.2: Related Documentation .................................................................................................................................8
Table 1.1 Related Documentation ..........................................................................................................8
1.3: Agency Listings .............................................................................................................................................8
1.3.1: Compliance..........................................................................................................................................8
1.3.2: Installation ...........................................................................................................................................9
1.4: Environmental Requirements ........................................................................................................................9
1.5: Compatibility ...............................................................................................................................................10
Table 1.2 NFN Network and NOTIFIER® Panel Compatibility ........................................................10
1.6: Upgrade Information ...................................................................................................................................10
1.7: Troubleshooting ...........................................................................................................................................11
1.8: System Requirements ..................................................................................................................................11
1.9: System Architecture.....................................................................................................................................12
1.9.1: Single Panel Architecture ..................................................................................................................12
Figure 1.1 BACnet Gateway Single Panel Diagram ............................................................................12
1.9.2: NFN Network Architecture ...............................................................................................................13
Figure 1.2 BACnet Gateway Network Diagram ..................................................................................13
Section 2 BACnet Gateway Embedded Installation............................................................. 15
2.1: Required Equipment ....................................................................................................................................15
2.2: BACnet Gateway Installation Overview .....................................................................................................15
2.2.1: BACnet Gateway Board Layout........................................................................................................16
Figure 2.1 BACnet Gateway Board......................................................................................................16
2.2.2: BACnet Gateway Example Installation Diagram..............................................................................17
Figure 2.2 Example Installation Diagram ............................................................................................17
2.3: CAB3/CAB4 Cabinet Installation ...............................................................................................................18
Figure 2.3 CAB-3/CAB-4 Series Installation Document, 15330 .........................................................18
2.4: BACnet Gateway Assembly Installation .....................................................................................................18
Figure 2.4 BACnet Gateway Assembly Installation Diagram .............................................................19
2.5: BACnet Gateway Power Supply Connection ..............................................................................................19
Table 2.1 46175 Power Supply Specifications.....................................................................................19
Figure 2.5 BACnet Gateway Power Connection..................................................................................20
2.5.1: Network Communication Module Installation ..................................................................................20
Figure 2.6 NCM W/F Board Installation Document, 51533 ................................................................20
2.5.2: IP and NFN Network Connections....................................................................................................21
Figure 2.7 Ethernet Connection............................................................................................................21
Figure 2.8 NCM-W/F Power Connection ............................................................................................22
Section 3 BACnet Gateway Configuration and Operation .................................................. 23
3.1: BACnet Gateway Configuration..................................................................................................................23
3.1.1: BACnet Gateway Configuration Overview.......................................................................................23
3.1.2: BACnet Gateway Configuration Tool Installation............................................................................23
3.1.3: Connect the Configuration Computer to the BACnet Gateway ........................................................24
3.1.4: Prepare the Configuration Computer to Communicate with BACnet Gateway................................24
3.1.5: Log into the BACnet Gateway for Configuration .............................................................................25
3.1.6: Configure the BACnet Gateway........................................................................................................26
3.1.7: Viewing BACnet Gateway Activity with the BACnet Gateway Configuration Tool.......................31
3.1.8: Connect the BACnet Gateway to the NFN Network or FACP .........................................................32
Figure 3.1 DB-9 to NUP Connection ...................................................................................................32
3.1.9: Back Up BACnet Gateway................................................................................................................33
3.1.10: Restore BACnet Gateway................................................................................................................33
3.2: BACnet Gateway Operation ........................................................................................................................34
3.2.1: About BACnet Gateway Start Up .....................................................................................................34
BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 5
Table of Contents

Appendix A: Glossary ............................................................................................................ 37

Appendix B: PIC Statement ................................................................................................... 39
B.1: BACnet Protocol Implementation Conformance Statement (Normative) ..................................................39
Appendix C: BACnet Gateway Local Configuration............................................................ 45
C.1: Direct Connection to the Gateway Board ...................................................................................................45
Figure C.1 Configuration Computer Direct Connection ......................................................................45
Table C.1 Cross Over Cable (568B).....................................................................................................45
Appendix D: Equations for Object IDs (Instance Numbers) ............................................... 47
Index ........................................................................................................................................ 49

6 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Section 1 NOTIFIER® BACnet Gateway Features

1.1 Product Description

The NOTIFIER® BACnet Gateway (BACnet Gateway) provides a communication link between
networks that use the BACnet communication protocol and NFN network (NFN) resident Fire
Alarm Control Panels (FACP). The NFN network communicates with the gateway through an
NCM-W/F network control module that is on that NFN network or through a direct connection to a
single NOTIFIER® panel. The BACnet communication protocol is an American National
Standard (ANSI/ASHRAE 135-1995).
The BACnet Gateway application represents physical fire devices as BACnet objects and manages
the object database. As events occur, the object properties are updated in real-time, and messages
are sent to the appropriate BACnet report destination (BACnet computer clients are computers with
graphical user interface workstation front end). BACnet clients may make requests to read
properties of the BACnet objects. Those properties are the values of the device status and
programming. The user subscribes to Event Notification objects per FACP, and the BACnet device
receives events from objects on the FACP as a result of this subscription.
The BACnet client workstation front end must conform to BACnet Standard Annex J for IP and
support Device Objects, Binary Output Objects, and Multi-state Input or Life Safety Points/Zones.
It is also required to write to Notification Objects and receive confirmed/unconfirmed event
notification messages. For details, refer to Appendix B, “PIC Statement”, on page 39.
The BACnet Gateway Configuration Tool, an offline programming utility that is included with the
BACnet Gateway assembly when ordered, is used to configure the BACnet Gateway. It is installed
onto a computer that is will be used to configure the gateway. Refer to “BACnet Gateway
Configuration and Operation” on page 23.

1.1.1 BACnet Gateway Features

Below are some of the features of the BACnet Gateway and BACnet Gateway Configuration Tool.
• Multiple Gateways can be used for networks greater than 14 panels/15,000 objects.
• Use of IP or crossover Ethernet cable for BACnet Gateway configuration.

NOTE: This manual is written with the understanding that its user is trained in BACnet operations
and services. The information provided here is solely for the configuration of the Gateway to
communicate event information to an existing BACnet network.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 7

NOTIFIER® BACnet Gateway Features Related Documentation

1.2 Related Documentation

Below is a list of documentation that relates to the use of the BACnet Gateway.

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 Veri•Fire™ Tools on-line help file VeriFire-TCD

Veri•Fire™ Medium Systems on-line help file VeriFire-CD

VeriFire-TCDNetworking NFN Manual 51584

NCM-W/F Installation Document 51533
MIB Media Interface Board Manual 50255

Panels and Annunciators NFS-320 Installation/Operation/Programming Manual 52745/52746/52747

NFS-640 Installation/Operation/Programming Manual 52544/52545/52546
NFS2-640 Installation/Operation/Programming Manual 52741/52742/52743
NFS-3030 Installation/Operation/Programming Manual 51330/51344/51345
NFS2-3030 Installation/Operation/Programming Manual 52544/52546/52545
Network Control Annunciator (NCA) Manual 51482
Network Control Annunciator-2 (NCA-2) Manual 52482
Network Control Station (NCS) Manual 51095
AFP-200 Operating Instruction Manual 15620
AFP-300/400 Installation/Operation/Programming Manual 50253/50260/50259
AM2020/AFP1010 Installation, Operation, and Programming Manual 15088
DVC Series Digital Voice Command Manual 52411
Uninet® 2000 Online Installation and Operation Manual 51994

1.3 Agency Listings

NOTE:
UL 864, 9th Edition—Notifier systems work with products that have been UL 864, 9th Edition
listed as well as products that have not received UL 864, 9th Edition certification. Operation of
systems that are comprised of equipment that is UL 864, 9th Edition listed together with products
that are not UL 864, 9th Edition listed requires the approval of the local Authority Having
Jurisdiction (AHJ).
CAN/ULC-S559-04, 1st Edition—Notifier systems work with products that have been CAN/ULC-
S559-04, 1st Edition listed as well as products that have not received CAN/ULC-S559-04, 1st
Edition certification. Operation of systems that are comprised of equipment that is CAN/ULC-
S559-04, 1st Edition listed together with products that are not CAN/ULC-S559-04, 1st Edition
listed requires the approval of the local Authority Having Jurisdiction (AHJ).

1.3.1 Compliance
This product has been investigated to, and found to be in compliance with the following standards.
National Fire Protection Association
• NFPA 72—National Fire Alarm Code
Underwriters Laboratories
• UL-864—Control Units for Fire Alarm Systems, Ninth Edition
• UL-2017—General-Purpose Signaling Devices and Systems, First Edition

8 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

Environmental Requirements NOTIFIER® BACnet Gateway Features

Underwriters Laboratories Canada

• CAN/ULC-S527-99—Standard for Control Units for Fire Alarm Systems, Second Edition
• CAN/ULC-S559-04—Equipment for Fire Signal Receiving Centres and Systems, First
Edition
ANSI/ASHRAE
• ANSI/AHSRAE Standard 135-1995, BACnet

1.3.2 Installation
This product is intended to be installed in accordance with the following regulatory agencies.
Local
• AHJ—Authority Having Jurisdiction
National Fire Protection Association
• NFPA 70—National Electrical Code
• NFPA 72—National Fire Alarm Code
• NFPA 101—Life Safety Code
Underwriters Laboratories
• UL-1076—In certified applications, the unit shall be installed in accordance with Proprietary
Burglar Alarm Units and Systems, Fifth Edition
Underwriters Laboratories Canada
• CAN/ULC-S524-06—Standard for the Installation of Fire Alarm Systems, Fifth Edition
• CAN/ULC-S561-03—Installation and Services for Fire Signal Receiving Centres and
Systems, First Edition
Canada
• CSA C22.1—Canadian Electrical Code, Part I, Safety Standard for Electrical Installations

WARNING: Installation
! Improper installation, maintenance, and lack of routine testing could result in system malfunction.

1.4 Environmental Requirements

This product must be installed in the following environmental conditions:
• Temperature range of 0°C to 49°C (32°F - 120°F).
• 93% humidity non-condensing at 30°C (86°F).

NOTE: Refer to Appendix B, “PIC Statement”, on page 39 for the BACnet PIC statement.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 9

NOTIFIER® BACnet Gateway Features Compatibility

1.5 Compatibility
NOTE: The BACnet Gateway requires that at least one node on the NFN network be an ONYX
series panel. Running a BACnet Gateway on an NFN network with only classic panels will cause
events to be labeled with incorrect times and dates, and may cause other problems.

The BACnet Gateway behaves as any other node on a NFN network and is compatible with the
following.

Table 1.2 NFN Network and NOTIFIER® Panel Compatibility

NFN Node Type Network Interface Board

AFP-1010 MIB-WPCC

†
AFP-2800 NCM-W/F

AM2020 SIB-NET

DVC NCM-W/F

NCS NCM-W/F

NCA NCM-W/F

NCA-2 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

NFS2-3030* NCM-W/F

*Supported NOTIFIER® panel or annunciator that allow direct connection from

BACnet Gateway’s DB-9 connector to its CPU motherboard’s NUP port.
†Only available in Australia.

1.6 Upgrade Information

Upgrading Firmware
Firmware for systems running BACnet Gateway versions prior to 3.11 should not be upgraded
unless there is an ONYX series panel on the system. Running an updated BACnet Gateway on an
NFN network with only classic panels will cause events to be labeled with incorrect times and
dates, and may cause other problems. Use the ONYXWorks Download Utility to upgrade the
gateway firmware. For more information, refer to ONYXWorks Download Utility Installation &
Operation Manual, PN 53509.
Flash Memory Upgrade
The BACnet Gateway may be upgraded with a flash memory kit. For more information, refer to
Embedded Gateway (NFN, NWS and BACnet) Upgrade Kit, PN 53511.

10 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

Troubleshooting NOTIFIER® BACnet Gateway Features

When Upgrading Network Communication Modules (NCMs)

Use the following procedure when upgrading NCMs on a network with a BACnet Gateway:
Step 1. Upgrade the NFN network and verify all NCMs except the NCM supporting the BACnet
Gateway have been upgraded.
Step 2. Switch the NCM supporting the BACnet Gateway with an upgraded NCM.
Step 3. Upgrade the NCM that had been supporting the BACnet Gateway.

1.7 Troubleshooting
Before calling technical support, please do the following:
Step 1. Log the entire discovery process from start to finish including the panel online message
from the Gateway Activity window and save the file. Please refer to, “Viewing BACnet
Gateway Activity with the BACnet Gateway Configuration Tool” on page 31.
Step 2. Make a backup file of your BACnet Gateway. Please refer to, “Back Up BACnet
Gateway” on page 33.

1.8 System Requirements

The BACnet Gateway can monitor up to fourteen panels, but the combined object count across the
monitored panels cannot exceed 15,000 objects. This includes all detectors, monitor modules,
control modules, bell circuits, etc. Refer to the NFN network manual for details about wiring
limitations.
The computer on which the BACnet Gateway Configuration Toolis installed should be
Windows 2000 or Windows XP.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 11

NOTIFIER® BACnet Gateway Features System Architecture

1.9 System Architecture

NOTE: The BACnet Gateway client workstation is not intended as a primary annunciator and is
ancillary in nature.

These are connections options for the BACnet Gateway architecture:

• NFN network connection; a connection is made to a NCM that is on the same NFN network as
the BACnet Gateway (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 10 for a list of supported panels and
annunciators.
An Internet or Intranet IP network connection is used with both architectures.

1.9.1 Single Panel Architecture

BACnet/IP Client with Workstation Front End

Ethernet

From PNET-1

EIA-232 Gateway

Computer with BACnet Configuration Tool FACP

(only for configuration and activity viewing)

Figure 1.1 BACnet Gateway Single Panel Diagram

12 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

System Architecture NOTIFIER® BACnet Gateway Features

1.9.2 NFN Network Architecture

BACnet/IP Client with Workstation Front End

Ethernet

From PNET-1

EIA-232 Gateway
and NCM-W/F

OR

Computer with BACnet Configuration Tool

(only for configuration and activity viewing)
EIA-232

NOTI•FIRE•NET™

Annunciator FACP FACP FACP

BACnet Client Workstation or

Network Control Status

Figure 1.2 BACnet Gateway Network Diagram

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 13

NOTIFIER® BACnet Gateway Features System Architecture

14 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Section 2 BACnet Gateway Embedded Installation

2.1 Required Equipment

NOTE: The BACnet Gateway is for ancillary use only and does not increase the burglary grade of
service for the system.

The BACnet Gateway requires the following:

BACnet Gateway Assembly
The following are shipped with the BACnet Gateway:
• BACnet Gateway (P/N 46173).
• Power supply (P/N 46175) - used for supplying +24VDC to +5VDC to the BACnet Gateway.
• BACnet Gateway/Power Supply Mounting Plate (P/N 18541).
• HDD Power connector (P/N 75581) - used for supplying +24VDC to +5VDC to the BACnet
Gateway.
• PNET-1 surge suppressor (P/N PNET-1).
• RJ45 to RJ45 standard Ethernet network cable (P/N 75585) - used to connect the BACnet
Gateway to PNET-1 surge suppressor.
• DB9 to NUP Cable (P/N 75554) - used to connect the BACnet Gateway to an NCM-W/F
board.
• NUP to +24VDC power cable (P/N 75583) - used for supply power to the NCM-W/F board.
• BACnet Gateway Configuration Tool version 3.11.112 (supplied on CD-ROM, P/N BACNET-
SW).
Network Components
• RJ45 to RJ45 standard Ethernet network cable - customer’s internet or intranet connection to
PNET-1 surge suppressor (supplied by customer).
• NFN network - version 5.0 or above (sold separately).
• Network Communication Module: NCM-W/F board - used to facilitate network
communication between the BACnet Gateway and NFN network (sold separately).

NOTE: No NCM W/F is required when the BACnet Gateway connects directly to a supported
NOTIFIER® panel or annunciator when it is a standalone panel or annunciator. Refer to Table 1.2
on page 10 for a list of supported panels and annunciators.

Cabinet and Hardware (sold separately)

• CAB-3/CAB-4 series cabinet.
• CHS-4L chassis.
Customer Supplied Equipment
• Computer to run BACnet Gateway Configuration Tool.
• Option Ethernet crossover cable (only needed when configuration computer cannot be
connected to the same IP network as the BACnet Gateway. For more information, please refer
to Appendix C, “BACnet Gateway Local Configuration”, on page 45).

2.2 BACnet Gateway Installation Overview

This is the recommended installation order:

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 15

BACnet Gateway Embedded Installation BACnet Gateway Installation Overview

• “CAB3/CAB4 Cabinet Installation” on page 18

• “BACnet Gateway Assembly Installation” on page 18.
• “Network Communication Module Installation” on page 20 (if applicable).

2.2.1 BACnet Gateway Board Layout

DB9-NUP Connector -
used for operation as
the network connection
to NFN
HDD Power
Connector (P1)

RJ45 Ethernet
Connector (CN2)

Figure 2.1 BACnet Gateway Board

NOTE: The replacement of the lithium battery on the board is to be performed by a trained
technician.

16 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Installation Overview BACnet Gateway Embedded Installation

2.2.2 BACnet Gateway Example Installation Diagram

Figure 2.2 shows the components and connections of a BACnet Gateway 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.

Fire Alarm Control Panel (FACP)

+24VDC power
connection from
power supply to
POWER FIRE
ALARM
PREALARM SECURITY SUPERVISORY SYSTEM
TROUBLE
DISABLED
POINTS
ALARM
SILENCED Gateway 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

Z X C V B N M SPACE Enter / INCREMENT )

NUMBER

To Customers FACP Chassis

Internet or Intranet
Mounting Plate

Gateway
Board

Direct data connection

between FACP NUP Port
and DB-9 Connector

PNET-1 connection

Figure 2.2 Example Installation Diagram

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 BACnet Gateway circuits are power limited. Route wiring per the power limited and
non-power limited constraints defined in the pertinent Fire Alarm Control Panel manual.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 17

BACnet Gateway Embedded Installation CAB3/CAB4 Cabinet Installation

2.3 CAB3/CAB4 Cabinet Installation

NOTE: In Canada, if the BACnet Gateway is installed in a separate cabinet, the cabinet must be
connected to the Fire Alarm Control Panel (FACP) with a close nipple fitting.

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 10 for
list of supported panels and annunciators.

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
“BACnet Gateway Assembly Installation” on page 18.

CAB-3/CAB-4 Series Cabinets

Product Installation Document

PN 15330:I 10/23/07 07-695

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 five sizes: A through D, and AA. 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; “AA” size holds one chassis with no compartment for 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, CHS2-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
CAB door RH.wmf

mounted in a confined area or side by side (as shown). In this manner

CAB door LH.wmf

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

Figure 2.3 CAB-3/CAB-4 Series Installation Document, 15330

2.4 BACnet Gateway Assembly Installation

Step 1. Install BACnet Gateway 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.

18 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Power Supply Connection BACnet Gateway Embedded Installation

Step 6. You are now ready to perform the “Network Communication Module Installation” on
page 20 if its use is applicable to your installation, if not perform the “BACnet Gateway
Configuration” on page 23.

2 1

3
4
6

Figure 2.4 BACnet Gateway Assembly Installation Diagram

2.5 BACnet Gateway Power Supply Connection

The BACnet Gateway is powered by a +24VDC to +5VDC power supply unit (P/N 46175). If a
customer supplied power supply is used it may be any regulated, UL 1481 listed, power limited,
battery backed, +24 VDC power supply.
For Canadian installation, The BACnet Gateway must be powered by a ULC listed Fire Alarm
Control Unit or a ULC listed power supply for fire application.

Table 2.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

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 19

BACnet Gateway Embedded Installation BACnet Gateway Power Supply Connection

24VDC REF Input

+24VDC Input

Earth
+5VDC Output
5V REF Output

Red wire

Black wire To BACnet Gateway Board’s

HDD Power Connector
P/N 75581

Figure 2.5 BACnet Gateway Power Connection

Step 1. Connect the power supply to the gateway (Figure 2.5).

2.5.1 Network Communication Module Installation

Step 1. If applicable to your BACnet Gateway installation, install the type of NCM W/F board
you will use into the new CAB3/CAB4 cabinet or an existing panel’s or annunciator’s
cabinet.

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 board configuration that fits your installation needs.
• NCM-W with twisted pair wire.
• NCM-F with fiber-optic cable.
12 Clintonville Road
Northford, CT 06472-1653 USA
203-484-7161 • FAX 203-484-7118
www.notifier.com
Network Communications Module NCM-W/F
Product Installation Document
PN 51533:C 12/28/2006 06-069

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.

Figure 2.6 NCM W/F Board Installation Document, 51533

20 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Power Supply Connection BACnet Gateway Embedded Installation

Step 2. After the installation perform “BACnet Gateway Configuration” on page 23.

NOTE: For complete details on powering and connecting an NCM-W/F, refer to its Product
Installation Document P/N 51533.

2.5.2 IP and NFN Network Connections

NOTE: Connect BACnet Gateway to the IP network before connecting it to the NFN network.

Connecting a BACnet Gateway to an IP Network

This connection is the BACnet Gateway to your IP network (Internet or Intranet). A PNET-1 surge
suppressor must be used between the BACnet Gateway board and your network.
Step 1. Plug one end the RJ45 cable into the BACnet Gateway 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.

Gateway Board
Gateway board to PNET-1

To Internet or Intranet
PNET-1 surge suppressor

Figure 2.7 Ethernet Connection

Connecting a BACnet Gateway to an NFN Network

„ Power Supply Connection
An NCM-W/F can be powered by a NOTIFIER® panel/annunciators power source or the P/N
46175 power supply (Figure 2.8). If using a customer supplied external power supply, it may be
any regulated, UL 1481 listed, power limited, battery backed, +24 VDC power supply. For a
customer supplied external power supply in a Canadian installation, it must be a ULC listed Fire
Alarm Control Unit or a ULC listed power supply for fire application.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 21

BACnet Gateway Embedded Installation BACnet Gateway Power Supply Connection

Refer to Table 2.1, “46175 Power Supply Specifications” for power supply specifications.

24VDC REF Input

+24VDC Input

Earth
+5VDC Output
5V REF Output Black wire

Red wire P/N 75583*

To NCM NUP Port

*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.

Figure 2.8 NCM-W/F Power Connection

„ NFN Network Connection

The BACnet Gateway should not be connected to the NFN network until after it has been properly
configured. For more information, please refer to Section 3.1, “BACnet Gateway Configuration”,
on page 23.
Once the BACnet Gateway has been configured, refer to “Connect the BACnet Gateway to the
NFN Network or FACP” on page 32 for more information.

22 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Section 3 BACnet Gateway Configuration and
Operation

3.1 BACnet Gateway Configuration

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.

3.1.1 BACnet Gateway Configuration Overview

Perform the gateway configuration in this order:
• “BACnet Gateway Configuration Tool Installation” on page 23
• “Connect the Configuration Computer to the BACnet Gateway” on page 24
• “Prepare the Configuration Computer to Communicate with BACnet Gateway” on page 24
• “Log into the BACnet Gateway for Configuration” on page 25
• “Configure the BACnet Gateway” on page 26
• “Connect the BACnet Gateway to the NFN Network or FACP” on page 32

3.1.2 BACnet Gateway Configuration Tool Installation

The BACnet Gateway Configuration Tool CD-ROM is provided when the gateway is ordered. Use
these steps as guideline to install the application onto the computer that has Windows 2000 or XP
installed.
Step 1. Insert the CD-ROM into the CD-ROM drive on the computer that will be connected to the
gateway so the gateway can be configured.
Step 2. From Windows Explorer or the Run command, select and start the setup.exe file that is
located in the CD-ROM’s root directory. The installation program starts.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 23

BACnet Gateway Configuration and Operation BACnet Gateway Configuration

Step 3. Follow the displayed instructions to install the BACnet Gateway Configuration Tool.

3.1.3 Connect the Configuration Computer to the BACnet

Gateway
If your configuration computer is on the same IP network you connected the BACnet Gateway to in
the section, “Connecting a BACnet Gateway to an IP Network” on page 21, then your
configuration computer is already connected to the BACnet Gateway. Proceed to “Connect the
Configuration Computer to the BACnet Gateway” on page 24.
Otherwise, refer to Appendix C, “BACnet Gateway Local Configuration”, on page 45.

3.1.4 Prepare the Configuration Computer to Communicate with

BACnet Gateway
Configure your configuration computer to communicate with the default BACnet Gateway IP
address of 192.168.1.2.:
Step 1. From the Windows taskbar, click Start Ö Connect To Ö Show All Connections.
Step 2. Right-click your LAN connection, and then click Properties in the menu that appears.

24 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Configuration BACnet Gateway Configuration and Operation

Step 3. Select Internet Protocol (TCP/IP), and then click Properties.

Step 4. Record your current Internet Protocol (TCP/IP) property settings so you can restore them
later.
Step 5. Click Use the following IP address, and then type 192.168.1.X into the IP address field.

NOTE: X can be any number between 0 and 255 except for 2 (since the BACnet Gateway
default IP address is 192.168.1.2).

Step 6. Click OK, and then close all remaining open windows.

3.1.5 Log into the BACnet Gateway for Configuration

NOTE: The BACnet Gateway Configuration Tool must run at a resolution of 1024 X 768 or
greater.

Step 1. Launch the BACnet Gateway Configuration Tool by clicking Start Ö All Programs Ö
BACnet Gateway Config Tool from the Windows taskbar.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 25

BACnet Gateway Configuration and Operation BACnet Gateway Configuration

Step 2. Click the Address field, and then click the default gateway IP address 192.168.1.2 in the
menu that drops down.

Step 3. Click File Ö Login....

Step 4. Type the default password, 00000000, and then click OK.

3.1.6 Configure the BACnet Gateway

Set Up the SNTP Server
Synchronizing with an SNTP server allows the BACnet Gateway to keep accurate time.

NOTE: By default, the BACnet Gateway synchronizes its internal clock with the NFN network
time, or with the Fire Alarm Control Panel in the case of a direct connection. Configuring the
SNTP server is only necessary if you want the gateway to synchronize with another server, such
as an ONYXWorks® Workstation or an SNTP time server.

Step 1. In the left pane of the BACnet Gateway Configuration Tool under the Gateway heading,
click SNTP Configuration.
Step 2. Click the SNTP Server Address field under the Value heading, and then type the address
of the SNTP server.

Configure Time Zone Settings

Step 1. In the left pane of the BACnet Gateway Configuration Tool under the Gateway heading,
click Time Zone Configuration.

26 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Configuration BACnet Gateway Configuration and Operation

Step 2. Use the fields under the Value heading to enter your local Greenwich Mean Time offset
value as well as the appropriate information about the observance of Daylight Savings
Time.

Configure IP Settings
Step 1. In the left pane of the BACnet Gateway Configuration Tool under the Gateway heading,
click IP Configuration.
Step 2. Click the fields under the Value heading, and type the IP, Subnet Mask, and Gateway
(router) addresses this BACnet Gateway will use on your network.
Step 3. Click Apply to activate these settings.

The BACnet Gateway reboots automatically.

Restore Your Standard Internet Protocol (TCP/IP) Settings
Step 1. From the Windows taskbar, click Start Ö Connect To Ö Show All Connections.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 27

BACnet Gateway Configuration and Operation BACnet Gateway Configuration

Step 2. Right-click your LAN connection, and then click Properties in the menu that appears.

Step 3. Select Internet Protocol (TCP/IP), and then click Properties.

Step 4. Enter the settings you recorded earlier into the Internet Protocol (TCP/IP) Properties
dialogue, and then click OK to return your configuration computer to your IP network.
Finalize the BACnet Gateway Configuration
„ Log into the BACnet Gateway
Step 1. Click View Ö Refresh Gateway List to refresh the gateway address list.

28 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Configuration BACnet Gateway Configuration and Operation

Step 2. Click the Address field, and then, from the menu that drops down, click the IP address
you assigned this BACnet Gateway.

Step 3. Click File Ö Login....

Step 4. Type the default password, 00000000, and then click OK.

The BACnet Gateway Configuration Tool now displays the remaining configurable
settings for the BACnet Gateway. Click the fields under the Value heading to enter
appropriate values, following the guidelines in the following steps.

„ Gateway Properties
• We recommend you select the Life Safety Notification Type if your system supports it.
Otherwise, virtually all clients support Multi State notification.

• Set the NCM address to a nonzero number.

• If you are adding the BACnet Gateway to a network that already includes another gateway or
gateways, assign the Network Number based on the highest Network Number used by any
gateway already on the network. The Network Number for the new BACnet Gateway must be
greater than the highest Network Number by one thousand. For example, if the network

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 29

BACnet Gateway Configuration and Operation BACnet Gateway Configuration

already includes a gateway with a Network Number of 1001, then the lowest Network Number
which can be assigned to the new BACnet Gateway is 2001.

„ BBMD Configuration
• If the BACnet Gateway and the Building Management System (BMS) are connected to the IP
network across different subnets, they must be connected through a BACnet Broadcast
Management Device (BBMD). When using a BBMD, set the Foreign Device value to True
and enter values for IP Address, Port and Register Time.

„ Multiple Gateways
• NFN networks with more than 15 nodes must be monitored using the Multiple Gateway
option.
• When using this Multiple Gateway option, set the Multiple Gateway value to True, and enter a
value for each network node to be monitored by this BACnet Gateway.

• You may enter up to 14 nodes for FACPs to be monitored, since the BACnet Gateway can
support 15 nodes including itself.

30 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Configuration BACnet Gateway Configuration and Operation

„ Apply Settings
Step 5. Once all BACnet Gateway settings have been properly configured, click Apply at the
bottom of the Value pane to apply the settings and reboot the gateway.

NOTE: If you are changing settings on a BACnet Gateway previously configured with monitored
nodes, this screen button will be labeled Apply And Delete Objects.

3.1.7 Viewing BACnet Gateway Activity with the BACnet Gateway

Configuration Tool
The Gateway Activity window displays information about panels, network objects and NUP events
processed by the BACnet Gateway. This utility tracks up to the 4,000 most recent records. Store
this information permanently by clicking Save.

NOTE: The NFN network must be stable with very few events in order for the discovery process
to discover all objects upon initial configuration. After initial configuration, the BACnet Gateway
updates the network daily at its specified Network Update Time (the default time is 2:00:00).

It is helpful to launch the Gateway Activity window before connecting the BACnet Gateway to an
NFN network or directly to a Fire Alarm Control Panel, so you can monitor the messages the
BACnet Gateway generates in its initial Auto Discovery and Property Search routines. To open the
Gateway Activity window:
Step 1. Log into the BACnet Gateway (refer to “Log into the BACnet Gateway” on page 28).
Step 2. Click View Ö Gateway Activity.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 31

BACnet Gateway Configuration and Operation BACnet Gateway Configuration

The Gateway Activity window opens. Network traffic will affect the time required to populate the
Gateway Activity window.

3.1.8 Connect the BACnet Gateway to the NFN Network or FACP

Connecting the BACnet Gateway to an NCM-W/F allows the gateway to communicate with
devices on a NFN network. The NCM-W/F must be on the same NFN network as the gateway. The
BACnet Gateway may also be connected directly to a Fire Alarm Control Panel (FACP).

DB-9 end - connect to EIA-232 port

on Gateway Board Gateway Board

NUP end - connect to outer NUP port J2

Connect to an NCM-W/F or
a Supported NOTIFIER Panel
or Annunciator DB9 to NUP cable P/N 75554

Figure 3.1 DB-9 to NUP Connection

Step 1. A DB9 to NUP cable is used to connect a DB9 to NUP cable between the gateway and
NFN network in one of these ways:
• Connect the cable between to the BACnet Gateway board’s DB9 connector and a
NCM W/F 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 BACnet Gateway board’s DB9 connector and a
supported NOTIFIER® panel’s and annunciator’s CPU NUP connector.
Refer to Table 1.2 on page 10 for supported NOTIFIER® panels and annunciators.
Step 2. After the cable connection is made the gateway configuration is complete.
Step 3. You should now configure your BACnet Client to communicate with the gateway.

32 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Configuration BACnet Gateway Configuration and Operation

The BACnet client workstation front end must conform to BACnet Standard Annex J for
IP and support Device Objects, Binary Output Objects, and Multi-state Input or Life
Safety Points/Zones. It is also required to write to Notification Objects and receive
confirmed/unconfirmed event notification messages. For details, refer to Appendix B,
“PIC Statement”, on page 39.

3.1.9 Back Up BACnet Gateway

Backing up the BACnet Gateway is important once the gateway is working properly. In some
cases, if the gateway loses power while saving files, the gateway object database may be deleted.
Without a backup file, the gateway will need to rediscover the network and the recipient list may
also need to be set up again.

CAUTION: Auto Discovery and Property Search

! To ensure the full object database is preserved, give the BACnet Gateway time to complete its initial
Auto Discovery and Property Search procedures before backing it up. For more information, please
refer to “Viewing BACnet Gateway Activity with the BACnet Gateway Configuration Tool” on
page 31.

Step 1. Log into the BACnet Gateway (refer to “Log into the BACnet Gateway” on page 28).
Step 2. Click Tools Ö Backup Gateway.

Step 3. Navigate to where you want to store the backup file, type a name for the file, and then
click Save.

3.1.10 Restore BACnet Gateway

Follow these steps to restore a previously backed up BACnet Gateway.
Step 1. Log into the BACnet Gateway (refer to “Log into the BACnet Gateway” on page 28).

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 33

BACnet Gateway Configuration and Operation BACnet Gateway Operation

Step 2. Click Tools Ö Restore Gateway.

Step 3. Navigate to where the backup file (.bnk) was saved, click on the file name, and then click
Open.

The gateway is restored, and reboots automatically.

3.2 BACnet Gateway Operation

3.2.1 About BACnet Gateway Start Up
On start up, the gateway auto discovers devices (panels and annunciators.) and objects (detectors,
modules, panels circuits, zones, loops, battery, AC Power, Ground, etc....) on NFN network it is
connected to and creates BACnet objects according to your configuration.
Devices and objects are given names Below are some format examples:

An AFP1010 as node 142: .Name = 142AFP1010 (BACnet Device Object)

An NFS640 as node 234: .Name = 234_NFS640 (BACnet Device Object)

(Detector) Loop 5, Detector 83: L005D083 (BACnet Life Safety Point or Multi-state Input Object)

(Zone) Zone 134: ZONE0134 (BACnet Life Safety Zone or Multi-state Input Object)

Any Node, Loop 5, Control Module 12: L005C012 (BACnet Binary Output Object)

An AM2020 as node 120: .Name = 120_AM2020 (_ denotes spaces) (BACnet Device Object)

An NCM as node 11 connected to BACnet GW: .Name = 011_ _ _ BACGW (BACnet Device Object)

(Module) Loop 9, Module 120: L009M120 (BACnet Life Safety Point or Multi-state Input Object)

(Zone) Zone 1003: ZONE1003 (BACnet Life Safety Zone or Multi-state Input Object)

34 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Gateway Operation BACnet Gateway Configuration and Operation

(Panel Internal Devices)--LOOP 8, LOOP10, BATTERY, ANNUN021, ACPOWER, PANEL (BACnet Life Safety Point or
Multi-state Input Object)

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 35

BACnet Gateway Configuration and Operation BACnet Gateway Operation

36 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Appendix A: Glossary
B
NOTIFIER® BACnet Gateway An interface that
allows the NFN network to communicate with a
BACnet network.
F
FTP File Transfer Protocol, used to back up the
NOTIFIER® BACnet Gateway database and download
firmware for field upgrades.
H
HS-NCM-W/F High Speed Network Control Module,
a network interface enabling the NOTIFIER® BACnet
Gateway to communicate with other NFN devices.
I
IP Address Logical address designating a node on an
IP network with the format NNN.NNN.NNN.NNN,
where NNN groups can be between 0 and 255.
NFN The network of Fire Alarm Control
Panels.Ethernet - Local area network protocol.
T
Telnet An Internet protocol that allows you to
communicate directly with another computer on the
Internet by specifying the host name, port and terminal
type.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 37

Glossary

38 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Appendix B: PIC Statement

B.1 BACnet Protocol Implementation Conformance

Statement (Normative)
(This appendix is part of this Standard and is required for its use.)
• Applications Software Version: 3.11
• Firmware Revision: 3.11
• BACnet Protocol Revision: 1.2
Product Description:
This product presents NOTIFIER® Fire Panel and Annunciator nodes (operating as part of a NFN
network or stand-alone) and their associated objects as BACnet objects. Event notification for
Alarms, Troubles and other states are sent to registered BACnet client workstations.
BACnet Standardized Device Profile (Annex L)

BACnet Inter-operability Building Blocks Supported (Annex K)

DS-RP-B DS-RPM-B

DS-WP-B DS-WPM-B

AE-N-I-B AE-ACK-B

AE-ASUM-B AE-INFO-B

DM-DDB-B

DM-DOB-A DM-DOB-B

DM-LM-B

Segmentation Capability
• Segmented requests supported, Window Size 1024 max.
• Segmented responses supported, Window Size 1024 max.
Standard Object Types Supported - Life Safety Point/Life Safety Zone

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 39

PIC Statement BACnet Protocol Implementation Conformance Statement (Normative)

Present Value BACnet Enumeration BACnetLifeSafetyState NFN State

0 IssQ uiet Norm al

1 IssP reA larm P reA larm

2 IssA larm Fire A larm , S ecurity A larm (Life/P rope rty), C ritical P rocess A larm
(Life/P rope rty), M edical E m ergency
3 IssFault S ecurity Trouble, Fire Trouble, Non-Fire Trouble, Fire D evice or Zone
D isabled , Non-Fire D evice D isabled

7 IssA ctive Non-Fire A ctivation

22 IssS upervisory Supervisory (E quipm ent), S upervisory (G uard’s Tour)

Tracking Value BACnet Enumeration BACnetLifeSafetyState NFN State

0 IssQ uiet Norm al

1 IssP reA larm P reA larm

2 IssA larm Fire A larm , S ecurity A larm (Life/P rope rty), C ritical P rocess A larm
(Life/P rope rty), M edical E m ergency
3 IssFault S ecurity Trouble, Fire Trouble, Non-Fire Trouble, Fire D evice or Zone
D isabled , Non-Fire D evice D isabled
7 IssA ctive Non-Fire A ctivation

22 IssS upervisory Supervisory (E quipm ent), S upervisory (G uard’s Tour)

Event State BACnet Enumeration BACnetEventState NFN State

0 E sNorm al Norm al

1 E sFault S ecurity Trouble, Fire Trouble, Non-Fire Trouble, Fire D evice or Zone
D isabled , Non-Fire D evice D isabled
2 E sO ffNorm al A ll statuses other than norm al and fault.

Reliability BACnet Enumeration BACnetReliability NFN State

0 reNoFaultD etected A ll statuses other than trouble.

7 re_ UnreliableO ther S ecurity Trouble, Fire Trouble, Non-Fire Trouble

Mode BACnet Enumeration BACnetMode NFN State

0 Ism O ff P ow er-Up State

10 Ism E nabled S et if point has bee n disabled and subsequently enabled since startup.

11 Ism D isabled Fire D evice or Zone D isab led , Non-Fire D evice D isabled

Silence State BACnet Enumeration NFN State

0 ssUnsilenced A udibles Unsilenced

1 ssA udiblesS ilenced A udibles S ilenced

Operation BACnet Enumeration NFN State

Expected
0 NA

Maintenance BACnet Enumeration NFN State

Required
NA NA NA

Event Enable BACnet Event Transition Bit

toO ffNorm al

toFault

Direct Reading R E AL NA % A larm

Status Flags Boolean BACnet Status Flags NFN State

0,0,0,0 Norm al

1,0,0,0 InA larm Fire A larm , S ecurity A larm (Life/P rope rty), C ritical P rocess A larm
(Life/P rope rty), M edical E m ergen , P reA larm

1,1,0,0 InAlarm , Fault S ecurity Trouble, Fire Trouble, Non-Fire Trouble

1,0,0,1 InA larm , O utO fService Fire D evice or Zone D isab led , Non-Fire D evice D isabled

Out of Service Boolean NFN State

0 FALSE A ll statuses other than disable

1 TR UE Fire D evice or Zone D isab led , Non-Fire D evice D isabled

40 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Protocol Implementation Conformance Statement (Normative) PIC Statement

Standard Object Types Supported - Multi-state Input Standard Object Types

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 41

PIC Statement BACnet Protocol Implementation Conformance Statement (Normative)

Supported - Binary Output

Present Value BACnet Enumeration BACnetLifeSafetyState NFN State
0 IssQ uiet Norm al

1 IssP reAlarm P reAlarm

2 IssAlarm Fire Alarm , Security Alarm (Life/Prope rty), C ritical Process A larm
(Life/P roperty), M edical E m ergency
3 IssFault S ecurity Trouble, Fire Trouble, Non-Fire Trouble, Fire D evice or Zone
D isabled, Non-Fire D evice D isabled
7 IssA ctive Non-Fire A ctivation

22 IssSupervisory Supervisory (E quipm ent), Supervisory (G uard’s Tour)

Tracking Value BACnet Enumeration BACnetLifeSafetyState NFN State

0 IssQ uiet Norm al

1 IssP reAlarm P reAlarm

2 IssAlarm Fire Alarm , Security Alarm (Life/Prope rty), C ritical Process A larm
(Life/P roperty), M edical E m ergency
3 IssFault S ecurity Trouble, Fire Trouble, Non-Fire Trouble, Fire D evice or Zone
D isabled, Non-Fire D evice D isabled
7 IssA ctive Non-Fire A ctivation

22 IssSupervisory Supervisory (E quipm ent), Supervisory (G uard’s Tour)

Event State BACnet Enumeration BACnetEventState NFN State

0 E sNorm al Norm al

1 EsFault S ecurity Trouble, Fire Trouble, Non-Fire Trouble, Fire D evice or Zone
D isabled, Non-Fire D evice D isabled
2 E sO ffNorm al All statuses other than norm al and fault.

Reliability BACnet Enumeration BACnetReliability NFN State

0 reNoFaultD etected All statuses other than trouble.

7 re_UnreliableO ther Security Trouble, Fire Trouble, Non-Fire Trouble

Mode BACnet Enumeration BACnetMode NFN State

0 Ism O ff Pow er-Up State

10 Ism E nabled S et if point has been disabled and subsequently enabled since startup.

11 Ism D isabled Fire D evice or Zone D isabled, Non-Fire D evice D isabled

Silence State BACnet Enumeration NFN State

0 ssUnsilenced Audibles Unsilenced

1 ssA udiblesS ilenced Audibles S ilenced

Operation BACnet Enumeration NFN State

Expected
0 NA

Maintenance BACnet Enumeration NFN State

Required
NA NA NA

Event Enable BACnet Event Transition Bit

toO ffNorm al

toFault

Direct Reading R E AL NA % Alarm

Status Flags Boolean BACnet Status Flags NFN State

0,0,0,0 Norm al

1,0,0,0 InA larm Fire Alarm , Security Alarm (Life/Prope rty), C ritical Process A larm
(Life/P rope rty), M edical E m ergen , PreA larm

1,1,0,0 InA larm , Fault S ecurity Trouble, Fire Trouble, Non-Fire Trouble

1,0,0,1 InA larm , O utO fS ervice Fire D evice or Zone D isabled, Non-Fire D evice D isabled

Out of Service Boolean NFN State

0 FA LS E All statuses other than disable

1 TR UE Fire D evice or Zone D isabled, Non-Fire D evice D isabled

42 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

BACnet Protocol Implementation Conformance Statement (Normative) PIC Statement

Standard Object Types Supported - Notification Class

Write Property/Add List element required for Intrinsic Reporting.

„ Data Link Layer Options

„ Device Address Binding:

Is static device binding supported? (This is currently necessary for two-way communication with
MS/TP slaves and certain other devices.)
• Select - Yes
• No

„ Networking Options:
• Select - Router, Clause 6 - List all routing configurations, e.g., ARCNET-Ethernet, Ethernet-
MS/TP, etc. BACnet to Proprietary ARCnet Fire Network
• Annex H, BACnet Tunneling Router over IP
• BACnet/IP Broadcast Management Device (BBMD)
Does the BBMD support registrations by Foreign Devices?
• Yes
• Select - No

„ Character Sets Supported:

Indicating support for multiple character sets does not imply that they can all be supported
simultaneously.

If this product is a communication gateway, describe the types of non-BACnet equipment/

network(s) that the gateway supports:
Notifier Fire and Annunciator nodes compatible with NFN network v5.0 and later operating in a
network or stand-alone configuration.

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 43

PIC Statement BACnet Protocol Implementation Conformance Statement (Normative)

44 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Appendix C: BACnet Gateway Local Configuration

NOTE: This procedure is only necessary if you are configuring an BACnet Gateway using a
Configuration computer that is not already on the same IP network as the BACnet Gateway. Refer
to “IP and NFN Network Connections” on page 21.

NOTE: A direct connection requires that a cross over Ethernet cable to be made or purchased
by the customer.

C.1 Direct Connection to the Gateway Board

Connect the cross over cable between the Configuration computer network card’s RJ45 connector
and the BACnet Gateway board’s RJ45 connector (refer to "Cross Over Cable Specifications").

Gateway Board

To Configuration Computer

Figure C.1 Configuration Computer Direct Connection

„ Cross Over Cable Specifications

This cross over cable will be directly connected between the Configuration computer network
card’s RJ45 connector and the BACnet Gateway board’s RJ45 connector.
The cross over cable can be purchased or you can make one. Please use the following information
for the correct pinout requirements for each end of the cable. EIA/TIA wire color-code standard
568B is applicable.

Table C.1 Cross Over Cable (568B)

RJ45 Pin # RJ45 Pin #

Wire Color Diagram End #1 Wire Color Diagram End #2
(END 1) (END 2)

1 White/Orange 1 White/Green

2 Orange 2 Green

3 White/Green 3 White/Orange

4 Blue 4 Blue

5 White/Blue 5 White/Blue

6 Green 6 Orange

7 White/Brown 7 White/Brown

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 45

BACnet Gateway Local Configuration Direct Connection to the Gateway Board

Table C.1 Cross Over Cable (568B)

8 Brown 8 Brown

46 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Appendix D: Equations for Object IDs (Instance
Numbers)
These equations describe how object IDs (also called instance numbers) are assigned for each
panel.
• Zone = Panel address X 10000 + zone number + 1500
• Release Zone = Panel address X 10000 + zone number + 5500
• Forward Zone = Panel address X 10000 + zone number + 5520
• Device object = Panel address X 10000
• Detector = Panel address X 10000 + ((loop-1) X 1000) + (detector address-1)
• Module = Panel address X 10000 + ((loop-1) X 1000) + (module address+199)
• “PANEL” = Panel address X 10000 + 506
• “RESET” = Panel address X 10000 + 507
• “NETWORK_A” = Panel address X 10000 + 579
• “NETWORK_B” = Panel address X 10000 + 580
• “WALK TEST” = Panel address X 10000 + 582
• “CPU” = Panel address X 10000 + 505
• “GROUND” = Panel address X 10000 + 500
• “BATTERY” = Panel address X 10000 + 502
• “ACPOWER” = Panel address X 10000 + 501
• “LOOP 1” = Panel address X 10000 + 503
• “LOOP 2” = Panel address X 10000 + 504
• “LOOP 3” = Panel address X 10000 + 605
• “LOOP 4” = Panel address X 10000 + 677
• “LOOP 5” = Panel address X 10000 + 678
• “LOOP 6” = Panel address X 10000 + 679
• “LOOP 7” = Panel address X 10000 + 680
• “LOOP 8” = Panel address X 10000 + 681
• “LOOP 9” = Panel address X 10000 + 682
• “LOOP10” = Panel address X 10000 + 683

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 47

Equations for Object IDs (Instance Numbers)

48 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 Index
A installation 15
installation procedure 18
ANSI/ASHRAE 135-1995 7
PC Board layout 16
architecture
NFN network 13 PC board part number 15
power connection 19
single panel 12
system 12
ARCNET 43 H
HDD Power connector 15
B
BACnet Configuration Tool I
installation procedure 23 Installation
BACnet Gateway Environmental Conditions 9
Compatibility 10 IP
Features 7 connections 21
Network Diagram 13 IP Address 37
BACnet Inter-operability Building Blocks 39
BACnet Standard Annex J for IP 7
Bacnet Standardized Device Profile 39
L
Binary Output Objects 7 Life Safety Points 7
Life Safety Zones 7
lithium battery 16
C
cabinet installation 18
Character Sets Supported 43
M
Configuration computer Multi-state Input 7
connections 24
direct connection 45 N
NCM installation 20
D NCM-F 32
Data Link Layer Options 43 NCM-W 32
DB9 to NUP Cable 15 Network Interface PC Board 15
device NFN Network
BACnet names 34 power connection 21
Device Address Binding 43 NFN Network Connection 21
Device Compatibility 8 NFN Network Connections 21
Device Objects 7 Normative 39
Notification Class 43
Notification Objects 7
E NUP to +24VDC power cable 15
EIA/TIA wire color-code standard 45
Ethernet Connection 21
Ethernet cross over cable
O
specifications 45 object
Ethernet network cable 15 BACnet names 34

G P
Gateway Panel Compatibility 10
configuration 45 PIC STATEMENT 39
features 7 PNET-1 15
gateway Power Connections 19, 21
configuration overview 23 power supply
example installation diagram 17 mounting plate 15

BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 49

 Index

part number 15
Power Supply Connections 19, 21

R
Related Documentation 8

S
Segmentation Capability 39
Standard Object Types Supported 39
Supported - Binary Output 42
System Requirements 11

W
Wiring
Power 19

50 BACnet Gateway Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09

 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.

Notifier BACnet Gateway - Installation and Operation Manual - P/N: 51659:Rev: A7 2/10/09 51
 World Headquarters
12 Clintonville Road
Northford, CT 06472-1610 USA
203-484-7161
fax 203-484-7118

www.notifier.com