A6V10316241 NK8237 Installation

NK8237 MP4.
60
Modbus Gateway for Sinteso™
STT20 and Cerberus® PRO
Fire Detection Systems
Installation
Function & Configuration
Commissioning
Safety Regulations
Building Technologies
Fire Safety & Security Products
Table of contents
About this document.........................................................................................................7

1 Safety regulations ............................................................................................10
1.1 Country-specific standards.................................................................................10
1.2 Assembly and installation...................................................................................10
1.3 Commissioning and testing ................................................................................11
1.4 Disposal and recycling .......................................................................................11
1.5 Modifications to the system design and the products ........................................11
1.6 Data privacy and protection ...............................................................................11
2 Introduction ......................................................................................................12
2.1 Connectivity examples .......................................................................................12
2.2 What's new .........................................................................................................13
3 System limits ....................................................................................................14
4 Structure and functions...................................................................................16
4.1 NK8237 hardware ..............................................................................................16
4.1.1 Front panel..........................................................................................16
4.1.2 Internal DIP switches ..........................................................................17
4.1.3 Internal jumpers ..................................................................................18
4.1.4 Serial interfaces ..................................................................................19
4.1.5 Onboard I/O ........................................................................................20
4.1.6 I2C interface: DF8090 power supply supervision ...............................20
4.1.7 Ethernet interfaces..............................................................................22
4.1.8 USB interface......................................................................................22
4.1.9 SD card ...............................................................................................23
5 Hardware installation .......................................................................................24
5.1 NK8237 hardware installation ............................................................................24
5.2 NE8000 cabinets ................................................................................................30
5.2.1 NE8000 hardware requirements.........................................................30
5.2.2 NE8000 hardware installation.............................................................30
6 Software installation ........................................................................................34
6.1 Installation checklist ...........................................................................................34
6.2 Composer tool ....................................................................................................34
6.3 Launching Composer .........................................................................................35
6.4 NW8202 IP configuration download tool ............................................................36
6.4.1 NW8202 hardware requirements........................................................37
6.4.2 NW8202 software requirements .........................................................37
6.4.3 NW8202 installation ............................................................................37
6.5 NW8204 maintenance and diagnostic tool.........................................................37
6.5.1 NW8204 hardware requirements........................................................38
3
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
6.5.2 NW8204 software requirements .........................................................38
6.5.3 NW8204 installation ............................................................................38
7 Configuration ....................................................................................................39
7.1 Configuration checklist .......................................................................................39
7.2 Configuring IP settings via NW8202...................................................................40
7.3 Creating a new NK8237 Composer project........................................................42
7.4 Creating the Modbus system(s) .........................................................................45
7.4.1 Modbus system creation procedure....................................................45
7.5 Creating the NK8237 Gateway...........................................................................45
7.5.1 NK8237 creation procedure ................................................................46
7.5.2 TCP/IP Modbus configuration procedure............................................46
7.5.3 Serial Modbus configuration procedure ..............................................49
7.6 Configuring the Fire network ..............................................................................49
7.6.1 FS20 fire system .................................................................................50
7.6.2 STT20 fire system ...............................................................................52
7.6.3 NK823x BACnet Protocol....................................................................54
7.6.4 FS20 BACnet connection to NK823x..................................................57
7.6.5 STT20 BACnet connection to NK823x................................................58
7.7 Customising the Modbus Interface.....................................................................59
7.7.1 General gateway parameters..............................................................59
7.7.2 General parameters configuration procedures ...................................60
7.7.3 Modbus addresses..............................................................................61
7.7.4 Modbus address configuration procedures.........................................62
7.7.5 Export and re-import of the Modbus address map .............................62
7.8 Downloading the NK8237...................................................................................63
7.8.1 Verifying the connection to the NK8237 unit.......................................64
7.8.2 NK8237 configuration download .........................................................64
7.8.3 NK8237 firmware download procedure...............................................64
8 System test .......................................................................................................68
9 Maintenance and diagnostics .........................................................................69
9.1 Kernel update .....................................................................................................69
9.2 SNMP monitoring ...............................................................................................70
9.3 The NW8204 maintenance and diagnostic tool .................................................70
9.3.1 Launching NW8204 from DMS host ...................................................70
9.3.2 File commands....................................................................................73
9.3.3 Diagnostic functions ............................................................................73
9.3.4 Uploading diagnostic files ...................................................................76
9.3.5 Using log files......................................................................................79
9.3.6 Menu "Send Default Configuration File" .............................................82
9.4 The Modbus Client simulator..............................................................................83
9.4.1 Simulation Workspace ........................................................................84
9.4.2 Working with the Simulator .................................................................87
4
9.5 Correcting communication failures.....................................................................90
9.5.1 Modbus communication problems ......................................................90
9.5.2 Fire systems communication problems ..............................................92
9.5.3 Control unit generated a fault .............................................................92
9.5.4 Control unit won't respond ..................................................................92
9.5.5 No fault generated by network failure - MP3.15 and higher ...............93
10 Secure operation requirements ......................................................................94
5
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). For implementing the Modbus interface, you will also
need to refer to the NK8237 Modbus Interface Specifications (document no.
A6V10316242).
Scope
This document applies to the NK8237 MP4.60.
Target audience
This documentation is intended for the following users:
 Project Managers
 Project Engineers
 Commissioning Personnel
It is assumed that individuals performing the operations described in this manual have
prior expertise and training in the field of safety and security, at least a moderate level
of familiarity with the Siemens Building Technologies product line, and experience with
the installation, configuration, and commissioning of security management systems.
Documentation resource information

The DMS8000 Documentation Resource Information and Glossary Guide assembles
important information regarding documentation resources. This document contains the
following:
 Comprehensive definitions of the target audiences for Siemens FS DMS
documents
 Training program information including the Siemens intranet link
 A complete list of all available DMS8000 documents
 Instructions for how to obtain a document via the Siemens intranet using the
Siemens Asset Portal
 A map of relevant documents for each target audience group
 Customer Support links & resources
 A glossary containing definitions of all terms and acronyms used in DMS8000
documentation
To access the DMS8000 Documentation Resource Information and Glossary Guide
(document no. A6V10089056), go to the link and follow the document search
instructions below:
http://assetportal.bt.siemens.com/portal/index.html
1. In the Search column on the left, set:
- Segment: 04 Fire -3F
7
About this document
- 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.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.
Liability disclaimer for damage or injuries

Before products are delivered, they are tested to ensure they function correctly when
used properly. Siemens disclaims all liability for damage or injuries caused by the
incorrect application of the instructions, or the disregard of danger advisories. This
disclaimer applies in particular to personal injuries or damage caused by:
 Improper and/or incorrect use.
 Disregard of safety instructions in the documentation or on the product.
 Poor maintenance or a lack of maintenance.
We have checked the contents of this manual for agreement with the hardware and
software described. Since deviations cannot be precluded entirely, we cannot
guarantee full agreement. However, the data in this manual are reviewed regularly and
any necessary corrections are included in subsequent editions. Suggestions for
improvement are welcome.
Copyrights and registered trademarks

Brand or product names mentioned in this document may be names protected by
copyright law or registered trademarks of other companies. These are mentioned only
for identification purposes and have no recommendatory character in regard to the
product or manufacturer, unless otherwise stated.
Documentation Conventions
The following table lists conventions to help you use this document in a quick and
efficient manner.
Convention Examples
Numbered Lists (1, 2, 3…) indicate a 1. Turn OFF power to the field panel.
procedure with sequential steps. 2. Disconnect the power cord.
3. Open the cabinet.
One-step procedures are indicated by a bullet  Expand the Event List.
point.
8
About this document
Conditions that you must complete or must be ⊳ The report you want to print is open.
met before beginning a procedure are
designated with a ⊳. 1. Click the Print icon .
Results, after completing a step or at the end ⇨ The Print dialog box appears.
of the entire procedure, are designated with a
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. Click OK to save changes and close the dialog
box.
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 successfully
Courier New font. 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. Notes provide
additional information or helpful hints.
This is a Caution message and indicates that
Caution minor or moderate injury or property damage
may occur if a procedure is not followed.
This is a Warning message and indicates that
Warning a serious injury or a severe equipment and
property damage may occur if a procedure is
not followed.
Cross references to other information in For more information on creating flowcharts,
printed material are indicated with an arrow see Flowcharts [→92].
and the page number, enclosed in brackets:
[→92]
Modification index
Note: For versions more than four years old, please visit the Siemens Asset Portal.
Version Date Notes

A6V10316241_a_en 06.2013 NK8237 MP4.60
For details regarding updates/modifications, see What's
new [➙ 13].
A6V10316241_a_en 06.2012 NK8237 MP4.50:
– New sections: Modbus Client Simulator; Using log
files (logging on USB device).
– New Composer light version for commissioning
activities.
A6V10316241_a_en 06.2011 NK8237 MP4.40:
– New NKM8001-A2 mainboard.
A6V10316241_a_en 12.2010 NK8237 MP4.30.
9
Safety regulations
1 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. While there are no specific safety
regulations that apply to these devices, modifications made to safety/security systems
in general may present a risk to the safety of the individual performing those
modifications, as well as to the equipment itself.
If used, the NE8001 cabinet is powered with AC voltage and the required power cable
should be installed following scrupulously the instructions given in this manual.
1.1 Country-specific standards

Siemens Building Technologies products are developed and produced in compliance
with the relevant international and European safety standards. This document provides
warnings and recommendations specific to NK8000 products. Any additional country-
specific or local safety standards and/or regulations that apply concerning project
planning, installation, operation, and device disposal must also be taken into account.
Note: As for any electrical equipment, proper grounding is critical to the safe
operation as it provides a protection against electrical shocks. Before starting any
activity, be sure that the electrical installation complies with relevant regulations and
conforms to local safety standards.
1.2 Assembly and installation

The NK8237 units and NE800x cabinets should always be installed in a clean and
stable environment; see the specific requirements given in the Technical Data section
of the specific datasheets.
In particular, keep units and cabinets away from the following:
 High levels of dust
 High temperature and humidity
 Locations where it might became wet
 Vibration and impact
Also, abide by the safety regulations of the connected devices.
10
Safety regulations
Commissioning and testing
1
1.3 Commissioning and testing

 Activate security-, fire- and third party systems or devices only in the presence of
the person responsible.
 Inform people before the testing of alarm devices — consider the possibility of
panic reactions.
 Inform the alarm and fault receiving stations connected to the system before
carrying out tests.
1.4 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.
However, they contain parts (batteries) that require disposal in a controlled waste
stream according to local environmental standards and/or regulations.
1.5 Modifications to the system design and the products

Note: Modifications to a system or to individual products may cause faults or
malfunctioning.
Please request written approval from Siemens Building Technologies and from any
relevant authorities concerning intended system modifications and system extensions.
1.6 Data privacy and protection

