Siemens MK8000 Quick Reference Manual

Download

Page 1

MK8000 MP4.10 OPC Server for subsystems

Installation Function & Configuration Commissioning Safety Regulations

Building Technologies

Fire Safety & Security Products

Page 2

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

About this Document ..............................................................................................5

Definitions of Terms..............................................................................................11

1 Safety Regulations................................................................................12

1.1 Country-specific standards .....................................................................12

1.2 Assembly, installation, commissioning and testing work........................12

1.3 Modifications to the system design and the products.............................12

2 Introduction ...........................................................................................13

2.1 What has been changed in MP 4.10.......................................................15

2.1.1 Documentation changes and corrections in this edition .........................15

3 Installation .............................................................................................16

3.1 Installation requirements.........................................................................16

3.1.1 MK8000 OPC Server System Requirements..........................................16

3.2 Installation types .....................................................................................18

3.2.1 Selecting the MK8000 configuration .......................................................18

3.2.1.1 Redundant server solution with Marathon virtual server.........................18

3.2.2 Selecting the type of Windows security..................................................20

3.2.3 Enabling the automatic start-up ..............................................................20

3.3 Installation checklist................................................................................21

4 Installing MK8000 Software .................................................................22

4.1 Welcome screen .....................................................................................23

4.2 Installing the MS-SQL Server software...................................................24

4.2.1 Installing the MSDE 2000 software.........................................................24

4.2.2 Installing the SQL Express 2005 and SQL 2005 Backward Compatibility24

4.3 Installing the SQLXML 3.0 software........................................................24

4.4 Installing the Microsoft .NET Framework V1.1 .......................................25

4.5 Installing the Microsoft .NET Framework V2.0 .......................................26

4.6 MK8000 OPC server...............................................................................28

4.6.1 MK8000 installed software......................................................................28

4.7 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

4.8 Testing the network communication (Distributed Systems)....................34

5 Configuring the MK8000.......................................................................35

5.1 Configuration Checklist...........................................................................35

5.2 MK8000 architecture in the Composer project .......................................37

5.3 Control units and network components...................................................39

5.4 MK8000 Communication drivers.............................................................39

5.5 Connecting networks to the MK8000......................................................41

5.5.1 What to drag to the drivers......................................................................41

5.6 Adjusting network settings ......................................................................46

5.7 Setting vitality..........................................................................................47

5.7.1 Connecting a CS11 (and FC700A) directly to the MK8000....................47

5.8 Setting OPC Group names .....................................................................48

5.9 Setting the Multi-state value data format................................................48

5.10 Setting up the diagnostic log...................................................................49

5.11 Downloading configuration to the MK8000 .............................................50

5.11.1 Verifying the MK8000 license .................................................................51

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 4

6 Testing the Configuration ....................................................................52

6.1 Checking Stations ...................................................................................52

6.2 Checking Internal Configuration..............................................................52

7 Tips for Integrating with an OPC client...............................................57

7.1 Exporting data to a 3rd party OPC Client................................................57

7.2 Using the test client.................................................................................59

7.3 Integrating into a network (Distributed configuration).............................59

7.4 Possible difficulties in integrating an OPC client.....................................61

7.4.1 Exporting data to a 3rd party OPC client..................................................61

7.4.2 Integrating the OPC server into a network..............................................61

7.4.3 DCOM settings on OPC clients...............................................................71

7.5 Integrating clients that don’t support DCOM...........................................72

Appendix A. Using the System Monitor...........................................................74

Appendix B. Enabling & disabling MK8000 auto-start...................................78

4 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 5

Safety Regulations

About this Document

Purpose of this document

This manual is a guide to the installation, configuration, and commissioning procedures for the MK8000 OPC Server. It is specifically for those individuals responsible for the commissioning of the MK8000 OPC Server.

Scope

This document applies to the MK8000 OPC Server for subsystems, MP 4.10.

Target audience

Individuals performing the operations described in this manual are expected to have prior expertise and training in the field of security, at least a moderate level of familiarity with the Siemens Building Technologies product line, and experience with the installation, configuration, and commissioning of security management systems.

This documentation and the instructions herein are intended for the following users:

Project managers The project manager is responsible for planning and managing a project at the customer site. He is

the link between the operator/customer and the DU. He is in charge of local project management, coordinates the schedules of all groups of people working on a project as well as resources. He also continuously obtains the technical information required for project realization.

Project engineers The Project engineers provide the parameterisation of products, devices, and systems in the DU for a

specific customer. They give the go-ahead for the commissioning of products, devices, and systems at the place of installation, and monitor the serviceability of it. They are also responsible for troubleshooting.

A Project engineer has had the training appropriate to his function and to the products, devices, and systems to be configured. He/she has also attended the appropriate technical training courses, and is familiar with the standard windows operating system environment.

Commissioning personnel Commissioning personnel are responsible for the configuration of the products, devices, or systems

for specific customers at the place of installation. They check serviceability, and officially clear the product, device, or system for use by the operator/customer. They are also responsible for troubleshooting.

Related training

Siemens Fire & Security Products offers a comprehensive training program. You can find information about training courses in the BT FS Intranet.

Operational and safety regulations

Before beginning work on the MK8000 OPC Server, you must have read and understood the related documents. In particular, chapter 1 in this manual, Safety Regulations, p.12.

Liability disclaimer for damage or injuries

Before products are delivered, they are tested to ensure they function correctly when used properly. Siemens disclaims all liability for damage or injuries caused by the incorrect application of the instructions, or the disregard of danger advisories. This disclaimer applies in particular to personal injuries or damage caused by:

 Improper and/or incorrect use.  Disregard of safety instructions in the documentation or on the product.  Poor maintenance or a lack of maintenance.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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.

We assume no liability for problems resulting from the use of this manual. The information contained in this document may be changed without prior notice. We reserve the right to publicize any such changes by issuing updated versions or new editions.

6 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 7

Safety Regulations

Reference documents

The most recently released documentation for customers can be found in the STEP Documentation Repository System released at SBT FS for end-users via the STEP Web Client interface at the following address:

https://intranet.sbt.siemens.com/dbcom/en/db_porta/client.asp

The following describes one way to search and find a document:

1. Click on the "STEP WEB Client" image:

2. Choose "04 Fire -3F" from the "Product Segment" box and select “Activate filter”.

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 (e.g. A6V10062415 or 007121) and press “Enter”.

Hint: For a specific version, specify the Market Package as *MPn.nn* in the

“Classification No.” field (e.g. *MP4.10*). Note: STEP provides no results when the number of found objects is equal to or greater than 200.

 To learn about other ways to locate a document, see DMS8000 Quick Reference Guidelines for Search and Finding DMS Documents in STEP (A6V10064704).

Product and Document Name Document no. Date Last up-

date Sales documents MM8000

023 Product Datasheet A6V10062415_a 06.2007 053 System Description A6V10062417_a 06.2007 039 Sales Presentation A6V10062423_a 06.2007 074 Sales Guide A6V10062427_a 06.2007 074 Tender Specifications A6V10062419_a 06.2007 074 Offer Template A6V10062429_a 06.2007

MP4.10 MP4.10 MP4.10 MP4.10 MP4.10 MP4.10

MK8000 023 Product Datasheet A6V10062405_a 06.2007 039 Sales Presentation 007121_a 03.2003 074 Sales Guide 004970_b 03.2003

MT8001

023 Product Datasheet 006952_e 09.2005 053 System Description 008605_a 09.2005 039 Sales Presentation 007346_b 03.2003 074 Sales Guide 007286_c 09.2005 074 Tender Specifications 007788_c 09.2005 023 Demo Material 008078_b 09.2005

NK8000

023 Product Datasheet NK8223 A6V10062431_a 06.2007 023 Product Datasheet NK8222 A6V10062433_a 06.2007

MP4.10

MP1.10 MP1.10

MP3.15 MP3.15 MP1.01 MP3.15 MP3.15 MP3.15

MP4.10 MP4.10

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 8

Safety Regulations

023 Product Datasheet NK8225 A6V10062445_a 06.2007 023 Product Datasheet NK8225 PICS A6V10062449_a 06.2007

023 Product Datasheet NE8000 A6V10062421_a 06.2007 039 Sales Presentation A6V10062435_a 06.2007 074 Sales Guide A6V10062439_a 06.2007 023 Demo Material 008077_b 02.2004

MP4.10 MP4.10

MP4.10 MP2.11

Technical documents MM8000

073 Release Notes MP4.10 A6V10062455_a 06.2007

MP4.10

073 Release Notes MP3.20-03 A6V10075048_a 06.2007 MP3.20-03 073 Release Notes MP3.20-02 A6V10067812_a 04.2007 MP3.20-02 073 Release Notes MP3.20-01 009421_b 12.2006 MP3.20-01 048 Autronica BSxx, ICC ad-on 008750_a 06.2006 048 LIST SCU 2000, ICC add-on 009248_a 06.2006 048 MAXSYS PC601, ICC add-on 008751_a 06.2006 048 CP100, ICC add-on 009848_a 06.2006 048 R Card M5 ICC add-on A6V10064742_a 06.2007 048 MODBUS ICC add-on A6V10067800_a 06.2006 048 CDDL-CDSF ICC add-on A6V10067787_a 06.2006 048 DLCS ICC add-on A6V10067792_a 06.2007 048 GEUTEBRUECK ICC add-on A6V10067796_a 06.2007 029 Operation A6V10062409_a 06.2007 022 Operation Quick Reference A6V10067779_a 06.2007 048 Installation, Configuration and

