Unlock-Modbus Gateway IOM B2

MODBUS-GW
Installation and Operation Manual
Document LS10015-000NF-E
8/8/2013
Rev:
P/N LS10015-000NF-E:B2
B2
ECN 13-0116
Fire Alarm & Emergency Communication System Limitations

While a life safety system may lower insurance rates, it is not a substitute for life and property insurance!
An automatic fire alarm systemtypically made up of smoke
detectors, heat detectors, manual pull stations, audible warning
devices, and a fire alarm control panel (FACP) with remote notification capabilitycan provide early warning of a developing fire.
Such a system, however, does not assure protection against
property damage or loss of life resulting from a fire.
An emergency communication systemtypically made up of
an automatic fire alarm system (as described above) and a life
safety communication system that may include an autonomous
control unit (ACU), local operating console (LOC), voice communication, and other various interoperable communication methodscan broadcast a mass notification message. Such a
system, however, does not assure protection against property
damage or loss of life resulting from a fire or life safety event.
The Manufacturer recommends that smoke and/or heat
detectors be located throughout a protected premises following
the recommendations of the current edition of the National Fire
Protection Association Standard 72-2002 (NFPA 72-2002),
manufacturer's recommendations, State and local codes, and
the recommendations contained in the Guide for Proper Use of
System Smoke Detectors, which is made available at no charge
to all installing dealers. This document can be found at http://
www.systemsensor.com/appguides/. A study by the Federal
Emergency Management Agency (an agency of the United
States government) indicated that smoke detectors may not go
off in as many as 35% of all fires. While fire alarm systems are
designed to provide early warning against fire, they do not
guarantee warning or protection against fire. A fire alarm system
may not provide timely or adequate warning, or simply may not
function, for a variety of reasons:
Smoke detectors may not sense fire where smoke cannot
reach the detectors such as in chimneys, in or behind walls, on
roofs, or on the other side of closed doors. Smoke detectors also
may not sense a fire on another level or floor of a building. A second-floor detector, for example, may not sense a first-floor or
basement fire.
Particles of combustion or smoke from a developing fire
may not reach the sensing chambers of smoke detectors
because:
Barriers such as closed or partially closed doors, walls, chimneys, even wet or humid areas may inhibit particle or smoke
flow.
Smoke particles may become cold, stratify, and not reach
the ceiling or upper walls where detectors are located.
Smoke particles may be blown away from detectors by air
outlets, such as air conditioning vents.
Smoke particles may be drawn into air returns before reaching the detector.
The amount of smoke present may be insufficient to alarm
smoke detectors. Smoke detectors are designed to alarm at various levels of smoke density. If such density levels are not created by a developing fire at the location of detectors, the
detectors will not go into alarm.
Smoke detectors, even when working properly, have sensing
limitations. Detectors that have photoelectronic sensing chambers tend to detect smoldering fires better than flaming fires,
which have little visible smoke. Detectors that have ionizing-type
sensing chambers tend to detect fast-flaming fires better than
smoldering fires. Because fires develop in different ways and are
often unpredictable in their growth, neither type of detector is
necessarily best and a given type of detector may not provide
adequate warning of a fire.
Smoke detectors cannot be expected to provide adequate warning of fires caused by arson, children playing with matches
(especially in bedrooms), smoking in bed, and violent explosions
(caused by escaping gas, improper storage of flammable materials, etc.).

Heat detectors do not sense particles of combustion and alarm
only when heat on their sensors increases at a predetermined
rate or reaches a predetermined level. Rate-of-rise heat detectors may be subject to reduced sensitivity over time. For this reason, the rate-of-rise feature of each detector should be tested at
least once per year by a qualified fire protection specialist. Heat
detectors are designed to protect property, not life.
IMPORTANT! Smoke detectors must be installed in the same
room as the control panel and in rooms used by the system for
the connection of alarm transmission wiring, communications,
signaling, and/or power. If detectors are not so located, a developing fire may damage the alarm system, compromising its ability to report a fire.
Audible warning devices such as bells, horns, strobes,
speakers and displays may not alert people if these devices
are located on the other side of closed or partly open doors or
are located on another floor of a building. Any warning device
may fail to alert people with a disability or those who have
recently consumed drugs, alcohol, or medication. Please note
that:
An emergency communication system may take priority over
a fire alarm system in the event of a life safety emergency.
Voice messaging systems must be designed to meet intelligibility requirements as defined by NFPA, local codes, and
Authorities Having Jurisdiction (AHJ).
Language and instructional requirements must be clearly disseminated on any local displays.
Strobes can, under certain circumstances, cause seizures in
people with conditions such as epilepsy.
Studies have shown that certain people, even when they hear
a fire alarm signal, do not respond to or comprehend the
meaning of the signal. Audible devices, such as horns and
bells, can have different tonal patterns and frequencies. It is
the property owner's responsibility to conduct fire drills and
other training exercises to make people aware of fire alarm
signals and instruct them on the proper reaction to alarm signals.
In rare instances, the sounding of a warning device can cause
temporary or permanent hearing loss.
A life safety system will not operate without any electrical
power. If AC power fails, the system will operate from standby
batteries only for a specified time and only if the batteries have
been properly maintained and replaced regularly.
Equipment used in the system may not be technically compatible with the control panel. It is essential to use only equipment
listed for service with your control panel.
Telephone lines needed to transmit alarm signals from a premises to a central monitoring station may be out of service or temporarily disabled. For added protection against telephone line
failure, backup radio transmission systems are recommended.
The most common cause of life safety system malfunction is
inadequate maintenance. To keep the entire life safety system in
excellent working order, ongoing maintenance is required per the
manufacturer's recommendations, and UL and NFPA standards.
At a minimum, the requirements of NFPA 72-2002 shall be followed. Environments with large amounts of dust, dirt, or high air
velocity require more frequent maintenance. A maintenance
agreement should be arranged through the local manufacturer's
representative. Maintenance should be scheduled monthly or as
required by National and/or local fire codes and should be performed by authorized professional life safety system installers
only. Adequate written records of all inspections should be kept.
Limit-D-1-2013
MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013
Installation Precautions
Adherence to the following will aid in problem-free installation with long-term reliability:
WARNING - Several different sources of power can be
connected to the fire alarm control panel. Disconnect all
sources of power before servicing. The control unit and associated equipment may be damaged by removing and/or inserting cards, modules, or interconnecting cables while the unit is
energized. Do not attempt to install, service, or operate this
unit until this manual is read and understood.
CAUTION - System Reacceptance Test after Software
Changes. To ensure proper system operation, this product
must be tested in accordance with NFPA 72 after any programming operation or change in site-specific software. Reacceptance testing is required after any change, addition or
deletion of system components, or after any modification,
repair or adjustment to system hardware or wiring.
All components, circuits, system operations, or software functions known to be affected by a change must be 100% tested.
In addition, to ensure that other operations are not inadvertently affected, at least 10% of initiating devices that are not
directly affected by the change, up to a maximum of 50
devices, must also be tested and proper system operation verified.
This system meets NFPA requirements for operation at 0C to
49C (32F to 120F) and at a relative humidity 93% 2% RH
(non-condensing) at 32C 2C (90F 3F). However, the
useful life of the system's standby batteries and the electronic
components may be adversely affected by extreme temperature ranges and humidity. Therefore, it is recommended that
this system and all peripherals be installed in an environment
with a nominal room temperature of 15-27 C/60-80 F.
Verify that wire sizes are adequate for all initiating and indicating device loops. Most devices cannot tolerate more than a
10% I.R. drop from the specified device voltage.
Like all solid state electronic devices this system may operate
erratically or can be damaged when subjected to lightninginduced transients. Although no system is completely immune
from lightning transients and interferences, proper grounding
will reduce susceptibility. Overhead or outside aerial wiring is
not recommended, due to an increased susceptibility to
nearby lightning strikes. Consult with the Technical Services if
any problems are anticipated or encountered.
Disconnect AC power and batteries prior to removing or
inserting circuit boards. Failure to do so can damage circuits.
Remove all electronic assemblies prior to any drilling, filing,
reaming, or punching of the enclosure. When possible, make

all cable entries from the sides or rear. Before making modifications, verify that they will not interfere with battery, transformer, and printed circuit board location.
Do not tighten screw terminals more than 9 in-lbs. Over-tight-
ening may damage threads, resulting in reduced terminal contact pressure and difficulty with screw terminal removal.
Though designed to last many years, system components
can fail at any time. This system contains static-sensitive
components. Always ground yourself with a proper wrist strap
before handling any circuits so that static charges are removed
from the body. Use static-suppressive packaging to protect
electronic assemblies removed from the unit.
Follow the instructions in the installation, operating, and pro-
gramming manuals. These instructions must be followed to

avoid damage to the control panel and associated equipment.
FACP operation and reliability depend upon proper installation
by authorized personnel.
FCC Warning
WARNING: This equipment generates, uses, and can
radiate radio frequency energy and if not installed and
used in accordance with the instruction manual may
cause interference to radio communications. It has been
tested and found to comply with the limits for class A computing devices pursuant to Subpart B of Part 15 of FCC
Rules, which is designed to provide reasonable protection
against such interference when devices are operated in a
commercial environment. Operation of this equipment in a
residential area is likely to cause interference, in which
case the user will be required to correct the interference at
his or her own expense.
Canadian Requirements
This digital apparatus does not exceed the Class A limits
for radiation noise emissions from digital apparatus set
out in the Radio Interference Regulations of the Canadian
Department of Communications.
Le present appareil numerique n'emet pas de bruits radioelectriques depassant les limites applicables aux appareils numeriques de la classe A prescrites dans le
Reglement sur le brouillage radioelectrique edicte par le
ministere des Communications du Canada.
HARSH, NIS and NOTIFIRENET are all trademarks; and Acclimate Plus, FlashScan, NOTIFIER, ONYX, ONYX FirstVision, ONYXWorks,
VeriFire and VIEW are all registered trademarks of Honeywell International Inc. 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.
2013 by Honeywell International Inc. All rights reserved. Unauthorized use of this document is strictly prohibited.
Software Downloads
In order to supply the latest features and functionality in fire alarm and life safety technology to our customers, we make frequent upgrades to the embedded software in our products. To ensure that you are installing and programming the latest features, we strongly recommend that you download the most current version of software for each product prior to
commissioning any system. Contact Technical Support with any questions about software and the appropriate version for a
specific application.
Documentation Feedback
Your feedback helps us keep our documentation up-to-date and accurate. If you have any comments or suggestions about our
on-line help or manuals, please e-mail us at [email protected].
On-Line Help Please include the following information:
Product name and version number (if applicable)
Topic title
The content you think should be corrected/improved
Detailed suggestions for correction/improvement
Documents Please include the following information:
Document part number and title

Page number and paragraph
The content you think should be corrected/improved
Detailed suggestions for correction/improvement
Please Note: If you have any technical issues, please contact Technical Services.
Manual Usage
This manual is written with the understanding that the user has been trained in the proper operations and services for this product. The information provided in this manual is intended to assist the user by describing the configurations and how they affect
operations.
Table of Contents
Section 1 Product Overview .................................................................................................... 9
1.1: Operation .......................................................................................................................................................9
1.2: Functionality ..................................................................................................................................................9
1.3: Required Software .........................................................................................................................................9
1.4: Environmental Requirements ........................................................................................................................9
1.5: System Architecture.....................................................................................................................................10
Figure 1.1 Single Panel Architecture....................................................................................................10
Figure 1.2 NFN Network Architecture.................................................................................................10
1.5.1: Redundancy .......................................................................................................................................11
Figure 1.3 Redundant Modbus Gateways ............................................................................................11
1.6: IP Port Requirements ...................................................................................................................................12
1.7: Bandwidth Calculation ................................................................................................................................12
Table 1.1 Modbus TCP Request...........................................................................................................12
Table 1.2 Modbus TCP Response ........................................................................................................12
1.7.1: Calculating the Bandwidth Requirement...........................................................................................13
1.8: Agency Listings ...........................................................................................................................................13
1.8.1: Standards ...........................................................................................................................................13
1.8.2: Agency Restrictions and Limitations ................................................................................................14
1.9: Compatible Equipment ................................................................................................................................14
Table 1.3 MODBUS-GW Compatible Equipment...............................................................................14
Section 2 Installation ............................................................................................................. 15

2.1: Required Equipment ....................................................................................................................................15
2.2: Board Installation.........................................................................................................................................16
Figure 2.1 NFS-320 Series Installation ................................................................................................16
Figure 2.2 NFS2-640 Series Installation ..............................................................................................16
Figure 2.3 CHS-4L Installation ............................................................................................................16
Figure 2.4 Securing the Board..............................................................................................................16
2.3: Connections .................................................................................................................................................17
2.3.1: Board Layout .....................................................................................................................................17
Figure 2.5 MODBUS-GW Connections...............................................................................................17
Table 2.1 Connection Specifications....................................................................................................17
Figure 2.6 MODBUS-GW LEDs .........................................................................................................18
Table 2.2 LED Definitions ...................................................................................................................18
2.3.2: Connecting to a Standard NCM.........................................................................................................19
Figure 2.7 Routing Power and Communication to a Standard NCM...................................................19
Table 2.3 Standard NCM Connections.................................................................................................19
2.3.3: Connecting to an HS-NCM ...............................................................................................................20
Figure 2.8 Routing Power and Communication to an HS-NCM..........................................................20
Table 2.4 HS-NCM Connections .........................................................................................................20
2.3.4: Connecting to a Fire Alarm Control Panel (FACP) ..........................................................................21
Figure 2.9 Connecting to an FACP via NUP Connection ....................................................................21
2.3.5: Connecting to the PNET-1 Surge Suppressor ...................................................................................21
Figure 2.10 PNET-1 Surge Suppressor Connections ...........................................................................21
2.4: System Power ..............................................................................................................................................22
Table 2.5 Power Requirements.............................................................................................................22
2.5: Testing and Maintenance .............................................................................................................................22
Section 3 Configuration ......................................................................................................... 23

