CON_016 OPC Tools User Guide

OPC Tools User Guide CON_016 October 2008

Copyright Notice Since the equipment explained in this document has a variety of uses, the user and those responsible for applying this equipment must satisfy themselves as to the acceptability of each application and use of the equipment. Under no circumstances will Emerson Process Management be responsible or liable for any damage, including indirect or consequential losses resulting from the use, misuse, or application of this equipment. The text, illustrations, charts, and examples included in this manual are intended solely to explain ® the use and application of the Ovation unit. Due to the many variables associated with specific uses or applications, Emerson Process Management cannot assume responsibility or liability for actual use based upon the data provided in this manual. No patent liability is assumed by Emerson Process Management with respect to the use of circuits, information, equipment, or software described in this manual. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, including electronic, mechanical, photocopying, recording or otherwise without the prior express written permission of Emerson Process Management. The document is the property of and contains Proprietary Information owned by Emerson Process Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and the user agrees to treat this document in strict accordance with the terms and conditions of the agreement under which it was provided. This manual is printed in the USA and is subject to change without notice. Ovation and WEStation are registered trademarks of Emerson Process Management. All other trademarks or registered trademarks are the property of their respective holders. Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved. Emerson Process Management Power & Water Solutions 200 Beta Drive Pittsburgh, PA 15238 USA E-Mail: [email protected] Website: https://www.ovationusers.com

Contents 1

OPC introduction

1.1 1.2

What is OPC? ..................................................................................................................... 1 Ovation network overview ................................................................................................... 2

2

Ovation OPC Data Access Server

2.1 2.2 2.3 2.4

What is the Ovation OPC Data Access Server? ................................................................. 3 Hardware requirements for the Ovation OPC Data Access Server .................................... 5 Soft ware requirements for the Ovation OPC Data Access Server .................................... 5 License requirements for the Ovation OPC Data Access Server ....................................... 5 2.4.1 License limits ..................................................................................................... 5 Installation of the Ovation OPC Data Access Server software ........................................... 6 2.5.1 To Install the Ovation OPC Data Access Server............................................... 6 2.5.2 To license the Server ........................................................................................ 6 2.5.3 External libraries................................................................................................ 7 2.5.4 Files installed during setup................................................................................ 7 2.5.5 To remove Ovation OPC Data Access Server programs.................................. 7 Normal Ovation OPC Data Access Server operation ......................................................... 8 Client connection and operation ......................................................................................... 8 2.7.1 Required information to read or write to an OPC item ...................................... 8 2.7.2 Return values for Ovation OPC Data Access Server items ............................ 11 2.7.3 Update rate...................................................................................................... 12 2.7.4 OPC quality ..................................................................................................... 12 Ovation OPC Data Access Server control panel .............................................................. 14 2.8.1 To Use the Ovation OPC Data Access Server Control Panel......................... 14 Error Codes for the Ovation OPC Data Access Server .................................................... 17 Registry Entries................................................................................................................. 18 Browsing for Ovation OPC Data Access Servers on a Remote Network ......................... 19 Visual Basic automation interface for OPC Client ............................................................ 20 2.12.1 Visual Basic example ...................................................................................... 20

2.5

2.6 2.7

2.8 2.9 2.10 2.11 2.12

1

3

3

Ovation OPC Alarm and Events Server

3.1

What are Alarms and Events? .......................................................................................... 25 3.1.1 What are Simple Events?................................................................................ 26 3.1.2 What are Condition Events?............................................................................ 26 3.1.3 What are Tracking Events? ............................................................................. 26 3.1.4 What is Event Subscription? ........................................................................... 27 What is the Ovation OPC Alarms and Events Server?..................................................... 27 Licensing the Alarms and Events Server .......................................................................... 27 3.3.1 SOE Sequence of Events Licenses ................................................................ 27 3.3.2 Operator Event Licenses................................................................................. 28

3.2 3.3

CON_016

25

i

Table of Contents

3.4 3.5 3.6 3.7 3.8

4

Ovation OPC Client Mapper

4.1 4.2 4.3 4.4 4.5 4.6

4.10 4.11

What is the OPC Client Mapper?...................................................................................... 37 Ovation OPC Client Map Service...................................................................................... 37 Ovation OPC Configuration Tool ...................................................................................... 38 Ovation OPC Client Map Control Panel............................................................................ 38 Default installation and custom configurations of the Ovation OPC Client Mapper.......... 38 Operating system requirements........................................................................................ 38 4.6.1 To Install OPC Client Mapper from CDROM................................................... 38 4.6.2 To Change the Client Mapper from a Windows Service to COM Server........ 40 4.6.3 To Change the Client Mapper from COM Server to Windows Service........... 40 Configuring and customizing the OPC Client Mapper Server........................................... 40 4.7.1 To configure Rovisys OPC90 Server .............................................................. 41 4.7.2 To configure Intellution’s iFIX OPC server ...................................................... 41 4.7.3 To configure your OPC system ....................................................................... 41 Client Mapper data transfer............................................................................................... 43 4.8.1 Operation of OPC Client Mapper .................................................................... 44 Ovation OPC Client Mapper control panel........................................................................ 45 4.9.1 To Access the OPC Client Mapper control panel............................................ 45 OPC redundancy manager ............................................................................................... 46 OPC redundancy configuration ......................................................................................... 47

5

Ovation OPC Client/Configuration tools

5.1

What is the OPC Client/Configuration tool........................................................................ 49 5.1.1 To start the OPC Client/Configuration tool...................................................... 49 5.1.2 OPC Configuration tool main window ............................................................. 50 5.1.3 OPC Client tool main window.......................................................................... 51 OPC interface functions .................................................................................................... 52 5.2.1 Menu Bar ......................................................................................................... 52 5.2.2 Toolbar ............................................................................................................ 52 5.2.3 Hierarchy browser ........................................................................................... 53 5.2.4 Tree structure .................................................................................................. 54 5.2.5 View window.................................................................................................... 54

4.7

4.8 4.9

5.2

ii

System Requirements for the Alarms and Events Server ................................................ 28 eDB Configuration Information.......................................................................................... 28 To Install OPC Alarms and Events Server........................................................................ 28 To Configure OPC Alarm Client and Event Subscription.................................................. 29 3.7.1 To Add or Configure an Event Subscription.................................................... 31 Ovation OPC Event Monitor Tool...................................................................................... 31 3.8.1 To access the Ovation OPC Event Server Main Window ............................... 32 3.8.2 To Check the Ovation OPC Alarms and Events Server Status ...................... 32 3.8.3 To Change the Ovation OPC Alarms and Events Server from a Windows Service to COM Server................................................................. 33 3.8.4 To Change the Ovation OPC Alarms and Events Server from a COM Server to Windows Service................................................................. 33 3.8.5 To View or Configure OPC Alarms and Events Server Settings..................... 34 3.8.6 To View OPC Client Connections ................................................................... 35 3.8.7 To View Ovation Alarms and Events Server Version, Start Time Information 36

37

49

CON_016

Table of Contents

5.3

5.4 5.5 5.6

5.7

5.2.6 Status bar ........................................................................................................ 54 Right-click (context) menus............................................................................................... 54 5.3.1 Root context menu .......................................................................................... 55 5.3.2 Server context menu ....................................................................................... 55 5.3.3 Group context menu........................................................................................ 56 5.3.4 Item context menu........................................................................................... 57 5.3.5 Subscription context menu .............................................................................. 57 Shortcut keys .................................................................................................................... 58 Preferences....................................................................................................................... 59 OPC Interface windows..................................................................................................... 60 5.6.1 Server configuration window ........................................................................... 60 5.6.2 Group configuration window............................................................................ 61 5.6.3 Item window..................................................................................................... 62 5.6.4 Subscription window........................................................................................ 64 5.6.5 Monitor items window...................................................................................... 65 5.6.6 Monitor Events ................................................................................................ 66 Dialog Boxes for OPC Tools ............................................................................................. 66 5.7.1 Browse OPC Alarms and Events / Data Access Server windows .................. 67 5.7.2 OPC item ID browser ...................................................................................... 69 5.7.3 Ovation point browser ..................................................................................... 70 5.7.4 Ovation field browser....................................................................................... 71 5.7.5 Server State dialog box ................................................................................... 72 5.7.6 Group State dialog box.................................................................................... 73 5.7.7 Item State dialog box....................................................................................... 74 5.7.8 Item Properties dialog box............................................................................... 76 5.7.9 Write value to OPC item dialog box ................................................................ 77 5.7.10 Generate Items dialog box .............................................................................. 78 5.7.11 Add Multiple Items dialog box ......................................................................... 81 5.7.12 Find dialog box ................................................................................................ 81 5.7.13 Subscription State dialog box.......................................................................... 82 5.7.14 Subscription Filter dialog box .......................................................................... 83 5.7.15 Subscription Select Attributes dialog box........................................................ 88 5.7.16 Browse Categories dialog box......................................................................... 90

93

6

Security

6.1 6.2 6.3

Making connections between OPC Servers and Clients and connection scenarios ........ 93 Relationships between computers involved in OPC communication................................ 94 Situations where both computers are members of the same Windows domain............... 95 6.3.1 To add a local user to a system that is not used as a domain server ............. 95 6.3.2 To set up a Windows server to execute as a specific user ............................. 95 6.3.3 To set up a DCOM server to run as a particular user ..................................... 96 OPC clients running as an ordinary application on the user desktop ............................... 96 Setting Security for Windows NT and 2000 ...................................................................... 97 6.5.1 To set security ................................................................................................. 97 OPC via DCOM with Windows XP Service Pack 2 and Windows 2003 Server Service Pack 1............................................................................ 101 DCOM Enhancements .................................................................................................... 102 6.7.1 To Configure DCOM for OPC using XP Service Pack 2 and Windows 2003 Service Pack 1...................................................................... 102

6.4 6.5 6.6 6.7

CON_016

iii

Table of Contents

6.8 6.9

iv

Windows Firewall ............................................................................................................ 106 6.8.1 To Configure the Firewall .............................................................................. 107 Local Security Policy Settings ......................................................................................... 111 6.9.1 To set Local Security Policy Settings for Domain Machines......................... 111 6.9.2 To set Local Security Policy Settings for Workgroup Machines as Administrator ................................................................................................................... 113

Glossary of Terms

115

Index

137

CON_016

S

E C T I O N

1

OPC introduction

IN THIS SECTION What is OPC?...................................................................................................................... 1 Ovation network overview ................................................................................................... 2

1.1

What is OPC? OPC is an acronym for (Object Linking Embedding) OLE for Process Control. OPC is open connectivity in industrial automation and in the systems supporting the industry. OPC is a series of standard specifications which are created based on general computing technology to allow for interoperability between various industry standards. The OPC standard specifies the communication of real-time plant data between any manufactures control devices. OPC is based on OLE, COM, and DCOM technologies developed by Microsoft for the Microsoft Windows operating system. OPC was designed to form a connection between Windows based applications, and process control hardware and software applications. OPC is an open standard which allows for a consistent method of accessing data from various devices throughout the control process, regardless of the source and type of the data. The purpose of OPC is to define a common interface that is written once and then reused by any business, SCADA, HMI, or custom software package. Various software packages can have access to data from process control devices through an OPC server. Once an OPC server is written for a particular device, it can then be reused by any application that is able to act as an OPC client. OPC servers use Microsoft's OLE technology to communicate with clients, this is also referred to as COM technology (Component Object Model). COM technology provides a standard for real-time information exchange between software applications and process hardware to be defined. Note: For additional information about OPC, visit the OPC Foundation web site at http://www.opcfoundation.org.

CON_016

1

1.2 Ovation network overview

1.2

Ovation network overview The Ovation network transmits data elements known as “points” throughout the Ovation system. An Ovation point has a value and various other properties (fields, point name, limits, status, quality, point record type and ASCII descriptions). There are currently 11 Ovation point types, such as Analog, Digital and Packed Digital. Point Types are identified by a two-letter mnemonic as shown in the following table. For additional information, refer to Ovation Record Types Reference Manual. Examples of Ovation Points POINT N AME

FIELD N AME

DESCRIPTION

LA100

AV

Analog Value of point

LA101

1W

32-bit integer; status of analog point – includes point quality

DA100

PN

ASCII point name, (for example, LA100)

LD101

1W

32-bit integer; status of digital point - includes digital value in bit 0

LA101

HL

Analog high limit

DA101

TV

32-bit floating point number; top of output scale

Ovation points are identified by names up to 16 characters in length. Fully qualified point names are made up of three parameters: 16 character maximum point name, six character maximum unit name and an eight character maximum network name (for example, AI009.Unit1@Net2). Point names are not case sensitive. Note: Ovation systems 3.0 or later can have point names a maximum of 24 characters in length. Information about all points is stored in a database file called the Point Database. The Point Database also contains network names related to the system. These network names are used in the forming of OPC tags or item names as described, Client Connection and Operation (see page 8).

2

CON_016

S

E C T I O N

2

Ovation OPC Data Access Server

IN THIS SECTION What is the Ovation OPC Data Access Server? ................................................................. 3 Hardware requirements for the Ovation OPC Data Access Server .................................... 5 Soft ware requirements for the Ovation OPC Data Access Server .................................... 5 License requirements for the Ovation OPC Data Access Server ....................................... 5 Installation of the Ovation OPC Data Access Server software ........................................... 6 Normal Ovation OPC Data Access Server operation ......................................................... 8 Client connection and operation.......................................................................................... 8 Ovation OPC Data Access Server control panel .............................................................. 14 Error Codes for the Ovation OPC Data Access Server .................................................... 17 Registry Entries ................................................................................................................. 18 Browsing for Ovation OPC Data Access Servers on a Remote Network ......................... 19 Visual Basic automation interface for OPC Client............................................................. 20

2.1

What is the Ovation OPC Data Access Server? An OPC Data Access Server is a software program that runs on a Windows machine and supports the OPC Interface. This Interface can be used on Windows or Solaris systems and contains the following:

OPC Server Objects Each time a client is connected to the server, a Server object is created. The OPC Server object contains the following information about the state of the current connection: List of groups Server status Information about the available items

OPC Group Objects Can be multiple groups Contains a logical organization of data Identified by a user-defined name Groups contain a set of OPC items Items in a group have a common update rate

OPC Items (process data points) Organized into OPC groups OPC items are identified by a syntax specified by the server vendor. For the Ovation syntax, refer to Client Connection and Operation (see page 8).

CON_016

3

2.1 What is the Ovation OPC Data Access Server?

Use a common mechanism to read and write data Access to the OPC Data Access Server is through an OPC compliant client program. Multiple clients can connect to a single OPC Server application. Each client connects to a separate instance of an OPC Server object within the OPC Data Access Server. This means each client has its own sets of OPC groups and items. A client can execute either on the same computer as the OPC Data Access Server or can connect through a network.

Figure 1: OPC Interface Overview

4

CON_016

2.2 Hardware requirements for the Ovation OPC Data Access Server

2.2

Hardware requirements for the Ovation OPC Data Access Server The following requirements are necessary before starting the Ovation OPC Data Access Server:

2.3

2.4

PC must be Ovation compliant.

Server must have a connection to the Ovation network. Refer to the Ovation Operator Station User Guide.

(Optional) Ethernet network connection to other Windows 95/98/NT/2000/XP/2003 machines acting as OPC Clients to the Ovation OPC Data Access Server.

Soft ware requirements for the Ovation OPC Data Access Server

Server must be a computer running a Microsoft Windows operating system supported by Ovation.

OPC Client Application (for example, Intellution’s iFIX).

Ovation software including drivers, libraries, and executable programs providing connections to the Ovation network.

Ovation OPC Data Access Server license created with an appropriate number of connections.

License requirements for the Ovation OPC Data Access Server The Ovation OPC Data Access Server requires a license to operate. Licenses are based on the number of client connections. Each client requires a single connection to an Ovation OPC Data Access Server to operate. There are no licensing restrictions on the number of groups in a client connection or the number of OPC items in a group. A license permitting the desired number of simultaneous client connections is required to run the Ovation OPC Data Access Server. A drop fault code is issued when attempting to connect to the Ovation OPC Data Access Server whenever it is not properly licensed. The connection will be allowed even if there is a drop fault. However, periodic drop faults continue to occur. Each connection needs a single license. Once the connection is broken, the license is returned and is available for other clients. A trial license is provided with the Ovation OPC Data Access Server. Refer to the following section for instructions on acquiring a permanent license, for additional information refer to, To License the Server (see page 6).

2.4.1 License limits The Ovation OPC Data Access Server is licensed based on client connections. The license limits are determined when the software is purchased.

CON_016

5

2.5 Installation of the Ovation OPC Data Access Server software

2.5

Installation of the Ovation OPC Data Access Server software Before installing the Ovation OPC Data Access Server software, the Ovation Windows software must be installed, refer to Ovation Software Load Kit. The Ovation OPC Data Access Server is installed using a standard Windows installation procedure; refer to the To Install the Ovation OPC Data Access Server (see page 6). Note: Installation must be performed while logged in with Administrator privileges. This installation program performs the following:

Installs the Ovation OPC Data Access Server software onto the computer acting as the Server.

Installs various dynamically linked libraries, refer to External Libraries (see page 7).

Sets the location of files in the user-selected directory, refer to Files Installed During Setup (see page 7).

Registers the Ovation OPC Data Access Server and related files, refer to Files Installed During Setup (see page 7).

2.5.1 To Install the Ovation OPC Data Access Server 1. Insert the Ovation OPC Data Access Server CDROM containing the setup.exe program into the computer acting as the Ovation OPC Data Access Server. 2. Execute the setup.exe program found in the root directory on the CD. 3. Follow the instructions on the screen. Note: See the Security section for information on DCOM and Firewall security settings to ensure proper operation of the Data Access server. Refer to Security (see page 93).

2.5.2 To license the Server 1. Run the program C:\ovation\opc\license.exe. A window appears. 2. Select Product OPC Server. 3. Provide the code displayed there to Emerson Process Management. You will be given a key code. 4. Select Add License and enter the key code provided by Emerson. 5. Press Add.

6

CON_016

2.5 Installation of the Ovation OPC Data Access Server software

2.5.3 External libraries The Ovation OPC Data Access Server uses standard Ovation libraries to access and write Ovation point fields. These are installed during the Ovation installation. The following libraries, installed during the setup process, must be accessible to the Ovation OPC Data Access Server program. Dynamic linked libraries LIBRARY

DESCRIPTION

OPCDAAuto.dll

%WINDIR%\system32

OPCComn_ps.dll

%WINDIR%\system32

OPCProxy.dll

%WINDIR%\system32

2.5.4 Files installed during setup Three software components are installed by the install program.

Ovation OPC Data Access Server Software

Ovation OPC Client Software

OPC Data Access Control Panel Applet

The setup program installs software in the user-selected directory, makes entries into the registry, and registers the Ovation OPC Data Access Server and related files. The registration process also makes registry entries; this is what allows OPC clients to actually remotely connect to and retrieve values from the Ovation OPC Data Access Server. The setup program installs most files under the C:\ovation\opc directory. If desired, you can change this during installation. Some configuration and data files are installed under the directory tree specified by the WDPF_HOME environment variable.

2.5.5 To remove Ovation OPC Data Access Server programs 1. From the client machine, launch the Control Panel from the Start menu bar or My Computer. 2. Select the Add/Remove Programs icon from the Control Panel window. 3. Select and remove the entry labeled Ovation OPC Data Access Server from the scrolling list. 4. Restart the machine. Note: You must have administrative security privileges on the Windows drop in order to remove the Ovation OPC Data Access Server. Disconnect all clients using the Ovation OPC Data Access Server using the client machine.

CON_016

7

2.6 Normal Ovation OPC Data Access Server operation

2.6

Normal Ovation OPC Data Access Server operation The Ovation OPC Data Access Server is a Windows service that automatically starts when the system is started. Normal program operation of the Ovation OPC Data Access Server is automatic. This program is not visible when running. If you want to verify that OPC is running, right-click on the Task bar at the bottom of the computer screen and select Task Manager. Ovation OPC should be listed in the Task list. You can also check the status by accessing the Ovation OPC Data Access Server Control Panel window (described in Using the Ovation OPC Data Access Server Control Panel (see page 14)). If you experience trouble with starting the Ovation OPC Data Access Server, you must re-register the Server and the related DLLs.

2.7

Client connection and operation Note: This section assumes that you are familiar with the operation and specification of point data on an Ovation network. For more detailed information, refer to the Ovation Record Types Reference Manual.

2.7.1 Required information to read or write to an OPC item A client must specify three pieces of information in order to be able to read from or write to an OPC item:

Server Name — typically, a connection dialog box enumerates available OPC Servers on a machine. The name of the Ovation OPC Data Access Server is OVATION.OPC or OVATION.OPC.4 where 4 is the revision number. To connect to a remote Server you must indicate both the machine name and the OPC Server name.

Group Name — after a successful connection, the client must create and add one or more OPC Groups to the OPC Server.

Item Name — the client program creates and adds OPC Items to existing OPC Groups. The OPC Items are identified by a text string. The syntax of the text string is unique for each OPC Server type. The Ovation OPC Data Access Server supports two types of syntax for OPC Items. The syntax is selected from the Ovation OPC Data Access Server Control Panel window described in: Using the Ovation OPC Data Access Control Panel (see page 14).