A6V10062413_a 06.2007

MP3.20 MP3.20 MP3.20 MP3.20

MP4.10

MP3.20 MP3.20

MP4.10 MP4.10 MP4.10 MP4.10 MP4.10

Commissioning (ICC) 022 Configuration Quick Reference A6V10075052_a 06.2007 019 Localisation - Engineering guide A6V10062459_a 06.2007

MP4.10 MP4.10

MK8000

048 Release Notes for MP4.10 A6V10062459_a 06.2007 073 Release Notes for MP3.20 009423_a 06.2006 048 Installation, Configuration and

A6V10062407_a 06.2007

MP4.10

MP3.20

MP4.10

Commissioning (ICC)

MK8000 Interface Specifications

019 MK8000 OPC Server 004971_h 06.2006 019 CS11 EP5 004974_d 02.2004 019 CS11 EP7 007546_b 02.2004 019 FC700A 008596_a 12.2004 019 CS1115 009843_a 06.2006 019 FC330A 009842_a 06.2006 019 CS440 004973_b 10.2003 019 CS4 007078_b 10.2003 019 CZ12 007079_b 10.2003 019 CZ10 007080_b 10.2003 019 STT11 007081_c 10.2003 019 DMS7000 007082_b 10.2003 019 GW-20/NK8210 007122_b 10.2003 019 GW-21 007124_b 10.2003

MP3.20 MP1.31 MP1.31 MP3.10 MP3.20 MP3.20 MP1.30 MP1.30 MP1.30 MP1.30 MP1.30 MP1.30 MP1.30 MP1.30

8 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 9

Safety Regulations

019 MK7022 007125_b 10.2003 019 CK11 EP5 007126_b 02.2004 019 CK11 EP7 007129_b 02.2004 019 SK11 007127_b 10.2003 019 NK8223 (CDI-Net) 007154_b 10.2003 019 CS6 Guarto 007545_b 02.2004 019 SI410 Sintony 008597_a 12.2004 019 CC60 007547_b 10.2003 019 NK822x 007879_b 02.2004 019 CF9000 007880_a 10.2003 019 SIMATRIX 007881_a 02.2004 019 Philips/Burle CCTV 008085_a 02.2004 019 SiPass 008607_a 03.2006 019 TELSCAN 009426_a 03.2006 019 SIMATRIX 009427_a 03.2006 019 SISTORE 009428_a 03.2006 019 Video Camera 009429_a 03.2006

MP1.30 MP1.31 MP1.31 MP1.30 MP1.30 MP1.31 MP3.10 MP1.30 MP1.31 MP1.30 MP1.31 MP1.31 MP3.20 MP3.20 MP3.20 MP3.20 MP3.20

MT8001

073 Release Notes for MP3.15 008604_a 09.2005 048 Operation 006611_e 09.2005 022 Operation Quick Reference 008088_a 09.2005 048 Installation, Configuration and

006647_e 09.2005

MP3.15 MP3.15 MP3.15 MP3.15

Commissioning (ICC) 019 Localisation - Engineering guide 008083_b 09.2005 016 History Analysis Installation 006962_b 03.2003

MP3.15 MP1.00

NK8000

073 Release Notes for MP4.10 A6V10062457_a 06.2007

MP4.10

073 Release Notes for MP3.20-01 009422_b 12.2006 MP3.20-01 048 Installation, Configuration and

A6V10062437_a 06.2007

MP4.10

Commissioning (ICC) 048 OPC Connectivity A6V10065253_a 06.2007 048 OPC Connectivity A6V10065253_a 06.2007

MP4.10 MP4.10

DMS8000 and Composer

023 Composer Datasheet A6V10062403_a 06.2007 054 Composer Technical Manual A6V10062401_a 06.2007 022 Composer Quick Reference A6V10067783_a 06.2007 048 Network and Subsystems Connec-

A6V10062425_a 06.2007

MP4.10 MP4.10 MP4.10 MP4.10

tivity Guide 048 Access Control Connectivity A6V10062451_a 06.2007 048 Video Connectivity A6V10062457_a 06.2007 048 OPC Connectivity A6V10065253_a 06.2007 048 Graphical Map Configuration A6V10062441_a 06.2007 022 Graphical Map Configuration

A6V10069550_a 06.2007

MP4.10 MP4.10 MP4.10 MP4.10 MP4.10

Quick Reference 016 Migration from DMS7000 A6V10062443_a 06.2007

MP4.10

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 10

Safety Regulations

MK8000 OPC Server

In addition to the documents available through the STEP documentation system, the OPC Foundation publishes a number of other documents that are necessary and/or useful for understanding the underlying principles used in the MK8000 OPC Server. These PDF documents can be downloaded from www.opcfoundation.org. Select “Downloads” on the main page of the site. See “Comments” below for navigation details. *

* Registration may be required.

Name Date Comments

OPC DA 2.05a (Data Access Interface Specifications) 2002-06-28 OPC site: “Specifications”

Also available in STEP #004971_h

OPC via DCOM with XP SP2 2006-03-30 OPC site: “White Papers”

Also available in STEP #004971_h

Standard symbols

Italics Result

„ “ Quotation, reproduced identically

 Cross reference (...) Brackets contain supplementary text, suggestions etc.

Modification index

Version Date Notes

A6V10062407_a_en 06.2007 Latest update for MK8000 MP 4.10 004972_h_en 06.2006 Latest update for MK8000 MP 3.20 004972_g_en 03.2006 Corresponds to version 3.18 of MK8000 OPC Server Software 004972_f_en 12.2004 Corresponds to version 3.10 of MK8000 OPC Server Software 004972_e_en 02.2004 Corresponds to version 1.31 of MK8000 OPC Server Software 004972_d_en 10.2003 Corresponds to version 1.30 of MK8000 OPC Server Software 004972_c_en 07.2003 Corresponds to version 1.20 of MK8000 OPC Server Software 004972_b_en 03.2003 Corresponds to version 1.10 of MK8000 OPC Server Software 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.

10 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 11

Definitions of Terms

End Processor) stations, providing extended communication

Safety Regulations

Control unit

Data Point

Distributed System

FEP

Internal user

Metafile

PAK

Plug-In

Subsystem

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 detectors. When a control panel is connected to the MK8000 server, it behaves as a translator between the detectors and the MK8000.

The MK8000 supports different types of control units in the disciplines of fire and intrusion. Each type of control unit has a different set of terms to describe the hierarchical levels of the organisational structure it uses. At the lowest level are the detectors, which are organised into groups (e.g. zones). These groups are organised into larger groups (e.g. sections), and so on.

The software representation of any item whose state can be changed. Changes of state can occur on subsystems, groups of subsystems, sections, zones, and detectors.

One of the MK8000 architectures. In this solution, a set of networked stations can provide the system functionalities in different locations. Distributed system includes:

