NK8237 MP4.70 Modbus Gateway for Sinteso STT20 and Cerberus PRO Fire Detection Systems Installation Function & Configuration Commissioning Safety Regulations A6V10316241_a_en 30.09.
Table of contents About this document.........................................................................................................7 1 Safety regulations ............................................................................................10 1.1 Country-specific standards.................................................................................10 1.2 Assembly and installation...................................................................................10 1.
6.7 Secure communication for web services............................................................36 7 Configuration ....................................................................................................38 7.1 Configuration checklist .......................................................................................38 7.2 Configuring IP settings via the NK823x Web Server..........................................39 7.3 Configuring IP settings via NW8202..........................
10 9.6.2 Fire systems communication problems ..............................................91 9.6.3 Control unit generated a fault .............................................................91 9.6.4 Control unit won't respond ..................................................................91 9.6.5 No fault generated by network failure - MP3.15 and higher ...............91 Secure operation requirements ......................................................................
About this document About this document Purpose This document is a guide to the installation, configuration and commissioning of the NK8237 Modbus gateway for FS20, STT20, and FS720 fire detection systems. It includes an overview of the system, hardware requirements and limitations, and detailed installation and configuration instructions. This guide is to be used in conjunction with the Composer Technical Manual (document no. A6V10062401).
About this document 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.com/content/00001123/default.aspx Note: Before beginning work on the system you must have read and understood the Safety Regulations section in this manual.
About this document Menu paths are indicated in bold. Select File > Text, Copy > Group, which means from the File menu, then select Text, Copy and finally Group. Error and system messages are displayed in The message Definition Courier New font. successfully renamed displays in the status bar. Italics are used to emphasize a term. The Open Processor continuously executes a user-defined set of instructions called the control program. This symbol signifies a Note.
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. Danger potential to individuals NK8237 units are powered with low voltage DC.
Safety regulations Disposal and recycling 1.4 1 Disposal and recycling These devices include electrical and electronic components and must not be disposed of as domestic waste. Current local legislation must be observed. The NK8237 units have been manufactured as much as possible from materials that can be recycled or disposed of in a manner that is not environmentally damaging.
2 Introduction Connectivity examples 2 Introduction The NK8000 family provides LAN/WAN adapter products for a safety and security network: The NK822x series (phased out). The NK823x series. The NK8237 Modbus Gateway. The NK8237 Modbus Gateway for Sinteso FS20, STT20 and Cerberus PRO FS720 fire detection systems provides a connection (TCP/IP or Serial RTU) to a 3rd party Modbus station/unit for supervision and control of fire systems. 2.
Introduction What's new 2.2 2 What's new Here is the list of modifications for new functions and software improvements. Section Modifications NK823x Web Server [➙ 33] New NK823x Web Server to configure IP addresses and get diagnostic information. Configuring IP settings via the NK823x Web Server [➙ 39] The NK823x Web Server [➙ 82] NW8204 installation [➙ 36] Added command line for silent installation.
3 System limits 3 System limits The following describes the system limits for the NK8237 units. Fire control units The following control units are supported: FC2020 FC2030 FC2040 FC2060 FC2080 FT2040 FT2080 FC722 FC724 FC726 FT744 STT20 (with FCGW20-02) For detailed information about supported subsystem software versions see the NK8000 Release Notes (document n.A6V10062453.) Fire system topologies and max.connectivity Up to 16 FC20xx/FC72x control units.
System limits 2 Modbus hosts 3 Modbus hosts 4 Modbus hosts Max. 5,000 detectors. Max. 3,500 detectors. Max. 2,500 detectors. 3 8 FS20/FS720 units - OR 6 FS20/FS720 units and 5 STT20 units in FCnet/SAFEDLINK topology. 6 FS20/FS720 units - OR 5 FS20/FS720 units and 3 STT20 units in FCnet/SAFEDLINK topology.
4 Structure and functions NK8237 hardware 4 Structure and functions 4.1 NK8237 hardware The NK8237 is composed of an electronic board installed in a compact and robust plastic box. Note: NK8237 units with build state up to 01 are equipped with the NKM8001-A1 mainboard and NK8237 units with build state 10 or higher are equipped with the NKM8001-A2 mainboard. NK8237 gateway unit 4.1.1 Front panel The front panel houses 9 LED’s.
Structure and functions NK8237 hardware 4 Blinking (1 flash): missing or insufficient license. Blinking (2 flashes): trouble with the I2C bus to I/O modules. Blinking (3 flashes): not used Blinking (4 flashes): trouble with the serial/network interface. Blinking (5 flashes): trouble with DLL or RCLOCK file(s). Blinking (6 flashes): Modbus GW trouble. – – – SW trouble. No communication to FS20/FS720 or to the Modbus Master/Client.
4 Structure and functions NK8237 hardware 4.1.3 Internal jumpers 1 2 X1 X2 X3 3 X101 X102 X103 X104 4 X105 X111 Internal DIP switch and jumpers (NKM8001-A1 mainboard) Item Name Description 1 S101 DIP-Switches 2 S1 Reset button 3 S2 Tamper switch 4 X115 When closed, it disables the box tamper alarm. 18 Building Technologies Fire Safety & Security Products A6V10316241_a_en 30.09.
Structure and functions 4 NK8237 hardware 1 2 X1 X2 X3 3 X101 X102 X103 X104 4 X105 X111 Internal DIP switch and jumpers (NKM8001-A2 mainboard) Item 4.1.4 Name Description 1 S101 DIP-Switches 2 S1 Reset button 3 S2 Tamper switch 4 X115 When closed, it disables the box tamper alarm. Serial interfaces The NK8237.2 model is equipped with two serial lines available on the main board.
4 Structure and functions NK8237 hardware 3 NC The input signals can be used for acquiring external power supply supervision lines, e.g. for the supervision of the fire system power supply. Note that this is alternative to the DF8090 power supply supervision (see I2C interface: DF8090 power supply supervision [➙ 20]). X102 onboard inputs. Pin 4.1.
Structure and functions NK8237 hardware 4 PW MAINS 1 AC/DC LOW BATT BATT FUSE 2 DF8090 front panel Item Description 1 LEDs. 2 I2C connector to I/O modules. See Figure NK8237 power supply (see NK8237 hardware installation [➙ 23]) for the power supply connections. 4.1.7 Ethernet interfaces The NK8237 main board is equipped with two Ethernet interfaces.
4 Structure and functions NK8237 hardware 4.1.8 USB interface The NK8237 main board is equipped with a USB interface you can use to log data about network communications on a USB mass storage device (see Network Connectivity Guide, document no.A6V10359485). 4.1.9 SD card The NK8237 mainboard is equipped with a 16 GB SD card. The SD card slot is located below the CPU module and can be accessed only by removing the plastic housing.
Hardware installation NK8237 hardware installation 5 5 Hardware installation There are various possible installation scenarios. Namely: Installation of NK8237 in existing cabinets. a. DIN-rail mounting (typical) in plastic housing. b. Mounting of the NK8237 board in the control unit housing using card holders (NKA8011-A1 required). Installation of a complete NE8000 cabinet including the NK8237 unit.
5 Hardware installation NK8237 hardware installation Top view Back 1 2 3 4 5 6 7 8 NK8237 electrical interfaces (top view) Item Name Description 1 X1 USB 2 X2 Ethernet 2 3 X3 Ethernet 1 4 X101 1 output 5 X102 3 inputs 6 X103 Power supply 7 X104 RS485 (in place of COM1) 8 X105 RS485 (in place of COM2) Bottom view 1 2 Serial RS232-interfaces (bottom view) Item Name Description 1 COM 1 In place of X104. 2 COM 2 In place of X105.
Hardware installation NK8237 hardware installation X103 Power supply 5 X104 X105 RS485-1 RS485-2 POWER SUPPLY DF8090 BATTERY Vin 27Ah 12V Batt Vin = Voltage In Vout = Voltage Out Batt = Battery Vout NK8237 power connections WARNING There is a risk of explosion if the battery is replaced with an incorrect battery type. Use 27Ah 12V batteries. Dispose of the used battery at a recycling point in accordance with local environmental standards and regulations. X103: Power Supply Power connections.
5 Hardware installation NK8237 hardware installation 8 – X2/X3: Ethernet Connector A standard RJ45 connector connects Ethernet. Category 5 or 6 UTP cabling is best suited. Ethernet connections. Pin Assignment 1 TX+ 2 TX– 3 RX+ 4 n.c. 5 n.c. 6 RX– 7 n.c. 8 n.c. X101: Onboard I/O (Output Relay) Onboard I/O (output relay). Pin Assignment 1 Common 2 NO output 3 NC output X102: Onboard I/O (Inputs) Onboard I/O (inputs).
Hardware installation NE8000 cabinets 8 CTS 9 RI 5 DIN Rail Installation The modules are supplied in a plastic box that can be easily attached to the DIN rail by hooking it on the top of the rail and pressing it in on the opposite side. To detach the box, pull downward on the tab located at the rear of the module. The I/O modules are mounted the same way. Note: Before removing the box, carefully disconnect the flat cable (bus) of the I2C module, as well as the power supply cables.
5 Hardware installation NE8000 cabinets 5.2.1 NE8000 hardware requirements Environmental requirements The cabinets should always be installed in a clean and safe environment, away from dust, high temperature and humidity, vibrations and impacts. Conditions and power supply should match the specific requirements given in the Technical data section of the NK8237 datasheet. NE8001 power requirements.
Hardware installation NE8000 cabinets 5 WARNING Careful attention should be paid to the correct connections of VAC power lines. Input VAC 1.
5 Hardware installation NE8000 cabinets Wiring (1) – Front view of cabinet (arrow indicates cut-out holes) Wiring (2) – Entrance hole indicated by arrow 30 Building Technologies Fire Safety & Security Products A6V10316241_a_en 30.09.
Software installation Installation checklist 6 6 Software installation The software installation includes the following: Composer and basic tools for system configuration. Additional tools: NW8202 (for IP configuration download), NW8204 (for maintenance and diagnostic), NK823x Web Server (for NK8237 diagnostic information and IP configuration). 6.
6 Software installation Launching Composer 6.3 Launching Composer Do one of the following: - Launch Composer through the Start menu: Start > Programs > DMS8000 > Composer. - Launch Composer by selecting the shortcut icon on your desktop, if available. When you start Composer for the first time, the following window displays: Composer server selection Note: To see this window every time you start Composer, deselect the Hide this dialog check box.
Software installation NK823x Web Server 6 After you make your server selection, and for all subsequent times when you start Composer, the Projects Management window displays: Projects Management window The Project Market Package version is indicated in parentheses. Note 1: To access the Projects Management window from an open project, select Tools > Projects Management from the Main menu.
6 Software installation NK823x Web Server 4. Click Login and type the default username and password (see Table NK823x Web Server login profiles for available login profiles). At first access or after a reset of all passwords, the NK823x Web Server requires you to change the password. 5. If required, type a new password, then click Login. Note: To reset the username, password, and IP addresses to their default values, set the dip-switches S101-1 and S101-2 to ON and press the reset button.
Software installation NW8202 IP configuration download tool 6.5 6 NW8202 IP configuration download tool The NW8202 is used to download the IP configuration data to the target NK8237 units. The NW8202 Tool allows a unique IP configuration to be assigned to the NK8237(s). NW8202 should be installed on the PC used to send the IP configuration to the NK8237s prior to shipment, or remotely after shipment (usually the Technician’s PC). 6.5.1 NW8202 hardware requirements 6.5.
6 Software installation Secure communication for web services 6.6.1 NW8204 hardware requirements 6.6.2 NW8204 software requirements 6.6.3 Pentium-class PC hardware or higher Ethernet network interface adapter (IEEE 802.3, 10Base-T or 100Base-TX) 10 MB Free Disk Space 128 MB RAM (recommended) Windows XP Professional or higher operating system Network Configuration including TCP/IP protocol NW8204 installation You can install the NW8204 tool when you install the DMS.
Software installation Secure communication for web services 6 Here is how you can configure the browsers to trust the DMS8000 self-signed certificates: Firefox Add a security exception: – Open the browser to your server using HTTPS – When the warning message displays, expand I Understand the Risks – Click Add Exception – Click Confirm Security Exception Internet Explorer Install the self-signed certificate in the trusted certification list: – Open the browser to your server using HTTPS – When the warn
7 Configuration Configuration checklist 7 Configuration The following picture gives an overview about the configuration workflow. Engineering tools Sinteso Works Composer 3rd party configuration tool SiB-X BACnet/IP Automation level CSV Ethernet GAP ETH1 Modbus Slave BACnet client BACnet server Modbus Master Modbus RTU (RS-232) FC2020 Modbus GW Modbus device Field level Engineering data export Configuration download There are basically three configuration steps: 1.
Configuration Configuring IP settings via the NK823x Web Server 2. 3. 4. 5. 6. 7. 7 In Composer, create [➙ 41] the NK8237 project. Create [➙ 45] the Modbus system. Create [➙ 45] the NK8237 gateway. Configure [➙ 50] the fire network. Customise [➙ 59] the Modbus interface. Download [➙ 63] the configuration to the NK8237 via Composer. Testing and commissioning tasks 1. Test [➙ 68] the configuration. 2. Troubleshoot [➙ 69] and maintain the system using the NW8204 Tool. 7.
7 Configuration Configuring IP settings via NW8202 Configuring IP settings via the NK823x Web Server 7.3 Configuring IP settings via NW8202 This configuration must be performed before the NK8237 can be configured at the client’s site. This procedure details how to send the IP configuration information; that is, the IP address, Subnet mask, and Default address to the NK8237 via the NW8202 Tool.
Configuration Configuring IP settings via NW8202 7 NW8202 IP configuration download tool 7. Click Download. The Download Procedure window is displayed. 8. Follow the instructions displayed. Note: The network cable has to be connected to the NK8237 Ethernet port 1 or 2 depending on the IP address you have set in the service PC (to locate the correct Ethernet port, see Ethernet interfaces [➙ 21]).
7 Configuration Creating a new NK8237 Composer project 7.4 Creating a new NK8237 Composer project You can create a new NK8237 project using a predefined template. New NK8237 project using the predefined template Depending on the DMS8000 installation option you chose, you can also create an empty project, which have to be manually configured. Composer light version: Composer GW Tool (NK8237) If you chose the Composer GW Tool (NK8237) light version, proceed as follows: 1.
Configuration Creating a new NK8237 Composer project 7 Starting a new project: the New button Composer standard version If you chose the Composer standard version (Composer and Subsystems Tools, Stand-alone (MM8000) or Stand-alone Station (MK8000)), proceed as follows: 1. Click the Restore button in the Projects Management window. The Restore window displays. 2. Click the Browse button in the line corresponding with File to be restored. The Select Restore File window displays. 3.
7 Configuration Creating a new NK8237 Composer project Starting a new project: by restoring a saved Composer project backup Using the New button in the Projects Management results in different project types according to the installation option you chose: Composer and Subsystems Tools. A new NK8237 empty project is created. You have to configure the system starting from the section Creating the Modbus system(s) [➙ 45]. Stand-alone (MM8000) or Stand-alone Station (MK8000).
Configuration Creating the Modbus system(s) 7.5 7 Creating the Modbus system(s) This configuration task is performed in Composer on a project created for the NK8237 gateway starting from an empty template. Note: The creation of the Modbus system is the first step of the NK8237 configuration. Failing to create the Modbus system at the very beginning prevents you from configuring the fire system and the rest of the project. 7.5.1 Modbus system creation procedure Adding the folder for the Modbus system 1.
7 Configuration Creating the NK8237 Gateway 5. Select the Node tab. 6. In the NK Type, select 3- NK8237. 7. In the File transfer Setting section, if required (see Downloading the NK8237 [➙ 63]), click the Enable secure download checkbox or select the FTP Mode (Active/Passive). 7.6.2 TCP/IP Modbus configuration procedure Configuring the NK8237 for Modbus TCP/IP 1. Select the NK8237 node and expand the subtree. 2. Select the Ethernet node. 3. Select the Node tab. 4.
Configuration Creating the NK8237 Gateway 7 Routing table configuration Checking the routing table The configuration has been downloaded to the NK8237 unit. 1. Select the NK8237 node. 2. In the Routing tab, click the Get Info button to upload the routing configuration from the selected NK8237 unit. - The updated information populates the list in the Routing Info section. 3. Check that the uploaded table actually matches the configured table.
7 Configuration Creating the NK8237 Gateway Routing table upload and check Using the dynamic routing Dynamic routing makes use of the Open Shortest Path First (OSPF) protocol. OSPF automatically manages the shortest routing paths available in complex networks. To enable dynamic routing, proceed as follows: 1. In the Routing protocol section of the Routing tab, select the Enable dynamic routing (OSPF) check box.
Configuration Creating the NK8237 Gateway 7 Enabling dynamic routing Configuring the Modbus LAN connectivity 1. Select the NK8237 node and expand the subtree. 2. Select the Protocols node. 3. In the toolbar on the left, select the Modbus Protocol icon (yellow). The Modbus protocol node is created under the Protocols folder. By default, the new node is named “Modbus protocol #1”. 4. Select the new Modbus Protocol node. 5. Drag and drop the selection to the Ethernet node above.
7 Configuration Configuring the Fire network 5. Select the new Modbus Protocol node. 6. Drag and drop the selection to one of the NK8237 COM ports. A link node is created under the COM port node. In the Node tab, the Serial parameters section contains the communication settings. By default the physical communication is set as follows: 19200, E, 8, 1. 7. If necessary, modify the Serial parameters in the Node tab of the link node. 8.
Configuration Configuring the Fire network 7 Importing the FS20/FS720 configuration metafile (SiBX) 1. Select the FS20 node. 2. Select Tools > Import in the Composer menu to start importing. The software presents a browsing window to search for the file to import (a SiBX file with extension XML is expected). 3. Using standard Windows controls, do the following: - Locate the XML file. - Select it and click Open.
7 Configuration Configuring the Fire network Example of FS20 System BACnet settings Example of FS20 Station BACnet settings Setting the FC20xx/FC72x Ack/Reset mode Acknowledgement and reset commands can only be set as general actions in the Modbus gateway. This means that the commands apply to all the pending events of the affected control unit. 1. Select the FC20xx/FC72x Node tab. 2. Make sure to select the General Acknowledgement and General Reset options (default setting).
Configuration Configuring the Fire network 7 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.
7 Configuration Configuring the Fire network 7.7.3 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.
Configuration Configuring the Fire network 7 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.
7 Configuration Configuring the Fire network 192.168.2.1 to 254. Instead, Destination = 192.168.2.10 and Netmask = 255.255.255.0 define the single IP address 192.168.2.10. - 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.
Configuration Configuring the Fire network - 7 Time-To-Live (default is 1800, 0 means permanent; it normally should not be changed). 9. If the NK823x acts as BBMD, you have to configure the BBMD settings in the NS8011 BACnet Driver node: 7.7.4 - 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.
7 Configuration Configuring the Fire network 7.7.5 STT20 BACnet connection to NK823x All STT20 fire panels must be linked to the NK823x Modbus Gateway. Proceed as follows: 1. Select and expand the NK823x Ethernet node to display the BACnet Client Protocol. 2. Select the node of the first STT20 panel. 3. Drag and drop the selection to the BACnet Client Protocol node. A new node appears in the tree under the protocol representing the link. 4.
Configuration Customising the Modbus Interface 7.8 7 Customising the Modbus Interface In the Modbus Master node, a number of configuration settings can be customised related to general NK8237 gateway parameters as well as to the address of Modbus devices and data tables. Note: The NK8237 handles a number of data tables to implement the Modbus communication at application level. A detailed documentation of these tables is provided in the NK8237 Interface Specifications guide (document no. A6V10316242).
7 Configuration Customising the Modbus Interface 7.8.2 Time synchronization The time synchronization is important for setting the appropriate time stamp on the exchanged data messages. The NK8237 can handle the time synchronization in two ways. It can: 1. Receive date & time synchronization from the Modbus master station OR 2. Acquire date & time from the FS20 system every day at a given time General parameters configuration procedures Configuring the command level 1. Select the Modbus Master node. 2.
Configuration Customising the Modbus Interface Note: Do not select the Power Supply Supervision 7 option for the onboard inputs even if the signals are used for this supervision purpose. Instead, create the 3 generic inputs and then customise the description texts appropriately. The Power Supply Supervision configuration option, which globally defines the input signals, is currently not supported by the NK8237. Configuring the Time Synchronization mode 1. Select the Modbus Master node. 2.
7 Configuration Customising the Modbus Interface 3. In the bottom part of the Device section, modify the Modbus Base Address values as needed. Make sure to define a consistent address scheme and avoid any conflicts. Configuring the object offset address 1. Select the Modbus Master node. 2. Select the Address tab. 3. In the Device files, select the panel you want to modify. 4. Click the Edit Address button. The Address table is refreshed and presents the list of objects mapped for the selected panel. 5.
Configuration Configuring the relay output 7.9 7 Configuring the relay output Configuring the relay output The relay output can be activate by cable disconnection on Ethernet ports and by other NK8237 failures, such as low memory, logging failures and software errors. To enable the relay output for diagnostic purpose, proceed as follows: 1. Select the NK8237 node and expand the subtree. 2. In the toolbar on the left, select the Onboard I/O icon A new Onboard I/O node appears. . 3.
7 Configuration Downloading the NK8237 Standard FTP or secure download The download can be based on a standard FTP file transfer (available in active or passive mode) or secured by a dedicated protocol to ensure data privacy. To enable the secure download or to set the FTP mode, select the related option in the Node tab of the NK8237 node. If enabled, the secure download makes use of the TCP port 20500 instead of the ports 20 and 21 required by FTP. 7.10.
Configuration Downloading the NK8237 7 Note: You can check the current fimware version on the Tools tab of the NK8237 node by pressing the Read All button. 7.10.3.1 DMS8000 network infrastructure configuration Adding the download communication driver 1. Select the main node of the project. 2. In the toolbar on the left, click the Generic Template icon . A new folder is added to the project structure. By default, the new node is named “Generic Node #1”. 3. Rename the folder node and enter e.g.
7 Configuration Downloading the NK8237 8. Drag and drop the selection to the NS8011 BACnet Driver node. A link node is created under the driver node. 7.10.3.2 NK8237 firmware download Downloading a firmware update 1. Select the Download tab of the NS8011 Driver node. 2. In the Firmware list, select the version you want to download. Note: You add and remove versions in the Firmware list by selecting them and using the Add and Remove buttons. 3.
Configuration Downloading the NK8237 7 – – – – Kernel Version: Linux version and release date. Factory Burning Date (when the product burned-in). EEprom information: event logging and counters. Log Status: active, inactive, active after on-the-fly configuration changes have been set (by NW8204 tool). – Firewall Status: enabled, disabled. – Routing Status: enabled, disabled. Getting the unit status (point values). 67 Building Technologies Fire Safety & Security Products A6V10316241_a_en 30.09.
8 System test 8 System test General checks on NK8237 The power supply, vital functions, and diagnostic state of NK8237 can be checked on the front panel. On the Modbus interface, the LifeCheck register provides a incremental counting as long as the NK8237 communication with the fire system and with the Modbus station works properly. For more advanced diagnostics, see Maintenance and diagnostics [➙ 69].
Maintenance and diagnostics Kernel update 9 9 Maintenance and diagnostics 9.1 Kernel update The NK8237 Kernel is the main component of the operating system, which acts as a bridge between the application and the hardware level. In certain conditions, it may be necessary to update the Kernel, following specific instructions of the technical support. In such cases, you can use the NK8000Kernel_Update Setup.msi tool that is available in the NK8000 - Support Tools folder of the DMS8000 DVD.
9 Maintenance and diagnostics SNMP monitoring 9.2 SNMP monitoring The NK8237 units can support the SNMP protocol (Simple Network Management Protocol) to enable remote stations to monitor the units for conditions that may require administrative attention. Using the SNMPv1 (RFC 1155-1157) on the UDP port 161, the NK8237 provides two sets of internal information variables using the community IDs listed here below that enable the access to the MIB (Management Information Base) namespace.
Maintenance and diagnostics The NW8204 maintenance and diagnostic tool 9 (recommended – read-only privileges). - Administrative user: call customer support for username and password (read/write privileges). Case sensitive – enter letters in lower case only. NW8204 window (installed GUI) 2. Insert the NK IP Address. Note: Inserting an incorrect IP address causes the following window to appear. If you receive this message, select OK and re-type the IP Address.
9 Maintenance and diagnostics The NW8204 maintenance and diagnostic tool 1 2 3 6 4 7 5 8 NW8204 window with open connection (installed GUI) Item Name Description 1 Change User Select to display user login window (see step 1). 2 About Displays the version of the NW8204 tool. 3 Local File Browse for a local copy of DIAGNO.LOG or EEPROM.LOG to analyse/troubleshoot a remote NK82xx (admin user only). 4 Set Default IP Address See step 2.
Maintenance and diagnostics The NW8204 maintenance and diagnostic tool 9.3.2 9 File commands These commands are meant for remote technical maintenance and diagnostic of the NK8237 units. The commands apply to the file selection active in the list on the left hand side of the screen. Download file Transfer the selected file from the NK8237 . Upload file Transfer the selected file to the NK8237 (to upload diagnostic files see Uploading diagnostic files [➙ 76]).
9 Maintenance and diagnostics The NW8204 maintenance and diagnostic tool Setting date and time NK Vitality Opens a window, which shows the current status of the NK8237 point image. NW8204 Vitality window The window can be updated manually by pressing the Refresh button. You can use it to check if status changes are sent correctly from NK8237 (for example from the tamper switch). Read DLL Version Reads all subsystems configured.
Maintenance and diagnostics The NW8204 maintenance and diagnostic tool 9 Port number request A possible port number to check is 502 (Modbus). Click OK to check the port number. At that point, the associated field shows the type of information found (e.g. Last IP connected) and you can to use the field arrow controls to show the actual IP address. Note: If the IP address shows ‘0.0.0.0’, no PC was connected to that port. Read HW version Reads the NK8237 hardware version (NKM8001-A1, NKM8001-A2, …).
9 Maintenance and diagnostics The NW8204 maintenance and diagnostic tool Read Routing Status Reads the NK8237 routing status: Enabled, Disabled. 9.3.4 Uploading diagnostic files Diagnostic file purposes The purpose of these files is to record messages of what has taken place with the NK8237 to make it easier to determine if something is wrong, or if something important has taken place. Diagnostic file description DIAGNO.
Maintenance and diagnostics The NW8204 maintenance and diagnostic tool 9 17 EV_EEPROM_NEW_DATE_TIME Date and time changed over delta threshold 18 EV_EEPROM_RESET Reset command 19 EV_EEPROM_EMERGENCY Restart in emergency mode 20 EV_EEPROM_FTP_SESSION FTP session opened 21 EV_EEPROM_CONFIG_CHANGE Configuration file changed 22 EV_EEPROM_SW_CHANGE Software version changed 23 EV_EEPROM_CPU_CHANGE CPU changed 24 EV_EEPROM_ETH_PNP_UPDAT E Ethernet EEProm update 25 EV_EEPROM_ETH_PNP_ERROR
9 Maintenance and diagnostics The NW8204 maintenance and diagnostic tool The browsing window opens. 3. Choose where you want to save the file(s) and select Save. 4. Select Close Connection. If you do not close the connection, you will automatically be timed out in five minutes. Note: The diagnostic files can be sent to customer support for analysis. Once analyzed, you will be instructed what to do to resolve your problem. 9.3.
Maintenance and diagnostics The NW8204 maintenance and diagnostic tool 9 Configuring the log upload Uploading log data Note: If the data upload procedure seems to require a too long time to be accomplished, you can abort the procedure by clicking the Abort Log Upload button. Note: The log file can be imported as CSV file in a spreadsheet application in order to be analyzed by expert users (Technical Support).
9 Maintenance and diagnostics The NW8204 maintenance and diagnostic tool Setting the log storage WARNING Removing the USB key while the logging is enabled (without using the Safely Remove command) may cause the unit to restart or block (a manual restart is then needed).
Maintenance and diagnostics The NW8204 maintenance and diagnostic tool 9 Configuring logging function on the fly Note: Resetting the unit restores the original logging configuration saved in Composer. 9.3.6 Menu "Send Default Configuration File" Sends a default configuration file containing only the new IP-configuration to the NK8237.
9 Maintenance and diagnostics The NK823x Web Server Note: Two download options are available in the Download Mode section: FTP (default) or Secure Download (encrypted data transmission that makes use of TCP port 20500). 9.
Maintenance and diagnostics The Modbus Client simulator 9 with typically being C:\Program Files\... The tool software includes the Modbus Client.exe executable and few more utility files. It is also available on the DMS8000 DVD folder without installing DMS8000: simply copy the Modbus Client folder on your PC. Starting the simulator No direct link is available from the Windows Start menu to start the tool.
9 Maintenance and diagnostics The Modbus Client simulator Modbus Simulator Window On the top, the menu command list includes: File, to import the Modbus tables and leave the program. Search, to look for specific objects. Connection, to configure the TCP/IP or the serial RTU Modbus connection. Tools, including various useful commands. View, to enable the full view. About, to display program version and access online help.
Maintenance and diagnostics The Modbus Client simulator 9 Control Commands in the WordTables tab File menu The File menu includes the following commands: Import CSV, to import the Modbus mapping tables created by Composer. Both MP4.40 and MP4.50 formats are supported (automatic detection), but MP4.40 map files need to be manually modified before the import procedure. Last imported CSV, to quickly access the latest CSV file for a new import. Exit, to close the tool.
9 Maintenance and diagnostics The Modbus Client simulator Communication Settings, to select the TCP/IP or Serial RTU type and set the related parameters: IP address and TCP Port for TCP/IP, or COM port, Baud rate, and Data/Parity/Stop bits for serial RTU. Start / Stop the Modbus communication to poll the OPC server.
Maintenance and diagnostics The Modbus Client simulator 9.5.2 9 Working with the Simulator This section illustrates the simulation procedures in simple step-by-step instructions. 9.5.2.1 Importing the Modbus maps Modbus map import procedure The DMS8000 software has been installed on the simulation PC that will be connected to the NK823x Modbus server over a LAN or a serial connection.
9 Maintenance and diagnostics The Modbus Client simulator description in the Field Device column (see Figure Matching subsystem ID and Modbus Slave Address). 4. Select the first column in the CSV map file and replace all the ID values with the corresponding Modbus Slave Addresses by using the Replace command. Be sure not to change values in columns others than the first one. 5. Save and close the CSV map file. 6. Re-import the CSV map file in the Simulator.
Maintenance and diagnostics Correcting communication failures 9 Alternatively, for Serial RTU, configure the following: - COM port, by default “1” - Baud rate, by default “19200” - Parity, by default “even” - Data bits, by default “8” - Stop bits, by default “1” Click OK 4. In the Connection menu, click Start. The Modbus communication starts between the client simulator and the NK823x. The status bar at the bottom shows the selected connection type and the connection status (connected). 9.5.2.
9 Maintenance and diagnostics Correcting communication failures Check the NK8237 Check power, vital function, and diagnostic state on the respective LED, which is located on the front panel. Note: If you need to modify the IP address because of a network change, you might want to reset the device back to factory configuration by setting DIP-switch 1 or 2 to ON (see Internal DIP switches [➙ 17]) and then connect on the known address to change the IP address.
Maintenance and diagnostics Correcting communication failures 9.6.2 9 Fire systems communication problems TCP/IP network Troubleshoot the basic TCP/IP problems as described here above for the Modbus TCP/IP and using the Ping and the Traceroute buttons in the Tools tab of the NK8237 node in Composer. Make sure that all the FS20/FS720 units are reachable from NK8237. BACnet device identifier In the fire network, the BACnet/IP protocol is used.
9 Maintenance and diagnostics Correcting communication failures Note: Default value is 0 sec. 92 Building Technologies Fire Safety & Security Products A6V10316241_a_en 30.09.
Secure operation requirements 10 10 Secure operation requirements The security of systems requires appropriate planning and proper organizational procedures. Please review the following basic checklist of the issues to consider: Physical Security Access to the room and/or areas where the communication units and control stations are installed should be reserved to authorized personnel, and/or adequate protection should be put in place on the computers to prevent potential attacks or sabotage.
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 A6V10316241_a_en Edition 30.09.2014 © 2014 Copyright Siemens Switzerland Ltd Technical specifications and availability subject to change without notice.
