Siemens MK8000 Quick Reference Manual
  1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Server
  5. MK8000 MP4.30
  6. Quick reference manual
Siemens MK8000 Quick Reference Manual

Siemens MK8000 Quick Reference Manual

Opc server for subsystems
Hide thumbs Also See for MK8000:
Table of Contents

Advertisement

Quick Links

Download this manual
MK8000 MP4.10
OPC Server for subsystems
Installation
Function & Configuration
Commissioning
Safety Regulations
Building Technologies
Fire Safety & Security Products

Advertisement

Table of Contents
loading

Related Manuals for Siemens MK8000

Summary of Contents for Siemens MK8000

  • Page 1 MK8000 MP4.10 OPC Server for subsystems Installation Function & Configuration Commissioning Safety Regulations Building Technologies Fire Safety & Security Products...
  • Page 2 Data and design subject to change without notice. / Supply subject to availability. © 2007 Copyright by Siemens Switzerland Ltd We reserve all rights in this document and in the subject thereof. By acceptance of the docu- ment the recipient acknowledges these rights and undertakes not to publish the document nor...

  • Page 3: Table Of Contents

    Installing the MK8000 on the main (Stand-Alone) station.......30 4.7.1 Installing the MK8000 on the FEP (Distributed Systems).......32 4.7.2 Installing the MK8000 on the client (test for Distributed Systems) ..32 Testing the network communication (Distributed Systems)....34 Configuring the MK8000...............35 Configuration Checklist ................35 MK8000 architecture in the Composer project ........37...
  • Page 4 Integrating the OPC server into a network..........61 7.4.3 DCOM settings on OPC clients...............71 Integrating clients that don’t support DCOM ...........72 Appendix A. Using the System Monitor............74 Appendix B. Enabling & disabling MK8000 auto-start ........78 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007...

  • Page 5: About This Document

    BT FS Intranet. Operational and safety regulations Before beginning work on the MK8000 OPC Server, you must have read and under- stood the related documents. In particular, chapter 1 in this manual, Safety Regula- tions, p.12.
  • Page 6 Safety Regulations We have taken every possible care in preparing this manual. The contents of this manual are revised regularly and brought up to latest standards. Nevertheless, we are unable to provide any guarantee with regard to content, entirety or quality of the details contained in this manual.
  • Page 7 Sales Presentation A6V10062423_a 06.2007 MP4.10 Sales Guide A6V10062427_a 06.2007 MP4.10 Tender Specifications A6V10062419_a 06.2007 MP4.10 MP4.10 Offer Template A6V10062429_a 06.2007 MK8000 Product Datasheet A6V10062405_a 06.2007 MP4.10 Sales Presentation 007121_a 03.2003 MP1.10 Sales Guide 004970_b 03.2003 MP1.10 MT8001 Product Datasheet 006952_e 09.2005...
  • Page 8 Release Notes for MP4.10 A6V10062459_a 06.2007 MP4.10 Release Notes for MP3.20 009423_a 06.2006 MP3.20 Installation, Configuration and A6V10062407_a 06.2007 MP4.10 Commissioning (ICC) MK8000 Interface Specifications MK8000 OPC Server 004971_h 06.2006 MP3.20 CS11 EP5 004974_d 02.2004 MP1.31 CS11 EP7 007546_b 02.2004 MP1.31...
  • Page 9 Safety Regulations MK7022 007125_b 10.2003 MP1.30 CK11 EP5 007126_b 02.2004 MP1.31 CK11 EP7 007129_b 02.2004 MP1.31 SK11 007127_b 10.2003 MP1.30 NK8223 (CDI-Net) 007154_b 10.2003 MP1.30 CS6 Guarto 007545_b 02.2004 MP1.31 SI410 Sintony 008597_a 12.2004 MP3.10 CC60 007547_b 10.2003 MP1.30 NK822x 007879_b 02.2004 MP1.31...
  • Page 10 004972_a_en 12.2002 Corresponds to version 1.0 of MK8000 OPC Server Software Acknowledgments We wish to thank all the Siemens colleagues and the customers who have given us feedbacks and comments about this documentation. Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products...

  • Page 11: Definitions Of Terms

    The physical panel (for example, CS11 fire subsystems) that is connected to a group of detectors. The control unit receives messages from and sends commands to the detec- tors. When a control panel is connected to the MK8000 server, it behaves as a transla- tor between the detectors and the MK8000.

  • Page 12: Safety Regulations

    Safety Regulations This chapter describes the danger levels and the relevant safety regulations appli- cable for the use of Siemens FSP-DMS products. Please read the following sub- sections, as well as the previous section "About this document" thoroughly before beginning any work.

  • Page 13: Introduction

    DU through the installation, configuration and commissioning phases, while they configure the client for integration with the MK8000. Dur- ing this phase, the DU may need to provide information and guidance to the integration group with areas, such as the importance of certain “tags”.
  • Page 14 10 Configuration is loaded onto the station(s), and tested Commissioning, p. 52  Commissioning, p. 52 11 3rd party integration team connects OPC client to MK8000 Once the client is connected, the 3 party inte- gration team should be able to continue without further DU support 12 System is ‘acceptance tested’...

  • Page 15: What Has Been Changed In Mp 4.10

    Introduction What has been changed in MP 4.10 This section illustrates the new features of MK8000 MP4.10 in comparison with previous MP3.20. Section, Page Improvements 3.1.1, p. 16 MK8000 software requirements: .NET framework 2.0 now required 4.5, p. 26 3.1.1, p. 16 MK8000 software requirements: SQL Express 2005 and SQL 4.2.2, p.

  • Page 16: Installation

    (client/server) configurations. MK8000 and MM8000 solutions MK8000 MP4.10 can be installed both as an OPC server (as in previous versions) or integrated in the MM8000 management system. In the latter case, please refer to the system requirements in the MM8000 ICC manual (doc.no.A6V10062413).
  • Page 17 This is possible with a dedicated script provided in : <installation folder>\Utilities\Firewall Configuration In this folder, double click the file: ‘MK8000 Firewall Cnf.vbs’ to start the script pro- cedure. The script must be used on any type of MK8000 stations (Stand-Alone and FEP).

  • Page 18: Installation Types

    Installation Installation types 3.2.1 Selecting the MK8000 configuration MK8000 may be set up as a single station, as a distributed system, or as a station for performing project configuration only. The installation options include: Installation type Meaning Stand-Alone/Server Install all MK8000 software components as well as Composer station (full-featured) and the configuration tools.
  • Page 19 Installation Fig 1 Redundant server architecture When using the redundant option, the MM8000 setup procedure requires a few more parameter settings (see document no.A6V10062413). The MM8000 License Server does not run on the virtual machine. Instead, a new MM8000 setup option (‘License Station’) has been provided, which is meant for the physical machines and only includes the license-related components that need to check the physical ports.

  • Page 20: Selecting The Type Of Windows Security

    During setup, you will be also prompted to choose whether to enable the automatic start of the MK8000 server at start-up. Unless you need to perform testing or trou- bleshooting, it is usually best to enable auto-start. If you need to change this set- ting for any reason, please refer to Appendix B, "Enabling &...

  • Page 21: Installation Checklist

     DMS8000 MP4.10 Installation CD Please note that if you are migrating from an existing MK8000 to a newer version, you should refer to the Release Notes prior to performing the installation procedure. The following steps outline what you need to do to install MK8000: ...

  • Page 22: Installing Mk8000 Software

    MM8000 product installation. MK8000 architectures MK8000 OPC server may be set up as a single station or as a distributed system. On a single station PC, you need to install the MK8000 Stand-Alone software, in- cluding the OPC server and the related configuration tools.

  • Page 23: Welcome Screen

    Install MM8000 (including Composer and subsystem tools)  See MM8000 ICC manual (doc.no.A6V10062413). – Install MK8000 OPC server (including Composer and subsystem tools) Note: this option will also include the commands to install the additional Micro- soft system software described in the next paragraphs. –...

  • Page 24: Installing The Ms-Sql Server Software

    4.2.1 Installing the MSDE 2000 software On the MK8000 (and MM8000) Stand-Alone station, if SQL Server V8.00.760 is not installed already (check the MS-SQL icon in the task toolbar, see Fig 4, and the related ‘About’ window, available in the right-click menu), you need to install the MSDE package provided in the DMS8000 CD.

  • Page 25: Installing The Microsoft .Net Framework V1.1

    Selecting the SQL XML Setup Type Installing the Microsoft .NET Framework V1.1 MK8000 software requires the support of the Microsoft .NET V1.1 framework li- brary. As with other Microsoft libraries, this package is distributed free of charge and can be easily installed selecting the corresponding option in the ‘Pre- requisites’...

  • Page 26: Installing The Microsoft .Net Framework V2.0

    Successful termination of .NET framework V1.1 setup Installing the Microsoft .NET Framework V2.0 MK8000 software also requires the support of the Microsoft .NET V2.0 framework library (note that V2.0 does not replace V1.1, which remains required). As with other Microsoft libraries, this package is distributed free of charge and can be eas- ily installed selecting the corresponding option in the ‘Pre-requisites’...
  • Page 27 Accepting the .NET Framework V2.0 License Agreement Fig 11 Successful termination of .NET framework V2.0 setup Although not strictly required for MK8000 operations, the recommendation concerning the .NET framework update (see Fig 11) should be followed. Please refer to Microsoft support site at ...

  • Page 28: Mk8000 Opc Server

    Select ‘Client Station’ from the list to install the test client only. Updating previous MK8000 installations If you are migrating from an existing MK8000 to a newer version, you should refer to the Release Notes prior to performing the installation procedure.
  • Page 29 Utility files available in the <installation_folder >Utilities\Tools folder (typically C:\Program Files\DMS8000\Utilities\Tools...): Composer Preferences – allow for modifying the Composer project folder. – Empty database – clears the runtime MK8000 database (same as Empty – DB command). MM8KdcomSet – command-line batch procedure for repairing the MK8000 –...

  • Page 30: Installing The Mk8000 On The Main (Stand-Alone) Station

    4.1 on page 23). 4. Reboot the PC. 5. In the setup menu (Fig 3 on page 23), launch the MK8000 installation  Stand- Alone/Server Station. 6. Follow the instructions in the installation Wizard: as first step, confirm the desti- nation folder.
  • Page 31 MK8000 software, as well as the related Composer tools, is now installed. 10. Reboot the PC. At this point, you can notice the new MK8000 System Monitor icon in the Win- dows taskbar at the bottom right of the screen. Also, while starting up, status messages are displayed reporting the server task conditions (Fig 17).

  • Page 32: Installing The Mk8000 On The Fep (Distributed Systems)

    Installing the MK8000 on the FEP (Distributed Systems) Note: When you install the MK8000 on a FEP, you need to know the name of the PC where you want to install the server (Stand-Alone). See the procedure below for in- structions.
  • Page 33 To install MK8000 test tool on a client station, do the following: 1. Logon to client as Administrator. 2. Insert the DMS8000 Installation CD. 3. In the setup menu (Fig 3 on page 23), launch the MK8000 installation  Li- cense Station 4. Confirm the destination folder (C:\Program Files\DMS8000).

  • Page 34: Testing The Network Communication (Distributed Systems)

    Installing MK8000 Software Testing the network communication (Distributed Systems) After you have connected and activated the PAK, and rebooted the PC (as docu- mented in the DMS Connectivity Configuration Guide) you should verify that the main station (Stand-Alone) and FEPs are communicating correctly. You do this with the System Supervisor Browser that you access by right-clicking the System Monitor icon.

  • Page 35: Configuring The Mk8000

    The list in the Connectivity Guide serves as an overview of DMS product configuration in general, while the list provided below is a list of the actual steps in the MK8000 configuration process. The following abbreviations are used this table: DMS-CG –...
  • Page 36 Configuring the MK8000 CONFIGURING MK8000 The following steps outline what you need to do to configure MK8000:  Set up the Composer project Create a new project DMS-CG Define the general structure of the project tree, taking into account the goal of pre- senting a structure to the final user that is clear and familiar to him/her (Network –...

  • Page 37: Mk8000 Architecture In The Composer Project

    Configuring the MK8000 MK8000 architecture in the Composer project New MK8000 project in Composer A new MK8000 system must be defined in Composer. A new project can be cre- ated following the instructions given in the Composer Technical Manual (A6V10062401).
  • Page 38 Fig 23 Finding out the computer name Note: In the MK8000 system  Physical Configuration  Stand-Alone, the Station name (localhost) and IP address (127.0.0.1) fields are already set for this configu- ration (Fig 24). Do not change this setting.

  • Page 39: Control Units And Network Components

    MK8000 Communication drivers MK8000 network drivers On the MK8000 Stand-Alone and FEP stations, you need to add the drivers that provide the communication services for the OPC server. Several types of drivers are available, and should be selected according to the actual connections to be made with network devices and control units.
  • Page 40 (B), NS8210 NK8000 (C), NS8015 CNDL (D), NS8014 SI410 (E), and NS8011 BACnet (F). On the MK8000 FEP station you can also add serial drivers as described above and then connect them (drag & drop) to the Channel node of the Stand-Alone sta- tion (Fig 27).

  • Page 41: Connecting Networks To The Mk8000

    Configuring the MK8000 Connecting networks to the MK8000 Now you need to connect the control units and the network components with the network drivers in the MK8000 server. 5.5.1 What to drag to the drivers Cerloop Network – Drag the MK7022 to the Cerloop Driver.
  • Page 42 Configuring the MK8000 GW21  Lines  Line ‘n’ (for GW21)  Fig 30 Connecting GW21 line to the CDI-Net Driver Note: Only GW21 Lines 1 and 2 can be linked to the CDI-Net Driver. While line 1 is already defined for upstream, line 2 needs to be set for upstream link (‘Line Type: CMS’, see Fig 31).
  • Page 43 Connecting NK8225 to the NS8011 BACnet Driver Multiple hosts: NK822x can support the LAN/WAN connection to multiple hosts, both DMS8000 (MK8000/MM8000) . The network protocol can be CMSDL/IP (DMS8000) and/or BACnet/IP (DMS8000 ). Note that each DMS8000 host requires a separate Composer configuration that should match the one of the other hosts.
  • Page 44 Configuring the MK8000 NK822x - Serial link – Drag one of the NK822x serial lines to the NS8210 NK8000 Driver. Fig 34 Connecting NK822x serial line to the NS8012 CDI-Net Driver SI410 connection – Drag the SI410 unit to the SI410 Driver.
  • Page 45 Configuring the MK8000 SiPass subsystem – Drag the SiPass subsystem to the SiPass Driver. Fig 37 Connecting SiPass to the corresponding driver Video devices – Drag the Video device (e.g. SISTORE VDR) to the Video Driver. Fig 38 Connecting SISTORE to the corresponding driver Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc...

  • Page 46: Adjusting Network Settings

    A6V10062457). Serial connections tunnelled over IP networks. MK8000 serial connection to control units may be ported over IP network (LAN/WAN) by making use of serial-to-LAN adapters (on the control unit side) and appropriate software on the central location. The software must be able to emulate a virtual COM port that must be fully Windows compatible.

  • Page 47: Setting Vitality

    GW20 or GW21. It is mandatory when connecting a CS11 directly to the MK8000. Note: Setting the vitality timer is mandatory when connecting a CS11 directly to MK8000, while it needs to be ‘0’ when a CS11 is connected via MK7022 to the MK8000. 5.7.1...

  • Page 48: Setting Opc Group Names

    Bit-mask mode: A 4-byte value will map the possible states on 32 bits, with each bit corresponding to an elementary state. As shown in Fig 41, the ‘MK8000 OPC server node’ includes in the Node tab the option for setting one of the multi-state modes. For more information on OPC data formats, see the document 004971 MK8000 OPC Server Interface Specifications.

  • Page 49: Setting Up The Diagnostic Log

    The level of detail recorded (see table below for explanation of choices). Whether the file will be backed up or not at each MK8000 start-up. If yes, the existing log is backed up and a new empty log file is created at each start-up (in the same folder).

  • Page 50: Downloading Configuration To The Mk8000

    MK8000 server. Before downloading the configuration, you need to start the MK8000 on the server and FEP stations. You can start, stop and verify the status of the MK8000 server with the System Monitor icon in the bottom right corner of your screen.

  • Page 51: 5.11.1 Verifying The Mk8000 License

    The Composer tool can provide in any moment the required license parameters and check them against the values currently set. As shown in Fig 43, select the ‘MK8000’ node and then the ‘View License Data’ button on the ‘Node’ tab.

  • Page 52: Testing The Configuration

    OPC client. For a list of OPC Clients and other valuable OPC related information, go to www.opcfoundation.org on the Internet. There are three main elements to check. You want to determine that the MK8000:  Is running on the stations ...
  • Page 53 – Click OK.  The MK8000 server appears in the left pane (see Fig 45). Fig 45 Connecting to the MK8000 Server Checking that all subsystems are present, and adding them to the client...
  • Page 54 3. Verify that the child nodes of the top object are grey with value: Quiet (1000), Quality: BAD. (See Fig 47.) 4. Repeat steps 2 and 3 for each subsystem. Note: The MK8000 test client uses colours to indicate value. Each OPC group item should display in one of the following colours: –...
  • Page 55 Testing the Configuration Fig 47 Check Values while Disconnected from the Field Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007...
  • Page 56 Testing the Configuration Connecting the network subsystem, and verifying correct communication To connect the network subsystem to the field, and confirm that MK8000 commu- nicates correctly with the subsystems, do the following: 1. One by one, physically connect the network subsystem or gateway with the MK8000 OPC server.

  • Page 57: Tips For Integrating With An Opc Client

    Once you have completed the OPC Server configuration, the data is ready to be exported for use by the 3 party integration team. An application called Export Wizard was installed along with the MK8000 for gen- erating export files. The Export Wizard generates a CSV file (an MS Excel-compatible table) that can include the following fields: –...
  • Page 58 Tips for Integrating with an OPC client Fig 49 Select the fields to be included in the table 3. Click ‘Next’ to go to the Additional settings window. (See Fig 50.) Fig 50 Additional Settings window 4. Use the following checklist to specify your settings: ...

  • Page 59: Using The Test Client

    Tips for Integrating with an OPC client Using the test client You may want to use the MK8000 test client on the client stations for commission- ing and debugging purposes. You can choose to install the test client only during product installation.
  • Page 60 If necessary, adjust DCOM settings: instructions for the DCOM settings are given in the next section. Note: If there is a loss of communication between the MK8000 OPC Server and one of the client stations, it will not be reported by the MK8000 to the other clients. Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety &...

  • Page 61: Possible Difficulties In Integrating An Opc Client

    On a workgroup network, on the servers and clients an account with the same username/password combination must be created; – Check DCOM settings according to the next section. For more details, see the Integration tips section of the MK8000 Installation Con- figuration and Commissioning guide. Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety &...
  • Page 62 To ensure that the OPC server and clients will be able to communicate correctly, modify the following settings after MK8000 installation. To do this, in Windows XP computers, perform the following steps: 1) Log in as Administrator (necessary for modifying DCOM privileges).
  • Page 63 Tips for Integrating with an OPC client Fig 51 Selecting the computer DCOM configuration Note: – You have to be authorized to use dcomcnfg.exe (administrator) - ask your system administrator to set your DCOM if you are not; – Some changes in DCOM settings require rebooting the computer for changes to take an effect (for example, DCOM enable/disable).
  • Page 64 Tips for Integrating with an OPC client Fig 52 Default Properties tab  Default Protocols tab We recommend that you use Connection Oriented TCP-IP. You should have the preferred protocol at the TOP of the list in this tab. Set your Default Protocols tab to look like Fig 53 (note that some of the proto- cols below TCP-IP may be missing).
  • Page 65 Tips for Integrating with an OPC client  Default Security tab Note: When setting permissions for users, please note that ‘Administrator’ is the administrator of the local machine. To set permissions for users, do the following: – Select Edit Default… in the Access Permissions section of the COM security tab (Fig 54).
  • Page 66 OPC server as a service, you may need the SYSTEM account in- cluded as well. In workgroup configuration, the MK8000 ‘internal’ user (normally ‘DMS8000_PROC’) must also be authorized.
  • Page 67 Fig 56 Default Launch and Activation Permissions Specific MK8000 DCOM settings Select the MK8000 DCOM properties. To do this, in Windows XP computers, per- form the following steps: 1) In the Component Service window, right-click the node: Component Services  Computers  My Computer  DCOM Config ...
  • Page 68 Tips for Integrating with an OPC client Fig 57 Selecting the server component for detailed DCOM configuration General tab – MM8000Server Properties  We recommend leaving the Authentication level on ‘Default’. This means that the server will use this method of determining who will be allowed access that was set up on the Default Properties tab in the DCOM Config utility.
  • Page 69 Tips for Integrating with an OPC client  Location tab - MM8000Server Properties Make sure that the ‘Run application on this computer’ is the ONLY check box checked. The Location tab should look like Fig 59: Fig 59 MM8000Server Properties - Location tab ...
  • Page 70 Tips for Integrating with an OPC client  Endpoints tab - MM8000Server Properties We recommend leaving the Endpoints level to Default. This means that this server will use the protocols that were set up on the Default Properties tab in the DCOM Config utility.

  • Page 71: Dcom Settings On Opc Clients

    Tips for Integrating with an OPC client Fig 62 MM8000Server Properties - Identity tab On Windows XP systems, in case of difficulties related to the DCOM functions, you can get an advanced diagnostic log by activating the DCOMXPLogEnable.reg com- mand (see in C:\Program Files\DMS8000\Utilities\Reg). This command modifies a registry value that results in a detailed DCOM function trac- ing being enabled in the Windows application event list (start the ‘Event Viewer’...

  • Page 72: Integrating Clients That Don't Support Dcom

    Tips for Integrating with an OPC client Integrating clients that don’t support DCOM The MK8000 server uses DCOM (Distributed Component Object Model) to com- municate via network for distributed configurations. In the event that your OPC cli- ent does not have DCOM capability, this script can be installed on the client PC to create the illusion that the OPC server resides on the OPC client, and permits them to communicate effectively.
  • Page 73 Please note that OPC Transparency should not be deleted from the PC where the OPC server resides. To remove the OPC Transparency registry values, do the following: 1. Copy the ‘Delete Transparent OPC.reg’ file to the OPC client PC (MK8000 in- stallation dir>\Utilities\OPC Transparency). 2. Double-click the file to remove the registry file.

  • Page 74: Appendix A. Using The System Monitor

    Tips for Integrating with an OPC client Appendix A. Using the System Monitor The System Monitor is an application that is installed with the MK8000. As its name implies, it monitors the MK8000 system and reports the status of the server and FEPs.
  • Page 75 Tips for Integrating with an OPC client System Monitor right-click menu: Server is running, therefore the ‘Stop’ Fig 65 command is available Fig 66 DMS8000 information window (note that the version displayed in this pic- ture may not match the official product release) Advanced menu The Advanced menu includes –...
  • Page 76 System Monitor, or through the MK8000 program menu (StartPro- grams MK8000System Supervisor Browser). In the left pane (Fig 69-A), the MK8000 stations are listed. Selecting one of the sta- tions results in the corresponding processes showing in the right pane (Fig 69-B).
  • Page 77 In this case, try to stop and start the server again. If the problem persists, contact technical support. Fig 69 System Supervisor Browser Stations Server and FEP stations running the MK8000 Processes Processes running on the station selected in the left pane Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety &...

  • Page 78: Appendix B. Enabling & Disabling Mk8000 Auto-Start

    Appendix B. Enabling & disabling MK8000 auto-start During normal use of the MK8000, it is convenient to have the MK8000 server start automatically upon system start-up. During troubleshooting and system testing, however, it may be more convenient to disable auto start.
  • Page 80 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. A6V10062407_a_en MK8000 Technical Material Edition 06.2007 Section 2...

Table of Contents