– One server station (Stand-Alone) equipped with the OPC server software. – One or more FEP (Front-

capabilities.

Front End Processor. A dedicated PC that connects the main MK8000 station to the subsystems in the field.

In order to exchange data messages between tasks, MK8000 requires a Windows user account that is used as an identifier to get the necessary permissions from the Windows operating system. By default, this user is called “DMS8000_PROC”. This default setting can be changed if, during the MK8000 software setup, you select the “Restricted Security option and fill out the fields for the account name and password.

It is very important not to change the data associated to this user in the Windows user list. Modifying the information of the internal user will prevent the MK8000 tasks from working properly and require a complete re-installation.

A configuration file that is generated by the configuration tool of a corresponding control unit. It contains all the details of the local configuration (all the objects handled by a particular control unit). The information in this file can be read by and integrated into the MK8000 internal database, ensuring accuracy, and saving configuration time.

Product activation key: a 16-character code, associated to a hardware key (dongle) that enables MK8000 software to run and to perform.

A subsystem tool used during the configuration process in Composer. Plug-ins are automatically installed and registered in Composer along with the MK8000 product.

A control unit configured in the Composer environment.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 12

Safety Regulations

1 Safety Regulations

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

1.1 Country-specific standards

Siemens FSP-DMS products are developed and produced in compliance with the relevant international and European safety standards. This document provides warnings and recommendations specific to the MK8000 OPC Server. Any additional country-specific or local safety standards and/or regulations that apply concerning project planning, and installation and operation of the MK8000 OPC Server must also be taken into account.

1.2 Assembly, installation, commissioning and testing work

 Activate security-, fire- and third party systems or devices only in the presence

of the person responsible.

 Abide by the safety regulations of the connected sub-systems when working on

management stations. This especially applies when switching-off system components.

 Inform people before the testing of alarm devices - consider the possibility of

panic reactions.

 Inform the alarm and fault receiving stations connected to the system before

carrying out tests.

1.3 Modifications to the system design and the products

Modifications to a system or to individual products may cause faults or malfunctioning.

Please request written approval from Siemens Building Products, Fire and Safety Division, and any relevant authorities concerning intended system modifications and system extensions.

12 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 13

2 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-ofsale to project handover to the customer. Documentation that supports a given step is shown on the right-hand column; see Reference Documents at p.7.

Note: The steps relevant to this document are in black, while the other steps are shown in grey.

# Step Documents

Introduction

1 MM8000 Management Station is sold. 2 Customer chooses a 3rd party OPC Client and integration group. 3 MK8000 project is assigned to a project manager (PM)

Technical requirements defined during the sales process are given to the technical team that the PM oversees.

4 PM defines the exact needs of the customer.

Before planning commissioning, the project manager meets with the customer to understand any special needs he may have.

5 PM ensures that all “variables” necessary for installation and

commissioning are present.

“Variables” are items such as power supplies, network outlets, instal- lation areas, and connection wires to fire panels. These items should have been specified in the contract, and provided by the 3rd party suppliers or the customer. If there is a problem in this phase, the project plan is revised.

Note: The order of steps 6, 7, and 8 may vary.

6 DU provides information to the 3rd party integration group

about the MK8000 data model and interfaces

The 3rd party client integration will be working in parallel with the DU through the installation, configuration and commissioning phases, while they configure the client for integration with the MK8000. During this phase, the DU may need to provide information and guidance to the integration group with areas, such as the importance of certain “tags”.

[Sales Material]

[Contract]

[Interface specifications]

7 Hardware is installed at the client site

8 MK8000 project is configured in Composer

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Configuration, p 35 [DMS8000 connectivity configuration guide] [Composer Technical Manual]

Page 14

Introduction

9 Software is installed at the client site 10 Configuration is loaded onto the station(s), and tested 11 3rd party integration team connects OPC client to MK8000

Once the client is connected, the 3rd party integration team should be able to continue without further DU support

12 System is ‘acceptance tested’

This is typically done with both the DU and the 3rd party integration team working through any problems together.

13 Project is handed over to the customer

Once the system is running according to plan, the customer accepts the system and the project is closed.

14 Maintenance contract begins

If the customer purchased a maintenance contract, the DU begins performing routine maintenance and troubleshooting procedures.

Installation, p. 18 Commissioning, p. 52  Commissioning, p. 52

14 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 15

2.1 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

4.5, p. 26

3.1.1, p. 16

4.2.2, p. 24

3.2.1, p. 18 New configuration option: License Station

3.2.1.1, p. 18 New installation options for Marathon-based redundant solutions

4.1, p. 23 New welcome screen and installation menu

2.1.1 Documentation changes and corrections in this edition

Here is the list of corrections and modifications included in this edition of the document.

MK8000 software requirements: .NET framework 2.0 now required

MK8000 software requirements: SQL Express 2005 and SQL Backward Compatibility (optional installation in the place of MSDE)

Introduction

Section, Page Modifications

P. 5 About this Document

Updated Target Audience section and reference document table and intranet access (no mode EDMS, replaced by STEP). Added Acknowledgements section

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 16

Installation

3 Installation

3.1 Installation requirements

This chapter lists hardware and software requirements for installation of the MK8000 OPC Server. The list of requirements includes network related components required for distributed (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).

3.1.1 MK8000 OPC Server System Requirements

Hardware Requirements Pentium IV 2.4 GHz or faster

Operating System Microsoft Windows 2000 Professional

Microsoft Windows XP Professional SP2 (see note 1 below) Microsoft Windows 2003 Server Application Software (Stand-Alone station only) SQL Express 2005

SQL Backward Compatibility

SQL XML 3.0 SP3

Microsoft .NET Framework 1.1 SP3a

Microsoft .NET Framework 2.0

SiPass Integrated 2.3

Memory RAM 512 MB or better Hard disk space 500 MB free CD-ROM or DVD COM Port 1 (2-3 optional) LPT Port 1 USB Port 1 LAN Connections 10/100 MB Keyboard and pointing device Standard keyboard; mouse or trackball SW protection Key provided by SBT USB or parallel

Microsoft Windows 2000 Server

MSDE 2000 Microsoft SQL Server Desktop Engine

Microsoft SQL Server 2005 Express Edition (New in MP4.10)

(New in MP4.10)

(if access control is used)

SP4

SP3a (see note 2 below) Supplied in the DMS8000 CD, free license (See note 3 below) Supplied in the DMS8000 CD, free license

(See note 3 below) Supplied in the DMS8000 CD, free license

Supplied in the DMS8000 CD, free license

Supplied in the DMS8000 CD, free license SP3a Supplied in the DMS8000 CD, free license Build 21 or later (see note 4 below)

OPC compatibility

The MK8000 is compatible with OPC data access version 2.0. Note: MK8000 is not compatible with OPC data access version 1.0.

Note 1

16 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Windows XP SP2 includes firewall software that should be disabled or re-configured for MK8000 software to work properly in the following network configurations:

– A) Distributed architectures with Client and/or FEP stations. – B) Architectures including NK8000 or Serial/IP network devices.

Page 17

Note 2

Installation

– C) Architecture including SiPass and CCTV units in network.

Local configurations do not require any change to the Windows firewall setting. If the PC does not have access to the Internet or is somehow protected, the Win- dows firewall can be disabled with the following commands:

– Start  Settings  Control Panel  Windows Firewall. – In the form that appears (in the General tab), set the firewall to Off.

Alternatively, the Windows firewall can be configured in order to allow MK8000 to operate over the network. 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 procedure. The script must be used on any type of MK8000 stations (Stand-Alone and FEP).  See also the technical paper: ‘Using OPC via DCOM with Microsoft Windows XP Service Pack 2’ available in the download page at www.opcfoundation.org.

The Microsoft SQL Server 2000 Data Engine (MSDE 2000) software should typically be installed before MK8000 on the Stand-Alone station. MSDE 2000 is distributed free of charge and available on the DMS8000 installation CD.

The MSDE 2000 software is not needed if:

– The full-featured SQL Server 2000 SP3 (V8.00.760) is already installed on the same

machine.

– SiPass V2.3 is installed on the same PC and therefore its own copy of MSDE 2000

is also installed Note that the SiPass setup does not accept as valid the MSDE copy installed by MK8000.

MSDE is distributed at no charge by Microsoft and can also be downloaded at:  http://www.microsoft.com/sql/msde/downloads/download.asp For more information on MSDE, see:  http://www.microsoft.com/sql/msde/default.asp

Notes:

– In MK8000 MP3.18, no external SQL Server available in the network can be used

for the MK8000 database management functions. A local SQL server is always required.

– For security reason, after installing MSDE, the SQL user account should be custom-

ised using the ‘Special_UT’ utility tool (see pag.29).

Note 3

The Microsoft SQL Express 2005 and SQL Backward Compatibility softwares should typically be installed in the place of the MSDE. They are distributed free of charge and available on the DMS8000 installation CD.

Note 4

SiPass software should be installed and configured before MK8000.

If you have installed MK8000 MP3.20 before SiPass, then proceed as follows:

– Uninstall MK8000 and reboot – If MSDE is installed, uninstall it and reboot – Delete the MSDE folder, typically C:\Program Files\Microsoft SQL Server – Install SiPass – Install MK8000

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 18

Installation

3.2 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 station (full-featured)

FEP station (Front-End Processor providing communication services)

Client application – Install only the MK8000 testing client application. License station

(New in MP4.10)

During the MK8000 setup procedure, you need to select the installation type.

Install all MK8000 software components as well as Composer and the configuration tools. Select this option when you need:

– A single station with configuration and test tools; – A server station, with communication capabilities as well as

configuration and test tools for a Distributed System.

Install MK8000 communication layer only. A networked StandAlone station will be required to configure and operate. Select this option when you need:

– A Front-End Processor providing, in a Distributed System,

extended serial communication services to a Stand-Alone station (type 1). Note: A FEP station can support up to 16 serial ports.

Install the software required to handle the license key and the associated PAK code. This installation type is only required on the physical PCs supporting a redundant virtual server based on Marathon software.

3.2.1.1 Redundant server solution with Marathon virtual server

In DMS8000 systems, the Marathon EverRun FT (Fault Tolerant) software can be used in order to satisfy fault-tolerant requirements.

Marathon EverRun FT is a software application that can provide a Virtual server based on two identical PC machines connected over a hi-speed, dual local network. MM8000 can be installed on the virtual machine, which appears in all respects as a fully standard Windows system. The Marathon software is able to support an uninterrupted service even in case one of the two physical devices (or part of it) fails.

The virtual machine creates a perfect environment for DMS8000 software to run with only one exception, concerning the license key, which requires to be installed on a physical port and handled by the physical machine.

In fact, two identical hardware keys have to be installed on the same port of the two physical machines. The figures below show the architecture.

18 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

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.

Fig 2 Virtual server and Physical servers

For more information about Marathon solutions, refer to the following web site:

http://www.marathontechnologies.com/Continuous_Avail.html

Also, an online demo can be found at the following web address:

http://www.marathontechnologies.com/demo.html

In general, it is recommended that anyone installing, configuring, or administering a Marathon FT virtual Server environment running MM8000 attend a Marathon authorized training course.

 Please contact support for more information about technical details and purchase options.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 20

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.

Note that the ‘DMS8000_PROC’ user must be defined (and maintained) on all the PCs involved in the OPC communication, both server and client(s). Note: Do not remove this user.

During the installation, the MK8000 user can be defined in two different ways:

– Standard security: the internal user is automatically created with the name

‘DMS8000_PROC’.

– Restricted security: the internal username and password can be specified as

desired. You can specify a new user account or an existing one.

During the installation procedure of MK8000 software, you are asked to specify whether the user security is handled in standard or restricted mode.

In both cases, the internal user information can be changed later using the ‘Special_UT’ utility application (see page 29).

3.2.3 Enabling the automatic start-up

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 troubleshooting, it is usually best to enable auto-start. If you need to change this setting for any reason, please refer to Appendix B, "Enabling & disabling MK8000 auto-start”, p.78.

20 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 21

3.3 Installation checklist

The following two checklists tell you what you need for MK8000 installation, and the steps you go through to install it. Make a mark in the corresponding checkbox as you satisfy each item.

