EasyManua.ls Logo

Siemens NK8237 MP4.40 - Fire System Communication Problems

Siemens NK8237 MP4.40
68 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Maintenance and diagnostics
66
Building Technologies
048_DMS_NK8237_ICC_MP4.40_A6V10316241_a_en.doc
Fire Safety & Security Products 06.2011
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)
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.4.2 Fire system communication problems
TCP/IP network
Troubleshoot the basic TCP/IP problems as described here above for the Modbus
TCP/IP and using the Ping button in the Tools tab of the NK8237 node in Com-
poser. 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 as-
signed 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.

Table of Contents

Related product manuals