Make sure that the configuration of the system complies with local data privacy and
protection regulations.
11
Introduction
2 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.1 Connectivity examples
Management 3rd party Modbus system

level
e.g. SCADA system
BACnet/Ethernet Modbus client Modbus TCP/IP Ethernet
Automation
GAP ETH1 ETH2
level
BACnet client Modbus server
BACnet server
NK8237
FC2020
Field level
Modbus TCP/IP connectivity
12
Introduction
What's new
2
Management
level
BACnet/Ethernet
GAP
Automation Modbus Modbus
level FT2040
ETH1 Slave Master
Alarm transmission
FCnet /
FC2040
SAFEDLINK
Modbus RTU
FC2020
FC2060 Modbus GW Modbus device
FDnet
XC10
Conv.
Modbus Serial RTU connectivity
2.2 What's new

Here is the list of modifications for new functions and software improvements.
Section Modifications
System limits [➙ 14] - FC2080 and FT2080 control unit support.
- Large Fire systems support.
Front panel [➙ 16] Vitality green LED: twice blinking if logging is
running.
Configuring the Fire network [➙ 49] STT20 integration.
SD card [➙ 23] 16 GB SD card onboard for network communication
logging.
Kernel update [➙ 69] Kernel update procedure: checking of available
memory space added.
SNMP monitoring [➙ 70] SNMP port is closed by default by the firewall.
Diagnostic functions [➙ 73] Status information for logging, firewall and routing
added.
Simulation Workspace [➙ 84] Modbus Simulator, Tools menu: new Set Date&Time
command added.
Fire systems communication problems [➙ 92] A button to execute a Traceroute command is now
available to ease commissioning activities.
13
System limits
3
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.
 Up to 12 FC20xx/FC72x control units and 10 STT20 units in FCnet topologies via
SAFEDLINK.
Detectors
 Max 10,000. This includes all the physical elements of the FC20/FC720 control
units.
Modbus device/station
Up to four Modbus protocols can be handled, via serial and/or TCP/IP connection:
 Serial connection: two links as Modbus slave in RTU mode over an RS232 or
RS485 line.
 TCP/IP connection: Modbus server for four TCP/IP client connections. Separate
Ethernet ports can be used for BACnet/IP and Modbus TCP/IP for maximum
protection of the safety network.
Up to 14 NK823x can be linked to a Modbus Master, with the limit of 64 fire panels per
Modbus Master. See the Table Modbus hosts and system limits about how many
detectors and units are supported per NK823x depending on the number of Modbus
hosts.
Note: Due to the limits of two BACnet clients per FS20/FS720 site, there is a limit of
two NK823x clients per site. For larger FS20/FS720 sites you may need to split the
site into smaller sites.
14
System limits
3
Modbus hosts and system limits per each connected NK823x unit.
Modbus hosts Detectors and units per NK823x
1 Modbus host  Max. 10,000 detectors.
 16 FS20/FS720 units
- OR -
12 FS20/FS720 units and 10 STT20 units in FCnet/SAFEDLINK topology.
2 Modbus hosts  Max. 5,000 detectors.
- OR -
- OR -
- OR -
3 FS20/FS720 units and 2 STT20 units in FCnet/SAFEDLINK topology
Interaction capabilities
Unlike other NK8000 units, the NK8237 does not support interactions.
I/O modules locally connected via I2C

Unlike other NK8000 units, the NK8237 does not support DF8000 I/O modules.
15
Structure and functions
4 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.
Left Side LED’s

The five LED’s on the left side are, from top to bottom:
Power (LED green)
Power (hardware – controlled).
Vital functions (LED green)
Software vitality:
 Blinking (1 flash): core software running.
 Blinking (2 flash): core software running and logging function active.
Tamper (LED bicolour)
Unit tamper:
 Red means tamper alarm (hardware controlled).
 Green means tamper disabled (from management station).
16
NK8237 hardware
4
Download (LED red)

Network diagnostics:
 Off: status OK.
 Blinking (1 flash): missing identification from NS8xxx.
 Blinking (2 flashes): not used.
 Blinking (3 flashes): FTP channel open (default mode; for switch settings see
Internal DIP Switches.
 On: critical/hardware fault.
Diagnostics (LED yellow)
Internal interface diagnostics:
 Off: status OK.
 Blinking (fast): booting operating system after restart.
 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.
– No NK8237 or FS20/FS720 registers reading (Modbus Master watchdog
expired).
 On: critical/hardware fault.
Right Side LED’s

The four LED's on the right side are, from top to bottom:
Name Function
Com1 Status Com1
Com2 Status Com2 Red: RX
Green: TX
Com3 (not used) Status Com3
Com4 (not used) Status Com4
4.1.2 Internal DIP switches

The internal DIP switches (S101) enable a download session via FTP using a default
IP address.
Internal switch Functions

DIP switch 1 Default mode/network access: If DIP-switch 1 is ON, an FTP connection occurs
by default on the Ethernet 1 at the default IP address 192.168.9.41.
DIP switch 2 Default mode/network access: If DIP-switch 2 is ON, an FTP connection occurs
by default on the Ethernet 2 at the default IP address 192.168.10.41.
17
4 NK8237 hardware
4.1.3 Internal jumpers

The internal jumpers are used for:
 X115: When closed, it disables the box tamper alarm.
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
NK8237 hardware
4
Internal DIP switch and jumpers (NKM8001-A2 mainboard)

1 S101 DIP-Switches
2 S1 Reset button
3 S2 Tamper switch
4 X115 When closed, it disables the box tamper alarm.
4.1.4 Serial interfaces

The NK8237.2 model is equipped with two serial lines available on the main board.
The serial port can be configured as an RS232 interface using connector COM1 and
COM2, or as an RS485 interface using connectors X104 and X105.
All lines are fully RS232 compliant and have EMC/ESD protection.
No galvanic isolation is provided; all serial lines have a common ground.
19
4 NK8237 hardware
4.1.5 Onboard I/O

The NK823x main board is equipped with three digital inputs (X102) and one relay
output (X101).
The relay output can be used for reporting a faulty communication detected by a
watchdog timeout expiration (see General gateway parameters [➙ 59]).
X101 onboard relay output.

Pin Signal Circuit
1 Common X101
2 NO
2 NO
3 NC
1
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 Signal Circuit 1 Circuit 2
(internal power supply) (external power supply)
1 Input 1 (Mains failure) X102 X102
2 Input 2 (Battery fault) 1, 2, 3
3 Input 3 (Power supply 4K7 4K7 1, 2, 3

fault) 4 4
4 Common 100R 5 100R
5
5 + Val 6 6
6 - Val
4.1.6 I2C interface: DF8090 power supply supervision

The I2C interface (X11) allows for a direct support of:
 Power supply supervision: one DF8090 power supply supervision module.
The module can be installed on the DIN-rail, next to NK8237 unit.
Note: Although it can be supported, the DF8090 is not frequently used in the NK8237
installations, which typically rely on the fire system power supply and the related
supervision, whose signals are acquired on the X102 onboard inputs. Note also that
the DF8090 signals are not reported on the Modbus interface.
20
NK8237 hardware
4
DF8090 Power Supply Supervision

DF8090 is a module designed for monitoring a 12V DC power supply. It can detect the
conditions listed below, shown on the DF8090 local panel and report them to NK8237,
and in turn to management station (see the following):
 Mains failure (no 220VAC)
 Battery low
 Power supply failure (trouble with AC/DC converter)
 Battery protection fuse blown (internal micro-fuse type MSF 3.15A/250V)
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 [➙ 24]) for the
power supply connections.
21
4 NK8237 hardware
4.1.7 Ethernet interfaces

The NK8237 main board is equipped with two Ethernet interfaces. The two RJ-45
connectors also include 2 LEDs (yellow and green) reporting the LAN status as follows:
 Yellow LED: if on, a 100 Mbps link is active.
 Green LED: flashing when data is received or transmitted.
1
Back
Ethernet connectors
Item Description
1 Ethernet 1
2 Ethernet 2
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).
22
NK8237 hardware
4
4.1.9 SD card
The NK8237 main board 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. The SD card can be used to log data about network communications (see
Network Connectivity Guide, document no.A6V10359485).
SD card slot location on the mainboard
Item Description
1 SD card slot
23
Hardware installation
5 NK8237 hardware installation
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.
Environmental requirements
The NK82xx units should always be installed in a protective housing, 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 on the specific NK82xx model datasheet.
Network requirements
 Ethernet IEEE 802.3, 10Base-T (100Base-T also possible for NK823x), RJ-45
connection
 Fixed IP address (DHCP not supported)
 Stable network with guaranteed transmission characteristics (no down-times for
maintenance, predictable network load).
For the special mounting kits, refer to the NK8000 datasheets.
WARNING
The installation must be carried out by technically qualified personnel.
5.1 NK8237 hardware installation

Installation
1. Install the NK8237 unit on the DIN rail.
2. Connect fire subsystems on the Ethernet line.
3. Connect the Modbus serial device line or the Modbus station Ethernet line.
4. If used, connect the power supply supervision module DF8090.
5. Connect power supply.
See Figure NK8237 power supply if using a DF8090 supervision module.
WARNING
Do not connect or disconnect any device when the device is powered on!
24
NK8237 hardware installation
5
Top view
Back
1 2 3 4 5 6 7 8
NK8237 electrical interfaces (top view)

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)
25
Bottom view
1 2
Serial RS232-interfaces (bottom view)

1 COM 1 In place of X104.
2 COM 2 In place of X105.
26
5
Power connections
Note the dual power supply input for redundant solutions.
X103 X104 X105

Power supply RS485-1 RS485-2
POWER
SUPPLY
DF8090
BATTERY
Vin 27Ah 12V

Batt
Vout Vin = Voltage In
Vout = Voltage Out
Batt = Battery
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.
Power supply Pin Assignment
Primary 1 +
2 Earth
3 –
N/A 4 Not used
N/A 5 Not used
27
Secondary 6 +
(optional)
7 Earth
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).
Pin Assignment
1 Input 1 (Mains failure)
2 Input 2 (Battery fault)
3 Input 3 (Power supply fault)
4 Common
5 + Val
6 – Val
28
5
COM 1, COM 2: RS232 Connectors

RS232 lines are connected to 9pin D-Sub connectors, female type.
RS232 connections.
Pin Assignment
1 CD
2 RXD
3 TXD
4 DTR
5 GND
6 DSR
7 RTS
8 CTS
9 RI
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.
Installation in Subsystem Housing Without DIN-Rail

NK8237 can be installed without the plastic box into the control unit cabinet. In this
case, the NKA8011-A1 mounting plate may be needed.
NKA8011-A1 mounting plate
29
5 NE8000 cabinets
5.2 NE8000 cabinets

NE8000 cabinet series offers compact and convenient housing solutions:
 NE8001. Metallic cabinet for easy wall-mounting, including a DIN rail and a
prewired power supply for the unit and local I/O.
 NE8002. The sole metallic cabinet with DIN rail.
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.