3.1: Configuration Web Page ..............................................................................................................................23
3.2: Connecting the Configuration Computer.....................................................................................................23
3.3: Configuring the MODBUS-GW..................................................................................................................23
3.3.1: Logging into the Web Page ...............................................................................................................23
3.3.2: Basic Configuration Tool Layout ......................................................................................................23
Figure 3.1 Basic Configuration Tool Layout .......................................................................................23
Table of Contents
3.3.3: MODBUS-GW Main Menus.............................................................................................................24

3.3.4: Product Information...........................................................................................................................25
3.3.5: Additional Properties.........................................................................................................................26
3.3.6: Node List ...........................................................................................................................................28
Section 4 Operation ................................................................................................................ 29

4.1: Panel and Gateway Synchronization ...........................................................................................................29
4.2: Modbus Command Support .........................................................................................................................29
4.2.1: Modbus Commands...........................................................................................................................29
4.2.2: Exception Responses .........................................................................................................................29
4.3: Modbus Addressing .....................................................................................................................................30
4.4: Analog Values and Trending........................................................................................................................30
4.4.1: Trending of Analog Values ...............................................................................................................30
4.4.2: Analog Value Use Cases ...................................................................................................................31
Section 5 Register Mapping................................................................................................... 33

5.1: Register Mapping Overview........................................................................................................................33
5.2: Point Status Holding Registers ....................................................................................................................33
Table 5.1 Device/Module Holding Register Addresses .......................................................................33
5.3: Point Device Type Holding Registers..........................................................................................................34
Table 5.2 Device And Module Addresses............................................................................................35
5.4: Zones/Panel Circuits Status Holding Registers ...........................................................................................35
Table 5.3 Zones ....................................................................................................................................36
Table 5.4 Panel Circuits .......................................................................................................................36
Table 5.5 Supported Circuits by Panel .................................................................................................36
5.5: Bell Circuits Status Holding Registers ........................................................................................................37
Table 5.6 Bell Circuit Holding Register Addresses .............................................................................37
5.6: Bell Circuits Device Type Holding Registers..............................................................................................38
Table 5.7 Bell Circuit Type Code Holding Register Addresses...........................................................38
5.7: Panel Status Holding Register .....................................................................................................................38
Table 5.8 Panel Status Holding Register Addresses ............................................................................38
5.8: Analog Values Input Registers.....................................................................................................................39
Table 5.9 Input Register Analog Values ..............................................................................................39
5.9: Panel and System Troubles Input Registers.................................................................................................39
Table 5.10 Panel and System Troubles Input Register Addresses .......................................................39
5.10: Gateway Information Input Registers........................................................................................................40
Table 5.11 Information/Debug Value Holding Register Addresses.....................................................40
5.10.1: Node Status Details .........................................................................................................................40
Table 5.12 Node Status Example .........................................................................................................40
5.10.2: Read Device Identification (0x2B/0x0E) ........................................................................................41
Table 5.13 43 / 14 (0x2B / 0x0E) READ DEVICE IDENTIFICATION ............................................41
Section 6 Troubleshooting..................................................................................................... 43
6.1: What are some basic guidelines I should use when installing a MODBUS-GW? ......................................43
6.2: How fast can the Modbus client poll the gateway? .....................................................................................43
6.3: How can I tell if the gateway is running? ....................................................................................................43
6.4: How do I recover a lost password from the gateway?.................................................................................43
6.5: What is an initialization read for analog values? .....................................................................................44
6.6: How many analog values can I read at a time?............................................................................................44
6.7: Why do I get an exception code when trying to read an analog value? ......................................................44
6.8: Why do I get all zeros when I read an analog value? ..................................................................................44
6.9: What is the Analog Value Polling Time Out? ..........................................................................................44
6.10: System Trouble ..........................................................................................................................................44
Appendix A: Gateway Settings.............................................................................................. 45

A.1: Viewing Existing IP Settings ......................................................................................................................45
A.2: Resetting Factory Default Values ...............................................................................................................45
Table of Contents
Appendix B: Exception Responses ..................................................................................... 47

Table B.1 Exception Codes ..................................................................................................................47
Appendix C: MODBUS-GW Active Event Types .................................................................. 49

Table C.1 Event Type Categories.........................................................................................................49
Appendix D: Device Types..................................................................................................... 51

Table D.1 Device Type Values Detectors .........................................................................................51
Table D.2 Device Type Values Monitor Modules ............................................................................52
Table D.3 Device Type Values Control Modules .............................................................................53
Appendix E: System Troubles .............................................................................................. 55

Table E.1 System Troubles Register Map............................................................................................55
Appendix F: Moxa MGate MB3180 Interface ........................................................................ 73

F.1: Hardware Configuration ..............................................................................................................................73
F.2: Moxa MGate MB3180 Interface with Modbus Gateway ............................................................................73
Figure F.1 Example System: Connect Through Cross Over Ethernet Cable .......................................73
Figure F.2 Example System: Connect Through Router .......................................................................74
F.3: Software Configuration................................................................................................................................74
Figure F.3 Connect a Configuration Computer....................................................................................74
Figure F.4 Moxa MGate Manager........................................................................................................75
Figure F.5 Moxa MGate Manager: Broadcast Search..........................................................................75
Figure F.6 Moxa MGate Manager: Configuration ...............................................................................76
F.3.1: Mode Tab ..........................................................................................................................................77
Figure F.7 Moxa MGate Manager Configuration Software: Mode Tab ..............................................77
F.3.2: Network Tab......................................................................................................................................78
Figure F.8 Moxa MGate Manager Configuration Software: Network Tab..........................................78
F.3.3: Serial Tab ..........................................................................................................................................79
Figure F.9 Moxa MGate Manager Configuration Software: Serial Tab ..............................................79
F.3.4: Slave ID Map Tab .............................................................................................................................80
Figure F.10 Moxa MGate Manager Configuration Software: Slave ID Map Tab ...............................80
F.3.5: Modbus Tab.......................................................................................................................................81
Figure F.11 Moxa MGate Manager Configuration Software: Modbus Tab ........................................81
F.4: Using The Moxa MGate MB3180 ...............................................................................................................81
Table of Contents
Section 1 Product Overview

1.1 Operation
The MODBUS-GW provides a communication link between stand alone FACPs or FACPs communicating
over an NFN or a high-speed NFN to Modbus client application.
1.2 Functionality
The MODBUS-GW:
Communicates with the NFN network through an HS-NCM or NCM that is on that NFN network or
a direct connection to a single FACP.
Supports Modbus Application Protocol Specification V1.1b
Monitors up to 4 FACPs. Additional MODBUS-GWs may be added to an NFN network to
accommodate additional FACPs.
1.3 Required Software

Microsoft Internet Explorer version 8 or later with the latest version of Java is required to configure the
MODBUS-GW.
1.4 Environmental Requirements

This product meets the following requirements for operation:
Temperature - 0C to 49C (32F - 120F)
Relative Humidity - 93 2% non-condensing at 32 2C (90 3F)
However, it is recommended that this product be installed in an environment with a normal room
temperature of 15-27 C (60-80 F).
Product Overview
System Architecture
1.5 System Architecture

An Internet or Intranet IP network connection is used with the architectures described in Figures 1.1 and 1.2.
IP Network
Ethernet
Ethernet
NUP
MODBUS-GW
FACP
Modbus/IP Client
Figure 1.1 Single Panel Architecture
IP Network
Ethernet
Ethernet
Ethernet
Modbus/IP Client
MODBUS-GW
Configuration Web
Page
MODBUS-GW
HS-NCM
or
NCM
NFN Network
FACP
FACP
FACP
Figure 1.2 NFN Network Architecture
10
System Architecture
Product Overview
1.5.1 Redundancy
To implement a redundant gateway, simply set up another MODBUS-GW to monitor the same nodes as the
first. The second gateway will need to have a separate and unique IP address from the first gateway. The
Modbus client can get the same information from either gateway.
Ethernet
Ethernet
Modbus Client
IP Network
Ethernet
MODBUS-GW
Configuration Web
Page
Ethernet
MODBUS-GW
MODBUS-GW
HS-NCM
OR
NCM
HS-NCM
OR
NCM
NFN Network
FACP
FACP
FACP
Figure 1.3 Redundant Modbus Gateways
11
Product Overview
IP Port Requirements
1.6 IP Port Requirements

The following IP ports must be available to the MODBUS-GW:
Port
Type
80
TCP
502
TCP
4016
TCP
62957
TCP
The following restrictions apply:

Functionality
Restriction
Infrastructure
Must have a Static IP Address, DHCP is not supported.

Web Access does not support access through an HTTP Proxy server.
1.7 Bandwidth Calculation

Use the following information to calculate the network bandwidth MODBUS-GW usage requires and how it
will impact the network.
Table 1.1 Modbus TCP Request
Description
Bytes
Ethernet Header
14
IP Header
20
TCP Header
20
MBAP Header
Message5 bytes Function code (1) + Start Address (2) + Quantity of Registers (2)
Total Bytes
66
Table 1.2 Modbus TCP Response

Description
12
Bytes
Ethernet Header
14
IP Header
20
TCP Header
20
MBAP Header
MessageFunction code (1) + Byte Count (1) + Max 100 registers of each 2 Bytes
(200)
202
Total Bytes
263
Agency Listings
Product Overview
1.7.1 Calculating the Bandwidth Requirement
One request and response pair requires 329 Bytes (66 + 263).
If a client is polling at one second intervals, then request and response are both possible in
one second.
A request and response pair creates network traffic of 329 Bytes per second (329 x 1).
In other words, a request and response pair creates network traffic of 2632 bits per second (329 x 8).
Therefore, the network must be able to accommodate at least 0.0027 Mbps data flow.
Once every five seconds, an analog request adds a small amount of network traffic.
Formula for MODBUS-GW network bandwidth requirement based on polling rate:

Bandwidth Requirement = (329 x (1000/polling rate in milliseconds) x 8) / (106) Mbps
1.8 Agency Listings

1.8.1 Standards
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
UL-2017
UL-2572
Control Units for Fire Alarm Systems, Ninth Edition

General Purpose Signaling Devices and Systems, First Edition
Mass Notification Systems, First Edition
Underwriters Laboratories Canada
CAN/ULC S527-99
CAN/ULC S559-04
Standard for Control Units for Fire Alarm Systems, Second Edition
Standard for Equipment for Fire Signal Receiving Centres and Systems, First
Edition
Installation - This product is intended to be installed in accordance with the following:

Local
AHJ
Authority Having Jurisdiction
National Fire Protection Association
NFPA 70
NFPA 72
NFPA 101
National Electrical Code

National Fire Alarm Code
Life Safety Code
Underwriters Laboratories Canada
CAN/ULC S524-06
CAN/ULC S561-03
Installation of Fire Alarm Systems, Fifth Edition

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
13
Product Overview
Compatible Equipment
1.8.2 Agency Restrictions and Limitations

MODBUS-GW is UL-864 listed for supplementary use only.
MODBUS-GW is UL-2572 listed for supplementary use only and cannot be used to trigger mass
notification announcements.
1.9 Compatible Equipment

For additional documentation on this product, go to http://esd.notifier.com.
Table 1.3 MODBUS-GW Compatible Equipment
Type
Equipment
Fire Panels:
Network Cards:
Other Products:
NFS-320
NFS2-640
NFS2-3030
NCM-W, NCM-F
HS-NCM-W, HS-NCM-SF, HS-NCM-MF, HS-NCM-WSF, HS-NCM-WMF,
HS-NCM-MFSF
DVC
NCA-2
NWS-3
BACNET-GW-3
NFN-GW-EM-3
PC NFN Gateways:
NFN-GW-PC-F
(Unmonitored/Network Compatible)
NFN-GW-PC-W
NFN-GW-PC-HNMF
NFN-GW-PC-HNSF
NFN-GW-PC-HNW
VESDA-HLI-GW
14
Section 2 Installation
2.1 Required Equipment
MODBUS-GW Assembly:
The following components are shipped with the MODBUS-GW:
MODBUS-GW printed circuit board
Surge suppressor (P/N PNET-1)
NUP-to-NUP Cable (P/N 75577) - Used to connect the MODBUS-GW board to an NCM-W or
NCM-F board or supported panel
Wire Leads-to-NUP Cable (P/N 75583) - Used to connect 24V power from the MODBUS-GW board
to an NCM-W or NCM-F board
USB Cable (P/N 75665) - Used to connect the MODBUS-GW board to an HS-NCM board:
HS-NCM-W
HS-NCM-WMF
HS-NCM-WSF
HS-NCM-MF
HS-NCM-SF
HS-NCM-MFSF
Network Components:
High-speed Network Communication Module (HS-NCM) - Used to facilitate network
communication between the MODBUS-GW and a high-speed NFN network (sold separately)
OR
Network Communication Module (NCM) - Used to facilitate network communication between the
MODBUS-GW and an NFN network (sold separately)
OR
Compatible FACP with NUP port
Customer Supplied Equipment:

A computer to run a Web Browser - Used to configure the MODBUS-GW
RJ45 to RJ45 standard Ethernet network cable - Customers Internet or intranet connection
15
Installation
Board Installation
2.2 Board Installation