Note: If the network is not specified, the network where the OPC Server resides will be utilized. 1. The first type of syntax is the Default Item syntax. Possible entries are: [email protected]:bit [email protected] PointName.Unit@NetworkName PointName.Unit PointName PointName.Field PointName.Field:bit For the first syntax, the point type as indicated by the point name implies a default field name. For example, Analog (LA, DA) points have the Analog Value (AV) field as the default field name. Digital (LD, DD) points have bit 0 of the Digital Status (1W) as the default field.

8

CON_016

2.7 Client connection and operation Some fields, depending on record type, allow access to individual bits of the field. Refer to the Ovation Record Types Reference Manual for information about data types of record fields. To access a single bit in a record field, the following syntax would be used: . : OR . @ .: This syntax identifies a single bit in the record field. Multiple bits cannot be accessed. Access the entire field instead. The data type of individual bits is Boolean. Single Bit Data Type Examples for Default Syntax RECORD TYPE

BIT NUMBER

DESCRIPTION

Digital Point

D100.1W:15

Accesses time-out bit in status word.

Packed Point

GP100.A2:4

Accesses bit 4 of the value field.

Analog

A100.2W:4

Quality latch bit of analog second status word.

Drop Status

Drop1.HC:2

FDDI ring down bit of network status word.

2. The second type of syntax is the Alternate Item syntax. Possible entries are: PointName$Unit@NetworkName$Field%bit PointName$Unit@NetworkName$Field PointName$Unit@NetworkName PointName$Unit PointName PointName$Field PointName$Field%bit Some fields, depending on record type, allow access to individual bits of the field. Refer to the Ovation Record Types Reference Manual for information about data types of record fields. To access a single bit in a record field, the following syntax would be used: $% OR $ @ $% This syntax identifies a single bit in the record field. Multiple bits cannot be accessed. Access the entire field instead. The data type of individual bits is Boolean. Single Bit Data Type Examples for Alternate Syntax RECORD TYPE

BIT NUMBER

DESCRIPTION

Digital Point

D100$1W%15

Accesses time-out bit in status word.

Packed Point

GP100$A2%4

Accesses bit 4 of the value field.

Analog

A100$2W%4

Quality latch bit of analog second status word.

Drop Status

Drop1$HC%2

FDDI ring down bit of network status word.

The following table provides examples of the syntax for Item Names (Default or Alternate):

CON_016

9

2.7 Client connection and operation

Item Name Syntax Examples POINT N AME A100.Unit1@Net3

FIELD N AM E

OPC ITEM

—

A100.Unit1@Net3 OR A100$Unit1@Net3

D100.Unit1@Net3

—

D100.Unit1@Net3 OR D100$Unit1@Net3

A101.Unit1@Net3

HL

[email protected] L OR

NOTES This is an analog point which implies the “AV” or floating point value field as the field name. This is a fully qualified point name. This is a digital point which implies the “1W” or First Status field. Furthermore, the value bit (Bit 0) is extracted from the data to return a Boolean value. This is the high limit field (a floating point value) for a fully qualified point name.

[email protected] L P200

A2

P200.A2 OR

This is a Packed point returning a 16-bit integer value.

P200$A2 AI100

HL

AI100.HL OR

This is a high limit field of an analog point returning a 32-bit floating point value.

AI100$HL DI101

1W

DI101.1W OR DI101$1W

First Status word of a digital point. Because the field name is explicitly named, the return value is the entire 32-bit integer value.

The following table lists the default fields for point record types: Point record type default fields POINT RECORD TYPE

10

DEFAULT FIELD D AT A TYPE

POINT RECORD MNEMONICS

Analog

AV

Float (VT_R4)

LA, DA

Digital

See Note 1

Boolean (VT_BOOL)

LD, DD

Packed

A2

Long (VT_I4)

LP, DP

Algorithm

CN

Short (VT_I2)

LC

Drop Status

FC

Short (VT_I2)

DU

Module

1W

Long (UT_I4)

RM

Node

1W

Long (UT_I4)

RN

1

2 2

CON_016


POINT RECORD TYPE

DEFAULT FIELD D AT A TYPE

POINT RECORD MNEMONICS

1

Special processing is performed for digital points. The entire 32 bit 1W field is read, the Value bit (BIT 0) is extracted, and the Value bit is returned as a Boolean. 2

For some record types, there is no Value field. For these record types, the default field is arbitrarily designated.

2.7.2 Return values for Ovation OPC Data Access Server items As described in the previous table, Point Record Type Default Fields, the record type Field Name determines the basic data type of the return data. OPC Items return a VARIANT data structure. The VARIANT data structure is a union of a large number of simple data types. The basic data types of fields in an Ovation point map into the VARIANT data structure in a straightforward fashion. The exception to this is the ASCII data type. The basic string data type in the VARIANT is called a BSTR. The BSTR data types encapsulate the actual string of characters and length. Refer to the following table. Variant types OV ATION FIELD TYPE

V ARI ANT TYPE

NOTES

(B) Byte - 8 Bit integer

V_11

No real distinction in Ovation field types between signed and unsigned integer types.

(I16) Integer - 16 Bit Integer

V_12


(I32) Long Integer - 32 Bit Integer

V_14


(R32) Floating Point - 32 Bit

V_R4

Double (64 Bit) floating point values are not supported in Ovation.

C6 - Six byte ASCII

BSTR

C8 - Eight byte ASCII

BSTR

C16 - Sixteen byte ASCII

BSTR

C30 - Thirty byte ASCII

BSTR

The normal rules for reading and writing Ovation points apply. You cannot write to the value field (AV, 1W, ...) of a point unless it is originated on the drop. You can modify the other fields such as the HL or high-limit field of an analog point.

CON_016

11


2.7.3 Update rate When a group is created, the user specifies an interval in milliseconds for updating the data. In OPC, only changes to the data are broadcast. If you define the interval of a group as 1,000 milliseconds (1 second), then the Ovation OPC Data Access Server reads the value of each item in the group every 1,000 milliseconds. If a particular item has not changed value, then the Ovation OPC Data Access Server does not transmit that value to the client. Only changed item values are sent. For Ovation systems, the minimum update rate is 100 milliseconds.

2.7.4 OPC quality OPC quality is read only. It cannot be changed by OPC Client applications. Quality is only propagated for the default fields (point values). For all other fields, OPC quality is always good if the data is available. If the data is not available, the quality is always bad. In order to obtain the default fields (point value), specify the point name without a field or the value field. Refer to the Point Record Type Default Fields table for default field definitions, Return Values for Ovation OPC Data Access Server Items (see page 11). OPC has a definition of quality that differs from Ovation defined quality. Ovation point quality is associated with the point value. This is the AV field for analog points. For fields other than the value fields of a point, the OPC point quality is always OPC_QUALITY_GOOD, unless the point is timed out or not available. For the point value field of a point, the Ovation point quality maps to the OPC quality. OPC quality is based on certain bits; refer to the 1W Record Type field in the following table:

Bit 15 = Timeout bit

Bit 11 = Scan off bit

Bit 10 = Operator entered bit

Bit 9, Bit 8 = SHC quality

OPC Quality Bits POINT TYPE

CONDITIONS

OPC QUALITY

LA, DA

High Limit and Low Limit Bits Set (Sensor Alarm)

OPC_QUALITY_BAD+

Good Quality AND Operator Entered Bit Set

OPC_QUALITY_GOOD+

Good Quality AND Operator Entered Bit NOT Set AND Scan off Mask Set

OPC_QUALITY_UNCERTAIN+

LA, DA

Other Good Quality Cases

OPC_QUALITY_GOOD

LA, DA

Fair Quality AND Operator Entered Bit Set

OPC_QUALITY_GOOD+

LA, DA

LA, DA

OPC_QUALITY_SENSOR_FAILURE

OPC_QUALITY_LOCAL_OVERRIDE

OPC_QUALITY_LAST_USABLE


12

CON_016


POINT TYPE

CONDITIONS

OPC QUALITY

LA, DA

Fair Quality AND Operator Entered Bit NOT Set AND Scan off Mask Set


LA, DA

Other Fair Quality Cases

OPC_QUALITY_UNCERTAIN

LA, DA

Bad Quality AND Scan off Mask Set

OPC_QUALITY_BAD+


OPC_QUALITY_OUT_OF_SERVICE LA, DA

Other Bad Quality Cases

OPC_QUALITY_BAD

LA, DA

If the Low Limit Bit is Set

OPC_LIMIT_LOW is added to the calculated OPC Quality

LA, DA

If the High Limit Bit is Set

OPC_LIMIT_HIGH is added to the calculated OPC Quality

LA, DA

Timeout Bit Set

OPC_QUALITY_BAD+ OPC_QUALITY_LAST_KNOWN

LD, DD

High Limit and Low Limit Bits Set (Sensor Alarm)

OPC_QUALITY_BAD+

Good Quality AND Operator Entered Bit Set

OPC_QUALITY_GOOD+

Good Quality AND Operator Entered Bit NOT Set AND Scan off Mask Set


LD, DD

Other Good Quality Cases

OPC_QUALITY_GOOD

LD, DD

Fair Quality AND Operator Entered Bit Set

OPC_QUALITY_GOOD+

LD, DD

LD, DD

OPC_QUALITY_SENSOR_FAILURE



OPC_QUALITY_LOCAL_OVERRIDE LD, DD

Fair Quality AND Operator Entered Bit NOT Set AND Scan off Mask Set


LD, DD

Other Fair Quality Cases

OPC_QUALITY_UNCERTAIN

LD, DD

Bad Quality AND Scan off Mask Set

OPC_QUALITY_BAD+


OPC_QUALITY_OUT_OF_SERVICE LD, DD

Other Bad Quality Cases

OPC_QUALITY_BAD

LD, DD

Timeout Bit Set


LP, DP,

Scanoff Mask NOT Set

RM, RN LP, DP,

OPC_QUALITY_UNCERTAIN+ OPC_QUALITY_LAST_USABLE

Other Cases

OPC_QUALITY_GOOD

Timeout Bit Set

OPC_QUALITY_BAD+

RM, RN LP, DP, RM, RN DU, LC

CON_016

OPC_QUALITY_LAST_KNOWN All Cases

OPC_QUALITY_GOOD

13

2.8 Ovation OPC Data Access Server control panel

POINT TYPE

CONDITIONS

OPC QUALITY

DU, LC

Timeout Bit Set


Note: If the point is a status field (1W), OPC quality is always OPC_QUALITY_GOOD.

2.8

Ovation OPC Data Access Server control panel The Ovation OPC Data Access Server control panel is used to start, stop, and monitor the Ovation OPC Data Access Server.

2.8.1 To Use the Ovation OPC Data Access Server Control Panel 1. Select: Start -> Control Panel -> Ovation OPC Data Access Server Config.

14

CON_016

2.8 Ovation OPC Data Access Server control panel 2. The Ovation OPC Data Access Server Control Panel window appears. Make the desired changes. The controls in this window are described in the following table.

Figure 2: Ovation OPC Data Access Server Control Panel Window Ovation OPC Data Access Server control panel attributes FIELD

DESCRIPTION

Start/Stop Button

Toggle button starting (green light) or stopping (red light) the Ovation OPC Data Access Server. Displays the current running status of the Server.

CON_016

15

2.8 Ovation OPC Data Access Server control panel

FIELD

DESCRIPTION

Logging Level

Indicates the minimum security level of events which are logged by the Server. Options are: None = No messages are logged. System = System messages are logged. Errors = Errors and system messages are logged. Warnings = Warnings, errors, and system messages are logged. Informational = Informational, warnings, errors, and system messages are logged. Debug = Detailed messages used in troubleshooting.

Debug Level

Debug Level fields become active when Debug is selected from the Logging Level drop-down menu. Selecting one or more of the Debug Level options from the menu sends the associated messages to the Ovation Error Log.

Use Default Item Syntax

Indicates the Item syntax currently being used by the Server.

OR Use Alternate Item Syntax # Servers

Number of Servers connected at this time.

# Groups

Number of Groups connected at this time.

# Items

Number of Items connected at this time.

# Updates

Total number of Item updates since the Server started.

# Async Reads

Total asynchronous reads since the Server started.

# Sync Reads

Total synchronous reads since the Server started.

# Async Writes

Total asynchronous writes since the Server started.

# Sync Writes

Total synchronous writes since the Server started.

OK Button

Saves the changes to the Server.

Apply Button

Saves the changes to the Server.

Cancel Button

Restores the settings to the last saved settings.

3. After the desired changes are made, select OK or Apply to commit the changes to the Server. After the changes have been applied, stopping and starting the Server is recommended. 4. Press the Start button to start the Server (light becomes green) or press the Stop button to stop the Server (light becomes red). Yellow lights indicate transition of information.

16

CON_016

2.9 Error Codes for the Ovation OPC Data Access Server

2.9

Error Codes for the Ovation OPC Data Access Server OPC sends Fault Code information and Server status information to an Ovation Error Log file displayed in the General Message Display and the Drop Details diagram on an Ovation Station. Refer to the Fault Information Tool for additional information. The Ovation Fault Information Tool is a useful maintenance tool and is available for the Ovation system. You can diagnose most Fault Codes by accessing the Ovation Fault Information Tool. To access the tool, log on to the Ovation/WDPF Users site, and click the Fault Information Tool in the left hand menu. Or, enter the following URL to log on to the Fault Information Tool directly: https://www.ovationusers.com/FIT/index.asp For help using the Ovation Fault Information Tool, click the Help button in the tool.

CON_016

17

2.10 Registry Entries

2.10 Registry Entries The Ovation OPC Data Access Server uses Microsoft services to communicate across the network. DCOM, (Distributed Common Object Model), and its associated security model is the underlying mechanism for an Ovation OPC Data Access Server and OPC Client to communicate. The Ovation OPC Data Access Server uses DCOM; therefore, relies heavily on a number of registry entries for correct configuration and operation. These values are set during program installation and should not be changed. You can re-register the Ovation OPC Data Access Server with DCOM and reset the registry values by running the program from a command line: C:\> c:\ovation\opc\programs\OvationOPC.exe /service Alternately, the Ovation OPC Data Access Server can be set up as a DCOM Server (not an NT service) by using the following command: C:\> c:\ovation\opc\programs\OvationOPC.exe /RegServer Similarly, you can remove the Ovation OPC Data Access Server from DCOM by running: C:\> c:\ovation\opc\programs\OvationOPC.exe /UnregServer The dynamic link library, OPCProxy.dll, is used to marshall interfaces for OPC clients and seamlessly transmit data over the network. This DLL is registered with DCOM during installation. You can re-register by running this program from a command line: C:\winnt\system32> regsvr32 OPCProxy.dll Note: The current directory must be the same as the actual location of the DLL. If this operation is successful, you should get a confirming message box. The dynamic link library, OPCDAAuto.dll, implements the automation interface. This allows the Ovation OPC Data Access Server to be used with Visual Basic, Visual Basic for Applications and Microsoft J++ (Java). This DLL is registered with DCOM during setup. You can re-register by running the program from a command line with this syntax: C:\winnt\system32> regsvr32 OPCDaAuto.dll Note: The current directory must be the same as the actual location of the DLL. If this operation is successful, you should get a confirming message box. The dynamic link library, OPCComn_ps.dll marshals interfaces for OPC Servers. This DLL is registered with DCOM during setup. You can re-register by running the program from a command line with this syntax: c:\winnt\system32> rgsvr32 OPCComn_ps.dll Note: The current directory must be the same as the actual location of the DLL. If this operation is successful, you should get a confirming message box.

18

CON_016

2.11 Browsing for Ovation OPC Data Access Servers on a Remote Network The program OPCEnum.exe is used to provide Ovation OPC Data Access Server information to remote machines. It is registered with DCOM during installation. You can re-register by running the program from a command line with this syntax: c:\winnt\system32> OPCEnum -service

2.11 Browsing for Ovation OPC Data Access Servers on a Remote Network You can browse the list of Ovation OPC Data Access Servers on a remote network by adding the following information to the registry on the client’s machine to make the remote OPC Server available on the local client machine. When this method of registration is used, the connection to the remote Server is done as if the Server were located on the local client machine. If an entry field appears on the local client machine asking for the name of the remote machine, leave the field empty. Place the following information into a file with a .reg extension and import it into the registry. Replace the last line of the file with the appropriate information in order for the file to work properly. REGEDIT4 [HKEY_CLASSES_ROOT\Ovation.OPC] @="Ovation OPCServer Class" [HKEY_CLASSES_ROOT\Ovation.OPC\CLSID] @="{4525AD4E-17BD-11d5-8183-0050046FAB6D}" [HKEY_CLASSES_ROOT\Ovation.OPC\CurVer] @="Ovation.OPC.4" [HKEY_CLASSES_ROOT\Ovation.OPC\OPC] [HKEY_CLASSES_ROOT\Ovation.OPC\OPC\Vendor] @="Emerson Process Management" [HKEY_CLASSES_ROOT\Ovation.OPC.4] @="Ovation OPCServer Class" [HKEY_CLASSES_ROOT\Ovation.OPC.3\CLSID] @="{4525AD4E-17BD-11d5-8183-0050046FAB6D}" [HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-8183-0050046FAB6D}] @="Ovation OPCServer Class" "AppID"="{791B48EF-1732-11D5-8183-0050046FAB6D}" [HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-81830050046FAB6D}\Implemented Categories] [HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-81830050046FAB6D}\Implemented Categories\{63D5F430-CFE4-11D1-B2C80060083BA1FB}] [HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-81830050046FAB6D}\Implemented Categories\{63D5F432-CFE4-11D1-B2C80060083BA1FB}] [HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-81830050046FAB6D}\ProgID] @="Ovation.OPC.4"

CON_016

19

2.12 Visual Basic automation interface for OPC Client

[HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-81830050046FAB6D}\Programmable] [HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-81830050046FAB6D}\TypeLib] @="{791B48EE-1732-11D5-8183-0050046FAB6D}" [HKEY_CLASSES_ROOT\CLSID\{4525AD4E-17BD-11d5-81830050046FAB6D}\VersionIndependentProgID] @="Ovation.OPC" [HKEY_CLASSES_ROOT\AppID\{791B48EF-1732-11D5-8183-0050046FAB6D}] @="OvationOPC Service" "RemoteServerName"=""

2.12 Visual Basic automation interface for OPC Client You can use Microsoft ® Visual Basic or Visual Basic for Applications and the automation interface to Ovation OPC Data Access Server to provide specialized programming tasks. Note: This section assumes the reader is familiar with Visual Basic programming.

2.12.1 Visual Basic example The brief coding example below connects to the Ovation OPC Data Access Server, adds a group, adds items, reads values and writes values. 1. Access the Visual Basic Program or the Visual Basic for Applications environment for a Microsoft Office Product. Add the OPC Automation Library 2.0 (opcdaauto.dll) to the list of references using the Tools\References menu item. 2. Copy the example subroutine below into a module. Execute the code from the debugger.

20

CON_016

2.12 Visual Basic automation interface for OPC Client Option Explicit ' ' ' ' '

this is an example of the use of Ovation OPC this example must be modified to be used by an Ovation system. The correct machine name and correct point names must be inserted in the appropriate variables

Sub OPCExample() Dim myOPCServer As OPCServer Dim myOPCBrowser As OPCBrowser Dim myOPCGroup As OPCGroup Dim myOPCItem(3) As OPCItem Dim OPCItemTemp As OPCItem Dim Dim Dim Dim

myServerName As String myNodeName As String myGroupName As String myItemName(3) As String

Dim i As Integer Dim Dim Dim Dim Dim Dim

lCount As Long lClientHandle As Long myClientHandles(3) As Long myServerHandles() As Long myErrors() As Long lReturn As Long

Dim myValue As Variant Dim myQuality As Variant Dim myTimeStamp As Variant ' ' Modify these as needed for a specific ' OPC Server/group/item ' myServerName = "Ovation.OPC.4" myNodeName = "Drop200" myGroupName = "Group" ' ' ' ' ' ' ' '

This name must definitely be modified to match a legal name on the OvationHighway The syntax for a fully qualified Ovation Item is: [email protected] ex. [email protected]

' Create a new server Set myOPCServer = New OPCServer ' Connect to the Ovation OPC Server On Error GoTo NoConnect Call myOPCServer.Connect(myServerName, myNodeName)

CON_016

21