Item Power supply requirement
Input voltage 100-240 Vac, 50-60Hz
Input current 2A
Note: A switch-box including a bipolar cut-out (phase + neutral) is required in the

electrical installation.
5.2.2 NE8000 hardware installation

The cabinet is typically wall-mounted. A proper support must be provided for the
maximum weight (see Technical data on the NK8237 datasheet). Four supporting
screws or hooks (min. 10 mm) are required.
WARNING
Supporting wall must not be composed of inflammable material.
30
NE8000 cabinets
5
360 mm
415 mm
Cabinet installation
The VAC power supply wires (1.5 mm2) should be connected as illustrated in Figure
VAC power connection.
WARNING
Careful attention should be paid to the correct connections of VAC power lines.
Input VAC
1.5 mm2 wires
Ground
Phase
Neutral
VAC power connection
Wires pass through 20 mm (cut-out) holes at the top of the cabinet (see Figure Top
view of NE8000 cabinet), and continue behind the cabinet to pass through the rear-
side cavity to the entrance hole (see Figure Wiring (1) – Front view of cabinet (arrow
indicates cut-out holes) and Figure Wiring (2) – Entrance hole indicated by arrow)
where they should be anchored securely before being connected to the screw
terminators.
31
5 NE8000 cabinets
20 mm hole cut-outs
Top view of NE8000 cabinet
WARNING
When entering the metallic frame of the cabinet, wires should be protected by a self-
extinguishing plastic cord guard (UL94-V2 flammability rating).
(Not provided in the supply).
Wiring (1) – Front view of cabinet (arrow indicates cut-out holes)
32
NE8000 cabinets
5
Wiring (2) – Entrance hole indicated by arrow
33
Software installation
6 Installation checklist
6 Software installation
The software installation includes the following:
 Composer and basic tools for system configuration.
 Additional tools: NW8202 (for IP configuration download) and NW8204 (for
maintenance and diagnostic).
6.1 Installation checklist

Items needed for the installation
 The DMS8000 DVD
 The DMS8000 Service key (dongle) - not required for Composer GW Tool
(NK8237) setup type
 The Service key license PAK code (or the REG file that contains it) - not required
for Composer GW Tool (NK8237) setup type
Installation checklist
1. Install the Composer Software and, if required, the license key & PAK.
If necessary, you can refer to the following documentation:
– Composer Technical Manual (A6V10062401)
– MM8000 Installation, Configuration & Commissioning (A6V10062413)
– DMS8000 Network Connectivity Guide (A6V10359485)
– MM8000 Release Notes (A6V10062509)
2. Install the NW8202 tool [➙ 36].
3. If required for diagnostics, install the NW8204 tool [➙ 37].
6.2 Composer tool

Composer tool can be installed using the standard DMS8000 DVD.
If you just need to commission an NK8237, you can choose the Composer GW Tool
(NK8237) installation option, which is a light version of Composer with only the
functionalities required for commissioning. The Composer GW Tool version needs no
license.
A full-feature version of Composer is installed along with the following installation
types, all requiring a license:
 Composer and Subsystem Tools. This option installs the standard version of
Composer with all functionalities required to commissioning MM8000, MK8000 or
NK8000 products.
 Stand-alone (MM8000). This option installs the MM8000 Server and Client and the
standard version of Composer with all functionalities required to commissioning
MM8000 and NK8000 products.
 Stand-alone Station (MK8000). This option installs the MK8000 OPC Server and
the standard version of Composer with all functionalities required to commissioning
MK8000 and NK8000 products.
34
Launching Composer
6
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.
 Do one of the following:
- Click Local then OK to confirm that you want a local server connection.
- Click Browse to connect to another server.
 A Browse window displays.
Server browsing window
35
6 NW8202 IP configuration download tool
Note 1: To change a server connection at a later time, select the appropriate project
or root node in the Projects Management window tree and then select the Change
server icon (see figure Projects Management window).
Note 2: You cannot change a server connection while a project is open.
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.
Note 2: To return to the project, double-click on it in the Projects Management tree or
select it and then click Open icon .
6.4 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).
36
NW8204 maintenance and diagnostic tool
6
6.4.1 NW8202 hardware requirements

 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)
6.4.2 NW8202 software requirements

 Windows XP Professional or higher operating system
 Network Configuration including TCP/IP protocol
6.4.3 NW8202 installation

You can install the NW8202 tool when you install the DMS. You can also install it
separately on a different PC (such as a service PC) at a later time.
On a DMS8000 system, you launch NW8202 by selecting the NW8202.exe file from
the following directory:
<InstallationDir> > Utilities > NW8202
with the default installation folder being: C:\Program files\DMS8000 (assuming an
English version of Windows).
To install the NW8202 tool on a service PC, do the following:
1. Logon to computer as Administrator (for details ask network administrator).
2. Insert the DMS8000 DVD.
3. Select the Support Tools option.
4. Select Install NW8202.exe.
 Install Shield Wizard opens.
5. Follow the instructions in the installation wizard.
6.5 NW8204 maintenance and diagnostic tool

The NW8204 is a powerful maintenance and diagnostic tool, which provides
functionalities for (but not limited to) the following:
 Downloading firmware
 Setting IP addresses
 Loading default configurations
 Using available diagnostic files
Note: Part of the NW8204 tool is available in Composer (limited functionality).

For details, see the Network Connectivity Guide (document no.A6V10359485).
37
6 NW8204 maintenance and diagnostic tool
6.5.1 NW8204 hardware requirements

 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)
6.5.2 NW8204 software requirements

 Windows XP Professional or higher operating system
 Network Configuration including TCP/IP protocol
6.5.3 NW8204 installation

You can install the NW8204 tool when you install the DMS. You can also install it
separately on a different PC (such as a service PC) at a later time.
On a DMS8000 system, you launch NW8204 by selecting the NW8204.exe file from
the following directory:
<InstallationDir>\Communication Layer\NK8210WebServer\NW8204
To install the NW8204 tool on a service PC, do the following:
1. Logon to computer as Administrator (for details ask network administrator).
2. Insert the DMS8000 DVD.
3. Select the Support Tools option.
4. Select Install NW8204.exe.
 Install Shield Wizard opens.
5. Follow the instructions in the installation wizard.
38
Configuration
Configuration checklist
7
7 Configuration
The following picture gives an overview about the configuration workflow.
Engineering Sinteso Works Composer 3rd party configuration tool

tools SiB-X CSV
BACnet/IP Ethernet
Automation
level GAP ETH1
BACnet server BACnet client Modbus Modbus

Slave Master
Modbus RTU (RS-232)

FC2020 Modbus GW Modbus device
Field level
Engineering data export

Configuration download
There are basically three configuration steps:

1. Configure the fire detection with Sinteso Works (or Cerberus-Engineering-Tool)
and download the fire system. Then, export the configuration in SiB-X format.
2. Configure the NK8237 in Composer and import the SiB-X file. If requested, the
Modbus mapping can be customized. Download the configuration to the NK8237.
Export the Modbus mapping table in CSV format.
3. The Modbus device needs to be configured by the integrator based on the
information provided in the Modbus mapping table (CSV export file).
The following chapters describe the configuration steps in detail.
7.1 Configuration checklist

Verify that you have satisfied the items needed in the first checklist before proceeding
to the configuration checklist that follows.
The following abbreviations are used in the checklists:
 DMS-CG: DMS8000 Network Connectivity Guide (document no. A6V10359485)
 DMS-ICC: Product-specific (e.g. MM8000) Installation, Configuration &
Commissioning Guide
Items needed for configuration

 All FS20/FS720 Stations are equipped with the a FCA2013-A1 License key L2
(A5Q00018857) for enabling the BACnet protocol.
 FS20/FS720 System commissioned. SiB-X export file available.
 Danger Management software installed (at least Composer - see DMS-ICC).
 To set the IP address(es) on NK8237, NW8202 is required (see NW8202 IP
configuration download tool [➙ 36]).
39
Configuration
7 Configuring IP settings via NW8202
 NK8237 unit(s) must be installed.

 The network configuration must be defined, including all IP addresses, IP masks
and the default gateway.
If multiple routing is required, each route should be defined, including the
destination IP address, mask, and gateway.
 If used, the serial Modbus communication parameters should be defined.
Configuration workflow
1. If necessary, configure [➙ 40] the NK8237 IP address(es) via NW8202.
2. In Composer, create [➙ 42] the NK8237 project.
3. Create [➙ 45] the Modbus system.
4. Create [➙ 45] the NK8237 gateway.
5. Configure [➙ 49] the fire network.
6. Customise [➙ 59] the Modbus interface.
7. 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.2 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.
Note: This configuration procedure can be performed prior to shipping the NK8237 to
the client, or at a later time at the client’s site.
1. Set the Service PC IP address to 192.168.9.1 (to use the NK8237 Ethernet port 1)
or to 192.168.10.1 (to use the NK8237 Ethernet port 2) and the subnet mask to
255.255.255.0.
a) Select Start > Settings > Network and Dial up Connections (Windows XP) or
Control Panel > All Control Panel Items > Network and Sharing Center (Windows
7).
b) Double-click Local Area Connection.
c) Click the Properties button.
d) Select Internet Protocol (TCP/IP).
e) Click the Properties button.
f) Make note of the current IP address before replacing it with the new one.
2. Click OK to restart PC when prompted.
3. Remove the cover of the NK8237 to be configured (press the 4 white tabs to the
rear of the left and right sides of the unit and lift gently).
4. Open the NW8202 application by selecting NW8202.exe located in the
<InstallationDir>\Utilities\NW8202 folder.
40
Configuration
Configuring IP settings via NW8202
7
Note: On Windows 7 it might be needed to launch NW8202 with "Run as

administrator" (depending on your system security settings).
5. Select the Firmware Version NK823x.
6. Select the Download Mode: FTP (default) or Secure Download (encrypted data
transmission that makes use of TCP port 20500).
7. Enter IP address, Subnet mask, and Default gateway in the corresponding fields.
NW8202 IP configuration download tool
8. Click Download.
 The Download Procedure window is displayed.
9. 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]). You need also to set to ON the
correct DIP switch: DIP switch 1 to use Ethernet port 1; DIP switch 2 to use
Ethernet port 2 (see Internal DIP switches [➙ 17]).
Note: For direct connection between PC and NK8237, you can use either a
crossed or straight-through Cat. 5 twisted pair patch cable. In fact, NK8237
supports automatic crossover.
 While the download is being performed, the FTP Diagnostic window is
displayed with the current status of the download.
 Once the operation has been performed, a final status notification and
instruction window will be displayed.
10. Follow the instructions displayed in the final instruction window.
11. Disconnect the NK8237 from the PC, and replace the cover.
12. Reset the Service PC IP address back to the original address.
 Now the NK8237 is ready to work in the network.