ITEMS NEEDED FOR INSTALLATION

The following list outlines information and items needed to install MK8000:

 Administrator logon ID and password  All networked PCs configured into the same workgroup or domain  Station names and IP address of all PCs  Hardware key (Dongle)  PAK (Product Activation Key) license codes for MK8000 and Composer  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:  1. Log on as Administrator.

2. On the main (Stand-Alone) station, install the required application software:



- MSDE 2000 software See p. 24 (after installing MSDE, reboot and check that SQL Server is running) Or



SQL Express 2005 and SQL 2005 Backward Compatibility software.... See p. 24



- SQL XML 3.0 software See p. 24



- Microsoft .NET Framework 1.1 software See p. 25



- Microsoft .NET Framework 2.0 software See p. 26

 3. Install MK8000 software on the Stand-Alone station See p. 30  4. Connect and activate the hardware key See DMS-CG  5. Install MK8000 software on the FEP and Client See p. 32  6. Test the connections of the OPC server See p. 32

Expert users may simply follow the checklist above and possibly refer to the detailed sections indicated for each item. Instead, new users are recommended to read through the sections that follow.

Installation

DMS-CG – DMS Configuration Guide (EDMS no. – 007083)

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 22

Installing MK8000 Software

4 Installing MK8000 Software

MK8000 and MM8000 solutions

The MK8000 OPC server MP4.10 can be used both as an independent OPC server (as in previous versions) or run as a component of a larger 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 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. The same Stand-Alone software has to be installed on the main station of a distrib-

uted system, which can also include more stations, equipped with either MK8000 communication FEP (Front End Processor) software or OPC Client applications.

In the Stand-Alone station, the MK8000 requires some additional software to be already installed (pre-requisite); namely: MSDE 2000 (or SQL Express 2005 and SQL 2005 Backward Compatibility), SQLXML 3.0, NET framework V1.1.and NET framework V2.0. This software is provided free of charge on the DMS8000 CD.

In order to run and perform, the MK8000 software requires a hardware key (dongle) and a related Product Activation Key (PAK), i.e. a 16-character code.

Distributed systems may include a redundant solution (see 3.2.1.1).

22 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 23

4.1 Welcome screen

The DMS8000 MP4.10 CD provides a welcome page that guides you in the installation process. The page appears automatically when you insert the CD. In very special cases, if the ‘Autorun’ option is disabled on your PC, you need to execute the Autorun.exe file manually in the CD main folder.

As shown in Fig 3 below, the welcome page presents a menu including the following commands:

– 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 Microsoft system software described in the next paragraphs.

– Install Composer and subsystem tools – Install Support Tools (tools for: NK8000, SiPass, Sintony) – Browse the Product Documentation

Note: this option will also include the commands to open DMS8000 MP4.10 Release Notes, browse the Documentation files – PDF format -, and install the Acrobat Reader – PDF reader

– Show the Contact information. – Close the setup menu (Exit)

Installing MK8000 Software

Fig 3 MK8000 MP4.10 welcome page

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 24

Installing MK8000 Software

4.2 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.

Fig 4 Checking the MS-SQL server

If an earlier version of SQL Server or MSDE is installed, proceed as follows:

– Uninstall the SQL Server or MSDE – Reboot – Delete the SQL folder, typically C:\Program Files\Microsoft SQL Server – Install the new MSDE software

The installation command is straightforward, just select the ‘Install MSDE’ button in the ‘Pre-requisites’ menu and let the installation procedure run.

Then, reboot the PC. At this point, the MS-SQL icon (see Fig 4) appears in the toolbar at the bottom right of the screen.

Due to important security concerns, it is strongly recommended to customise the SQL default user information using the ‘Special_UT’ utility application (see page 29).

4.2.2 Installing the SQL Express 2005 and SQL 2005 Backward Compatibility

Alternatively, if you don’t want to install the MSDE 2000 package, you may install the SQL Express 2005 and SQL 2005 Backward Compatibility packages, which may be compatible with other new software. All packages are provided in the DMS8000 CD.

4.3 Installing the SQLXML 3.0 software

An extension to the standard MS-SQL software is also required for handling XML files. This is also a free package from Microsoft named SQL XML 3.0.

It is recommended to install this software after MSDE or SQL Express 2005 and SQL 2005 Backward Compatibility.

In the ‘Pre-requisites’ menu, select the ‘Install SQLXML’ options and follow the installation Wizard (Fig 5).

24 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 25

Installing MK8000 Software

Fig 5 Starting the SQL XML Installation Wizard

You have to accept the terms in the license agreement, then enter your name and company, and finally confirm the installation folder. After that, in the ‘Setup Type’ step, press the ‘Install Now’ button (Fig 6) and wait for the setup procedure to complete.

Fig 6 Selecting the SQL XML Setup Type

4.4 Installing the Microsoft .NET Framework V1.1

MK8000 software requires the support of the Microsoft .NET V1.1 framework library. As with other Microsoft libraries, this package is distributed free of charge and can be easily installed selecting the corresponding option in the ‘Prerequisites’ menu.

In the installation procedure, you only have to agree on the terms of the license agreement (Fig 7), press ‘Install’, and then wait for the software setup to complete (Fig 8).

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 26

Installing MK8000 Software

Fig 7 Accepting the .NET Framework V1.1 License Agreement

Fig 8 Successful termination of .NET framework V1.1 setup

4.5 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 easily installed selecting the corresponding option in the ‘Pre-requisites’ menu.

During the setup procedure, follow the installation wizard (Fig 9), confirm you accept the terms of the license agreement (Fig 10), and wait for the procedure to complete (Fig 11).

Fig 9 Starting the .NET framework V2.0 setup wizard

26 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 27

Installing MK8000 Software

Fig 10 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  http://www.microsoft.com/downloads and search for “.NET Framework” in the “Windows Security and Updates” section.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 28

Installing MK8000 Software

4.6 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.

Installing the test client for debugging purposes

When commissioning or debugging, you may need to install the test client on the client stations. 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.

Start menu

The MK8000 setup adds a new folder in the Windows Start menu, providing the appropriate commands to control the MK8000 OPC server and tools. The complete set of commands is configured for the Windows user who installs the MK8000 software, whereas all other Windows users get a reduced menu, including basic set of commands only.

4.6.1 MK8000 installed software

Commands in the Windows Start menu

The MK8000 Installation disk will install the following applications:

 In the main Start  Programs  DMS8000 menu:

– Composer – configuration tool for configuring the OPC server. – System monitor – launches the system monitor icon in your task bar. – PAK manager – activates the hardware key with the software license code. – MK8000 server (SBT.MK8000 OPC server), which can be started and

stopped using the corresponding commands Start Server and Stop Server (this command is available only to the installation user).

– System Supervisor Browser – monitors the MK8000 connection (this

command is available only to the installation user).

 In the Start  Programs  MK8000  Tools submenu:

– Composer Plug-in Installer – shows which plug-ins are currently loaded

and available in Composer and allows for installing new ones (this command is available only to the installation user).

– Export wizard – allows for configuration export into *.CSV file. – Inspector – logs OPC messages and activity for troubleshooting. – MK8000 test client – tests the server configuration and connection with the

subsystems.

28 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 29

Installing MK8000 Software

Technical utilities

 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

current user association or for creating a new association to an existing Windows administrator (same as ‘Special_UT’; refer to section 3.2.2 above). Launch the MM8KdcomSet command in DOS mode with the ‘/h’ parameter to get help on the command syntax.

– Special_UT.exe – permits modification of the following accounts:

– SQL Server user: specify username and password for customising the

default SQL account (refer to the note on page 24).

– MK8000 internal user: specify username and password for repairing the

association to the Windows user specified during setup or for creating a new association to an existing Windows administrator (refer to section

3.2.2 above).

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 30

Installing MK8000 Software

4.7 Installing the MK8000 on the main (Stand-Alone) station

To install MK8000 on a Stand-Alone station, do the following:

1. Logon to computer as Administrator (for details ask your network administrator).

2. Insert the DMS8000 Installation CD.

3. In the setup menu, launch the installation or the required applications (see sec-

tion 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 destination folder.

Fig 12 Selecting the destination folder.

7. At this point, in relation to the MK8000 internal user definition (refer to section

3.2.2 above), select the security mode (Fig 13). Note: In case of doubts, select the Standard mode.

Fig 13 Selecting the user security setting

30 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 31

Installing MK8000 Software

The Restricted option requires that you specify the MK8000 internal user information (Fig 14). You can also simply confirm the default data.

Fig 14 Defining the MK8000 user account information

8. Next, you are prompted to enable (recommended) or disable the automatic start

(Fig 15) of the MK8000 server task at start-up (refer to 3.2.3 above).

Fig 15 Enabling automatic startup

9. Finally, the actual software installation starts.

During the procedure, you are asked to remove any USB key (dongle) you may have inserted (Fig 16). This is required by the installation of the key support software.

Fig 16 Request to remove the USB key

 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 Windows taskbar at the bottom right of the screen. Also, while starting up, status messages are displayed reporting the server task conditions (Fig 17).

Fig 17 MK8000 System Monitor icon

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 32

Installing MK8000 Software

4.7.1 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 instructions.

Determining the name of a PC To find out the name of a PC, do the following:

1. Right-click My Computer and select properties.

 The properties window appears.

2. Select the Properties button from the Network ID tab of the Properties window.

 The computer name appears.

Installing MK8000 on a FEP

To install MK8000 on a FEP station, do the following:

1. Logon to FEP as Administrator.

2. Insert the DMS8000 Installation CD.

3. In the setup menu (Fig 3 on page 23), launch the MK8000 installation  FEP

Station

4. Confirm the destination folder (C:\Program Files\DMS8000).

5. At this point, in relation to the MK8000 internal user definition (refer to section

3.2.2 above), select the security mode, Standard or Restricted. In case of restricted mode, set the very same username and password as you did for the Stand-Alone/Server station.

6. Insert the name of the PC where the Stand-Alone MK8000 was installed.

7. Choose the automatic start option.

8. Repeat the steps above for each of the FEP PCs.

At this point you need to connect and activate the hardware key on the Stand-Alone station. See the DMS8000 Network, Fire, and Intrusion Connectivity Configura-

tion Guide (doc. no.A6V10062425).

4.7.2 Installing the MK8000 on the client (test for Distributed Systems)

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  Test

Client Station

4. Confirm the destination folder (C:\Program Files\DMS8000).

5. Repeat the steps above for each of the Client PCs.

 The functions available in the test client software are presented in section 6 on

page 52.

4.7.3 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 18), each of the physical servers must be equipped with the “license station”

