User Manual

Installation

Building Technologies 008751_b_en MaxSys - MM8000 3.20 add-on.doc

Fire Safety & Security Products 09.2006

2.3 Communication network

The MAXSYS is connected to the MM8000 system by means of the NK8000 net-

work and namely via the NK8222, NK8223, or NK8225 units.

In order to communicate with the MAXSYS, the NK822x units should however be

equipped with a new firmware that is included in the installation package as an ad-

ditional component (DLL) to be added to the standard firmware file set.

The software installation procedure provides to copy the firmware files (a com-

pressed ZIP archive) in the ‘NK822x – Firmware’ folder of the MM8000. From

there, the files can be downloaded to the NK822x units using standard Composer

commands. The required procedure is described here below.

2.3.1 NK822x firmware download

The following are the download procedures for the NK822x firmware supporting the

MAXSYS communication protocol.

Note: It is assumed that the NK822x are physically installed, powered on, and

communicating over the network. For more information about the NK8000 installa-

tion, please see the document no. 007083, DMS8000 Network, Fire and Intrusion

Connectivity Configuration Guide, section 4.3. More advanced technical issues are

also discussed in the document no. 007798, NK8000 Installation, Configuration

and Commissioning.

Also, you should have available the Composer project that includes the NK8000

network and all the NK822x units.

1. Verifying the connection with NK822x

The NK822x download requires that the TCP/IP connection between the host

PC and the NK822x is working properly. In the Windows Command Prompt

window, you can check easily this connection using the “Ping” command:

ping n.n.n.n

where ‘n.n.n.n’ is the IP address of the NK822x unit, e.g. 168.123.8.76.

If the IP connection is good, the message text looks like the ones in Fig. 5, i.e.:

Reply from n.

n.n.n: bytes=… time … TTL=…

If the IP connection is not working for any reason, different messages may ap-

pear (Request timed out, Destination net unreachable, etc.) In these cases, ver-

ify the network settings and cabling and try again.

Fig. 5 Checking IP connection