13. Using an IP ping command from networked station, check that the NK8237
responds to the new address.
41
Configuration
7 Creating a new NK8237 Composer project
7.3 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. Click the New button in the Projects Management window (if Composer is already
open, you can also click File > New in the menu bar).
2. Enter the project name in the New window.
3. Click OK.
 A new NK8237 project is created based on the predefined template.
42
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. Select the file NK8237.bak in the folder:
<InstallationDir>\Sample Projects
4. Click Open.
5. In the field Project name, enter a suitable name or select an existing project using
the Browse button.
6. Click Restore.
 A new NK8237 project is created based on the predefined template.
43
Configuration
7 Creating a new NK8237 Composer project
Note: For a subsequent use, you may want to copy the NK8237.bak file in a folder
location more convenient to locate.
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). A new empty project is
created. This kind of project is not suitable for configuring an NK8237.
Note: Do not use an MM8000 or MK8000 empty project for configuring the NK8237,
which cannot be used in MM8000 or MK8000 configurations. In such cases, you can
apply the NK8232 and NK8235 units.
44
Configuration
Creating the Modbus system(s)
7
Opening the project

 To open the NK8237 project, select it in the Projects Management window and
click Open.
By default, the project main node is named “Project Node”. You can customise this
name by clicking the node and then:
 Pressing F2 and typing the new name in the node.
 Clicking the node again and typing the new name in the node.
 Selecting the Node tab on the right pane and typing the new name in the
Description field.
Note: If the project is empty, be careful not to add to the project structure any node
that is not included in the following procedures. In fact, it may not be allowed to delete
such nodes (e.g. Security).
7.4 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.4.1 Modbus system creation procedure

Adding the folder for the Modbus system
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. “Modbus System”.
Adding the Modbus Master station

1. Select the Modbus system folder.
2. In the toolbar on the left, select Network and then the Modbus Master icon .
 A new node is added to the project structure.

By default, the new node is named “Modbus Master #1”.
7.5 Creating the NK8237 Gateway

This configuration task is performed in Composer on a project created for the NK8237
gateway starting from an empty template to which a Modbus system has been added.
45
Configuration
7 Creating the NK8237 Gateway
7.5.1 NK8237 creation procedure

Adding the folder for the NK8237 gateway

3. Rename the folder node and enter e.g. “NK8237 Gateway”.
Adding the NK8237 node

1. Select the NK8237 folder node.
2. In the toolbar on the left, select the Network folder icon .

3. In the menu that appears, select the NK823x icon .
Set the NK Type to NK8237 (see the Node tab).
4. Rename the folder node and enter e.g. “NK8237 Unit”.
5. Select the Node tab.
6. In the NK Type, select 3- NK8237.
7. If required (see Downloading the NK8237 [➙ 63]), click the Enable secure
download check box.
7.5.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.
4. In the form on the right pane, you must enter:
- IP address.
- Subnet mask.
- Default gateway (optional, it may be left = “0.0.0.0” if not used).
- If NAT (Network Address Translation) is used on the network, enable it and
enter the external IP address (NAT address) of the NK8237.
Configuring the routing table

1. Select the NK823x node.
2. In the Routing tab, click the Add button to add a new route.
3. Configure the following parameters:
- Applying standard IP addressing concepts, enter Destination and Netmask to
describe the destination range on an external subnet.
46
Configuration
Creating the NK8237 Gateway
7
For example, destination 192.168.2.0 and netmask 255.255.255.0 defines any

address in the range 192.168.2.1 to 254. Instead, destination 192.168.2.10 and
netmask 255.255.255.0 defines the single IP address 192.168.2.10.
- Enter the IP address of the Gateway, on the same subnet, which can provide
connectivity for the destination subnets.
- If multiple routes are available for the same destination, use the Metric field to
indicate the cost (e.g. the number of devices along the network path) of each
route: the higher the number (cost), the lower the corresponding priority.
4. Add as many routes as required by your network configuration.
5. Check the Routing between ETH1 and ETH2 check box (available when both
Ethernet ports are used) to enable a general routing across the two lines. Note
that:
This ETH1/ETH2 routing is not required for supporting the communications across
the two Ethernet lines, e.g. between a management station network on ETH1 and
a subsystem network on ETH2. Instead, the unit-controlled routing is required to
enable the IP connectivity for other units operating on the two separated subnets.
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.
47
Configuration
7 Creating the NK8237 Gateway
3. Check that the uploaded table actually matches the configured table.
Inconsistencies will indicate a configuration error or network problems.
 At this point, you can be sure that the unit can access the external subnets over
the configured routes.
Note: Use the Ping button in the Tools tab to check the actual connectivity between
the unit and IP devices on the subnets.
Routing table upload and check
Configuring the Modbus LAN connectivity

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.
48
Configuration
Configuring the Fire network
7
5. Drag and drop the selection to the Ethernet node above.

 A link node is created under the Ethernet node.
In the Node tab, the Modbus parameters section contains the Port Number.
By default the Port Number is set to 502.
6. If necessary, modify the TCP Port Number in the Modbus parameters section of
the link Node tab.
7. Select the Modbus Protocol link under the Ethernet node.
8. Drag and drop the selection to the Modbus Master node.
 A link node is created under the Modbus Master node.
7.5.3 Serial Modbus configuration procedure

Configuring the Modbus Serial connectivity
2. Select the Serial Lines node and expand the subtree.
 The COM port nodes appear. Either of them can be used.
3. Under the NK8237, select the Protocols node.
4. 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”.
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. If RS485 is used, enable the corresponding check box in the Node tab of the COM
port node.
9. Select the Modbus Protocol link under the COM port node.
10. Drag and drop the selection to the Modbus Master node.
 A link node is created under the Modbus Master node.
7.6 Configuring the Fire network

This configuration task is performed in Composer.
The communication between FS20/FS720/STT20 (with FCGW20-02) and the NK823x
Modbus gateway is based on BACnet/IP. The following rules apply:
 The STT20, FS20 and NK823x units must share the same BACnet Virtual Network
(typically =1).
49
Configuration
7 Configuring the Fire network
 If the STT20, FS20 and NK823x units do not share the same IP subnet,
appropriate IP and BBMD settings must be configured.
 BACnet Device Identifiers must be uniquely defined for each unit including
NK823x.
Note: NK823x supports only BACnet ID's in the range from 1 to 65533.
 The Device Identifier set for NK823x must match the client ID expected by the
STT20 and FS20 configuration.
7.6.1 FS20 fire system

General FS20 prerequisites
Note: Each FS20/FS720 station needs to be equipped with a FCA2013-A1 License

key L2 (A5Q00018857) to enable the BACnet protocol.
Configuration Procedure
1. In the left-hand bar, click the Generic Template icon .
2. Select the new folder and name it in the Description field of the Node tab.
Adding the FS20 fire system node

1. Select the new folder.
2. In the left-hand bar, select the Fire Folder icon .

3. In the menu that appears, select the FS20 icon to add a new fire system node.
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.
 A new window appears, displaying the list of stations included in the system
and represented in the SiBX file.
50
Configuration
7
Selecting FC20 subsystems to import
4. Select the stations to import.

Select All to import the structure of the entire fire system, or select the individual
stations you want to import. After that, click OK.
 In a few moments, the FS20/FS720 structure is imported, all the stations and the
related nodes are represented in the Composer tree.
Note: After the import procedure, selecting the Import tab results in a page report
being displayed. This contains the detailed logs of the latest import procedure,
including all the added or removed objects.
Beyond the node structures of the stations, the import procedure acquires the BACnet
parameters set in the fire system. This information shows in the Node tab of the
FS20/FS720 System and FC20xx/FS72x stations.
Example of FS20 System BACnet settings
51
Configuration
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).
Note: The parameter settings about the Single Event Acknowledgement and Single
Event Reset are not supported by the NK8237 and should not be used
7.6.2 STT20 fire system

Configuration Procedure
1. In the left-hand bar, click the Generic Template icon .
2. Select the new folder and name it in the Description field of the Node tab.
Adding the STT20 fire system node

1. Select the new folder.
2. In the left-hand bar, select the Fire Folder icon .

3. In the menu that appears, select the STT20 icon to add a new STT20 fire
system node.
Importing the STT20 metafile

1. Select the STT20 node.
2. Select Tools > Import in the Composer menu to start the import procedure.
52
Configuration
7
 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.
 In a few moments, the STT20 structure is imported, and the node is represented in
the Composer tree.
Note: After the import procedure, selecting the Import tab results in a page report
being displayed. This contains the detailed logs of the latest import procedure,
including all the added or removed objects.
Checking STT20 BACnet settings

Specific STT20 networking information display in the Information Box provided after
the import procedure. The information list includes the IP addressing, the BACnet
BBMD configuration, and the valid BACnet clients (DMS 1 and DMS 2) managed by
the GAP station.
Note that the BACnet clients are identified in the STT20 by both a BACnet Device
Identifier and an IP address.
To read the Information Box:
1. Select the STT20 node.
Information Box populated after the XML import
53
Configuration
7.6.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.
Configuring the NK823x IP addressing

1. If this connection requires a separate LAN port, add a second Ethernet node:
a. Select the NK823x node.
b. In the toolbar on the left, select the Ethernet #2 icon .
 A new Ethernet node is created under the NK823x node.
2. Select the NK823x node and expand the subtree.
3. Select the Ethernet node to be used for the BACnet connection.
5. In the form on the right pane, you must enter:
- IP address of the NK823x.
- Subnet mask, typically related to the fire network access. See also the
following Routing Tables section.
- Default gateway, typically the GAP station IP address, it may be left = “0.0.0.0”
if not used. See also the following Routing Tables section.
- If NAT (Network Address Translation) is used on the network, enable it and
enter the external IP address (NAT address) of the NK823x.
Note: You can ignore the step above if the Ethernet port is shared with Modbus
configuration and the IP settings was already defined for Modbus.
54
Configuration
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.
For example, assuming a SAFEDLINK including 14 addresses available for fire
detection units from 192.168.10.1 to 192.168.10.14 and 14 addresses available for
fire actuation from 192.168.10.17 to 192.168.10.30, two routes can be created, as
illustrated in the following table:
Another example, including 126 addresses per subnet (192.168.10.1 to

192.168.10.127 and 192.168.10.129 to 192.168.10.254) is shown in the following
table:
In both examples, note the external address of the GAP units (IP addresses on the
NK8000 subnet), which are specified in the routing table as gateways to the fire
subnets.
For more information, refer to the guide for DMS8000 Connectivity Network
(A6V10359485).
Configuring the Routing Tables

To configure the routing table, do the following:
1. Select the NK823x node and then the Routing tab.
2. Click the Add button to add a new route.
3. Configure the following parameters:
55
Configuration
- Destination and Netmask, addressing a subnet (recommended) or a single