2.12 Visual Basic automation interface for OPC Client Set myOPCBrowser = myOPCServer.CreateBrowser ' Add a group On Error GoTo NoGroup Set myOPCGroup = myOPCServer.OPCGroups.Add(myGroupName) ' ' modify some group values ' myOPCGroup.UpdateRate = 500 myGroupName = "Group2" myOPCGroup.Name = myGroupName ' ' add 3 OPC Items ' On Error GoTo NoAddItem ' initialize data myItemName(1) = "la006-122" myItemName(2) = "da006-122" myItemName(3) = "ld006-122" myClientHandles(1) = 2500 myClientHandles(2) = 2501 myClientHandles(3) = 2502 Call myOPCGroup.OPCItems.AddItems(3, _ myItemName, _ myClientHandles, _ myServerHandles, _ myErrors) ' read the data For Each OPCItemTemp In myOPCGroup.OPCItems Call OPCItemTemp.Read(0, myValue, myQuality, myTimeStamp) Debug.Print OPCItemTemp.ItemID & " " & myValue & " quality " & myQuality & " time " & myTimeStamp Next OPCItemTemp ' write the data On Error GoTo NoWrite Set OPCItemTemp = myOPCGroup.OPCItems.GetOPCItem(myServerHandles(1)) OPCItemTemp.Write (OPCItemTemp.Value + 1#) Set OPCItemTemp = myOPCGroup.OPCItems.GetOPCItem(myServerHandles(2)) OPCItemTemp.Write (OPCItemTemp.Value + 1#) Set OPCItemTemp = myOPCGroup.OPCItems.GetOPCItem(myServerHandles(3)) OPCItemTemp.Write (Not OPCItemTemp.Value) For Each OPCItemTemp In myOPCGroup.OPCItems OPCItemTemp.Write (OPCItemTemp.Value + 1) Call OPCItemTemp.Read(0, myValue, myQuality, myTimeStamp) Debug.Print OPCItemTemp.ItemID & " " & myValue & " quality " & myQuality & " time " & myTimeStamp Next OPCItemTemp ' ' Leave with the quiet confidence of a job well done '

22

CON_016

2.12 Visual Basic automation interface for OPC Client

On Error GoTo RemoveItemsFault lCount = myOPCGroup.OPCItems.Count Call myOPCGroup.OPCItems.Remove(lCount, myServerHandles, myErrors) myOPCServer.OPCGroups.Remove (myGroupName) myOPCServer.Disconnect Exit Sub NoWrite: Debug.Print "Write Item " & " returns error; " & Err.Number & "; (" & Err.Description & "); """ Resume Next NoAddItem: Debug.Print "Add Item " & myOPCItem(i).ItemID & " returns error " & Err.Number & " (" & Err.Description & ")" Resume Next RemoveItemsFault: Debug.Print "Remove Items returns error " & Err.Number & " (" & Err.Description & ")" myOPCServer.OPCGroups.Remove (myGroupName) myOPCServer.Disconnect Exit Sub NoGroup: MsgBox "Can't add group " & myGroupName myOPCServer.Disconnect Exit Sub NoConnect: ' fail to connect MsgBox "Connect to " & myNodeName & " Server " & myServerName Exit Sub End Sub

CON_016

23

S

E C T I O N

3

Ovation OPC Alarm and Events Server

IN THIS SECTION What are Alarms and Events? .......................................................................................... 25 What is the Ovation OPC Alarms and Events Server?..................................................... 27 Licensing the Alarms and Events Server .......................................................................... 27 System Requirements for the Alarms and Events Server ................................................ 28 eDB Configuration Information.......................................................................................... 28 To Install OPC Alarms and Events Server........................................................................ 28 To Configure OPC Alarm Client and Event Subscription.................................................. 29 Ovation OPC Event Monitor Tool...................................................................................... 31

3.1

What are Alarms and Events? Alarms and events are indications or areas of the process requiring immediate attention. Alarms and events provide process information from various areas of the control system. An alarm is an abnormal condition; therefore, becomes a special case of a condition. An event is a detectable occurrence which is of significance to the OPC Event Server, the device it represents and its OPC Clients. A condition is a named state of the OPC Event Server or of one of its contained objects, which is of interest to its OPC Client. Events might or might not be associated with a condition. Alarms and Events can be defined in three categories:

Simple Events

Condition Events

Tracking Events

CON_016

25

3.1 What are Alarms and Events?

3.1.1 What are Simple Events? Simple events are all events other than condition-related or tracking-related events since simple events are not acknowledged. Simple events are used for several Ovation alarms that do not accept acknowledgement. Clients can filter on simple events. An example of a simple event is a component failure within the system or device represented by the OPC Event Server. For example, the Ovation OPC Alarms and Events Server use the following simple events to report the following items.

Operator Event Messages - The source of the message is the drop sending the message.

SOE or Sequence of Events messages - The source of the message is the point originating the messages.

COS or Change of State messages - The source of the message is the point that is changing state.

Simple events are also used to report errors encountered during the operation of the Ovation OPC Alarms and Events Server. The source of these event messages is:

System - For Error messages

3.1.2 What are Condition Events? Condition-related events are associated with OPC Conditions, and represent transitions into or out of the states represented by the OPCConditions and OPCSubConditions. An alarm is an abnormal condition; therefore, is a special case of a condition. A condition is a named state of the OPC Alarms and Events Server, or one of its contained objects, which is of interest to its OPC Clients. Condition definitions are Server specific. Conditions can be single or multi-state. A multi-state condition is one whose state encompasses multiple sub-states. A single state condition has only one sub-state of interest, therefore, has only one sub-condition associated with it.

3.1.3 What are Tracking Events? Tracking-related events represent occurrences involving the interaction of an OPC Client with a "target" object within the OPC Event Server. Tracking-related events have the same attributes as condition-related events plus an ActorID. An ActorID is the identifier of the OPC Client which initiated the action resulting in the tracking-related event. These values are Server specific.

26

CON_016

3.2 What is the Ovation OPC Alarms and Events Server?

3.1.4 What is Event Subscription? OPC Event Subscription provides an interface to allow the OPC Client to specify a filter. In addition, event subscriptions implement the standard DCOM Connection Point interfaces to provide the mechanism for notifying OPC Clients of event occurrences. The OPCEventSubscription object is the object that an OPC Event Server delivers to manage a single event subscription. Each subscription between a client and Server has only one filter; although, filters can include several criteria. Clients can implement multiple filters using multiple subscriptions, each with their own filter. When the subscription is established, a default filter is created equivalent to “no filtering” (that is, send all event notifications). The criteria for defining the scope of the filter is to eliminate the majority of events a client is not interested in, without having to be exhaustive. The primary reason for the filter is to reduce unnecessary communication overhead and to improve performance.

3.2

What is the Ovation OPC Alarms and Events Server? The Ovation OPC Alarms and Events Server is a software application tool. The Alarms and Events Server tool interprets and exports Ovation alarm and event information to a compatible OPC Alarms and Events Client, allowing for third-party software to receive, display, and respond to Ovation alarms and events. Through the use of the Alarms and Events Client, alarm information can be translated into a standard language that the OPC Server understands and can use for evaluation of each alarm and event message received.

3.3

Licensing the Alarms and Events Server OPC Alarms and Events Server licenses are supplied with each Ovation OPC Alarms and Events Server. A ten-day trial license is extended on each newly installed Ovation system. After the tenday period, the trial license becomes invalid and a new license is required to continue alarm and event functionality. If additional connections are necessary, additional licenses are also required. The OPC Alarms and Events Server also has the ability to generate SOE and Operator Event messages. This feature, by default, is turned off and requires a separate license to enable this feature.

3.3.1 SOE Sequence of Events Licenses SOE or Sequence of Events option allows you to monitor events and alarms occurring in a specific order. SOE information can be useful for system diagnosis. All 2.4 and later Ovation systems have SOE capability but require separate licenses to activate SOE functionality.

CON_016

27

3.4 System Requirements for the Alarms and Events Server

3.3.2 Operator Event Licenses The Operator Event option monitors the activities or actions by system users or operators. This function is useful to monitor operator actions to improve operator efficiency and accuracy. All 3.0 and later software releases of Ovation are loaded with the Operator Event option and need a separate license to activate this functionality.

3.4

System Requirements for the Alarms and Events Server Hardware Requirements: The hardware required to install the OPC Alarms and Events Server is a PC loaded with a Windows XP operating system. Software Requirements: The Ovation Alarm Event Server is intended to be loaded and run on a PC using a Microsoft Windows platform. All necessary Ovation Windows software must be loaded prior to installing the OPC Alarm Event Server. For information and instructions about loading Ovation Windows software, see the appropriate Ovation Software Installation manual.

3.5

eDB Configuration Information When using the Alarms and Events Server in conjunction with the Ovation eDB, there are a few considerations to take into account during configuration. A limit of two SOE (Sequence of Events) loggers can be used on any Ovation system at a time, therefore, redundant eDB SOE Scanners and OPC Alarms and Events Scanner can not be configured on the same network. The same drop cannot be used as both the Alarms and Events Server and:

eDB SOE scanner for SOE configuration.

eDB OpEvent scanner for OpEvent configuration.

Configuration of SOE and OpEvents is done through the Ovation Developer Studio. Configuration procedures and additional information on the Ovation eDB is found in section three of the eDB Historian User Guide.

3.6

To Install OPC Alarms and Events Server 1. Insert the OPC Alarms and Events Server CDROM into the CDROM drive.

28

CON_016

3.7 To Configure OPC Alarm Client and Event Subscription 2. Select the Start button and choose Run. The Run dialog box appears.

Figure 3: Run Dialog Box 3. In the Open field, enter E:/setup.exe and select OK. The Setup Welcome dialog box appears. Note: Ensure the CDROM drive is E. If it is not E, be sure to use the appropriate drive letter in the Run dialog box. 4. Close all other Open applications and select Next. The Software License Agreement dialog box appears. 5. Read and accept the software license agreement and select Next to continue. The Selection of License Manager Installation Information dialog box appears. 6. After accepting the licensing agreement, the Setup Types Installation dialog box appears. Two installation options are available to choose from. You can choose to perform a Complete installation or a Custom installation of the OPC Alarms and Events Server. Complete - Installs all features of the OPC Alarms and Events Server. Custom - Allows you to specify location and install separate modules of the OPC Alarms and Events Server. After you have made your selections click Next. 7. The Ready to Install progress window appears. Choose Install. 8. Installation of the OPC Alarms and Events Server begins. After installation is complete click Finish.

3.7

To Configure OPC Alarm Client and Event Subscription 1. Access the Ovation OPC Client Tool by selecting the following path: Start -> Ovation -> Ovation OPC Event Server -> OPC Client Tool 2. Select OPC Servers from the hierarchy on the left side of the Ovation OPC Client Tool.

CON_016

29

3.7 To Configure OPC Alarm Client and Event Subscription

3. Select Add Alarm/Event Server from the menu. The Server window appears.

Figure 4: Main Menu Selections 4. Select the Lookup button in the Server window to browse OPC Alarm and Event Servers. 5. Highlight the appropriate Server and select Ok to populate the Prog ID: and CLSID: fields. 6. Select Apply. Note: In the following figure, the window heading reads Ovation Alarm & Event Server. However, the heading name on the dialog window changes depending of the name entered into the Name box.

Figure 5: Ovation Alarm & Event Server Window

30

CON_016

3.8 Ovation OPC Event Monitor Tool

3.7.1 To Add or Configure an Event Subscription 1. Select the Add Event Subscription from the menu shown below.

Figure 6: Add Event Subscription main menu 2. The Subscription window appears. Select Apply in the Subscription dialog window to save your selection

3.8

Ovation OPC Event Monitor Tool The Ovation Event Monitor is a snap-in tool used to monitor the Ovation OPC Event Server and configure control.

CON_016

31


3.8.1 To access the Ovation OPC Event Server Main Window 1. Select: Start > Programs > Ovation > Ovation OPC Event Server > Event Server Monitor

Figure 7: Event Server Main Window 2. Right-click over any item in the Ovation OPC Event Monitor tree to access a menu, listing the following options:

Register as Service

Register as Server

View

New Window from Here

Refresh

Export List

Help

3.8.2 To Check the Ovation OPC Alarms and Events Server Status 1. Select Service/Server(local) from the OPC Event Monitor tree. 2. In the details pane of the main window, the current status displays.

32

CON_016

3.8 Ovation OPC Event Monitor Tool The following example illustrates an icon with a green light indicating that the Event Server is running. This example also displays the current status of the Event Server in the Status column.

Figure 8: Refresh and Select Service/Server(local) Node

3.8.3 To Change the Ovation OPC Alarms and Events Server from a Windows Service to COM Server 1. Open the Command prompt tool. 2. Type cd %WDPF_HOME%\opceventServer and press the Enter key. 3. Type ovationeventServer -unregServer and press the Enter key. 4. Type ovationeventServer -regServer and press the Enter key. OR 1. Right-click Service/Server(local) from the OPC Event Monitor tree. 2. Choose Register a Server.

3.8.4 To Change the Ovation OPC Alarms and Events Server from a COM Server to Windows Service 1. Open the Command Prompt tool. 2. Type cd %WDPF_HOME%\opceventServer and press the Enter key. 3. Type ovationeventServer -unregServer and press the Enter key. 4. Type ovationeventServer -service and press the Enter key. OR 1. Right-click Service/Server(local) from the tree. 2. Choose Register a Service.

CON_016

33


Note: When the Alarms and Events Server is configured as a Service, the Service automatically starts during start up.

3.8.5 To View or Configure OPC Alarms and Events Server Settings Selecting Properties from the Emerson OPC Event Server window displays a list of the Ovation Alarms and Events Server registry entries and are listed below:

Debug - Enables debug logging. Default: 0

UseAltLog - Sends logging information to the LogFile instead of the Ovation Error Log.

LogFile - Alternate Log File name. Default: \EventServer.log. This file is used only when UseAltLog is set.

SeverityMaxLevel - Logging severity levels.

UseAltItemSyntax - Alternate Item syntax. Default is 0. If set to 1, the following is used: Example: ¾ PointName$Unit@NetworkName$Field%bit ¾ PointName$Unit@NetworkName$Field ¾ PointName$Unit@NetworkName ¾ PointName$Unit ¾ PointName ¾ PointName$Field ¾ PointName$Field%bit

OneTenthSecCounterAttempts - Number of attempts to obtain or retrieve Ovation alarm information. If the data is not available within the number of attempts, the System simple event is raised. Default: 5.

The bulleted items listed above display in the Event Server dialog box. Each selection has its own associated dialog box. For example, to access the Debug Properties window, select Debug from the window and the associated dialog box appears. Use the following procedure to access any of the items listed above: 1. Select Properties from the Emerson OPC Event Server window. 2. Make selections from the list of options displayed.

34

CON_016

3.8 Ovation OPC Event Monitor Tool The Debug option is selected in following example. The Debug Properties window appears.

Figure 9: Debug Properties Window Menu Options OPTION

DESCRIPTION

Debug

Sets debug properties.

OK

Accepts and saves the selections to the registry and closes the window.

Cancel

Cancels the selections and does not save them to registry.

Apply

Accepts and saves the selections to the registry and does not close the window.

3.8.6 To View OPC Client Connections 1. Select OPC Event Monitor from the Console Root Tree. 2. Choose OPC Client Connections from the tree.

CON_016

35


By selecting OPC Client Connections option, you can view individual client connections. The Client Connections associated attributes display in the detail pane of the main window.

Figure 10: OPC Client Connection

3.8.7 To View Ovation Alarms and Events Server Version, Start Time Information 1.

Select OPC Event Monitor from the tree.

2. Choose OPC Server Info. Selecting the OPC Server Info selection allows you to view the associated Server attributes and their associated values. OPC Server Information displays in the detail pane of the main window.

Figure 11: OPC Server Selection Properties Window

36

CON_016

S

E C T I O N

4

Ovation OPC Client Mapper

IN THIS SECTION What is the OPC Client Mapper? ...................................................................................... 37 Ovation OPC Client Map Service...................................................................................... 37 Ovation OPC Configuration Tool....................................................................................... 38 Ovation OPC Client Map Control Panel............................................................................ 38 Default installation and custom configurations of the Ovation OPC Client Mapper.......... 38 Operating system requirements ........................................................................................ 38 Configuring and customizing the OPC Client Mapper Server........................................... 40 Client Mapper data transfer............................................................................................... 43 Ovation OPC Client Mapper control panel........................................................................ 45 OPC redundancy manager ............................................................................................... 46 OPC redundancy configuration ......................................................................................... 47

4.1

What is the OPC Client Mapper? The Ovation OPC Client Map Service (OPC Mapper) is used to interface an Ovation system with any OPC Server. Ovation points can be mapped to OPC items to allow for the exchange of information. Using the OPC Client Mapper, data is read from an OPC Server and stored in Ovation point record fields. Data can also be sent from Ovation point record fields to the OPC Server, depending upon the configuration of the Server. (See Ovation Record Types Reference Manual.) This section describes the installation and operation of the Ovation OPC Client Mapper.

4.2

Ovation OPC Client Map Service The OPC Map Service is responsible for reading and writing information between the Ovation network and an OPC Server. The Ovation OPC Client Map configuration file defines the mapping of interest. The file is created using the Ovation OPC Mapper Configuration Tool. The Ovation OPC Client Map Service runs in the background as a Windows Service. The Service is started when the PC boots. Any user interaction is performed through the OPC Client Mapper control panel applet.

CON_016

37

4.3 Ovation OPC Configuration Tool

4.3

Ovation OPC Configuration Tool The Ovation OPC Mapper Configuration Tool is the main interface to the Ovation OPC Mapper. The Ovation OPC Mapper Configuration Tool is used to create and modify OPC Client Map Service configuration files. It can also operate as an OPC Client which can simultaneously connect to multiple OPC Servers to read and write values. The OPC Mapper Configuration Tool is described in OPC Configuration Tool (see page 49) and Right-click (Context) Menus (see page 54).

4.4

Ovation OPC Client Map Control Panel The Ovation OPC Client Map Control Panel is used to configure various parameters used by the Ovation OPC Client Map Service. The OPC Mapper Settings Control Panel applet is used for starting and stopping the OPC Mapper, setting its default configuration file, and setting other runtime parameters. This panel is described in Using the OPC Configuration Tool.

4.5

Default installation and custom configurations of the Ovation OPC Client Mapper The default installation establishes the Ovation OPC Client Mapper as a Windows service. In the default configuration, the Mapper starts when the Windows system starts, even before a user logs on to the computer. Note: In some situations, this might not be acceptable for your application. For example, if you want a third-party program to start before the Mapper starts, refer to Intellution’s iFIX OPC Server (see page 41). Under some circumstances, it might be necessary to change the OPC Client Mapper to a standalone application. A stand-alone application is one executed from a command line, Windows Explorer, or some other means. The following procedures describe converting between a Windows service and a stand-alone application.

4.6

Operating system requirements The Ovation OPC Client Mapper runs on both Windows and Solaris Ovation Systems. The Ovation OPC Client Mapper is intended to be loaded and run on a PC using a Microsoft Windows platform. All necessary Ovation Windows software must be loaded prior to installing the OPC Client Mapper. For information and instructions about loading Ovation Windows software, see the applicable Ovation Software Installation Manual.

4.6.1 To Install OPC Client Mapper from CDROM 1. Insert the OPC Client Mapper CDROM into the CDROM drive.

38

CON_016

4.6 Operating system requirements 2. Select the Start button and choose Run. The Run dialog box appears.

Figure 12: Run Dialog Box 3. In the Open field, enter E:/setup.exe and select OK. The Setup Welcome dialog box appears. Note: Ensure the CDROM drive is E. If it is not E, be sure to use the appropriate drive letter in the Run dialog box. 4. Close all other open applications and select Next. The Software License Agreement dialog box appears. 5. Read the software license agreement and select Yes to continue. The Selection of License Manager Installation Information dialog box appears. 6. Read and make a note of the information in the dialog box then determine which installation should be selected in the next dialog box. Note: For Windows applications: If you are installing the Client Mapper on an Ovation 2.x or later system, your system already contains a network License Server; therefore, select Client Installation in the next dialog box. Typically, the License Server resides on your Database Server. For Solaris applications: If this is the first OPC Client Mapper installation on the network, select Server Installation in the next dialog box. The License Server must be installed on only one machine. Install all licenses on this machine. The License Server resides on the machine where you first installed the Client Mapper application. For all additional OPC Client Mapper installations on the network, select Client Installation in the next dialog box. 7. After reading the information, select Next and the Choose from a Server or Client Installation dialog box appears.

CON_016

39

4.7 Configuring and customizing the OPC Client Mapper Server

If you select the Server Installation, proceed to Step 8. If you select the Client Installation, skip to Step 10. 8. If you select Server Installation, a Question dialog box appears prompting you to validate the choice of License Server. 9. Select No to return to the previous dialog box. Select Yes to accept the license Server. Skip to Step 11. 10. If you select Client Installation, the Enter Text dialog box appears. Enter the name of the drop acting as the license Server and select Next. The Redundancy Manager Installation dialog box appears. 11. If necessary, select Yes to Install an Ovation Redundancy Manager. Refer to OPC Redundancy Manager for additional information. After making a selection, the Choose Destination Location dialog box appears. 12. Select the Browse button to choose a destination folder in which to save the OPC application, or select Next to accept the default destination folder. The installation begins and the progress of the installation displays on the installation screen. 13. When the installation is complete, the Install Shield Wizard Complete dialog box appears. Select Finish to exit the setup process.

4.6.2 To Change the Client Mapper from a Windows Service to COM Server 1. Open the Command prompt tool. 2. Type cd %WDPF_HOME%\opcclientmap and press the Enter key. 3. Type opcclientmap -unregServer and press the Enter key. 4. Type opcclientmap -regServer and press the Enter key. The opcclientmap entry is then removed from the Services Control Panel applet.

4.6.3 To Change the Client Mapper from COM Server to Windows Service 1. Open the Command Prompt tool. 2. Type cd %WDPF_HOME%\opcclientmap and press the Enter key. 3. Type opcclientmap -unregServer and press the Enter key. 4. Type opcclientmap -service and press the Enter key. When the Client Mapper is configured as a service, the service automatically starts during start up. The opcclientmap entry is then placed back into the Services Control Panel and configured to automatically run on start up.

4.7

Configuring and customizing the OPC Client Mapper Server Specific OPC Servers can require a custom configuration of the OPC Client Mapper. The following procedures describe how to configure the mapper for two specific Servers. Other Servers typically require different configurations. Each application must be evaluated to determine the best method of setup.

40

CON_016


4.7.1 To configure Rovisys OPC90 Server 1. Open the Command Prompt tool. 2. Type dcomcnfg and press the Enter key. 3. On the Applications tab, double-click the OPC90 Server in the list. 4. Click the Identity tab and select This User radio button. 5. Enter a valid user name and password. This provides for starting the OPC Server by the OPC Mapper on reboot, and it also permits other OPC Clients to connect to the OPC Server without starting a new instance. Note: Only users with system administration access can perform this configuration.

4.7.2 To configure Intellution’s iFIX OPC server 1. Open the Command Prompt tool. 2. Type cd %WDPF_HOME%\opcclientmap and press the Enter key. 3. Type opcclientmap -unregServer and press the Enter key. 4. Type opcclientmap -regServer and press the Enter key. 5. From the iFIX Workspace window, double-click on System Configuration, OR Select the Start button, choose iFIX, then System Configuration. 6. In the iFIX System Configuration Tool, select Configure from the menu bar and choose Tasks. 7. At the top of the dialog in the Filename entry field, enter %WDPF_HOME%\opcclientmap\opcclientmap.exe, OR Click the Question Mark button, select the opcclientmap.exe program and choose OK. 8. In the iFIX System Configuration Tool, select Configure from the menu and choose Local Startup. 9. Select the Continue Running after Logoff and Start FIX at System Boot checkboxes. Note: This procedure causes iFIX to run as a Windows service. When the PC boots up, iFIX starts. iFIX then starts the OPC Client Mapper.

4.7.3 To configure your OPC system 1. Open the OPC Mapper Configuration Tool. 2. Right-click on the OPC Servers node in the Hierarchy Browser and select Add Data Access Server to add an OPC Server to the configuration. The Server Configuration window displays. See Server Configuration Window (see page 60) for more information. 3. Enter a name for the Server in the Name field and add an optional description in the Description field.

CON_016

41


4. In the Node field, enter the node where the Server exists. The node can be a host name or an IP address. If the Server is on the local node, this field can remain blank. 5. Select the Lookup button and the Browse OPC Servers dialog box appears.

Figure 13: Browse OPC Servers Dialog Box Note: In the Browse OPC Servers window shown above, the Version 2.0 Servers and Version 1.0 Servers options are not applicable for the OPC Alarms and Events Server. 6. The Browse OPC Servers dialog box lists the ProgIDs of the available OPC Servers on the chosen node. Choose the appropriate Server and select OK to commit the changes. Note: The changes are not saved to disk until the File->Save or File->Save As menu item is chosen in the OPC Mapper Configuration Tool. 7. To add a group to the Server, right-click on the newly added Server in the Hierarchy Browser and select Add Group. The Group Configuration window displays and a new group icon appears below the Server in the Hierarchy Browser. 8. Provide a user-friendly name for the group and an optional description. Fill in the remainder of the fields as needed. Refer to Group Configuration Window (see page 61) for more information about the fields in the Group Configuration window.

42

CON_016

4.8 Client Mapper data transfer 9. After the group has been configured, items can be added. In the Hierarchy Browser, rightclick on the newly added group and select Add Item. The Item Configuration window displays, and a new item icon appears below the group. The information in this window is used to establish a mapping between an OPC item and an Ovation point.

Figure 14: Item Configuration Window 10. Enter a name for the item in the Name field and a description in the Description field. Note: To browse the items available to the Server, right-click on the Server's icon in the Hierarchy Browser and select Connect. This should enable the Browse button in the Item Configuration window. 11. Fill in the remaining OPC related fields as needed. Refer to Monitor Items Window (see page 65) for more information about the fields in the Item Configuration window. 12. Save the configuration when complete. If the OPC Mapper is running it automatically detects the changed configuration file and reloads the file.

4.8

Client Mapper data transfer The Ovation OPC Client Mapper is used as an OPC client to enable transfer of data between Ovation and a generic OPC Server. Ovation point record values or individual fields can be mapped to items in the OPC Server. Typically, the Client Mapper executes as a Windows service and has no interaction with the Windows desktop. Interaction with the mapper is through the OPC Client Config tool, which is used to define the mapping used. Interaction is also through the OPC mapper settings control panel applet, which is used to start and stop the mapper as well as define several of its operating parameters.

CON_016

43

4.8 Client Mapper data transfer

4.8.1 Operation of OPC Client Mapper When the OPC Client Mapper starts, it reads the Windows registry at: HKEY_LOCAL_MACHINE\SOFTWARE\Westinghouse\Ovation OPC Mapper

It searches for the string value CFGFile. If the string value is present, that entry defines the configuration file to be used. If the string value is not present, the default file is used: %WDPF_HOME%\OPCClientmap\OPCclientmap.cfg The configuration file contains the Servers that are to be connected and the groups and items to be defined within those Servers. After OPC Client Mapper connects to the Server, it defines the specified OPC groups and adds the items to those groups. You can specify data transfer within the OPC Client Mapper to occur in three ways:

Points defined in the configuration as OPC to Ovation are only received from the OPC Server. Upon startup, the mapper performs an initial read of the item to get an initial value. After the initial read, the Server is responsible for sending any changes in the value of the item to the Client Mapper. In addition, if a forced rate value is defined in the OPC group configuration, the Client Mapper performs a read of the values at that frequency.

Data points that are defined as Ovation to OPC are not read from the OPC Server, but instead are written from Ovation values to the OPC Server. These values also operate in an exception based manner. The Client Mapper sends an initial value to the OPC Server when it first starts. After the initial value is sent, the Client Mapper monitors the value of the data, when the value changes, it sends the new value to the OPC Server. Ovation to OPC values also use the forced rate value, sending a write of the value at the forced rate frequency (if defined) to the OPC Server.

Data items can also be marked as both directions. This is a special case. When the Client Mapper starts, it performs an initial read of these values from the OPC Server, but it does not perform an initial write. The Client Mapper accepts change notices from the OPC Server and updates the value of the Ovation value accordingly. It also monitors the value of the Ovation point record field. If a change of the value is initiated in Ovation, a write of the new value to the OPC Server is then performed. Changes resulting from an update from the OPC Server do not result in the Client Mapper performing a write of that value. The forced rate operation, with regard to both direction type values, is to read from the OPC Server and not to perform writes. The only time a write needs to be performed is if a change in value is detected as having originating from Ovation.

The Client Mapper continually monitors the configuration file. At a period specified in the OPC mapper settings control panel applet, the Client Mapper checks if the configuration file has changed. If the configuration file has changed, it clears the old configuration, deletes any existing items and groups, disconnects from any Servers, and reads in the new configuration. Notice that changing the configuration online causes the data transfer through the Client Mapper to stop for a short period of time.

44

CON_016

4.9 Ovation OPC Client Mapper control panel

4.9

Ovation OPC Client Mapper control panel The Ovation OPC Client Mapper control panel is used to configure the parameters used by the Ovation OPC Client Mapper Service, and to start or stop the Client Mapper Service.

4.9.1 To Access the OPC Client Mapper control panel 1. Select Start > Settings > Control Panel > OPC Mapper Settings OR Start > Programs > Ovation > Ovation OPC Mapper >OPC Mapper Settings 2. The OPC Client (Control Panel) Mapper Properties window appears. Make the desired changes.

Figure 15: Ovation Client Mapper properties The following table describes the fields in the OPC Client Mapper Control Panel: Ovation OPC Client Mapper Properties (Control Panel) fields FIELD/BUTTON

DESCRIPTION

Config File

The Ovation OPC Client Map configuration file that the Ovation OPC Client Map Service loads upon startup. The Ovation OPC Mapper Configuration Tool also initially loads this file upon startup.

File Read Period

The time period (in seconds) when the Ovation OPC Client Map Service checks the configuration file for changes. If changes are detected, the mapper reloads the configuration file with the new information.

Scan Rate

The time period (in milliseconds) when the Ovation OPC Client Map Service reads Ovation values for items configured to transfer data in the Ovation to OPC direction (this includes those configured for both directions).

OPC Server Status Rate

The time period (in seconds) when the Ovation OPC Client Map Service checks each Server to verify the connection is still communicating.

CON_016

45

4.10 OPC redundancy manager

FIELD/BUTTON

DESCRIPTION

Start/Stop

This button starts or stops the Ovation OPC Client Map Service. A green light indicates that the service is running. A red light indicates that it is stopped. A yellow light indicates that it is in transition. You must have system administrator access.

Force Fault Drop [Redundant Drops]

Forces the drop (if in control) to go into backup/fail mode when the service is stopped or the machine is shutdown or rebooted.

Multi-Threaded OPC Server

This field is set to 1 for Multi-Threaded OPC Server (if required). The default setting is set to zero. The recommended setting is zero.

OK

This button accepts and saves all changes to the registry and closes the window.

Cancel

Closes the window without saving any changes.

Apply

This button accepts and saves all changes to the registry but does not close the window. It is only enabled if changes have been made to the configuration.

Help

Provides on-line help.

4.10 OPC redundancy manager The OPC Redundancy Manager is used with redundant Ovation Windows Stations running the OPC Client software. If the application is not being installed in a redundant Windows Station situation, do not install the Redundancy Manager. Ovation workstations can be configured to be redundant. One of the workstations performs control while the other acts as a backup. If the one in control fails, is shut down, or has some problem where it no longer functions as an Ovation workstation, the backup detects this and takes control. It is also possible for a software module inside the workstation to forcibly fail the workstation, if circumstances warrant. The Ovation Redundancy Manager can be used to monitor a station’s connection to an OPC Server. The Redundancy Manager connects to an OPC Server, adds a pre-defined set of items, and monitors the connection. If the connection fails completely (determined by all the items having bad OPC quality), then the Server assumes the OPC connection has become unusable and fails the station.

46

CON_016

4.11 OPC redundancy configuration

4.11 OPC redundancy configuration The Redundancy Manager is configured using the Ovation OPC Client Configuration Tool. No Ovation points need to be defined, just a set of OPC items. There should be sufficient items defined to determine positively that the OPC connection has failed. Once the Redundancy Manager installation is selected, a default configuration file, such as Redundant.cfg, is copied into OPC Client map directory. The registry entry which specifies the redundancy configuration file is: HKEY_LOCAL_MACHINE\SOFTWARE\WESTINGHOUSE\Ovation OPC Mapper\CFGRedundFile The Ovation OPC Redundancy Manager looks to this entry for the name of the configuration file. You must open this file and specify the pre-defined OPC items to check the bad qualities. The configuration file needs to be copied on both of the redundant drops since identical redundancy checking conditions are required. Also, you must copy the OPCclientmap.cfg file to both drops. Note: If you need another configuration filename, modify this entry and always specify the complete path. If you choose redundancy and have not configured the redundant.cfg file the redundant process starts and stops automatically. In the event that Redundancy Manager Installation is selected, Setup.exe puts the Redundancy Manager executable’s complete path in another registry entry, CFGProcessList. This entry helps the OPC Client Map service spawn the list of processes specified in this variable, which is delimited by a semicolon (;) or comma (,). Be sure to specify the complete path. Note: By default, setup.exe puts only the OvationOPCRedundancy.exe executable in the CFGProcess List registry entry. If you want to spawn another process, either append or modify the list delimited by either semicolon (;) or comma (,). OPC Client Mapper service reads this entry and spawns all the processes specified in this variable. If Redundancy Manager installation is not selected, the CFGProcessList remains empty. If you do not need the Redundancy Manager, manually remove the value from the CFGProcessList entry or uninstall and reinstall the OPC Client Mapper and be sure to select the Redundancy option in the Redundancy Manager, Installation dialog box during setup. Note: Always keep a backup copy of OPCclientmap.cfg and redundant.cfg file so that these files can be reused after reinstalling the software.

CON_016

47

S

E C T I O N

5

Ovation OPC Client/Configuration tools

IN THIS SECTION What is the OPC Client/Configuration tool........................................................................ 49 OPC interface functions .................................................................................................... 52 Right-click (context) menus............................................................................................... 54 Shortcut keys..................................................................................................................... 58 Preferences ....................................................................................................................... 59 OPC Interface windows..................................................................................................... 60 Dialog Boxes for OPC Tools ............................................................................................. 66

5.1

What is the OPC Client/Configuration tool The Ovation OPC Client/Configuration tool is used to create and modify configuration files. The Client/Configuration tool can also operate as an OPC Client, simultaneously connecting to multiple OPC Servers. The Ovation OPC Client Mapper Service (OPC Mapper) interfaces Ovation systems with any OPC Server, allowing for the exchange of information by mapping Ovation points to OPC items. The OPC Mapper is responsible for reading and writing information between the Ovation network and an OPC Server. The Ovation OPC Client Mapper Configuration file defines the mapping of interest. Note: Configuration files are created in Unicode.

5.1.1 To start the OPC Client/Configuration tool Select Start > Programs > Ovation Windows > \\ > OPC Config Tool. Installed OPC Packages are the Ovation OPC Data Access Server, Ovation OPC Event Server, or Ovation OPC Mapper. The OPC Client/Configuration tool main window appears. Note: By default, the file specified by the following registry entry is loaded if OPC Client Mapper software is installed. HKEY_LOCAL_MACHINE\SOFTWARE\Westinghouse\Ovation OPC Mapper\CFGFile Initially, the opcclientmap.cfg file located in %WDPF_HOME%/ OPCClientmap is specified.

CON_016

49

5.1 What is the OPC Client/Configuration tool

5.1.2 OPC Configuration tool main window The following illustrations display the OPC Client/Configuration Tool main windows:

Figure 16: OPC Configuration Main Window The main window is comprised of the following:

50

Menu bar

Toolbar

Hierarchy browser

View window

Status bar

CON_016

5.1 What is the OPC Client/Configuration tool

5.1.3 OPC Client tool main window The OPC Client tool main window is shown below:

Figure 17: OPC Client Tool Main Window The following icons are associated with the OPC Client/Configuration Tool Main Window. ICON

DESCRIPTION OPC Servers Root Level icon. OPC Alarms and Events Server icon. OPC Alarms and Events Subscription icon. OPC Data Access Server icon. OPC Data Access Group icon. OPC Data Access Item icon.

CON_016

51

5.2 OPC interface functions

5.2

OPC interface functions The following toobars help you navigate the OPC Client/Configuration tools.

5.2.1 Menu Bar The Menu bar is located across the top of the OPC Client/Configuration Tool. The options on the Menu bar are dependent upon the item opened in the View window. A list of all possible Menu bar options is shown below:

File

Edit

View

Servers

Subscription - Applicable for the OPC Alarms and Events Server.

Groups - Applicable for the OPC Data Access Server.

Items - Applicable for the OPC Data Access Server.

Window

Help

5.2.2 Toolbar The Toolbar appears under the Menu bar. The position of the Menu bar can be changed if desired. Refer to the following table for explanations of the toolbar buttons. Toolbar buttons BUTTON

52

TITLE

DESCRIPTION

New

Creates a new configuration.

Open

Opens a configuration previously saved.

Save

Saves the current configuration.

Cut

Cuts selected text to the clipboard.

Copy

Copies selected text to the clipboard.

Paste

Pastes clipboard contents to the selected field.

Add

Adds a new Server if a Server is active, adds a new group if a group is active, adds a new item if an item is active, adds a new subscription if a subscription is active.

Previous

Displays the previous Server if a Server is active. Displays the previous group if a group is active. Displays the previous item if an item is active. Displays the previous subscription if a subscription is active.

Next

Displays the next Server if a Server is currently active. Displays the next group if a group is currently active. Displays the next item if an item is currently active. Displays the next subscription if a subscription is active.

CON_016

5.2 OPC interface functions

BUTTON

TITLE

DESCRIPTION

Find

Locates defined text in a Server, group, subscription, or item display.

5.2.3 Hierarchy browser The Hierarchy Browser initially appears on the left side of the main window. Refer to the Main Window (see page 50). This window displays a tree structure containing the configuration in the following levels (from top to bottom):

Top level = Root Level (OPC Servers).

Server Level.

Subscription Level - Applicable only for the OPC Alarms and Events Server.

Group Level - Applicable for the OPC Data Access Server.

Item Level - Applicable for the OPC Data Access Server.

The Hierarchy Browser can be re-positioned by moving the pointer over the top border of the Browser window, left-click and drag the window to the desired location. The Browser window can be docked on either the left or right sides of the main window, and it can float unattached to the main window. The Browser window can also be resized. When docked, drag the left or right side of the Browser window to the desired size. When it is floating, all four sides as well as all four corners can be dragged to resize the window.

CON_016

53

5.3 Right-click (context) menus

5.2.4 Tree structure The tree structure displays icons at four different levels:

Root Level - The topmost level. There is always a single node at this level. This node is the parent of all of the OPC Servers in the configuration.

OPC Servers Level - Multiple OPC Servers can exist in a configuration and act independently of one another (for example, some might be connected, others might not be connected). Management of OPC connection information is maintained at this level.

OPC Group or OPC Subscription Object Level - The OPC Subscription object is the second level for the OPC Alarms and Events Server. The Group object is the second level for the OPC Data Access Servers. Management of OPC Group configuration information, such as update period and deadband is conducted at this level.

OPC Item Level - The lowest level in the tree structure. Item information such as Item IDs and Ovation Mapping information is maintained at this level.

The Server icons, Group icons, Item icons, and Subscription icons can be displayed in three different colors:

A Red icon indicates the object is not connected with an OPC Server.

A Yellow icon indicates the Group, Item, or Subscription is inactive.

A Green icon indicates the object is connected.

Selecting the Delete key removes the currently selected object in the tree. A prompt appears confirming this operation before proceeding. If a view has unapplied changes, then an asterisk is displayed at the end of its corresponding icon's label. If the configuration has changes which have not been saved to a file, then an asterisk is displayed next to the Root levels label. Note: The available menu selections depends on the OPC Server selections.

5.2.5 View window The View window displays individual dialog boxes for Server, Group, Subscription, and Item configuration. Refer to OPC Interface Windows (see page 60) for more information about the View windows.

5.2.6 Status bar The Status bar appears at the bottom of the window and displays helpful information as well as the state of the Caps Lock and Num Lock keys.

5.3

Right-click (context) menus Right-click while over any icon or label in the Hierarchy Browser to display a menu for that object. The right-click menu is also known as a Context menu because the components of the menu directly relate to the object on which you clicked.

54

CON_016


5.3.1 Root context menu Right-click on OPC Servers and a Root menu appears providing options for Server actions. The following menu options are available: Root menu options OPTION

DESCRIPTION

Add Data Access Server

Creates a new OPC Data Access Server object and initializes it with a default name. The Server Configuration window for the new Server is automatically opened.

Add Alarm/Event Server

Creates a new OPC Alarms & Events Server object and initializes it with a default name. The Server Configuration window for the new Server automatically opens.

Remove All Servers Removes all Servers from the configuration. You are prompted to confirm the operation before proceeding. Sort

Sorts the Servers by name.

Connect All

Attempts to connect all configured Server objects to their OPC Servers. This menu item is only available if at least one of the Servers is not connected.

Disconnect All

Disconnects all connected Server objects from their OPC Servers. This menu item is only available if at least one of the Servers is connected.

Cut

Not enabled at this level.

Copy

Not enabled at this level.

Paste

Pastes a Server object that is currently on the clipboard.

5.3.2 Server context menu Right-click the Server icon in the tree structure to display a Server Context menu. The following menu options are available: Server menu options OPTION

DESCRIPTION

Configure Server

Opens the Server Configuration window for the selected Server.

Remove Server

Removes the selected Server from the configuration. You are prompted to confirm the operation before proceeding.

Add Group

Creates a new group object, initializes it with a default name, and adds it to the selected Server. The Group Configuration window for the new group is automatically opened.

Remove All Groups Removes all child groups from the selected Server. You are prompted to confirm the operation before proceeding. Sort

Sorts the child groups of the selected Server by name.

Connect (Disconnect)

Attempts to connect to the selected Server. If the Server is already connected, this menu item's label is changed to Disconnect.

CON_016

55


OPTION

DESCRIPTION

Display Server State Displays the Server State dialog for the selected Server. This menu item is only available if the selected Server is connected. Cut

Cuts the current Server object and places it on the clipboard.

Copy

Copies the current Server object and places it on the clipboard.

Paste

Pastes either a Server or Group object from the clipboard.

Add Event Subscription

This selection adds an Event Subscription.

5.3.3 Group context menu Right-click the group icon in the tree structure to display a Group Context menu. The following menu options are available: Group menu options OPTION

DESCRIPTION

Configure Group

Opens the Group Configuration window for the selected group.

Remove Group

Removes the selected group from the configuration. You are prompted to confirm the operation before proceeding.

Add Item

Creates a new item object, initializes it with a default name, and adds it to the selected group. The Item Configuration window for the new item is opens automatically.

Add Multiple Item

Creates multiple items.

Generate Items

Displays the Generate Item window.

Remove All Items

Removes all child items from the selected group. You are prompted to confirm the operation before proceeding.

Sort

Sorts the child items of the selected group by name.

Monitor Items

Displays the Item Monitor window. This menu item is only available if the group's Server is connected.

Display Group State Displays the Group State dialog for the selected group. This menu item is only available if the group's Server is connected.

56

Read Items

Forces a read of all items in the group. The I/O type used is determined by the I/O Type parameter in the Group Configuration window. Refer to the Group Configuration Window (see page 61). This menu is only available if the group's Server is connected and the group has child items.

Cut

Cuts current Group object and places it on the clipboard.

Copy

Copies current Group object and places it on the clipboard.

Paste

Pastes either Group or Item object from the clipboard.

CON_016


5.3.4 Item context menu Right-click over an Item icon in the Hierarchy Browser Tree to display the Item Context menu. The following menu options are available: Item menu options OPTION

DESCRIPTION

Configure Item

Opens the Item Configuration window for the selected group.

Remove Item

Removes the selected item from the configuration. You are prompted to confirm the operation before proceeding.

Display Item State

Displays the Item State dialog for the selected item. This menu item is only available if the item's Server is connected.

Display Item Properties

Displays the Item Properties Dialog for the selected item. This menu item is only available if the item's Server is connected.

Async Read

Forces an asynchronous read of the selected item. During an asynchronous read, the client does not wait for the read operation to complete before continuing. This menu item is only available if the item's Server is connected.

Sync Read

Forces a synchronous read of the selected item. During a synchronous read, the client waits for the read operation to complete before continuing. This menu item is only available if the item's Server is connected.

Write

Displays the Write OPC Value dialog for the selected item. This menu item is only available if the item's Server is connected.

Cut

Cuts current Item object and places it on the clipboard.

Copy

Copies current Item object and places it on the clipboard.

Paste

Pastes Item object from the clipboard.

5.3.5 Subscription context menu Right-click over a Subscription Icon in the Hierarchy Browser Tree to display the Subscription Context menu. The following menu options are available: Subscription context menu options OPTION

DESCRIPTION

Configure Subscription

Opens Subscription Configuration for the selected subscription.

Remove Subscription

Removes the current subscription selected. A prompt appears asking if you are sure you want to remove the selected subscription.

Configure Filters

Opens the Subscription Filters dialog box.

Select Attributes

Displays selected attributes in the Subscription Select Attributes dialog box.

Display Subscription Displays the state of the current subscription in the Display Subscription State dialog State box.

CON_016

57

5.4 Shortcut keys

5.4

OPTION

DESCRIPTION

Browse Categories

Displays the Browse Categories dialog box.

Monitor Events

Displays the Monitor Events window.

Refresh

From each event subscription object, sends the current state of all conditions which are active, or which are inactive but unacknowledged.

Cancel Refresh

Cancels the Refresh selection.

Clear

Clears all selections.

Shortcut keys The following shortcut keys are available within the application: Item menu options

58

SHORTCUT KEYS

DESCRIPTION

Ctrl+N

New configuration

Ctrl+O

Opens a configuration

Ctrl+S

Saves the current configuration

Ctrl+Z

Undo

Ctrl+X

Cut

Ctrl+C

Copy

Ctrl+F

Find

Ctrl+P

Paste

Ctrl+A

Adds a new Server if a Server is currently active. Adds a new group if a group is currently active. Adds a new item if an item is currently active.

Ctrl+Up Arrow

Displays the previous Server if a Server is currently active. Displays the previous group if a group is currently active. Displays the previous item if an item is currently active. If a subscription is active, this action displays the previous subscription.

Ctrl+Down Arrow

Displays the next Server if a Server is currently active. Displays the next group if a group is currently active. Displays the next item if an item is currently active. If a subscription is active, this action displays the next subscription.

CON_016

5.5 Preferences

5.5

Preferences Choose Edit from the Configuration Tool main window to display a drop-down menu listing various options. Choose Preferences to display the following window.

Figure 18: Preferences Window Within the Preferences window are two sections:

Data Server Preferences - Used for the OPC Client Mapper and OPC Client. Selecting the Data Server Preferences allows you to automatically set item names to be the item ID when browsing. An item name is automatically assigned when this selection is set. When this option is not selected, the program applies a default name.

Event Server Preferences - Preferences allow you to choose background and foreground coloring for Alarms and Events. These colors are applied using standard Microsoft tools. After choosing the desired colors, they are displayed in the Monitor Events window. Based on severity level, different colors represent different levels of severity. This feature is not applicable for the OPC Client Mapper. Also defined in this window is the number of attribute columns displayed in the Monitor Events window. In this example 10 columns are selected in the Max. Number of Event Attrs: dialog box; therefore, ten attribute columns are applied to the table in the Monitor Events window.

CON_016

59

5.6 OPC Interface windows

5.6

OPC Interface windows The following windows appear as you navigate the OPC Client/Configuration tools.

5.6.1 Server configuration window You must configure the OPC Server to define OPC Server parameters used during local and remote connections. To display the Server Configuration window: 1. Select a Server icon in the Hierarchy Browser and either double-click or right-click to display the Server Context menu. 2. Choose the Configure Server option.

Figure 19: Server Configuration Window The following table describes the fields and buttons in the Server Configuration window. Server configuration fields

60

FIELD/BUTTON

DESCRIPTION

Name

A user-defined name which describes the OPC Server. Appears in the Hierarchy Browser next to the corresponding Server icon.

Description

An optional description which is useful in identifying the Server.

Node

The host name or IP address of the computer where the OPC Server resides. If blank, the local host is assumed.

Prog ID

The Prog ID of the OPC Server. This value is modified by successfully completing the Lookup operation.

CLSID

The CLSID of the OPC Server. This value is modified by successfully completing the Lookup operation.

CON_016


FIELD/BUTTON

DESCRIPTION

Lookup

Displays the Browse OPC Servers dialog. This button is only enabled when the Server is not connected. Successful completion of the Browse OPC Servers dialog fills in values for the Prog ID and CLSID fields.

Connect/ Disconnect

Attempts to connect to the specified OPC Server. If the Server is already connected, this button disconnects from the OPC Server.

OK

Commits all of the changes to memory and closes the window.

Apply

Commits all of the changes to memory but does not close the window.

Revert

Restores the configuration to the state it was in at the time it was opened or the most recent Apply.

Close

Closes the window without committing the changes to memory. If changes exist, you are prompted to commit the changes.

5.6.2 Group configuration window The Group Configuration window defines OPC Group parameters. To display the Group Configuration window: 1. Select a Group icon in the Hierarchy Browser and double-click or right-click to display the Group Context menu. 2. Choose the Configure Group option. The Group Config window appears.

Figure 20: Group Configuration Window

CON_016

61


The following table describes the fields and buttons in the Group Configuration window. Group configuration fields OPTION

DESCRIPTION

Name

A user defined name which describes the OPC Group. This name appears in the Hierarchy Browser next to the corresponding Group icon.

Description

An optional description which is useful in identifying the group.

Update Rate

The fastest time period in which data changes, in milliseconds, is sent from the OPC Server. This is a requested rate. The Server operates in an implementation specific manner. The actual update rate can be determined by displaying the Group State dialog when connected. Entering a 0 in this field indicates the Server should use the fastest practical rate.

Forced Rate

The time period in milliseconds in which all values are forcefully updated regardless whether they have changed. This parameter is only used by the OPC Client Map Service.

Deadband

The percent change in an item which causes the OPC Server to send change notifications.

Time Bias

The initial time bias for the group in minutes.

Locale ID

The language to be used by the OPC Server (if supported).

Data Source

The desired source of the input data. The choices are Cache or Device. Cache requests that the data be read from the OPC Server's cache (if available) rather than forcing a read from the device.

I/O Type

The type of I/O used in group-wide operations (such as Read Items). The choices are Synchronous and Asynchronous. If Synchronous is specified, the application waits until the operation completes before continuing. An Asynchronous read continues on and notifies when the I/O is ready.

OK

Commits all of the changes to memory and closes the view.

Active

Active/Inactive status of an OPC Group.

Apply


Revert


Close

Closes the window without committing the changes to memory. If changes exist, the user is prompted to commit the changes.

5.6.3 Item window The Item Configuration window is used to define OPC Items or to configure item data when used as a generic client. To display the Item Configuration window: 1. Select an Item icon in the Hierarchy Browser and either double-clicking or right-clicking. 2. Choose the Configure Item option.

62

CON_016

5.6 OPC Interface windows This window is used to define one item at a time. If you want to define multiple items, refer to Generate Items Dialog Box (see page 78).

Figure 21: Item Configuration Window The following table describes the fields and buttons in the Item Configuration window. Item Configuration Fields FIELD/BUTTON

DESCRIPTION

Name

A user defined name which describes the OPC Item. This name appears in the Hierarchy Browser next to the corresponding item icon.

Description

An optional description which is useful in identifying the item.

OPC Item ID

An item name that is known by the OPC Server and uniquely defines the OPC Item.

Access Path

The access path the OPC Server should associate with this item. If blank, the Server should select the access path.

Preferred Data Type The requested data type to be returned if possible. Options are: Boolean, Byte, Double, Float, Long, Native Type (default), Signed, String, Unsigned, Word Active

Active/Inactive status of an OPC item.

Ovation Point

The Ovation point name to map to the OPC data. Use the Ovation Point Browse button to select the Ovation point name. Otherwise, enter the name of a valid Ovation point. This parameter is used by the OPC Client Map Service. Only used when configuring a Client Mapper.

Ovation Field

The Ovation field to map to the OPC data. If blank, the default field for the point is used. Only used when configuring a Client Mapper.

CON_016

63


FIELD/BUTTON

DESCRIPTION

Direction

The direction of data flow for the item (OPC to Ovation, Ovation to OPC, or both directions). Only used when configuring a Client Mapper.

Set Timestamp

OPC item timestamp. Used to map the Ovation U8, U9 fields for DA/DD/DP point record types. Applicable for the OPC Client Map Service only.

OPC Item ID Browse

Displays the OPC Item Browser dialog. The item's Server must be connected for this button to be enabled.

Ovation Point Browse Button

Displays the Ovation Find Points dialog. This button only works if the program is running on an Ovation drop. Only used when configuring a client mapper.

Ovation Field Browse Button

Displays the Browse Ovation Fields dialog. This button only works if the program is running on an Ovation drop. Only used when configuring a Client Mapper.

OK

Commits all of the changes to memory and closes the window.

Apply


Revert


Close

Closes the window without committing the changes to memory. If changes exist, you are prompted to commit to the changes.

5.6.4 Subscription window

Figure 22: Subscribtion1 The following table describes the fields and buttons in the Subscription Dialog Box window. Subscription dialog box menu options

64

OPTION

DESCRIPTION

Name

A user-defined name which identifies the OPC subscription. Appears in the Hierarchy Browser next to the corresponding Server icon.

Description

An optional description which is useful in identifying the Server.

CON_016


OPTION

DESCRIPTION

Buffer Time [ms]

Buffer time tells the Server how often to send event notifications. Buffer time is in milliseconds. A value time of 0 means that the Server should send an event notification as soon as it receives one.

Max Size

The maximum number of events that is sent in a single IOPCEventSink::OnEvent callback. A value of 0 means that there is no limit to the number of events that are sent in a single callback.

Active

Indicates if the subscription is active.

OK

Commits the changes or selections to memory and closes the window.

Apply

Commits the changes or selections to memory but does not close the window.

Revert

Restores the configuration to the state it was in at the time it was opened or the state of the most recent Apply.

Close

Closes the window without committing the changes to memory. If changes exist you are prompted to commit or not commit the changes.

Help


5.6.5 Monitor items window The Monitor Items window shown below is used to monitor the status of items for a group. To display the Monitor Items window: 1. Select a Group icon in the Hierarchy Browser and right-click. 2. Choose the Monitor Items option. The Monitor Items option is only available if the OPC Server that owns the group is connected.

Figure 23: Item Monitor Window Each of the group's items are listed in the Item Name column. The values, time-stamps, and qualities are all updated by exception.

CON_016

65

5.7 Dialog Boxes for OPC Tools

5.6.6 Monitor Events The Monitor Events window displays all the alarm and event notifications for each alarm and event sent by the Ovation OPC Alarm Server. An example of the Monitor Events window is shown in the following figure. Several fields display useful data that is associated with each event.

Figure 24: Monitor Events Window The following table describes the buttons for the Monitor Events window.

5.7

OPTION

DESCRIPTION

Close

Closes the window.

Help


Dialog Boxes for OPC Tools When modal dialog boxes are displayed, you cannot perform any other task until the dialog box is closed. Non-modal boxes can remain open while other tasks are performed. The following boxes are modal boxes typically used for monitoring.

66

CON_016


5.7.1 Browse OPC Alarms and Events / Data Access Server windows The Browse OPC Alarms and Events Server window is accessed by selecting the Lookup button in the Server Configuration window. The Browse OPC Alarms and Events/Data Access Server windows are used to choose OPC Servers from the list. After selecting a Server from the list, select OK to add the Server to the Server Configuration window. The following window appears when you select an OPC Alarm and Events Server:

Figure 25: Browse OPC Alarm and Events Server

CON_016

67


If you are selecting and OPC Data Access Server, the following dialog appears:

Figure 26: Browse OPC Data Access Server

68

CON_016


5.7.2 OPC item ID browser Use the OPC Item Browser to browse the address space of an OPC Data Access Server. Some Data Servers may not support this functionality. Select the OPC Item ID Browse button from the Item Configuration window to display the OPC Item Browser window. When you double-click on an item, the item displays in the Item ID field located at the bottom of the Item Browser window.

Figure 27: OPC Item Browser

CON_016

69


5.7.3 Ovation point browser Select the Ovation Find Points Browse button from the Item Configuration window to display the Find Points window. Point information displays on the right side of the Find Points window when a Drop name is selected. Double-clicking on a point in the Point Name field applies the point, or you can single select point names and select Apply to apply the selected points.

Figure 28: Find Points Browser

70

CON_016


5.7.4 Ovation field browser Select the Ovation Field Browse button from the Item Configuration window to display the Browse Ovation Fields window. Double-click on an Ovation field to apply the field or you can also single select a field and select Apply.

Figure 29: Ovation Field Browser

CON_016

71


5.7.5 Server State dialog box The Server State dialog box is a modal dialog window used to monitor the status of a Server. In order to display the Server State dialog box, select a Server icon in the Hierarchy Browser and right-click. Then, choose the Display Server State option. The Display Server State option is only available if the Server is connected.

Figure 30: Server State Dialog Box The following table describes the fields in the Server State dialog box: Server State fields

72

FIELD/BUTTON

DESCRIPTION

Name

The user input name which describes the Server.

Handle

The Server handle maintained by the OPC Server.

Startup Time

The time the Server was started.

Current Time

The current time as known by the Server.

Last Update Time

The time the Server last sent data to this client.

State

The current status of the Server. Possible values are Running, Failed, No Configuration Information Loaded, Suspended, and Test Mode.

Number of Groups

The total number of groups being managed by the Server. Applicable for OPC Data Access Server.

CON_016


FIELD/BUTTON

DESCRIPTION

Bandwidth

Server specific implementation of the approximate percent of bandwidth being used by the Server. Applicable for OPC Data Access Server.

Major Version

The major version of the Server software.

Minor Version

The minor version of the Server software.

Build Number

The build number of the Server software.

Vendor Info

A vendor specific string describing the Server.

Close button

Closes the dialog box.

Help button

Used to access on-line help.

5.7.6 Group State dialog box The Group State dialog box is used to monitor the status of a group. In order to display the Group State dialog box, select a Group icon in the Hierarchy Browser and right-click. Then, choose the Display Group State option. The Display Group State option is only available if the Server which owns the group is connected.

Figure 31: Group State Dialog Box The following table describes the fields in the Group State dialog box. Group State Fields FIELD/BUTTON

DESCRIPTION

Name

The user input name which describes the OPC Group.

Handle

The handle that the OPC Server maintains for this group.

Update Rate

The actual update rate, in milliseconds, used by the group.

CON_016

73


FIELD/BUTTON

DESCRIPTION

Deadband

The percent change in an item which causes the OPC Server to send change notifications.

Time Bias

The time bias for the group in minutes.

Locale ID

The language used by the OPC Server (if supported).

Client Handle

The client handle that was passed to the OPC Server for this group.

Close button


Help button


5.7.7 Item State dialog box The Item State dialog box is used to monitor the status of an item. In order to display the Item State dialog box: 1. Select an Item icon in the Hierarchy Browser and right-click. 2. Choose the Display Item State option.

74

CON_016

5.7 Dialog Boxes for OPC Tools The Display Item State option is only available if the Server which owns the item is connected.

Figure 32: Item State Dialog Box Item State Fields FIELD/BUTTON

DESCRIPTION

Name

The user input name describing the item.

Item ID

The item name that uniquely defines the OPC item.

Access Path

The access path the OPC Server uses to associate with this item. If blank, the Server selects the access path.

Client Handle

The handle associated with this item by the client.

Server Handle

The handle associated with this item by the Server.

Req. Data Type

Data type of item. A data type is requested by the client and accepted or rejected by the Server. This field contains the data type that is used.

Native Data Type

The default data type of the item as defined by the Server.

Access Rights

Either Read, Write or Read/Write.

CON_016

75


FIELD/BUTTON

DESCRIPTION

Read Value

The value received by the last update or read for the item.

Timestamp

The time of the last update or read.

Quality

The quality of the item whenever the last update or read occurred. Possible values are Good, Bad and Uncertain.

Write Value

The last value written to the item.

Read Value Changed

A flag indicating whether the read value has changed since the last update.

Write Value Changed

A flag indicating whether the write value has changed since the last update.

Error Code

The last error code for the item.

Close button


Help button


5.7.8 Item Properties dialog box The Item Properties dialog box displays the properties of an item. In order to display the Item Properties box: 1. Select an Item icon in the Hierarchy Browser and right-click. 2. Choose the Display Item Properties option.

76

CON_016

5.7 Dialog Boxes for OPC Tools The Display Item Properties option is only available if the Server which owns the item is connected.

Figure 33: Item Properties Item Properties Fields FIELD/BUTTON

DESCRIPTION

Description

Item Property returned by the OPC Server. This list varies from Server to Server.

Value

Value of the Item Property.

5.7.9 Write value to OPC item dialog box The Write Value To OPC Item dialog box is used to write values to an item. In order to display the Write Value To OPC box: 1. Select an Item icon in the Hierarchy Browser and right-click. 2. Choose the Write option.

CON_016

77


The Write option is only available if the Server which owns the item is connected.

Figure 34: Write Value To OPC Item dialog box Write Value to OPC Item fields FIELD/BUTTON

DESCRIPTION

Name

The user specified item name.

OPC Item ID

An item name that uniquely defines the OPC Item.

Value To Write

The value to be written to the item.

Async Write

Pressing the Async Write button causes the value to be written. The client does not wait for the write to complete before continuing. When the write has completed, the client is notified via a callback procedure.

Sync Write

Pressing the Sync Write button causes the value to be written. The client waits for the write to complete before continuing.

5.7.10 Generate Items dialog box The Generate Items dialog box is used to create multiple OPC items for a selected group. The fields in the dialog box allow you to define how many items you want to generate, and how the items are incremented, named, and defined. In order to display the Generate Items dialog box: 1. Select a Group icon in the Hierarchy Browser and right-click. 2. Choose the Generate Items option. The Generate Items dialog box appears.

78

CON_016


Note: Depending on the tool and selections that you choose, some fields could be grayed out or might not display.

Figure 35: Generate Items Dialog Box Generate Items Fields FIELD/BUTTON

DESCRIPTION

Generation Control Parameters (defines numerical range of items to be generated) From

Starting number of items (for example, 1).

To

Ending number of items (for example, 10).

Increment

Numerical incrementation of item numbers (if 1 is selected and the range is from 1 to 10, then 10 items would be generated; if 2 is selected, then 5 items would be generated)

# Pad Chars

Number of digits that is included in the item name between the prefix and the suffix (if 3 is selected and the range is 1 to 10, then 001 to 010 would be generated; if 4, then 0001 to 0010 would be generated).

Generation Parameters (can be defined for generated items) Name

CON_016

Prefix should be entered and the Generate box should be checked in order to generate valid items. Suffix is optional. A sample of the item name appears (for example, LA001200).

79


FIELD/BUTTON

DESCRIPTION

Description

Optional description of the item.

OPC Item ID

An item name that is known by the OPC Server and uniquely defines the OPC item.

Access Path

The access path the OPC Server should associate with this item.

Ovation Point

The Ovation point name to map to the OPC item. This field is only applicable for the Ovation Client Mapper.

Common Parameters (defines parameters applied to all generated items) Preferred Data Type The requested data type to be returned if possible. Options are: Boolean, Byte, Double, Float, Long, Native Type (default), Signed, String, Unsigned, Word Ovation Field

The Ovation field to map to the OPC data. If blank, the default field for the point is used. This field is only applicable for the Ovation Client Mapper.

Direction

The direction of data flow for the items (OPC to Ovation, Ovation to OPC or both directions). This field is only applicable for the Ovation Client Mapper.

Active

Active/Inactive status of the generated items.

Set Time-stamp

Determines if a time-stamp is set for the items. This field is only applicable for the Ovation Client Mapper.

OK

Starts generation of items defined in window.

Cancel

Cancels all the current changes.

Help

Use to access on-line help.

Generate Multiple Items Example: The following is an example of generating multiple items: The Generate Items dialog box example uses the following values.

The digit 1 is entered in the From entry field.

The digit 10 is entered in the To entry field.

The digit 1 is entered in the Increment field.

The digit 2 is entered in the # Pad Chars. field.

LA is entered in the Name Prefix entry field and the Generate box is checked. The digit -200 is entered in the Suffix field. When you select the OK button, ten items are generated, beginning with LA001-200 and ending with LA010-200. The parameters of the items reflects the values that were entered/selected in the Parameter fields.

80

CON_016


5.7.11 Add Multiple Items dialog box The Add Multiple Items dialog box is used to create multiple OPC items for a selected group. The fields in the dialog box allow you to define how many items you would like to add. In order to display the Add Multiple Items dialog box: 1. Select a Group icon in the Hierarchy Browser and right-click. 2. Then, choose the Add Multiple Items option. The Add Items dialog box appears.

Figure 36: Add Items Dialog Box

5.7.12 Find dialog box Clicking on the binoculars icon in any dialog box displays a Find dialog box. In this dialog box you can enter the item that you would like to locate in the Find What entry field, then select the Find Next button.

Figure 37: Find Dialog Box

CON_016

81


5.7.13 Subscription State dialog box OPC Clients can obtain the current state of all subscriptions which are active or inactive.

Figure 38: Subscription State Subscription State menu options

82

OPTION

DESCRIPTION

Buffer Time [ms]

Buffer time tells the Server how often to send event notifications. Buffer time is in milliseconds. A value time of 0 means that the Server should send an event notification as soon as it receives one.

Max Size

The maximum number of events that is sent in a single IOPCEventSink::OnEvent callback. A value of 0 means that there is no limit to the number of events that is sent in a single callback.

Client Handle

The client handle for the subscription object sending the event notifications.

Active

The current active state of the subscription.

Close

Accepts the selections and closes the window.

Help


CON_016


5.7.14 Subscription Filter dialog box A filter is a structure containing criteria for selecting events of interest to the client. A null filter results in the OPC Client receiving all event notifications. Events can be selected using the following criteria:

Type of event - simple, condition, or tracking.

Severity Level - lowest to highest level.

Event Categories.

Process Area.

Event Sources.

The Subscription Filtering window has three tabs to choose from:

Types and Severity Tab (see page 84).

Categories Tab (see page 86).

Areas and Sources (see page 87).

CON_016

83


Types and Severity tab The Types and Severity tab displays the alarm type and the severity of each alarm and event. Event Types can be identified as Simple, Condition, or Tracking. Events and Alarms are defined by the level of severity to the system.

Event Types are different classifications of events recognized by the OPC Server.

Severity Level indicates the urgency of the sub condition. Commonly called priority, especially in relation to process alarms. Severity ranges must be distributed across the 1 to 1,000 range in a manner that clients can assume linear distribution.

Figure 39: Types and Severity Tab Types and Severity menu options

84

OPTION

DESCRIPTION

Simple Event Type

Simple events are all events other than Tracking or Condition events. An example of a simple event is a component failure within the system represented by the OPC Event Server.

Condition Event Type

Condition-related events are associated with OPC conditions and represent transitions into or out of the states represented by the OPCConditions and OPCSubConditions.

CON_016


OPTION

DESCRIPTION

Tracking Event Type

Tracking-related events are not associated with conditions but represent occurrences which involve the interaction of an OPC Client with a "target" object within the OPC Event Server.

Lowest Severity Level

Lowest severity level is 1. Severity level ranges from 1 to 1,000. Severity levels can have several ranges. See the following table.

Highest Severity Level

Highest severity level is 1,000. Severity level ranges from 1 to 1,000. Severity levels can have several ranges. See the following table.

OK

Accepts and saves the selections.

Cancel

Closes the window and does not save the selections.

Help


Severity level ranges OPC defines severity on a scale from 1 to 1000. The following table shows an example of eight severity levels with the following mapping. OV ATION PRIORITY

OPC SEVERITY

8

100

7

200

6

300

5

400

4

500

3

800

2

900

1

1000

CON_016

85


Categories tab Event Categories define groupings of events supported by an OPC Event Server. Event categories can be defined for all event types, such as Simple, Condition-related and Tracking Events. Names of event categories must be unique within the event Server. Event subscriptions can be filtered based on event categories. For example, event categories might include COS, SOE, System, Discrete, and so forth. The following window displays a list of Available Categories are displayed. In this example the first four categories are simple events, while the remainder are conditional events.

Figure 40: Categories Tab Categories tab menu options

86

OPTION

DESCRIPTION

Enable Category Filtering

This option enables category filtering.

Available Categories [Code]

Lists all available OPC Alarms and Events Server categories to be selected.

Selected Categories [Code]

Lists all categories selected.

Add

Adds the selected category from the list of available categories.

CON_016


OPTION

DESCRIPTION

Remove

Removes the category selected from the selected categories list.

OK

Accepts and saves the selections.

Cancel

Closes the window and does not save the changes to memory.

Help


Areas and Sources tab The Areas and Sources tab allows you to select specified process areas and event sources and place them into an enabled state. An area is a grouping of plant equipment configured by the user, typically according to areas of operator responsibility. A source is enabled if its condition is set to enable, and all areas within the hierarchy of its containing areas are enabled.

Figure 41: Areas and Sources Tab

CON_016

87


Areas and Sources tab menu options OPTION

DESCRIPTION

Enable Area Filtering

Enables area filtering for the select area. Allows you to add areas and area branches.

Add Area

Adds the selected area in the Selected Area dialog box.

Add Area Branch

Adds the selected area branch in the Selected Area dialog box.

Remove Areas

Removes selection from the Selected Area dialog box.

Remove All

Removes all selections from the Selected Area dialog box.

Enable Source Filtering

When selected enables source filtering for the selected sources.

Add Source

Adds the selected source in the Selected Sources dialog box.

Remove Sources

Removes the selected source in the Selected Sources dialog box.

OK

Accepts and applies the selections.

Cancel

Dismisses the selections and does not save the changes to memory.

Help


5.7.15 Subscription Select Attributes dialog box The Event Attributes window displays selection fields and their associated attributes.

Figure 42: Event Attributes

88

CON_016

5.7 Dialog Boxes for OPC Tools Event Attributes menu options OPTION

DESCRIPTION

Categories [Code]

Lists OPC Alarms and Events Server categories.

Available Attributes[ID]

Lists all available attributes and the associated ID number.

Selected Attributes[ID]

Lists selected attributes and their associated ID number.

Add

Adds selected attributes.

Remove

Removes selected attributes.

OK

Accepts and commits the changes to memory and closes the window.

Cancel

Cancels the current changes and does not close the window.

Help


CON_016

89


5.7.16 Browse Categories dialog box The Browse Categories window lists all the OPC alarms and events categories and enables you to browse OPC categories, conditions and sub conditions.

Categories - Event Categories define groupings of events that are supported by the OPC Event Server for the selected categories.

Conditions - A condition is a named state of the OPC Event Server. An alarm is a special case of a condition which is deemed to be abnormal and requires special attention.

Subconditions - Sub conditions allows clients to more easily deal with closely related event notifications.

In the following example, Level (4) is selected which displays all the associated conditions and sub conditions with the Level (4) category.

Figure 43: Browse categories menu Browse Categories menu options

90

OPTION

DESCRIPTION

Categories [Code]

Lists OPC Alarms and Events Server categories.

Conditions

Lists OPC conditions for the selected event categories.

Subconditions

Lists OPC sub conditions for the selected OPC condition.

CON_016


OPTION

DESCRIPTION

Close

Closes the window.

Help


CON_016

91

S

E C T I O N

6

Security

IN THIS SECTION Making connections between OPC Servers and Clients and connection scenarios ........ 93 Relationships between computers involved in OPC communication................................ 94 Situations where both computers are members of the same Windows domain............... 95 OPC clients running as an ordinary application on the user desktop ............................... 96 Setting Security for Windows NT and 2000 ...................................................................... 97 OPC via DCOM with Windows XP Service Pack 2 and Windows 2003 Server Service Pack 1............................................................................ 101 DCOM Enhancements .................................................................................................... 102 Windows Firewall ............................................................................................................ 106 Local Security Policy Settings ......................................................................................... 111

6.1

Making connections between OPC Servers and Clients and connection scenarios Several possible situations exist when connecting an OPC server to a client.

The client and server may both reside on the same computer.

The client and server may be on different computers.

If the client and server are on different computers:

The computers may be in the same Windows domain.

The computers may be in different domains.

One or both computers may not be in any domain.

Each scenario requires different software configurations. Various software configurations are discussed in this section. In the simple situation where both OPC client and server reside on the same computer, there are no configuration issues to contend with. In this situation, install and configure both pieces of software according to the vendors' instructions and they will connect without any sort of security setup at all.

CON_016

93

6.2 Relationships between computers involved in OPC communication

6.2

Relationships between computers involved in OPC communication Most OPC installations involve a client and a server on two different computers. Naturally, there must be network connectivity between the computers. Some configuration requires customized configuration of network hardware between the computers. This document assumes that there is connectivity and that it allows OPC communication but does not address the network between the computers. In all cases of OPC communication between computers there is a basic level of security configuration required in order to enable a successful connection. The remaining sections describe how to configure the security settings for both DCOM and the Windows firewall. This section describes how you must configure user accounts and applications. There are two possible relationships between computers involved in OPC communication. 1. The two computers are in the same Windows domain. 2. The computers are not in the same domain. This scenario covers situations where each computer is in a different domain, or one or both of the computers is not in any domain. In all situations, OPC connectivity requires that each computer is able to authenticate the user that is attempting to connect to it from the remote computer. This means the user account that the remote OPC software is executing must be known to the local computer. As an example consider the following situation.

COMPUTER 1

COMPUTER 2

OPC Client A

OPC Server B

Runs as

Runs as

OPCUSER1

OPCUSER2

In this example, OPC Client A attempts to connect to OPC Server B on Computer 2. OPC Client A is executing under the user account OPCUSER1. To establish a successful connection, Computer 2 must have knowledge of OPCUSER1. Typically, OPCUSER1 would be a user that has some set of privileges on Computer 2. Because OPC is symmetrical, the opposite situation must also be true: To establish a successful connection for OPC Server B running under the user account OPCUSER2, to send data back to the client on Computer 1, then Computer 1 must be able to authenticate OPCUSER2.

94

CON_016

6.3 Situations where both computers are members of the same Windows domain

6.3

Situations where both computers are members of the same Windows domain In the situation where both computers are members of the same Windows domain, the users may be users defined in that domain. If this is the Ovation domain, these users may be Ovation users. If the two computers are not in the same domain, the only way to enable OPC connections is to define local users on both computers that have both the same username and the same password. Use the following procedure to add a local user to a Windows XP system or a Windows Server 2003 system that is not being used as a domain server. Note: You cannot add local users to a domain server. Therefore, you may not be able to use a domain server as one end of an OPC connection. In all the remote situations, all of the OPC software must execute as a common user. Depending on how the software is set up to execute, there are different ways to ensure this situation. The OPC clients and server may be executing as a Windows service, as a DCOM server or as a user mode application running on the desktop. Each of these situations requires a different setup to ensure execution as a specific user.

6.3.1 To add a local user to a system that is not used as a domain server 1. Select: Start -> Control Panel 2. Double-click on the User Accounts item. 3. Click on the Advanced tab. 4. Click the Advanced button. 5. Right-click on the Users item on the right side of the Local Users and Groups window. 6. Select New User. A window opens allowing you to create a new local user. 7. Enter the User name and enter the password twice. The Full name and Description fields may be filled in but are not necessary. Typically, you will want to uncheck the User must change password at next logon option and check the Password never expires option. 8. Click the Create button to create the user. 9. Click the Close button to exit the window. Use this username to execute all your remote OPC software. Note: This procedure adds a local user to a Windows XP system or a Windows Server 2003 system that is not being used as a domain server. You cannot add local users to a domain server. Therefore you may not be able to use a domain server as one end of an OPC connection.

6.3.2 To set up a Windows server to execute as a specific user 1. Select: Start -> Control Panel 2. Double-click on Administrative Tools. 3. Double-click on Services. 4. From the list of services, find the service you are configuring and double-click on that line. 5. Click on the Log On tab.

CON_016

95

6.4 OPC clients running as an ordinary application on the user desktop

6. Click the This account radio button and fill in the username and password edit fields and select OK. 7. After configuring the service, you must either stop and restart the service or reboot the computer. Note: The Ovation OPC Server and Ovation OPC Client Mapper both run as Windows services.

6.3.3 To set up a DCOM server to run as a particular user Some OPC servers may execute as a DCOM server. 1. From the start menu select Run. 2. Enter dcomcnfg in the edit field and click OK. 3. In the tree view on the left side of the Component Services window expand Component Services, Computers and My Computer. 4. Double-click on DCOM Config. You may see some DCOM Configuration Warning messages. 5. At this time, click NO for these questions. 6. You will now see a list of DCOM servers on the right side of the Component Services window. Find the server in question, right-click on it and select Properties. 7. In the properties window click the Identity tab. 8. Select the This user radio button and fill in the User and Password edit fields. 9. Click OK. After you have made these selections, when the DCOM server runs, it will run in the context of the user you have entered.

6.4

OPC clients running as an ordinary application on the user desktop An OPC client may run as an ordinary application on the user desktop. Typically, this is the case with the Ovation OPC Config tool. Do not confuse the OPC Config tool with the OPC Client Mapper. The OPC Config tool is not the same client as the OPC Client Mapper. The Config tool is a separate client and has no connection with the OPC Client Mapper, other than generating the configuration file that Client Mapper uses. Both clients operate independently and make separate connections to the OPC server. When running an OPC client on the user desktop, you must execute the software as the specific user you have designated as your OPC user. Normally this requires logging into the computer as this user. You may also use the Windows runas command to execute the Config tool. See the Windows help for instructions for using the runas command.

96

CON_016

6.5 Setting Security for Windows NT and 2000

6.5

Setting Security for Windows NT and 2000 Security for an OPC Server and for a client is configured with dcomcnfg.exe, a program supplied with the Windows operating system. Security must be configured on the OPC Server machine and also on the Client machine to ensure proper operation of the OPC functions. You must be logged on with Administrator privileges to change the DCOM configuration using Windows. CAUTION! Changing default values can have far reaching consequences; therefore, changing these values should be carefully considered. Before making changes, record the existing values so that you can return to the original values if your experimentation fails.

6.5.1 To set security 1. Select the Start -> Run. The Run window appears. Enter dcomcnfg in the Open entry field and select OK. The Distributed COM Configuration Properties window appears. 2. Select the Applications tab. If the OPC Server is installed correctly and registered with DCOM, you should see an “OPC Server” entry in the list.

Figure 44: DCOM Window (Applications Tab)

CON_016

97


3. Select the Default Properties tab. The recommended Default values are described in the following table. Your own application could require higher security requirements.

Figure 45: DCOM Window (Default Properties Tab) Default Properties Values

98

ENTRY

VALUE

Enable Distributed COM on this computer

Checked

Enable COM Internet Services on this computer

Not checked

Default Authentication Level for Windows 2000 and NT

None

Default Impersonation Level

Identify

Provide Additional Security for Reference Tracking

Not checked

CON_016

6.5 Setting Security for Windows NT and 2000 4. Select the Default Security tab.

Figure 46: DCOM Window (Default Security Tab) 5. Select Edit Default in the Default Access Permissions section of the Default Security tab. The Registry Value Permissions window appears. Note: The following user/group security settings are typical for most OPC Server situations. However, different settings could be required due to special security considerations for your system. 6. Ensure that the following users/groups appear in the Registry Value Permissions window: Administrators Everyone Interactive Network System 7. If some or all of these names do not appear in the window, select the Add button and the Add Users and Groups window appears. 8. Select the appropriate names from the scrolling list and select the Add button to move them from the scrolling list to the Add Names box. After the names have been added, select Allow Access for the Type of Access. Select the OK button. 9. Return to the Default Security tab. 10. Select Edit Default in the Default Launch Permissions section of the Default Security tab. The Registry Value Permissions window appears.

CON_016

99


11. Ensure that the following Users/Groups appear in the window: Administrators Everyone Interactive Network System 12. If some or all of these names do not appear in the window, select the Add button and the Add Users and Groups window appears. 13. Select the appropriate names from the scrolling list and select the Add button to move them from the scrolling list to the Add Names box. After the names have been added, select Allow Launch for the Type of Access. Select the OK button. 14. Select the Applications tab and click on OPC Service. Click on the Properties button. You should see another tabbed dialog box. The settings in the following table are recommended; however, site security policies could dictate different settings. These settings are generally unrestricted allowing any user that can be authenticated on the local machine to access the OPC Server: OPC Service Values T AB

ENTRY

VALUE

NOTES

General

Authentic Level

Default

Location

Run application on computer where data is located.

Unchecked

Location

Run application on this computer.

Checked

Location

Run application on the following computer.

Unchecked

Security

Use default access permissions.

Select radio button

Customize this if default permissions are too restrictive.

Security

Use default launch permissions.

Select radio button


Security

Use default configuration permissions.

Select radio button


Identify

Select radio button


Endpoints

Default system protocols

15. If desired, you can modify the Default Launch and Default Access permissions with the controls on the Default Security tab. Windows 3.51/4.0 security is certified to the C2 level. There are no security restrictions for local OPC access to the OPC Server.

100

CON_016

6.6 OPC via DCOM with Windows XP Service Pack 2 and Windows 2003 Server Service Pack 1

Note: In order for the OPC applications to create DCOM objects on the remote computer, the user account, which the application runs, must be known to the remote computer. Identified in the Identity tab, there are two ways this can happen: 1. If both computers are in the same Windows domain, a domain user can be used. 2. In all cases, local user accounts can be set up on both computers. These user accounts must have the exact same user name and password. Both OPC applications should be set up to execute under that user account.

6.6

OPC via DCOM with Windows XP Service Pack 2 and Windows 2003 Server Service Pack 1 If you are using a third-party OPC Server, refer to the specific vendors OPC manual for DCOM/Security Settings. Note: The following information is used with permission from the OPC Foundation. Additional OPC information can also be found on the OPC Foundation website http://www.opcfoundation.org. The goal of Windows XP Service Pack 2 and Windows 2003 Server Service Pack 1 is to reduce common available scenarios for malicious attack on Windows XP and Windows 2003 Servers. The Service Pack reduces the effect of most common attacks in four ways: 1. Improvement in shielding Windows XP from the network. RPC and DCOM communication enhancements. Enhancements to the internal Windows firewall. 2. Enhanced memory protection. 3. Safer handling of e-mail. 4. Internet Explorer security enhancements. Most OPC Clients and Servers use DCOM, (Distributed Component Object Model), to communicate over a network and thus are impacted due to the changes in Service Pack. When Service Pack is installed with its default configuration settings, OPC communication via DCOM ceases to work. This document describes the settings necessary to restore OPC communication when using XP Service Pack 2 (SP2) and 2003 Server Service Pack 1 (SP1). Since the callback mechanism used by OPC essentially turns the OPC Client into a DCOM Server and the OPC Server into a DCOM Client, the instructions provided here must be followed on all nodes containing either OPC Servers or OPC Clients. Note: PC communication that is confined to a single machine using COM, but not DCOM, continues to work properly after installing either SP1 or SP2 without following the instructions in this document.

CON_016

101

6.7 DCOM Enhancements

6.7

DCOM Enhancements Windows XP Service Pack 2 and Windows 2003 Server Service Pack Service 1 have made security enhancements to DCOM. Two in particular need to be taken into consideration when using OPC on a network:

First, the default Launch and Access permissions dialogs have been modified to allow the user to configure limits on the permissions given to applications using DCOM.

Secondly, for each user now defined in the Launch and Access permissions, both local and remote access can be explicitly defined.

Launch permissions define who can launch a COM based application (such as an OPC server) both over the network or locally. Access permissions define who can access that application once it has been launched. Applications can get their Launch and Access permissions from one of three places: 1. They can use explicitly defined setting for their application. 2. They can use the default permissions. 3. They can set their own permissions programmatically. Since an application could set its own permissions programmatically, the explicitly defined or default settings, although set properly, might not be used. Therefore the user is not able to explicitly have control over these settings. To overcome this security flaw, Microsoft has added limits to the DCOM security settings from Launch and Access to limit the permissions that an application can use. This limit prevents the application from using permissions beyond what is specified in the DCOM configuration settings. By default, the limits set by Windows XP Service Pack 2 and Windows 2003 Server Service Pack 1 do not allow for OPC communications over the network. In addition to the new permissions limits, one must now specify if the user or group specified has permissions locally or remotely (or both). In order for OPC applications to work over the network with DCOM, the permissions must be set such that remote users can launch and/or access the OPC servers and clients on the machine.

6.7.1 To Configure DCOM for OPC using XP Service Pack 2 and Windows 2003 Service Pack 1 1. Select Start -> Run and enter DCOMCnfg and click on OK.

Figure 47: Run Dialog Box 2. Click on Component Services under the Console Root to expand.

102

CON_016

6.7 DCOM Enhancements 3. Click on Computers under Component Services to expand. 4. Right-click on My Computer in the pane on the right and select Properties.

Figure 48: Component Services Window 5. Go to the COM Security tab and note these are the four permission configurations that you might have to edit:

Figure 49: My Computer Properties Window 6. Edit the Limits for Access and Launch a) Access Permissions – Select Edit Limits...You need to check the Remote Access box for the user labeled ANONYMOUS LOGIN in this dialog.

