Honeywell Notifier MODBUS-GW Installation And Operation Manual
  1. Manuals
  2. Brands
  3. Honeywell Manuals
  4. Gateway
  5. Notifier MODBUS-GW
  6. Installation and operation manual

Honeywell Notifier MODBUS-GW Installation And Operation Manual

Modbus gateway
Hide thumbs
Table of Contents

Advertisement

Quick Links

MODBUS-GW Installation and Operation Manual
Modbus Gateway
MODBUS-GW

Installation and Operation Manual

Document LS10015-000NF-E Rev: C2
4/30/2019 ECN: 19-0599

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Notifier MODBUS-GW and is the answer not in the manual?

Questions and answers

Related Manuals for Honeywell Notifier MODBUS-GW

Summary of Contents for Honeywell Notifier MODBUS-GW

  • Page 1: Installation And Operation Manual

    MODBUS-GW Installation and Operation Manual Modbus Gateway MODBUS-GW Installation and Operation Manual Document LS10015-000NF-E Rev: C2 4/30/2019 ECN: 19-0599...
  • Page 2 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 system—typically made up of smoke Heat detectors do not sense particles of combustion and alarm detectors, heat detectors, manual pull stations, audible warning only when heat on their sensors increases at a predetermined rate devices, and a fire alarm control panel (FACP) with remote notifica-...

  • Page 3: Installation Precautions

    HARSH™, NIS™, and NOTI•FIRE•NET are all trademarks; and Acclimate® Plus™, eVance®, FlashScan®, FAAST Fire Alarm Aspiration Sensing Technology®, Honeywell®, Intelligent FAAST®, NOTIFIER®, ONYX®, ONYXWorks®, SWIFT®, VeriFire®, and VIEW® are all registered trademarks of Honeywell International Inc. Microsoft® and Windows® are registered trademarks of the Microsoft Corporation. Chrome™ and Google™ are trademarks of Google Inc.
  • Page 4 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 email us at FireSystems.TechPubs@honeywell.com. On-Line Help – Please include the following information: • Product name and version number (if applicable) •...

  • Page 5: Table Of Contents

    Table of Contents Section 1 Product Overview ..............................8 1.1: Operation ..........................................8 1.2: Functionality .........................................8 1.3: Recommended Cybersecurity Practices ................................8 1.4: Required Software ........................................8 1.5: Environmental Requirements ....................................8 1.6: IP Requirements........................................8 1.6.1: IP Port Settings ......................................8 1.6.2: IP Restrictions......................................8 1.7: Bandwidth Calculation ......................................9 Table 1.1 Modbus TCP Request ..................................9 Table 1.2 Modbus TCP Response................................9 1.7.1: Calculating the Bandwidth Requirement..............................9...
  • Page 6 Table of Contents Table 3.1 Main Menus ....................................23 3.2.4: Product Information....................................24 Table 3.2 Product Information...................................24 3.2.5: Additional Properties ....................................25 Table 3.3 Additional Properties .................................25 3.2.6: Node List .........................................27 Table 3.4 Node List Display ..................................27 3.3: Security Certificate ......................................28 Figure 3.2 Chrome Security Warning Example............................28 Section 4 Operation................................29 4.1: Panel and Gateway Synchronization ..................................29 4.2: Modbus Command Support ....................................29...
  • Page 7 Table of Contents Appendix A Gateway Settings............................43 A.1: Viewing Existing IP Settings.....................................43 A.2: Resetting Factory Default Values ..................................43 Appendix B Exception Responses ..........................44 Table B.1 Exception Codes ..................................44 Appendix C MODBUS-GW Active Event Types .......................45 Table C.1 Event Type Categories ................................45 Appendix D Device Types..............................46 Table D.1 Device Type Values –...

  • Page 8: Section 1 Product Overview

    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 a Modbus master application. The MODBUS-GW operates as a Modbus slave device. 1.2 Functionality The MODBUS-GW: •...

  • Page 9: Bandwidth Calculation

    Bandwidth Calculation Product Overview 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 IP Header TCP Header MBAP Header Message—5 bytes Function code (1) + Start Address (2) + Quantity of Registers (2) Total Bytes Table 1.2 Modbus TCP Response...

  • Page 10: System Architecture

    Product Overview System Architecture 1.8 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 FACP MODBUS-GW Modbus/IP Client Figure 1.1 Single Panel Architecture IP Network Ethernet Ethernet Ethernet...

  • Page 11: 1: Redundancy

    System Architecture Product Overview 1.8.1 Redundancy A redundant gateway is a second gateway which communicates with a Modbus client. The second gateway must have a separate and unique IP address from the first gateway. An example system is shown in Figure 1.3.

  • Page 12: Agency Listings

    Product Overview Agency Listings 1.9 Agency Listings 1.9.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 and Signaling Code Underwriters Laboratories •...

  • Page 13: Compatible Equipment

    Compatible Equipment Product Overview 1.10 Compatible Equipment The MODBUS-GW is compatible with the following equipment: Table 1.3 Compatible Equipment Type Equipment • NFS-320 • NFS2-640 Fire Panels: • NFS2-3030 • NCM-W, NCM-F • HS-NCM-W, HS-NCM-SF, HS-NCM-MF, HS-NCM-WSF, Network Cards: HS-NCM-WMF, HS-NCM-MFSF •...

  • Page 14: Section 2 Installation

    Section 2 Installation 2.1 Required Equipment 2.1.1 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.

  • Page 15: Board Installation

    Board Installation 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 Bracket Slot Install bracket on 1/2” standoffs. Place the board’s Mount in 4th column of the NFS2-640 Series tab in the bracket slot and screw the board to the chassis.

  • Page 16: Connections

    Installation Connections 2.3 Connections 2.3.1 Connecting the MODBUS-GW USB “A” Host (J2) USB “B” Device (J1) Ethernet Connector (J3) NUP A Mounting Hole Connector (J4) (1 of 12) Not Used (J5) Not Used (TB1) 24 V Out (TB2) 24 V In Figure 2.5 MODBUS-GW Connections Table 2.1 Connection Specifications Reference...

  • Page 17: Figure 2.6 Modbus-Gw Leds

    Connections Installation (J1) (J3) LEDs (See Table Below) (J4) (J5) (TB1) (TB2) Figure 2.6 MODBUS-GW LEDs Table 2.2 LED Definitions Reference Label Description Designator ACTIVE Active/Lit indicates that WinCE is running. NUPA RX Blinks when data is received on the NUP A port (J4). PROGRAM Not Used NUPB RX...

  • Page 18: 2: Connecting To A Standard Ncm

    Installation Connections 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 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...

  • Page 19: 3: Connecting To An Hs-Ncm

    Connections Installation 2.3.3 Connecting to an HS-NCM For Communications, Connect USB A to B OR USB B to A HS-NCM MODBUS-GW Out to HS-NCM – – 24V In From External 24 VDC Power Source to TB2 Figure 2.8 Routing Power and Communication to an HS-NCM Table 2.4 HS-NCM Connections Type Connection...

  • Page 20: 4: Connecting To A Fire Alarm Control Panel (Facp)

    Installation Connections 2.3.4 Connecting to a Fire Alarm Control Panel (FACP) Panel is shown for illustrative purposes only. The NUP Cable Provides Both MODBUS-GW is mounted within the FACP cabinet and Power and Communication connected with the NUP connection located on the FACP.

  • Page 21: System Power

    System Power Installation 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 S536. MODBUS-GW Installation and Operation Manual —...

  • Page 22: Section 3 Configuration

    Section 3 Configuration 3.1 Configuration Web Page Configuration of the MODBUS-GW is through a web page running on the MODBUS-GW. Supported web browsers are listed in 1.4, "Required Software". The following information applies to IP settings: • Each MODBUS-GW is shipped with a default IP address of 192.168.1.2 and a default node number of 240. •...

  • Page 23: 2: Basic Configuration Tool Layout

    Configuring the MODBUS-GW Configuration 3.2.2 Basic Configuration Tool Layout Click to Enter or Click for Product Change Text Information (see 3.2.4) Main Menus (see 3.2.3) Click for Drop-down List Click to View Sub-items Click to Apply Changes Error Log (Not Used) Navigation Tree: Additional Properties (see 3.2.5) Node List (see 3.2.6)

  • Page 24: 4: Product Information

    Configuration Configuring the MODBUS-GW Table 3.1 Main Menus (Continued) Menu Option Description Set Device Displays a dialog box allowing the user to change the current password. Tools Password • Passwords are case sensitive. • Alpha and numeric characters are supported. •...

  • Page 25: 5: Additional Properties

    Configuring the MODBUS-GW Configuration 3.2.5 Additional Properties The following table describes the options available under Additional Properties in the navigation tree (see Figure 3.1). After configuring the settings, click Apply in the lower-right corner of the window. Table 3.3 Additional Properties Navigation Property Value...
  • Page 26 Configuration Configuring the MODBUS-GW Table 3.3 Additional Properties (Continued) Navigation Property Value Tree Label Node Node Mapping Mapping Authorized Client IP This is an optional security feature. The options are: • Enter the authorized client IP address. The gateway only responds to requests from the client at that IP –...

  • Page 27: 6: Node List

    Configuring the MODBUS-GW Configuration Table 3.3 Additional Properties (Continued) Navigation Property Value Tree Label Node Node Mapping Node List Node Column (Continued) Displays the node numbers and names of nodes on the NFN network. Monitored Column: • Select Yes to monitor the node. •...

  • Page 28: Security Certificate

    Configuration Security Certificate 3.3 Security Certificate The MODBUS-GW communicates with the browser using secure communications facilitated by a self-signed security certificate. Using the self-signed security certificate will cause the browser to display warnings similar to the following: Figure 3.2 Chrome Security Warning Example The browser warning is displayed upon each connection to the gateway.

  • Page 29: Section 4 Operation

    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-GW synchronizes with a panel: •...

  • Page 30: Analog Values And Trending

    Operation Analog Values and Trending 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 4–20 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 sepa- rate poll is sent for these points in groups of up to 10 points at a time, following the rules outlined below.

  • Page 31: Section 5 Register Mapping

    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 into an upper and lower byte as described below and in Table...

  • Page 32: Table 5.2 Point Status Holding Register Device/Module Addresses

    Register Mapping Point Status Holding Registers The holding register addresses and the points contained in these addresses are detailed in Table 5.2. Each range of holding registers is used for either detectors or modules. Table 5.2 Point Status Holding Register Device/Module Addresses Start Address End Address Address...

  • Page 33: Point Device Type Holding Registers

    Point Device Type Holding Registers Register Mapping 5.3 Point Device Type Holding Registers There are 2000 point device type holding registers. Each register address consists of two bytes (upper and lower) as defined in Table 5.3 representing two detectors or modules as shown in Table 5.4.

  • Page 34: Zones/Panel Circuits Status Holding Registers

    Register Mapping Zones/Panel Circuits Status Holding Registers 5.4 Zones/Panel Circuits Status Holding Registers Each of the zones/panel circuits status holding registers are divided into an upper and lower byte as described below and in Table 5.5. • Upper Byte: The upper byte contains general status information about the zone or panel circuit. •...

  • Page 35: Table 5.7 Panel Circuits

    Zones/Panel Circuits Status Holding Registers Register Mapping The holding register addresses and the panel circuits contained in these addresses are detailed in Table 5.7. Table 5.7 Panel Circuits Register Address Panel Circuits 49111–49118 P1.1–P1.8 49119–49126 P2.1–P2.8 49127–49134 P3.1–P3.8 49135–49142 P4.1–P4.8 49143–49150 P5.1–P5.8 49151–49158...

  • Page 36: Bell Circuits Status Holding Registers

    Register Mapping Bell Circuits Status Holding Registers 5.5 Bell Circuits Status Holding Registers NFS2-640 and NFS-320 Only  Each of the bell circuits status holding registers are divided into an upper and lower byte as described below and in Table 5.9.

  • Page 37: Bell Circuits Device Type Holding Registers

    Bell Circuits Device Type Holding Registers Register Mapping 5.6 Bell Circuits Device Type Holding Registers Each bell circuits device type holding register address consists of two bytes (upper and lower) as defined in Table 5.11 representing two bell circuits as shown in Table 5.12.

  • Page 38: Analog Values Input Registers

    Register Mapping Analog Values Input Registers 5.8 Analog Values Input Registers Analog values listed in Table 5.15 are only available for 4–20 mA modules. Refer to 4.4, "Analog Values and Trending" for details regarding analog values. Table 5.15 Input Register Analog Values Start Address End Address Analog Value (16 bits)

  • Page 39: Gateway Information Input Registers

    Gateway Information Input Registers Register Mapping 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 and in Table 5.17.

  • Page 40: Table 5.19 43/14 (0X2B/0X0E) Read Device Identification

    Register Mapping Gateway Information Input Registers 5.10.2 Read Device Identification (0x2B/0x0E) This function code allows reading the identification and additional information about the MODBUS-GW as shown in Table 5.19. Table 5.19 43/14 (0x2B/0x0E) Read Device Identification Object Name / Object ID Description Value 0x00...

  • Page 41: Section 6 Troubleshooting

    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.

  • Page 42: What Is The "Analog Value Polling Time Out

    Troubleshooting What is the “Analog Value Polling Time Out”? 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.

  • Page 43: Appendix A Gateway Settings

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

  • Page 44: Appendix B Exception Responses

    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.

  • Page 45: Appendix C Modbus-Gw Active Event Types

    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. Table C.1 Event Type Categories Event Modbus Register Value No Active Status (see note) Mass Notification Alarm, High Priority Fire Alarm Security Alarm (Life)

  • Page 46: Appendix D Device Types

    Appendix D Device Types Device types are organized into the following categories: • Detectors (1–50) - Table D.1 • Monitor Modules (51–150) - Table D.2 • Control Modules (151–250) - Table D.3 Table D.1 Device Type Values – Detectors DEVICE TYPE Value HEAT DETECTOR ION DETECTOR...

  • Page 47: Table D.3 Device Type Values - Control Modules

    Device Types Table D.2 Device Type Values – Monitor Modules (Continued) DEVICE TYPE Value DEVICE TYPE Value FIRE CONTROL MASS NOTIFICATION TROUBLE MON HAZARD ALERT MASS NOTIFICATION MONITOR Table D.3 Device Type Values – Control Modules DEVICE TYPE Value DEVICE TYPE Value CONTROL ALARMS PEND...

  • Page 48: Appendix E System Troubles

    Appendix E System Troubles Table E.1 System Troubles Register Map Register Bit No. System Trouble Name Bit No. System Trouble Name GROUND FAULT INTERNAL RAM ERROR 35001 AC FAIL EXTERNAL RAM ERROR BATTERY PROGRAM CORRUPTED STYLE 6 POS. LOOP 1 NO DEV.
  • Page 49 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name NETWORK FAIL PORT B UDACT TROUBLE 35006 NETWORK FAILURE UDACT NO ANSWER ADV WALK TEST PROG MODE ACTIVATED CHARGER FAIL LOADING NO SERVICE GROUND FAULT LOOP 2 BASIC WALK TEST...
  • Page 50 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name ANNUN.57 TROUBLE ANNUN.61 TROUBLE 35011 ANNUN.57 NO ANSWER ANNUN.61 NO ANSWER ANNUN.58 TROUBLE ANNUN.62 TROUBLE ANNUN.58 NO ANSWER ANNUN.62 NO ANSWER ANNUN.59 TROUBLE ANNUN.63 TROUBLE ANNUN.59 NO ANSWER...
  • Page 51 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name STYLE 6 SHORT LOOP 8 TM4 NO ANSWER 35016 STYLE 6 SHORT LOOP 9 TM4 DISABLED STYLE 6 SHORT LOOP 10 SELF TEST FAILED NODE xxx COMMUNICATIONS FAILURE NETWORK INCOMPATIBILITY...
  • Page 52 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name ANNUN. 97 TROUBLE ANNUN. 101 TROUBLE 35021 ANNUN. 97 NO ANSWER ANNUN. 101 NO ANSWER ANNUN. 98 TROUBLE ANNUN. 102 TROUBLE ANNUN.
  • Page 53 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name REMOTE DISPLAY 9 TROUBLE REMOTE DISPLAY 13 TROUBLE 35026 REMOTE DISPLAY 9 NO ANSWER REMOTE DISPLAY 13 NO ANSWER REMOTE DISPLAY 10 TROUBLE REMOTE DISPLAY 14 TROUBLE REMOTE DISPLAY 10 NO ANSWER REMOTE DISPLAY 14 NO ANSWER...
  • Page 54 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name Reserved Reserved 35031 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved NO POWER SUPPLY INST 35032 Reserved LOOP 1-2 COMM FAILURE...
  • Page 55 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name 35035 TRANSMIT/RECIEVE ERROR ABOVE LIMIT ON LOOP 10 TOO MANY DEVICES ON LOOP 8 TOO MANY DEVICES ON LOOP 9 MISMATCHED LOOP TYPE ON LOOP 7 35036 TOO MANY DEVICES ON LOOP 10...
  • Page 56 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name Reserved Reserved 35040 Reserved Reserved 35041 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved 35042...
  • Page 57 System Troubles Table E.1 System Troubles Register Map (Continued) Register Bit No. System Trouble Name Bit No. System Trouble Name Reserved Reserved 35045 Reserved Reserved 35046 Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved 35047...

  • Page 58: Appendix F Conversion To Modbus Rtu

    Appendix F Conversion to Modbus RTU 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 the MODBUS-GW.

  • Page 59: Connecting The Moxa Mgate Mb3180 Interface To The Modbus-Gw

    Connecting the Moxa MGate MB3180 Interface to the MODBUS-GW Conversion to Modbus RTU F.3 Connecting the Moxa MGate MB3180 Interface to the MODBUS-GW NOTE: The configuration used must have the approval of the AHJ (Authority Having Jurisdiction). Connect the RTU master to the Serial port (RS232, RS485, RS422) of the MB3180. Connect the MB3180 to the MODBUS-GW.
  • Page 60 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.
  • Page 61 NOTIFIER 12 Clintonville Road Northford, CT 06472-1610 USA 203-484-7161 www.notifier.com...

Table of Contents

Save PDF