address according to IP addressing rules. For example, Destination =
192.168.2.0 and Netmask = 255.255.255.0 define any address in the range
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.
- If multiple routes are available for the same destination, use the Metric field to
indicate the cost (e.g. the number of devices along the network path) of each
route: the higher the number (cost), the lower the corresponding priority.
4. Repeat steps above to add as many routes as necessary.
Use the Routing between ETH1 and ETH2 check box (available when both Ethernet
ports are used) to enable a general routing across the two NK823x lines.
Note that ETH1/ETH2 routing is not required for supporting the NK823x
communications across the two Ethernet lines, e.g. between a management station
network on ETH1 and a subsystem network on ETH2. Instead, the NK823x-controlled
routing is required to enable the IP connectivity for other units operating on the two
separated subnets. Be also informed that enabling the NK823x firewall function results
in this field being handled automatically.
Configuring the NK823x BACnet/IP connectivity

2. In the toolbar on the left, select the BACnet Client Protocol icon (violet).
 The BACnet client protocol node is created under the Protocols folder.
By default, the new node is named “BACnet Client Protocol”.
3. Select the new BACnet Client Protocol node.
4. Drag and drop the selection to the appropriate Ethernet node.
5. Select the BACnet Client Protocol link under the Ethernet node.
7. In the form on the right pane, configure the BACnet parameters:
- UDP Port (must match the UDP port configuration configured in the fire GAP
unit; default value is 47808 or BAC0 hex).
- Device Identifier (must match one of the valid client identifiers configured in the
fire system; note that NK823x units do not support BACnet IDs greater than
65533).
- Virtual Network Number (the default value 1 may need to be changed if there
is already a foreign BACnet network with virtual network number 1 in place. In
all cases, remember to keep the NK823x and FS20/FS720/STT20
configuration consistent).
- Process Id (the default value 1 normally should not be changed).
56
Configuration
7
8. If the NK823x acts as BACnet Foreign Device, enable the Foreign Device check
box and configure the BBMD router settings:
- Remote BBMD IP address.
- Remote BBMD Port Number (must match the UDP port configuration
configured in the unit acting as BBMD; default value is 47808 or BAC0 hex).
- 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:
- 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 check box on the right.
- In the lower part, add the corresponding routing partner(s) in the other
subnet(s).
7.6.4 FS20 BACnet connection to NK823x

All FC20/FC720 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 FC20xx/FC72x 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. Repeat the last two steps for all the panels of the fire system.
If several stations have to be linked to the network driver, you can profit of the
Composer grid mode and link all stations in one shot. Just proceed as follows:
1. Expand the NK823x Ethernet node to display the BACnet Client Protocol.
2. Select the FS20/FS720 system node.
3. Select the Children tab.
 The list of stations appears.
4. Select all stations: click the first FC20xx/FC72x icon (in the first column, see image
below), then press the SHIFT key and click the last icon in the list. Alternatively,
you can also select one icon after the other keeping the CTRL key pressed.
5. Keeping the SHIFT or CTRL key pressed, drag and drop the selected list to the
Network Driver. Note that you may wait a little while before a link icon shows up on
the destination node.
57
Configuration
7.6.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. Repeat the last two steps for all the panels of the fire system.
If several stations have to be linked to the network driver, you can profit of the
Composer grid mode and link all stations in one shot. Just proceed as follows:
1. Expand the NK823x Ethernet node to display the BACnet Client Protocol.
2. Select the STT20 folder node.
3. Select the Children tab.
 The list of stations appears.
4. Select all stations: click the first STT20 icon (in the first column, see image below),
then press the SHIFT key and click the last icon in the list. Alternatively, you can
also select one icon after the other keeping the CTRL key pressed.
5. Keeping the SHIFT or CTRL key pressed, drag and drop the selected list to the
Network Driver. Note that you may wait a little while before a link icon shows up on
58
Configuration
Customising the Modbus Interface
7
the destination node.
7.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.7.1 General gateway parameters

The general parameters include:
 Command level
This parameter defines the command access level allowed for the Modbus master
station. The option list includes:
– No command: the Modbus master station cannot send any command to the
fire system.
– Ack only: the Modbus master station can only send the Acknowledgement
command to the fire system.
– Ack, Reset: the Modbus master station can only send the Acknowledgement
and Reset commands to the fire system.
59
Configuration
7 Customising the Modbus Interface
– Ack, Reset, Basic command: the Modbus master station can send the
complete set of defined commands to the fire system.
 Watchdog timeout
This parameter defines a maximum delay (in seconds) for the Modbus master
station to poll the Modbus virtual devices (NK8237 and FS20/FS720 units). If the
timeout of the polling of one of the Modbus virtual devices expires, the NK8237
generates a fault condition that is reflected in the Modbus register area, in the
diagnostic LED (blinking 6 times) and, if the relay output is configured (see General
parameters configuration procedures [➙ 60]), also as a relay output activation.
 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
7.7.2 General parameters configuration procedures

Configuring the command level
1. Select the Modbus Master node.
2. Select the Host tab.
3. In the Command Level field, choose the required access level.
Configuring the watchdog timeout

3. In the Watchdog Timeout field, enter the maximum polling delay in seconds.
Configuring the relay output (communication fault)

2. In the toolbar on the left, select the Onboard I/O icon .

 A new Onboard I/O node appears.
3. Select the new I/O Onboard node.
4. In the toolbar on the left, select the Relay Output icon .

 A new Relay Output node appears under the Onboard I/O node.
The relay is configured for communication diagnostics.
By default, the node is named “Relay Output”.
For the onboard output connection see Onboard I/O [➙ 19] (Table X101 onboard relay
output).
Configuring the inputs (for power supervision or other purposes)

2. Select the new I/O Onboard node.
60
Configuration
Customising the Modbus Interface
7
3. In the toolbar on the left, select the Generic Input icon .

 A new node appears under the Onboard I/O node.
By default, the new node is named “Generic Input #1”.
4. If necessary, click one or two more times the Generic Input icon .
 New Generic Input nodes appear under the Onboard I/O node.
By default, the new nodes are named “Generic Input #2” and “Generic Input
#3”.
For the onboard input connections see Onboard I/O [➙ 19] (Table X102 onboard
inputs).
Note: Do not select the Power Supply Supervision 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

3. In the Time Synchronization fields, defined the required mode:
- If the time synchronization is received from the Modbus master station, check
the Host enable check box.
- If the time synchronization is acquired from the FS20, uncheck the Host enable
check box and enter the time of the daily acquisition (HH:MM).
7.7.3 Modbus addresses

The address parameters include:
Modbus devices slave address

These parameters define the Modbus slave addresses of the fire units mapped. By
default, the device address corresponds with the node number in Composer.
Modbus tables base address

These parameters define the base address of the data tables that collect the fire
system status in Modbus registers.
For detailed information about these tables, refer to the NK8237 Interface
Specifications guide (document no. A6V10316242).
Fire object offset address

These parameters define the offset address of the individual objects in the data tables.
61
Configuration
7 Customising the Modbus Interface
7.7.4 Modbus address configuration procedures

Configuring the device address
3. In the top part of the Device section, modify the Modbus Slave Address values as
needed. Make sure to define a consistent address scheme and avoid any conflicts.
Configuring the table base address

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

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. In the Address table, modify the Modbus Address values as needed.
Make sure to define a consistent address scheme and avoid any conflicts. The
configuration tool will anyway verify that no overlap occurs and prompt you with an
error message whenever a modification causes such an overlapping.
Note: Large modifications of the offset addresses can be better performed using a
spreadsheet application. To do so, export and then re-import the address map as
described in the section below.
7.7.5 Export and re-import of the Modbus address map

The entire address map can be exported into a CSV file for customizing it, e.g. with
MS-Excel, and then re-importing it into the Composer environment.
When modifying the addresses, make sure to be consistent and avoid any conflicts.
Proceed as follows:
Exporting the address map

1. Right click the Modbus Master node and select Node Commands.
2. Select the Export to CSV command.
62
Configuration
Downloading the NK8237
7
3. In the browsing window that appears, define the location and name of the file, and
click Save.
 In a few moments, the CSV file is created.
Note: The export command also generates a TXT file containing information about
supported Modbus functions.
For detailed information about the CSV file structure, refer to the NK8237 Interface
Specifications guide (document no. A6V10316242).
Importing the address map

1. Right click the Modbus Master node and select Node Commands.
2. Select the Import from CSV command.
3. In the browsing window that appears, locate the file to import and click Open.
 In a few moments, the CSV file is imported and the address map updated.
A message on the screen indicates the correct execution of the import.
7.8 Downloading the NK8237

Configuration download
The configuration download allows the Composer tool to transfer all the settings into
the NK8237 for runtime use.
Once the NK8237 unit is connected over the IP network, this operation can be quickly
performed from Composer using a right click command of the NK8237 node.
Firmware download
A firmware download may also be necessary when a new firmware version needs to
be installed. Unlike the configuration download, the firmware download requires a
software communication infrastructure between the Composer tool and the NK8237.
This is realized based on the standard DMS8000 NS8011 BACnet driver, which has to
be added to the Composer project along with the associated DMS8000 station and
channel folders. Once this is in place, the NK8237 download can be performed
applying the usual techniques of the NK8000 family (see NK8237 firmware download
procedure [➙ 64]).
Standard FTP or secure download

The download can be based on a standard FTP file transfer or secured by a dedicated
protocol to ensure data privacy.
To enable the secure download, select the related option in the Node tab of the
NK823x node. If enabled, the secure download makes use of the TCP port 20500
instead of the ports 20 and 21 required by FTP.
To enable the secure download see NK8237 creation procedure [➙ 46].
63
Configuration
7 Downloading the NK8237
7.8.1 Verifying the connection to the NK8237 unit

The download requires that the TCP/IP connection between the host PC and the unit is
working properly. To check the connection, when required by the download
configuration procedures, proceed as follows:
1. Run the Command Prompt.
From the Start menu:
Start > Programs > Accessories > Command Prompt
 A black window appears.
2. Type:
ping n.n.n.n
with n.n.n.n being the 4-number IP address of the unit, and press ENTER.
3. Analyse the reply message.
- If the IP connection is good, the message text looks like:
Reply from n.n.n.n: bytes=… time… TTL=…
- If the IP connection is not working for any reason, different messages may
appear (Request timed out, Destination net unreachable, etc.). In these cases,
verify the network settings and cabling and try again.
7.8.2 NK8237 configuration download

The NK8237 configuration download procedure includes:
 Verifying the connection [➙ 64] to the NK8237 unit.
 Downloading the configuration file.
Downloading the configuration file

1. Right-click the NK8237 node.
2. Select Node Commands > Download Configuration File.
 The download procedure starts.
Note: In the same menu, you can also create a backup copy of the NK8237
configuration INI file (Create INI file), which might be helpful for troubleshooting.
After the download, the NK8237 unit stops and then reboots. The restarting phase is
monitored by the Composer tool.
7.8.3 NK8237 firmware download procedure

