A6V10316241 NK8237 Installation
A6V10316241 NK8237 Installation
A6V10316241 NK8237 Installation
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
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
About this document
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.
7
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
About this document
Note: Before beginning work on the system you must have read and understood the
Safety Regulations section in this manual.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
9
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
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.
10
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Safety regulations
Commissioning and testing
1
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.
Please request written approval from Siemens Building Technologies and from any
relevant authorities concerning intended system modifications and system extensions.
11
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
Automation
GAP ETH1 ETH2
level
BACnet client Modbus server
BACnet server
NK8237
FC2020
Field level
12
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
System limits
3
3 System limits
The following describes the system limits for the NK8237 units.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
8 FS20/FS720 units
- OR -
6 FS20/FS720 units and 5 STT20 units in FCnet/SAFEDLINK topology.
3 Modbus hosts Max. 3,500 detectors.
6 FS20/FS720 units
- OR -
5 FS20/FS720 units and 3 STT20 units in FCnet/SAFEDLINK topology.
4 Modbus hosts Max. 2,500 detectors.
4 FS20/FS720 units
- 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.
15
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
4 NK8237 hardware
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.
16
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
NK8237 hardware
4
Name Function
Com1 Status Com1
Com2 Status Com2 Red: RX
Green: TX
Com3 (not used) Status Com3
Com4 (not used) Status Com4
17
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
4 NK8237 hardware
18
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
NK8237 hardware
4
19
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
4 NK8237 hardware
3 NC
The input signals can be used for acquiring external power supply supervision lines,
e.g. for the supervision of the fire system power supply. Note that this is alternative to
the DF8090 power supply supervision (see I2C interface: DF8090 power supply
supervision [➙ 20]).
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
NK8237 hardware
4
PW
MAINS
1 AC/DC
LOW BATT
BATT FUSE
2
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
4 NK8237 hardware
Ethernet connectors
Item Description
1 Ethernet 1
2 Ethernet 2
22
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Structure and functions
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).
Item Description
1 SD card slot
23
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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
WARNING
Do not connect or disconnect any device when the device is powered on!
24
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
NK8237 hardware installation
5
Top view
Back
1 2 3 4 5 6 7 8
NK8237 electrical interfaces (top view)
25
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
5 NK8237 hardware installation
Bottom view
1 2
26
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
NK8237 hardware installation
5
Power connections
Note the dual power supply input for redundant solutions.
POWER
SUPPLY
DF8090
BATTERY
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.
27
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
5 NK8237 hardware installation
Secondary 6 +
(optional)
7 Earth
8 –
Ethernet connections.
Pin Assignment
1 TX+
2 TX–
3 RX+
4 n.c.
5 n.c.
6 RX–
7 n.c.
8 n.c.
28
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
NK8237 hardware installation
5
RS232 connections.
Pin Assignment
1 CD
2 RXD
3 TXD
4 DTR
5 GND
6 DSR
7 RTS
8 CTS
9 RI
Note: Before removing the box, carefully disconnect the flat cable (bus) of the I2C
module, as well as the power supply cables.
29
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
5 NE8000 cabinets
WARNING
30
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
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
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
5 NE8000 cabinets
20 mm hole cut-outs
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).
32
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Hardware installation
NE8000 cabinets
5
33
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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).
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].
34
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Software installation
Launching Composer
6
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.
35
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Software installation
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:
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 .
36
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Software installation
NW8204 maintenance and diagnostic tool
6
37
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Software installation
6 NW8204 maintenance and diagnostic tool
38
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Configuration checklist
7
7 Configuration
The following picture gives an overview about the configuration workflow.
BACnet/IP Ethernet
Automation
level GAP ETH1
39
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Configuring IP settings via NW8202
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.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Configuring IP settings via NW8202
7
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Creating a new NK8237 Composer project
Depending on the DMS8000 installation option you chose, you can also create an
empty project, which have to be manually configured.
42
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Creating a new NK8237 Composer project
7
43
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Creating the Modbus system(s)
7
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).
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.
2. In the toolbar on the left, select Network and then the Modbus Master icon .
45
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Creating the NK8237 Gateway
46
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Creating the NK8237 Gateway
7
47
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Configuring the Fire network
7
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.
49
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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.
Configuration Procedure
1. In the left-hand bar, click the Generic Template icon .
A new node is added to the project structure.
2. Select the new folder and name it in the Description field of the Node tab.
50
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Configuring the Fire network
7
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.
51
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Configuring the Fire network
Note: The parameter settings about the Single Event Acknowledgement and Single
Event Reset are not supported by the NK8237 and should not be used
52
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Configuring the Fire network
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.
53
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Configuring the Fire network
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Configuring the Fire network
7
Routing Tables:
NK823x can handle a static routing table to address multiple subnets via IP routers
(e.g. SAFEDLINK GAP stations). Accesses to subnets that are not handled by the
NK323x Default gateway must be defined as routing table.
Note that, if a SAFEDLINK network includes both FS20 and STT20 units, two
separate GAPs must be addressed and specific routing tables for two separate
subnets must be defined accordingly.
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:
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).
55
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Configuring the Fire network
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.
A link node is created under the Ethernet node.
5. Select the BACnet Client Protocol link under the Ethernet node.
6. Select the Node tab.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Configuring the Fire network
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).
57
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Configuring the Fire network
58
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Customising the Modbus Interface
7
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).
59
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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
60
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Customising the Modbus Interface
7
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.
61
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Customising the Modbus Interface
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.
62
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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).
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]).
63
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Downloading the NK8237
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.
64
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Downloading the NK8237
7
Note: You can check the current fimware version on the Tools tab of the NK8237
node by pressing the Read All button.
12. In the toolbar on the left, select the NS8011 BACnet Driver .
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
7 Downloading the NK8237
66
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Configuration
Downloading the NK8237
7
67
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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].
WARNING
68
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
Kernel update
9
69
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 SNMP monitoring
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.
70
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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.
If you receive this message, select OK and re-type the IP Address. If you want to
71
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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.
1 2 3 4 5
6 7 8
72
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The NW8204 maintenance and diagnostic tool
9
Note: If you do not close the connection, you will automatically be timed out in five
minutes.
73
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 The NW8204 maintenance and diagnostic tool
NK Vitality
Opens a window, which shows the current status of the NK8237 point image.
74
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The NW8204 maintenance and diagnostic tool
9
Read HW version
Reads the NK8237 hardware version (NKM8001-A1, NKM8001-A2, …).
75
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 The NW8204 maintenance and diagnostic tool
76
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The NW8204 maintenance and diagnostic tool
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.
77
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 The NW8204 maintenance and diagnostic tool
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.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The NW8204 maintenance and diagnostic tool
9
79
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 The NW8204 maintenance and diagnostic tool
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).
80
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The NW8204 maintenance and diagnostic tool
9
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.
81
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 The NW8204 maintenance and diagnostic tool
Note: Resetting the unit restores the original logging configuration saved in
Composer.
82
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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).
83
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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.
84
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The Modbus Client simulator
9
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 The Modbus Client simulator
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The Modbus Client simulator
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.
87
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
9 The Modbus Client simulator
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.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
The Modbus Client simulator
9
89
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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).
Note: The NK8237 accepts only the commands which have been enabled in the
selected Command Level (Modbus Master node, Host tab).
90
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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.
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
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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
92
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Maintenance and diagnostics
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.
93
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
Secure operation requirements
10
94
Building Technologies A6V10316241_a_en
Fire Safety & Security Products 30.06.2013
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