CON_016

103


Note: This setting is necessary for OPCEnum.exe to function and for some OPC Servers and Clients that set their DCOM Authentication Level to None in order to allow anonymous connections. If you do not use OPCEnum, you might not need to enable remote access for anonymous users.

Figure 50: Access Permissions Window b) Launch and Activation Permissions – Select the Edit Limits... button. You need to check the remote boxes for the user labeled Everyone in this dialog.

104

CON_016


Note: Since Everyone includes all authenticated users, it is often desirable to add these permissions to a smaller subset of users. One suggested way to accomplish this is to create a group named “OPC Users” and add all user accounts to this group that executes any OPC Server or Client. Then substitute “OPC Users” everywhere that Everyone appears in these configuration dialogs.

Figure 51: Launch Permissions Window 7. Edit Default Permissions for Access and Launch For each user (or group) that participates in OPC communication (for example OPC Users), make sure that both the Local Allow and Remote Allow check boxes are both checked. Access permissions per user:

Figure 52: Permissions for Everyone Window

CON_016

105

6.8 Windows Firewall

Launch and Activation permissions per user:

Figure 53: Permissions for Everyone Window

6.8

Windows Firewall The Windows firewall allows traffic across the network interface when initiated locally, but by default stops any incoming “unsolicited” traffic. However, this firewall is “exception” based, meaning that the administrator can specify applications and ports that are exceptions to the rule and can respond to unsolicited requests. The firewall exceptions can be specified at two main levels, the application level and the port and protocol level. The application level is where you specify which applications are able to respond to unsolicited requests and the port and protocol level is where you can specify the firewall to allow or disallow traffic on a specific port for either TCP or UDP traffic. To make any OPC Client/Server application work via DCOM, changes need to be made on both levels. Exceptions need to be added to the Windows Firewall if you are accessing the Server from a remote client. Note: Developers of OPC Products might want to automatically make the necessary firewall settings programmatically. Microsoft supplies the Windows firewall API to support this.

