NK823x MP4.50 Modbus Gateway for STT20 Add-on Module Installation Configuration Commissioning A6V10374340_a_en 24.09.
Table of Contents About this document.........................................................................................................5 1 Safety regulations ..............................................................................................8 1.1 Country-specific standards...................................................................................8 1.2 Assembly and installation.....................................................................................8 1.
5.2.3 NK823x Gateway Register Map..........................................................41 5.2.3.1 Status Tables ......................................................................................41 5.2.3.2 NK823x Objects ..................................................................................42 4 Building Technologies Fire Safety & Security Products A6V10374340_a_en 24.09.
About this document About this document Purpose of this document This manual is intended as a guide for the installation, configuration, and operation of the NK8000 network units that can support the STT20 BACnet connectivity for DMS8000 as well as 3rd party Modbus stations and devices.
About this document - Segment: 04 Fire -3F - Document Type: All - Image Type: All - Advanced search criterias: Select Brochure No. and enter the document number to search for (A6V10089056). Alternatively, select Title and enter the product name (DMS8000). 2. Click Search to start. 3. In the resulting area on the right, click on Contents link to show the list of search results. For more information such as Siemens news and announcements, visit the STEP Web portal at: https://workspace.sbt.siemens.
About this document Conditions that you must complete or must be met before beginning a procedure are designated with a ⊳. Results, after completing a step or at the end of the entire procedure, are designated with a ⇨. ⊳ The report you want to print is open. 1. Select the Print icon . ⇨ The Print dialog box appears. 2. Select the printer and click Print. ⇨ The print confirmation appears. Bold font in a procedure indicates something Type F for Field panels. you should select or type.
1 Safety regulations Country-specific standards 1 Safety regulations This section describes the danger levels and the relevant safety regulations applicable to the use of the products described in this manual. Please read the following work instructions as well as the preceding section About this document thoroughly before beginning any work. 1.1 Country-specific standards Siemens products are developed and produced in compliance with the relevant international and European safety standards.
Safety regulations Modifications to system design and products 1 Modifications to a system or to individual products may cause faults or malfunctioning. Please request written approval from Siemens Building Technologies, FS-DMS, and the relevant authorities concerning intended system modifications and system extensions. 9 Building Technologies Fire Safety & Security Products A6V10374340_a_en 24.09.
2 Introduction 2 Introduction Addressing the French regulations, STT20 system is designed to perform automatic actions (called “fire actuations”) following the detection of fire alarms by a fire detection system, which can be: CS11 AlgoRex system, connected over a Cerloop network. FS20 Sinteso system, connected over a SAFEDLINK network providing a BACnet/IP interface. STT20 is made up of a physical and logical tree.
Installation Add-on distribution package 3 3 Installation There are basically three major installation steps: 1. Install the DMS8000 software. Referring to the setup menu presented in the DMS8000 installation, use one of the following setup options: – Stand-alone (MM8000), to install the complete MM8000 configuration and runtime environment. Use this option if the Modbus gateway is part of a wider MM8000 system.
3 Installation Software installation NOTE: hardware key and PAK code are not required if the setup option Composer GW tool (NK8237) is selected. Task list 1. Check for requirements, compatibility, and license 2. Install the DMS8000 software and the required license key and PAK – See the MM8000 Installation, Configuration and Commissioning manual (A6V10062413) – See the MM8000 Release Notes (A6V10062509) 3. Install the mandatory Hotfix #04 for DMS8000 MP4.50 4.
Installation Software installation 3 NK8235 Ethernet Port for DMS8000 with Modbus Gateway A normal MM8000 license is required, including # of panels, # of physical points, driver, and so on. In addition, a Composer license or a Service-key is required for the configuration tasks. NK8237 Modbus Gateway No runtime license is required. Composer configuration will need no license either as long as the Composer GW Tool setup is used.
3 Installation Software installation 3.2.4 Multiple add-on's installations In general, it is possible to install multiple add-on packages and benefit of their combined functionalities. However, specific incompatibilities might exist. Please check about possible problems in the documentation of all add-on modules that must be installed. 3.2.5 Removing the Add-on module The add-on module cannot be uninstalled. 14 Building Technologies Fire Safety & Security Products A6V10374340_a_en 24.09.
Configuration Configuring the fire network 4 4 Configuration There are basically three major configuration steps: 1. Configure the STT20 units (as well as FC20 detection units) using the specific tools and download the fire system. Then, export the configuration in XML format (SiB-X format for FS20). – For detailed information, refer to the STT20 (and FS20) configuration tool manuals. 2. Configure the NK823x and the fire systems in Composer. You need to import the STT20 and FS20 export files.
4 Configuration Configuring the fire network A new node is added to the project structure. Importing the STT20 metafile 1. Select the STT20 node. 2. Select Tools > Import in the Composer menu to start the import procedure. The software presents a browsing window to search for the file to import (XML file). 3. Using standard Windows controls, do the following: - Locate the file. - Select it and click Open.
Configuration Configuring the fire network 4.1.2 4 NK823x BACnet Protocol The fire system connection to the NK823x Modbus Gateway makes use of the BACnet protocol over IP. In the BACnet/IP communication with the fire units, the NK823x Modbus Gateway acts as a BACnet client. The NK823x configuration in Composer include the definition of the IP addressing and the BACnet/IP connectivity. In both cases, the NK823x configuration must match what is expected by the fire system.
4 Configuration Configuring the fire network Routing Tables: NK823x can handle a static routing table to address multiple subnets via IP routers (e.g. SAFEDLINK GAP stations). Accesses to subnets that are not handled by the NK323x Default gateway must be defined as routing table. Note that, if a SAFEDLINK network includes both FS20 and STT20 units, two separate GAPs must be addressed and specific routing tables for two separate subnets must be defined accordingly.
Configuration Configuring the fire network 4 - IP address of the Gateway (GAP) that can provide connectivity to the destination subnet. TIP: Use the Ping button in the Tools tab to check that the IP connectivity is properly established between the NK823x and the routing gateway. - If multiple routes are available for the same destination, use the Metric field to indicate the cost (e.g.
4 Configuration Configuring the fire network 9. If the NK823x acts as BBMD, you have to configure the BBMD settings in the NS8011 BACnet Driver node: 4.1.3 - Press the BBMD Configuration button. The BBMD window that appears is organised in two tables. - In the upper table, set the required BBMD role of the NK823x components (max one per subnet): enable the checkbox on the right. - In the lower part, add the corresponding routing partner(s) in the other subnet(s).
Modbus Interface Specifications Modbus Gateway 5 5 Modbus Interface Specifications The NK823x Modbus gateway enables Modbus master/client stations to access the STT20 units for acquiring the status information. The gateway also allows for control commands to be transmitted from the Modbus master/client stations to the fire system. A specific agreement with Siemens is required for this type of functions.
5 Modbus Interface Specifications Modbus Data Model Function code Function Applicable table types Notes 0x04 Read Input Registers Summary; Status; Compact Status Use it for reading status information 0x06 Write Single Register Command; Synchronization Use it for writing command registers, to perform control actions, and date & time registers, thus synchronizing the NK8237 clock.
Modbus Interface Specifications Modbus Data Model 5 Once finalized, the CSV file can be used for integrating the model information in the Modbus master/client station, and the corresponding register map downloaded into the NK823x unit. NOTE: All addressing starts with offset 0. 5.2.1.1 Customizing Modbus Maps The following illustrates the overall map customization procedure. 1. Start the Composer tool and open the Modbus gateway project. The project tree displays in the Composer environment. 2.
5 Modbus Interface Specifications Modbus Data Model Modifying the registers address and (re)organize the data memory to optimize the Modbus master/client treatment. Feeding the fire system configuration into the Modbus master/client configuration tool. The following fields (columns) are present in the CSV file: SubsystemId Identifier of the subsystem in the Composer project, and used during file re-import. It cannot be modified.
Modbus Interface Specifications Modbus Data Model 5 For each object, the actual Modbus register address is determined by summing the Modbus BaseAddress and the ModbusAddress. CommandRange Starting address of the set of Modbus Holding Registers associated to the command objects. Modifications to this field are ignored in the re-import. Note however that the base addresses for the command tables can be modified in the Composer configuration.
5 Modbus Interface Specifications Modbus Data Model – The vitality counter (1 word register). – As many as 525 data change flags (33 word registers) reporting any modifications in the register area (the complete range of 65536 registers is monitored). Status tables These are word input registers reporting the conditions of all the mapped objects.
Modbus Interface Specifications Modbus Data Model – Battery Fault – Function Safety Position Failed – Function In Command – Function Wait Position Failed – Function Fault – UGA Alarm – UGA Activated Evacuation – UGA Fault – BOP Evacuation Mode On Manual Command tables The output command tables (read/write holding registers) enables Modbus master/client stations to initiate control commands to the fire control panels.
5 Modbus Interface Specifications Modbus Data Model Bit Information Notes about affected objects and conditions corresponding to the “1” state (bit active) Legal information for a repeater terminal. 2 Evacuation active BOP Alarm function or HLB Alarm function. Legal information for a repeater terminal. 3 Alarm received BOP Alarm function. Legal information for a repeater terminal. 4 Reset command required A reset command is expected by the STT20 panel.
Modbus Interface Specifications Modbus Data Model 5 Data Change A set of 33 input word registers (525 bits are used) reporting any modifications in the register area. The complete range of 65536 Modbus registers is covered, with each flag representing changes in one or more registers in a corresponding group of 125 word registers. The first flag, i.e.
5 Modbus Interface Specifications Modbus Data Model NOTE: For detailed information about the time synchronization options on the Modbus host interface, refer to the Modbus interface configuration section of the NK8237 Installation, Configuration, and Commissioning manual (A6V10316241). 5.2.2.3 Status Tables The status tables include an input word register per object. The number of tables depends on the specific systems whose object list is defined at configuration time.
Modbus Interface Specifications Modbus Data Model 5 Buzzer Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-7 - Not used 8 Non-default value Abnormal condition resulting in a reduced safety 9-14 - Not used 15 Active WT_Buzzer (Input registers, default base address: 1400) Communication Link (SafeDlink, Cerloop) Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-7 - Not used 8 Non-
5 Modbus Interface Specifications Modbus Data Model MEA – Module Electronique Adressable (addressable field control module) Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-7 - Not used 8 Non-default value Abnormal condition resulting in a reduced safety 9-12 - Not used 13 Fault 14-15 - Not used WT_MEA (Input registers, default base address: 1700) MDHW – Matériel Déporté (Remote Module Hardware) Bit Information Notes 0 (lsb) Non-d
Modbus Interface Specifications Modbus Data Model 5 Battery Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-7 - Not used 8 Non-default value Abnormal condition resulting in a reduced safety 9-12 - Not used 13 Fault Battery fault (on MC20, MCO, or MD20 modules) or battery element faulty 14-15 - Not used WT_Battery (Input registers, default base address: 2500) MCIO – MC20 Input/Output Bit Information Notes 0 (lsb) Non-default mode
5 Modbus Interface Specifications Modbus Data Model Function – Standard / Stop fan / Fire technical / Technical / Rearming functions Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-6 - Not used 7 Locked Function locked 8 Non-default value Function locked without fault 9-11 - Not used 12 Wait position failed Wait position fault 13 Fault 14 In command or Safety position 15 Safety position failed Safety position fault WT_Function
Modbus Interface Specifications Modbus Data Model 5 BOP Evacuation Mode Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-4 - Not used 5 Manual (OnManual) Manual mode 6-7 - Not used 8 Non-default value Manual mode 9-15 - Not used WT_BOPEvacuationMode (Input registers, default base address: 7500) Horn Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-6 - Not used 7 Disabled 8
5 Modbus Interface Specifications Modbus Data Model Extinguishing Element Bit Information Notes 0 (lsb) Non-default mode Abnormal mode status resulting in a reduced safety 1-7 - Not used 8 Non-default value Abnormal condition resulting in a reduced safety 9-13 - Not used 14 Extinguishing released 15 - Not used WT_ExtElement (Input registers, default base address: 9200) 5.2.2.
Modbus Interface Specifications Modbus Data Model 5.2.2.5 5 Bit Status Tables The bit status tables presents single on/off event conditions for specific types of object (Panel, Faults, Functions, and so on) and related conditions, for example function in command. In all tables, the value 1 indicates that the condition is present for at least one of the objects considered. The list of objects is defined at configuration time. The table below collects the list of bit status tables.
5 Modbus Interface Specifications Modbus Data Model 5.2.2.6 Command Tables The command tables enable the Modbus master/client to issue control commands to the fire units. A read/write holding register is foreseen for each of the objects listed below. Given an initial object state, a data value corresponding to a control action can be written in the register to trigger the command that is then expected to modify the object state and therefore cause a corresponding change in the object input registers.
Modbus Interface Specifications Modbus Data Model 5.2.2.7 5 Example of Register Map The following illustrates an example of a register map as it is presented in the Composer configuration tool. In the case of the panel map, the default addresses are listed, which can be customized in the Composer configuration.
5 Modbus Interface Specifications Modbus Data Model Modbus Table Modbus Base Address Offset Register WT_Battery 2500 0 Input register WT_Battery 2500 1 Input register WT_MCIO 3500 0 Input register WT_MCIO 3500 1 Input registert WT_MCIO 3500 2 Input register WT_MDIO 4000 0 Input register WT_MDIO 4000 1 Input register WT_Function 5000 0 Input register WT_Function 5000 1 Input register WT_Function 5000 2 Input register WT_Function 5000 3 Input register WT_Funct
Modbus Interface Specifications Modbus Data Model 5 WARNING The convention of Modbus base addresses frequently found, namely 3xxxx for input registers, 4xxxx for holding registers and so on, is not followed by NK823x. Note that some tools strictly based on this convention will not work properly with NK823x. 5.2.3 5.2.3.1 NK823x Gateway Register Map Status Tables The gateway status tables include two types of input word registers applied to a number of objects.
5 Modbus Interface Specifications Modbus Data Model 5.2.3.2 NK823x Objects This section lists the gateway objects and the corresponding types in the NK823x Modbus data model (refer to the Register Map section). WT_NK823xPoint Application node (NK823x status) NK823x unit tamper Digital Input Onboard (power supply supervision or generic inputs) Digital Output Onboard (Modbus communication fault) 42 Building Technologies Fire Safety & Security Products A6V10374340_a_en 24.09.
Issued by Siemens Switzerland Ltd Infrastructure & Cities Sector Building Technologies Division International Headquarters Gubelstrasse 22 CH-6301 Zug Tel. +41 41-724 24 24 www.siemens.com/buildingtechnologies Document ID A6V10374340_a_en Edition 24.09.2012 © 2012 Copyright Siemens Switzerland Ltd Technical specifications and availability subject to change without notice.
