Siemens MK8000 MP4.30 Installation/Configuration Manual
  1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Server
  5. MK8000 MP4.30
  6. Installation/configuration manual
Siemens MK8000 MP4.30 Installation/Configuration Manual

Siemens MK8000 MP4.30 Installation/Configuration Manual

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

Advertisement

Quick Links

Download this manual See also: Quick Reference Manual
MK8000 MP4.30
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 MP4.30

Summary of Contents for Siemens MK8000 MP4.30

  • Page 1 MK8000 MP4.30 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. © 2010 Copyright by Siemens Switzerland Ltd We reserve all rights in this document and in the subject thereof. By acceptance of the document the recipient acknowledges these rights and undertakes not to publish the document nor the subject thereof in full or in part, nor to make them available to any third party without our prior express written authorization, nor to use it for any purpose other than for which it was delivered to him.

  • Page 3: Table Of Contents

    About this Document ....................5 Safety Regulations..................7 Country-specific standards ...............7 Assembly, installation, commissioning and testing work ......7 Modifications to the system design and the products .......7 Data Privacy and Protection ..............7 Introduction .....................8 What has been changed in MP 4.30............9 2.1.1 Documentation changes and corrections in this edition .....9 Installation .....................10 Installation requirements.................10...
  • Page 4 Exporting data to a 3rd party OPC Client..........70 Using the test client.................72 Integrating into a network (Distributed configuration) ......72 Possible difficulties in integrating an OPC client........74 6.4.1 Exporting data to a 3 party OPC client ........74 6.4.2 Integrating the OPC server into a network .......74 6.4.3 DCOM settings on OPC clients ..........84 Integrating clients that do not support DCOM.........85...

  • Page 5: About This Document

     Training program information including the Siemens intranet link  A complete list of all available DMS8000 documents  Instructions for how to obtain a document via the Siemens intranet using the STEP Documentation Repository System  A map of relevant documents for each target audience group ...
  • Page 6 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.30_A6V10062407_a_en Fire Safety & Security Products...

  • Page 7: 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 8: Introduction

    Introduction Introduction This is a guide to the software installation, configuration and commissioning of the MK8000 OPC Server. From point-of-sale to project handover The following is an overview of the phases or steps that occur from the point-of- sale to project handover to the customer. Documentation that supports a given step is shown on the right-hand column (refer to the list of Reference Documents in DMS8000 MP4.30 Documentation Resource Information Guide, document no.

  • Page 9: What Has Been Changed In Mp 4.30

    If the customer purchased a maintenance contract, the DU begins performing routine maintenance and troubleshooting procedures. What has been changed in MP 4.30 This section illustrates the new features of MK8000 MP4.30 in comparison with previous MP4.20. Section, Page Improvements 3.1.1, p.10...

  • Page 10: Installation

    Installation Installation Installation requirements This chapter lists hardware and software requirements for installation of the MK8000 OPC Server. The list of requirements includes network related compo- nents required for distributed (client/server) configurations. MK8000 and MM8000 solutions MK8000 OPC Server can be installed both as a separate OPC server or integrated in the MM8000 management system.
  • Page 11 Installation  Microsoft SQL Server 2000 (local or available in the network) -- or -- Microsoft SLQ Server Desktop Engine (MSDE 2000) -- or -- Microsoft SQL 2005 + SP2 -- or -- Microsoft SQL Express 2005 SP2 is required for handling the internal databases. ...
  • Page 12 Installation Internet Information Services (IIS) is available but not installed in Windows. You can install IIS by selecting Control Panel  Add/Remove Programs  Add/Remove Windows components (follow the on-screen instructions to install, remove, or add components to IIS). For more information on IIS, see  http://www.microsoft.com/WindowsServer2003/iis/default.mspx http://www.iis.net/ Note: ISS should be installed before MM8000.
  • Page 13 Installation Reboot – Uninstall MSDE – Reboot – Delete the MSDE folder, typically C:\Program Files\Microsoft SQL Server – Install SiPass – Re-install MK8000 –  See also the installation checklist in section Error! Reference source not found. at p.Error! Bookmark not defined.. Windows Vista includes several new features.

  • Page 14: Secure Operation Requirements

    Installation virtualization works similarly and applies to registry keys under the HKEY_LOCAL_MACHINE\SOFTWARE subtree. This feature causes no problem to MM8000 operations as long as you do not use system folders, such as “C:\Windows” or “C:\Program Files” to store any project information. 3) Windows Vista does not officially support MSDE 2000.
  • Page 15 As stated in 1.4 at p.7, compliance with local regulations must be addressed. This can concern paper listings as well as tapes and memory support. For further information on general security issues regarding Siemens products, please refer to the internal document IT security in BT project execution.

  • Page 16: 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 Com- station (full-featured) poser and the configuration tools.
  • Page 17 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 18: Selecting The Type Of Windows Security

    Installation 3.2.2 Selecting the type of Windows security The MK8000 installation procedure needs to define a new ‘internal’ Windows user (DMS8000_PROC, default password = ‘Dixie#65A39!PWD’) and assign it to the administration user group. This is required for handling the internal inter-process communication.

  • Page 19: Installation Checklist

    Installation Installation checklist The following checklists tell you what you need for MK8000 installation, and the steps you go through to install it. ITEMS NEEDED FOR INSTALLATION The following list outlines information and items needed to install MK8000:  Administrator account name and password is required. ...

  • Page 20: Installation Procedures

    Installation read through the sections that follow. Installation Procedures MK8000 and MM8000 solutions The MK8000 can be an independent OPC server or run as a component of an MM8000 management system. This document discusses the installation procedure of the first of the two options, whereas the MM8000 ICC manual (doc.no.A6V10062413) should be referred to about the MM8000 product installa- tion.
  • Page 21 Installation Fig. 3 DMS8000 Installation Welcome Page Selecting MK8000 results in the following page being displayed (Fig. 4), which pre- sents the Installation Types (see 3.2 at p. 16). Fig. 4 MK8000 Station Selection page The Stand-Alone / Server type (Fig. 5) presents the most complete list of required applications or pre-requisites: MSDE 2000 (or SQL Express 2005+compatibility pack), SQLXML 3.0, .NET framework V1.1 and V2.0.

  • Page 22: Mk8000 Stand-Alone Station: Installing The Ms Software

    Installation Fig. 5 MK8000 Software Setup page The MK8000 Installation command, at the bottom of the page, becomes active only if a valid combination of pre-requisites has been installed (see 3.1.1 at p. 10). 3.4.2 MK8000 stand-alone station: installing the MS software 3.4.2.1 Installing the Microsoft .NET framework V1.1 MK8000 software requires the support of the Microsoft .NET V1.1 framework li- brary.
  • Page 23 Installation Fig. 7 Successful termination of .NET framework V1.1 setup 3.4.2.2 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 menu.
  • Page 24 Installation Fig. 10 Successful termination of .NET framework V2.0 setup Although not strictly required for MK8000 operations, the recommendation concern- ing the .NET framework update (see Fig. 10) should be followed to ensure software stability. Please refer to Microsoft support site at  http://www.microsoft.com/downloads and search for “.NET Framework”...
  • Page 25 Installation Microsoft .NET V2.0 framework library is a pre-requisite for SQL Express 2005 Installing SQL Express 2005 1. Launch the SQL Express 2005 installation from the setup page (Fig. 5). If necessary, Windows Installer 3.1 (Microsoft code KB893803) is automatically installed.
  • Page 26 Installation Fig. 14 System Configuration Check before installing SQL Express 2005 6. If no critical errors are present, you are allowed to press Enter to continue. 7. At this point, fill in the registration information (Fig. 15). Do not uncheck the option Hide Advanced Configuration Options. Fig.
  • Page 27 Installation Confirm the default option (Windows Authentication Mode) and click Next. Fig. 17 Selecting the SQL Express 2005 authentication mode. 10. The configuration window that follows (Fig. 18) configures SQL user options. In general, we recommend enabling both options (Enable User Instances and Add user to the Server Administration role) unless specific security issues apply (contact IT Manager).
  • Page 28 Installation Fig. 20 Ready to install SQL Express 2005 12. At this point, setup installs the software. This may take a few minutes. A setup progress window (Fig. 21) displays on the screen, and a summary log is finally available in the next window (Fig. 22). Click Summary Log to open and possibly save the log file.
  • Page 29 Installation Fig. 22 SQL Express 2005 setup summary log 13. Click Finish to close the setup procedure. You now need to add the Backward Compatibility Package. Installing Backward Compatibility Package 1. From the setup page (Fig. 5), launch the installation of SQL Express 2005 Backward Compatibility Package.
  • Page 30 Installation Fig. 25 Filling in the Backward Compatibility Package registration information 4. Next, the Feature Selection window (Fig. 26) shows the list of components. You may use the Disk Cost function to check the disk space available and the detailed requirements. Do not modify the default setting.
  • Page 31 Installation Fig. 28 Completing the Backward Compatibility Package setup 3.4.2.5 Installing the SQLXML 3.0 software An extension to the standard MS-SQL software is also required for handling XML files. This is a free package from Microsoft named SQL XML 3.0. It is recommended to install this software after MSDE 2000 or SQL Express 2005.
  • Page 32 Installation Fig. 30 Selecting the SQL XML Setup Type Building Technologies 048_DMS_MK8000_ICC_MP4.30_A6V10062407_a_en Fire Safety & Security Products 06.2010...

  • Page 33: Mk8000 Opc Server

    Installation 3.4.3 MK8000 OPC server While the installation process is relatively straightforward, there are a few items that should be noted. Setting up a distributed configuration When setting up a distributed configuration, ensure that the MK8000 Stand-Alone and FEP stations have been set up in the same workgroup or domain, and that you are able to log on to both of them with the same Administrator ID and password.
  • Page 34 Installation  FEP station  License station  For a discussion of installation types, see 3.2 at p. 16. Note that, on the installation menu pages, the installation button is not avail- able if any required software if missing (refer to Fig. 5 at p. 22). 4b.
  • Page 35 Installation Fig. 31 Selecting the MK8000 security option Fig. 32 Advanced Security settings Note: The internal user account can also be modified after the installation using the Engineering Tools (see 3.4.5.1 at p.42). 4d. External SQL server settings If no SQL server is available on the local PC and a Stand-Alone or Server type has been selected, the setup procedure cannot proceed and proposes three possible solutions (see Fig.
  • Page 36 Installation Fig. 33 SQL server options The external SQL server can be defined as specified in the following Fig. 34. Namely:  The SQL server Name, as required to identify the Server in the network (for details ask your network administrator). ...
  • Page 37 Installation Fig. 35 Selecting the Automatic Server Startup In the same window, you can set the dual server option and set specify the PC names of the physical machines supporting the Marathon EverRun FT environment. Note that the IP address is not valid. ...
  • Page 38 Installation Fig. 37 DMS8000 setup complete 3.4.3.2 Attaching & activating the hardware key At this point, on the main station, you need to connect and activate the hardware key for Composer and MK8000 and restart the PC.  See DMS8000 Network, Fire and Intrusion Connectivity Guide (document no.A6V10062425).
  • Page 39 Installation At this point, you can notice the new MK8000 System Monitor icon in the Windows taskbar at the bottom right of the screen. Also, while starting up, status messages are displayed reporting the server task conditions (Fig. 38). Fig. 38 MK8000 System Monitor icon 3.4.3.3 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...

  • Page 40: Mk8000 Installed Software

    Installation 3.4.3.5 Installing the MK8000 license station (dual-server with Marathon EverRun FT) In case of dual server solution based on Marathon EverRun FT (see 3.2.1.1 on page 16), each of the physical servers must be equipped with the license station software, which is capable of handling the dongle checks, which cannot be man- aged by the virtual server that runs the actual MK8000 software.

  • Page 41: Mk8000 Technical Utilities

    Installation  Composer User Manager – Allows adding and removing users enabled to access Composer (any project) and defining their capability. Composer us- ers must be defined in Windows.  Refer to the Composer Technical Manual, document no.A6V10062401.  Export wizard – allows for configuration export into *.CSV file. ...
  • Page 42 Installation 3.4.5.1 Program Tools In <installation folder>\Utilities\, the Tools subfolder contains additional useful software components. The list includes: Engineering Tools This utility allows changing various internal options and initialising databases. The list of functions includes:  SLQ Server  Configuring the computer name and name of SQL database for MK8000. ...
  • Page 43 Installation Set MSDE 2000 Password: SQL database security SetSQLServerPassword.bat – Set a (non-default) password for MSDE. This can prevent unauthorised access to the history databases from external sources. Due to important security concerns, it is strongly recommended to use this command set a new password for MSDE (this does not apply to SQL Express 2005).

  • Page 44: Nk8000 Firmware

    Installation and they are named according to a scheme that includes the creation date and time stamp: “NK8210Log_ddmmyy_hhmmss.txt”, e.g.: NK8210Log_021604_112449.txt The file format is CSV and includes the fields shown in the short extract: TYPE TIME BRANCH IP-ADDRESS/COMMAND VERSION STATUS EVENT 11:24:51 NULL...

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

    Installation 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 46: Configuring The Mk8000

    Configuring the MK8000 Configuring the MK8000 Configuration Checklist DMS Configuration Process Overview The following two checklists tell you what you need for MK8000 configuration, and the steps you go through to configure it. Make a mark in the corresponding check- box as you satisfy each item.
  • Page 47 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 presenting a structure to the final user that is clear and familiar to him/her (Net- work –...

  • Page 48: 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). MK8000 architecture When setting up your project in Composer, the first thing you should do is to repre- sent your MK8000 architecture.
  • Page 49 Configuring the MK8000 Fig. 43 Setting station parameters Computer name Be aware that, while the Description field can be freely defined to describe the station, the Name field must correspond to the network name of each PC: right click on My Computer on the Desktop, and then select Properties and Computer Name (Fig.

  • Page 50: Control Units And Network Components

    Configuring the MK8000 After MK8000 has been installed, any change in the computer name of the stations requires a special procedure. Refer to the Engineering Tools de- scribed in 3.4.5.1, p.42. Control units and network components At this point, in your Composer project, you can add the control units and network components.
  • Page 51 Configuring the MK8000 Adding the network drivers On the MK8000 Stand-Alone station, do the following: 1. Select MK8000 system  Physical Configuration  Stand-Alone station. The serial Channel is defined by default. 2. If necessary, add the Video Network Manager and/or the SiPass Driver by clicking the corresponding icons on the left (Fig.
  • Page 52 Configuring the MK8000 Fig. 48 Dragging the FEP driver to the Channel node Building Technologies 048_DMS_MK8000_ICC_MP4.30_A6V10062407_a_en Fire Safety & Security Products 06.2010...

  • Page 53: 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. 4.5.1 What to drag to the drivers Cerloop Network  Drag the MK7022 to the Cerloop Driver. Fig.
  • Page 54 Configuring the MK8000 Fig. 50 Connecting GW20 line to the CDI-Net Driver  GW21  Lines  Line ‘n’ (for GW21) Fig. 51 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.
  • Page 55 Configuring the MK8000 NK822x – NK8000 Network (NS8210 driver)  Drag the NK822x Ethernet line to the NS8210 NK8000 Driver. Fig. 53 Connecting NK822x Ethernet line to the NS8210 NK8000 Driver NK82X5 – BACnet Network (NS8011 driver)  Drag the NK82X5 main node (not the Ethernet line!) to the NS8011 BACnet- Driver.
  • Page 56 Configuring the MK8000 NK822x - Serial link  Drag one of the NK822x serial lines to the NS8210 NK8000 Driver. Fig. 55 Connecting NK822x serial line to the NS8012 CDI-Net Driver SI410 connection  Drag the SI410 unit to the SI410 Driver. Fig.
  • Page 57 Configuring the MK8000 FC330A/CC1115 connection  Drag the FC330A unit to the NS8015 Fire CNDL Driver. Fig. 57 Connecting FC330A unit to the corresponding CNDL driver SPC connection  Drag the SPC unit to the NS8013 SPC Driver. Fig. 58 Connecting SPC6000 unit to the corresponding SPC Driver SiPass subsystem ...

  • Page 58: Adjusting Network Settings

    Configuring the MK8000 Fig. 60 Connecting SISTORE to the corresponding driver Adjusting network settings Once you have connected the subsystems to the network drivers, in the node tab of the linked network subsystem, you can adjust some specific parameters that de- pend on the type of connection.

  • Page 59: Setting Vitality

    Configuring the MK8000 Note: For the detailed description please refer to the following documents:  DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide (document no. A6V10062425).  DMS8000 Access Control Connectivity Configuration Guide (document no. A6V10062451).  DMS8000 Video Connectivity Configuration Guide (document no. A6V10062457).

  • Page 60: Setting Opc Group Names And Access Limitations

    Configuring the MK8000 Fig. 61 Setting the vitality check in the CC11 directly connected to the MK8000 Setting OPC Group names and access limitations Set the OPC group name for each subsystem (control unit or device), as it should appear in the OPC client. This field is located in the MK8000 Extensor tab avail- able for each subsystem.
  • Page 61 Configuring the MK8000 As shown in Fig. 63, 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. Note: the field MK8000 and MM8000 selection can only be used in MM8000 sys- tem, which can switch the project type (refer to MM8000 ICC manual, document no.

  • Page 62: Setting Up The Diagnostic Log

    Configuring the MK8000 4.10 Setting up the diagnostic log The MK8000 will record all system activity in a log file, which can be accessed for troubleshooting and debugging purposes. If you want to modify any of the default settings for this log, you can do it now, or wait until you have an immediate need for it.

  • Page 63: Downloading Configuration To The Mk8000

    Configuring the MK8000 4.11 Downloading configuration to the MK8000 When the configuration process is complete, backup your project. Detailed instruc- tions for this can be found in the DMS Connectivity Configuration Guide (A6V10062425). After you have backed up the project you are ready to transfer the configuration to the MK8000 server.

  • Page 64: 4.11.1 Verifying The Mk8000 License

    Configuring the MK8000 4.11.1 Verifying the MK8000 license Each MK8000 license supports a limited number of data points (according to what was purchased). Specifically, the limitation applies to the total number of control units and devices configured in Composer. Note that the licensing mechanism has been changed in MP3.18. Previously, the limitation was related to the number of OPC items dynamically connected.

  • Page 65: Testing The Configuration

    Testing the Configuration Testing the Configuration Once the configuration has been downloaded to the MK8000, you need to perform the following tests with an OPC client. For a list of OPC Clients and other valuable OPC related information, go to www.opcfoundation.org on the Internet.
  • Page 66 Testing the Configuration Fig. 66 Client options  If you are connecting to the server from a remote client, then select the Re- mote Connection box and select the station where the server resides.  If your OPC Client supports a limited number of characters for objects, then check the Use short item name box (names will be limited to 50 charac- ters).
  • Page 67 Testing the Configuration Fig. 68 Server Address Space Dialog Window 2. Verify that all the subsystems are displayed in this list. Note: The subsystem names that are displayed here correspond with the OPC group names entered in the MK8000 tab of composer during the configuration process (see section 4.8, p.60).
  • Page 68 Testing the Configuration Note: The MK8000 test client uses colours to indicate value. Each OPC group item should display in one of the following colours: Grey: Quality BAD – Green: Quality GOOD, State Quiet – Yellow: Quality GOOD, State Fault –...
  • Page 69 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 70: Tips For Integrating With An Opc Client

    Tips for Integrating with an OPC client Tips for Integrating with an OPC client This section contains general tips to help facilitate the process of integration with an OPC client. Exporting data to a 3rd party 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.
  • Page 71 Tips for Integrating with an OPC client Fig. 71 Select the fields to be included in the table 3. Click Next to go to the Additional settings window. (See Fig. 72.) Fig. 72 Additional Settings window 4. Use the following checklist to specify your settings: ...

  • Page 72: 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 73 Tips for Integrating with an OPC client Here are some general guidelines:  For a distributed configuration, the OPC Server and Clients must be part of the same workgroup or domain.  On a workgroup network all users who will have access to the OPC server must belong to this workgroup.

  • Page 74: Possible Difficulties In Integrating An Opc Client

    Tips for Integrating with an OPC client Possible difficulties in integrating an OPC client 6.4.1 Exporting data to a 3 party OPC client This section addresses problems you may have when exporting data to a 3 party OPC client, and provides solutions to those problems. Exported data columns are not separated properly Different regions in the world use different symbols to represent the point where lists of data are separated.
  • Page 75 Tips for Integrating with 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.
  • Page 76 Tips for Integrating with an OPC client The instructions below refer to Windows XP. If you are using Windows 2000, please contact the Technical Support. Fig. 73 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;...
  • Page 77 Tips for Integrating with an OPC client Fig. 74 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. 75 (note that some of the proto- cols below TCP-IP may be missing).
  • Page 78 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.
  • Page 79 Tips for Integrating with an OPC client Fig. 77 Default Access permissions  Select Edit Default… in the Launch and Activation Permissions section of the COM security tab (Fig. 76).  Allow local and remote Launch and Activation (Fig. 78) to the authorised users.
  • Page 80 Tips for Integrating with an OPC client Fig. 78 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 ...
  • Page 81 Tips for Integrating with an OPC client Fig. 79 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 82 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. 81: Fig. 81 MM8000Server Properties - Location tab ...
  • Page 83 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 84: Dcom Settings On Opc Clients

    Tips for Integrating with an OPC client Fig. 84 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 command (see in C:\Program Files\DMS8000\Utilities\Reg). This command modifies a registry value that results in a detailed DCOM function tracing being enabled in the Windows application event list (start the ‘Event Viewer’...

  • Page 85: Integrating Clients That Do Not Support Dcom

    Tips for Integrating with an OPC client Integrating clients that do not 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 86 Tips for Integrating with an OPC client Removing OPC Transparency Support Once installed, the OPC Transparency values should not be deleted from the reg- istry by hand. Instead, use the utility provided to remove it. Please note that OPC Transparency should not be deleted from the PC where the OPC server resides.

  • Page 87: 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 88 Tips for Integrating with an OPC client  Close: remove the System Monitor icon from the system tray. Note that the icon application can be easily started again from the Windows Start menu (‘Start  Programs  DMS8000  DMS8000 System Monitor’). Fig.
  • Page 89 Tips for Integrating with an OPC client Fig. 89 Getting detailed status information Starting the MK8000 Server in Simulation mode In the Advanced menu, you can start the MK8000 server in simulation mode. This mode results in starting an additional application (Field Simulator), which allows generating messages as though they were coming from the fire and intrusion con- trol units in the field.
  • Page 90 Tips for Integrating with an OPC client Object property list List of properties of the currently selected object Simulation logging Logging of the simulated communication The events from the SiPass Access Control system and from the CCTV Network cannot be simulated with the standard Field Simulator. Launching and using the System Supervisor Browser The System Supervisor Browser can be launched either through the right click menu of the System Monitor, or through the MK8000 program menu...

  • Page 91: Enabling & Disabling Mk8000 Auto-Start

    Tips for Integrating with an OPC client 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. Changing the auto start settings To change the auto start settings, do the following: 1.
  • Page 92 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.2010 Section 2...

Table of Contents