The NK8237 firmware download procedure includes:
 Configuring the network infrastructure.
 Verifying the connection to the NK8237 unit (see Verifying the connection to the
NK8237 unit [➙ 64].)
 Downloading the firmware file and (if required) a new configuration file.
64
Configuration
7
Note: You can check the current fimware version on the Tools tab of the NK8237
node by pressing the Read All button.
7.8.3.1 DMS8000 network infrastructure configuration
Adding the download communication driver


3. Rename the folder node and enter e.g. “Download”.
4. Select the new folder node.
5. In the toolbar on the left, select the Dixie Main icon .

 A new Dixie Main node is added to the project structure.
6. Select the Dixie Main node and expand the subtree.
7. Select the Physical Configuration node.
8. In the toolbar on the left, select Stations and then Stand-alone .

 A new Stand-alone station node is added to the project structure.
9. Select the Stand-alone node.
10. In the toolbar on the left, select the Channel icon .

 A new Channel node is added to the project structure.
11. Select the Channel node.
12. In the toolbar on the left, select the NS8011 BACnet Driver .
 A new Driver node is added to the project structure.
Configuring and linking the BACnet protocol for download

3. In the toolbar on the left, select the BACnet Protocol icon (red).
 The BACnet protocol node is created under the Protocols folder.
By default, the new node is named BACnet Protocol.
 In the Node tab, the Network Parameters section contains the UDP port.
By default the Port Number is set to 47808.
4. If necessary, modify the UDP Port Number in the Network Parameters section of
the Node tab.
Note: If the BACnet UDP port is changed, the same changes should be applied in
the BACnet parameters of the NS8011 BACnet Driver node.
65
Configuration
7 Downloading the NK8237
5. Select the new BACnet Protocol node.

6. Drag and drop the selection to the appropriate Ethernet node.
7. Select the BACnet Protocol link under the Ethernet node.
8. Drag and drop the selection to the NS8011 BACnet Driver node.
 A link node is created under the driver node.
7.8.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. Select the NK8237 in the list in the upper part of the form.
Note: In order to select multiple NK8237, keep the CTRL key pressed while you
make your selections.
4. Click the button Download Firmware.
 The download procedure starts.
5. To ensure that the download completed successfully, verify that the FW
Downloaded check box contains an X.
 After the download, the NK8237 unit stops and then reboots. The restarting phase
is monitored by the Composer tool.
Downloading the configuration file from the NS8011 driver node

1. Select the Download tab of the NS8011 Driver node.
2. Select a NK8237 unit (or more) in the list in the upper part of the form.
Note: In order to select multiple units, keep the CTRL key pressed while you make
your selections.
3. Click the Download Configuration button.
4. To ensure that download completed successfully, verify that the Cfg Downloaded
check box contains X. The box is automatically unchecked after any subsequent
modification to remind you that a further download is required.
 After the download, the NK8237 unit stops and then reboots. The restarting phase
is monitored by the Composer tool.
Controlling and checking the unit status

The Tools tab of the NK823x unit provides some control commands and a screen
status report of the unit. It allows for:
 Commanding a remote reset of the unit (that will disconnect the unit for about one
minute).
 Setting date & time in the unit.
66
Configuration
7
 Executing ping and traceroute commands.

 Reading a complete status report, which includes:
– Hardware version, e.g. NKM8001-A2.
– Firmware version (available on the PC and actually installed on the unit).
– Product Identifier (ID): NK8237.
– Delivery Date & Time.
– Add-on information: list of installed add-on components.
– Hardware configuration: 2 serial ports.
– Free RAM available (bytes).
– 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
System test
8
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].
Checking the Modbus connection

The serial line state can be monitored from the LEDs of the NK8237 front panel.
A complete check can be done from the Modbus unit.
You can also run a complete check of NK823x Modbus GW functions before
connecting the Modbus unit by using the Modbus Client simulator (see Maintenance
and diagnostics [➙ 69]).
Checking the fire system

If the Modbus communication works, detailed information is provided for each fire
control unit. A complete check of the fire detection points is required before handing
over the system.
For a complete documentation of the fire point mapping, refer to the NK8237 Modbus
Interface Specifications (document no. A6V10316242).
WARNING
Please be aware of the potential consequence of a configuration mismatch between

the fire system and the Modbus master station that deals with the safety alarm
presentation and treatment. Such a mismatch can actually result in a fire alarm being
missed.
Whenever a configuration change occurs in the fire system and/or in the NK8237
gateway, make sure to thoroughly and consistently import and set up a corresponding
configuration into the Modbus head-end system.
Note that the configuration inconsistency between the fire system and the NK8237 is
detected and reported in the Modbus map (refer to the NK8237 Points register
documented in the NK8237 Modbus Interface Specifications).
68
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.
The tool is provided as a Microsoft Installer file (MSI) and can be easily installed on the
Windows system that can connected to the NK8237 unit on the IP network.
Once installed, the NK8000Kernel_Update application can be started from the
Windows Start menu. The following window appears:
Updating the Kernel
To update the Kernel:

1. Enter the IP address of the NK8237 to update.
2. Click Update Kernel.
At that point, the tool performs a number of preliminary checks. Namely:
 It verifies whether the NK8237 firmware is compatible with the new Kernel. If not, a
message will instruct you to download a new firmware and try updating the Kernel
again.
 It verifies whether the existing Kernel is older, the same, or newer then the new
Kernel and prompts you to confirm the update.
 It verifies whether there is enough free memory space to install the new Kernel. If
not, the NK8237 configuration will be temporarily removed to free memory space.
You will be prompted to choose whether to restore the configuration at the end of
the Kernel upgrade or not (the latter can be useful to save time if you are
upgrading the system and are going to download a new configuration from
Composer).
The Kernel update may take several minutes. Make sure not to power off the NK8237
unit or the Windows computer during the updating procedure.
If needed, you can show the Kernel version by clicking the About button. Note that two
Kernel versions are presented that are automatically selected for the NKM8001-A1 or
the NKM8001-A2 mainboard, respectively.
69
9 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.
 Public, providing a basic set of information
 Engineer, providing the access to the complete set of information
WARNING
The NK8237 built-in firewall closes by default the SNMP port. To enable the SNMP
protocol, select the snmp check box in the Firewall tab.
Note: The event-based notifications (trap) is not supported.
9.3 The NW8204 maintenance and diagnostic tool

The NW8204 is a powerful maintenance and diagnostic tool. In the event that a
problem occurs during or after NK8237 configuration, you use the NW8204
maintenance tool’s FTP (File Transfer Protocol) and diagnostic interface to locate
where the problem occurred so you can resolve it. This tool provides functionalities for
(but not limited to) the following:
 Downloading firmware
 Setting IP addresses
 Loading default configurations
 Using available diagnostic and log files
Since the NW8204 maintenance tool is designed mainly for customer support /
technical use, this guide covers only the most important features used for
troubleshooting.
You access the NW8204 tool by installing and then launching the application on the
host DMS.
9.3.1 Launching NW8204 from DMS host

To access the NW8204 tool, do the following:
 You need to install the NW8204 maintenance tool (via the DMS8000 DVD) on the
host DMS before proceeding, if it is not already installed.
For NW8204 installation instructions, see NW8204 maintenance and diagnostic
tool [➙ 37].
1. Select Start > Programs > NW8204 > NW8204 (executable file)
Note: On Windows 7 it might be needed to launch NW8204 with "Run as
administrator" (depending on your system security settings).
70
The NW8204 maintenance and diagnostic tool
9
 You are logged in as ‘guest’ (default user type) when the NW8204 window
appears.
- To change user type (for example from ‘guest’ to ‘admin’), select Change User
to display the Login window.
Note: There are two ways you can log in to the NW8204 tool:
- Guest user (default): user name = “guest” / password = “guest”
(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. If you want to
71
9 The NW8204 maintenance and diagnostic tool
enter the NK8237 default IP address 192.168.9.41, you can use the menu Set
Default IP Address instead of typing it.
3. Select Open Connection.

 NW8204 opens a FTP session on the NK8237 and lists all files available on the
NK8237 flash disk.
1 2 3 4 5
6 7 8
NW8204 window with open connection (installed GUI)

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 See step 2.
Address
72
9
5 Send Default See Menu "Send Default Configuration File" [➙ 82].

Configuration File
6 History log frame —
7 Error log frame —
8 Download/Upload Transferred Bytes, Percent, and Byte/Sec rate.
progress status.
Note: If you do not close the connection, you will automatically be timed out in five
minutes.
9.3.2 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]).
Delete/rename file
Delete or Rename the selected file in the NK8237.
Refresh
Update the file list.
Properties
Display the detailed properties if the selected file.
Download Reset NK
Download a file that forces the NK8237 to perform a software reset.
Edit Configuration File
Edit/View the INI file containing the NK8237 configuration.
Edit Diagno.log
Edit/View the diagnostic file (see Uploading diagnostic files [➙ 76]).
Edit EEprom.log Event.log
Edit/View the diagnostic file (see Uploading diagnostic files [➙ 76]).
9.3.3 Diagnostic functions

Reset NK
Allows you to reset an NK8237 from a remote location.
Note: This function is only available when logged in as user “admin”.
73
Save EEProm on file

Stores the content of the EEProm in the file EEProm.LOG on the NK8237 flash disk.
Set System Time
Sets the RTC (Real Time Clock) of NK8237 to the PC system time.
Set Date Time

Opens a window for setting date and time and downloads the new settings to the RTC
of NK8237.
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. Displays a dialog box with a list of configured
subsystems organised by name, number, and creation date.
74
9
Read Kernel Version

Reads the version of the Linux kernel installed on NK8237 .
Read NK Version
Reads the version of the installed NK8237 firmware (NK8237.EXE).
Read NK Date Time
Reads current settings of date and time from the NK8237 RTC.
Read HW Conf. ID
Reads the HW Configuration ID from the unit. The HW Conf. ID is used to check the
HW Configuration from a remote location:
 Serial: NKA8001-A1 or NKA8001-A2 serial port add-on board installed.
Read Memory
Displays the amount of RAM (in bytes) available on the NK8237.
Read Connected IP
Reads the IP address of the last host PC that was connected to the selected port.
Pressing this button causes the following dialog box to display:
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, …).
Note: NK8237 MP4.40 or later firmware is required.
Read PIC24FW Ver

Reads the PIC24 microcontroller firmware version.
Read WDT Status

Reads the NK823x watchdog status (enabled or disabled).
75
Read Mass Storage