106

CON_016


6.8.1 To Configure the Firewall By default the Windows firewall is set to the ON setting located in the General Tab of the Windows Firewall window. This setting is recommended by Microsoft and by OPC to give your machine the highest possible protection. For trouble-shooting, you might want to temporarily turn off the firewall to prove or disprove if the firewall configuration is the source of any communication failure. Note: It could be appropriate to permanently turn off the firewall if the machine is sufficiently protected behind a corporate firewall. When turned off, the individual firewall settings outlined here need not be performed to allow OPC communication.

Figure 54: Windows Firewall General Tab

CON_016

107


1. Select the Exceptions tab and add all OPC Clients and Servers to the exception list. Also add Microsoft Management Console used by the DCOM configuration utility DCOM Enhancements (see page 102).

Figure 55: Windows Firewall Exceptions Tab

108

CON_016

6.8 Windows Firewall 2. In the Exceptions dialog box there is a listing of programs on the machine; however, not all programs show up on this list. Click on the Add Program button and the Add a Program window appears.

Figure 56: Add a Program Window 3. Browse to find the applicable executables installed on the computer. The following table lists the executable files used for the specified OPC related programs. Firewall Exceptions OV ATION OPC PRODUCT

EXECUTABLE FILE USED

OPC Data Access Server

OvationOPC.exe - (typically found in C:\Ovation\OPC). OPCENUM.exe - (typically found in C:\windows\system32). OPCConfig.exe - (typically found in C:\OPCEventServer, C:\OPCClientMap, C:\Ovation\OPC).