32 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 33

Installing MK8000 Software

software, which is capable of handling the dongle checks, which cannot be managed by the virtual server that runs the actual MK8000 software.

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).

5. Repeat the steps above for each of the Client PCs.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 34

Installing MK8000 Software

4.8 Testing the network communication (Distributed Systems)

After you have connected and activated the PAK, and rebooted the PC (as documented 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.

 For more information about using the System Monitor and the System Supervi-

sor Browser, see Appendix A, “Using the System Monitor”, p.74.

Testing Stand-Alone-to-FEP communication

1. Log on to the Stand-Alone and FEPs with the same user name and password. Note: Step 1 is required if the PCs are the same workgroup. For FEPs in the

same domain, it is not necessary that the user name is the same.

2. If the server has not started automatically (the System Monitor icon shows a flashing yellow dot, see Fig 18), right-click the icon and select ‘Start Server’.

3. Launch the System Supervisor Browser (right-click the System Monitor icon and select ‘System Supervisor Browser’).

Fig 18 System Monitor right-click menu

4. Check that the System Supervisor Browser on the Stand-Alone station (the first in the station list on the left) displays a green icon corresponding to each server task (Fig 19).

Fig 19 System Supervisor Browser

5. Check that all of the FEP stations are listed.

6. Select each FEP and verify that the right pane of each shows all green icons.

34 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 35

5 Configuring the MK8000

5.1 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 checkbox as you satisfy each item. The configuration checklist is a general guide to the larger configuration process. The order in which you perform the tasks in the checklist may vary depending on your personal preference. This is not an absolute guide, but rather lends context to the tasks discussed in this manual.

Note: A similar configuration list is provided in the DMS8000 connectivity configuration guide. While the two lists are similar, they are not identical, as each product has specific characteristics that impact this process. 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 – DMS8000 connectivity Configuration Guides:

 Network and Subsystem Connectivity (document no. A6V10062425)  Video Connectivity (document no. A6V10062457)  SiPass Connectivity (document no. A6V10062451).

– DMS – Danger Management System

– SPECS – Configuration specifications (agreed upon with the customer).

– N/A – Not Applicable – this step, while included in the list of configuration steps

for DMS products (for example, in the connectivity guide) is not necessary for this product.

–

ITEMS NEEDED FOR CONFIGURATION



Administrator logon id and password



Networked OPC Server (Stand-Alone station) and FEPs with software installed



Composer installed on the server machine



Station names and IP addresses of OPC Server (Stand-Alone station) and FEP PCs

Configuring the MK8000

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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 – Subsystems) DMS-CG

Create the MK8000 project and system architecture p. 37

Configure the communication network DMS-CG

Add and configure the subsystems, following the planned structure in the SPECS DMS-CG

Link the subsystems to the communication network DMS-CG

Add the required Communication Drivers p. 39

Connect the MK8000 with the network and FEP stations p. 41

Adjust network settings (baud rate, ports, etc) p. 46

Set vitality (mandatory if connecting CS11 without MK7022) p. 47

Set OPC group names (subsystems) p. 48

Set up the Multi-state value data format p. 48

Set up the diagnostic log. p. 49

Transfer the Configuration to the MK8000. p. 50

Test the configuration p. 52

Backup your Project DMS-CG

Generate an OPC configuration export file p. 57

Set the MK8000 server to automatically start, if necessary p. 78

36 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 37

5.2 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 created 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 represent your MK8000 architecture.

Note that, unlike previous MK8000 software releases, any new project includes the basic internal system structure, which will already be set up for you (Fig 20).

Configuring the MK8000

Fig 20 Internal MK8000 structure in a new project

You should then add the FEP stations to the project; do the following:

1. Select ‘Project  MK8000 System  MK8000  Physical Configuration’ and

click the Station Icon on the left (Fig 21).

2. Choose the type of station to add: FEP.

Fig 21 Inserting a FEP station

3. Select the new station and then the Node tab on the right area of the screen

(Fig 22) and enter the station parameters: Description, Name, and IP address.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 38

Configuring the MK8000

Fig 22 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 23).

Note that, in case the ‘Full computer name’ includes more levels separated by dots, you should consider only the first of them, e.g. ‘PCar4.it001’ becomes ‘PCar4’ for the MK8000 ‘Station name’.

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 configuration (Fig 24). Do not change this setting.

Fig 24 Setting station name and address - Stand-Alone

38 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 39

5.3 Control units and network components

At this point, in your Composer project, you can add the control units and network components.

This part is not discussed in this manual. Please refer to the following documents:

– Network and Subsystems Connectivity Guide (A6V10062425). – SiPass Connectivity Guide (A6V10062451). – Video Connectivity Guide (A6V10062457).

5.4 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.

The drivers are organised in groups (channel or manager); the list includes:

 Serial channel (Channel), including:

– NS8010 Cerloop (ISO1745) Driver

used for connections to MK7022, CS11 (via CK11), FC700A (via FG700A).

– NS8011 BACnet Driver

used for connections to NK8225 devices.

– NS8012 CDI-Net Driver

used for connections to GWxx gateways.

– NS8210 NK8000 Driver

used for connections to NK8222, NK8223, and NK8225 devices.

– NS8014 SI410 Driver

used for connections to Sintony control units.

– NS8015 Fire CNDL Driver

used for connections to FC330A/CC1115 control units.

 Video Network Manager, including:

– TELSCAN Video Driver

used for connections to TELSCAN video web servers.

– SISTORE Video Driver

used for connections to SISTORE Video Digital Recorders.

 SiPass Driver

used for connecting to the SiPass Access Control application.

Note: for each station, you only need to include once each driver that is used, regardless of the actual number of physical connections. Also, it is better not to add drivers which are not used and would only make the project larger.

Configuring the MK8000

Adding the network drivers

On the MK8000 Stand-Alone station, do the following:

1. Select ‘…MK8000  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 click-

ing the corresponding icons on the left (Fig 25).

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 40

Configuring the MK8000

Fig 25 Selecting Video Network Manager (A), the SiPass Driver (B) and the OP

Driver (C, not available in MK8000)