Reads a mass storage device (USB mass storage device or SD card) available on the
NK8237 unit. Right-click the icon of the connected mass storage device (the icons
display in the box at right) to show the available commands:
 Show info: show information about the connected mass storage device.
 Unmount: command needed to safely remove the mass storage device.
 Set as Log storage: set the selected device (USB mass storage device or SD
card, if both are available on the system) as the active storage device.
Set Default Log
Restores the NK8237 log settings as set in Composer.
Protocol Info
Opens the NK Protocols window, which allows to configure the NK8237 logging on the
fly (see Using log files [➙ 79]).
Read Logging Status
Reads the NK8237 logging status: Active, Inactive, Active (Modified) after on-the-fly
configuration changes have been set.
Read Firewall Status
Reads the NK8237 firewall status: Enabled, Disabled.
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.LOG
This file is always present, and contains detailed technical information about the
behaviour of the software application running on the NK8237. For example, if it wasn’t
possible to open an internal queue during the initialisation phase, that message is
saved to this file.
The information in this file is not meant to be used by filed engineers on site. In case of
technical problems, the DIAGNO.LOG file can be transmitted to the technical support
for a specific analysis.
EEProm.LOG
You create this file by selecting the Save EEProm on File button. This file contains
information about the NK8237 hardware status stored on the EEProm. For example, if
it wasn’t possible to use the serial interface on COM3 because the serial add-on board
is broken, that message is saved to the EEProm.
76
9
Note: Every time you select the Save EEProm on File button, you overwrite any
existing EEProm.LOG file.
A detailed description of the EEProm log entries is provided in the table here below.
ID Message text Meaning

0 EV_EEPROM_NULL —
1 EV_EEPROM_INIT EEProm initialization
2 EV_EEPROM_START NK8000 unit restart
3 EV_EEPROM_NOT_ALIGNED EEProm not aligned
4 EV_EEPROM_NO_ETH_INIT Ethernet initialization failed
5 EV_EEPROM_TAMPER_OPEN NK8000 unit box opened
6 EV_EEPROM_TAMPER_CLOSE NK8000 unit box closed
8 EV_EEPROM_NO_SER0_INIT COM1 initialization failed
12 EV_EEPROM_SER0_ERROR COM1 error
16 EV_EEPROM_DATE_TIME Date and time changed within delta threshold
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_UPDATE Ethernet EEProm update
25 EV_EEPROM_ETH_PNP_ERROR Ethernet EEProm update failed
34 EV_EEPROM_DLL_LOAD_FAILED DLL load failure
35 EV_EEPROM_DLL_EXCLUDED DLL excluded from round-robin schedule
36 EV_EEPROM_DLL_OVERRUN DLL response time over threshold 1
37 EV_EEPROM_DLL_VER_ERR DLL version error
38 EV_EEPROM_DLL_INIT_ERR DLL initialization error
39 EV_EEPROM_DLL_OVERTIME DLL response time over threshold 2
40 EV_EEPROM_DLL_TIMEOUT DLL response time over threshold 3
41 EV_EEPROM_DLL_EVENT DLL diagnostic event
77
42 EV_EEPROM_HW_MISMATCH PIC24 microcontroller init detected a

hardware version different from version in
EEProm
43 EV_EEPROM_PIC24_FLASH_FAILU PIC24 microcontroller init failed to write the
RE microcontroller flash memory
44 EV_EEPROM_PIC24_PROGRAMM PIC24 microcontroller init wrote a new
ED firmware into the microcontroller flash
memory
45 EV_EEPROM_PIC24_WRONG_HEX PIC24 microcontroller init detected a wrong
firmware into the microcontroller
46 EV_EEPROM_HW_FAILURE Unable to retrieve information from the
EEProm or from the PIC24 microcontroller
47 EV_EEPROM_FOUND_USB USB mass storage device plugged
48 EV_EEPROM_REMOVE_USB USB mass storage device unplugged

49 EV_EEPROM_FOUND_SD SD card plugged
50 EV_EEPROM_REMOVE_SD SD card unplugged
EVENT.LOG
This file is present only after the EEProm is full for the first time. It contains (up to) the
four most recent backups of the EEProm.LOG file.
Upload of diagnostic files

1. Select one or more of the following diagnostic files:
- DIAGNO.LOG
- EEProm.LOG
- EVENT.LOG
2. Select Upload File.
 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
analysed, you will be instructed what to do to resolve your problem.
78
9
9.3.5 Using log files

NK8237 units can be configured by Composer to log data about network
communications on a mass storage device (SD card or USB mass storage device; see
Network Connectivity Guide, document no.A6V10359485). If that is the case, NW8204
allows to upload the log data and to configure on the fly the logging function.
Note: The unit is equipped with a 16 GB SD card.
Uploading log data

To upload the log data, do the following:
1. Click the Upload Log button.
2. Select the source media (Usb or SD) from the Media drop-down list in the Source
section.
3. In the Filtering Criteria section of the Upload Log window, select the filtering criteria
that fit your needs:
- Period section: you can select a time frame (select the Enable criteria check
box to enable this criterion).
- Category section: you can select the information categories you are interested
in (select the Enable criteria check box to enable this criterion).
- Miscellaneous section: you can insert various specific data to be used as
filtering criteria. Note that in this section you can also filter the data
communication direction (Input, Output or All).
4. Choose log file location and name in the Output section, by using a Windows
standard select button (a TXT file will be created).
- To split the data in several files, select the Split output file by size limit (bytes)
check box and insert the maximum bytes size for the log files to be uploaded in
the related field.
5. Click the Start Log Upload button to start the data upload.
 The upload starts and a progress bar shows the uploading speed.
79
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).
Changing the active mass storage device on the fly

If two mass storage devices are available on your system (USB and SD card), you can
change on the fly the active storage device. Proceed as follows:
1. Right-click the inactive mass storage device you want to be active.
2. Select Set as Log storage.
 The active mass storage device is represented by a floppy disk icon.
80
9
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).
Always use the Safely Remove command before removing the USB memory device!
Note: If you use the SD card as default log storage, removing an USB mass storage
device temporarily set as the active log storage doesn’t automatically set again the
SD card as the active log storage. In such a case, you need to manually set the SD
card as the active log storage.
Configuring the logging function on the fly

To configure the log files on the fly, do the following:
 You need to be logged in as ‘admin’ (see Launching NW8204 from DMS host [➙
70] about different user types).
1. Click the Protocol Info button.
2. In the NK Protocols window, select the protocol about which you want to configure
the logging function.
3. Select the check boxes you are interested in:
- The Logger Category section shows the available information categories.
- The Logger Mask section shows the information types that will be written in the
log files about every information category.
4. Click the Apply button.
 The logging function configuration is modified on the fly.
81
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.
This function allows the download of a default configuration file with new IP parameter
settings to any reachable NK8237, while NW8202 assumes that the NK8237 is set to
default IP address before downloading the new configuration.
Send default configuration file
82
The Modbus Client simulator
9
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.4 The Modbus Client simulator

The Modbus Client Simulator is a convenient tool that can act as a Modbus TCP/IP
client and serial RTU master for testing the NK823x Modbus GW functions before
connecting the 3rd party Modbus station/device.
The simulator can be used during commissioning or for troubleshooting purposes if the
actual Modbus client/master is not available or when you do not want to use it
intentionally.
Installing the simulation tool

The simulator is a Windows application that is installed by DMS8000 setup in the
following folder:
<installation folder>\DMS8000\Utilities\Modbus Client\
with <installation folder> 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.
To start the simulator, select the installation folder and launch the Modbus Client
program. For frequent use, we recommend to create a shortcut on the desktop.
More than one instance can be started and run at the same time on a PC.
Connecting the simulator

The TCP/IP connection requires LAN connectivity between the simulation PC and the
NK823x.
The IP address and port of the NK823x can be configured in the simulator.
The serial RTU connection requires a serial line between any serial port of the PC and
the NK823x.
Serial connectivity options, COM port, Baud rate, data bits and son on, can be
configured in the simulator.
Modbus data map

The simulator can import the CSV file provided by the NK823x tool. Two file formats
are supported:
 MP4.40: this CSV file format includes the Modbus objects organised in multiple
tables: Word, Compact, Bit, and Command Tables.
83
9 The Modbus Client simulator
 MP4.50 and higher: on top of the MP4.40 information, this format also contains
information about Modbus Slave Address, Field Device description, Modbus Table
name and applicable Modbus function codes.
For more information about the CSV file formats, refer to the NK8237 Interface
Specifications document, document n. A6V10316242.
9.4.1 Simulation Workspace

The Simulation tool presents a standard Windows interface including a menu, a multi-
tab data area, and a status bar.
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.
The data area is organized in the following tabs:
 Data tables tabs (when connected), to show the Modbus readings organized in
multiple tables (WordTables , CompactTables, BitTables, DataChange,
LifeCheckAndDateTime). Table contents are dynamically updated as new values
are acquired from the Modbus server. Coloured texts are used for object properties
to represent active states.
One or more objects can be selected and control commands are available for the
WordTables tab in the right-click contextual menu.
 Polling Log, to list the communication logs.
 History Log, to list the changes of state.
84
9
 CSV, to show the imported CSV file.

 Others, to support special functions to generate sequences of commands to the
NK823x server.
Note that the available sequences are pre-programmed in the Configuration.xml
file.
At the very bottom of the window, the status bar displays the type of connection
configured (Ethernet or Serial) and status (connected or disconnected).
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.
File Menu
Search menu
The search commands opens a Find dialog box that allows to search for an object
indicated by its name (in the Find what field) and optionally by the column (in the
85
Column Name field). A Find and Find Next command buttons are available as well as a
Close button to leave the search mode.
Search Menu
Connection menu
The Connection menu includes the following commands:
 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.
Connection Menu
Tools
The Tools menu includes the following commands:
 Polling Options, to enable (you can toggle each of the following options)
– Word and LifeCheckDateTime tables
– Compact Table (only with MP4.50 CSV format)
– Bit Tables (only with MP4.50 CSV format)
 Single Reads, to use single poll commands (if checked) or multiple, consecutive
readings.
 TCP/IP Auto Reconnection, to enable the client to automatically re-establish the
TCP/IP link after a connection fault.
 Log to File, to select a file where to store the Polling Log.
 Set Date&Time, to set date and time on all the imported devices (only usable
when Time Synchronization from Host is enabled in the Host tab of the Modbus
Master node)
86
9
Tools Menu
View
The View menu only includes the Full View command.
 When checked, this option enables the display of the complete number of column,
including technical information such as Subsystem ID and Node ID that are not
present in the standard view.
View Menu
About menu
The About command in this menu shows the simulation program version.
9.4.2 Working with the Simulator

This section illustrates the simulation procedures in simple step-by-step instructions.
9.4.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.
 The CSV file of the Modbus configuration (export from Composer tool) is available
and matches the current NK823x Modbus maps.
1. On the simulation PC, select the folder
<installation folder>\DMS8000\Utilities\Modbus Client\
with <installation folder> typically being C:\Program Files\...
and start the Modbus Client.exe program.
 The Modbus client window appears. The status bar at the bottom shows the
connection type and the connection status (disconnected).
2. In the File menu, select Import CSV to select the Modbus map file to import.
NOTE: You can select Last imported CSV to repeat the latest import selection and
skip the file search.
 The Select a csv file browsing window appears.