The MODBUS-GW may be installed in a CAB-3 or CAB-4 cabinet as shown below.
Keypad Removed
Mounting Studs
Board
Board
Tab
Bracket Slot
Install bracket on 1/2 standoffs. Place the boards
Mount in 4th column of the NFS2-640 Series
tab in the bracket slot, screw the board to the top of
chassis. Mount chassis to backbox before installing
the standoffs. May be stacked in front of or behind
the board in rear position. May be mounted in front
another board using standoffs of adequate length to
of another board using standoffs of adequate length
clear the rear board.
to clear the rear board.
Figure 2.1 NFS-320 Series Installation
Three Possible Mounting

Positions - Rear Only
Figure 2.2 NFS2-640 Series Installation
Board Grounding Area
Screws
Screws
Slot
Slot
Figure 2.3 CHS-4L Installation
16
Figure 2.4 Securing the Board
Connections
Installation
2.3 Connections
2.3.1 Board Layout
USB B Device (J1)
USB A Host (J2)
Ethernet
Connector (J3)
NUP A
Connector (J4)
Mounting Hole
(1 of 12)
Not Used (J5)
Not Used (TB1)
(TB2)
+
+
24 V Out
24 V In
Figure 2.5 MODBUS-GW Connections

Table 2.1 Connection Specifications
Reference
Designator
TB2
Description
Specifications
N/A
Nominal Voltage: 24 VDC, Regulated

Current: 125 mA
Locate in same cabinet or use close nipple fitting
USB B
J2
USB A
J3
Ethernet
Line Impedance 100 ohm

Max Distance 328.083 ft. (100 m)
J4
NUP A
RS-232
J1
DC Power
Circuit
Class
All wiring from the power supply is power limited, and a separation of at least 1/4-inch (6.35 mm) must be maintained between
power limited and non-power limited wiring.
All interconnects are power limited.
Ethernet connections are power limited and supervised except for ground faults.
17
Installation
Connections
LEDs
(See Table Below)
D2
D3
D4
D7
D8
D9
D10
(J1)
(J2)
D1
D11
(J3)
D12
(J4)
(J5)
(TB1)
(TB2)
D22
Figure 2.6 MODBUS-GW LEDs

Table 2.2 LED Definitions
18
Reference
Designator
Label
D1
ACTIVE
D2
NUPA RX
D3
PROGRAM
Not Used
D4
NUPB RX
Not Used
D7
USB B
D8
NUPA TX
D9
USB A
D10
NUPB TX
D11
DATA
Blinks to indicate data transmission to or from the Ethernet port (J3).
D12
LINK
Active/Lit indicates an Ethernet connection.
D22
WDT FAIL
Description
Active/Lit indicates that WinCE is running.
Blinks when data is received on the NUP A port (J4).
Active/Lit indicates a device is connected to the USB B port (J1).

Blinks when data is sent on the NUP A port (J4).
Active/Lit indicates a device is connected to the USB A port (J2).
Not Used
Active/Lit indicates the system has undergone a reset due to a Watchdog

circuit activating.
Connections
Installation
2.3.2 Connecting to a Standard NCM

Connect Either
Cable to Either
NUP Connector
on the NCM
Communication
from NUP A (J4)
Only
MODBUS-GW
TB2
NCM
Out to NCM
24V In From External

Power Source to TB2
+
24 VDC
Figure 2.7 Routing Power and Communication to a Standard NCM

Table 2.3 Standard NCM Connections
Type
Connection
NCM-W
Twisted pair wire
NCM-F
Fiber-optic cable
19
Installation
Connections
2.3.3 Connecting to an HS-NCM
For Communications,
Connect USB A to B
OR USB B to A
MODBUS-GW
HS-NCM
TB2
Out to HS-NCM
+
24V In From External
Power Source to TB2
24 VDC
Figure 2.8 Routing Power and Communication to an HS-NCM

Table 2.4 HS-NCM Connections
20
Type
Connections
HS-NCM-W
Twisted pair wire
HS-NCM-SF
Single mode fiber-optic cable
HS-NCM-MF
Multimode fiber-optic cable
HS-NCM-WSF
Twisted pair wire, Single mode fiber-optic cable
HS-NCM-WMF
Twisted pair wire, Multimode fiber-optic cable
HS-NCM-MFSF
Multimode fiber-optic cable, Single mode fiber-optic cable
Connections
Installation
2.3.4 Connecting to a Fire Alarm Control Panel (FACP)
NUP Cable Provides Both

Power and Communication
From FACP
NUP Connector
To NUP A
(J4) only
MODBUS-GW
FACP
Not Used
Figure 2.9 Connecting to an FACP via NUP Connection
2.3.5 Connecting to the PNET-1 Surge Suppressor
J3
Ground
PNET-1
MODBUS-GW
Figure 2.10 PNET-1 Surge Suppressor Connections

21
Installation
System Power
2.4 System Power

Table 2.5 Power Requirements
Power
Requirement
Input Voltage (Nominal)
24 VDC
Input Current @ 24 VDC
125 mA
2.5 Testing and Maintenance

Testing and maintenance should be performed according to the Testing and Maintenance section of
NFPA-72 and CAN/ULC S561-03.
22
Section 3 Configuration
3.1 Configuration Web Page
The MODBUS-GW is configured through a dedicated web page running on the MODBUS-GW itself.
Microsoft Internet Explorer version 8 or later with the latest version of Java is required to configure the
MODBUS-GW.
3.2 Connecting the Configuration Computer

The computer used to configure the MODBUS-GW must be able to establish an IP connection to the
gateway. The default IP address of the MODBUS-GW is 192.168.1.2. Consult a network administrator if
unsure how to make this connection.
Refer to Appendix A, Gateway Settings for instructions on resetting and reviewing the IP settings for the
MODBUS-GW.
3.3 Configuring the MODBUS-GW

CAUTION: Multiple MODBUS-GW Installations
All MODBUS-GWs must be individually configured because they all use the same default IP address
and node number.
3.3.1 Logging into the Web Page