3. Select the serial Channel node (by default ‘Channel #1’)

4. Add the required drivers by clicking the corresponding icon on the left (Fig 26).

Fig 26 Adding serial drivers: NS8010 Cerloop/ISO1745 (A), NS8012 CDI-Net

(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 station (Fig 27).

Fig 27 Dragging the FEP driver to the Channel node

40 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 41

5.5 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.

Configuring the MK8000

Fig 28 Connecting the MK7022 to the Cerloop Driver

CS11 and FC700A fire systems can also be connected to the NS8010 Driver. In these cases, the CK11 and FG700A interfaces should be dragged to the driver, respectively. See 5.7.1 below.

CDI-Net Network

– Drag the appropriate CMS or upstream line to the CDI-Net Driver.

The CMS or upstream lines are located in the following areas:

 GW20  CMSPad  line ‘n’ (for GW20)

Fig 29 Connecting GW20 line to the CDI-Net Driver

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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).

Fig 31 Defining GW21 line 2 type as ‘CMS’

42 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 43

Configuring the MK8000

NK822x – NK8000 Network (NS8210 driver)

– Drag the NK822x Ethernet line to the NS8210 NK8000 Driver.

Fig 32 Connecting NK822x Ethernet line to the NS8210 NK8000 Driver

NK8225 – BACnet Network (NS8011 driver)

– Drag the NK8225 main node (not the Ethernet line!) to the NS8011 BACnet-

Driver.

Fig 33 Connecting NK8225 to the NS8011 BACnet Driver

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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. Note: The NK822x units can be downloaded by only one of the DMS8000 hosts.  See the DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide (document no. A6V10062425) for more information on network architectures.

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.

Fig 35 Connecting SI410 Sintony to the corresponding driver

Note: SI410 network connections, supported via protocol tunnelling over IP LAN, will also be configured with the same type of link. In the COM port setting (see 5.6 below), you will then select the virtual port emulated in software.  See the DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide (document no. A6V10062425) for more information on SI410 connectivity options.

FC330A/CC1115 connection

– Drag the FC330A unit to the NS8015 Fire CNDL Driver.

Fig 36 Connecting FC330A unit to the corresponding CNDL driver

44 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

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 Fire Safety & Security Products 06.2007

Page 46

Configuring the MK8000

5.6 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 depend on the type of connection.

Serial links require defining the COM port, the baud rate and other parameters related to the physical data link. The ISO1745 protocol also allows fine tuning the traffic control: message rate, sample time, and status request timeout (see Tab.1).

Parameter Meaning Notes Message rate Traffic threshold (messages per sec.) above

which the status requests are delayed for limiting the impact on the network.

Sample time Period of time for evaluating traffic rate. Default value is 10. Smaller values will speed

Status request timeout

Max delay before starting a new status request, even without having properly received the end message of the previous request.

Tab.1 ISO1745 traffic control parameters

Default value is 5. Large Cerloop may need a lower value, e.g. = 3. Fast links may tolerate higher values, up to 20.

up the Sample time - used only for fast networks. Default is 30. It may be decreased for speeding up specific technical tests.

In general, MK8000 can communicate with…

– The MK7022, CK11, and FG700A interface using the NS 8010 driver for

ISO1745 protocol at 1200 or 2400 (recommended) baud. Note: the vitality check is required for CK11 and FG700A (see 5.7 below).

– The GW20, GW21, NK822x using the NS8012 driver for CMSDL protocol at

4800 or 9600 (recommended) baud.

– The NK822x over LAN/WAN using the NS8210 driver for CMSDL/IP or CEI79

protocol.

– The NK8225 over LAN/WAN using the NS8011 driver for BACnet/IP protocol. – The SI410 over a serial RS232 line using the NS8014 driver for Sintony protocol

(9600 baud 8N1 recommended).

– The FC330A over a serial RS232 line using the NS8015 driver for CNDL proto-

col.

– The SiPass access control system using the SiPass driver for LAN protocol. – Video devices using the Video Network Manager for LAN video protocols.

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).

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. Please refer to the DMS8000 Network, Fire, and Intrusion Connectivity Configuration Guide (document no. A6V10062425 and particularly to the section dealing with the SI410 Sintony.

46 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 47

5.7 Setting vitality

The vitality timer defines the maximum time between telegrams received from the subsystem. Recommended vitality is 50 seconds (maximum 90 seconds). Setting the vitality is recommended when using 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 Connecting a CS11 (and FC700A) directly to the MK8000

When connected directly to the MK8000, CS11 AlgoRex and FC700A require supervision by the vitality check. You set the vitality timer in the Node tab of the CK11 (and FG700A) and the CC11 (and FC700A).

Connecting a CS11/FC700A to the MK8000

To connect a CS11/FC700A to MK8000, do the following:

1. Set the Vitality (in seconds) in the subsystem node tab for the CK11(FG700A)

and CC11(FC700A). See Fig 39.

2. Drag the CK11(FG700A) to the MK8000 Cerloop Driver.

Configuring the MK8000

Fig 39 Setting the vitality check in the CC11 directly connected to the MK8000

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 48

Configuring the MK8000

5.8 Setting OPC Group names

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 available for each subsystem.

Note also the checkbox named “Exposed in the OPC interface” that must be checked in order to enable the OPC communication on the selected subsystem.

Fig 40 Set the OPC Group Name in each subsystem tab

5.9 Setting the Multi-state value data format

The OPC data item provided by MK8000 (multi-state item) can assume two alternative structures:

 Threshold mode: The item value will be a number represented in 2 bytes; the

possible states will correspond to specific values.

 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.

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. A6V10062413).

Fig 41 Setting the multi-state data format

48 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 49

5.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.

Configuring the MK8000

Fig 42 Setting the diagnostic log options

Item:

Choose:

Where the file will be located.

What the file will be called. Default name is MK8000.log.

How large the file can get before data is written over. Can range from 1-100 MB.

Which log column separator to use when exporting data.

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).

If you choose yes, choose the maximum number of backup files to be kept. Value can be 1-

10. Note that the size parameter (see 3) applies to each individual file.

Detail level Explanation None No log at all

Low Logs: start-up, shutdown, configuration changes, critical errors and diagnostic mes-

Medium In addition to what is logged in ‘low’, operator command actions, messages and warn-

High In addition to what is logged in ‘medium’, OPC messages are logged.

sages

ings about the system function are logged.

Debug All messages are logged.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 50

Configuring the MK8000

5.11 Downloading configuration to the MK8000

When the configuration process is complete, backup your project. Detailed instructions 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.

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.  For more information, see Appendix A Using the System Monitor, p. 74.

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 a download.

Downloading configuration to MK8000

To download the configuration, do the following:

1. Launch the System Supervisor Browser (right click the system monitor iconSystem Supervisor Browser).

2. Wait for the Server and any FEP station icons to turn green.

3. Select a station icon in the left pane.

4. Verify that all the items listed in the right pane turn green.

5. Repeat steps 3 and 4 for each station.

6. From the tools menu, select ‘Download’.

7. Enter specific comments about this download when prompted.

The download completed successfully window appears when download is complete.

50 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 51

5.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. As for the MM8000 license, the MK8000 OPC server license calculation is now based on the static information of the Composer project. More precisely, the license parameters are the:

– physical subsystems configured – physical objects configured for each subsystems – network drivers configured and connected to subsystems

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.

At this point, the required license values for the Composer configuration appear. Clicking ‘Check License Data’ results in the values being compared to the PAK codes. If the license is correct, the text ‘Available’ show in the ‘Available license’ column.

Before checking the license, be sure that the MK8000 server is running. You can start and verify the status of the server tasks with the System Monitor icon in the bot-

tom right corner of your screen.  For more information, see Appendix A Using the System Monitor, p. 74.

Configuring the MK8000

Fig 43 Viewing and checking the MK8000 license

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 52

Testing the Configuration

6 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.

There are three main elements to check. You want to determine that the MK8000:

 Is running on the stations  Has been configured correctly  Communicates correctly with the subsystems.

6.1 Checking Stations

You should perform the following test while the MK8000 is still disconnected from the subsystems to verify that the configuration performed in Composer is correct. Once verified, you should then connect the MK8000 to the subsystems and verify that there are no communication problems (see section 6.2).

To verify that the MK8000 is running on the stations, do the following:

1. Launch the System Supervisor Browser on the OPC server station.

2. Select a station icon in the left pane.

3. Verify that all the items listed in the right pane have turned green.

4. Repeat steps 2 and 3 for each station.

6.2 Checking Internal Configuration

Check the internal configuration with the MK8000 OPC Test Client, which was automatically installed with the MK8000 Stand-Alone software.

This section discusses the testing process using the MK8000 OPC test client.

Connecting to the MK8000 OPC Server

To connect to the MK8000 OPC Server, do the following:

1. Open the OPC Client by clicking: Start  Programs  MK8000  Tools  MK8000 OPC Client

2. Connect MK8000 with OPC Client, just select: ServerConnect to MK8000

 The MK8000 Client Property window appears (see Fig 44).

Fig 44 Client options

52 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 53

Testing the Configuration

– 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 characters).

– Next option concerns the number of items per object, which can be one or

three. If your OPC Client cannot access the OPC item vendor specific prop- erties (containing command information) and you will handle the item commands with two more separate items, then check the “Use new mode" for command items.

– Finally, you have to select the multi-state mode, which can be numeric

(threshold) or bit oriented (bit-mask). Default is numeric mode, check the Bitmask mode checkbox if you want to change it.

– 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

To verify that all subsystems are present, and add them to the client, do the following:

1. Open the Server Address Space dialog window with the Browser Server

icon.

Fig 46 Server Address Space Dialog Window

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 54

Testing the Configuration

2. Verify that all the subsystems are displayed in this list.

3. Use the ‘Add Branch’ button to insert subsystems into the main window for test-

Starting the subsystems, and verifying value and quality

To start the subsystems, and verify their values and qualities, do the following:

1. Select and start the subsystems one by one with the start icon , -- or --

2. Verify that the top OPC object of a subsystem is yellow with value: Fault Ack

3. Verify that the child nodes of the top object are grey with value: Quiet (1000),

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:

– Grey: Quality BAD – Green: Quality GOOD, State Quiet – Yellow: Quality GOOD, State Fault – Blue: Quality GOOD, State Warning – Red: Quality GOOD, State Severe Alarm – Violet: Quality GOOD, State Alarm – White: Quality GOOD, State Anomaly

This colour scheme is specific to the test client and may vary for other clients.

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 5.8, p.48).

ing, and select ‘Done’ when finished.

 The subsystems appear in the main window of the client.

Note: The OPC Test Client performs best with less than 5000 points attached at a time. Therefore it is recommended that you test a few branches at a time rather than testing everything all at once.

Start all the subsystems at once with the start-all icon .

 The subsystem nodes change to yellow.

(1999), and Quality: GOOD.

Note: Do this step while still disconnected from the subsystems.

Quality: BAD. (See Fig 47.)

Checking the values of the objects and their children

When checking values, note that the grid to the right of each selected node shows both the attributes of the selected node and the attributes of its child nodes. In addition, a real time transaction log is shown.

– To open the properties page, use the properties page icon , or double click

on the node selected.

– To display more information on the grid, select ViewView Advanced.

Tip: Use the right-click menu to expand or collapse all items under an object.

54 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

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 communicates correctly with the subsystems, do the following:

1. One by one, physically connect the network subsystem or gateway with the MK8000 OPC server.

2. Verify that each OPC Object turns green, and shows the corresponding value of the subsystem and Quality: GOOD (see Fig 48).

Note: It takes a minute for child nodes to change to good.

3. Send a command from the client and verify that the subsystem receives it.

Fig 48 Subsystem Connected to the Field

Note: If you have any problems, check that the local addresses, baud rates, and COM port being used match the ones defined in the configuration. If there is a problem with vitality, the test client should report a vitality fault.