87
3. Browse in the file system to locate and select the CSV file, then click Open.
 The Select Items window appears, showing the subsystems in the Modbus
maps. The list includes the NK823x unit and the connected fire units with a
corresponding check box. By default, all units are selected.
4. Uncheck the units you do not want to import. Use the Select All and Unselect All
buttons for a global selection/deselection. When ready, click Import.
 The import process starts. In a few seconds, the data tables get populated by the
Modbus objects and appears as new tabs in the data area of the Modbus client
window.
MP4.40 format Modbus map files need to be manually modified and re-imported
(Modbus map files format from MP4.50 onwards can be imported without any
modification).
In order to modify the MP4.40 Modbus map file as needed, see the following
Updating an MP4.40 format map file.
Updating an MP4.40 format map file

 An MP4.40 format map file has been imported into the Simulator.
1. Open the CSV map file you just imported by using a spreadsheet application, such
as Microsoft Excel. The first column contains the subsystem IDs that have to be
substituted with the corresponding Modbus Slave Addresses. See the following
steps to match the correct values.
2. Open the Simulator LifeCheckAndDateTime tab. Check the subsystem IDs
corresponding to the Field Device description.
3. Open the Host tab of the ModBus Master node in Composer. Here you can match
the corresponding Modbus Slave Addresses by comparing the text 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.
This procedure is aimed only to get the correct map file for the Modbus Client
Simulator. Do not re-import the modified CSV file in Composer.
88
9
Matching subsystem ID and Modbus Slave Address
9.4.2.2 Establishing the Modbus connection

 The simulation PC is connected to the NK823x Modbus server over a LAN or a
serial connection.
 The Modbus client program is running.
 The CSV file with the configuration of the NK823x Modbus gateway has been
imported in the Modbus client.
1. In the Connection menu, select Communication Settings.
 The Select Connection Type window appears.
2. Depending on the physical link between the simulation PC and the NK823x, select
TCP/P or Serial RTU.
3. For TCP/IP, configure the following:
- IP address
- TCP Port, typically 502
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.
89
9 Correcting communication failures
 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.4.2.3 Commanding Modbus objects

 The Modbus client program is running and Modbus communication has been
established with the connected NK823X Modbus server applying the configuration
of the imported CSV file.
 You wish to issue a control command (manned, unmanned, arm, disarm, ask,
reset) towards one or more Modbus objects.
1. Select the WordTables tab
2. Click the object you want to command in the lists.
Keep the CTRL key pressed and click more objects to perform a multiple selection.
 The rows corresponding to the selected objects are highlighted.
3. Right click while keeping the mouse pointer into the selected area.
 The contextual menu appears, providing the list of available commands.
4. Click the command you wish to issue. The menu list includes:
- manned (attended, day mode)
- unmanned (unattended, night mode)
- arm (include, set)
- disarm (exclude, unset)
- ack (acknowledge, silence)
- reset (clear, rearm)
 The command execute on the selected object(s).
Note: The NK8237 accepts only the commands which have been enabled in the
selected Command Level (Modbus Master node, Host tab).
9.5 Correcting communication failures
9.5.1 Modbus communication problems

If a communication fault occurs on the Modbus, there may be one or more causes. The
problem may be in the NK8237 unit, or in the connections.
Check the NK8237

Check power, vital function, and diagnostic state on the respective LED, which is
located on the front panel.
90
Correcting communication failures
9
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.
Check the serial connections (Modbus serial)

Diagnostic information about the serial line state can be obtained from the LEDs
placed on the front panel of NK8237.
 General problems
– Check to make sure all connections are correct, tight and that the quality of the
cable is good.
– Disturbances, caused by ground loops, if more than one device connects the
shield to ground. Also, check that the shield is not grounded in the middle of
the cable, e.g. because it is accidentally connected to some grounded metal
object.
– Electric motors, high voltage power lines, radio transmitters, microwave ovens
or other sources of electrical noise near the line may cause communication
errors.
 RS232
Typical problems of RS232 communication:
– Make sure that line length does not exceed the maximum of 15m. Solve
problems of exceeding line length by using:
- RS232 line drivers
- Fibre optic converters
- RS422 converters
 RS485
Typical problems of RS485 communication:
– In a multi-drop RS485, a device with a bad serial port can cause problems on
the entire network. Try removing the devices one at the time.
– Termination and/or biasing problems may occur if the cable is very long or if
there are many RS485 devices on the same cable. Check to make sure that
the line is properly terminated.
Check the network connections (Modbus TCP/IP)

 LAN
Diagnostic information about the LAN state can be obtained from different layers:
Link state LED of Repeater or Ethernet adapters gives you information about the
physical connection and the speed of the Ethernet link.
1) Select Start > Programs > Accessories > Command Prompt.
2) Choose from the following commands:
Command Meaning
ipconfig /all Shows comprehensive information about the local PC’s IP configuration (for
example, the IP address)
ping n.n.n.n Lets you check the communication with an IP network participant (“n.n.n.n” is the
IP address to check)
91
9 Correcting communication failures
ping n.n.n.n –t Lets you continuously check the communication with an IP network participant
(“n.n.n.n” is the IP address to check)
Netstat Provides you the information about all established TCP/IP connections
arp -a Displays the physical address translation table
9.5.2 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. All control units as well as the
NK8237 have a unique Device Identifier. The BACnet Device Identifier is assigned
automatically to the NK8237 and control units and displayed in the BACnet tab of the
NK8237 node in Composer.
Check that the Device Identifier assigned by Composer for NK8237 networks are
compatible with your BACnet configuration.
BBMD and Foreign Device configuration

Make sure that the BBMD’s in all subnets are configured consistently.
9.5.3 Control unit generated a fault

If a control unit generated a fault, the problem may be in the connectivity between one
of the control units (or subsystems) and the NK8237 .
Check network connections

 RS232
Diagnostic information about the RS232 state can be obtained from the LEDs
placed on the front panel of NK82xx. Typical problems of RS232 communication
are:
– Mix of RXD / TXD lines.
– Line length exceeds the maximum of 15m.
– Disturbances, caused by ground loops.
– Solve problems of exceeding line length by using:
– RS232 line drivers
– Fibre optic converters
– RS422 converters
9.5.4 Control unit won't respond

When adding and configuring an NK8237 node, verify that you have the correct Local
address and Baud rate, and that the data link is up (blinking red and green). If you
92
Correcting communication failures
9
have an incorrect Local address or Baud rate, you will no communication in run-time,
though no error message will be generated.
Note: The Local address must correspond with the one assigned to the subsystem
during the configuration in the NK8000 Composer tool.
9.5.5 No fault generated by network failure - MP3.15 and higher

If you do not receive a fault from an NK8237 when a network failure has occurred, or if
there is a long delay before you receive the fault, decrease the Timer for Micro
Interruptions Threshold communication parameter.
Note: Default value is 0 sec.
93
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. On computer stations equipped with license-related devices (e.g. USB
keys), particular attention should be given to the protection of these devices. Power
supply should include UPS to guarantee stable power. Cabinets with sensitive
information (e.g. documents, passwords, backup tapes, and memory support)
should be properly protected and possibly locked. Security on the IP Network
communication should be evaluated and appropriate protections implemented with
the possible application of encrypted communication protocols, including the
NK8000 secure download option.
 System configuration
Depending on the IT security strategy, adequate firewall as well as virus, spyware,
and malware protection should be installed on the system computers. NK823x
systems offer a built-in firewall protection (see Network Connectivity Guide,
document no.A6V10359485). Critical Operating System updates should also be
installed whenever they are available and required for security and/or system
stability (refer to Microsoft Windows Updates web services). DMS8000 software
and tools have shown good compatibility with most popular antivirus and security
suite applications. In the installation and configuration, the specific security features
should be applied as required.
 Operational procedures
An appropriate security policy should be applied to the password management and
expiration using the related tools. Operators should be instructed to logout (or at
least lock their screen, if that is permitted) when they are away from their desk. No
written passwords or related hints should ever be left on the desks.
 Configuration backups
Configuration backups should be performed after every project modification, and
the related media stored in a safe place and possibly offsite. The backup list
includes:
Based on the above listed data and information, a data recovery scheme should be
put in place.
 Passwords
Keep a (security protected) copy of the master passwords for Windows and other
administration password(s).
 Data privacy and protection
Compliance with local regulations must be addressed. This can concern paper
listings as well as tapes and memory support.
For further information on general security issues regarding Siemens products, please
refer to the internal documentation and procedures on this subject.
94
Issued by © 2013 Copyright Siemens Switzerland Ltd
Siemens Switzerland Ltd Technical specifications and availability subject to change without notice.
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 DMS8000 Technical Material

Edition 30.06.2013 Section 2

A6V10316241 NK8237 Installation

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

A6V10316241 NK8237 Installation

Uploaded by

Copyright:

Available Formats

NK8237 MP4.

About this document.........................................................................................................7

About this document

Documentation resource information

- Document Type: All

Liability disclaimer for damage or injuries

Copyrights and registered trademarks

Version Date Notes

Danger potential to individuals

1.1 Country-specific standards

1.2 Assembly and installation

1.3 Commissioning and testing

1.4 Disposal and recycling

1.5 Modifications to the system design and the products

1.6 Data privacy and protection

2.1 Connectivity examples

Management 3rd party Modbus system

BACnet/Ethernet Modbus client Modbus TCP/IP Ethernet

Modbus TCP/IP connectivity

Modbus Serial RTU connectivity

2.2 What's new

Fire control units

Fire system topologies and max.connectivity

I/O modules locally connected via I2C

4 Structure and functions

4.1 NK8237 hardware

NK8237 gateway unit

4.1.1 Front panel

Left Side LED’s

Download (LED red)

Right Side LED’s

4.1.2 Internal DIP switches

Internal switch Functions

4.1.3 Internal jumpers

Internal DIP switch and jumpers (NKM8001-A1 mainboard)

Item Name Description

Internal DIP switch and jumpers (NKM8001-A2 mainboard)

Item Name Description

4.1.4 Serial interfaces

4.1.5 Onboard I/O

X101 onboard relay output.

X102 onboard inputs.

3 Input 3 (Power supply 4K7 4K7 1, 2, 3

4.1.6 I2C interface: DF8090 power supply supervision

DF8090 Power Supply Supervision

DF8090 front panel

4.1.7 Ethernet interfaces

4.1.8 USB interface

SD card slot location on the mainboard

The installation must be carried out by technically qualified personnel.

5.1 NK8237 hardware installation

Item Name Description

Serial RS232-interfaces (bottom view)

Item Name Description

X103 X104 X105

Vin 27Ah 12V

NK8237 power connections

X103: Power Supply

X2/X3: Ethernet Connector

X101: Onboard I/O (Output Relay)

X102: Onboard I/O (Inputs)

COM 1, COM 2: RS232 Connectors

DIN Rail Installation

Installation in Subsystem Housing Without DIN-Rail