1.
Start Microsoft Internet Explorer.
2.
Navigate to the IP address of the MODBUS-GW (default http://192.168.1.2).
3.
Depending on the version of Java installed on the configuration computer, a security prompt may
appear. If it does, click NO to proceed to the configuration web page.
4.
If prompted, click Run to enable the applet.
5.
When the login dialog box displays, enter the password (default is eight zero characters) and then
click Login.
3.3.2 Basic Configuration Tool Layout

Click for Product
Information (see 3.3.4)
Navigation Tree
Main Menus (see 3.3.3)
Click to View Subitems (see 3.3.5)
Property/Value Pane
Click Blue Values

to Change
Click Boxes to
Select/Deselect
Node List (see 3.3.6)

(Red Indicates Off-line)
Figure 3.1 Basic Configuration Tool Layout

23
Configuration
Configuring the MODBUS-GW
3.3.3 MODBUS-GW Main Menus

The configuration main menus are located at the upper left-hand area of the screen (see Figure 3.1).
Menu
Sub-Menu
Description
File
Reboot
Reboots the MODBUS-GW.
View
Refresh Node
List
Refreshes the node list in the MODBUS-GW navigation pane.
Connected
Clients
Opens the Connected Clients screen. This screen displays IP Addresses for
Modbus clients connected to the MODBUS-GW.
Save to File - Saves the information in the activity window to a file.
Tools
Set Password
Displays a dialog box allowing the user to change the current password.
Default: 00000000 (eight zeros)
Passwords are case sensitive.
Alpha and numeric characters are supported.
One character minimum and 8 characters maximum.
Backup...
Browse to the folder where the current MODBUS-GW configuration settings

are to be stored, and then click Save.
Restore...
Displays a dialog box allowing that allows the user to restore the MODBUSGW configuration settings to a previously saved state.
Control
Displays a dialog box allowing the user to enable the Control feature.
Note: UL certification is voided if control is enabled.
Create CSV
Report
Allows the user to create a Comma Separated Value (CSV) register map
report in standard file format. This register map file serves as a reporting tool
for Modbus Master configuration.
With All Points Displays a dialog box that allows the user to generate
and save a map showing all possible points on all configured panels.
With Actual Points (Recommended) Displays a dialog box that allows
the user to generate and save a map of only the points that are configured
and mapped.
A register map report contains the following information:
Gateway IP Address Gateways configured IP address
Gateway Node Number NFN node number of the MODBUS-GW
Gateway Version MODBUS-GW Firmware version
Gateway Unit ID Modbus Unit ID. It is recommended this be the same
as the Gateway Node Number.
Gateway Node Type MODBUS-GW
Authorized Modbus Client IP Address This is a security feature. This
is the IP address of the client that is allowed to connect to the
MODBUS-GW If it is set to 0.0.0.0 then any client can connect.
Node Mapping for All Four Monitored Nodes Modbus mapping of
NFN nodes
Upgrade
24
Print CSV
Report
Prints the most recently generated register map report on the designated
printer. It is recommended that a new register map report be generated
immediately before printing.
Firmware
In the Look In drop down menu, select the file name that begins,
#MGNUW and has the extension .AR. Then click Open. An on-screen
dialog indicates a successful upgrade.
Configuration
3.3.4 Product Information

The following information displays when initially opening the configuration tool. It may also be accessed by
clicking the first entry in the navigation tree (see Figure 3.1).
Property
Value
Type
Displays the gateway type by name.
Version
Displays the gateway version number.
Board Type
Displays the hardware model type.
HS-GW-EM Kernel
Displays additional software version information.
HS-GW-EM Boot
Displays additional software version information.
25
Configuration
3.3.5 Additional Properties

The additional properties folder is located in the navigation tree area of the configuration tool (see
Figure 3.1).
Sub-Item
IP Address
Settings
Property
Value
IP Address
Click the value to change the IP address of the MODBUS-GW.

(Default is 192.168.1.2)
Subnet Mask
Click the value to change the subnet address of the MODBUS-GW.

(Default is 255.255.255.0)
IP Gateway
Click the value and enter the IP address of the IP Gateway for the host
network.
(Default is 0.0.0.0)
MAC Address
This is the MAC address of the gateway Ethernet port and is not configurable.
Note: After configuring the IP address settings, click Save in the lower right corner of the window.
NFN Settings
NFN
Information
(Read Only)
Node
Click value to assign the NFN node number of the MODBUS-GW.

(Default is 240)
Panel Label
Click value to enter panel label.
Channel A
Threshold
Select High for a high-noise NFN network.

Set to Low for a low-noise NFN network.
Channel B
Threshold
Select High for a high-noise NFN network.

Set to Low for a low-noise NFN network.
Style 7
Click the checkbox for a Style 7 SLC (Signaling Line Circuit) configured NFN
network.
Uncheck the checkbox for Style 4 SLC configured NFN network.
Connection
Port
Displays Serial when there is no NFN connection.
Connection
Type
Describes how the gateway is connected to the NFN.
NCM Version
Displays the NCM version number.

Note: NCM Version does not appear when there is no NFN connection.
NCM Status
Bits
Displays the NCM status, which can be: Piezo, UPS Failure, Network Fail Port A,
Network Fail Port B, High Speed Audio, NCM Sniffer Mode Active, Local Connection
Limit Exceeded, or None.
Note: NCM Status Bits does not appear if there is no NFN connection.
Fire Network
Time Policy
26
Displays Unsynced since MODBUS-GW does not synchronize time with the network.
Sub-Item
Node
Mapping
Configuration
Property
Authorized
Client IP
Value
This is an optional security feature. Click the IP address text to enter/change the client
IP address.
By default (0.0.0.0) the gateway allows any client to request data.
If anything other than 0.0.0.0 is entered into the Authorized Modbus Client IP
Address field, the gateway only responds to requests from a single client at that IP
no other Modbus clients may communicate with the gateway. However, any
computer running a browser in the local network will still be able to access the
MODBUS-GW configuration web page as normal.
Note: Even with the IP set to 0.0.0.0, the MODBUS-GW only communicates with one
client at a time. Once MODBUS-GW accepts a clients request to connect, it will not
accept any other request to connect until the original client has disconnected.
Gateway Unit
ID
This property assigns the Modbus Unit ID which the MODBUS-GW will use in the
Modbus network. This is a configurable property of the nodes. By default, the Modbus
Unit ID for a monitored node is set to be the same as the NFN Node ID. If for any reason
the Unit ID needs to be changed, click the value and type the new Unit ID number. Since
each Unit ID in the Modbus Network needs to be unique, change this number only if
there is a conflict in the Unit IDs in the Modbus network.
Note: Each of the 240 possible nodes on the NFN network (except for gateways, web
servers and DVCs) is automatically assigned a Modbus Unit ID. When a new Unit ID
number for a node is entered, the old Unit ID number is reassigned to whichever node
previously used the new Unit ID number was entered. However, the MODBUS-GW
configuration web page will not accept a new Unit ID number that is currently being used
by a monitored node. In order to reassign a Unit ID number used by a monitored node,
first assign a new Unit ID number for the monitored node.
Analog Value
Timeout
The minimum frequency at which the MODBUS-GW expects to receive continuing polls
from clients seeking analog values from 4-20 mA devices.
When a client that had been polling a set of analog values fails to re-poll the values
within the time out period, the MODBUS-GW stops polling the points in question. Once
the time out period expires without the MODBUS-GW receiving a repeated poll, any
further poll received will be treated as a new poll, and the first read will be considered an
initialization read (for more information, refer to 3.4, "Analog Values and Trending".
By default, the Analog Value Polling Time Out is 20 seconds.
Show All
Nodes
Check the Show All Nodes check box to display a list of all nodes defined on the
NFN network (even nodes that are unknown and/or off line).
In Show All Nodes mode, check the Show Online or Mapped Nodes box to display
only monitored and on-line nodes.
Node List
Monitored Column - A checkbox appears beside the name of nodes that the
MODBUS-GW can monitor, and also beside every Unknown node. Click the checkbox
to monitor the node. Uncheck the checkbox to disable monitoring.
Notes:
The Unknown nodes can only be seen in Show All Nodes mode.
If an Unknown node comes on line and is found to be of the wrong type for the
MODBUS-GW to monitor, its box is automatically unchecked.
Other nodes are displayed that are on the network, but are not usable by the MODBUSGW. Such nodes do not have a check box or unit ID.
Unit ID Column - Click the value to change the unit ID.
Note: Click Save in the lower right corner of the window after making changes to node mapping values in
this window. After clicking Save, wait while the gateway automatically reboots. Log in to the configuration
web page again when prompted.
27
Configuration
3.3.6 Node List

The node list is located in the navigation tree area of the configuration tool screen (see Figure 3.1). Click the
desired node designator to view information about that node. The information displayed is dependent on the
node type. Designators for off-line nodes display in red text.
Since the MODBUS-GW monitors itself, it also appears as a monitored node in the navigation pane. The
MODBUS-GW may be listed as an NFN gateway in the navigation pane. The MODBUS-GW displays
general register mapping information only, since unlike FACPs it does not connect directly to network
points.
Property
Value
Node
Displays the NFN network node number of the monitored node.
Version
Displays the hardware and software version information about the monitored node and the
devices used to connect it to the NFN network.
Register
Information
Displays hardware and software version information for the monitored node. The devices
used to connect the node to the NFN network are listed under the light blue Version
heading row.
For the Register Type property, click the down arrow in the Value column to select how
register information is displayed. The options are:
Analog Value Shows the analog values from 420 mA modules, if any, connected to the
node.
Device Type Shows a map of the registers storing device type information for points
attached to the node.
Status Shows a map of the registers storing status information for points attached to the
node.
28
Section 4 Operation
4.1 Panel and Gateway Synchronization
When making programming changes to a panel, it is important to verify that the MODBUS-GW has
synchronized with these changes. This assures reliable data from the gateway. There are several ways in
which a Modbus synchronizes with a panel:
Every 24 hours the gateway will attempt to compare its database with the panel database. If there is a
difference then the gateway will synchronize.
If the gateway receives a message from the panel that it has been reprogrammed through a
programming tool or from the front panel, then the gateway will attempt to resynchronize.
If the gateway is reset, the power is cycled or the panel connectivity is lost and reapplied.
Resynchronization does several things. First, the gateway updates all of its device type registers to match the
panels. Second, the gateway updates the device status registers to assure the gateway will provide accurate
state data. If the panel and panel network are not completely stable while the gateway is resynchronizing,
then the gateway aborts resynchronization.
4.2 Modbus Command Support

4.2.1 Modbus Commands
The MODBUS-GW supports the following Modbus commands:
Read Input Registers (0x04)
Read Holding Registers (0x03)
Write Single register (0x06)
Read Device Identification supported 43 / 14 (0x2B / 0x0E)
4.2.2 Exception Responses

The MODBUS-GW sends exception responses to its Modbus clients as appropriate (e.g. Invalid Command,
invalid data etc.). For more information, refer to Appendix B, Exception Responses, on page 47.
29
Operation
Modbus Addressing
4.3 Modbus Addressing

The MODBUS-GW uses Modbus Addressing within the following guidelines:
The MODBUS-GW operates similarly to a Modbus Bridge. Each MODBUS-GW can support up to
four panels on an NFN network. Each fire panel being addressed by the Modbus master on the NFN
network is identified by the Unit ID.
The Unit ID used in the MODBUS-GW must be in the range 1 through 247. This is a Modbus range
limitation. The Unit ID should match the node number of the NFN node that is being addressed. For
example, a unit ID of 127 addresses NFN node 127.
The MODBUS-GW communicates on standard Modbus IP port 502.

NOTE: Communication on Modbus IP port 502 not configurable and is a Modbus norm.
Standard register types and reference ranges are:

0x Coil 0000109999
1x Discrete Input 1000119999
3x Input Register 3000139999
4x Holding Register 4000149999
For more information on Modbus addressing, refer to Section 5, Register Mapping, on page 33.
4.4 Analog Values and Trending

4.4.1 Trending of Analog Values
Trending of analog values is supported on all of the panels/networks 420 mA modules. The only limitation
is that the gateway will only actively read analog values for up to 10 analog modules at a time. All the
analog values on all the modules can be read as long as a separate poll is sent for these points in groups of up
to 10 points at a time, following the rules outlined below. Reference 4.4.2, "Analog Value Use Cases" for
clarity on this issue.
Accept a poll for up to any 10 analog (420 mA) points per gateway.
Requests for more points than this are rejected with an exception code.
If any of the points in the request are not 420 mA modules then the gateway rejects the request with
an exception code.
The first poll for analog values is an initialization poll. This initialization poll informs the gateway to
start acquiring analog values for these points at 5 second intervals.
Points are only polled on the NFN if the 420 mA module is in at least the first level of alarm status.
If the point is normal then the gateway returns a value of zero.
NOTE: The first response to an analog point poll is zero. This response is an initialization
confirmation from the gateway.
Upon receiving the initialization confirmation, the client can begin polling the analog points. The client
should wait 5 seconds after the initialization request to insure that the MODBUS-GW has had enough
time to get the analog values and load the registers. Thereafter the MODBUS-GW continues to poll the
points. The analog value in the MODBUS-GW are updated no faster than once every 5 seconds.
Points are polled if the device is in at least the first level of alarm status. Zero is returned for devices
not in alarm status.
When a point being polled enters normal status, polling for that point on the NFN is terminated and
the analog value register for that point is filled with zeros.
30
The MODBUS-GW ceases polling the analog points when:

Analog Values and Trending
Operation
The client does not make a request for these exact same points over a period defined in the Modbus
Configuration Tool as Analog Value Time Out. The default is 20 seconds.
The gateway makes a request for a point (or points) that is not exactly the same as the initial request.
The MODBUS-GW first sends an initial confirmation for the new set of analog points, and then
begins polling those points at 5 second intervals.
When a 420 mA module is in fault, the analog value register for that point is filled with zeros.
4.4.2 Analog Value Use Cases

Use Case 1: A client requests analog values from the points L1M1 through L1M10 every 10 seconds.
Result: The MODBUS-GW sends back zeros in response to the first request for analog values from the
points L1M1 through L1M10. The MODBUS-GW sends back actual values on the second request from
the client 5 seconds later. The MODBUS-GW continues to poll these devices as long as the client
continues to send analog value requests for points L1M1 through L1M10 at a rate faster than the Analog
Value Time Out.
Use Case 2: A client requests analog values from the points L1M1 through L1M10. After 10 minutes of
polling on a 10 second interval the client stops requesting analog values for these points.
the client 10 seconds later. The MODBUS-GW continues to poll these devices as long as the client
continues to send analog value requests for points L1M1 through L1M10. When the client stops polling
at 10 minutes, the MODBUS-GW will stop polling the NFN after the Analog Value Time Out expires.
polling on a 10 second interval the client requests analog values from the points L1M20 to L1M22.
the client 10 seconds later. The Gateway continues to poll these devices as long as the client continues
to send analog value requests for the points L1M1 through L1M10. When the client sends a request for
analog values from the points L1M20 through L1M22, the MODBUS-GW immediately sends back
zeros in response to the first analog value request from these points, and starts polling L1M20 through
L1M22. The MODBUS-GW only polls the points specifically requested.
polling on a 10 second interval, the client requests analog values from the points L1M5 through L1M12.
points L1M1 through L1M10. The MODBUS-GW sends back actual values in response to the second
request from the client 10 seconds later. The MODBUS-GW continues to poll these devices as long as
the client continues to send analog value requests for the points L1M1 through L1M10. When the client
sends a request for analog values from the points L1M5 through L1M12, the gateway immediately
sends back zeros in response to the first analog value request from points L1M11 and L1M12 (since
these are newly requested points) and it sends back actual values in response to the continuing analog
value requests for points L1M5 through L1M10 (since it already has been polling these points). The
gateway stops polling points L1M1 through L1M4 and starts polling points L1M5 through L1M12.
Use Case 5: A client requests analog values from the points L1M1 through L1M15.
Result: The MODBUS-GW sends back an exception response, because it can only process requests for
up to 10 analog values at a time. The client should request and receive values for L1M1 through
L1M10, and then send a request for L1M11 through L1M15. Note that the first request for analog
values from a valid range of points is considered an initialization request, which returns zeros.
31
Operation
32
Analog Values and Trending
Section 5 Register Mapping

5.1 Register Mapping Overview
The MODBUS-GW uses 16-bit registers.
One Modbus Input register and one Modbus Holding Register are allocated for each device address.
These registers represent a contiguous address mapping of all devices and points.
5.2 Point Status Holding Registers

Each of the point status holding registers are divided up into two bytes as defined below:
Active Event Type: This byte communicates the active event type as defined in Appendix C,
MODBUS-GW Active Event Types, on page 49. An active state is defined in this gateway as any
Fire, Security, Critical Process, Medical or Supervisory alarm state. This byte will be all 0's if the device
is not in an active state (see Active bit description in the bulleted list below). Inactive states include any
state not shown in Appendix C. These states include, normal, troubles, disables, prealarms, etc. This
byte will be all 1's if the point is not present in the panel.
Ack Fire Alarm: If this bit is set to 1 then the fire alarm on this point is acknowledged.
Disable: If this bit is set to 1 then the point is disabled.
Enable: If this bit is set to 1 then the point is enabled.
Active: If this bit is set to 1 then the point is Active and there will be an active event type in the lower
byte.
InActive: If this bit is set to 1 then the point is not active.
Trouble: If this bit is set to 1 then the point is in a trouble state.
Prealarm: If this bit is set to 1 then the point is in a prealarm state.
Ack Block: If this bit is set to 1 then all events on this point, other than fire alarm, are acknowledged.
Upper Byte
15
Ack Block
14
13
Prealarm Trouble
12
11
Lower Byte
10
7 6 5 4 3 2 1 0
InActive Active Enable Disable Ack Fire Alarm
Active Event Type
Table 5.1 Device/Module Holding Register Addresses

Start Address
End Address
Device Address
40001
40200
L1D1L1D159
40201
40400
L1M1L1M159
40401
40600
L2D1L2D159
40601
40800
L2M1L2M159
40801
41000
L3D1L3D159
41001
41200
L3M1L3M159
41201
41400
L4D1L4D159
33
Register Mapping
Point Device Type Holding Registers
Table 5.1 Device/Module Holding Register Addresses (Continued)

Start Address
End Address
Device Address
41401
41600
L4M1L4M159
41601
41800
L5D1L5D159
41801
42000
L5M1L5M159
42001
42200
L6D1L6D159
42201
42400
L6M1L6M159
42401
42600
L7D1L7D159
42601
42800
L7M1L7M159
42801
43000
L8D1L8D159
43001
43200
L8M1L8M159
43201
43400
L9D1L9D159
43401
43600
L9M1L9M159
43601
43800
L10D1L10D159
43801
44000
L10M1L10M159
NOTES:
There are unused registers on every loop in order to make the register addresses easier to
remember and allow for future expansion *(e.g. registers 40159 through 40200 are not used).
On the AFP-2800, output activation status is not reported to the MODBUS-GW and therefore
the bits and event type will always indicate a non-active state. AFP-2800 activations from the
Modbus client are not supported.
5.3 Point Device Type Holding Registers
Consists of 2000 holding registers.
Each register represents the device or module type for two points as defined below.
The upper byte has the even number points; the lower byte has the odd number points.
See Appendix D, Device Types, on page 51 for device type definition.
Upper Byte
15
14
13
12
11
Device Type
34
Lower Byte
10
Device Type
Zones/Panel Circuits Status Holding Registers
Register Mapping
Table 5.2 Device And Module Addresses

Start Address
End Address
Devices In Upper Byte
Devices In Lower Byte
44001
44100
Loop 1 Detector 2,4,6,8,10...158
Loop 1 Detector 1,3,5,9,11...159
44101
44200
Loop 1 Module 2,4,6,8,10...158
Loop 1 Module 1,3,5,9,11...159
44201
44300
Loop 2 Detector 2,4,6,8,10...158
Loop 2 Detector 1,3,5,9,11...159
44301
44400
Loop 2 Module 2,4,6,8,10...158
Loop 2 Module 1,3,5,9,11...159
44401
44500
Loop 3 Detector 2,4,6,8,10...158
Loop 3 Detector 1,3,5,9,11...159
44501
44600
Loop 3 Module 2,4,6,8,10...158
Loop 3 Module 1,3,5,9,11...159
44601
44700
Loop 4 Detector 2,4,6,8,10...158
Loop 4 Detector 1,3,5,9,11...159
44701
44800
Loop 4 Module 2,4,6,8,10...158
Loop 4 Module 1,3,5,9,11...159
44801
44900
Loop 5 Detector 2,4,6,8,10...158
Loop 5 Detector 1,3,5,9,11...159
44901
45000
Loop 5 Module 2,4,6,8,10...158
Loop 5 Module 1,3,5,9,11...159
45001
45100
Loop 6 Detector 2,4,6,8,10...158
Loop 6 Detector 1,3,5,9,11...159
45101
45200
Loop 6 Module 2,4,6,8,10...158
Loop 6 Module 1,3,5,9,11...159
45201
45300
Loop 7 Detector 2,4,6,8,10...158
Loop 7 Detector 1,3,5,9,11...159
45301
45400
Loop 7 Module 2,4,6,8,10...158
Loop 7 Module 1,3,5,9,11...159
45401
45500
Loop 8 Detector 2,4,6,8,10...158
Loop 8 Detector 1,3,5,9,11...159
45501
45600
Loop 8 Module 2,4,6,8,10...158
Loop 8 Module 1,3,5,9,11...159
45601
45700
Loop 9 Detector 2,4,6,8,10...158
Loop 9 Detector 1,3,5,9,11...159
45701
45800
Loop 9 Module 2,4,6,8,10...158
Loop 9 Module 1,3,5,9,11...159
45801
45900
Loop 10 Detector 2,4,6,8,10...158
Loop 10 Detector 1,3,5,9,11...159
45901
46000
Loop 10 Module 2,4,6,8,10...158
Loop 10 Module 1,3,5,9,11...159
5.4 Zones/Panel Circuits Status Holding Registers

Each of the zones/panel circuits holding registers are divided up into two bytes as defined below:
Fire, Security, Critical Process, Medical or Supervisory alarm state. This byte will be all 0's if the zone/
panel circuit is not in an active state (see Active bit description in the bulleted list below). Inactive states
include any state not shown in Appendix C. These states include, normal, troubles, disables, prealarms,
etc. This byte will be all 1's if the zone/panel circuit is not present in the panel.
Ack Fire Alarm: If this bit is set to 1 then the fire alarm on the zone/panel circuit is acknowledged.
Disable: If this bit is set to 1 then the zone/panel circuit is disabled.
Enable: If this bit is set to 1 then the zone/panel circuit is enabled.
35
Register Mapping
Zones/Panel Circuits Status Holding Registers
Active: If this bit is set to 1 then the zone/panel circuit is Active and there will be an active event type in
the lower byte.
InActive: If this bit is set to 1 then the zone/panel circuit is not active.
Trouble: If this bit is set to 1 then the zone/panel circuit is in a trouble state.
Prealarm: If this bit is set to 1 then the zone/panel circuit is in a prealarm state.
Ack Block: If this bit is set to 1 then all events on the zone/panel circuit, other than fire alarm, are
acknowledged.
Upper Byte
15
14
Ack Block
13
12
Prealarm Trouble
11
Lower Byte
10
7 6 5 4 3 2 1 0
InActive Active Enable Disable Ack Fire Alarm
Active Event Type
Table 5.3 Zones

Zone Type
Register Address
Zone Address
General Zones
4600147000
Z 1,2,3,4,5,6,7,8,...1000
Logic Zones
4700149000
Z 1,2,3,4,5,6,7,8,...2000
Trouble Zones
4900149100
Z 1,2,3,4,5,6,7,8,...100
Releasing Zones
4910149110
Z 1,2,3,4,5,6,7,8,9,10
Table 5.4 Panel Circuits

Register Address
Panel Circuits
4911149118
4911949126
4912749134
4913549142
4914349150
4915149158
4915949166
4916749174
4917549182
4918349190
4919149198
4919949206
P1.1P1.8
P2.1P2.8
P3.1P3.8
P4.1P4.8
P5.1P5.8
P6.1P6.8
P7.1P7.8
P8.1P8.8
P9.1P9.8
P10.1P10.8
P11.1P11.8
P12.1 P12.8
Table 5.5 Supported Circuits by Panel
36
Panel
Max Panel Circuits Points
NFS-320
Not Supported
NFS-640
NFS2-640
Not Supported
NFS-3030
12
NFS2-3030
Not Supported
Bell Circuits Status Holding Registers
Register Mapping
5.5 Bell Circuits Status Holding Registers

NFS2-640 and NFS-320 Only
Each of the bell circuits status holding registers are divided up into two bytes as defined below:
Fire, Security, Critical Process, Medical or Supervisory alarm state. This byte will be all 0's if the bell
circuit is not in an active state (see Active bit description in the bulleted list below). Inactive states
include any state not shown in Appendix C. These states include, normal, troubles, disables, prealarms,
etc. This byte will be all 1's if the bell circuit is not present in the panel.
Ack Fire Alarm: If this bit is set to 1 then the fire alarm on the bell circuit is acknowledged.
Disable: If this bit is set to 1 then the bell circuit is disabled.
Enable: If this bit is set to 1 then the bell circuit is enabled.
Active: If this bit is set to 1 then the bell circuit is Active and there will be an active event type in the
lower byte.
InActive: If this bit is set to 1 then the bell circuit is not active.
Trouble: If this bit is set to 1 then the bell circuit is in a trouble state.
Prealarm: If this bit is set to 1 then the bell circuit is in a prealarm state.
Ack Block: If this bit is set to 1 then all events on the bell circuit, other than fire alarm, are
acknowledged.
Upper Byte
15
14
Ack Block Prealarm
Lower Byte
13
12
11
10
Trouble
InActive
Active
7 6 5 4 3 2 1 0
Enable Disable Ack Fire Alarm
Active Event Type
Table 5.6 Bell Circuit Holding Register Addresses

Start Address
End Address
Device Address
49400
49400
Bell Circuit 1
49401
49401
Bell Circuit 2
49402
49402
Bell Circuit 3
49403
49403
Bell Circuit 4
37
Register Mapping
Bell Circuits Device Type Holding Registers
5.6 Bell Circuits Device Type Holding Registers

Each register represents the device type for two points as defined below.
Each register represents two bell circuits as defined below.
See Appendix D, Device Types, on page 51 for device type definition.

Upper Byte
15
14
13
12
11
Lower Byte
10
Device Type
Device Type
Table 5.7 Bell Circuit Type Code Holding Register Addresses

Start Address
End Address
Device Address
Device Address
49410
49410
Bell Circuit 2
Bell Circuit 1
49411
49411
Bell Circuit 4
Bell Circuit 3
5.7 Panel Status Holding Register

The holding register is divided up into bit fields as defined below:
Reset: Not used.
Silence: The fire alarm control panel is silenced when this bit is set to 1.
Upper Byte
15
14
13
12
11
Lower Byte
10
Not used
1
Silence
0
Reset
Table 5.8 Panel Status Holding Register Addresses

Start Address
49500
38
End Address
49500
Description
Panel Status Holding Register
Analog Values Input Registers
Register Mapping
5.8 Analog Values Input Registers

Analog Values are only available for 420 mA modules. Refer to Section 4.4, Analog Values and
Trending, on page 30 for details regarding analog values.
Table 5.9 Input Register Analog Values
Start Address
End Address
Analog Value (16 bits)
30001
30200
L1M1L1M159
30201
30400
L2M1L2M159
30401
30600
L3M1L3M159
30601
30800
L4M1L4M159
30801
31000
L5M1L5M159
31001
31200
L6M1L6M159
31201
31400
L7M1L7M159
31401
31600
L8M1L8M159
31601
31800
L9M1L9M159
31801
32000
L10M1L10M159
5.9 Panel and System Troubles Input Registers

Sixty-Four 16 bit registers are reserved for panel troubles.
One register is assigned as an overall panel trouble indicator.
Table 5.10 Panel and System Troubles Input Register Addresses
Start Address
End Address
Description
35000
35000
Panel Trouble Summary (Total number of Trouble bits set

for the node)
35001
35064
Panel Troubles
A single bit is reserved for each trouble in the system. The assignment of bits to trouble codes are shown in
Appendix E, System Troubles, on page 55.
39
Register Mapping
Gateway Information Input Registers
5.10 Gateway Information Input Registers

NOTE: Information/debug values are used by the MODBUS-GW Unit ID only. All other nodes
reject reads in this address range.
The MODBUS-GW records some status and configuration information for debugging and technical support
purposes. This information is stored in some reserved gateway registers as outlined below:
Gateway Modbus address
Gateway IP address
Gateway Version Number
Gateway status
Table 5.11 Information/Debug Value Holding Register Addresses
Start Address
End Address
Description
35100
35500
Information/Debug info
35100
35115
Node Status
1 = On Line
0 = Off Line
The MODBUS-GW tracks the node status of all
nodes on the NFN network.
35116
35116
Gateway major version number
35117
35117
Gateway minor version number
35118
35118
Gateway build
35119
35119
Gateway Status
1 = On Line
0 = Off Line
5.10.1 Node Status Details

Each nodes status is represented by a bit in a register. If the bit is set then the node is on line. Below is an
example of how this is represented in a register:
Table 5.12 Node Status Example
40
Bit#
15
14
13
12
11
10
3510
0
N1
6
N1
5
N1
4
N1
3
N1
2
N1
1
N1
0
N9
N8
N7
N6
N5
N4
N3
N2
N1
3510
1
N3
2
N3
1
N3
0
N2
9
N2
8
N2
7
N2
6
N2
5
N2
4
N2
3
N2
2
N2
1
N2
0
N1
9
N1
8
N1
7
Register Mapping
5.10.2 Read Device Identification (0x2B/0x0E)

This function code allows reading the identification and additional information.
Table 5.13 43 / 14 (0x2B / 0x0E) READ DEVICE IDENTIFICATION
Object ID
Object Name /
Description
Value
0x00
VendorName
Notifier
0x01
ProductCode
0x02
MajorMinorRevision
V1.0
0x03
VendorUrl
www.honeywelllifesafety.com
0x04
ProductName
Modbus Gateway
0x05
ModelName
Modbus Gateway
0x06
UserApplicationName
Modbus Gateway
41
Register Mapping
42
Section 6 Troubleshooting
6.1 What are some basic guidelines I should use when
installing a MODBUS-GW?
Polling should be done slowly to start.
Use Modscan to debug the system rather than a more complicated client. Verify that registers are being
updated as events happen on the NFN network/panel.
Make sure gateway can be pinged from the same computer on which the client application is being
installed.
Check and double check the power supplies as well as all cabling.
Make sure the client supports Unit IDs.
Stop the client from sending a subsequent request until after it receives a response from the gateway.
Make sure the client accepts all exception responses. Including 0xA and 0xB.
Use Wireshark to debug IP traffic.
Be sure only one client is polling the gateway.
Check the MODBUS-GW configuration tool and be sure that the Authorized Client IP address is set to
0.0.0.0. If using the Authorized Client IP security feature, confirm that the address in the gateway
matches the address in the Modbus client.
6.2 How fast can the Modbus client poll the gateway?
The polling rate is a function of several variables. Some issues that will determine the maximum poll rate
are:
The size of the NFN network that is being monitored.
The number of points on the panels.
The event activity on the NFN network/panel (i.e. VeriFire downloads).
Requests for analog values are much slower than other requests
If only a partial response form the gateway is seen in the Modbus client, try increasing the response
time out value in the client to a larger value. If the value is set to 5 seconds or more, this should be
adequate. The exact response time out will depend on IP network delays and routing. On a small IP
network, the gateway responds to a read of 100 register in less than 1 second.
The gateway also has some processing overhead in order to do such things as maintain the registers.
6.3 How can I tell if the gateway is running?
Ping the gateway from the computer on which the Modbus client is running.
Use Wireshark to analyze the data on the IP network.
Modscan was one tool that was used during development to test the gateway. It is designed primarily as
a testing device for verification of correct protocol operation in new or existing systems.
6.4 How do I recover a lost password from the gateway?

If the password for the gateway is lost, programming changes cannot be made. In this situation, the gateway
settings must be reset. Please refer to Appendix A, Gateway Settings for instructions.
43
Troubleshooting
What is an initialization read for analog values?
6.5 What is an initialization read for analog values?

This is the first read of up to 10 analog values from a 420 mA module. This first read tells the gateway that
it should begin a polling routine for the analog values in this request. The first response from the
initialization will usually be all zeros. Subsequent responses will have the actual values.
6.6 How many analog values can I read at a time?

Ten analog values can be read at one time. An initialization read must be performed.
6.7 Why do I get an exception code when trying to read an

analog value?
There are several reasons why an exception code is received when requesting an analog value:
The point from which an analog value is being requested is not a 420 mA Analog Input Module.
At least one of the points in the group of points from which an analog value is being requested is not a
420 mA Analog Input Module.
More than 10 analog values have been requested in a single request.
6.8 Why do I get all zeros when I read an analog value?

There are several reasons a zero reading from an FMM-420 Analog Input Module is received:
The first read for an analog value from the gateway initializes the polling routine in the gateway to
retrieve analog values from the NFN network. The first response will usually be all zeros. This is
normal. The subsequent polls of an analog value for the same point or group of points will return actual
values. As long as the same points continue to be polled at a rate faster than the Analog Poll Time Out,
then the gateway will continue to poll the same points.
The gateway does not actually take an analog value reading unless the module has reached the first
threshold and therefore it will return a zero reading.
If the client polls the gateway too quickly after the initialization poll then the gateway may still return
zeros.
If the client polls the analog values slower than the Analog Poll Time Out, then the gateway may return
all zeros.
6.9 What is the Analog Value Polling Time Out?

This is how long a gateway will continue to poll analog points after the last client read request of the points.
As long as the client makes analog reads of the same points faster than the Analog Value Polling Time then
the gateway will continue to poll these points. If the client polls slower than the Analog Value Polling Time
then the gateway may return readings of zero because this will be considered an initialization read.
6.10 System Trouble

For information about system trouble information stored in holding registers, please refer to Section 5.9,
Panel and System Troubles Input Registers, on page 39.
44
Appendix A: Gateway Settings

NOTE: The procedures in this Appendix require the use of a USB flash memory drive.
A.1 Viewing Existing IP Settings

1. Connect the flash drive to the MODBUS-GW.
2. Reboot the gateway.
A file is created that matches the configured IP address of the gateway, followed by the extension
.txt (e.g., 192.168.1.2.txt). If the file already exists on the drive, it will be altered to match the
Gateway configuration. The file contains additional information such as the MAC address of the
gateway.
3. Connect the drive to a PC and view the files.
The flash drive should contain a file that matches the configured IP address of the gateway,
followed by the extension .txt (e.g., 192.168.1.2.txt). If the file already exists on the drive, it has
been altered to match the gateway configuration. The file contains additional information such as
the MAC address of the gateway.
A.2 Resetting Factory Default Values

1. Connect the flash drive to a PC and create a file named default.ldc. The contents of the file is not
significant; however, ensure that the file does not have an additional hidden file extension. This file
will be automatically deleted from the flash drive by the gateway.
2. Eject the flash drive from the PC.
3. Disconnect power from the gateway.
4. Disconnect the communication cable to the Gateway USB port (if present) and connect the flash
drive.
5. Reconnect the 24 VDC power supply to the gateway.
6. After approximately one minute, disconnect the flash drive from the USB port and (if necessary)
reconnect the cable removed in Step 4.
7. Connect the flash drive to the PC and verify that the file named 192.168.12.txt is on the drive.
If the file is on the flash drive, the reset has been accomplished.
If the file is not on the flash drive:

The flash drive may not have been connected during the reboot period or was removed early.
The flash drive is not seen as a valid drive by the hardware.
A software error has occurred and technical support may need to be contacted.
45
46
Appendix B: Exception Responses

If a Modbus master device sends an invalid command or attempts to read an invalid holding register, an
exception response is generated. The exception response follows the standard packet format. The high order
bit of the function code in an exception response is 1. The data field of an exception response contains the
exception error code. Table B.1, Exception Codes describes the exception codes supported and the
possible causes.
Table B.1 Exception Codes
Exception Code
Conditions
Exception Name
0x01
Protocol Identifier in Modbus packet does not match

Modbus protocol. Protocol Identifier in Modbus should
always be 0.
Function code sent by the client is not supported by the
MODBUS-GW or the FACP.
A Control command was sent to the gateway. Please
contact customer service.
Illegal function
0x02
Register address range specified by the client is not

supported by the FACP.
Register address range requested is valid but the
device (e.g. Detector, Module, Zone, etc.) is not present
in the specified FACP.
Analog Value is requested from a register which is not
associated with a 420 mA device.
Illegal data address
0x03
Number of registers requested exceeds the maximum

allowed limit. The maximum number of registers that a
client can read at one time is 100. The exception to this
is for analog values where the maximum number of
registers a client can read at one time is 10.
Invalid Data written to the register when sending
commands.
Illegal data value
0x0A
Unit ID specified in the request packet is not configured

for monitoring.
Gateway path failed
0x0B
FACP is off line or there is a communication problem on

the panel and/or NFN.
Gateway target failed
47
Exception Responses
48
Appendix C: MODBUS-GW Active Event Types

All NFN events are mapped into Modbus event categories which are stored in the Modbus register. Events
are mapped as shown in Table C.1, Event Type Categories.
Table C.1 Event Type Categories
Event
Modbus Register Value
No Active Status (see note)
00H
Mass Notification Alarm, High Priority
05H
Fire Alarm
10H
Security Alarm (Life)
11H
Critical Process Alarm (Life)
12H
Medical Emergency (Life)
13H
CO Alarm
14H
Mass Notification Alarm, Low Priority
15H
Security Alarm (Property)
20H
Critical Process (Property)
21H
Mass Notification Supervisory, High Priority
25H
Supervisory Signal (Guards Tour)
30H
Supervisory Signal (Equipment)
40H
Mass Notification Supervisory, Low Priority
45H
Disabled Alarm
52H
Disabled Active
55H
Non-Fire Activation
71H
Non-Fire Activation (no acknowledgment required)
72H
CO Alarm & Fire Alarm
EAH
CO Supervisory
EBH
CO Supervisory & Photo Supervisory
ECH
CO Supervisory & Fire Alarm
EDH
CO Alarm & Photo Supervisory
EEH
Device Not Present
0xFFH
NOTES:
Multiple states are possible for a device. For example, a device connected to a Fire Alarm
Control Panel may be both Active and Disabled. Also, a device may be in the Trouble and
Fire Alarm states at one time.
No Active Status does not indicate the point/device is in a normal state. The holding register
for the point or device contains more detail. For more information, refer to Section 5,
Register Mapping, on page 33.
49
MODBUS-GW Active Event Types
50
Appendix D: Device Types

Device types are organized into the following categories:
Detectors (150) Appendix D.1
Monitor Modules (51150) Appendix D.2
Control Modules (151250) Appendix D.3

Table D.1 Device Type Values Detectors
DEVICE TYPE
Value
HEAT DETECTOR
ION DETECTOR
PHOTO DETECTOR
LASER DETECTOR
OMNI DETECTOR
PHOTO DETECTOR
ASPIRATION
51
Device Types
Table D.2 Device Type Values Monitor Modules

DEVICE TYPE
52
Value
DEVICE TYPE
Value
MONITOR MODULE
51
MEDIC ALERT
79
HEAT DETECT
52
NON FIRE
80
MONITOR
53
PAS INHIBIT
81
PULL STATION
54
POWER MONITR
82
RF MON MODUL
55
PROCESS MON
83
RF PULL STA
56
PROCESS AUTO
84
SMOKE CONVEN
57
RESET SWITCH
85
SMOKE DETECT
58
SIL SWITCH
86
WATERFLOW
59
TELE PAGE
87
WATERFLOW S
60
TORNADO ALRT
88
ACCESS MONTR
61
TROUBLE MON
89
AREA MONITOR
62
ABORT SWITCH
90
AUDIO SYSTEM
63
MAN RELEASE
91
EQUIP MONITR
64
MANREL DELAY
92
HOLD UP
65
SECOND SHOT
93
RF SUPERVSRY
66
SECURITY T
94
SECURITY L
67
NC MONITOR
95
LATCH SUPERV
68
NC SUP T
96
TRACK SUPERV
69
NC SUP L
97
SPRINKLR SYS
70
NC NON FIRE
98
SYS MONITOR
71
SECURE/ACCESS
99
TAMPER
72
DISABLE MON
100
ACK SWITCH
73
4-20mA
101
ALLCALL PAGE
74
CO MONITOR MOBILE
102
DRILL SWITCH
75
MASS NOTIFICATION TRACKING

SUPERVISORY
103
EVACUATE SW
76
MASS NOTIFICATION LATCHING

SUPERVISORY
104
FIRE CONTROL
77
MASS NOTIFICATION TROUBLE MON
105
HAZARD ALERT
78
MASS NOTIFICATION MONITOR
106
Device Types
Table D.3 Device Type Values Control Modules

DEVICE TYPE
Value
DEVICE TYPE
Value
CONTROL
151
ALARMS PEND
168
RELAY
152
CONTROL NAC
169
BELL CIRCUIT
153
GEN ALARM
170
STROBE CKT
154
GEN SUPERVIS
171
HORN CIRCUIT
155
GEN TROUBLE
172
AUDIBLE CKT
156
GENERAL PEND
173
SPEAKER
157
TROUBLE PEND
174
REL END BELL
158
FORM C RESET
175
(blank)
159
ISOLATED SPK
176
RELEASE CKT
160
ISOLATED NAC
177
REL CKT ULC
161
RELAY FDBACK
178
RELEA.FORM C
162
REL FORM C FB
179
REL AUDIBLE
163
MASS NOTIFICATION GENERAL
180
NONRESET CTL
164
MASS NOTIFICATION CONTROL
181
TELEPHONE
165
MASS NOTIFICATION STROBE
182
REL CODE BELL
166
MASS NOTIFICATION SPEAKER
183
INSTANT RELE
167
MASS NOTIFICATION RELAY
184
53
Device Types
54
Appendix E: System Troubles

Table E.1 System Troubles Register Map
Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35001
GROUND FAULT
INTERNAL RAM ERROR
AC FAIL
EXTERNAL RAM ERROR
BATTERY
10
PROGRAM CORRUPTED
STYLE 6 POS. LOOP 1
11
NO DEV. INST ON L1
STYLE 6 POS. LOOP 2
12
PANEL DOOR OPEN
CORRUPT LOGIC EQUAT
13
AUXILIARY TROUBLE
LCD80 SUPERVISORY
14
TERM. SUPERVISORY
EPROM ERROR
15
ANNUN. 1 TROUBLE
ANNUN. 1 NO ANSWER
ANNUN. 5 NO ANSWER
ANNUN. 2 TROUBLE
ANNUN. 6 TROUBLE
ANNUN. 2 NO ANSWER
10
ANNUN. 6 NO ANSWER
ANNUN. 3 TROUBLE
11
ANNUN. 7 TROUBLE
ANNUN. 3 NO ANSWER
12
ANNUN. 7 NO ANSWER
ANNUN. 4 TROUBLE
13
ANNUN. 8 TROUBLE
ANNUN. 4 NO ANSWER
14
ANNUN. 8 NO ANSWER
ANNUN. 5 TROUBLE
15
ANNUN. 9 TROUBLE
ANNUN. 9 NO ANSWER
ANNUN.13 NO ANSWER
ANNUN.10 TROUBLE
ANNUN.14 TROUBLE
ANNUN.10 NO ANSWER
10
ANNUN.14 NO ANSWER
ANNUN.11 TROUBLE
11
ANNUN.15 TROUBLE
ANNUN.11 NO ANSWER
12
ANNUN.15 NO ANSWER
ANNUN.12 TROUBLE
13
ANNUN.16 TROUBLE
ANNUN.12 NO ANSWER
14
ANNUN.16 NO ANSWER
ANNUN.13 TROUBLE
15
ANNUN.17 TROUBLE
35002
35003
55
System Troubles
Table E.1 System Troubles Register Map (Continued)

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35004
ANNUN.17 NO ANSWER
ANNUN.21 NO ANSWER
ANNUN.18 TROUBLE
ANNUN.22 TROUBLE
ANNUN.18 NO ANSWER
10
ANNUN.22 NO ANSWER
ANNUN.19 TROUBLE
11
ANNUN.23 TROUBLE
ANNUN.19 NO ANSWER
12
ANNUN.23 NO ANSWER
ANNUN.20 TROUBLE
13
ANNUN.24 TROUBLE
ANNUN.20 NO ANSWER
14
ANNUN.24 NO ANSWER
ANNUN.21 TROUBLE
15
ANNUN.25 TROUBLE
ANNUN.25 NO ANSWER
ANNUN.29 NO ANSWER
ANNUN.26 TROUBLE
ANNUN.30 TROUBLE
ANNUN.26 NO ANSWER
10
ANNUN.30 NO ANSWER
ANNUN.27 TROUBLE
11
ANNUN.31 TROUBLE
ANNUN.27 NO ANSWER
12
ANNUN.31 NO ANSWER
ANNUN.28 TROUBLE
13
ANNUN.32 TROUBLE
ANNUN.28 NO ANSWER
14
ANNUN.32 NO ANSWER
ANNUN.29 TROUBLE
15
NETWORK FAIL PORT A
NETWORK FAIL PORT B
UDACT TROUBLE
NETWORK FAILURE
UDACT NO ANSWER
ADV WALK TEST
10
PROG MODE ACTIVATED
CHARGER FAIL
11
LOADING NO SERVICE
GROUND FAULT LOOP 2
12
BASIC WALK TEST
STYLE 6 NEG. LOOP 1
13
NFPA 24HR REMINDER
STYLE 6 NEG. LOOP 2
14
NVRAM BATT TROUBLE
GROUND FAULT LOOP 1
15
(reserved)
35005
35006
56
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35007
Reserved
OPTION MODULE
Reserved
STYLE 6 ON LOOP 3
Reserved
10
AVPS. TROUBLE
Reserved
11
NAM CCBE PROG. LOST
Reserved
12
MAN. EVAC INITIATED
Reserved
13
MAN. EVAC RECEIVED
Reserved
14
(reserved)
Reserved
15
(reserved)
ANNUN.33 TROUBLE
ANNUN.37 TROUBLE
ANNUN.33 NO ANSWER
ANNUN.37 NO ANSWER
ANNUN.34 TROUBLE
10
ANNUN.38 TROUBLE
ANNUN.34 NO ANSWER
11
ANNUN.38 NO ANSWER
ANNUN.35 TROUBLE
12
ANNUN.39 TROUBLE
ANNUN.35 NO ANSWER
13
ANNUN.39 NO ANSWER
ANNUN.36 TROUBLE
14
ANNUN.40 TROUBLE
ANNUN.36 NO ANSWER
15
ANNUN.40 NO ANSWER
ANNUN.41 TROUBLE
ANNUN.45 TROUBLE
ANNUN.41 NO ANSWER
ANNUN.45 NO ANSWER
ANNUN.42 TROUBLE
10
ANNUN.46 TROUBLE
ANNUN.42 NO ANSWER
11
ANNUN.46 NO ANSWER
ANNUN.43 TROUBLE
12
ANNUN.47 TROUBLE
ANNUN.43 NO ANSWER
13
ANNUN.47 NO ANSWER
ANNUN.44 TROUBLE
14
ANNUN.48 TROUBLE
ANNUN.44 NO ANSWER
15
ANNUN.48 NO ANSWER
35008
35009
57
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35010
ANNUN.49 TROUBLE
ANNUN.53 TROUBLE
ANNUN.49 NO ANSWER
ANNUN.53 NO ANSWER
ANNUN.50 TROUBLE
10
ANNUN.54 TROUBLE
ANNUN.50 NO ANSWER
11
ANNUN.54 NO ANSWER
ANNUN.51 TROUBLE
12
ANNUN.55 TROUBLE
ANNUN.51 NO ANSWER
13
ANNUN.55 NO ANSWER
ANNUN.52 TROUBLE
14
ANNUN.56 TROUBLE
ANNUN.52 NO ANSWER
15
ANNUN.56 NO ANSWER
ANNUN.57 TROUBLE
ANNUN.61 TROUBLE
ANNUN.57 NO ANSWER
ANNUN.61 NO ANSWER
ANNUN.58 TROUBLE
10
ANNUN.62 TROUBLE
ANNUN.58 NO ANSWER
11
ANNUN.62 NO ANSWER
ANNUN.59 TROUBLE
12
ANNUN.63 TROUBLE
ANNUN.59 NO ANSWER
13
ANNUN.63 NO ANSWER
ANNUN.60 TROUBLE
14
ANNUN.64 TROUBLE
ANNUN.60 NO ANSWER
15
ANNUN.64 NO ANSWER
GROUND FAULT LOOP 3
STYLE 6 NEG. LOOP 3
GROUND FAULT LOOP 4
STYLE 6 NEG. LOOP 4
GROUND FAULT LOOP 5
10
STYLE 6 NEG. LOOP 5
GROUND FAULT LOOP 6
11
STYLE 6 NEG. LOOP 6
GROUND FAULT LOOP 7
12
STYLE 6 NEG. LOOP 7
GROUND FAULT LOOP 8
13
STYLE 6 NEG. LOOP 8
GROUND FAULT LOOP 9
14
STYLE 6 NEG. LOOP 9
GROUND FAULT LOOP 10
15
STYLE 6 NEG. LOOP 10
35011
35012
58
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35013
STYLE 6 POS. LOOP 3
PRINTER SUPERVISORY
STYLE 6 POS. LOOP 4
BUZZER SUPERVISORY
STYLE 6 POS. LOOP 5
10
CRT SUPERVISORY
STYLE 6 POS. LOOP 6
11
PRINT QUEUE FULL
STYLE 6 POS. LOOP 7
12
MEMORY LOSS
STYLE 6 POS. LOOP 8
13
PRINTER COVER OPEN
STYLE 6 POS. LOOP 9
14
PRINTER PAPER OUT
STYLE 6 POS. LOOP 10
15
PRINTER OFF LINE
Workstation Fan Failure
STYLE 4 SHORT A LOOP 3
UPS Failure
STYLE 4 SHORT B LOOP 3
MANUAL MODE ENTERED
10
NCM COMM LOSS
11
12
13
14
15
GENERAL PS FAULT
STYLE 6 SHORT LOOP 1
10
11
12
13
14
15
35014
35015
59
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35016
TM4 NO ANSWER
TM4 DISABLED
10
SELF TEST FAILED
NODE xxx
COMMUNICATIONS
FAILURE
11
NETWORK
INCOMPATIBILITY
NCM PIEZO BATTERY

FAILURE
12
Not Used
DVC COMM LOSS
13
Not Used
POWER SUPPLY CABLE

NOT CONNECTED
14
Not Used
TM4 TROUBLE
15
Not Used
ANNUN. 65 TROUBLE
ANNUN. 69 TROUBLE
ANNUN. 65 NO ANSWER
ANNUN. 69 NO ANSWER
ANNUN. 66 TROUBLE
10
ANNUN. 70 TROUBLE
ANNUN. 66 NO ANSWER
11
ANNUN. 70 NO ANSWER
ANNUN. 67 TROUBLE
12
ANNUN. 71 TROUBLE
ANNUN. 67 NO ANSWER
13
ANNUN. 71 NO ANSWER
ANNUN. 68 TROUBLE
14
ANNUN. 72 TROUBLE
ANNUN. 68 NO ANSWER
15
ANNUN. 72 NO ANSWER
ANNUN. 73 TROUBLE
ANNUN. 77 TROUBLE
ANNUN. 73 NO ANSWER
ANNUN. 77 NO ANSWER
ANNUN. 74 TROUBLE
10
ANNUN. 78 TROUBLE
ANNUN. 74 NO ANSWER
11
ANNUN. 78 NO ANSWER
ANNUN. 75 TROUBLE
12
ANNUN. 79 TROUBLE
ANNUN. 75 NO ANSWER
13
ANNUN. 79 NO ANSWER
ANNUN. 76 TROUBLE
14
ANNUN. 80 TROUBLE
ANNUN. 76 NO ANSWER
15
ANNUN. 80 NO ANSWER
35017
35018
60
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35019
ANNUN. 81 TROUBLE
ANNUN. 85 TROUBLE
ANNUN. 81 NO ANSWER
ANNUN. 85 NO ANSWER
ANNUN. 82 TROUBLE
10
ANNUN. 86 TROUBLE
ANNUN. 82 NO ANSWER
11
ANNUN. 86 NO ANSWER
ANNUN. 83 TROUBLE
12
ANNUN. 87 TROUBLE
ANNUN. 83 NO ANSWER
13
ANNUN. 87 NO ANSWER
ANNUN. 84 TROUBLE
14
ANNUN. 88 TROUBLE
ANNUN. 84 NO ANSWER
15
ANNUN. 88 NO ANSWER
ANNUN. 89 TROUBLE
ANNUN. 93 TROUBLE
ANNUN. 89 NO ANSWER
ANNUN. 93 NO ANSWER
ANNUN. 90 TROUBLE
10
ANNUN. 94 TROUBLE
ANNUN. 90 NO ANSWER
11
ANNUN. 94 NO ANSWER
ANNUN. 91 TROUBLE
12
ANNUN. 95 TROUBLE
ANNUN. 91 NO ANSWER
13
ANNUN. 95 NO ANSWER
ANNUN. 92 TROUBLE
14
ANNUN. 96 TROUBLE
ANNUN. 92 NO ANSWER
15
ANNUN. 96 NO ANSWER
ANNUN. 97 TROUBLE
ANNUN. 101 TROUBLE
ANNUN. 97 NO ANSWER
ANNUN. 101 NO ANSWER
ANNUN. 98 TROUBLE
10
ANNUN. 102 TROUBLE
ANNUN. 98 NO ANSWER
11
ANNUN. 99 TROUBLE
12
ANNUN. 103 TROUBLE
ANNUN. 99 NO ANSWER
13
ANNUN. 100 TROUBLE
14
ANNUN. 104 TROUBLE
15
35020
35021
61
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35022
ANNUN. 105 TROUBLE
ANNUN. 109 TROUBLE
ANNUN. 106 TROUBLE
10
ANNUN. 110 TROUBLE
11
ANNUN. 107 TROUBLE
12
ANNUN. 111 TROUBLE
13
ANNUN. 108 TROUBLE
14
ANNUN. 112 TROUBLE
15
ANNUN. 113 TROUBLE
ANNUN. 117 TROUBLE
ANNUN. 114 TROUBLE
10
ANNUN. 118 TROUBLE
11
ANNUN. 115 TROUBLE
12
ANNUN. 119 TROUBLE
13
ANNUN. 116 TROUBLE
14
ANNUN. 120 TROUBLE
15
ANNUN. 121 TROUBLE
ANNUN. 125 TROUBLE
ANNUN. 122 TROUBLE
10
ANNUN. 126 TROUBLE
11
ANNUN. 123 TROUBLE
12
ANNUN. 127 TROUBLE
13
ANNUN. 124 TROUBLE
14
ANNUN. 128 TROUBLE
15
35023
35024
62
System Troubles

Register
35025
35026
Bit Number
System Trouble Name
Bit Number
System Trouble Name
REMOTE DISPLAY 1
TROUBLE
REMOTE DISPLAY 5
TROUBLE
REMOTE DISPLAY 1 NO
ANSWER
REMOTE DISPLAY 5 NO
ANSWER
REMOTE DISPLAY 2
TROUBLE
10
REMOTE DISPLAY 6
TROUBLE
REMOTE DISPLAY 2 NO
ANSWER
11
REMOTE DISPLAY 6 NO
ANSWER
REMOTE DISPLAY 3
TROUBLE
12
REMOTE DISPLAY 7
TROUBLE
REMOTE DISPLAY 3 NO
ANSWER
13
REMOTE DISPLAY 7 NO
ANSWER
REMOTE DISPLAY 4
TROUBLE
14
REMOTE DISPLAY 8
TROUBLE
REMOTE DISPLAY 4 NO
ANSWER
15
REMOTE DISPLAY 8 NO
ANSWER
REMOTE DISPLAY 9
TROUBLE
REMOTE DISPLAY 13
TROUBLE
REMOTE DISPLAY 9 NO
ANSWER
REMOTE DISPLAY 13 NO
ANSWER
REMOTE DISPLAY 10
TROUBLE
10
REMOTE DISPLAY 14
TROUBLE
ANSWER
11
ANSWER
REMOTE DISPLAY 11
TROUBLE
12
REMOTE DISPLAY 15
TROUBLE
ANSWER
13
ANSWER
REMOTE DISPLAY 12
TROUBLE
14
REMOTE DISPLAY 16
TROUBLE
ANSWER
15
ANSWER
63
System Troubles

Register
35027
35028
64
Bit Number
System Trouble Name
Bit Number
System Trouble Name
REMOTE DISPLAY 17
TROUBLE
REMOTE DISPLAY 21
TROUBLE
ANSWER
ANSWER
REMOTE DISPLAY 18
TROUBLE
10
REMOTE DISPLAY 22
TROUBLE
ANSWER
11
ANSWER
REMOTE DISPLAY 19
TROUBLE
12
REMOTE DISPLAY 23
TROUBLE
ANSWER
13
ANSWER
REMOTE DISPLAY 20
TROUBLE
14
REMOTE DISPLAY 24
TROUBLE
ANSWER
15
ANSWER
REMOTE DISPLAY 25
TROUBLE
REMOTE DISPLAY 29
TROUBLE
ANSWER
ANSWER
REMOTE DISPLAY 26
TROUBLE
10
REMOTE DISPLAY 30
TROUBLE
ANSWER
11
ANSWER
REMOTE DISPLAY 27
TROUBLE
12
REMOTE DISPLAY 31
TROUBLE
ANSWER
13
ANSWER
REMOTE DISPLAY 28
TROUBLE
14
REMOTE DISPLAY 32
TROUBLE
ANSWER
15
ANSWER
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35029
SYSTEM INITIALIZATION
Reserved
POWER SUPPLY COMM

FAILURE
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
35030
35031
65
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35032
Reserved
NO POWER SUPPLY INST
Reserved
LOOP 1-2 COMM FAILURE
LINK PROTECTOR PRIMARY

STATUS
10
LINK PROTECTOR
SECONDARY STATUS
11
LINK PROTECTOR NOT

PRESENT
12
EVENT BUFFER 80% FULL
13
EBI STATUS
14
TEST PROGRAM UPDATE
SOFTWARE MISMATCH
15
HISTORY 80% FULL
LOOP CONTINUITY TEST

FAIL LOOP 1

FAIL LOOP 9

FAIL LOOP 2

FAIL LOOP 10

FAIL LOOP 3
10
UNPROGRAMMED DEVICE
ON LOOP 1

FAIL LOOP 4
11
UNPROGRAMMED DEVICE
ON LOOP 2

FAIL LOOP 5
12
UNPROGRAMMED DEVICE
ON LOOP 3

FAIL LOOP 6
13
UNPROGRAMMED DEVICE
ON LOOP 4

FAIL LOOP 7
14
UNPROGRAMMED DEVICE
ON LOOP 5

FAIL LOOP 8
15
UNPROGRAMMED DEVICE
ON LOOP 6
35033
66
System Troubles

Register
35034
Bit Number
System Trouble Name
Bit Number
System Trouble Name
UNPROGRAMMED DEVICE
ON LOOP 7
IR ENABLED ON LOOP 5
UNPROGRAMMED DEVICE
ON LOOP 8
UNPROGRAMMED DEVICE
ON LOOP 9
10
UNPROGRAMMED DEVICE
ON LOOP 10
11
12
13
14
TRANSMIT/RECIEVE
ERROR ABOVE LIMIT ON
LOOP 1
15
TRANSMIT/RECIEVE
LOOP 2
TRANSMIT/RECIEVE
LOOP 3
TOO MANY DEVICES ON

LOOP 1
TRANSMIT/RECIEVE
LOOP 4
TOO MANY DEVICES ON

LOOP 2
TRANSMIT/RECIEVE
LOOP 5
10
TOO MANY DEVICES ON

LOOP 3
TRANSMIT/RECIEVE
LOOP 6
11
TOO MANY DEVICES ON

LOOP 4
TRANSMIT/RECIEVE
LOOP 7
12
TOO MANY DEVICES ON

LOOP 5
TRANSMIT/RECIEVE
LOOP 8
13
TOO MANY DEVICES ON

LOOP 6
TRANSMIT/RECIEVE
LOOP 9
14
TOO MANY DEVICES ON

LOOP 7
TRANSMIT/RECIEVE
LOOP 10
15
TOO MANY DEVICES ON

LOOP 8
35035
67
System Troubles

Register
35036
35037
68
Bit Number
System Trouble Name
Bit Number
System Trouble Name
TOO MANY DEVICES ON

LOOP 9
MISMATCHED LOOP TYPE

ON LOOP 7
TOO MANY DEVICES ON

LOOP 10

ON LOOP 8

ON LOOP 1
10

ON LOOP 9

ON LOOP 2
11

ON LOOP 10

ON LOOP 3
12
Ground Fault Port A

ON LOOP 4
13
Ground Fault Port B

ON LOOP 5
14
Amplifier Trouble

ON LOOP 6
15
AUXIN Trouble
DIGIN Trouble
ANALOG OUTPUT A
TROUBLE
FFT TROUBLE
ANALOG OUTPUT B
TROUBLE
REMOTE MIC Trouble
10
ANALOG OUTPUT C
TROUBLE
DAP Port A Failure
11
ANALOG OUTPUT D
TROUBLE
DAP Port B Failure
12
FLASH IMAGE ERROR
DAL No Answer
13
POWER SUPPLY TROUBLE
LOCAL MIC TROUBLE
14
AMPLIFIER LIMIT
LOCAL PHONE TROUBLE
15
AMPLIFIER SUPERVISION
System Troubles

Register
35038
35039
Bit Number
System Trouble Name
Bit Number
System Trouble Name
DAL ADDRESS CONFLICT
MAPPING IN PROGRESS
LOOP 7
DEVICE SERVICING
REQUIRED
MAPPING IN PROGRESS
LOOP 8
MAPPING IN PROGRESS
LOOP 1
10
MAPPING IN PROGRESS
LOOP 9
MAPPING IN PROGRESS
LOOP 2
11
MAPPING IN PROGRESS
LOOP 10
MAPPING IN PROGRESS
LOOP 3
12
DATABASE CORRUPTED
MAPPING IN PROGRESS
LOOP 4
13
AUDIO LIBRARY
CORRUPTED
MAPPING IN PROGRESS
LOOP 5
14
DATABASE INCOMPATIBLE
MAPPING IN PROGRESS
LOOP 6
15
AUDIO LIBRARY
INCOMPATIBLE
DAL DOWNLOAD IN
PROGRESS
PRIMARY AMP 1 TROUBLE
FIRE VOICE TROUBLE
FIRE VOICE NO ANSWER
10
PHONE CHANNEL LIMIT

EXCEEDED
11
NCM SMIFFER MODE

ACTIVE
12
BACKUP AMP 1 TROUBLE
LOCAL CONNECTION LIMIT

EXCEEDED
13
HARDWARE MISMATCH
14
DAL DEVICE NO ANSWER
15
69
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35040
DSBUS 1 COMMFAIL
Reserved
DSBUS 2 COMMFAIL
Reserved
DSBUS 3 COMMFAIL
10
Reserved
DSBUS 4 COMMFAIL
11
Reserved
AA TROUBLE BUS FAIL
12
Reserved
NFN PAGING CHANNEL

LIMIT EXCEEDED
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
35041
35042
70
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35043
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
35044
35045
71
System Troubles

Register
Bit Number
System Trouble Name
Bit Number
System Trouble Name
35046
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
10
Reserved
Reserved
11
Reserved
Reserved
12
Reserved
Reserved
13
Reserved
Reserved
14
Reserved
Reserved
15
Reserved
35047
35048
72
Appendix F: Moxa MGate MB3180 Interface

Modbus Gateway (acting as a Modbus slave) interfaces with a Modbus master through Modbus TCP
protocol. The Moxa MGate MB3180 can be used to convert Modbus TCP protocol to Modbus RTU (Serial)
protocol so that a Modbus RTU master can interface with Modbus Gateway.
CAUTION: Slave ID Range

The MGate MB3180 monitors devices with virtual slave IDs in the range 199. By default, Modbus
Gateway assigns each node on the NFN network a Modbus Unit ID equal to its node number. (The
MGate MB3180 accepts the Modbus Unit ID as a virtual slave ID.) These numbers can be changed
to fall within the range 199, but no more than 99 devices can be monitored. For more information
about changing Modbus Unit IDs, refer to 3.3.5, "Additional Properties",Gateway Unit ID.
F.1 Hardware Configuration

Refer to the Moxa MGate MB3180 Quick Installation Guide for hardware configuration of the MB3180.
F.2 Moxa MGate MB3180 Interface with Modbus Gateway

NOTE: The configuration used must have the approval of the AHJ (Authority Having Jurisdiction).
These illustrations show possible configurations for connecting Modbus Gateway to the Moxa MGate
MB3180 interface.
Modbus RTU
Master
Serial cable
Modbus
Gateway
HS-NCM-W/SF/MF
NFN
Network
USB
Cross Over
Ethernet cable
MB3180
FACP
FACP
FACP
Figure F.1 Example System: Connect Through Cross Over Ethernet Cable
73
Moxa MGate MB3180 Interface
Software Configuration
Modbus RTU
Master
Serial cable
HS-NCM-W/SF/MF
Modbus
Gateway
NFN
Network
USB
Ethernet
cable
Ethernet
cable
Router
MB3180
FACP
FACP
FACP
Figure F.2 Example System: Connect Through Router
F.3 Software Configuration

Configure Modbus Gateway as a node in the NFN network with a node number. Make sure the NFN
network is stable. For details about configuration, consult the NOTIFIRENET Network Systems
Interface Manual (P/N 51584) or High Speed NOTIFIRENET Instruction Manual, (P/N 54013).
1.
Connect MB3180 to a configuration computer through an Ethernet cable to configure the device.
Ethernet cable
Configuration
computer
MB3180
Figure F.3 Connect a Configuration Computer

2.
Run the MGate Manager installation software (MGM_Setup_Verx.x_Build_xxxxxxxx.exe), found on the

Software CD shipped with the Moxa MGate MB3180.
3.
Once the software has been installed, run MGate Manager:

From the Windows task bar, click Start Programs MGate Manager MGate Manager.The
Moxa MGate Manager program launches.
74
Figure F.4 Moxa MGate Manager

4.
Click Broadcast Search to automatically detect the Moxa MGate MB3180 attached to the
configuration computer.
NOTE: Make sure the MB3180 is powered on and that the Ready and Ethernet lights are illuminated.
The MGate Manager software searches for the MB3180.
Figure F.5 Moxa MGate Manager: Broadcast Search
75
Once located, the MB3180 appears in the device table and new MGate Manager Program options
become available.
Figure F.6 Moxa MGate Manager: Configuration

5.
76
Click the MB3180 in the device field to highlight it, and then click Configuration. The Configuration
dialogue opens with the Mode tab visible. Use the instructions on the following pages to configure the
MB3180, clicking the tab names to navigate among the tabs.
F.3.1 Mode Tab
Figure F.7 Moxa MGate Manager Configuration Software: Mode Tab

1.
From the Mode tab, click RTU master.
77
F.3.2 Network Tab
Figure F.8 Moxa MGate Manager Configuration Software: Network Tab

1.
From the Network tab, set up an IP address scheme for the MB3180 to use, either static or assigned
through DHCP.
To assign a static IP address, select Static from the Network Configure drop down menu. Then, fill in
the IP address information in the appropriate fields.
To have DHCP assign an IP address, select DHCP from the Network Configure drop down menu.
78
F.3.3 Serial Tab
Figure F.9 Moxa MGate Manager Configuration Software: Serial Tab

1.
Set up the serial port configuration based on the settings for your RTU master.
79
F.3.4 Slave ID Map Tab
Figure F.10 Moxa MGate Manager Configuration Software: Slave ID Map Tab
1.
Type the Modbus Gateway IP address in the Remote TCP Slave IP field.
80
CAUTION: Slave ID Range

The MGate MB3180 monitors devices with virtual slave IDs in the range 199. By default, Modbus
Gateway assigns each node on the NFN network a Modbus Unit ID equal to its node number. (The
MGate MB3180 accepts the Modbus Unit ID as a virtual slave ID.) These numbers can be changed to
fall within the range 199, but no more than 99 devices can be monitored. For more information about
changing Modbus Unit IDs, refer to 3.3.5, "Additional Properties",Gateway Unit ID.
2.
Click Add/Modify to add the Modbus Gateway to the Slaves Channels Information list.
3.
In the fields below Virtual Slaves ID Range, type the range of NFN node numbers of the devices which
the Modbus Gateway is monitoring.
4.
Click Set.
Using The Moxa MGate MB3180
F.3.5 Modbus Tab
Figure F.11 Moxa MGate Manager Configuration Software: Modbus Tab

1.
Type 0 (zero) in the field beside Initial Delay.
2.
Type 1000 in the field beside Response.
(These values are typical and tested.)

3.
Click OK.
This saves the configuration information to the MB3180.

4.
Click Exit to exit the MGate Manager.
F.4 Using The Moxa MGate MB3180

Connect the RTU master to the Serial port (RS232, RS485, RS422) of the MGate MB3180. For illustrations,
refer to Moxa MGate MB3180 Interface with Modbus Gateway on page 73.
The Modbus Gateway is now able to handle requests sent from the Modbus RTU master through the Moxa
MGate MB3180.
81
82
Using The Moxa MGate MB3180
Manufacturer Warranties and Limitation of Liability

Manufacturer Warranties. Subject to the limitations set forth
herein, Manufacturer warrants that the Products manufactured by it
in its Northford, Connecticut facility and sold by it to its authorized
Distributors shall be free, under normal use and service, from
defects in material and workmanship for a period of thirty six
months (36) months from the date of manufacture (effective Jan. 1,
2009). The Products manufactured and sold by Manufacturer are
date stamped at the time of production. Manufacturer does not
warrant Products that are not manufactured by it in its Northford,
Connecticut facility but assigns to its Distributor, to the extent
possible, any warranty offered by the manufacturer of such
product. This warranty shall be void if a Product is altered,
serviced or repaired by anyone other than Manufacturer or its
authorized Distributors. This warranty shall also be void if there is
a failure to maintain the Products and the systems in which they
operate in proper working conditions.
MANUFACTURER MAKES NO FURTHER WARRANTIES, AND
DISCLAIMS ANY AND ALL OTHER WARRANTIES, EITHER
EXPRESSED OR IMPLIED, WITH RESPECT TO THE
PRODUCTS, TRADEMARKS, PROGRAMS AND SERVICES
RENDERED BY MANUFACTURER INCLUDING WITHOUT
LIMITATION, INFRINGEMENT, TITLE, MERCHANTABILITY, OR
FITNESS
FOR
ANY
PARTICULAR
PURPOSE.
MANUFACTURER 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 USES OF ITS PRODUCTS.
This document constitutes the only warranty made by
Manufacturer with respect to its products and replaces all previous
warranties and is the only warranty made by Manufacturer. No
increase or alteration, written or verbal, of the obligation of this
warranty is authorized. Manufacturer does not represent that its
products will prevent any loss by fire or otherwise.
Warranty Claims. Manufacturer shall replace or repair, at
Manufacturer's discretion, each part returned by its authorized
Distributor and acknowledged by Manufacturer to be defective,
provided that such part shall have been returned to Manufacturer
with all charges prepaid and the authorized Distributor has
completed Manufacturer's Return Material Authorization form. The
replacement part shall come from Manufacturer's stock and may
be new or refurbished. THE FOREGOING IS DISTRIBUTOR'S
SOLE AND EXCLUSIVE REMEDY IN THE EVENT OF A
WARRANTY CLAIM.
Warn-HL-08-2009.fm
83
World Headquarters
12 Clintonville Road
Northford, CT 06472-1610 USA
203-484-7161
fax 203-484-7118
www.notifier.com

Unlock-Modbus Gateway IOM B2

Uploaded by

Copyright:

Available Formats

Unlock-Modbus Gateway IOM B2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unlock-Modbus Gateway IOM B2

Uploaded by

Copyright:

Available Formats

MODBUS-GW

Installation and Operation Manual

Fire Alarm & Emergency Communication System Limitations

(caused by escaping gas, improper storage of flammable materials, etc.).

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

reaming, or punching of the enclosure. When possible, make

gramming manuals. These instructions must be followed to

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

Document part number and title

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

Section 2 Installation ............................................................................................................. 15

Section 3 Configuration ......................................................................................................... 23

3.3.3: MODBUS-GW Main Menus.............................................................................................................24

Section 4 Operation ................................................................................................................ 29

Section 5 Register Mapping................................................................................................... 33

Appendix A: Gateway Settings.............................................................................................. 45

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

Appendix B: Exception Responses ..................................................................................... 47

Appendix C: MODBUS-GW Active Event Types .................................................................. 49

Appendix D: Device Types..................................................................................................... 51

Appendix E: System Troubles .............................................................................................. 55

Appendix F: Moxa MGate MB3180 Interface ........................................................................ 73

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

Section 1 Product Overview

1.3 Required Software

1.4 Environmental Requirements

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

1.5 System Architecture

Figure 1.1 Single Panel Architecture

Figure 1.2 NFN Network Architecture

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

Figure 1.3 Redundant Modbus Gateways

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

1.6 IP Port Requirements

The following restrictions apply:

Must have a Static IP Address, DHCP is not supported.

1.7 Bandwidth Calculation

Table 1.2 Modbus TCP Response

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

1.7.1 Calculating the Bandwidth Requirement

Formula for MODBUS-GW network bandwidth requirement based on polling rate:

1.8 Agency Listings

National Fire Alarm Code

Control Units for Fire Alarm Systems, Ninth Edition

Underwriters Laboratories Canada

Installation - This product is intended to be installed in accordance with the following:

Authority Having Jurisdiction

National Fire Protection Association

National Electrical Code

Underwriters Laboratories Canada

Installation of Fire Alarm Systems, Fifth Edition

Canadian Electrical Code, Part I, Safety Standard for Electrical Installations

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

1.8.2 Agency Restrictions and Limitations

1.9 Compatible Equipment

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

Customer Supplied Equipment:

MODBUS-GW Installation and Operation Manual P/N LS10015-000NF-E:B2 8/8/2013

2.2 Board Installation