OPC Alarm and Event Server

OvationEventServer.exe - (typically found in C:\Ovation\OPCEventServer) OPCENUM.exe - (typically found in C:\windows\system32). OPCConfig.exe - (typically found in C:\OPCEventServer, C:\OPCClientMap, C:\Ovation\OPC).

OPC Client Mapper

OPCClientMap.exe - (typically found in C:\Ovation\OPCClientMap). OPCConfig.exe - (typically found in C:\OPCEventServer, C:\OPCClientMap, C:\Ovation\OPC).

4. Click OK to accept the changes.

CON_016

109


Note: Only EXE files are added to the exceptions list. For in-process OPC Servers and Clients (DLLs and OCXs) you must add the EXE applications that call them to the list instead. 5. You need to add TCP port 135 as it is needed to initiate DCOM communications, and allow for incoming echo requests. In the Exceptions tab of the Windows Firewall window, click on Add Port.

Figure 57: Exception Tab Add a Port Window 6. The Add a Port dialog box appears. Fill out the fields as follows: Name: DCOM Port number: 135

110

CON_016

6.9 Local Security Policy Settings 7. Choose the TCP radio button

Figure 58: Add a Port Dialog Box 8. Click OK to accept your selections.

6.9

Local Security Policy Settings Modifications to the local security policy settings may be necessary to allow OPC Servers and Clients to communicate. For example, in some cases security setting changes are necessary if Server or Client machines are not on the same domain, or one of the machines is a member of a workgroup. Local security policies need to be modified on both the OPC Server and Client machines whenever the machines reside on different domains. The following modifications to local security policy changes are applicable to all 2.4 Ovation systems and later.

