DMS8000 MP4.
Data and design subject to change without notice. / Supply subject to availability. © 2008 Copyright by Siemens Switzerland Ltd We reserve all rights in this document and in the subject thereof.
Table of contents About this document ............................................................................................... 4 1 Introduction ............................................................................................. 7 1.1 1.2 What has been changed in MP4.15 configuration tools ........................... 8 1.1.1 Documentation changes and corrections in this edition ............. 8 Overview of networks and subsystems..................................................... 9 1.
.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 Configuring a CS1115 ........................................................................... 101 4.3.1 Configuration checklist ............................................................ 101 4.3.2 Configuration procedures – CS1115 systems ........................ 103 4.3.3 Configuration procedures – CS1115-x ................................... 104 4.3.4 Configuration procedures – CS1115-ECO ............................. 107 4.3.
.5 Configuring a CZ12 ............................................................................... 183 5.5.1 Configuration checklist............................................................ 184 5.5.2 Configuration procedures ....................................................... 185 6 Configuring other control units ......................................................... 188 6.1 Configuring a CC60............................................................................... 188 6.1.
Introduction 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 NK8000) It is a guide to, and reference for the manual configuration of networks and subsystems supported by these products.
Introduction 3. Select “All” in the Documents section of the Quick Search page and select “Advanced Search”. 4. Enter the document number in the “Brochure No.” field (A6V10089056) and press “Enter”. Operational and safety regulations i Before groups of persons begin work on any DMS system, they must have read and understood the related documents. In particular the Safety Regulations included in the Installation, Configuration, and Commissioning manual (ICC) for each specific product.
Introduction Acknowledgments We wish to thank all the Siemens colleagues and the customers who have given us feedback and comments about this documentation. 6 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Introduction 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. However, the time involved with commissioning tasks can be substantial.
Introduction 1.1 What has been changed in MP4.15 configuration tools Here is the list of modifications included in MP4.15 for new functions and software improvements. 1.1.1 Section, Page Modifications 2.3.3. p. 14 Projects and licenses are identified based on sales-channels: Solutions and Products. P. 17 New license/PAK summary table 3.4, p. 74 New BACnet section 3.5, p. 76 New section about “Serial to network adapters” that used to be integrated in the SI410 chapter. 4.1, p.
Introduction 1.2 Overview of networks and subsystems Siemens Building Technologies products are organised into three levels: Management level: It presents the events, and allows for control of the site via the management station(s). The majority of the human interface takes place at this level. Automation level: The majority of the real-time control functions are carried out at this level. It provides data communication links between the other two levels and defines the network topology and structure.
Introduction 1.3 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.
Configuration process overview 2 Configuration process overview DMS8000 Configuration Process Overview The following overview is a general guide to the phases or steps that occur in the configuration process. Documentation that supports a given step is shown at right. The order in which these tasks are performed may vary depending on personal preference or specifications in the product configuration manual. This is not an absolute guide, but rather lends context to the tasks discussed in this manual. 1.
Configuration process overview 2.1 Porting existing configuration databases The DMS8000 configuration tools allows for restoring the configuration of existing installations. The following formats are supported: Configuration database backup of previous versions of the same DMS8000 product (MM8000, MK8000, or MT8001). Refer to the specific Release Notes of the latest software for detailed information.
Configuration process overview Use the “right-click” menu for common tasks The right-click menu contains the most common tasks you will need to perform in Composer, such as deleting a folder or icon. Refer to the Composer Technical Manual for general functions and shortcuts While basic tasks for setting up a project in Composer are covered here briefly, Composer contains a number of functions and shortcuts that may prove to be valuable timesavers as you become more familiar with using it.
Configuration process overview 2. Select the entire list of subsystem tools in the right column 3. Click the Install button The list of Plug-ins appears in the Plg-ins Installed pane (see Fig. 1 at p.14). Note that this may take a couple of minutes. Watch the Installer messages at the bottom of the window to monitor the status. 4. Click Exit Fig.
Configuration process overview fore the actual expiration, a specific message warns Composer users about the need of renewing the service key license. The PAK is printed on the License of Use that came with the hardware key. You can enter this number using the License Manager software that was installed with the Composer software. Note: If you received the code in a file (.REG), you can quickly import the PAK as described at p.17.
Configuration process overview Warning: Before entering the PAK, press the backspace key to ensure that there are no spaces in the PAK field. Also, when you enter the PAK, do not type any dashes or spaces. For example, if the License of Use PAK is: TJNW-NHVX-UKS3-LIAY, the PAK should be entered as: TJNWNHVXUKS3LIAY. Please note that the number 0 (zero) is not used. 7. Click Save. The license appears in the Available licenses list. 8.
Configuration process overview Import PAK from the .REG file If you received the PAK in a file with the extension .REG, do the following: 1. Copy the file on your local computer disk. 2. Select the menu command File Import PAK. A file browsing window displays. 3. Locate and select the .REG file, click OPEN 4. Confirm you want to merge the new codes in the system registry. The file is read and the PAK code imported.
Configuration process overview 2.3.4 Checking the license requirements Composer can provide the detailed license requirements for the current configuration. Select the main node of the DMS8000 system, e.g. Project MK8000 System MK8000 and then the Node tab (Fig. 6). In the page that appears, click View License Data. The resulting list shows the required license parameters for the current configuration. Note the Available License column that shows Unknown.
Configuration process overview Note: Older version of Composer (e.g. MP3.15 and earlier) will show a different welcome window. Please refer to the previous editions of this guide. Projects can take quite a bit of space on the hard disk. Therefore, it is not recommended that you create multiple copies of the same project. If you wish to save a particular project configuration for later use, you can do this using the backup function (see section 7 at p.216). Fig.
Configuration process overview 2.4.2 Setting up the structure Now that you have created the project, you need to set up the node structure to reflect the structure of the site. Please refer to the specific DMS Installation Configuration & Commissioning manual (ICC) (reference documents are listed in the Resource Information document described at p.4).
Configuration process overview Fig. 10 Selecting project version Here you can select how you want Composer to handle the project, whether you want to update it to a newer version or keep it as it is. Obviously, the decision depends on which DMS8000 product version will be running this project on site. 21 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring networks and network components 3 Configuring networks and network components This section describes how to configure networks. Possible networks are: Cerloop CDI-Net NK8000 BACnet The networks consist of the following components: MK7022 GW21 GW20 NK8222 NK8223 NK8225 Note: A direct connectivity to the DMS8000 management system is possible for several types of units, either over a serial line or via a local area network. Serial to LAN adapters may also be used as illustrated in section 3.
Configuring networks and network components 3.1 Configuring Cerloop The Cerloop network provides a redundant connectivity solution for Siemens fire, rd safety, security, and 3 party control units. The network has a ring topology, and each unit can communicate via two different wiring paths, thus assuring a redundant link in case of failure in any point in the loop.
Configuring networks and network components 3.1.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number of Cerloop networks. For each Cerloop: – The type of each control unit connected to it (CZ10, CS11, etc.), and its local address (111, 112, etc.) – The number of MK7022 interface(s) to be used for accessing the loop.
Configuring networks and network components 3.1.2 Configuration procedures Adding the Cerloop network node to the network folder 1. Select the destination folder. 2. In the left-hand bar, select the Network folder icon 3. In the menu that appears, select the Cerloop Network icon to add the Cerloop network node (see Fig. 12-A). A new node is added to the project structure. Fig. 12 Selecting the icon to add a new Cerloop node Adding the MK7022 node to the Cerloop network 1.
Configuring networks and network components Fig. 14 Setting the MK7022 local address Linking the MK7022 node to the Cerloop driver Note: These connections can be made once the DMS and the subsystems of the Composer project have been inserted. The order in which you perform these connections may vary from the following steps. Also, note that the MK7022 may also be connected to a CDI-Net or NK8000 port. 1. Select the MK7022 node.
Configuring networks and network components The communication baud rate (either 1200 or 2400 baud). This value must match the actual MK7022 hardware setting. 3. The flow control parameters - specifically Message rate, Sample time, and Status request timeout – do not usually require any modification. They may be required, however, for tuning the status requests in case of large systems. See p.80. Fig.
Configuring networks and network components 3.2 Configuring CDI-Net The CDI-Net network provides point-to-point connectivity solutions for Siemens rd fire, safety, security, and 3 party control units. CDI-Net is a family of products including: GW20 gateway, that supports up to 20 RS232 lines to subsystems (downstream), and up to 4 RS232 lines to the DMS (upstream). GW21 gateway, that supports up to 4 RS232 lines to subsystems (downstream), and up to 2 RS232 lines to the DMS (upstream).
Configuring networks and network components 3.2.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number and the type of gateways, as well as the global connectivity architecture. The hardware configuration in relation to the RS232 lines that should be used for each gateway. The connectivity to the DMS (lines, protocol setting).
Configuring networks and network components 3.2.2 Configuration procedures Adding the CDI-Net network node to the network folder 1. Select the destination folder. 2. In the left-hand bar, select the Network folder icon 3. In the menu that appears, select the CDI-Net icon to add the CDI-Net network node (Fig. 19-A). A new node is added to the project structure. Fig.
Configuring networks and network components Fig. 21 Selecting the icons to add the GW20 pads A Click this icon to add a Subsystem Pad, for connecting a subsystem. B Click this icon to add a NetM Pad, for connecting a GW21 in a 2-level network. C Click this icon to add a FHI Pad, for connecting a Foreign Host. D Click this icon to add a Nise Pad, for connecting NCRS (BAU). Note: Each pad is equipped with 4 serial lines.
Configuring networks and network components See “Expansion option” at p.32. 4. Double-click the Lines folder to open it. 5. Select a line (1-4). 6. Set the Line Type in the Node tab. See Fig. 23, the following table, and the Line type descriptions. 7. Repeat steps 5 and 6 for all four (or six) lines. Fig. 23 Setting the type of GW21 line GW21 line types CMS Line 1 X Line 2 X Subsyst.
Configuring networks and network components Fig. 24 Adding the GW21 expansion board Connecting CDI-Net to the DMS This connection can be made once the DMS components of the Composer project have been inserted. The order in which you perform this connection may vary from the following steps. 1. Select the line. Expand the folders in the Communication network until you reach the DMS line. 2. Locate the CDI-Net driver.
Configuring networks and network components Fig. 26 Connecting GW21 line to DMS Setting the communication parameters for the CDI-Net driver (NS8012) 1. Select the Node tab of the COM port link node under CDI-Net driver. 2. Adjust the CDI-Net communication parameters (see Fig. 27): The number of the hardware port to be used by the DMS The communication baud rate (ranging from 2400 to 9600 baud) This value must match the actual GW2x hardware setting. 3.
Configuring networks and network components 3. Select the subsystem node. Note: depending on the subsystem type, you may have to select the control unit node (such as CZ10, CS4, CZ12, CF9000 etc.) or its gateway (such as CK11 for CS11, SK11 for STT11 etc.). See specific instructions in the section dedicated to each subsystem. 4. Drag and drop the subsystem to the associated CDI-Net line. See Fig. 28 below. The subsystem node appears in the hierarchical tree under the associated line. Fig.
Configuring networks and network components Fig. 29 Linking GW21 to GW20 in a 2-level CDI-Net 36 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring networks and network components 3.3 Configuring NK8000 The NK8000 network, formerly CDI-WAN, provides IP and Dial-up connectivity sord lutions for Siemens and 3 party control units. NK8000 is a family of network products including: NK8222 Ethernet port: LAN/WAN (CMSDL/IP, CEI-79) and Dial-up (CEI-79) communication unit supporting one subsystem connection over RS232 line or CerCom/LON bus, and local I/O units. It can provide local interactions between the connected subsystem and local I/O.
Configuring networks and network components LAN/WAN connectivity NK822x can also be set-up for handling upstream connectivity over IP LAN/WAN. NK8222 and NK8223 connect to DMS8000 hosts equipped with the NS8210 driver (CMSDL/IP and CEI 79-5 driver). NK8225 has the same characteristics of NK8223 and can, for a limited number of subsystems, also supports BACnet/IP connectivity for DESIGO INSIGHT stations (availability to be announced) and for DMS8000 as well.
Configuring networks and network components 3.3.1 NK822x for upstream serial connectivity Fig. 30 Example of NK8000 serial connectivity 3.3.1.1 Configuration checklist NK822x units can communicate with DMS8000 host via serial line in the so-called “CDI-Net emulation” mode. If you are familiar with CDI-Net family of products, this solution results in the NK822x being used as a GW21.
Configuring networks and network components ITEMS NEEDED FOR CONFIGURATION The number and the type of gateways, and the global connectivity architecture. The NK822x IP address, as initially loaded with NW8202 or NW8204. – Refer to NK8000 ICC guide (doc. no A6V10062437). The hardware configuration in relation to the RS232 lines used for subsystem connectivity on each gateway. The connectivity to the DMS (lines, protocol setting).
Configuring networks and network components 3.3.1.2 Configuration procedures Adding and configuring an NK822x node 1. Select the destination folder. 2. In the left-hand bar, select the Network folder icon 3. In the menu that appears, select the NK822x icon to add the NK822x node (see Fig. 31-A). A new node is added to the project structure. Note: An old NK8223 type is also present under the CDI-Net icon list. This refers to CDI-WAN 1x modelling for serial connectivity and should not be used any longer.
Configuring networks and network components Fig. 32 Connecting NK822x directly to DMS Setting the communication parameters for the CDI-Net driver (NS8012) 1. Select the Node tab of the COM port link node under CDI-Net driver. 2. Adjust the CDI-Net communication parameters (see Fig. 27 at p.
Configuring networks and network components 3.3.2 NK822x for dial-up connectivity Fig. 33 Example of NK8000 dial-up connectivity 3.3.2.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. The NW8202 tool should be used prior to configuring NK8000 in Composer. That is required for setting a valid IP address for downloading.
Configuring networks and network components ITEMS NEEDED FOR CONFIGURATION The number and the type of gateways, as well as the global connectivity architecture. The NK822x IP address, as initially loaded with NW8202 or NW8204. – Refer to NK8000 ICC guide (doc. no A6V10062437). The hardware configuration in relation to the RS232 lines used for subsystem connectivity on each gateway.
Configuring networks and network components Configuring the NS8210 driver 1. Open the Channel collection in: MM8000 (or MK8000) System Physical configuration Station (or FEP) Channel collection 2. Select the NS8210 driver for CEI-79 link to DMS8000. 3. Configure the network options: select the driver node (See Fig. 34). A form appears on the right side of the screen. Fig.
Configuring networks and network components 4. Select the Node tab of the new modem node and configure the following: Phone number of the DMS8000 location AT initialization string AT end-of-command string AT reset string Modem signals check interval (in sec.) If required, set the “Pulse” mode (default is “Tone”).
Configuring networks and network components Adding and configuring the NK822x modem 1. Select the parent node for the communication network. 2. In the left-hand bar, select the Network folder icon 3. In the menu that appears, select the Modem icon . to add the modem node. A new node is added to the project structure. 4. Select the Node tab of the modem and configure: Phone number of the NK822x location AT initialization string AT end-of-command string AT reset string Periodic modem checks delay (in sec.
Configuring networks and network components 3.3.3 NK822x for upstream IP connectivity to DMS8000 Fig. 35 Example of NK8223 IP connectivity to DMS8000 Fig. 36 Example of NK8225 IP connectivity to DMS8000 Note that NK8222 and NK8223 do not support BACnet and cannot connect to NS8011 BACnet Driver. Instead, NK8225 can work on both CMSDL/CEI and BACnet network and can simultaneously connect to both NS8210 and NS8011 drivers on multiple hosts.
Configuring networks and network components 3.3.3.1 Configuration checklist The NK822x units can communicate with DMS host over TCP/IP networks. You can define and download the NK8000 technical configuration with Composer tools. The NW8202 or NW8204 tool is necessary to initialise the IP address of NK822x units prior to downloading configurations from Composer. Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows.
Configuring networks and network components CONFIGURING NK8000 1. Configure the NS8210 or NS8011 driver in the DMS channel 2. Add folders as required for representing your geographical structure. 3. Add and configure the NK822x unit p. 52 4. Configure the Ethernet link p. 53 5. Connect NK822x to the main DMS host on NS8xxx driver p. 55 6. Connect NK822x to additional DMS host(s) p. 56 7. Connect subsystems to NK822x p. 59 8. Configure the local I/O modules, if used p.
Configuring networks and network components 3.3.3.2 Configuration procedures The following are the configuration procedures required for the NK8000 IP network based on NK822x units. Configuring the NS8210 driver (or NS8011) 1. Open the Channel collection in: MM8000 (or MK8000) System Physical configuration Station (or FEP) Channel collection 2. Select the NS8210 driver for CMSDL/IP or CEI-79 link to DMS8000 -- or -the NS8011 driver for BACnet/IP connectivity to DESIGO or DMS8000.
Configuring networks and network components Other fields are particular to NS8011 (BACnet parameters); namely: Parameter Meaning Notes IP address IP address of the local BACnet router in DMS8000 This is typically the same IP address as the DMS8000 PC. In case of multiple LAN adapters, you can select here the one working on BACnet.
Configuring networks and network components Note: Unlike CDI-Net and Cerloop (that are based on a start topology), the NK8000 units do not need to be allocated into a dedicated folder. This solution is designed to support the representation of dispersed units, and to allow for distributing the unit nodes in multiple folders. 2. In the left-hand bar, select the Network folder icon 3. In the menu that appears, select the NK822x icon (see Fig. 39).
Configuring networks and network components For NK8222/NK823, the CEI protocol must be necessarily selected when the dial-up connectivity is required. An additional connection over serial line (CMSDL) can also be supported. This option, however, will limit the CMSDL/IP or BACnet/IP links to three instead of four. Fig. 40 Configuring IP parameters for a network with NAT gateway 4.
Configuring networks and network components Fig. 41 Configuring NK822x Ethernet and CEI-79 parameters Connecting NK822x to the DMS 1. Open the Channel Collection in: MM8000 (or MK8000) System Physical configuration Station (or FEP) Channel collection You will see the NS8210 driver node (CMDSL/IP or CEI-79/IP) or the NS8011 driver (BACnet/IP). 2. Select the NK822x node. 3. For connecting to NS8210 (but not to NS8011) select the Ethernet node. 4.
Configuring networks and network components Fig. 43 Setting “Branch In Scan” and the CEI Master key in the NK822x link node Connecting NK822x to additional DMS hosts (CMSDL/IP) NK822x can be connected to additional CMSDL/IP hosts, they can support as many as four connections, including serial (max 1) and LAN (max 4) links. – The configuration of each DMS8000 host requires a separate Composer project. In order to add an additional connection, proceed as follows: 1. Select the NK822x node. 2.
Configuring networks and network components Assuming that as many as four DMS hosts are connected to the same NK822x, and that the first port (3001) is used by the first DMS (that is, the corresponding icon is linked to the NS8210 driver as described at p.55), then the configuration of the other hosts should include the links of the Ethernet icons with port 3002, 3003 and 3004, respectively.
Configuring networks and network components Note that each host node must be configured on the Node tab with the corresponding unique BACnet Device Identifier (Instance number) as shown in see Fig. 47. Then, the main node of the NK8225 can be connected to the hosts (max four connections) identified by their device identifier.
Configuring networks and network components Fig. 48 Linking an additional host connection over serial line Note that the configuration of the “additional” host will require a separate project where the NK822x will appear connected to the station over a serial line (see 3.3.1 at p.39). For example, assuming a system with one host on LAN (main DMS) and one host over serial line (additional DMS), you need 2 projects: – Project 1 (main DMS) should include an NK822x with one Ethernet link and one serial link.
Configuring networks and network components Otherwise, proceed to step 3. 3. Expand the tree structure until you reach the subsystem you want to connect. Note: If needed, you can add the serial line expansion (Fig. 50) or the LON expansion (Fig. 44-B). 4. Select the subsystem node. Note: Depending on the subsystem type, you may have to select the control unit node (such as CZ10, CS4, CZ12, etc.) or its gateway (such as CK11 for CS11, SK11 for STT11, etc.).
Configuring networks and network components Configuring the local I/O If local I/O modules are used, do the following: 2 1. Expand the NK822x folder and select the I C node. 2. Add the required modules, you can insert as many as: Two input modules DF8040 (see Fig. 52-A) One output module DF8020 (see Fig. 52-B) One power supervision module DF8090 (see Fig. 52-C) Fig.
Configuring networks and network components 3.3.4 NK822x interactions Automatic functions The NK822x configuration can include interactions, i.e. reaction programs that the NK822x executes when a specific set of incoming signals (i.e. point states) is detected. When that occurs, one or more commands are generated according to the programmed interaction logic. The incoming signals are called trigger, whereas the outgoing commands are the effects.
Configuring networks and network components Fig. 54 Adding NK822x interactions A Click this icon to add a new interaction program B Click this icon to add a new folder 5. Select the node of the new interaction and then the Node tab. Note the Interaction enabled checkbox (Fig. 55), which should be checked in order for the program to be downloaded. Fig. 55 Enabling Single Interaction Note also the Validate interactions checkbox (Fig. 59 at p.
Configuring networks and network components Fig. 56 Dragging and dropping trigger and effect signals Nodes can be linked to the Interactions only if the corresponding subsystem is linked to the local NK822x or to a networked NK82225 that must be linked, in turn, to the NSxxxx Driver. Also, note that removing these links at later time results in the configured interactions being deleted as show in the warning message that appears when such deletions occur: 7.
Configuring networks and network components Fig. 57 Defining the Interaction‟s logic 8. Edit the interaction program. Proceed as follows: 8.A Select the Trigger section: IF (trigger) The section shows with a light blue background 8.B Enter the trigger list, you can select the following statements/conditions clicking on the left menu: – Comment: to enter a text line. – Field condition: to specify an input state. – OR/XOR: to enter a logic operator and combine two conditions.
Configuring networks and network components The field conditions are specified indicating: – Field point: In the list that appears, click one of the points linked to the interaction; the points are listed with their customer text, technical text, or both (see step 7 at p.64). – Property: Open the drop-down list and select one of the properties of the point, typically “Active” or “Alarm”. The list of properties depends on the specific point.
Configuring networks and network components The commands are specified indicating: – Field point: In the list that appears, click one of the points linked to the interaction; the points are listed with their customer text, technical text, or both (see step 7 at p.64). – Property: Open the drop-down list and select one of the properties of the point, typically “Active” or “Off”. The list of properties depends on the specific point.
Configuring networks and network components Fig. 58 Programming the Interaction 9. When triggers and effects are included, the interaction is ready. At this point, the text on the top should read: “The interaction is valid”. If this is not the case, move the mouse on the (yellow) line, read the tooltip, and follow the instructions about how to complete or fix the interaction program. 10 In the Node tab of the NK822x node, do not forget to enable the checkbox Validate and download interactions (Fig. 59).
Configuring networks and network components 3.3.5 Downloading NK822x The NK822x configuration download allows loading the connectivity setting and the interaction configuration into the NK822x unit. In case of multiple DMS systems, the NK822x should be described in each DMS projects, but the download is required only once. Downloading procedure The NK822x configuration download can be performed either from the NK822x node or the NS8xxx driver node.
Configuring networks and network components Fig. 60 Testing LAN connection: successful ping check Fig. 61 Testing LAN connection: unsuccessful ping check Downloading NK822x firmware updates (optional) Note: If you receive a new NK822x firmware for an update, you need to add the new version before being able to select and download it to the NK822x units. You do this with the Add button next to the Firmware Version list (see Fig. 63). 1. Check that NK822x units respond to the ping message (see p.69) 2.
Configuring networks and network components Warning: Check again the "ping" connection of the NK822x unit before proceeding with further downloads. It is essential to wait for the NK822x to restart and respond to the ping messages. In fact, starting a new download (e.g. configuration download) before the NK822x properly restarts may results in the NK822x unit to crash and even lose its internal IP address. Should that occur, you will need to set the address again using the NW8202 tool.
Configuring networks and network components 1. Check that NK822x units respond to the ping message (see p.69). 2. Open the Channel collection in DMS. 3. Select the NS8210 or NS8011 driver node and then the Download tab. Fig. 63 Downloading NK822x configuration and firmware 4. Select one or more branches (NK822x) in the list in the upper part of the form. See Fig. 63. Note: In order to select multiple branches, keep the CTRL key pressed while you make your selections. 5.
Configuring networks and network components Fig. 64 Controlling and checking NK822x In case of insufficient RAM for allocating the protocol software related to the selected subsystems, some of the protocols may not be downloaded. 73 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring networks and network components 3.4 Configuring BACnet BACnet is a building automation and control networking protocol designed to meet the communication needs of building automation and control systems. After specific enhancements, BACnet can also fully support safety and security applications. DMS8000 uses BACnet in combination with IP networks (typically Ethernet). That solution is called BACnet/IP. 3.4.
Configuring networks and network components Fig. 66 BACnet Tab showing the Device Identifier Multiple IP subnets BBMD routers A BACnet/IP network comprising multiple IP subnets require IP routing services – provided by standard IP equipment– and additional BACnet routing services by a BBMD device (BACnet Broadcast Management Device). BBMD devices handle the BACnet broadcast messages across multiple IP subnets.
Configuring networks and network components 3.5 Serial to network adapters Serial to network adapters (e.g. Lantronix UDS1100) allow for the LAN connection to DMS8000 systems, converting the serial line traffic into network packets and vice versa. On the DMS8000 station, network communication functions are required to acquire the messages. In some cases (SI410 Sintony, see 5.1.3 at p.162), DMS8000 software can directly handle this acquisition.
Configuring networks and network components Fig. 67 UDS1100 Device Installer Once the IP address is set, you can access the UDS1100 unit using a web browser: just type in the IP address. The resulting page provides access to further pages for configuring (UDS Setting: please see serial and network settings) and installing the device. 3.5.1.1 Serial port redirection at DMS8000 server level When the serial connection is “tunnelled” over a network link.
Configuring networks and network components Fig. 69 LANTRONIX Redirector: COM ports setup Then, click Advanced and: Set the TCP keep alive time to 30000 ms Check the Run as a service box Confirm with OK To correctly run the Lantronix Redirector in service mode, it is necessary to manually remove a registry value. Open the Windows registry editor and delete the key: "Redirector"="C:\\Program Files\\Lantronix\\Redirector\\red32.exe" under the [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru
Configuring networks and network components Fig. 71 LANTRONIX Redirector: Service setup As final step, click Port Settings and configure the parameters shown in Fig. 72: Fig. 72 LANTRONIX Redirector: Port settings Confirm with OK, then Save, and finally Close the configuration. At this point, a reboot may be required. The new (virtual) COM port is now available as shown in the Windows hardware / Device manager list (see example below).
Configuring networks and network components 3.6 Adjusting network settings Once you have connected the network subsystems to the network drivers, you can adjust the network parameters. The type of network determines which setting you can adjust. They include: Physical layer settings: Port, Baud Rate, Character Bits (Cerloop, CDI-Net, Sintony).
Configuring networks and network components Fig. 77 Adjusting NK8000 network settings Communication parameters Serial Port and Baud Rate settings should match the physical connection and settings on the connected hardware. The flow control parameters do not usually need any adjustment. They are available for the special cases where the status request issued by the DMS towards the control units may create peaks of incoming traffic unsustainable for the network.
Configuring control units – Fire 4 Configuring control units – Fire This section describes how to configure the fire control unit subsystems. The list includes: FS20 CS11 AlgoRex FC700A CS1115 SIGMASYS/D100 CZ10 STT11, STT20, STT2410 4.1 Configuring an FS20 FS20 systems The FS20 is a comprehensive and versatile fire detection and extinguishing system.
Configuring control units – Fire FCnet with FS20 stations interconnected via SAFEDLINK: DMS8000 systems connect to a main FC20 station (CAP) that, in turn, connects to other FC20 stations on the redundant SAFEDLINK loop. Ethernet FC20 CAP Station SAFEDLINK Fig. 80 FS20 SAFEDLINK architecture FCnet with FS20 stations interconnected via Ethernet and SAFEDLINK (mixed solution). Ethernet FC20 CAP Station SAFEDLINK Fig.
Configuring control units – Fire 4.1.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number and structure of FS20 systems. IP and Bacnet network addressing of FC20 stations. The SiBX file(s) exported by the FS20 configuration tool and describing the entire FS20 system(s).
Configuring control units – Fire 4.1.2 Configuration procedures Adding NS8011 Network Driver 1. In the Composer project, select the Channel collection in: MM8000 (or MK8000) System Physical configuration Station (or FEP) Channel collection 2. In the command bar on the left, click the NS8011 BACnet Driver. A new node is added to the project structure. Configuring the Driver BACnet parameters 1. Select the new NS8011 BACnet Driver node. 2. Select the Node tab 3.
Configuring control units – Fire These parameters, and specifically all ADPU timeouts, should match the corresponding ones in FS20. The following parameters can be customised: Maximum message latency time ADPU timeouts ADPU segment timeouts Number of ADPU retries Fig. 82 Setting the Driver BACnet parameters Adding the folder for the FC20 system Create a folder for the FS20 components. Adding the FS20 system node 1. Select the new folder. 2. In the left-hand bar, select the Fire folder icon (Fig. 83).
Configuring control units – Fire Fig. 83 Adding a new FS20 node Importing the FS20 SiBX metafile 1. Select the FS20 node. 2. Select Tools Import in the Composer menu to start FS20 import. After a confirmation request, 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.
Configuring control units – Fire Checking imported BACnet parameters Beyond the node structures of the stations, the import procedure acquires the BACnet parameters set in the FS20 system. This information is shown in the Node tab of the FS20 System (Fig. 85) and FC20 stations (Fig. 86). Fig. 85 Example of FS20 System BACnet settings In the FS20 System settings, the BACnet Client Configuration section shows the valid Client Identifiers for FS20.
Configuring control units – Fire Fig. 87 Linking FC20 station to NS8011 Network Driver Tip: If many FC20 stations have to be linked to the network driver, you can profit of the Composer grid mode and link all stations in one shot.
Configuring control units – Fire Fig. 88 Setting individual/general ack/reset Warnings: – Note that moving objects in FS20 tool may result in inconsistent results in DMS8000 as the objects are deleted and then added again as new items during the subsequent import (same issue as in CS11 AlgoRex). – The time zone setting must be exactly the same in FS20 systems and DMS8000 in order to get a consistent time display.
Configuring control units – Fire 4.2 Configuring a CS11 General architecture The CS11 AlgoRex is a fire-detection and extinguishing system, which is physically made up of: CC11 control unit(s) with separated control panels (CT11) CK11 gateway(s) CI11 control unit(s), an integrated model that includes the CT11 control panel All of these units are connected over a local bus (C-Bus). The CC11 units handle the actual fire detection and the appropriate alarming outputs.
Configuring control units – Fire 4.2.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number, version (EP5 or EP7), and model (Data Base Variant) of CS11 systems. The number of CC11 units and CK11 gateways for each CS11. The local address (address 110, 111, 112, etc.) for each unit and gateway.
Configuring control units – Fire CONFIGURING A CS11 1. Add the folder(s) required for identifying the location of the CS11 in the project structure tree. p. 94 2. Add the CS11 EP5 or CS11 EP7 node to the new folder p. 94 3. Set the CC11 Local Address and Vitality Timer p. 95 4. Set the CC11 metafile p. 96 5. Import the CC11 metafile p. 96 6. Repeat steps 3 through 5 for the remaining CC11s. 7. Add the CK11 node to the CS11 system node p. 98 8.
Configuring control units – Fire 4.2.2 Configuration procedures The following are the configuration procedures for the CS11 system: Adding the folder for the CS11 system 1. Open the Composer project. 2. Create a folder for the Fire / AlgoRex components. Adding the CS11 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 one of the CS11 system icons to add a CS11 node: CS11 EP5 (see Fig. 89-A) or CS11 EP7 (see Fig. 89-B).
Configuring control units – Fire Adding the CC11 node to the CS11 system node 1. Select the CS11 node. 2. Select one of the CC11 icons: (CC11 EP5) or (CK11 EP5) or (CK11 EP7) or (CC11 EP7) to add a CC11 node in the CS11 (see Fig. 91 and Fig. 92 for EP5 and EP7, respectively). A new node is added to the project structure. Fig. 91 Selecting the icon to add a CC11 control unit in a CS11 EP5 A Click this icon to add a CC11 EP5 B Click this icon to add a CK11 gateway Fig.
Configuring control units – Fire The Vitality Timer is related to the frequency of the heartbeat message periodically transmitted by the control unit. This value is the maximum tolerated delay in seconds, and should be 3 to 6 times as long as the heartbeat message. For example, if the heartbeat message is 30 seconds, you set the Vitality Timer to 90 to 180 seconds.
Configuring control units – Fire Fig. 94 Starting CC11 import After a confirmation request, the software presents a browsing window to search for the file to import (a metafile with extension TXT is expected). 3. Using standard Windows controls, do the following: Locate the file Select it and click Open (see Fig. 95) Fig. 95 Selecting the metafile to import In a few moments, the CC11 structure is imported, and the node is represented in the Composer tree.
Configuring control units – Fire Fig. 96 Manual matching of CC11 objects Adding the CK11 interface node to the CS11 system node After adding all the CC11s, you need to add the CK11 interface node to the CS11 system node. Perform the following steps: 1. Select the CS11 node. 2. Select one of the CK11 icons: (CK11 EP5) or (CK11 EP7) to add the CK11 interface node (see Fig. 91 and Fig. 92 for EP5 and EP7, respectively). A new node is added to the project structure.
Configuring control units – Fire 2. Select ToolsImport in the Composer menu to start CK11 import (see Fig. 94). Connecting a CS11 directly to the DMS8000 With DMS8000 it is possible to connect a CS11 (whose CK11 is set for ISO1745 communication) directly to the DMS8000 server instead of through a network. After you have set the vitality, do the following: 1. Drag the CK11 to the DMS8000 Cerloop Driver for each CS11. 2. In the link node that appears, set the communication parameters (see 3.6 at p.80).
Configuring control units – Fire Fig. 98 Linking CK11 to a NK8000 network (NK8223, COM3) When the link is established, a new node appears on the structure tree, and its properties can be seen on the Link tab of both connected nodes (see Fig. 99). Fig. 99 New link to a CK11 in the GW21 line 100 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Fire 4.3 Configuring a CS1115 The CS1115-x and CS1115-ECO are fire detection systems. Both subsystems support a number of basic features in a pre-assembled unit and additional options. The list includes: One (CS1115-ECO) or two (CS1115-x) Loops or Collective Lines. 2, 4, and 16 Loops/Lines extensions are available for CS1115-x. Four inputs (16 I/O contacts may be optionally added). Remote transmission outputs and power supply unit.
Configuring control units – Fire CONFIGURING A CS1115 1. Add the folder(s) required for identifying the location of the CS1115 in the project structure tree p. 103 2. Add the CS1115 system node to the new folder 3. Import the internal configuration p. 104 – OR – enter the fire system configuration, including Physical and Logical structure: - CS1115-x ............................................................................................... p. 104 - CS1115-ECO ...............................
Configuring control units – Fire 4.3.2 Configuration procedures – CS1115 systems The following are the configuration procedures for the CS1115 subsystems: Adding the folder for the CS1115 systems 1. Select the new folder. 2. In the left-hand bar, select the folder icon to create a folder for the fire protection components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab (for example, “Fire”). Adding the CS1115 system node 1.
Configuring control units – Fire Importing the CS1115 metafile 1. Select the CS1115 node. 2. Select ToolsImport in the Composer menu to start the import procedure. After a confirmation request, the software presents a browsing window to search for the file to import (a metafile with extension C15 is expected). 3. Using standard Windows controls, do the following: Locate the file Select it and click Open In a few moments, the CS1115 structure is imported, and the node is represented in the Composer tree.
Configuring control units – Fire - or select the Collective Line icon and the Loop icon once to add a collective line node, once to add a loop node. 4. Select the K3L110 icon (“G”) to add a K3L110 node. Adding this node inserts 16 input nodes. 5. Select the K3M030 icon (“D”) to add a K3M030 node. 6. Choose, based on customer requirements, either the K3M010 or K3M020 (“F”) icon (“E”) to add the respective node. 7.
Configuring control units – Fire Fig. 104 CS1115-x Logical tree icons A B CS1115-x logical tree component icons: Control Zone Fire Zone 2. Select the Fire Zone icon (“B”) and add up to 512 fire zone nodes by continuing to select the icon (keep the SHIFT key pressed when clicking to invoke the multiple insert feature). 3.
Configuring control units – Fire 4. Drag and drop the appropriate collective line nodes to all the appropriate fire zone nodes located in the logical tree. Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . When the link is established, a new node appears on the structure tree, and its properties can be seen on the Link tab of both connected nodes Fig. 106 Valid Collective Line links: drag Collective Lines to Fire Zones 4.3.
Configuring control units – Fire Fig. 107 CS1115-ECO Physical Tree icons A B C D CS1115-ECO physical tree component icons: Input Loop Collective Line K3L110 (“A”) to add up to 4 Input nodes. 2. Select the Input icon 3. Do one of the following, based on configuration requirements: Select the Loop icon - or - (“B”) to add a loop node select the Collective Line icon 4. Select the K3L110 icon (“C”) to add a collective line node (“D”) to add a K3L110 node. Adding this node inserts 16 input nodes.
Configuring control units – Fire Fig. 109 CS1115-ECO Logical tree icons A CS1115-ECO logical tree component icons: Control Zone B Fire Zone 2. Select the Fire Zone icon (“B”) and add up to 128 fire zone nodes by continuing to select the icon (keep the SHIFT key pressed when clicking to invoke the multiple insert feature). 3.
Configuring control units – Fire Connecting collective lines to fire zones Expand the Physical Tree. If this node contains a collective line node, select it, and drag and drop to all the appropriate fire zone nodes located in the logical tree. Note: You cannot link collective lines to fire zone nodes containing detector nodes. Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon .
Configuring control units – Fire 3. Select the Serial Port in the the Node tab of the link node (Fig. 113). Fig. 113 Selecting the Serial Port for CS1115 communication 111 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Fire 4.4 Configuring an FC700A The FC700A is a fire detection system that is physically made up of: FC700A control unit(s) FG700A gateway(s) The FC units handle the actual fire detection and the appropriate alarming outputs. Instead, the FG provides the serial connectivity to a larger system. The physical components are hosted in cabinets equipped with adequate power supply and connectivity to the required external devices.
Configuring control units – Fire DMS8000 connection MM8000 station LAN RS232 E3H02x FC700A 4.4.2 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number of FC700A systems. The number of FC units and FG gateways for each system. The local address (address 110, 111, 112, etc.) for each unit and gateway.
Configuring control units – Fire CONFIGURING AN FC700A 4.4.3 1. Add the folder(s) required for identifying the location of the FC700A in the project structure tree p. 114 2. Add the FC700A system node to the new folder p. 114 3. Add the FC700A unit node to the system node p. 115 4. Set the FC700A unit Local Address and Vitality Timer p. 115 5. Import the FC700A unit metafile p. 116 6. Repeat steps 3 through 5 for the remaining units of the system. 7.
Configuring control units – Fire Fig. 114 Selecting the icon to add a FC700A system A Click this icon to add a FC700A system Adding the FC700A control unit to the system node 1. Select the FC700A system node. 2. Select the FG700A (see Fig. 115-A) or the FC700A (see Fig. 115-B) control unit icon to add a FC700A control unit. A new node is added to the project structure. Fig.
Configuring control units – Fire The Vitality Timer is related to the frequency of the heartbeat message periodically transmitted by the control unit. This value is the maximum tolerated delay in seconds, and should be 3 to 6 times as long as the heartbeat message. For example, if the heartbeat message is 30 seconds, you set the Vitality Timer to 90 to 180 seconds.
Configuring control units – Fire 3. Using standard Windows controls, do the following: Locate the file Select it and click Open (see Fig. 118) Fig. 118 Selecting the metafile to import In a few moments, the FC700A structure is imported, and the node is represented in the Composer tree. Some FC700A objects that have been renumbered in the local configuration tool may need to be manually re-assigned to the existing Composer nodes during the subsequent import.
Configuring control units – Fire 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.
Configuring control units – Fire Fig. 120 Linking FG700A to the DMS8000 station (direct link) Fig. 121 Linking FG700A to a NK8000 network (NK8223, COM1) When the link is established, a new node appears on the structure tree, and its properties can be seen on the Link tab of both connected nodes (see Fig. 122). Fig. 122 New link to FG700A in the NK8000 network 119 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Fire 4.5 Configuring an FC330A The FC330A-x and FC330A-ECO are fire detection systems. Both subsystems support a number of basic features in a pre-assembled unit and additional options. The list includes: One (FC330A-ECO) or two (FC330A-x) Loops / Collective Lines. 2, 4, and 16 Loops/Lines extensions are available for FC330A-x.
Configuring control units – Fire CONFIGURING AN FC330A 1. Add the folder(s) required for identifying the location of the FC330A in the project structure tree p. 122 2. Add the FC330A system node to the new folder 3. Import the internal configuration p. 123 – OR -enter the fire system configuration, including Physical and Logical structure: - FC330A-x .................................................................................................. p. 123 - FC330A-ECO ............................
Configuring control units – Fire 4.5.2 Configuration procedures – FC330A systems The following are the initial configuration procedures for both of the FC330A subsystems: Adding the folder for the FC330A systems 1. Select the Field node. 2. Select the folder icon to create a folder for the fire protection components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab (for example, “Fire”). Adding the FC330A system node 1.
Configuring control units – Fire Importing the FC330A metafile 1. Select the FC330A node. 2. Select ToolsImport in the Composer menu to start the import procedure. After a confirmation request, the software presents a browsing window to search for the file to import (a metafile with extension C15 is expected). 3. Using standard Windows controls, do the following: Locate the file Select it and click Open In a few moments, the FC330A structure is imported, and the node is represented in the Composer tree.
Configuring control units – Fire - or select the Collective Line icon and the Loop icon once to add a collective line node, once to add a loop node. 4. Select the K3L110 icon (“G”) to add a K3L110 node. Adding this node inserts 16 input nodes. 5. Select the K3M030 icon (“D”) to add a K3M030 node. 6. Choose, based on customer requirements, either the K3M010 or K3M020 (“F”) icon (“E”) to add the respective node. 7.
Configuring control units – Fire Configuring the logical tree 1. Expand the FC330A-x node and select the Logical Tree node. Fig. 127 FC330A-x Logical tree icons A B FC330A-x logical tree component icons: Control Zone Fire Zone 2. Select the Fire Zone icon (“B”) and add up to 512 fire zone nodes by clicking the icon again (keep the SHIFT key pressed when clicking to invoke the multiple insert feature). 3.
Configuring control units – Fire 2. Expand the K3M030 subfree in the Physical Tree if this node contains any collective line nodes, select the appropriate Collective Line node, and drag and drop to all of the appropriate fire zone nodes located in the logical tree. 3. Expand either the K3M010 or the K3M020 node 4. Drag and drop the appropriate Collective Line nodes to all the appropriate Fire zone nodes located in the Logical Tree.
Configuring control units – Fire 4.5.4 Configuration procedures – FC330A-ECO The following are the configuration procedures for the FC330A-ECO subsystem, which are similar to those for the FC330A-x but with fewer components: Configuring the physical tree 1. Expand the FC330A-ECO node and select the Physical Tree node. Fig. 130 FC330A-ECO Physical Tree icons A B C D FC330A-ECO physical tree component icons: Input Loop Collective Line K3L110 (“A”) to add up to 4 Input nodes. 2.
Configuring control units – Fire Fig. 131 FC330A-ECO Physical Tree configuration example Configuring the logical tree 1. Expand the FC330A-ECO node and select the Logical Tree node. Fig. 132 FC330A-ECO Logical tree icons A B FC330A-ECO logical tree component icons: Control Zone Fire Zone 2. Select the Fire Zone icon (“B”) and add up to 128 fire zone nodes by continuing to select the icon (keep the SHIFT key pressed when clicking to invoke the multiple insert feature). 3.
Configuring control units – Fire Connecting collective lines to fire zones Expand the Physical Tree. If this node contains a collective line node, select it, and drag and drop to all the appropriate fire zone nodes located in the logical tree. Note: You cannot link collective lines to fire zone nodes containing detector nodes. Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . Fig.
Configuring control units – Fire 4.5.5 Linking an FC330A system to the DMS 1. Expand the Management Station folder until you reach the NS8015 driver: Physical Configuration Channels Collection NS8015 Fire CNDL 2. Drag the CS1115-ECO node to the NS8015 Fire CNDL node (see Fig. 135). Fig. 135 Linking CS1115 to the DMS system When the link is established, a new node appears on the structure tree, and its properties can be seen on the Node tab. 3.
Configuring control units – Fire 4.5.6 FC330 configuration tips Configuring the communication port in FC330A In FC330A, in order to enable the communication prodotol on the serial port, you need to configure the unit at control panel level (please also refer to FC330A Manual n.1583). Follow this procedure: 1. Press “Start” and login for operating access (password required) 2. Select option 4 (“Other Functions”) 3. Select option 4 (“Configuration”) 4.
Configuring control units – Fire 4.5.7 FC330 facts and limitations FC330A and CS1115 cannot be connected via NK8000 Automatic zones, manual zones, sprinkler zones etc.
Configuring control units – Fire 4.6 Configuring SIGMASYS/D100 The SIGMASYS/D100 is a family of fire systems that includes: SIGMASYS fire control units D100 fire system These systems can communicate with a head-end host using the VBF (Virtuelle BedienFeld Schnittstelle) protocol. The NK822x network units can communicate over serial lines using the VBF protocol and to convert the application messages appropriately.
Configuring control units – Fire CONFIGURING A SIGMASYS/D100 4.6.3 1. Add the folder(s) required for identifying the location of the SIGMASYS/D100 in the project structure tree. p. 134 2. Add the SIGMASYS/D100 control unit node to the new folder. p. 134 3. In the PLAN D100 tool, create the configuration files. p. 135 4. Import the configuration file. p. 135 5. Link the SIGMASYS/D100 to the communication network. p. 136 6.
Configuring control units – Fire Fig. 137 Adding a SIGMASYS/D100 subsystem The unit just added should be the one that can communicate with DMS8000 via NK822x (master node). In case of complex architectures including multiple units, other SIGMASYS/D100 can be added below the master node in order to represent e.g. an SM88 system (just select the master node and insert the other units).
Configuring control units – Fire In the folder, locate the XML file (note that the required EXP file is automatically found and processed). Select the file and click Open. The Panels List windows shows the panels included in the export file. Fig. 138 SIGMASYS/D100 panels to import Select one the panel and click OK. In a few moments, the SIGMASYS/D100 internal structure is imported.
Configuring control units – Fire Fig. 139 Link SIGMASYS/D100 to the NK8000 network When the link is established, a new node appears on the structure tree, and its properties can be seen on the Node tab. 137 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Fire 4.7 Configuring a CZ10 The CZ10 is a danger detection control unit handling the risk sectors Fire, Extinguishing, Gas and Building Services. The basic control unit (master) permits the connection of 24 collective, or 24 individually addressable signal lines. Physically, the CZ10 is composed of a central module, hosted in a cabinet, and connected to signal lines and alarming devices. Authorised operators can operate the system locally on a CT10 terminal.
Configuring control units – Fire 4.7.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The CZ10 parameter settings, which can be provided in three ways: – The DMS7000 metafile to import – The LMSmodular databases DB_PUL.DBF and DB_SUB.
Configuring control units – Fire 4.7.2 Configuration procedures The following are the configuration procedures for the CZ10 system: Adding the folder for the CZ10 system 1. Open the Composer project. 2. Create a folder for the Fire / CZ10 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab (for example, “Fire”). Adding the CZ10 system node 1. Select the new folder. 2. In the left-hand bar, select the Fire folder icon 3.
Configuring control units – Fire 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.
Configuring control units – Fire In a few moments, the CZ10 structure is imported, and the node is represented in the Composer tree. Defining the CZ10 physical configuration If you were not able to import the configuration, you will need to configure the CZ10 by hand to reflect the actual hardware configuration.
Configuring control units – Fire 3. Drag and drop the CZ10 node to the network node (see Fig. 143 and Fig. 144). Note: The valid link position for Cerloop is always the same main node, representing the entire loop. The valid link positions on CDI-Net/NK8000 gateways are distributed along the subsystem lines. Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . Fig. 143 Linking CZ10 to a Cerloop network Fig.
Configuring control units – Fire 4.8 Configuring an STT11 STT11 system is designed to perform automatic actions (called “fire actuations”) following the detection of a fire alarm by a CS11 AlgoRex unit. It operates with a CS11 in a common Cerloop network. STT11 is made up of a physical and logical tree.
Configuring control units – Fire CONFIGURING AN STT11 4.8.2 1. Add the folder(s) required for identifying the location of the STT11 in the project structure tree. p. 145 2. Add the STT11 system node to the new folder p. 145 3. Add the STT11 CPU node to the new folder p. 146 4.Set the STT11 Local Address and Vitality Timer p. 146 5. Import the STT11 metafile p. 147 6 Repeat steps 3 to 5 for the remaining STT11 CPU (max. 2) 7. Add the SK11 node to the STT11 system p.
Configuring control units – Fire Fig. 145 Selecting the icon to add an STT11 subsystem Adding the STT11 CPU node 1. Select the STT11 System node. 2. Select the STT11 CPU icon to add a CPU unit to the STT11 system (see Fig. 146). A new node is added to the project structure. Fig. 146 Selecting the icon to add an STT11 CPU Setting the STT11 CPU Local Address and the Vitality Timer 1. Select the STT11 CPU node. 2. In the Node tab, set the Local Address and the Vitality Timer (see Fig. 147).
Configuring control units – Fire 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.
Configuring control units – Fire Fig. 148 Selecting the icon to add the SK11 node 3. Select the new SK11 node. 4. Set the Local Address and Vitality Timer (see page 146). Linking the SK11 to the Communication network It is now necessary to include the STT11 system in the communication network. You do this by linking the SK11 to the network node it belongs to. Proceed as follows: 1. Expand the network folders until you reach the node that represents the Cerloop network physically connected to the SK11. 2.
Configuring control units – Fire 4.9 Configuring an STT20 STT20 system is designed to perform automatic actions (called “fire actuations”) following the detection of a fire alarm by a CS11 AlgoRex unit. It operates with a CS11 in a common Cerloop network. STT20 is made up of a physical and logical tree. The fire system is logically organised in a 4-level structure (Area, Sections, Functions, Elements) like the STT11 unit.
Configuring control units – Fire 4.9.2 Configuration procedures The following are the configuration procedures for the STT20: Adding the folder for the STT20 system 1. Open the Composer project. 2. Create a folder for the STT20 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the STT20 system node 1. Select the new folder. 2. In the left-hand bar, select the Fire folder icon 3.
Configuring control units – Fire 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.
Configuring control units – Fire Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . Fig. 152 Connecting the STT20 node to the Cerloop network When the link is established, a new node appears on the structure tree, and its properties can be seen on the Node tab. 152 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Fire 4.10 Configuring an STT2410 STT2410 system is designed to perform automatic actions (called “fire actuations”) following the detection of a fire alarm by Fire detection unit. In the Composer configuration, the only supported architecture is the Cerloop network. The physical and logical configuration for an STT2410 is first defined for the hardware unit set-up.
Configuring control units – Fire 4.10.2 Configuration procedures The following are the configuration procedures for the STT2410: Adding the folder for the STT2410 system 1. Open the Composer project. 2. Create a folder for the STT2410 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the STT2410 system node 1. Select the new folder. 2. In the left-hand bar, select the Fire folder icon 3.
Configuring control units – Fire Fig. 154 Setting STT2410 Local Address Configuring the STT2410 internal structure 1. Select the STT2410 node. The default structure includes the following nodes: Fig. 155 Default STT2410 structure 2. Select the Controls node The Line command becomes available in the toolbar. Fig. 156 STT2410 „Line‟ command icon 3. Click the Line icon to add a line Repeat as many times as required by the STT2410 configuration. 4.
Configuring control units – Fire Fig. 157 STT2410 Input/Output command icon 5. Click the Input/Output command icon to add an I/O signal Repeat as many times as required by the STT2410 configuration. Linking the STT2410 to the Communication network It is now necessary to include the STT2410 system in the communication network. You do this by linking the STT2410 node to the network node it belongs to. Proceed as follows: 1.
Configuring control units – Intrusion 5 Configuring control units – Intrusion This section describes how to configure the intrusion control unit subsystems. The list includes: CS6 Guarto SI410 Sintony CS4 CS440 CZ12 5.1 Configuring a CS6 Guarto 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.
Configuring control units – Intrusion 5.1.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number of CS6 in the system. The CS6 metafiles (CNAP profile files). The CerCom/LON addresses (Subnet, Node, Logical address) for each unit. The connection to the network on CerCom/LON.
Configuring control units – Intrusion 5.1.2 Configuration procedures The following are the configuration procedures for the CS6 system. Adding the folder for the CS6 system 1. Open the Composer project. 2. Create a folder for the Intrusion/CS6 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the CS6 system node 1. Select the new folder. 2. In the left-hand bar, select the Intrusion folder icon 3.
Configuring control units – Intrusion 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. 160 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Intrusion Linking the CS6 to the Communication network To link the CS6 node to the NK822x node, do the following: 1. Expand the network folders until you reach the node that represents the NK8000 network node physically connected to the CS6. 2. Select the CS6 node. 3. Drag and drop the CS6 node to the CerCom LON network node depending on the type of NK node (see Fig. 160). Note: The valid link position for Cerloop is always the same main node, representing the entire loop.
Configuring control units – Intrusion Fig. 161 Setting CS6 addresses on CerCom/LON bus 5.1.3 Commissioning tips Commissioning procedure In order to properly set the BACnet logical address on the LON network, we recommend the following procedure: Switch off power of CS6 control unit(s). Connect CS6 unit(s) to NK822x on the LON network. Switch on power of CS6 control unit(s): after power-up, CS6 has no BACnet logical address. Reset NK822x. Upon starting up, NK822x distributes the BACnet logical addresses.
Configuring control units – Intrusion 5.2 Configuring a SI410 Sintony The SI410 Sintony is an intrusion detection unit with individual addressing and access control capability. It can handle detection lines on which transponder units can concentrates alarm inputs and outputs. Inputs can be operated in groups, organised in Rooms, Wards, and Clusters.
Configuring control units – Intrusion DMS8000 connection SYLCOM tool connection (serial) SYLCOM tool connection (LAN) MM8000 + Sylcom MM8000 station MM8000 station LAN LAN LAN RS232 RS232 RS232 J10 J10 Sylcom SI410 SI410 J10 RS232 J7 SI410 SMN36 C - Network connection via adapters The use of serial-to-network adapter permits the LAN connection to DMS8000 using the SI410 Sintony serial port. The internal adapter SMN36 or an external device (e.g.
Configuring control units – Intrusion 5.2.2 SI410 connectivity: technical notes 5.2.2.1 SI410 Sintony: internal options and settings Serial ports The SI410 Sintony can provide serial connectivity to host computers on the port J7 and J10 (please refer to SI410 documentation). Port J7 is used for connecting to the Sylcom PC, whereas J10 is used for DMS8000. In the connection solutions to DMS8000, the J10 port is used in the configuration A and B (see 5.2.1) as well as in the network configuration C (see 5.
Configuring control units – Intrusion Fig. 162 Sintony configuration for network connectivity Further options required in the Sylcom tool In order to be able to reset alarms from DMS8000 with no need of unsetting the Ward, make sure to enable the Clear Al.Mem Full Set option in the System Properties. 5.2.3 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows.
Configuring control units – Intrusion CONFIGURING AN SI410 SINTONY 1. Generate the Sintony metafile. 2. Add the folder(s) required for identifying the location of the SI410 in the project structure tree. p. 171 3. Add SI410 system node to the new folder p. 171 4. Import the metafile p. 171 5. Link the SI410 to the communication line p. 172 6. Configure the serial or network link options p. 172 7. Repeat the steps above for all the SI410s in the project. p.
Configuring control units – Intrusion 5.2.4 Generating the Sintony metafile Configuration uploading tool The Sintony physical and logical configuration should be saved into an export file (metafile) in order to import it into Composer. The metafile is generated by the Sintony Uploader tool that is capable of acquiring the configuration data from the Sintonycontrol unit over the serial line. This tool is one of the utilities available in the DMS8000 products.
Configuring control units – Intrusion Fig. 163 Sintony Uploader: selecting the connection type Fig. 164 Sintony Uploader: Auto-detecting the COM port 4. At this point, press Next and let the Read Data page show up. 5. Then press the Start button. The software starts communicating with the Sintony and acquiring the configuration data over the serial line. An item list and a progress bar show the activities and the uploading results (see Fig. 165). Fig.
Configuring control units – Intrusion Note: In case of errors, check the Sintony firmware release (compare with latest requirements in the DMS8000 product Release Notes). 6. When the upload process has completed, a success message appears. Click OK to acknowledge it. 7. Save the uploaded data. You have now to select the file name and destination folder of the metafile. Use the browsing button to open the navigation windows (see Fig. 166). Fig. 166 Sintony Uploader: Saving the configuration 8.
Configuring control units – Intrusion 5.2.5 Configuration procedures The following are the configuration procedures for the SI410 system. Adding the folder for the SI410 system 1. Open the Composer project. 2. Create a folder for the Intrusion / SI410 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the SI410 system node 1. Select the new folder. 2. In the left-hand bar, select the Intrusion folder icon 3.
Configuring control units – Intrusion Linking the SI410 to the Communication network (NK8000) To link the SI410 node to the NK822x node, do the following: 1. Expand the network folders until you reach the node that represents the NK8000 network node physically connected to the SI410. 2. Select the SI410 node. 3. Drag and drop the SI410 Sintony node to the serial port of the NK822x node (see Fig. 168). 4. In the newly created link, configure the communication Baud Rate.
Configuring control units – Intrusion Fig. 169 Setting the serial communication options Fig. 170 Setting the network communication options 173 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Intrusion 5.3 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.
Configuring control units – Intrusion CONFIGURING A CS4 5.3.2 1. Add the folder(s) required for identifying the location of the CS4 in the project structure tree. p. 175 2. Add the CS4 system node to the new folder. 3. Set the CS4 Local Address, Vitality Timer, and Sub type ......................... p. 176 4.Import the CS4 List file. 5. Link the CS4 to the Communication device line, according to the communication links. p. 177. 6.
Configuring control units – Intrusion Fig. 171 Selecting the icon to add a CS4 subsystem 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.
Configuring control units – Intrusion 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. 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.
Configuring control units – Intrusion 5.4 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.
Configuring control units – Intrusion 5.4.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number of CS440s in the system. The local address (111, 112, etc.) for each unit. The metafile generated by the CS440 tool for each unit The connection to the DMS: Cerloop, CDI-Net, or NK8000.
Configuring control units – Intrusion 5.4.2 Configuration procedures The following are the configuration procedures for the CS440 system: Adding the folder for the CS440 system 1. Open the Composer project. 2. Create a folder for the Intrusion/ CS440 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the CS440 system node 1. Select the new folder. 2. In the left-hand bar, select the Intrusion folder icon 3.
Configuring control units – Intrusion 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.
Configuring control units – Intrusion Fig. 174 Linking CS440 to NK8223 When the link is established, a new node appears on the structure tree, and its properties can be seen on the Node tab. 182 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring control units – Intrusion 5.5 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.
Configuring control units – Intrusion 5.5.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The CZ12 parameter settings, which can be provided in three ways: – The DMS7000 metafile to import – The LMSmodular databases DB_PUL.DBF and DB_SUB.
Configuring control units – Intrusion 5.5.2 Configuration procedures The following are the configuration procedures for the Intrusion/CZ12 system: Adding the folder for the CZ12 system 1. Open the Composer project. 2. Create a folder for the Intrusion/ CZ12 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the CZ12 system node 1. Select the new folder. 2. In the left-hand bar, select the Intrusion folder icon 3.
Configuring control units – Intrusion 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.
Configuring control units – Intrusion Door monitoring zones Users Time programs Linking the zones to the sections Drag and drop the zones to the sections where they belong. Linking the CZ12 to the Communication network Link the CZ12 node to the Cerloop, CDI-Net, or NK8000: 1. Expand the network folders until you reach the node that represents the network physically connected to the CZ12 (Cerloop, CDI-Net, or NK8000). 2. Select the CZ12 node. 3. Drag and drop the CZ12 node to the network node (see Fig. 176).
Configuring other control units 6 Configuring other control units This section describes how to configure various subsystems available from Building Technologies. The list includes: CC60 Gas detection unit DMS7000 units CF9000 I/O subsystem DESIGO PX system 6.1 Configuring a CC60 The CC60 is a gas detection unit. The system is logically organised in up to 56 zones and 56 elements, and collected in a general Gas Sector.
Configuring other control units 6.1.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The CC60 parameter settings, which can be provided in two ways: – The LMSmodular databases DB_PUL.DBF and DB_SUB.DBF to import – Complete information about the CC60 configuration: Output boards, VD60 Displays, Gas zones and elements, etc. The local address (111, 112, etc.).
Configuring other control units 6.1.2 Configuration procedures The following are the configuration procedures for the CC60 system: Adding the folder for the CC60 system 1. Open the Composer project. 2. Create a folder for the CC60 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the CC60 system node 1. Select the new folder. 2. In the left-hand bar, select the Gas folder icon 3.
Configuring other control units 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.
Configuring other control units Fig. 178 Adding VD60 Displays to a CC60 Fig. 179 Adding Output boards to a CC60 Fig. 180 Adding Outputs to an Output board in a CC60 192 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring other control units Fig. 181 Adding Gas elements to a VD60 in a CC60 Fig. 182 Adding Gas zones to a Gas sector in a CC60 Linking the gas elements to the gas zones 1. Expand the physical tree nodes until you reach the gas elements. 2. Expand the logical tree nodes until you reach the gas zones. 3. Drag and drop a gas element to the corresponding zone (see Fig. 183). Fig.
Configuring other control units 1. Locate the network node. Expand the network folders until you reach the node that represents the network that is physically connected to the CC60 (Cerloop, CDI-Net, or NK8000). 2. Select the CC60 node. 3. Drag and drop the CC60 node to the network node (see Fig. 184). Note: The valid link position for Cerloop is always the same main node, representing the entire loop. The valid link positions on CDI-Net/NK8000 gateways are distributed along the subsystem lines.
Configuring other control units 6.
Configuring other control units DMS7000 systems can provide a metafile describing the general tree structure that can be imported in Composer for DMS8000. Please refer to DMS8000 product ICC manual. 6.2.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The unit local address (111, 112, etc.). For MM7033 units, the number of installed MUX or DMX cards.
Configuring other control units CONFIGURING A DMS7000 UNIT 1. Add the folder(s) required for identifying the location of the DMS7000 unit in the project structure tree p. 198 2. Add the unit node to the new folder p. 198 3. Set the unit Local Address and Vitality Timer p. 198 4. Define the configuration (E2A032 Demultiplex or E2A041 Multiplex modules): p. 199 - MUX_MM_IE4 (48 digital inputs each) - DMX_MM_OE1 (48 digital outputs each) - MUX_MM_IE2 (24 monitored inputs each) 5.
Configuring other control units 6.2.2 Configuration procedures The following are the configuration procedures for the DMS7000 unit: Adding the folder for the DMS7000 units 1. Open the Composer project. 2. Create a folder for the DMS7000 components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the DMS7000 node 1. Select the new folder. 2. In the left-hand bar, select the Building Services folder icon 3.
Configuring other control units 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.
Configuring other control units Fig. 187 MUX_MM_IE4, 48 digital inputs (E2A041MUX card) Fig. 188 DMX_MM_OE1, 48 digital outputs (E2A032 DMX card) 200 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring other control units Fig.
Configuring other control units Note: The valid link position for Cerloop is always the same main node, representing the entire loop. The valid link positions on CDI-Net/NK8000 gateways are distributed along the subsystem lines. Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon . Fig.
Configuring other control units 6.3 Configuring a CF9000/DF8000 The DF8000/CF9000 is a family of input/output (I/O) modules that can provide distributed digital I/O over a RS485 line.
Configuring other control units 6.3.1 Configuration checklist Verify that you have satisfied the items needed in the first checklist before proceeding to the configuration checklist that follows. ITEMS NEEDED FOR CONFIGURATION The number of DF8000/CF9000 RS485 lines. The number and the model of DF8003/CF9003 CPU units for each line. The local address (0 to 15) for each unit. The module configuration for each unit, which can be provided in two ways: – The LMSmodular databases DB_PUL.
Configuring other control units CONFIGURING A DF8000/CF9000 1. Add the folder(s) required for identifying the location of the DF8000/CF9000 in the project structure tree p.206 2. Add the DF8000/CF9000 system node to the new folder p.206 3. Add the DF8003/CF9003 unit node in the subsystem p.206 4. Set the DF8003/CF9003 Local Address p.207 5a. Import the LMS database, if available -- or -5b. Proceed with defining the DF8003/CF9003 detailed configuration p.207 p.207 6.
Configuring other control units 6.3.2 Configuration procedures The following are the configuration procedures for the CF9000: Adding the folder for DF8000/CF9000 1. Open the Composer project. 2. Create a folder for the I/O components. A new node is added to the project structure. 3. Select the new folder and name it in the Description field of the Node tab. Adding the DF8000/CF9000 system node 1. Select the new folder. 2. In the left-hand bar, select the Building Services folder icon 3.
Configuring other control units Fig. 192 Selecting the icon to add a CF9003 unit Setting the Local Address of the CPU unit 1. Select the DF8003/CF9003 node. 2. In the Node tab, set the Local Address. Note: The address value should range from 0 to 15 and it should match what is set in the hardware setting of the CPU module. Importing the LMSmodular configuration 1. Select the DF8003/CF9003 node. 2. Select Tools Import in the Composer menu to start the import.
Configuring other control units Fig. 193 Adding I/O modules A Click this icon to add a DF9040 ON/OFF input modules B Click this icon to add a DF8045 supervised input module (NO) C Click this icon to add a DF9020 output modules D Click this icon to add a DF8046 supervised input module (NC) Linking the DF8000/CF9000 to the Communication network Link the DF8000/CF9000 node to the CDI-Net or NK8000: 1.
Configuring other control units Fig. 194 Linking a CF9000 to GW21 When the link is established, a new node appears on the structure tree, and its properties can be seen on the Node tab. 209 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Configuring other control units 6.4 Configuring a DESIGO PX The DESIGO PX automation system is used for control and monitoring of heating, ventilation, air-conditioning and other building services. The integration of DESIGO PX in DMS8000 is based on BACnet/IP. Note that LON-based PX units need an IP adapter in order to communicate to DMS8000.
Configuring other control units CONFIGURING A DESIGO PX 1. Add the BACnet driver 2. Add the folder(s) required for identifying the location of the DESIGO PX system in the project structure tree p. 212 3. Add the DESIGO PX node to the new folder p. 212 4. Set the DESIGO PX subscription p. 213 5. Import the DESIGO PX object file (EDE) p. 213 6. Link the DESIGO PX node to the BACnet driver p. 214 7. Customising the BACnet Notification Classes p. 214 8.
Configuring other control units 6.4.2 Configuration procedures The following are the initial configuration procedures for DESIGO PX system. Adding the NS8011 BACnet driver 1. Open the Composer Project. 2. If not already done, add the BACnet Driver (NS8011) in the path: Supervision System Setting MM8000 System Physical configuration Station (e.g. My Station) Channels collection 3. Click on the NS8011 driver icon in the icon toolbar (Fig. 195). The new driver node appears in the station folder.
Configuring other control units Setting the DESIGO PX BACnet Subscription 1. Select the DESIGO PX node. 2. If no DESIGO INSIGHT is present, then select the Perform BACnet subscription checkbox. Instead, If DESIGO INSIGHT is present, deselect the checkbox (Fig. 197). In the DESIGO INSIGHT settings, configure the DMS8000 as additional subscription host (you will need the Device ID that you can get in the Node tab of the NS8011 driver node). Fig.
Configuring other control units Fig. 198 Selecting the PX unit in the import list Linking the DESIGO PX to the Communication Network 1. Select the DESIGO PX node. 2. Expand the Management Station folder until you reach NS8011 node. -> Physical Configuration -> -> Channels Collection 3. Drag and drop the DESIGO PX node to the NS8011 BACnet driver (Fig. 199) Composer helps you in recognising a valid link by showing a shortcut Link icon instead of the circle No-link icon .
Configuring other control units 4. In the new row, click and select the Notification Class and the Event State, then click the associated DMS8000 property (CNAP Property). 5. The customised classes are listed in the configuration window. You can remove any of them by clicking on the corresponding row and then select Delete Row. Fig. 200 Customising BACnet Notification class 215 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Backing up your project 7 Backing up your project This section discusses why you should backup your project, and details how to do it. 7.1 Do I need to backup? When you leave the Composer environment, your project is saved on your hard disk in the folder (or working area) you specified and/or named when you created or restored the project. You can re-open it in this working area later.
Backing up your project Fig. 201 Starting the Project Backup Fig. 202 Backing up a project When the backup procedure is completed successfully, a message is displayed. Warning: Backup (and Restore) functions can only work on local disks. Network disk units cannot be used. Warning: note that the Composer Backup does not include product-specific files linked to the configuration but external to the Composer, e.g. HTML pages providing event treatment instructions, address book databases.
Appendix A – Network connectivity options KEY: Connection Network Upstream data-link protocol Downstream network Downstream interface device CS440 CZ12 / CS4 CS6 Guarto (via LON interface) SI410 / 420 / Plus Sintony Propriet. Direct LAN Direct LAN Direct LAN ISO1745 BACnet/IP OPC Propriet.
This page intentionally left blank 219 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Appendix B – Figure list The following is a list of images contained in this guide, and their corresponding page numbers. Fig. 1 Composer Plug-ins (Subsystem Tools or ST) installer p. 14 Fig. 2 PAK Manager p. 15 Fig. 3 Composer license p. 16 Fig. 4 Viewing / modifying PAK p. 16 Fig. 5 Importing PAK p. 17 Fig. 6 Showing the required license p. 18 Fig. 7 Starting Composer: Project Management window p. 19 Fig. 8 Naming the new project p. 19 Fig.
Fig. 36 Example of NK8225 IP connectivity to DMS8000 p. 48 Fig. 37 Configuring the parameters for NS8210 Driver p. 51 Fig. 38 Configuring the parameters for NS8011 Driver p. 52 Fig. 39 Selecting the icon to add an NK822x node p. 53 Fig. 40 Configuring IP parameters for a network with NAT gateway p. 54 Fig. 41 Configuring NK822x Ethernet and CEI-79 parameters p. 55 Fig. 42 Linking the NK822x Ethernet line to the NS8210 driver p. 55 Fig.
Fig. 77 Adjusting NK8000 network settings p. 81 Fig. 78 Standalone FS20 system p. 82 Fig. 79 FS20 Ethernet architecture p. 82 Fig. 80 FS20 SAFEDLINK architecture p. 83 Fig. 81 FS20 Mixed Ethernet and SAFEDLINK architecture p. 83 Fig. 82 Setting the Driver BACnet parameters p. 86 Fig. 83 Adding a new FS20 node p. 87 Fig. 84 Selecting FC20 subsystems to import p. 87 Fig. 85 Example of FS20 System BACnet settings p. 88 Fig. 86 Example of FS20 Station BACnet settings p. 88 Fig.
Fig. 117 Starting FC700A import p. 116 Fig. 118 Selecting the metafile to import p. 117 Fig. 119 Setting FG700A Local Address and Vitality Timer p. 118 Fig. 120 Linking FG700A to the DMS8000 station (direct link) p. 119 Fig. 121 Linking FG700A to a NK8000 network (NK8223, COM1) p. 119 Fig. 122 New link to FG700A in the NK8000 network p. 119 Fig. 123 Select the icon to add an FC330A system p. 122 Fig. 124 Choose FC330A system p. 122 Fig. 125 FC330A-x Physical tree icons p. 123 Fig.
Fig. 157 STT2410 Input/Output command icon p. 156 Fig. 158 Connecting the STT2410 node to the Cerloop network p. 156 Fig. 159 Selecting the icon to add a CS6 subsystem p. 159 Fig. 160 Linking CS6 to NK8223 (NK8223 for serial link) p. 161 Fig. 161 Setting CS6 addresses on CerCom/LON bus p. 162 Fig. 162 Sintony configuration for network connectivity p. 166 Fig. 163 Sintony Uploader: selecting the connection type p. 169 Fig. 164 Sintony Uploader: Auto-detecting the COM port p. 169 Fig.
Fig. 197 BACnet subscription: deselect if DESIGO INSIGHT is present p. 213 Fig. 198 Selecting the PX unit in the import list p. 214 Fig. 199 Linking DESIGO PX to the BACnet driver p. 214 Fig. 200 Customising BACnet Notification class p. 215 Fig. 201 Starting the Project Backup p. 217 Fig. 202 Backing up a project p. 217 225 Building Technologies Fire Safety & Security Products DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide 06.
Siemens Switzerland Ltd Building Technologies Group International Headquarters Fire Safety & Security Products Gubelstrasse 22 CH-6301 Zug Tel +41 41 724 24 24 Fax +41 41 724 35 22 www.sbt.siemens.com Document no. A6V10062425_a_en Edition 06.