IMPORTANT: Once you are sure that the configuration you performed in Composer is accurate, you should copy it and save it in a safe place. If the project is lost, you will also lose all the object names that are associated with each item. The object names are uniquely assigned in each new project. Therefore, even if you reproduce the project the object names for the first project will no longer be valid.

56 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 57

Tips for Integrating with an OPC client

7 Tips for Integrating with an OPC client

This section contains general tips to help facilitate the process of integration with an OPC client.

7.1 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 3rd party integration team.

An application called Export Wizard was installed along with the MK8000 for generating export files.

The Export Wizard generates a CSV file (an MS Excel-compatible table) that can include the following fields:

– Object Description; – Full Item Name (recommended); – Technical Text; – Short Item Name (Use this instead of the full item name if your client has a

character limit. Short Item Names are up to 50 characters in length.);

– Object Name.

Note: When exporting to DESIGO INSIGHT the format should be (in this order):

– Object Description – Full Item Name – Technical Text – Short Item Name – Object Name

Opening Export Wizard

You can launch the export wizard from the Start menu:

StartProgramsMK8000ToolsExport Wizard The export wizard allows you to create an export file of the successfully downloaded data.

Generating a table in Export Wizard

To generate a table, do the following:

1. Open the Export Wizard.

2. Click ‘Next’ and select the fields to be included in the table.

Note: Select the fields in the order they are to appear in the table. (See Fig 49.)

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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:

Do coherence test.



The coherence test checks for duplicate OPC object names in the configuration. Typically this feature isn’t used.

Select the character to separate each field.



Choose the character that is set in windows as the field separator. Note: If you aren’t sure which character is being used, select StartControl PanelRegional SettingsNumbers tab to view the list separator.

Include a title line in the table.



If you are exporting a file for viewing, and not for import, include a title line to identify the data columns.

Choose where to save the file.



5. Click next to generate the .CSV file.

Once the .CSV file has been generated, it can be opened in MS Excel and then converted to a MS Access file, if desired.

58 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 59

Tips for Integrating with an OPC client

7.2 Using the test client

You may want to use the MK8000 test client on the client stations for commissioning and debugging purposes. You can choose to install the test client only during product installation. Run the MK8000 installation application as usual on the client and select client from the installation type list.

7.3 Integrating into a network (Distributed configuration)

The key to getting security to work smoothly is to have an administrator account available on each system. On a workgroup network, just create an admin account on each computer with the same username/password combination.

DCOM (Distributed COM) settings have to be set properly on both Client and Server machines to allow the Client to launch and access the Server and to allow the Server to call back to the Client while providing subscribed values (when Client and Server are running on different computers).

The first issue is to properly define users and passwords.

Local user/group:

A Local user is an account that is known ONLY to the machine on which the account was set-up. The same is true for a Local Group. If you need an account to have access to another machine, and the account is a Local User, you will need to create a Local user with the identical username+password on the remote machine. For this reason, we recommend running OPC Client - Server set-ups in a Domain if you can - the maintenance and set-up is easier.

Domain Local user/group:

A Domain User account is one that can be used anywhere within a Windows domain as long as the computer is a member of the domain.

A primary domain controller machine handles authentication of the user, thus allowing you to centralise your security management on the user/group level.

A Domain Group is a group that is available to any computer that is a member of the domain.

We recommend using Domain user accounts and Groups to set-up your DCOM Configuration permissions when setting up OPC client/server connections - the risk of problems is lower, and the long-term maintenance is much easier.What if there

is no Domain?

When a Windows machine is not a member of a Domain, the ONLY user accounts it will trust are those it finds in its own "local" security database. The issue here is authentication. In a domain environment, the domain controller holds domain accounts that are valid on all machines that are part of the domain, while a ‘StandAlone machine’ receives authentication from its own Security Account Manager.In order to avoid permission issues between machines not belonging to the same Domain there is a workaround:You need to create the EXACT SAME user account names AND passwords on BOTH machines. This does not mean that you must be logged in as the same user on both machines to get the system to work, just that the same user/password combination must be defined on each machine.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 60

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.

 On a workgroup network, an account with the same username/password com-

bination must be created on the server and client stations.

 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.

60 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 61

Tips for Integrating with an OPC client

7.4 Possible difficulties in integrating an OPC client

7.4.1 Exporting data to a 3rd party OPC client

This section addresses problems you may have when exporting data to a 3rd 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. In the US this is typically a comma, while in Europe it is typically a semicolon. When the data is exported, the list separator chosen must match the list separator in the Windows Operating System where the data is to be imported.

 Check which list separator is being used

You can check which list separator is being used through the Numbers tab of

the Regional Settings window.

(Start  Control Panel  Regional Settings  Numbers tab)

 Find and replace the separator in the export file

Open the export file in MS Excel or Notepad, and find and replace the current

file separator with the correct one.

7.4.2 Integrating the OPC server into a network

This section addresses problems you may have when integrating into a network, and provides solutions to those problems.

Changing the auto start setting

 Open the services menu (Start  Programs  Administrative Tools  Services

or Start  Settings  Control Panel  Administrative Tools  Services)

 Select DixieSystem Supervisor.  Right-click DixieSystem Supervisor to display the Properties pop-up window.  Select the Automatic in the Startup type drop-down menu in the General tab.

Note: Once you have manually set auto start through Microsoft Services, this

behaviour should stop.

The OPC Client and MK8000 are not communicating

Verify that the name of the server is SBT.MK8000. When using OPC software to access remote OPC servers across the network, you

may encounter two DCOM security related problems:

– Browsing of OPC servers on a remote computer may fail due to the DCOM

settings;

– Access to your remote OPC server may be denied due to the settings of

DCOM.

Machine set-up tips:

– Both Client and Server machines should be within the same network Domain

or Workgroup;

– On a workgroup network all users who will have access to the OPC server

must belong to this workgroup;

– 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 Configuration and Commissioning guide.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 62

Tips for Integrating with an OPC client

Modifying DCOM settings

OPC security is based on the Microsoft Distributed Component Object Model (DCOM), which may affect access to all DCOM based Windows applications. Therefore, the default security settings that you select for the OPC server, FEP, and client machines will affect all DCOM based applications, regardless of whether they are part of OPC or not.

Setting up a DCOM connection between two computers means setting up the stations so that they have permission to access each other. This is a two way street. The client must have permissions to access the machine with the OPC server and vice versa. If you don't have permissions set both ways, then the machines will not communicate correctly.

There are three major types of permissions:

– Access:

These permissions allow a client machine to connect to a server, retrieve a list of OPC servers, and connect to an OPC server application. They also allow the OPC server to make what is known as a "callback" to your client. A callback occurs when you ask the OPC server to notify your client only when data changes.

– Launch:

These permissions are what allow an OPC client application to start or "launch" an EXE running on the machine where the OPC server is located. There are two common EXEs that get launched:

– OPCEnum.exe, a standard OPC common component that lists the available

OPC servers on a machine and returns that list to a client;

– The actual EXE that corresponds to the OPC server.

– Configuration:

These permissions allow a remote client to change the configuration of the OPC server set-up in the registry - you should rarely have to touch these permissions. In fact, you should not do so unless you are an expert with DCOM, and have a specific reason for doing so. The underlying objective here is to allow wide access to the general applications installed on the client and server PCs, while restricting access to the OPC server.

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).

2) Open the DCOM settings window (\WINNT\System32\dcomcnfg.exe).

3) In the Component Service window, right-click the node:

Component Services  Computers  My Computer

4) In the menu that appears, select ‘Properties’

The Computer Properties window will appear (Fig 51).

The instructions below refer to Windows XP. If you are using Windows 2000, please contact the Technical Support.

62 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

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).

General DCOM settings

 General tab

This tab only contains an optional Description field, which you can use to store

a comment text.

 Options tab

The Options tab contains some general parameters that should be kept in the

default settings unless you have very a specific reason for modifying them. The

default values are:

– Transaction timeout (sec) = 60

– Application Proxy RSN = < blank >

– Check local store … = Enabled

 Default Properties tab

Check ‘Enable Distributed COM on this computer’. In addition, make sure that

the Default Authorization Level shows ‘Connect’ and the Default Impersonation

Level are set to ‘Identify’. Uncheck the ‘Additional security for reference track-

ing’ box (match the settings below in Fig 52).

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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 protocols below TCP-IP may be missing).

Fig 53 Default Protocols tab

 MSDTC tab

This tab contains some parameters related to log information and tracing options. We recommend to keep the ‘local coordinator option’ checked and not to modify the other default settings.

64 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

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).

Fig 54 COM security window

The Access Permissions window will appear (Fig 55).

– Allow local and remote access (Fig 55) to the authorised users. For initial

test purposes, you can add ‘Everyone’ in the grant access list.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 66

Tips for Integrating with an OPC client

Fig 55 Default Access permissions

– Select Edit Default… in the Launch and Activation Permissions section of

the COM security tab (Fig 54).

– Allow local and remote ‘Launch’ and ‘Activation’ (Fig 56) to the authorised

users.

 In general, you should include at a minimum the group INTERACTIVE so

that local logged in users can launch the server and, if you are running the OPC server as a service, you may need the SYSTEM account included as well. In workgroup configuration, the MK8000 ‘internal’ user (normally ‘DMS8000_PROC’) must also be authorized. For initial test purposes, you can simply include ‘Everyone’ in the permission list.

– Click OK to close the Computer DCOM properties window.

66 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 67

Tips for Integrating with an OPC client

