DMS8000 MP4.50 SI410/420, SPC5000/6000, CS6, CS4, CS440, CZ12 Intrusion Connectivity Guide Building Technologies 29.06.
Table of Contents About this document.........................................................................................................4 1 Introduction ........................................................................................................7 1.1 What has been changed in MP4.50 .....................................................................7 1.1.1 Documentation changes and corrections in this edition .......................7 1.2 Additional documents ........................
About this document About this document Purpose of this document This manual is for use during the configuration of Danger Management Systems (DMS) and Building automation Systems (BMS) that include the following: MM8000 Management Station MT8001 Management Terminal MK8000 OPC Server for Subsystems NK8000 network devices DESIGO INSIGHT (for FS devices connectivity via MK8000) It is a guide to, and reference for the manual configuration of intrusion subsystems supported by these products
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.
About this document 007083_h 09.2005 MM8000 3.15; MT8001 3.15 ; NK8000 3.15 007083_g 06.2005 MM8000 3.12 007083_f 03.2005 MM8000 3.10-01; MK8000 3.10; NK8000 3.10 007083_e 12.2004 MM8000 3.10; MK8000 3.10; NK8000 3.10 007083_d 03.2004 MM8000 2.31; MK8000 1.31; MT8001 1.2; NK8000 2.11 007083_c 10.2003 MM8000 2.3; MK8000 1.3; MT8001 1.1; CDI-WAN 2.1 007083_b 07.2003 MM8000 2.2; MK8000 1.2; CDI-WAN 1.1 007083_a 03.2003 MM8000 2.1; MK8000 1.
Introduction What has been changed in MP4.50 1 1 Introduction Siemens fire safety and security products are designed to work together. While there are many occasions where only one product may be used in a facility, when combined our products create a robust and flexible set of architectural and connectivity solutions. The possible combinations of Danger Management Systems (DMS), network choices, and subsystems used in any given plant are extensive.
1 Introduction Additional documents 1.2 Additional documents Depending on your level of experience with Composer, and the architectural solutions available with our products, as well as where you are in the commissioning process, there are a number of additional documents that you may find useful. If you need a document that you do not have, you can download it on the Siemens Intranet.
Configuring intrusion control units Configuring an SI410 Intrunet 2 2 Configuring intrusion control units This guide describes how to configure the intrusion control units. The list includes: 2.1 SI410 Intrunet SPC5000/SPC6000 CS6 Guarto CS4 CS440 CZ12 Configuring an SI410 Intrunet The SI410 Intrunet is an intrusion detection unit with individual addressing and access control capability.
2 Configuring intrusion control units Configuring an SI410 Intrunet B - Network connection via NK8000 The NK8000 network allows for connecting a SI410 Intrunet unit using a serial line. The NK82xx Ethernet Port unit provides an optimised (and possibly encrypted) access to the LAN (Ethernet 10-Base-T) for DMS8000. NK82xx can also handle local interactions between the connected subsystems. The service PC running the SI410 SYLCOM tool can connect via another serial port or over a LAN link.
Configuring intrusion control units Configuring an SI410 Intrunet 2.1.2 2.1.2.1 2 SI410 connectivity: technical notes SI410 Intrunet: internal options and settings Serial ports The SI410 Intrunet can provide serial connectivity to host computers on the port J1, J7 and J10 (please refer to SI410 documentation). NOTE: Port J7 is used for connecting to the Sylcom PC, whereas J1 or J10 is used for DMS8000. In the connection solutions to DMS8000, the J10 port is used when the Sylcom tool is connected to J7.
2 Configuring intrusion control units Configuring an SI410 Intrunet IP gateway: if required, enter IP address for the router/gateway that links the SI410 subnet with the DMS8000 subnet. If not used, set 0.0.0.0 (the default 255.255.255.0 will not work). Mask IP: enter the required IP mask (typically 255.255.255.0). Sintony IP Port 2: IP Port number (contact network administration) used by the DMS8000 driver NS8014 to communicate over Ethernet.
Configuring intrusion control units Configuring an SI410 Intrunet 2 Plug-ins needed: – #352001 NOTE: Plug-ins are installed during the software setup procedure. You can check that the Plug-ins are actually available using the Composer Plug-in Installer in the DMS8000 start menu. Configuring an SI410 Intrunet 1. Generate the SI410 metafile. 2. Add the folder(s) required for identifying the location of the SI410 in the project structure tree. 3. Add SI410 system node to the new folder. 4.
2 Configuring intrusion control units Configuring an SI410 Intrunet should be reachable using the ping command. Note: Given that only one TCP port is available on SI410 for external hosts, the LAN connection of the Sintony Uploader makes use of the same port as the NS8014 DMS8000 driver. This implies that you need to stop the DMS8000 server software before connecting the Sintony Uploader.
Configuring intrusion control units Configuring an SI410 Intrunet 2 Sintony Uploader: auto-detecting the COM port 5. At this point, press Next and let the Read Data page show up. 6. Then press the Start button. The software starts communicating with the SI410 and acquiring the configuration data over the serial line. An item list and a progress bar show the activities and the uploading results.
2 Configuring intrusion control units Configuring an SI410 Intrunet Sintony Uploader: saving the configuration 3. Finally, press Next and then Finish to terminate the program. 2.1.5 Configuration procedures Adding the intrusion system folder 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. Adding the intrusion system node 1. Select the new folder. 2.
Configuring intrusion control units Configuring an SI410 Intrunet 2 Importing the SI410 metafile 1. Select the SI410 node. 2. Select Tools > Import in the Composer menu to start SI410 import. 3. The software presents a browsing window to search for the file to import (the INI file is expected, see Generating the SI410 metafile [➙ 13]). 4. Select the import file from the file selection window and click Open.
2 Configuring intrusion control units Configuring an SI410 Intrunet Linking the SI410 to the Communication network (MM8000/MK8000) To link the SI410 node to the MM8000/MK8000, do the following: 1. Expand the system station folders (Stand-alone or FEP) until you reach the node that represents the NS8014 driver. 2. Select the NS8014 SI410 Driver node. NOTE: If this driver is not present, you can add it to the Channels by clicking the corresponding icon on the left toolbar. 3.
Configuring intrusion control units Configuring an SPC5000/SPC6000 2.2 2 Configuring an SPC5000/SPC6000 The SPC5000 and SPC6000 are intrusion detection units belonging to the SPC series. They can support both wired and wireless intrusion devices (true hybrid controller) and a LAN interface possibly integrated by additional communications modules (PSTN/GSM/RF). Starting from SPC V3.1 all the SPC model types support Ethernet connection.
2 Configuring intrusion control units Configuring an SPC5000/SPC6000 Generating the SPC export file In File > Download Browse and download the file. WARNING When the web tool is connected to the SPC unit in Full Engineer mode, no alarm messages are transmitted to MM8000. 2.2.2 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows.
Configuring intrusion control units Configuring an SPC5000/SPC6000 2 4. Configure the network parameters for NS8013 Driver; namely: UDP port and Receiver ID, which should match the corresponding values in the EDP client list of SPC. Note that the valid values will be visible on the Node tab of the SPC units after importing the metafile. Adding the intrusion system folder 1. In the left-hand bar, click the Generic Template icon A new node is added to the project structure. . 2.
2 Configuring intrusion control units Configuring an SPC5000/SPC6000 NOTE: The node is renamed to match the metafile name. To customise the name, click the node text, type in a new name, and press ENTER. 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.
Configuring intrusion control units Configuring a CS6 Guarto 2.3 2 Configuring a CS6 Guarto CS6 Guarto Intrusion Control Unit The CS6 Guarto is an intrusion detection and access control system with individual addressing. It consists of the CC6 control unit and CT6 operating units. The ADI addressing elements transmit the detector signals to the control unit. The data structure of the CS6 includes multiple logical levels; namely: Area (max.
2 Configuring intrusion control units Configuring a CS6 Guarto Plug-ins needed: – #300101 NOTE: Plug-ins are installed during the software setup procedure. You can check that the Plug-ins are actually available using the Composer Plug-in Installer in the DMS8000 start menu. Configuring a CS6 Guarto 1. Add the folder(s) required for identifying the location of the CS6 in the project structure tree. 2. Add the CS6 system node to the new folder. 3. Import the metafile. 4.
Configuring intrusion control units Configuring a CS6 Guarto 2 Adding a new CS6 node Importing the CS6 metafile 1. Select the CS6 node. 2. Select Tools > Import in the Composer menu to start CS6 import. The software presents a browsing window to search for the file to import; the following CNAP profile files are expected: - DCD001_CLASS.TXT - DCD001_DATA.TXT - DCD001_INST.TXT - DCD001_LINK.TXT - DCD001_TEXT.TXT. 3. Select one of the import files from the file selection window.
2 Configuring intrusion control units Configuring a CS6 Guarto NOTE: The valid link position for Cerloop is always the same main node, representing the entire loop. The valid link positions on NK8000 units are distributed along the subsystem lines. NOTE: Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . Linking CS6 to NK822x Set CerCom/LON bus addresses 1. Select the CS6 link in the LON bus. 2.
Configuring intrusion control units Configuring a CS6 Guarto 2 Setting CS6 addresses on CerComLON bus 2.3.3 Commissioning tips Commissioning procedure To set the BACnet logical address on the LON network, we recommend the following procedure: 1. Switch off power of CS6 control unit(s). 2. Connect CS6 unit(s) to NK822x over the LON network. 3. Switch on power of CS6 control unit(s). After power-up, CS6 has no BACnet logical address. 4. Reset NK822x.
2 Configuring intrusion control units Configuring a CS6 Guarto Hardware and software prerequisites 1. Install SWE6 and RCCS6 software on a central PC connected to the LAN/WAN. The PC must be equipped with two serial ports. Note that RCCS6 is provided on the DMS8000 CD as one of the NK8000 support tools. 2. Connect the COM1 port used by SWE6 to another serial port used by RCCS6. A crossed serial cable shoud be used to enable the serial communication between SWE6 and RCCS6.
Configuring intrusion control units Configuring a CS4 2.4 2 Configuring a CS4 The CS4 is an intrusion detection system with individual addressing. It consists of the CC4 control unit, and the CT4 operating units. The ADI addressing elements transmit the detector signals to the control unit. The structure of the CS4 is divided into logical system levels, and planning and parameterisation determines its allocation to software and hardware. The logical system levels include: Area (max.
2 Configuring intrusion control units Configuring a CS4 Configuring a CS4 1. Add the folder(s) required for identifying the location of the CS4 in the project structure tree. 2. Add the CS4 system node to the new folder. 3. Set the CS4 Local Address, Vitality Timer, and Sub type. 4. Import the CS4 List file. 5. Link the CS4 to the Co0mmunication device line, according to communication links. 6. Repeat steps above for all the CS4s in the project. 2.4.
Configuring intrusion control units Configuring a CS4 2 Setting the CS4 Local Address, Vitality Timer and Sub type 1. Select the CS4 node. 2. In the Node tab, set the Local Address, Vitality Timer and Sub type. Please note that: The address value should range from 111 to 248 according to the DMS7000 addressing scheme (last digit cannot be 0 or 9), and it should match what is set in the configuration of the CS4 unit.
2 Configuring intrusion control units Configuring a CS4 Linking the CS4 to the Communication network Link the CS4 node to the Cerloop, CDI-Net, or NK8000 network. 1. Expand the network folders until you reach the node that represents the network that is physically connected to the CS4. 2. Select the CS4 node. 3. Drag and drop the CS4 node to the network node. When the link is established, a new node appears on the structure tree, and its properties can be seen on the Node tab.
Configuring intrusion control units Configuring a CS440 2.5 2 Configuring a CS440 The CS440 is a large intrusion detection system with individual addressing. It consists of the CS440 control unit and the CT411 operating units. The ADI addressing elements transmit the detector signals to the control unit. The structure of the CS440 is divided into logical system levels, and planning and parameterisation determines its allocation to software and hardware. The logical system levels include: Area (max.
2 Configuring intrusion control units Configuring a CS440 5. Link the CS440 to the network (Cerloop, CDI-Net, or NK8000). 6. Repeat steps above for all the CS440s in the project. 2.5.2 Configuration procedures Adding the intrusion system folder 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. Adding the intrusion system node 1. Select the new folder. 2.
Configuring intrusion control units Configuring a CS440 2 NOTE: The value to set in the Vitality Timer depends on the type of network. The following rule applies: - In Cerloop network, the MK7022 already handles the vitality check, and the DMS host does not receive the heartbeat messages. In this case, set the timer value = 0. - In NK8000 and CDI-Net networks, if the connection also includes the MK7022 Cerloop interface, leave the value = 0.
2 Configuring intrusion control units Configuring a CS440 NOTE: Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . Linking CS440 to NK82xx (NK8223, COM3) 36 Building Technologies Fire Safety & Security Products A6V10359489_a_en 29.06.
Configuring intrusion control units Configuring a CZ12 2.6 2 Configuring a CZ12 The CZ12, the predecessor of the CS4, is a control unit for intrusion detection. It was developed as part of the DMS7000 system. The CZ12 is physically composed of a central module, which is housed inside a cabinet, and connected to detection lines and alarming devices. The system can be operated locally on a CT12 terminal by a restricted number of authorised users.
2 Configuring intrusion control units Configuring a CZ12 Plug-ins needed: – #350201 NOTE: Plug-ins are installed during the software setup procedure. You can check that the Plug-ins are actually available using the Composer Plug-in Installer in the DMS8000 start menu. Configuring a CZ12 1. Add the folder(s) required for identifying the location of the CZ12 in the project structure tree. 2. Add the CZ12 system node to the new folder. 3. Set the CZ12 Local Address and Vitality Timer. 4.
Configuring intrusion control units Configuring a CZ12 2 Adding a new CZ12 node Setting the CZ12 Local Address and the Vitality Timer 1. Select the CZ12 node. 2. In the Node tab, set the Local Address and the Vitality Timer. Please note that: The address value should range from 111 to 248 according to the DMS7000 addressing scheme (last digit cannot be 0 or 9), and it should match what is set in the configuration of the CZ12 unit.
2 Configuring intrusion control units Configuring a CZ12 In a few moments, the CZ12 structure is imported, and the node is represented in the Composer tree. Importing the LMSmodular configuration 1. Select the CZ12 node. 2. Select Tools > Import in the Composer menu to start CZ12 import. The software presents a browsing window to search for the files to import. 3. Using standard Windows controls, do the following: - Look for LMS files, selecting the extension DBF in the browsing window.
Configuring intrusion control units Configuring a CZ12 2 NOTE: Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . Linking CZ12 to a Cerloop network 41 Building Technologies Fire Safety & Security Products A6V10359489_a_en 29.06.
Issued by Siemens Switzerland Ltd Infrastructure & Cities Sector Building Technologies Division International Headquarters Gubelstrasse 22 CH-6301 Zug Tel. +41 41-724 24 24 www.siemens.com/buildingtechnologies Document ID A6V10359489_a_en Edition 29.06.2012 © 2012 Copyright Siemens Switzerland Ltd Technical specifications and availability subject to change without notice.