6.9.1 To set Local Security Policy Settings for Domain Machines For Domain machines, choose the following path to access local security options, then perform the following procedure: Select Start -> Control Panel -> Administrative Tools -> Domain Security Policies The Default Domain Security Settings window appears Select Security Settings ->Local Policies -> Security Options 1. Navigate through the entry list to Network Access: Sharing and Security Mode for Local Accounts 2. Double click on your selection to open the item 3. Select the Define this policy setting checkbox 4. Select Classic - local users authenticate as themselves, from the drop down box 5. Select OK 6. Reboot the OPC Server or Client machine

CON_016

111

6.9 Local Security Policy Settings

The following figure illustrates the folder structure for security settings selections.

Figure 59: Domain Security Settings The following figure illustrates the required security policy setting selection.

Figure 60: Security Policy Setting

112

CON_016

6.9 Local Security Policy Settings

6.9.2 To set Local Security Policy Settings for Workgroup Machines as Administrator For Workgroup machines, choose the following path to access local security options, then perform the procedure below: Select Start -> Control Panel -> Administrative Tools -> Local Security Policies The Local Security Setting window appears Select Security Settings -> Local Policies -> Security Options 1. Navigate through the entry list to Network Access: Sharing and Security Mode for Local Accounts 2. Double click on your selection to open the item 3. Select Classic - local users authenticate as themselves, from the drop down box 4. Select OK 5. Reboot your machine

CON_016

113

Glossary of Terms A A Port Port on a dual-attached Ovation station where the primary ring enters and the secondary ring exits. Admin Tool The Administrative Tool is an Emerson utility that configures and downloads software to the drops through the use of GUIs. (Do not confuse this tool with the Sun utility also named Admin Tool.) Alarm A message or other signal intended to draw attention to a non-normal plant condition; for displays at user interfaces, an alarm reflects a point status. Algorithm 1) A set of rules, procedures, and mathematical formulas that define a desired control strategy. 2) Software provided with a Controller to automatically apply a specified algorithm during the system scan. 3) Ovation record type (LC) used to store tuning or data configuration for an algorithm in the system. Analog 1) Conditions or values that continuously vary across some range, represented by more than one bit. 2) A point that is an analog record type. Analog points are typically associated with I/O hardware that converts a field signal (for example, voltage) to a low-level signal used by the processor. Can be Long or Deluxe (Contrast with digital.) Aperiodic Points Points whose values are scanned only as needed or as requested. See also periodic points. API Application Programming Interface, a set of routines or functions a program calls to tell the operating system to perform a task. Application program 1) Emerson-supplied programs that perform frequently required functions. 2) A series of loops, ladders, and/or algorithms run in a processor to control plant functions. Also known as an Application. 3) Userdefined or commercially available software that performs a specific task. Apply GUI button that accepts changes and window remains open.

CON_016

115

Glossary of Terms ASCII American Standard Code for Information Interchange, a standard for representing computer characters. The set consists of 128 characters numbered from 0 to 127 and includes all the letters, numbers and punctuation marks. Asynchronous Data communication that is not time critical. Typically provided on demand only and provided at different times (Contrast with synchronous). AUI Cable Attachment Unit Interface Cable that interfaces the PCRR card to the MAU module in Ovation and WDPF migrated remote I/O applications. It contains four sets of individually shielded twisted pairs.

B B Port Port on a dual-attached Ovation station where the secondary ring enters and the primary ring exits. Bandwidth This is a description of how much information can be sent through a connection, usually measured in bitsper-second. Base Alarm System Standard package used for viewing and acknowledging alarms. Base Unit Hardware that consists of a printed circuit board, various connectors, and plastic housing and provides a mechanism for the user to land field wiring, and connects the field signals to the I/O module. The unit enables the I/O module to receive power, and also provides a low-impedance earth ground connection. Each Base Unit can house two sets of I/O modules, along with the associated field wiring. Baud Rate Number of bits-per-second a modem can send or receive. BG See Packed Group Alarm. Bit A single digit number in base-2, either a 1 or a zero. This is the smallest unit of computerized data. Bitmap file A file type that is used to define which icons are shown when using iconic alarming.

116

CON_016

Glossary of Terms Bootstrap A software routine used to start computer operation (sometimes abbreviated ‘boot’). The bootstrap routine will typically occur automatically after a reset or power cycle, but may require manual keying. Branch Set of Base Units configured consecutively on a DIN rail with a local bus being connected to the Ovation I/O Controller. Bridge Device that connects two or more network components and transmits data with source and destination addresses on different network components. Broadcast Process of sending information across the Ovation network. Broadcasts may be periodic (every second or every 0.1 of a second) or non-periodic (broadcast on demand only). Byte A set of bits that represent a single character. Typically, 8 or 10 bits in a byte.

C Cancel GUI button that cancels changes and dismisses window. CDDI Copper Distributed Data Interface (See FDDI). CDE Common Desktop Environment. A windowing system that runs on a Sun-compatible workstation under SunOs™ or Solaris™ Characteristics A set of 8 alphanumeric characters associated with a point, used to represent user-defined aspects of the controlled process. Characteristics are used in alarm processing and point review/search functions. Client A computer, or software program that is used to contact and obtain data from a server software program on a networked computer. Coil A ladder diagram element that represents either a real-world output field device (for example, a motor starter, solenoid, and so forth) or an internal calculated point. (See discrete output.)

CON_016

117

Glossary of Terms Collision Garbling of data when two or more nodes on the same network segment transmit data simultaneously. Collision Detection Switches are used to buffer simultaneous data messages and transmit them one at a time. Compact I/O Modules Ovation I/O modules that do not contain a Personality module, only an Electronics module. Concentrator FDDI node used to connect multiple Ovation stations to dual rings. Must have an “A” port, a “B” port, and at least one “M” port. Conducting The state of a ladder diagram circuit when there is a continuous current path condition caused by closed contacts. Configuration Entering initial data into a processor, including definition of associated hardware. The configuration process typically includes downloading the drop database and other required software, and may involve editing configuration files(s). Configuration File Typically, an ASCII file containing statements that specify the configuration of a drop or function. These files may use standard operating system formats or may use an Emerson source language. Contact A ladder diagram element that represents either a real-world input device (for example, a push-button, switch, etc.) or an internal calculated point. (See discrete input.) Control Builder Power tool package used to build control drawings and generate source code from the drawings. Control Sheet Drawing that contains a graphical representation of a control scheme. Control Task Specific Controller area where all control sheets in that area are scanned at the same frequency. Controller A drop used to control a process. The Controller passes process control information over the network to other drops or devices that need it.

118

CON_016

Glossary of Terms CPU Central Processing Unit, a microprocessor chip that powers a computer. May also refer to the case that holds the chip. CRT Cathode-Ray Tube, a tube of a monitor that produces images on the screen. Often used as a generic term for a computer monitor. Cursor A character on a display screen indicating the current active location.

D DAC/DAS Dual Attachment Concentrator/Dual Attachment Station. Provides dual attachment to the FDDI or Fast Ethernet network. Data Highway The communication link used to transfer time-critical information between drops or stations; also called a Local Area Network (LAN) or network. Data Structures Four portions of an Ovation point record type.See also Dynamic Data, Static Data, Flash Data, and MMI Data. Database A structured set of data, especially the Distributed database in each Ovation drop (which defines originated and received points) and the Ovation Master database (which defines the attributes of all points in the system). DCS Distributed Control System (such as Ovation). Deadband Range of values through which an input signal may vary without initiating an action that causes an observable change in the output signal. Default Points Points created by the Control Builder that have a defined naming convention. Default Value Used by a program when no specific value has been entered by the user. In the context of an iterative window or program, default may refer to a value specified in the function’s configuration file; in the context of configuring a function, default refers to the value used when there is no valid parameter entry.

CON_016

119

Glossary of Terms Deluxe record type Optional Ovation record type. Has same functions as Long record type, plus plant mode limits and scan time displays. Destination 1) The location in memory (such as a holding register) into which data is placed after the completion of certain programmable functions. (Contrast with source.) 2) A method of determining which alarms are displayed at a specific user interface drop, based on the first point characteristic (typically representing the plant area). Developer Studio Common interface that houses all of the integrated engineering tools necessary for a Microsoft Windows based Ovation system. Device 1) Peripheral equipment connected to the Ovation system. 2) Algorithm specifically designed to simplify operation of open/close or stop/start devices, using feedback signals to monitor command completion. DHC Data Highway Controller. Printed-circuit board(s) in each drop that manage Data Highway communication. Diagnostics Functions that examine hardware or software to isolate malfunctions and errors. In the Ovation system, each drop incorporates automatic self-test diagnostics. If faulty operation is detected, a message or alarm is usually initiated. Diagram A graphic depiction of a plant process (or other data), displayed on a CRT at a user interface. Dialog Box A user interface window that prompts the user to enter information needed by a process. Digital 1) Signals or conditions that are either on or off, represented by one bit. 2) A point that is a digital record type. Digital points are typically associated with discrete I/O hardware. Can be Long or Deluxe. (Contrast with analog.) DIN Connector conforming to the specifications of the German standards organization (Deutsche Industrie Norm). DIP Integrated circuit enclosed in a plastic or ceramic housing and connected to pins. (Dual Inline Package)

120

CON_016

Glossary of Terms Discrete I/O Individual hard-wired circuits connecting real-world field devices with the processor. Each discrete input provides the processor with a single digital signal based on a single state in the field device. Each discrete output sends a single digital signal to the field based on a single bit of data in the processor. Distributed Database Contains a subset of the information stored on the Master Database and is stored locally on a drop to allow that drop to operate if the Master Database is unavailable. A Distributed Database is present on each drop in the system and is continually updated as point information changes. Distributed I/O Hardware used to communicate between the processor and I/O modules located outside the processor chassis (also called Remote I/O). Domain Logical collection of computers and users on a network that share a common security database. Download The process of transferring data to the memory or disk of a drop. Drop A collective term for a Controller, Workstation, or Database Server that is a member of an Ovation network and is defined as a drop by an Ovation configuration tool (Developer Studio or Init Tool). Drop Loader Power Tool used to load control and originating point information into drops in an Ovation system. Links the Master Database with all the drops in the system. Drop Point (DU) Record type used to store status information for a drop. Every drop must be configured with at least one point of type DU. Dynamic Data Portion of an Ovation point record that is broadcast periodically in Dynamic Data Blocks (DDBs )by the originating drop and stored in volatile memory. DDB size is configured through the Ovation configuration tools.

E eDB Historian A drop on an Ovation control system that will collect, process, archive, and retrieve information that originates locally or throughout a geographically diverse set of process control sites.

CON_016

121

Glossary of Terms Electronics Module Part of Ovation I/O that contains the electronics for processing I/O signals. Fits into the Base Unit and is typically configured by a Personality Module. EMS Expanded Memory Specification, a bank-switched memory management scheme that allows applications to access vast quantities of memory. Engineering Station An Ovation drop used for configuration and entry of system programs. Known as the Developer Studio in a Windows-based system. Ethernet A standard network protocol. Used to transfer non-time-critical information between drops.

F Fast Ethernet Standard for transmitting data at 100 megabits per second. Similar to FDDI, but uses switches instead of concentrators, and dual-channel Ethernet NIC cards instead of dual-attachment FDDI NIC cards (Contrast to FDDI). FDDI Fiber Distributed Data Interface, a standard for transmitting data. Typically consists of a dual fiber-optic counter-rotating ring capable of carrying synchronous and asynchronous messages. Ring provides automatic “wrap-back” reconfiguration if a segment of the highway fails (Contrast to Fast Ethernet). Firewall Security system intended to protect an organization's computer network from external threats. All communication between the internal computer network and the outside world is routed through a server that determines if a message is safe to pass to the internal network. Flash Data Portion of an Ovation point record that is stored in the originating drop’s flash (or disk) memory and copied to receiving drop’s periodically. Force value To set the value of a coil or contact to a desired state (on/off; 0, 1), regardless of other values in the ladder diagram. FOUNDATION Fieldbus Digital, two-way, multi-drop communication link among intelligent measurement and control devices.

122

CON_016

Glossary of Terms FTP File Transfer Protocol, a set of rules that allows one computer to download a file from another computer via a network connection. Fully qualified point name Point name that specifically identifies a point by combining three parameters. Format is pointname.unit@network where point name contains a maximum of 24 characters, unit contains a maximum of 6 characters, network contains a maximum of 8 characters. Do not use when inserting a new point in Developer Studio, only insert point name parameter.

G Gateway Hardware or software that translates between two dissimilar protocols. GP See Packed Group. Graphics Builder Power Tool used to create and edit System Process Diagrams that display on the Operator Station. GUI Graphical User Interface, an industry-standard term used to describe a user interface based on a windowing system such as Microsoft Windows™.

H Historian Dedicated drop in the Ovation system that collects and stores process point data and other information. Can be an eDB, Ovation Process Historian (OPH), or a third-party historian such as a PI. HMI/MMI Human-Machine Interface/Man-Machine Interface. Refers to drops that provide user interface functions between a user and a machine (such as the Operator Station). Host Any computer on a network that is available for services to other computers. Hypertext Any text that contains “links” to other documents-words or phrases in the document that can be chosen by the reader and which cause another document to be retrieved and displayed.

CON_016

123

Glossary of Terms

I I/O Input/Output, a general term for reading and writing data on a computer. Digitizes information from plant processes and passes it to the Controller for use in control strategies. I/O Builder Power Tool used to define the I/O modules used in an Ovation system. I/O Controller Interface between the Network and the I/O. The Controller is located in the Ovation I/O cabinet. I/O Module Typically made up of an Electronics module and a Personality module. Performs the interface between the I/O Controller and the field devices. I/O Nodes Ovation record types Icon A small graphic on a windowing system display that represents an active process or available function. Typically, an icon can be expanded into a window. Iconic Alarming Provides a mechanism to group alarms based on their priority and their plant area. Each group of alarms is represented by a preconfigured bitmap on the display. Init Tool Initialization Tool. Ovation utility that defines the system drops and the software packages on the drops through the use of GUIs. IOIC Card Generic name for the Ovation I/O Interface card. Also known as PCI card. Options are IOIC, PCQL, PCRL, and PCRR cards. IP Address A unique number consisting of 4 parts separated by dots, (for example, 129.228.36.38). Every computer that is on the Internet has a unique IP address. ISA Industry Standard Architecture, the 8- and 16-bit bus design used in most PCs.

124

CON_016

Glossary of Terms

K KB Kilobyte, A thousand bytes, (actually 1024 bytes).

L Ladder 1) A diagram representing relay-type control logic (see coil, contact). 2) The user's control application program written in a variation of relay logic representation. LAN Local Area Network, A computer network limited to the immediate area, usually the same building. License A necessary permission to use certain Emerson Process Control software products. Log Server Utility used to define and modify custom reports for an Ovation system. Also known as Report Builder or Report Server. Login 1) The account name used to gain access to a computer system. 2) The act of entering into a computer system. Long record type Default record type for Ovation points. Has full alarming and I/O capabilities. Loop 1) A diagram representing a modulating or continuous process control. 2) The modulating control system for a particular physical process. Loop Interface Module (LIM) M/A Station interface connected to QLI card.

M M Port Port on a Concentrator that attaches to a drop or station.

CON_016

125

Glossary of Terms M/A Station Manual/Automatic Station. May be a diagram (sometimes called a “soft” M/A Station) that simulates the functions of a traditional panel-mounted control device. The M/A Station allows the operator to select manual or automatic control of the output, and to manipulate the set point or output value (depending on the selected control mode).