Fig 56 Default Launch and Activation Permissions

Specific MK8000 DCOM settings

Select the MK8000 DCOM properties. To do this, in Windows XP computers, perform the following steps:

1) In the Component Service window, right-click the node: Component Services  Computers  My Computer  DCOM Config  MM8000 Server (Fig 57).

2) In the menu that appears, select ‘Properties’.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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. The General tab should look like Fig 58:

Fig 58 MM8000Server Properties - General tab

68 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

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

 Security tab - MM8000Server Properties

The default security property settings will be overridden by these settings to restrict remote access to the users defined here. If you do not customize these settings, the default security settings are used. The Security tab should look like Fig 60:

Fig 60 MM8000Server Properties - Security tab

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

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. The Endpoints tab should look like Fig 61:

Fig 61 MM8000Server Properties - Endpoints tab

 Identity tab - MM8000Server Properties

This tab is used to determine which account you want to use to run the application. There are four choices that the system uses to determine which account your DCOM object will run under:

– The Interactive User: the application will run using the security context of the

user currently logged onto the computer. If this option is selected and the user is not logged on, then the application will not start.

– The Launching User: the application will run using the security context of the

user who started the application. The launching user and the interactive user may be the same (recommended).

– This User: you may specify the user whose security context will be used to

run the application.

– The System Account: this is available only for services that use DCOM.

Set the Identity as shown in Fig 62 (Launching User):

70 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 71

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 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’ in the ‘Windows Administration Tools’ to see the list). Use the ‘DCOMXPLogDisable.reg’ command to stop the log being generated.

7.4.3 DCOM settings on OPC clients

In the networked OPC client stations, in order to avoid potential conflicts when callbacks are sent from the server, the DCOM must have the same setting as that of the server.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 72

Tips for Integrating with an OPC client

7.5 Integrating clients that don’t support DCOM

The MK8000 server uses DCOM (Distributed Component Object Model) to communicate via network for distributed configurations. In the event that your OPC client 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.

This section explains how to install, customise, and remove the TransparentOPC.reg file on an OPC client.

Using the DCOM Transparency capability

– Prior to installing the TransparentOPC.reg file, the OPC client and server PCs

must recognise each other on the network. To check this, use the ‘ping’ command in the DOS window: ping ‘Remote Computer Name’

– The TransparentOPC.reg file is compatible with the MK8000 OPC Server.

Installing the file

To install the TransparentOPC.reg file, do the following:

1. Locate the TransparentOPC.reg file (select MK8000 Installation dir  Utili- tiesOPC Transparency).

2. Copy the TransparentOPC.reg file to the OPC client PC.

3. Open the TransparentOPC.reg file with Notepad (right-click menuOpen

with…Notepad)

4. Replace the text: <insert here computer IP address or name> with the name of the computer where the MK8000 server is installed. (See Fig 63.)

Note: Don’t delete the quotes.

Fig 63 Insert the name of the OPC Server

5. Save and close the file.

6. Double-click the file to register it. (Save as a .REG file in the registry.)

72 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 73

Tips for Integrating with an OPC client

Removing OPC Transparency Support

Once installed, the OPC Transparency values should not be deleted from the registry 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.

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.

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 74

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.

The System Monitor helps you quickly perform the following tasks:

– Check the MK8000 status at a glance (for example, whether or not the MK8000

is running)

– View which stations are connected to the MK8000, and if they are running – Start and stop the MK8000 server – Start the MK8000 simulation mode – Open the System Supervisor Browser window

By default, the System Monitor appears as an icon on your task bar at the lower right hand corner of your screen. If the icon is not there, you can launch the System Monitor through the MK8000 menu (Start  Programs  DMS8000  DMS8000 System Monitor). You can also remove the icon from your taskbar through the right-click menu associated with the icon.

Checking the MK8000 status at a glance

You can immediately see whether the MK8000 is running properly by the colour displayed in the icon :

White The MK8000 server or one of the FEPs is starting up. Green Everything is running properly. Yellow The server or one of the FEPs is not running (usually simply

means you need to launch the server).

Red There is an error at the level of the software (extremely rare).

Tooltip: viewing the status of stations connected to the MK8000

Moving the mouse pointer on the icon, a tool-tip text appears that shows the name of the stations configured in MK8000 and whether they are running or not. (See Fig

64.)

Fig 64 System Monitor tool-tip: Displays status of the stations

Right-click menu

Right clicking the System Monitor icon displays a menu (Fig 65) that includes:

– Start or Stop Server: depending whether the system is running or not, only one

of the two commands is active.

– Advanced: open a further submenu (see below). – System Supervisor Browser: launch the browser (see below). – DMS8000 info: open the information window, showing the software version and

the installation type (Fig 66).

– 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’).

74 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 75

Tips for Integrating with an OPC client

Fig 65 System Monitor right-click menu: Server is running, therefore the ‘Stop’

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

– Start Server in Simulation Mode: start the system with an additional applica-

tion that allows simulating field events (see below).

– Simulation Settings: this command permits to set the name of the simulation

PC: in most cases, the default option (localhost) is exactly what you need.

– Show Advanced Information: checking this option allows getting more de-

tailed information in the status messages (Fig 67).

Fig 67 Getting detailed status information

Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc Fire Safety & Security Products 06.2007

Page 76

Tips for Integrating with an OPC client

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 control units in the field.

The Field Simulator (Fig 68) presents a user interface quite similar to the Testing Client application (e.g. see Fig 48).

A tree structure on the left pane (Fig 68-A) allows for selecting the field objects. When an object is selected, the corresponding properties are listed in the top right pane (Fig 68-B). In this list, clicking the ‘Value’ field and picking up one the conditions allows for modifying the property state, thus simulating a field message generated by the control unit.

The pane at the bottom right (Fig 68-C) presents the simulation logging, where all messages are registered.

Fig 68 Field Simulator

A Object tree Hierarchical tree including control units and objects configured in MK8000 B Object property list List of properties of the currently selected object C 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 (StartPrograms MK8000System Supervisor Browser).

In the left pane (Fig 69-A), the MK8000 stations are listed. Selecting one of the stations results in the corresponding processes showing in the right pane (Fig 69-B).

For each process, a small coloured box shows the current process status. The System Supervisor Browser uses the same Green-Yellow-Red colour scheme used in the System Monitor:

– Green Everything is running properly.

76 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 77

Tips for Integrating with an OPC client

– Yellow The process is starting up. – Red There is an error at the level of the software.

In this case, try to stop and start the server again. If the problem persists, contact technical support.

Fig 69 System Supervisor Browser

A Stations Server and FEP stations running the MK8000 B 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 & Security Products 06.2007

Page 78

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. Open the services menu (Start  Settings  Control Panel  Administrative Tools  Services).

2. Select DixieSystem Supervisor.

3. Right-click DixieSystem Supervisor to display the Properties pop-up window.

4. Select one of the options available in the Startup type drop-down menu in the

General tab.

Fig 70 Change auto-start settings for the MK8000 server

78 Building Technologies 048_DMS_MK8000_ICC_MP4.10_A6V10062407_a_en.doc

Fire Safety & Security Products 06.2007

Page 79

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

Siemens MK8000 Quick Reference Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Safety Regulations

1.1 Country-specific standards

1.2 Assembly, installation, commissioning and testing work

1.3 Modifications to the system design and the products

Introduction

2.1 What has been changed in MP 4.10

2.1.1 Documentation changes and corrections in this edition

Installation

3.1 Installation requirements

3.1.1 MK8000 OPC Server System Requirements

3.2 Installation types

3.2.1 Selecting the MK8000 configuration

3.2.2 Selecting the type of Windows security

3.2.3 Enabling the automatic start-up

3.3 Installation checklist

Installing MK8000 Software

4.1 Welcome screen

4.2 Installing the MS-SQL Server software

4.2.1 Installing the MSDE 2000 software

4.2.2 Installing the SQL Express 2005 and SQL 2005 Backward Compatibility

4.3 Installing the SQLXML 3.0 software

4.4 Installing the Microsoft .NET Framework V1.1

4.5 Installing the Microsoft .NET Framework V2.0

4.6 MK8000 OPC server

4.6.1 MK8000 installed software

4.7 Installing the MK8000 on the main (Stand-Alone) station

4.7.1 Installing the MK8000 on the FEP (Distributed Systems)

4.7.2 Installing the MK8000 on the client (test for Distributed Systems)

4.7.3 Installing the MK8000 license station (dual-server with Marathon EverRun FT)

4.8 Testing the network communication (Distributed Systems)

5.1 Configuration Checklist

Configuring the MK8000

5.2 MK8000 architecture in the Composer project

5.3 Control units and network components

5.4 MK8000 Communication drivers

5.5 Connecting networks to the MK8000

5.5.1 What to drag to the drivers

5.6 Adjusting network settings

5.7 Setting vitality

5.7.1 Connecting a CS11 (and FC700A) directly to the MK8000

5.8 Setting OPC Group names

5.9 Setting the Multi-state value data format

5.10 Setting up the diagnostic log

5.11 Downloading configuration to the MK8000

Testing the Configuration

6.1 Checking Stations

6.2 Checking Internal Configuration

Tips for Integrating with an OPC client

7.1 Exporting data to a 3rd party OPC Client

7.2 Using the test client

7.3 Integrating into a network (Distributed configuration)

7.4 Possible difficulties in integrating an OPC client

7.4.1 Exporting data to a 3rd party OPC client

7.4.2 Integrating the OPC server into a network

7.4.3 DCOM settings on OPC clients