Man pages UNIX on-line documentation for operating system functions. Type “man” and the desired topic. Master Database Contains the entire process database. It is used for creating, modifying, and verifying control strategies and process points. At runtime, it supports queries of the process database, captures changes made to control and point attributes, and propagates those changes to the distributed database. MAU Media Attachment Unit. Interfaces the PCRR card (via the AUI cable) to an Ovation RNC card or a WDPF QOR card. MB Megabyte, A million bytes, a thousand Kilobytes. Menu A screen display representing a set of functions available to the user. Migration Process where Q-Line I/O is interfaced to an Ovation Controller. MMI Data Portion of the Ovation point record that is saved in the Distributed Database in every Ovation workstation. MMI/HMI Man-Machine Interface/Human-Machine Interface. Refers to drops that provide user interface functions between a user and a machine (such as the Operator Station). Modem MOdulator and DEModulator, A device that connects to a computer and to a phone line that allows the computer to talk to other computers through the phone system. Module Point (RM) Ovation record type used to configure and monitor status of Ovation I/O modules.

126

CON_016

Glossary of Terms Monitor 1) To observe the operation of a process without influencing it. 2) A computer terminal or CRT. Multiple Networks Function that enables separate Ovation Networks to communicate with each other, share data, and perform control actions.

N Network Two or more computers connected together so they can share resources. Network Item A subitem of the System item in the Ovation Developer Studio. Only one Network item can exist in the system. The Network item is the parent item to all files, objects, and folders that pertain to the Network. NIC Network Interface Card. Located in Ovation Controller cabinets, Stations, or HMIs. Node 1) Any single computer connected to a network. 2) Active element on an FDDI or Fast Ethernet network that has an address. Can be a station or a concentrator. Up to 1000 nodes are permitted per network. Node Point (RN) Node point is used to configure and monitor PCRL, PCRR, PCRQ cards, and remote I/O nodes.

O OpenWindows A windowing system that runs on a Sun-compatible workstation under SunOs™ or Solaris™. Operator Station A drop in an Ovation system used to control and monitor plant operation. Originated Points Points that were created in the current drop. Ovation I/O Line of Emerson I/O modules.

CON_016

127

Glossary of Terms Ovation Keyboard Also known as the Membrane Keyboard, a specialized keyboard that is connected to an Ovation Operator Station serial port and allows the user to execute a set of standard functions from the keyboard. Ovation Network Redundant, deterministic, high-speed network used for process control. Based on Fast Ethernet standards, it supplies input and output data to all the stations and Controllers connected to it. Ovation System An open architecture Emerson Process Control System that is based on ANSI and ISO network standards. Uses snap-in modules for I/O.

P Packed Digital Point (PD) A point that is a packed digital record type. Holds either 32 separate digital values or two 16-bit register (analog) values. Packed Point A point that is a packed point record type. Packs up to 16 digital (logical) bits in one point record. Each bit may be separately configured for I/O scanning. Can be Long or Deluxe. Password A code used to gain access to a locked system. PC 1) Common acronym for personal computer 2) Common acronym for programmable Controller. PCI Peripheral Component Interconnect. Generic name for the Ovation I/O Interface card. Also known as IOIC card. Options are IOIC, PCQL, PCRL, and PCRR cards. PCL Printer Control Language. Printer language that drives most laser and inkjet printers. PCQL Card Ovation IOIC card used to interface with Q-Line modules. PCRL Card Ovation IOIC card used to interface with local Ovation modules.

128

CON_016

Glossary of Terms PCRR Card Ovation IOIC card used to interface with remote Ovation modules and remote Q-Line I/O modules in migrated systems. PDS Process Diagram System. Contains graphics that are displayed on the Ovation Operator Station. Periodic Points Points whose values are scanned periodically at a defined frequency such as every 1 second or every 0.1 of a second. See also aperiodic points. Personality Module Part of Ovation I/O that configures the Electronics Module. Fits into the Base Unit beside the Electronic Module that it configures. PID Proportional, Integral, Derivative. A type of closed-loop, modulating control function. It acts according to an algorithm that detects deviations between a predetermined setpoint and an actual process variable input condition or value. Plant Mode Defines the current state of a plant (value range 1 - 6). Alarm limits can be defined that are based on plant mode. Can be defined in Deluxe points. Point A record in the Ovation master database containing a value (such as an input or output) and related data. Point Builder Power Tool used to create, modify, and delete Ovation points. Poke Field A location in a diagram where the cursor can be placed, allowing the operator to select an option. Port 1) A connection where information goes into or out of a computer. 2) Translating a piece of software to bring it from one type of computer system to another. Power Tools Set of unified and flexible engineering tools used to configure and maintain the Ovation system. All objects (such as points) created by the tools are stored in a master database.

CON_016

129

Glossary of Terms Process Diagrams Process diagrams are graphical images that represent actual plant process control equipment. Process diagrams display in the Graphics Display System at the Operator Station. Processing time The time, in milliseconds, required to make one complete pass through a Controller application program.

Q Q-Line Legacy line of Emerson I/O modules. Quality Indicates point condition to Operator Station and to the algorithms.

R Radio Button Button appears as a small circle that, when selected, has a smaller, filled circle inside it. Selecting one button in a set deselects the previously selected button so one and only one of the options in a set can be selected at any given time. RAM Random Access Memory, the generic term for memory that can be written to and read from. Received Points Points that were not created in the current drop. Record The set of data associated with a point, including the point name, System ID, value, status, and various other fields, depending on the point record type. Refresh Refreshes the display to the current contents of the object's database values. Register A data storage area in memory. In the Controller, there are four types: input registers (R), output registers (O), holding registers (H), and dynamic holding registers (G). At times, however, input groups (I) and output groups (C) are used as if they were an input or output register. Relational Database Central database (Oracle) for Ovation systems. Uses tables to store and locate information.

130

CON_016

Glossary of Terms Remote I/O A hardware configuration where the I/O is located remotely from the Controller. Remote Node A grouping of I/O modules that communicates with the Controller via media that can carry control signals over a long distance (for example, fiber-optic). Review Data retrieved from the Ovation network. Reviews can be retrieved based on point status requests and/or point characteristics. Ring Set of nodes where data is passed sequentially between nodes, examined or copied, and returned to the originating node. RISC Reduced Instruction-Set Computing, a microprocessor architecture that contains a smaller instruction set in order to increase processor speed. RNC Remote Node Controller (RNC) is an alternate name for the Ovation module containing the Remote Node Electronics module and Remote Node Personality module. The RNC interfaces the I/O modules in the Remote Node to an MAU module at the Controller via a fiber-optic communication link ROM Read-Only Memory, the generic term for memory that can read from but not be written to. ROP I/O hardware transition panel. Router A hardware or software set-up that handles the connection between two or more networks.

S S Port Port on a station that connects to an M port. SAC/SAS Single Attachment Concentrator/Single Attachment Station. Provides a single attachment to the FDDI or Fast Ethernet network.

CON_016

131

Glossary of Terms Scan The processor module's sequential and ongoing examination of each contact circuit, control relay, special function, and process control loop in the application program. During the scan, the processor accesses data stored in memory and the current states of the field I/O. The result is the energizing or de-energizing of the coils and the determination of analog output information. SCSI Small Computer System Interface, a peripheral-connect interface used to connect hard drives, CDROM drives, and other storage devices to a computer. Security Builder (Solaris-based) Ovation Power Tool that defines, configures, and manages security for an Ovation system. Select 1) For control applications, choosing the algorithm to be controlled, typically through an M/A Station. 2) Highlighting an item on the screen, such as an item on a menu or in a scrolling list, as a means of choosing an option. Server A computer, or software program that provides a specific kind of service to a client software running on other computers. Setpoint The desired value of a process variable. In modulating control, other variables are continuously modified to maintain the value of the controlled variable at the setpoint. SGML Standard Generalized Markup Language, a text-based language for describing the content and structure of digital documents. SID See System ID. Simulator Software package that runs on an actual Ovation Controller. Can use either simulated or actual I/O hardware to test control logic. SmartProcess Emerson’s plant optimization software used to improve plant processes. SNMP Simple Network Management Protocol. An Ovation program designed to monitor and report the activity in various devices on the network.

132

CON_016

Glossary of Terms SOE Sequence of Events. SOE messages are transferred from Controllers to certain drops on the network. SoftwareServer A drop on a network that provides storage and control of system software files. Source 1) A location, in memory, that is the origin of the data to be moved or converted. This may be a register or, at times, an input group used as a register. 2) An ASCII input file containing commands or statements in a programming language. Static Data Portion of the Ovation point record that is stored in volatile memory by the originating drop and broadcast to receiving drops on an as-needed basis. The receiving drop stores it in its volatile memory. Station Addressable node on FDDI or Fast Ethernet network; can transmit, repeat, and receive data. SVGA Super Video Graphics Array, an extension of the VGA video standard. SVGA enables video adapters to support up to 16.7 million colors, known as true colors in a 1024-by-768 pixel display. Switch Fast Ethernet device used to connect multiple Ovation Stations to the network. Synchronous High speed data communication that is time critical. Must be guaranteed service for nodes transmitting synchronous data. Typically provided periodically. System ID System Identification number (SID). The Data Highway reference number for each point which may be transmitted. System Item The parent item to all files, objects, and folders that pertain to that System in the Ovation Developer Studio. System Tree The system file structure represented as a hierarchal tree in the Ovation Developer Studio.

CON_016

133

Glossary of Terms

T TCP/IP Transmission Control Protocol / Internet Protocol, a set of communication protocols that allows dissimilar computers to share information over a network. Terminal 1) Solaris window where commands are entered. 2) A device that allows the user to send commands to a remote computer. TIFF Tagged Image File Format, a file format for bit-mapped graphics that stores the information in discrete blocks called tags. TND Remote Node transition panel. Token A field in the Drop Status Record (DSR) that identifies the drop that broadcast a message. Toolbar A row of icons that activate commands or functions when clicked. Trend A display that plots point values over a selected time interval. Trend displays may be generated based on data from the MMI trend history, from a Historian, or from an eDB. Tuning Manually changing the value of point record fields or algorithm record fields.

U Unit Item The subitem of a Network in the Ovation Developer Studio. The Unit item is a parent folder to all files, objects, and folders that pertain to that particular unit. UNIX An operating system used in Ovation drops. Ovation uses the Solaris version of UNIX.

V VGA Video Graphics Array, a standard graphics adapter that enables video adapters to support 16 colors in a 640-by-480 pixel display.

134

CON_016

Glossary of Terms Virtual Controller Software representation of an actual Ovation Controller, where no Controller hardware is required. Virtual Controllers have the same functionality as real Controllers, but do not actually connect to plant I/O and do not have control capabilities.

W Window A screen display using only part of the CRT, often movable and resizable. Windows Microsoft 32-bit multitasking Operating System (such as NT or XP). WYSIWYG What You See Is What You Get, when the appearance of the screen output matches exactly (or very closely) the printed output.

Z Zoom A way of enlarging or reducing a specific area in a graphic.

CON_016

135

Index A A Port • 115 Add Multiple Items dialog box • 81 Admin Tool • 115 Alarm • 115 Algorithm • 115 Analog • 115 Aperiodic Points • 115 API • 115 Application program • 115 Apply • 115 Areas and Sources tab • 87 ASCII • 116 Asynchronous • 116 AUI Cable • 116

B B Port • 116 Bandwidth • 116 Base Alarm System • 116 Base Unit • 116 Baud Rate • 116 BG • 116 Bit • 116 Bitmap file • 116 Bootstrap • 117 Branch • 117 Bridge • 117 Broadcast • 117 Browse Categories dialog box • 90 Browse OPC Alarms and Events / Data Access Server windows • 67 Browsing for Ovation OPC Data Access Servers on a Remote Network • 19 Byte • 117

C Cancel • 117 Categories tab • 86 CDDI • 117 CDE • 117 Characteristics • 117 Client • 117 Client connection and operation • 8 Client Mapper data transfer • 43 Coil • 117 Collision • 118 Collision Detection • 118 Compact I/O Modules • 118

CON_016

Concentrator • 118 Conducting • 118 Configuration • 118 Configuration File • 118 Configuring and customizing the OPC Client Mapper Server • 41 Contact • 118 Control Builder • 118 Control Sheet • 118 Control Task • 118 Controller • 118 Copyright Notice • 2 CPU • 119 CRT • 119 Cursor • 119

D DAC/DAS • 119 Data Highway • 119 Data Structures • 119 Database • 119 DCOM Enhancements • 102 DCS • 119 Deadband • 119 Default installation and custom configurations of the Ovation OPC Client Mapper • 38 Default Points • 119 Default Value • 119 Deluxe record type • 120 Destination • 120 Developer Studio • 120 Device • 120 DHC • 120 Diagnostics • 120 Diagram • 120 Dialog Box • 120 Dialog Boxes for OPC Tools • 66 Digital • 120 DIN • 120 DIP • 120 Discrete I/O • 121 Distributed Database • 121 Distributed I/O • 121 Domain • 121 Download • 121 Drop • 121 Drop Loader • 121 Drop Point (DU) • 121 Dynamic Data • 121

137

Index

E eDB Configuration Information • 28 eDB Historian • 121 Electronics Module • 122 EMS • 122 Engineering Station • 122 Error Codes for the Ovation OPC Data Access Server • 17 Ethernet • 122 External libraries • 7

F Fast Ethernet • 122 FDDI • 122 Files installed during setup • 7 Find dialog box • 81 Firewall • 122 Flash Data • 122 Force value • 122 FOUNDATION Fieldbus • 122 FTP • 123 Fully qualified point name • 123

G Gateway • 123 Generate Items dialog box • 78 GP • 123 Graphics Builder • 123 Group configuration window • 61 Group context menu • 56 Group State dialog box • 73 GUI • 123

H Hardware requirements for the Ovation OPC Data Access Server • 5 Hierarchy browser • 53 Historian • 123 HMI/MMI • 123 Host • 123 Hypertext • 123

I I/O • 124 I/O Builder • 124 I/O Controller • 124 I/O Module • 124 I/O Nodes • 124 Icon • 124 Iconic Alarming • 124 Init Tool • 124 Installation of the Ovation OPC Data Access Server software • 6 IOIC Card • 124

138

IP Address • 124 ISA • 124 Item context menu • 57 Item Properties dialog box • 76 Item State dialog box • 74 Item window • 62

K KB • 125

L Ladder • 125 LAN • 125 License • 125 License limits • 5 License requirements for the Ovation OPC Data Access Server • 5 Licensing the Alarms and Events Server • 27 Local Security Policy Settings • 111 Log Server • 125 Login • 125 Long record type • 125 Loop • 125 Loop Interface Module (LIM) • 125

M M Port • 125 M/A Station • 126 Making connections between OPC Servers and Clients and connection scenarios • 93 Man pages • 126 Master Database • 126 MAU • 126 MB • 126 Menu • 126 Menu Bar • 52 Migration • 126 MMI Data • 126 MMI/HMI • 126 Modem • 126 Module Point (RM) • 126 Monitor • 127 Monitor Events • 66 Monitor items window • 65 Multiple Networks • 127

N Network • 127 Network Item • 127 NIC • 127 Node • 127 Node Point (RN) • 127 Normal Ovation OPC Data Access Server operation • 8

CON_016

Index

O OPC Client tool main window • 51 OPC clients running as an ordinary application on the user desktop • 96 OPC Configuration tool main window • 50 OPC interface functions • 52 OPC Interface windows • 60 OPC introduction • 1 OPC item ID browser • 69 OPC quality • 12 OPC redundancy configuration • 47 OPC redundancy manager • 46 OPC via DCOM with Windows XP Service Pack 2 and Windows 2003 Server Service Pack 1 • 101 OpenWindows • 127 Operating system requirements • 38 Operation of OPC Client Mapper • 44 Operator Event Licenses • 28 Operator Station • 127 Originated Points • 127 Ovation field browser • 71 Ovation I/O • 127 Ovation Keyboard • 128 Ovation Network • 128 Ovation network overview • 2 Ovation OPC Alarm and Events Server • 25 Ovation OPC Client Map Control Panel • 38 Ovation OPC Client Map Service • 37 Ovation OPC Client Mapper • 37 Ovation OPC Client Mapper control panel • 45 Ovation OPC Client/Configuration tools • 49 Ovation OPC Configuration Tool • 38 Ovation OPC Data Access Server • 3 Ovation OPC Data Access Server control panel • 14 Ovation OPC Event Monitor Tool • 31 Ovation point browser • 70 Ovation System • 128

P Packed Digital Point (PD) • 128 Packed Point • 128 Password • 128 PC • 128 PCI • 128 PCL • 128 PCQL Card • 128 PCRL Card • 128 PCRR Card • 129 PDS • 129 Periodic Points • 129 Personality Module • 129 PID • 129

CON_016

Plant Mode • 129 Point • 129 Point Builder • 129 Poke Field • 129 Port • 129 Power Tools • 129 Preferences • 59 Process Diagrams • 130 Processing time • 130

Q Q-Line • 130 Quality • 130

R Radio Button • 130 RAM • 130 Received Points • 130 Record • 130 Refresh • 130 Register • 130 Registry Entries • 18 Relational Database • 130 Relationships between computers involved in OPC communication • 94 Remote I/O • 131 Remote Node • 131 Required information to read or write to an OPC item • 8 Return values for Ovation OPC Data Access Server items • 11 Review • 131 Right-click (context) menus • 54 Ring • 131 RISC • 131 RNC • 131 ROM • 131 Root context menu • 55 ROP • 131 Router • 131

S S Port • 131 SAC/SAS • 131 Scan • 132 SCSI • 132 Security • 93 Security Builder (Solaris-based) • 132 Select • 132 Server • 132 Server configuration window • 60 Server context menu • 55 Server State dialog box • 72 Setpoint • 132

139

Index Setting Security for Windows NT and 2000 • 97 SGML • 132 Shortcut keys • 58 SID • 132 Simulator • 132 Situations where both computers are members of the same Windows domain • 95 SmartProcess • 132 SNMP • 132 SOE • 133 SOE Sequence of Events Licenses • 27 Soft ware requirements for the Ovation OPC Data Access Server • 5 SoftwareServer • 133 Source • 133 Static Data • 133 Station • 133 Status bar • 54 Subscription context menu • 57 Subscription Filter dialog box • 83 Subscription Select Attributes dialog box • 88 Subscription State dialog box • 82 Subscription window • 64 SVGA • 133 Switch • 133 Synchronous • 133 System ID • 133 System Item • 133 System Requirements for the Alarms and Events Server • 28 System Tree • 133

T TCP/IP • 134 Terminal • 134 TIFF • 134 TND • 134 To Access the OPC Client Mapper control panel • 45 To access the Ovation OPC Event Server Main Window • 32 To add a local user to a system that is not used as a domain server • 95 To Add or Configure an Event Subscription • 31 To Change the Client Mapper from a Windows Service to COM Server • 40 To Change the Client Mapper from COM Server to Windows Service • 40 To Change the Ovation OPC Alarms and Events Server from a COM Server to Windows Service • 33

140

To Change the Ovation OPC Alarms and Events Server from a Windows Service to COM Server • 33 To Check the Ovation OPC Alarms and Events Server Status • 32 To Configure DCOM for OPC using XP Service Pack 2 and Windows 2003 Service Pack 1 • 102 To configure Intellution’s iFIX OPC server • 41 To Configure OPC Alarm Client and Event Subscription • 29 To configure Rovisys OPC90 Server • 41 To Configure the Firewall • 107 To configure your OPC system • 41 To Install OPC Alarms and Events Server • 28 To Install OPC Client Mapper from CDROM • 38 To Install the Ovation OPC Data Access Server • 6 To license the Server • 6 To remove Ovation OPC Data Access Server programs • 7 To set Local Security Policy Settings for Domain Machines • 111 To set Local Security Policy Settings for Workgroup Machines as Administrator • 113 To set security • 97 To set up a DCOM server to run as a particular user • 96 To set up a Windows server to execute as a specific user • 95 To start the OPC Client/Configuration tool • 49 To Use the Ovation OPC Data Access Server Control Panel • 14 To View OPC Client Connections • 35 To View or Configure OPC Alarms and Events Server Settings • 34 To View Ovation Alarms and Events Server Version, Start Time Information • 36 Token • 134 Toolbar • 52, 134 Tree structure • 54 Trend • 134 Tuning • 134 Types and Severity tab • 84

U Unit Item • 134 UNIX • 134 Update rate • 12

CON_016

Index

V VGA • 134 View window • 54 Virtual Controller • 135 Visual Basic automation interface for OPC Client • 20 Visual Basic example • 20

W What are Alarms and Events? • 25 What are Condition Events? • 26 What are Simple Events? • 26 What are Tracking Events? • 26 What is Event Subscription? • 27 What is OPC? • 1 What is the OPC Client Mapper? • 37 What is the OPC Client/Configuration tool • 49 What is the Ovation OPC Alarms and Events Server? • 27 What is the Ovation OPC Data Access Server? • 3 Window • 135 Windows • 135 Windows Firewall • 106 Write value to OPC item dialog box • 77 WYSIWYG • 135

Z Zoom • 135

CON_016

141

CON_016 OPC Tools User Guide

Recommend Documents