IEC 61850 Master Protocol OPC ENb PDF

MicroSCADA Pro
IEC 61850 Master Protocol (OPC) *1.1
Users Guide
1MRS755321 MicroSCADA Pro
Issued: 30.06.2004
Version: B/25.02.2005 Users Guide
Contents
1. About this manual .....................................................................7
1.1. Copyrights .....................................................................................7
1.2. Trademarks ...................................................................................7
1.3. General .........................................................................................7
1.4. Use of symbols ..............................................................................8
1.5. Document conventions ..................................................................8
1.6. Terminology ..................................................................................9
1.7. Abbreviations ..............................................................................10
1.8. Related documents .....................................................................11
1.9. Document revisions .....................................................................11
2. Introduction .............................................................................13
2.1. Product overview .........................................................................13
2.2. IEC 61850 OPC Server features .................................................14
3. Engineering .............................................................................15
3.1. Overview of engineering .............................................................15
3.2. Building object tree ......................................................................16
3.2.1. Adding Gateway or Computer Node object .....................18
3.2.2. Adding IEC 61850 OPC Server object .............................18
3.2.3. Adding IEC 61850 Subnetwork objects ...........................19
3.2.4. Adding IEC 61850 IED objects ........................................20
3.3. Configuring objects .....................................................................20
3.3.1. Configuring IEC 61850 OPC Server properties ...............22
3.3.2. Configuring IEC 61850 Subnetwork properties ................24
3.3.2.1. Configuring IEC 61850 Device properties ..........25
3.3.2.2. Configuring Logical Device properties ...............28
3.3.3. Wieving data object configuration ....................................29
3.3.4. Provided viewers ..............................................................30
3.3.5. Configuring report control blocks .....................................32
4. Operation .................................................................................35
4.1. Activating Gateway or OPC server with new configuration .........35
4.1.1. IEC 61850 OPC Server diagnostics .................................35
4.1.2. Diagnostic AE Client ........................................................37
4.2. Monitoring and controlling IEC 61850 subnetwork activity ..........38
4.3. Monitoring and controlling IEC 61850 device communication ....39
4.4. Monitoring and controlling IEC 61850 data object
communication ............................................................................40
5. Technical reference ................................................................41
5.1. IEC 61850 OPC server data object modelling ............................41
Copyright 2005 ABB Oy, Substation Automation Products, Vaasa, FINLAND 3

MicroSCADA Pro 1MRS755321
Users Guide
5.1.1. Common data attribute types .......................................... 41

5.1.1.1. IEC 61850 quality .............................................. 41
5.1.1.2. Mapping quality value to OPC ........................... 42
5.1.1.3. Mapping of DetailedQuality ................................ 42
5.1.1.4. Analogue value (AnalogueValue) ...................... 43
5.1.1.5. Configuration of analogue value
(ScaledValueConfig) .......................................... 43
5.1.1.6. Range configuration (RangeConfig) .................. 44
5.1.1.7. Step position with transient indication
(ValWithTrans) ................................................... 44
5.1.1.8. Pulse configuration (PulseConfig) ..................... 44
5.1.1.9. Originator ........................................................... 45
5.1.1.10.Unit .................................................................... 45
5.1.1.11.Vector ................................................................ 45
5.1.1.12.TimeStamp ........................................................ 45
5.1.1.13.AbbCommandBitmask ....................................... 46
5.1.2. Common data class specifications for status information 46
5.1.2.1. Single point status (SPS) ................................... 46
5.1.2.2. Double point status (DPS) ................................. 47
5.1.2.3. Integer status (INS) ............................................ 48
5.1.2.4. Protection activation information (ACT) ............. 49
5.1.2.5. Directional protection activation information
(ACD) ................................................................. 49
5.1.2.6. Security violation counter (SEC) ........................ 51
5.1.2.7. Binary counter reading (BCR) ............................ 51
5.1.3. Common data class specifications for measured
information ....................................................................... 52
5.1.3.1. Measured value (MV) ........................................ 52
5.1.3.2. Complex measured value (CMV) ....................... 53
5.1.3.3. Sampled value (SAV) ........................................ 54
5.1.3.4. WYE ................................................................... 55
5.1.3.5. Delta (DEL) ........................................................ 56
5.1.3.6. Sequence (SEQ) ................................................ 56
5.1.4. Common data class specifications for controllable status
information ....................................................................... 57
5.1.4.1. Controllable single point (SPC) .......................... 57
5.1.4.2. Controllable double point (DPC) ........................ 59
5.1.4.3. Controllable integer status (INC) ....................... 61
5.1.4.4. Binary controlled step position information
(BSC) ................................................................. 63
5.1.4.5. Integer controlled step position information
(ISC) .................................................................. 65
4
Users Guide
5.1.5. Common data class specifications for controllable

analogue information .......................................................66
5.1.5.1. Analogue set point (APC) ...................................66
5.1.6. Common data class specifications for status settings .....68
5.1.6.1. Single point setting (SPG) ..................................68
5.1.6.2. Integer status setting (ING) ................................68
5.1.7. Common data class specifications for analogue settings 69
5.1.7.1. Analogue setting (ASG) .....................................69
5.1.7.2. Setting curve (CURVE) ......................................69
5.1.8. Common data class specifications for description
information .......................................................................70
5.1.8.1. Device name plate (DPL) ...................................70
5.1.8.2. Logical node name plate (LPL) ..........................71
5.1.9. Application error codes ....................................................72
5.2. Attributes .....................................................................................72
5.2.1. Server attributes ...............................................................73
5.2.2. IEC 61850 line attributes ..................................................75
5.2.3. IEC 61850 device attributes .............................................78
5.2.3.1. Transparent XSAT .............................................82
5.2.4. IEC 61850 logical device attributes ..................................84
5.3. IEC 61850 File Transfer ..............................................................84
5.3.1. File Transfer attributes .....................................................85
5.3.2. File Transfer services .......................................................86
5.3.3. File Transfer service codes ..............................................90
5.4. ACSI conformance statement .....................................................91
5.4.1. ACSI basic conformance statement .................................91
5.4.2. ACSI models conformance statement .............................92
5.4.3. ACSI service conformance statement ..............................94
6. Index .........................................................................................99
5
Users Guide
1. About this manual
1.1. Copyrights
The information in this document is subject to change without notice and should not
be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for
any errors that may appear in this document.
In no event shall ABB Oy be liable for direct, indirect, special, incidental or
consequential damages of any nature or kind arising from the use of this document,
nor shall ABB Oy be liable for incidental or consequential damages arising from
use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written
permission from ABB Oy, and the contents thereof must not be imparted to a third
party nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license
and may be used, copied, or disclosed only in accordance with the terms of such
license.
Copyright 2005 ABB Oy
All rights reserved.
1.2. Trademarks
ABB is a registered trademark of ABB Group.
All other brand or product names mentioned in this document may be trademarks or
registered trademarks of their respective holders.
1.3. General
This users guide describes the IEC 61850 Master Protocol (OPC) *1.1 (later in this
manual IEC 61850 OPC Server) and the central concepts related to it. You will find
instructions on how to configure IEC 61850 OPC Server related objects. The basic
operation procedures are also discussed.
Information in this users guide is intended for application engineers who need to
configure the IEC 61850 OPC Server.
As a prerequisite, you should understand the basic principles and the IEC 61850
technology and standard.
This users guide is divided into following sections:
Introduction
This section gives an overview of the IEC 61850 OPC Server and its features.
Engineering
In this section you will find an overview of the engineering. You are given
instructions on how to configure IEC 61850 OPC Server related objects and the
model of a substation or system.
7

Users Guide
Operation
This section covers the basic operation procedures you can carry out when
transferring or activating the Gateway computer with new configurations. You are
also given instructions on how to monitor and control the condition of connections
in the IEC 61850 network.
Technical reference
This section describes the IEC 61850 data modeling. The section also contains
attributes and a list of status codes.
1.4. Use of symbols

This publication includes information icons that point out important information.
The corresponding icon should be interpreted as follows:
The information icon alerts the reader to relevant facts and

conditions.
1.5. Document conventions

The following conventions are used for the presentation of the material:
The words in names of screen elements (for example, the title in the title bar of a
window, the label for a field of a dialog box) are initially capitalized.
Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example CTRL key. The Enter is an exception, e.g. press Enter.
Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
Press CTRL+C indicates that you must hold down the CTRL key while pressing
the C key (to copy a selected object in this case).
Press ESC E C indicates that you press and release each key in sequence (to copy
a selected object in this case).
The names of push and toggle buttons are boldfaced. For example, click OK.
The names of menus and menu items are boldfaced. For example, the File menu.
The following convention is used for menu operations: Menu Name >
Menu Item > Cascaded Menu Item. For example: select File > Open >
New Project.
The Start menu name always refers to the Start menu on the Windows Task
Bar.
8
Users Guide
System prompts/messages and user responses/input are shown in the Courier

New font. For example, if you enter a value out of range, the following message
is displayed:
Entered value is not valid. The value must be 0 to 30.
You may be told to enter the string MIF349 in a field. The string is shown as
follows in the procedure:
MIF349
Variables are shown using lowercase letters:
sequence name
1.6. Terminology
The following is a list of terms associated with the IEC 61850 OPC Server that you
should be familiar with. The list contains terms that are unique to ABB or have a
usage or definition that is different from standard industry usage.
Term Description
Alarm An abnormal state of a condition.
Alarms and Events An OPC service for providing information about alarms and events
to OPC clients.
Data Access An OPC service for providing information about process data to
OPC clients.
Data Object Part of a logical node object representing specific information, e.g.,
status or measurement. From an object-oriented point of view a
data object is an instance of a class data object. DOs are normally
used as transaction objects; i.e., they are data structures.
Data Set The data set is the content basis for reporting and logging. The
data set contain references to the data and data attribute values.
Device A physical device that behaves as its own communication node in

the network, e.g. protection relay.
Event Change of process data or an OPC internal value. Normally, an

event consists of value, quality and timestamp.
Intelligent Electronic A physical IEC 61850 device that behaves as its own
Device communication node in the IEC 61850 protocol.
Logical Device Representation of a group of functions. Each function is defined as

a logical node. A physical device consists of one or several LDs.
Logical Node The smallest part of a function that exchanges data. A LN is an

object defined by its data and methods.
OPC item Representation of connections to data sources, i.e., object

properties. An OPC item is identified by a string <object
path>:<property name>. Associated with each OPC item are
Value, Quality and Time Stamp.
Property Named data item
9

Users Guide
Term Description
Report Control Block The report control block controls the reporting process for event
data as they occur. The reporting process continues as long as the
communication is available.
Substation XML-based description language for configurations of electrical

Configuration substation IEDs. Defined in IEC 61850 standard.
Language; SCL
1.7. Abbreviations
The following is a list of abbreviations associated with the IEC 61850 OPC Server
that you should be familiar with. See also the terminology table above.
Abbreviation Description
AE Alarms and Events
BRCB Buffered Report Control Block
CET Communication Engineering Tool
DA Data Access
DMCD Data Message Code Definition
DO Data Object
GW Gateway, component connecting two communication networks

together
IED Intelligent Electronic Device
LD Logical Device
LN Logical Node
NV Network Variable
OLE Object Linking and Embedding
OPC OLE for Process Control
SCL Substation Configuration Language defined by IEC 61850
SNTP Simple Network Time Protocol
SOAP Simple Object Access Protocol
RCB Report Control Block
URCB Unbuffered Report Control Block
XML eXtended Markup Language
10
Users Guide
1.8. Related documents

When you are using COM 610, the following manual should be available for
reference during the use of this manual:
Title MRS number Description
MicroSCADA Pro 1MRS755385 Users Guide for engineering and

Communication Gateway operating Communication Gateway
COM 610 *2.1 COM 610 and central concepts related
Users Guide to it.
1.9. Document revisions
Version Revision number Date History

A 1.0 30.06.2004 Document created
B 1.1 25.02.2005 File Transfer function additions
11
Users Guide
2. Introduction
2.1. Product overview

The IEC 61850 OPC Server enables OPC clients to access process data from IEC
61850 devices.
Network Control Center

(NCC)
Communication Engineering Tool

(CET)
COM 610 with

IEC 61850 OPC Server
MicroSCADA Pro with

Ethernet switch
Protection and control devices

communicating through IEC 61850
protocol
A050166
Fig. 2.1.-1 IEC 61850 OPC Server system overview

The IEC 61850 OPC server can be used as a part of the COM 610 Gateway or as a
part of the MicroSCADA Pro system (see Fig. 2.1.-1).
To create a common data interface between the OPC server and client, the process
data is modelled using the IEC 61850 protocol. The IEC 61850 protocol is a set of
specifications, which details layered substation communication architecture. The
International Standard IEC 61850 has been prepared by IEC technical committee 57:
Power system control and associated communications.
The IEC 61850 specifies usage of Manufacturing Message Specification (MMS,
ISO 9506) over TCP/IP as communication between the IEC 61850 server and client
(device/IEC 61850 OPC Server).
After the IEC 61850 OPC Server and other required components are installed, you
can build and configure hierarchically structured models of a substation or a system
for the IEC 61850 OPC Server using a Communication Engineering Tool (CET)
configuration files and device.
The configuration data is stored in SCL (XML based) format. After the IEC 61850
OPC Server has been launched, it reads the configuration file and establishes
communication with the IEC 61850 devices through the IEC 61850 protocol stack.
13
Product Type MicroSCADA Pro 1MRS755321

Users Guide
Configured IEC 61850 devices and their data are then exposed to OPC clients
through an OPC Data Access (DA) server and device reported changes in data with
DA subscription are reported to OPC clients.
2.2. IEC 61850 OPC Server features

The IEC 61850 OPC Server supports the following features:
Communication diagnostics
OPC Data Access v. 1.0/2.0 and OPC Alarms and Events specifications
IEC 61850 data modelling
System supervision:
IEC 61850 device communication
Command handling:
The IEC 61850 OPC Server supports the IEC 61850 command services.
IEC 61850 data objects:
SPS, DPS, INS, ACT, ACD, SEC, BCR, MV, CMV, SAV, WYE, DEL, SEQ,
SPC, DPC, BSC, ISC, APC, SPG, ING, ASG, CURVE, DPL, LPL.
IEC 61850 buffered and unbuffered reporting services
IEC 61850 File Transfer
Time synchronization:
The IEC 61850 OPC Server can act as an SNTP client and server for time
synchronization. When the IEC 61850 OPC Server is configured for
receiving time synchronization, it updates the operating system time of the
PC.
Multiple instance support
14
Users Guide
3. Engineering
This chapter guides you in the engineering tasks required before you can start using
the IEC 61850 OPC Server. For information on the IEC 61850 data modelling, refer
to the respective standards and specifications.
Both COM 610 and MicroSCADA Pro includes Communication Engineering Tool
(CET). All tasks introduced in this chapter apply for both COM 610 CET and
MicroSCADA Pro CET. If there are differences between these two CETs, you are
informed about these differences. First you need to start the COM 610 or
MicroSCADA Pro Communication Engineering Tool (CET) to open and name a
project.
3.1. Overview of engineering

The engineering work can be divided into two separate tasks:
1. building an object tree
2. configuring object properties
First, you need to build an object tree. This is done by adding objects to the object
tree, refer to Section 3.2. Building object tree. Connectivity Packages for certain
protection and control products usually contain preconfigurations and tools to
facilitate the building of the object tree.
Table 3.1.-1 describes the possible objects shown in the object tree. After you have
added the necessary objects to the object tree in the Communication structure, you
need to configure them, refer to Section 3.3. Configuring objects.
Table 3.1.-1 IEC 61850 OPC Server related objects
Object Description
IEC 61850 OPC Object representing the IEC 61850 OPC Server
Server
Event Definitions Object representing event definitions for IEC 61850 OPC Server
diagnostics
IEC 61850 Object representing a physical subnetwork. IEC 61850 OPC

Subnetwork Server supports only one subnetwork.
IEC 61850 Device Object representing a physical IEC 61850 protection and control
(IEC 61850 IED) device. You should not have more than 30 devices per each
subnetwork.
Attributes Predefined object that contains items for controlling or retrieving

status information for the parent object. The parent object can be
the Server, a Subnetwork or a Device object.
Logical Device (LD) Object representing a group of functions, each function is defined
as a logical node. A physical device consists of one or several
LDs.
Logical Node (LN) An object defined by its data and methods. LN is the smallest part
of a function that exchanges data.
15
Users Guide
Table 3.1.-1 IEC 61850 OPC Server related objects (Continued)
Object Description
Data Object (DO) A data object is an instance of one of the IEC 61850 Common
Data Classes, for example single point status, measured value
etc. Depending on the class, each data object has a set of
attributes for monitoring and controlling the object, for instance
value, quality and control.
Data Set (DS) The data set is the content basis for reporting and logging. The
data set contain references to the data and data attribute values.
Report Control The report control block controls the reporting process for event
Block (RCB) data as they occur. The reporting process continues as long as
the communication is available.
3.2. Building object tree

Before you can start using the IEC 61850 OPC Server, you need to build and
configure an object tree in Communication Engineering Tool (CET) to define the
Communication structure.
The Fig. 3.2.-1 shows an example of how the object tree may look like after it has
been built. In the example tree you can see the IEC 61850 OPC Server object and its
child objects like subnetworks, devices and data objects. Indentation is used to
indicate the parent-child relationship between the objects.
16
Users Guide
IECCETMain
Fig. 3.2.-1 Example view of the COM 610 Communication Engineering Tool
You have several possible ways to add objects to the object tree in the
Communication structure:
You can right-click the object to which you want to add a child object.
You can copy the object.
You can drag and drop the object.
Add the objects in the following order:
1. Gateway (COM 610) or Computer Node (MicroSCADA Pro)
2. IEC 61850 OPC Server
3. IEC 61850 Subnetwork
4. IEC 61850 Device (IEC 61850 IED)
5. Import devices configurations
If you want to connect Device Connection Status events to device

objects at this point, make sure that you have already created and
configured the event objects.
17
Users Guide
3.2.1. Adding Gateway or Computer Node object

1. To start building the object tree, add a COM 610 Gateway object in the
Communication structure by selecting the project name.
2. Right-click the project name and select New > Communication > Gateway,
see Fig. 3.2.1.-1.
Continue building the object tree in the same way until you have added all the
necessary objects in your current project.
This applies similarly to the MicroSCADA Pro CET.
IECGate
Fig. 3.2.1.-1 Adding a COM 610 Gateway object
3.2.2. Adding IEC 61850 OPC Server object

After the Gateway object has been successfully added, you can continue building the
object tree by adding an IEC 61850 OPC Server object.
To add an IEC 61850 OPC Server object:
1. Select the Gateway object in the Communication structure
2. Right-click the Gateway object.
3. Add an IEC 61850 OPC Server object.
By using the SCL Import function, it is possible to import configurations of an entire
server or individual devices without having to insert them manually.
To open the SCL Import function
1. Click the wanted object.
2. Select Tools > SCL Import.
Connectivity Packages for certain protection and control devices may also support
other ways to build this structure, depending on the configuration of an individual
device, for example device-related object types and wizards. Typically,
Connectivity Packages include SCL description files which need to be installed. For
further information on these Connectivity Packages, see the Connectivity Package
of a certain device in the product documentation.
18
Users Guide
You can also import the whole communication structure under IEC 61850 OPC
Server with new configurations from an existing file. This is done by SCL import
function. The file extentions for the import files can be .icd, .cid, .scd or .xml. Right-
click the IEC 61850 OPC Server and select SCL Import from the shortcut menu,
see Fig. 3.2.2.-1.
To import a new configuration file:
1. Click Choose File.
2. Browse to a new configuration file from the appearing dialo.g
3. Select the file and click Open.
4. Select the device to import from the drop-down list. You can preview the
configuration on the right.
5. Click Import.
The new preconfigurated objects appear in the object tree. If the configuration file
is very large, the import may take time. To import a configuration file for a different
OPC Server, right-click the OPC Server, select SCL Import again, and repeat the
steps above.
SCLImport
Fig. 3.2.2.-1 IEC 61850 OPC Server SCL Import
3.2.3. Adding IEC 61850 Subnetwork objects

After the server object has been successfully added, you can continue building the
object tree by adding an IEC 61850 Subnetwork objects.
To add an IEC 61850 Subnetwork object:

1. Select an IEC 61850 OPC Server object
2. Right-click the IEC 61850 OPC Server object.
3. Add an IEC 61850 Subnetwork object.
19
Users Guide
4. Rename the new object. Note that the name of the IEC 61850 Subnetwork have
to be unique.
Note! You can define one subnetwork per OPC Server.
3.2.4. Adding IEC 61850 IED objects

After adding a subnetwork you can add device objects.
To add a Device object:
1. Select a Subnetwork object.
2. Add an IEC 61850 Device (IEC 61850 IED) object.
3. Rename the new object. Note that the names of the devices within an IEC 61850
Subnetwork have to be unique.
You should not have more than 30 devices per each subnetwork.L
With SCL import function you can import new objects with configurations from an
existing file. Right-click the device and select SCL Import from the shortcut menu,
see Fig. 3.2.2.-1.
2. Browse to a new configuration file from the appearing dialog.
5. Click Import.
is very large, the import may take time. To import a configuration file for a different
device, right-click the device, select SCL Import again and repeat the steps above.
3.3. Configuring objects

After the objects have been added, you need to configure the object properties.
To configure an object:
1. Select an object in the object tree of the Communication structure.
2. The object properties appear now in the Object Properties window, see Fig. 3.3.-
1. You can see the selected object on the left and the available properties on the
right.
3. Select the property you want to configure. Depending on the property value
type, configuring is always done either by
selecting a predefined value from a drop-down combo box, or
entering a text string or a numerical value in a text field.
With SCL import function you can import new objects with configurations from an
existing file. Right-click the device and select SCL Import from the shortcut menu,
see Fig. 3.2.2.-1.
20
Users Guide

2. Browse to a new configuration file from the appearing dialog.
5. Click Import.
is very large the import may take time. To import a configuration file for a different
device,right-click the device, select SCL Import again and repeat the steps above.
IECObjProp
Fig. 3.3.-1 Example of object properties

The available properties for different objects are listed in the following subsections.
21
Users Guide
3.3.1. Configuring IEC 61850 OPC Server properties

Table 3.3.1-1 lists the configurable IEC 61850 OPC Server properties and value
ranges for them. The actual configuration by using Communication Engineering
Tool (CET) is performed as described on Section 3.3. Configuring objects.
Table 3.3.1-1 IEC 61850 OPC Server properties
Name Value/Value range Description
Basic
AE Prog ID Prog ID for OPC Alarm and Event Server

(Automatically generated by management
function)
DA Prog ID Prog ID for OPC Data Access Server
SNTP Client
1. Address for IP address or node name for SNTP Server

SNTP Server (Primary)
1. Port Number (1..65535) TCP/IP port number

Default: 123
1. (0..3600) Time syncronization interval in seconds. If

Synchronization Default: 15 value is 0, no time syncronization will be done.
Interval

SNTP Server
2. Port Number (1...65535) TCP/IP port number

Default: 123
2. (0..3600) Time synchronization interval in seconds. If

Interval

SNTP Server
Default: 123

Interval

SNTP Server

Default: 123

Interval
SNTP Enable True Controls if time synchronization client is initially
Client False in use or not
Default: True
22
Users Guide
Table 3.3.1-1 IEC 61850 OPC Server properties (Continued)
Name Value/Value range Description
SNTP Server
Enable Time True Controls if time synchronization server is

Synchronization False initially in use or not
server Default: True
Port Number For (1...65535) Port number for time synchronization server
Time Default: 123
Synchronization
Server
Communication Control
Report Control HSI1 Report Control Identity specifies, which report

Identity HSI2 control block instance is used by the OPC
GW1 Server. The value must match with the Report
GW2 Client attribute under the Report Enabled
(or free string) attribute of the report control block to be used.
Default: GW1
To enable the IEC 61850 OPC Server to use
the specific report control blocks and therefore
receive spontanious events, the Report Control
Identity field must match with one of the Report
enabled fields on devices report control block
configurations. This dedicates a report control
blocks specific instance from the device to be
used by the IEC 61850 OPC Server. If the
fields do not match, the configured report
control block is discarded.
Server Control operation Specifies the default originator category that is

Originator issued from an used for changing values and IEC 61850
Category operator using a client control services. This can be override by OPC
located at station level client for DPC control.
Control operation
issued from an
unknown location
Control operation from

a remote operater
outside the substation
(for example network
control center)
Default: Control
operation issued from
an operator using a
client located at station
level
23
Users Guide
3.3.2. Configuring IEC 61850 Subnetwork properties

The IEC 61850 Subnetwork properties that can be configured and value ranges for
them can be found in Table 3.3.2-1. The actual configuration by using the
Communication Engineering Tool (CET) is performed as described on Section 3.3.
Configuring objects.
Each IEC 61850 node of the system must have a unique subnet/
node address.
Table 3.3.2-1 IEC 61850 Subnetwork properties
Property/ Value or Value

Description
Parameter range/ Default
Basic
In Use In Use Controls whether the device communication

Not In Use is initially in use or not
Default: In Use
Communication Port
IP Address 127.0.0.1 IP Address for communication channel.

Dotted decimal to be used.
OSI ACSE AE 23 OSI ACSE AE Qualifier as defined in IEC

Qualifier 61850-8-1
OSI ACSE AP 1,3,9999,23 OSI ACSE AP Title Value as defined in IEC

Title Value 61850-8-1
OSI Presentation 0001 OSI Presentation Selector as defined in IEC

Selector 61850-8-1
OSI Session 0001 OSI Session Selector as defined in IEC

Selector 61850-8-1
OSI Transport 00000001 OSI Transport Selector as defined in IEC

Selector 61850-8-1
24
Users Guide
Table 3.3.2-1 IEC 61850 Subnetwork properties (Continued)
Property/ Value or Value

Description
Parameter range/ Default
System Event Disabled Level of system events (OPC AE events)

Level can be viewed with an OPC AE client or with
Level 1 (main a CET Diagnostic AE client for OPC Server.
operation and errors) Amount of events sent is cumulative: higher
level also contains lower level events.
Level 2 (time System event level configuration at
synchronization subnetwork overrides definitions at device
errors) level. Same or higher event level must be
set for Subnetwork as for IED.
Level 3 (time
synchronization System events can be used for debugging
done) and event flow monitoring, see Table
3.3.2.1-1 System Event Level. Event level
Level 4 (reported can be changed during the runtime by using
local updates from the Diagnostic events level attribute, see
devices) Table 5.2.2-1 Diagnostic events level.
Level 5 (reported
unconfigured
updates from
devices)
Default: Disabled
TCP/IP (1..3600) TCP/IP Keepalive time-out in seconds

Keepalive Time- Default: 15
out
3.3.2.1. Configuring IEC 61850 Device properties

Table 3.3.2.1-1 lists the configurable properties for IEC 61850 Device (used for
ABB protection and control devices) and value ranges for these properties. The
actual configuration by using the Communication Engineering Tool (CET) is
performed as described on Section 3.3. Configuring objects.
Each IEC 61850 node of the system must have a unique subnet or
node address.
Table 3.3.2.1-1 IEC 61850 Device properties
Value or Value range/

Name Description
Default
Basic
In Use In use Controls if the device communication is

Not in use initially in use or not.
Default: In use
25
Users Guide
Table 3.3.2.1-1 IEC 61850 Device properties (Continued)

Name Description
Default
Simulation Mode True Defines if the device is in simulation mode.

False
Default: False
System Event Level0=Disabled Level of system events (OPC AE events) can

Level be viewed with a CET Diagnostic AE client for
Level1=Level 1 (main OPC Server or with an OPC AE client. Amount
operation, error of events sent is cumulative: higher level also
replies, errors) contains lower level events. System event
level configuration at subnetwork overrides
Level2=Level 2 definitions at device level. The same or higher
(information reports, event level must be set for Subnetwork as for
OK replies, RCB IED.
initializing)
System events can be used for debugging and
Level3=Level 3 (sent event flow monitoring, see Table 3.3.2-1
requests (connect, System Event Level. Event level can be
read, write), changed during the run time by using the
transparent SPA Diagnostic events level attribute, see Table
messages) 5.2.3-1 Diagnostic events level.
Level4=Level 4
(reported local
updates)
Level5=Level 5
(reported unconfigured
updates)
Addresses
IP Address 127.0.0.1 IEC 61850 Node Number of the device
OSI ACSE AE 23 IEC 61850 Subnet Number of the device

Qualifier
OSI ACSE AP 1,3,9999,23 OSI ACSE AP Title Value as defined in IEC

Title Value 61850-8-1.
OSI Presentation 00000001 OSI Presentation Selector as defined in IEC

Selector 61850-8-1.
OSI Session 0001 OSI Session Selector as defined in IEC 61850-

Selector 8-1.
OSI Transport 0001 OSI Transport Selector as defined in IEC

Selector 61850-8-1.
Configuration Shall be empty if the Location for checking configuration revision for
Revision Check configuration check is IED before establishing communication. The
Location not in use. format is Logical Device Name\Logical Node
Name\Data Object Name\Attribute Name e.g.
LD1\LLN0\NamPlt\configRev
26
Users Guide

Name Description
Default
Enable EntryID True Enable reporting EntryID check. Report

Check False EntryIDs are used as sequence numbers for
Default: False buffered reporting. A gab in sequence
numbers caused a restart of reporting starting
from lost sequence number.
Report Control True Initialize to report control blocks and enable

Block Initialize False reporting.
Default: True
Use 32 Bit Entry True Enables or disables usage of 32 bit EntryIDs

ID False for information report sequence.
Default: False
The IEC 61850 standard defines 64 bit
EntryID, but e.g. SPA-ZC 40x uses 32 bit
EntryID.
Use Sequence True Enables or disables sequence number

Number Check False checking information reports for the IEC 61850
Default: False OPC server.
MMS Request 0...60000 Timeout for the MMS level is requested in

Timeout 0 = disabled milliseconds (msec).
Default: 5000
Polling
Polling Timeout (0..3600) Polling Timeout in seconds. If the device does

Default: 0 (disabled) not support reporting, ST and MX attributes
can be polled with this interval.
Control Authorization
Station/Remote OPC path of the station remote switch position

Switch OPC Path to be used with this device. The format is
Node#ProgID For OPC Server#Channel
Name\\IED Name\\Logical Device
Name\\Logical Node Name\\Data Object
Name E.g.
GW#ABB.IEC61850_OPC_DA_Server.Instanc
e[1]1#Channel1\\IED1\\LD1\\GGIO1\\loc
27
Users Guide

Name Description
Default
Configuration
Dynamically Controls dynamic dataset creation to the

Create Data Sets device.
When the dynamic dataset is created and the

connection is established, the IEC 61850 OPC
server creates all configured datasets to the
device and initializes the dedicated report
control blocks according to the configuration.
Dynamic datasets can be created persistent or

non-persistent. This attribute is configured with
the dataset name. Non-persistent datasets are
destroyed in the device when communication
is lost and persistent datasets remain.
@DatasetName =
Non-persistent NVL, AA-specific
/DatasetName = Persistent NVL, VMD specific
DataSetName = Persistent NVL, DOMAIN
specific
Refer to the IED manuals, if IED supports the

dynamic dataset creation services.
3.3.2.2. Configuring Logical Device properties

The logical devices are already configurated when they are imported with IEC61850
devices. The configurations can be monitored with viewers, refer to Section 3.3.4.
Provided viewers.
Table 3.3.2.2-1 Logical Device properties

Name Description
Default
Transparent SPA
SPA Address (0..999) The SPA address of the device connected via
Default: 0 TCP/IP.
By setting value >0 enables the built in TCP/

SPA client, wich can be used through the
Transparent SPA attribute, see Table 5.2.4-1.
SPA TCP Port (1..65535) SPA TCP Port

Default: 7001
SPA TCP (1..65535) SPA TCP Timeout in seconds

Timeout Default: 15
28
Users Guide
Table 3.3.2.2-1 Logical Device properties (Continued)
Control Authorization
Station/Remote Station/Remote Switch OPC Path

Switch OPC OPC path of the station remote switch position
Path to be used with this device. The format is
Node#ProgID For OPC Server#Channel
Name\IED Name\Logical Device Name\Logical
Node Name\Data Object Name E.g.
GW#ABB.IEC61850_OPC_DA_Server.Instanc
e[1]#Channel1\IED1\LD1\GGIO1\loc
3.3.3. Wieving data object configuration

IEC 61850 OPC Server supports data objects for status, measurand, controllable
status, and controllable analog information. IEC 61850 OPC Server supports 28 data
object types for an IEC 61850 Device. The data objects are already configurated
when they are imported with IEC 61850 devices. The configurations can be
monitored with viewers, refer to Section 3.3.4. Provided viewers.
Data classes for status information:
Single point status (SPS)
Double point status (DPS)
Integer status (INS)
Protection activation information (ACT)
Directional protection activation information (ACD)
Security violation counter (SEC)
Binary counter reading (BCR)
Data classes for measurand information:
Measured value (MV)
Complex measured value (CMV)
Sampled value (SAV)
WYE
Delta (DEL)
Sequence (SEQ)
Data classes for controllable status information:
Controllable single point (SPC)
Controllable double point (DPC)
Controllable integer status (INC)
Binary controlled step position information (BSC)
Integer controlled step position information (ISC)
Data classes for controllable analog information:
Analog set point (APC)
Data objects classes for status settings:
29
Users Guide
Single setting point (SPG)

Integer status setting (ING)
Data classes for analogue settings:
Analogue setting (ASG)
Setting curve (CURVE)
Data classes classes for description information:
Device name plate (DPL)
Logical Node name plate (LPL)
Data classes classes for internal status information:
Integer status (Internal INS)
Single point status (Internal SPS)
Controllable single point (Internal SPC)
The parameters are stored in object properties in the Communication Engineering
Tool (CET). The actual configuration for data objects is not supported.
3.3.4. Provided viewers

You can view configurated data object types, data attribute types and enumerated
attributes with provided viewers for IEC 61850 OPC Server.
To view data object type viewer:
1. Right-click the IEC 61850 OPC Server.
2. Select DOType Viewer from the shortcut menu.
With DOType Viewer you can view the attributes of the DOtypes under the IEC
61850 OPC Server in the communication structure. From the DOType drop-down
menu you can select the data object types to view, see Fig. 3.3.4.-1.
DOTypeView
Fig. 3.3.4.-1 IEC 61850 OPC Server DOType Viewer

To view data attribute type viewer:
2. Select DAType Viewer from the shortcut menu.
With DAType Viewer you can view the attributes of the DAtypes under the IEC
61850 OPC Server in the communication structure. From the DAType drop-down
menu you can select the data attribute types to view, see Fig. 3.3.4.-2.
30
Users Guide
DATypeView
Fig. 3.3.4.-2 IEC 61850 OPC Server DAType Viewer

To view enumerated basic type attributes:
2. Select Enum Viewer from the shortcut menu.
With Enum Viewer you can view the enumeration of EnumTypes under the IEC
61850 OPC Server in the communication structure. From the EnumType drop-down
menu you can select the enumerated basic type attributes to view, see Fig. 3.3.4.-3.
EnumView
Fig. 3.3.4.-3 IEC 61850 OPC Server Enum Viewer

With DOI Editor you can override the data objects default values if necessary, see
Fig. 3.3.4.-4. Refer to IEC standards IEC 61850-6 and IEC 61850-7-3.
31
Users Guide
DOIEdit
Fig. 3.3.4.-4 DOI Editor
3.3.5. Configuring report control blocks

A report control block (RCB) controls the spontaneous event reporting, and the
client can modify report sending behaviour by setting RCB attributes. Buffered
Report Control Blocks (BRCB) and Unbuffered Report Control Blocks (URCB) are
supported RCBs.
For BRCB, events issue immediate sending of reports or buffer the events for
transmission, such that data values are not lost due to transport flow control
constraints or loss of connection. For URCB, events issue immediate sending of
reports on a best efforts basis. If no association exists or if the transport data flow is
not fast enough to support it, events may be lost.
To allow multiple clients to receive the same data values, multiple instances of the
report control classes need to be made available. Report Enabled and Report Client
definitions are used to specify RCB instances to clients. Report Enabled shows the
maximum number of available RCB instances, and Report Client dedicates an
instance to a client (see Table 3.3.1-1 Report Control Identity). All configured RCBs
without IEC 61850 OPC Server specified instances are discarded.
Report Clients order specifies the RCB instance to be used and the RCB name. IEC
61850 OPC Server builts the RCB instance name to type RCBName<xx>. Each
RCB instance takes on the values from 01 to 99 as <xx>, for example the first Report
Client uses RCBName01. The naming convention can also be overriden by
removing the Report Enabled element. Now the RCBName is used as it is.
The control attribute values are received from the imported device configuration.
Some values can be overriden with the IEC 61850 OPC Server configuration.
Buffer Time
Controls the time interval in milliseconds when the BRCB buffers the events for
inclusion into a single report. Overridable.
Buffered
Controls RCB to to buffered (true) or unbuffered (false). Must be true for BRCB.
32
Users Guide
Configuration Revision
Represents the number of times that the configuration of the RCB has changed.
Data Set
Specifies the data set being monitored and what values are reported.
Integrity period
If this is set to integrity (>0), it indicates the period in milliseconds used for
generating an integrity report. An integrity report shall report the values of all
members of the related data set. Overridable.
Report ID
Report identifier is the BRCBs client-specified report identifier. Report
identifier generates the report.
Option Fields
Client specified optional fields to be included in the report issued by BRCB. This
attribute defines the optional header fields subset of the report that are included
in the report. Refer to IEC 61850-7-2 and IEC 61850-8-1 standards. The
IEC 61850 OPC Server uses a default value for option fields to receive the
necessary information for event updates and event flow control (cannot be
overriden):
BRCB (Sequence Number, Reason Code, Buffer Overflow, Entry ID),
URCB (Sequence Number, Reason Code). Overridable.
Trigger Options
Specifies the trigger conditions which BRCB monitores. The following values
are defined: Data Change(dchg), Quality Change(qchg), Data Update(dupd),
Period.
Buffer time and Integrity period are overridable. Option fields are also overridable,
except the default values that IEC 61850 OPC Server uses to receive the necessary
information for event updates and event flow control.
33
Users Guide
4. Operation
This section describes the basic operation procedures you can carry out after the
object properties for the IEC 61850 OPC Server have been configured.
4.1. Activating Gateway or OPC server with new configuration

Normally the IEC 61850 OPC server starts automatically when the first client
connects to it and shuts down when the last client disconnects.
You can either update the configuration files to the Gateway or restart the OPC
server with the management function. This is done by clicking the respective
buttons. Fig. 4.1.-1 shows the Gateway Management function for the IEC 61850
OPC Server. For more detailed information, see Communication Gateway COM
610 *2.0 Users Guide.
GWManage
Fig. 4.1.-1 COM 610 Gateway Management function
4.1.1. IEC 61850 OPC Server diagnostics

After the IEC 61850 OPC Server has been installed and configured, you can, for
example, monitor and control the condition of connections in an IEC 61850
network.
This is done by using the Online Diagnostics function in the Communication
Engineering Tool (CET), select Tools > Online Diagnostics or select the object,
right-click the IEC 61850 Server object and select Online Diagnostics from the
shortcut menu, see Fig. 4.1.1.-1.
The server, a device or data object is dragged and dropped from the Project
Explorers Communication structure under the Online Diagnostics function. Select
the Project Explorer from the View menu if it is not already open.
35

Users Guide
OPCDiag
Fig. 4.1.1.-1 IEC 61850 OPC Server Online Diagnostics

You have the following alternatives:
to reset counters (restart the OPC server)
to view the event log file
to clear the log file
to reconnect the online diagnostics
enable or disable the SNTP client
36
Users Guide
EventLog
Fig. 4.1.1.-2 Event log file
4.1.2. Diagnostic AE Client

Diagnostic events can be monitored and controlled using the Diagnostic AE Client
function, see Fig. 4.1.2.-1. Click Refresh to update the status information. To be
able to receive events from a certain device, diagnostic events must be enabled for
this device.
To enable diagnostic events:
1. Right-click the device.
2. Select Diagnostic AE client.
DiagAEClient
Fig. 4.1.2.-1 IEC 61850 OPC Server Diagnostic AE client
37

Users Guide
4.2. Monitoring and controlling IEC 61850 subnetwork activity

The IEC 61850 subnetwork activity can be monitored with the Online Diagnostics
function.
You can also take a subnetwork into use or out of use.
To monitor and control IEC 61850 subnetwork activity
1. Select the subnetwork you want to monitor in the object tree of the
Communication Engineering Tool (CET).
2. Right-click the channel.
3. Select Online Diagnostics.
SubDiag
Fig. 4.2.-1 IEC 61850 subnetwork Online Diagnostics

In the Diagnostic counters field, you can monitor the subnetwork activity and the
available properties, see Fig. 4.2.-1. To reset Diagnostic counters, click Reset
counters.
You can take an IEC 61850 subnetwork into use by selecting the In Use check box.
If you clear the check box, the subnetwork is taken out of use. To update the
diagnostic counters click Refresh.
38
Users Guide
4.3. Monitoring and controlling IEC 61850 device communication

The IEC 61850 device communication can be monitored with the Online
Diagnostics function.
To monitor and control IEC 61850 device communication:
1. Select the device you want to monitor in the object tree of the Communication
Engineering Tool (CET).
In the Status information field, you can monitor the device status. The Diagnostic
counters field provides information on device activity. To reset diagnostic counters,
click Reset counters. To update the diagnostic counters click Refresh.
You can take an IEC 61850 device into use by selecting the In Use check box. If you
clear the check box, the device is taken out of use.
DeviceDiag
Fig. 4.3.-1 IEC 61850 Device Online Diagnostics
39

Users Guide
4.4. Monitoring and controlling IEC 61850 data object

communication
The IEC 61850 data object diagnostics can be monitored with the Online
Diagnostics function.
To monitor and control IEC 61850 data object communication:
1. Select the data object you want to monitor in the object tree.
In the Status information field, you can monitor and set attribute values and use
control services. The Diagnostic counters field provides information on device
activity.
40
Users Guide
5. Technical reference
This document describes how IEC-61850 data objects according to IEC-61850-7-3
are mapped to OPC nodes and item tags.
In general it is done by using an OPC node to represent an IEC-61850 object, and
OPC item tags to represent the attributes of the object. Most objects are single-level
(i.e. use only on node) but some are hierarchical and use several nodes.
This section provides reference information about the following issues:
IEC 61850 data object modelling
IEC 61850 OPC Server data object modelling
Attributes
Status codes
5.1. IEC 61850 OPC server data object modelling
5.1.1. Common data attribute types

The relationship between IEC 61850 data models and the LON OPC Server is
described in this section.
For each data class, there is a table giving a detailed description about the relation
between the LON data and the IEC 61850 data object attributes and services. The
tables also describe how the data is presented on the OPC Server name space.
The columns in the tables have the following content types:
Name specifies the OPC item name of the attribute or service.
Type specifies the IEC 61850 type of the attribute.
Value/Value range specifies the allowed values and ranges of the attribute or
service.
Mandatory/Optional specifies whether the attribute is considered as mandatory
or optional according to the IEC 61850 standard.
OPC data type specifies the OPC data type used for the OPC item.
Bit specifies how many bits the attribute takes.
Description describes the data type and access and gives useful information.
5.1.1.1. IEC 61850 quality

The table below defines the mapping of quality in MMS (IEC 61850 7-3). Only 14
bits (LSB) in quality are valid.
Table 5.1.1.1-1 IEC 61850 quality
Value/
Name Type M/O/C Bit
Value range
validity 2bit good (0) | invalid (1) | reserved (2) M 0-1

| questionable (3)
overflow 1bit FALSE (0) | TRUE (1) M 2
41

Users Guide
Table 5.1.1.1-1 IEC 61850 quality
Value/
Name Type M/O/C Bit
Value range
outOfRange 1bit FALSE (0) | TRUE (1) M 3
badReference 1bit FALSE (0) | TRUE (1) M 4
oscillatory 1bit FALSE (0) | TRUE (1) M 5
failure 1bit FALSE (0) | TRUE (1) M 6
oldData 1bit FALSE (0) | TRUE (1) M 7
inconsistent 1bit FALSE (0) | TRUE (1) M 8
inaccurate 1bit FALSE (0) | TRUE (1) M 9
source 2bit process (0) | substituted (1) M 10-11
test 1bit FALSE (0) | TRUE (1) M 12
operatorBlocked 1bit FALSE (0) | TRUE (1) M 13
5.1.1.2. Mapping quality value to OPC

The value of validity is presented as the value of the quality attribute and the other
values are presented as OPC properties of the quality in the OPC namespace.
Table 5.1.1.2-1 Mapping quality value to OPC
Value/ OPC Data

Name Type M/O/C
Value range Type
Validity good (0) | invalid (1) | reserved (2) M VT_I4

| questionable (3)
DetailQuality DetailedQuality M VT_I4
Source process (0) | substituted (1) M VT_I4
Test FALSE (0) | TRUE (1) M VT_BOOL
OperatorBlocked FALSE (0) | TRUE (1) M VT_BOOL
5.1.1.3. Mapping of DetailedQuality

The value of DetailQuality is mapped to a DetailedQuality bitmap.
Table 5.1.1.3-1 Mapping of DetailedQuality
Value/
Name Type M/O/C Bit
Value range
overflow 1bit FALSE (0) | TRUE (1) M 0
outOfRange 1bit FALSE (0) | TRUE (1) M 1
badReference 1bit FALSE (0) | TRUE (1) M 2
oscillatory 1bit FALSE (0) | TRUE (1) M 3
failure 1bit FALSE (0) | TRUE (1) M 4
42
Users Guide
Table 5.1.1.3-1 Mapping of DetailedQuality
Value/
Name Type M/O/C Bit
Value range
oldData 1bit FALSE (0) | TRUE (1) M 5
inconsistent 1bit FALSE (0) | TRUE (1) M 6
inaccurate 1bit FALSE (0) | TRUE (1) M 7
Example:
DetailQuality = 1d = 00000001b > overflow = true
DetailQuality = 16d = 00010000b > failure = true
5.1.1.4. Analogue value (AnalogueValue)

Analogue values are always presented as 32 bit float values (VT_R4) so that the .f
and .i extensions are discarded from the attribute names to simplify the OPC
namespace. If a device only supports integer values, the value is converted to a
floating point presentation of the value according to its configuration and the
following formula, refer to Section 5.1.1.5. Configuration of analogue value
(ScaledValueConfig).
f 10 units.multiplier = ( i scaleFactor ) + offset
Table 5.1.1.4-1 Analogue value (AnalogueValue)
Value/ OPC Data

Name Type M/O/C
Value range Type
i INT32 integer value Not Used Not Used
f FLOAT32 floating point value Not Used Not Used
Example:
MV: mag.f (VT_R4) & mag.i (VT_I4) > mag (VT_R4)
5.1.1.5. Configuration of analogue value (ScaledValueConfig)

The table below defines the mapping of configuration of analogue value
(ScaledValueConfig).
Table 5.1.1.5-1 Configuration of analogue value (ScaledValueConfig)
Value/ OPC Data

Name Type M/O/C
Value range Type
scaleFactor FLOAT32 floating point value M VT_R4
offset FLOAT32 floating point value M VT_R4
43

Users Guide
5.1.1.6. Range configuration (RangeConfig)

The table below defines the mapping of range configuration (RangeConfig).
Table 5.1.1.6-1 Range configuration (RangeConfig)
Value/ OPC Data

Name Type M/O/C
Value range Type
hhLim AnalogueValue floating point value M VT_R4
hLim AnalogueValue floating point value M VT_R4
lLim AnalogueValue floating point value M VT_R4
llLim AnalogueValue floating point value M VT_R4
min AnalogueValue floating point value M VT_R4
max AnalogueValue floating point value M VT_R4
hhLim, hLim, lLim, llLim: These attributes are configuration parameters used in
the context with the range attribute.
min: The min (minimum) attribute represents the minimum process measurement
for which values of i or f are considered within process limits.
max: The max (maximum) attribute represents the maximum process measurement
for which values of i or f are considered within process limits.
5.1.1.7. Step position with transient indication (ValWithTrans)

The table below defines the mapping of Step position with transient indication
(ValWithTrans).
Table 5.1.1.7-1 Step position with transient indication (ValWithTrans)
Value/ OPC Data

Name Type M/O/C
Value range Type
posVal INT8 -64 63 M VT_I4
transInd BOOLEAN TRUE | FALSE M VT_BOOL
5.1.1.8. Pulse configuration (PulseConfig)

The table below defines the mapping of pulse configuration (PulseConfig).
Table 5.1.1.8-1 Pulse configuration (PulseConfig)
Value/ OPC Data

Name Type M/O/C
Value range Type
cmdQual ENUMERATED pulse(0) | persistent(1) M VT_I4
onDur INT32U M VT_I4
offDur INT32U M VT_I4
numPls INT32U M VT_I4
44
Users Guide
5.1.1.9. Originator
The table below defines the mapping of originator (Originator).
Table 5.1.1.9-1 Originator
Value/ OPC Data

Name Type M/O/C
Value range Type
orCat ENUMERATED not-supported(0) | bay-control(1) | M VT_I4

station-control(2) | remote-
control(3) | automatic-bay(4) |
automatic-station(5) | automatic-
remote(6) | maintenance(7) |
process(8)
orident OCTET TRUE | FALSE M VT_BSTR

STRING64
5.1.1.10. Unit
The table below defines the mapping of unit (Unit).
Table 5.1.1.10-1 Unit
Value/ OPC Data

Name Type M/O/C
Value range Type
SIUnit ENUMERATED M VT_I4

multiplier ENUMERATED O VT_I4
5.1.1.11. Vector
The table below defines the mapping of vector (Vector).
Table 5.1.1.11-1 Vector
Value/ OPC Data

Name Type M/O/C
Value range Type
mag AnalogueValue floating point value M VT_R4
ang AnalogueValue floating point value O VT_R4
5.1.1.12. TimeStamp
The timestamp OPC attributes are presented as OPC type VT_DATE. It is
implemented using an 8-byte floating-point number. Days are represented by whole
number increments starting with 30 December 1899, midnight as time zero. Hour
values are expressed as the absolute value of the fractional part of the number.
45

Users Guide
5.1.1.13. AbbCommandBitmask
The table below defines the mapping of AbbCommandBitmask. This ABB specific
control value is a bitmask value of a command to a device. This value is applicable
to ABB extension control attributes.
Table 5.1.1.13-1 AbbCommandBitmask
Value/ OPC Data

Name Type M/O/C
Value range Type
NormalControl 1bit FALSE (0) | TRUE (1) M 0
InterlockOverride 1bit FALSE (0) | TRUE (1) M 1
SynchrocheckOverride 1bit FALSE (0) | TRUE (1) M 2
TestCommand 1bit FALSE (0) | TRUE (1) M 3
Originator 4bit not-supported(0) | bay-control(1) | M 4-7

station-control(2) | remote-
control(3) | automatic-bay(4) |
automatic-station(5) | automatic-
remote(6) | maintenance(7) |
process(8)
ControlValue nbit M 8-31
NormalControl: True = normal operation, false = inverse operation (e.g. On > Off).
InterlockOverride: True = interlockcheck > false
SynchrocheckOverride: True = syncrocheck > false
TestCommand: True = test command
Originator: Command originator (= Originator.orCat)
5.1.2. Common data class specifications for status information
5.1.2.1. Single point status (SPS)

The table below defines the common data class of single point status.
Table 5.1.2.1-1 Single point status (SPS)
Value/ OPC Data

Name Type FC M/O
Value range Type
stVal BOOLEAN ST TRUE | FALSE M VT_BOOL
q Quality ST M VT_I4
t TimeStamp ST M VT_DATE
subEna BOOLEAN SV O VT_BOOL
subVal BOOLEAN SV TRUE | FALSE O VT_BOOL
subQ Quality SV O VT_I4
46
Users Guide
Table 5.1.2.1-1 Single point status (SPS)
Value/ OPC Data

Name Type FC M/O
Value range Type
subID VISIBLE SV O VT_BSTR

STRING64
d VISIBLE DC Text O VT_BSTR

STRING64
dU UNICODE DC O VT_BSTR
STRING255
cdcNs VISIBLE EX O VT_BSTR

STRING255
cdcName VISIBLE EX O VT_BSTR

STRING255
dataNs VISIBLE EX O VT_BSTR

STRING255
5.1.2.2. Double point status (DPS)

The table below defines the common data class of double point status.
Table 5.1.2.2-1 Double point status (DPS)
Value/ OPC Data

Name Type FC M/O
Value range Type
stVal CODED ENUM ST intermediate-state (0) | off (1) | on M VT_I4

(2) | bad-state (3)
subVal CODED ENUM SV intermediate-state (0) | off (1) | on O VT_I4

(2) | bad-state (3)

STRING64

STRING255
STRING255
47

Users Guide
Table 5.1.2.2-1 Double point status (DPS) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type

STRING255

STRING255

STRING255
5.1.2.3. Integer status (INS)

The table below defines the common data class of integer status.
Table 5.1.2.3-1 Integer status (INS)
Value/ OPC Data

Name Type FC M/O
Value range Type
stVal INT32 ST M VT_I4
subVal INT32 SV O VT_I4

STRING64
d VISIBLE DC O VT_BSTR
STRING255
STRING255

STRING255

STRING255

STRING255
48
Users Guide
5.1.2.4. Protection activation information (ACT)

The table below defines the common data class of protection activation information.
Table 5.1.2.4-1 Protection activation information (ACT)
Value/ OPC Data

Name Type FC M/O
Value range Type
general BOOLEAN ST M VT_BOOL
phsA BOOLEAN ST O VT_BOOL
phsB BOOLEAN ST O VT_BOOL
phsC BOOLEAN ST O VT_BOOL
neut BOOLEAN ST O VT_BOOL
operTm TimeStamp CF O VT_DATE

STRING255
STRING255

STRING255

STRING255

STRING255
5.1.2.5. Directional protection activation information (ACD)

The table below defines the common data class of directional protection
activation information.
Table 5.1.2.5-1 Directional protection activation information (ACD)
Value/ OPC Data

Name Type FC M/O
Value range Type
general BOOLEAN ST M VT_BOOL
dirGeneral ENUMERATED ST unknown (3) | forward (1) | M

backward (2)
phsA BOOLEAN ST O VT_BOOL
dirPhsA ENUMERATED ST unknown (3) | forward (1) | O

backward (2)
phsB BOOLEAN ST O VT_BOOL
49

Users Guide
Table 5.1.2.5-1 Directional protection activation information (ACD)
Value/ OPC Data

Name Type FC M/O
Value range Type
dirPhsB ENUMERATED ST unknown (3) | forward (1) | O

backward (2)
phsC BOOLEAN ST O VT_BOOL
dirPhsC ENUMERATED ST unknown (3) | forward (1) | O

backward (2)
neut BOOLEAN ST O VT_BOOL
dirNeut ENUMERATED ST unknown (3) | forward (1) | O

backward (2)

STRING255
STRING255

STRING255

STRING255

STRING255
50
Users Guide
5.1.2.6. Security violation counter (SEC)

The table below defines the common data class of security violation counting.
Table 5.1.2.6-1 Security violation counting (SEC)
Value/ OPC Data

Name Type FC M/O
Value range Type
cnt INT32U ST M VT_I4
sev ENUMERATED ST unknown (0) | critical (1) | major (2) M VT_I4

| minor (3) | warning (4)
addr OCTET ST O VT_BSTR

STRING64
addInfo VISIBLE ST O VT_BSTR

STRING64
O VT_BSTR

STRING255
STRING255

STRING255

STRING255

STRING255
5.1.2.7. Binary counter reading (BCR)

The table below defines the common data class of binary counter reading.
Table 5.1.2.7-1 Binary counter reading (BCR)
Value/ OPC Data

Name Type FC M/O
Value range Type
actVal INT128 ST M VT_I4
frVal INT128 ST Oa VT_I4
frTm TimeStamp ST Oa VT_DATE
units Unit CF O VT_R4
pulsQty FLOAT32 CF M VT_BOOL
frEna BOOLEAN CF Oa VT_DATE
51

Users Guide
Table 5.1.2.7-1 Binary counter reading (BCR) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type
strTm TimeStamp CF Oa VT_I4
frPd INT32 CF Oa VT_BOOL
frRds BOOLEAN CF Oa VT_BSTR

STRING255
STRING255

STRING255

STRING255

STRING255
a. All or none of these items must be present.
5.1.3. Common data class specifications for measured information
5.1.3.1. Measured value (MV)

The table below defines the common data class of measured value.
Table 5.1.3.1-1 Measured value (MV)
Value/ OPC Data

Name Type FC M/O
Value range Type
instMag AnalogueValue MX O VT_R4
mag AnalogueValue MX M VT_R4
range ENUMERATED MX normal (0) | high (1) | low (2) | O VT_I4

high-high (3) | low-low (4) |
q Quality MX M VT_I4
t TimeStamp MX M VT_DATE
subVal AnalogueValue SV O VT_R4

STRING64
units Unit CF O
db INT32U CF 0...100 000 O VT_I4
52
Users Guide
Table 5.1.3.1-1 Measured value (MV) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type
zeroDb INT32U CF 0...100 000 O VT_I4
sVC ScaledValueCo CF O
nfig
rangeC RangeConfig CF O
smpRate INT32U CF O VT_I4

STRING255
STRING255

STRING255

STRING255

STRING255
5.1.3.2. Complex measured value (CMV)

The table below defines the common data class of measured value.
Table 5.1.3.2-1 Complex measured value (CMV)
Value/ OPC Data

Name Type FC M/O
Value range Type
instCVal Vector MX O
cVal Vector MX M
range ENUMERATED MX normal (0) | high (1) | low (2) | O VT_I4

high-high (3) | low-low (4) |
subVal Vector SV O

STRING64
units Unit CF O
db INT32U CF 0...100 000 O VT_I4
zeroDb INT32U CF 0...100 000 O VT_I4
53

Users Guide
Table 5.1.3.2-1 Complex measured value (CMV) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type
rangeC RangeConfig CF O
magSVC ScaledValueCo O
nfig
angSVC ScaledValueCo O
nfig
angRef ENUMERATED CF V | A | other ... O VT_I4
smpRate INT32U CF O VT_I4

STRING255
STRING255

STRING255
STRING255

STRING255
5.1.3.3. Sampled value (SAV)

The table below defines the common data class of sampled value.
Table 5.1.3.3-1 Sampled value (SAV)
Value/ OPC Data

Name Type FC M/O
Value range Type
instMag AnalogueValue MX M VT_R4
units Unit CF O
nfig
min AnalogueValue CF O VT_R4
max AnalogueValue CF O VT_R4

STRING255
STRING255

STRING255
54
Users Guide
Table 5.1.3.3-1 Sampled value (SAV) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type

STRING255

STRING255
5.1.3.4. WYE
The table below defines the common data class of WYE. This class is a collection
of simultaneous measurements of values in a three phase system that represent phase
to ground values.
Table 5.1.3.4-1 WYE
Value/ OPC Data

Name Type FC M/O
Value range Type
phsA CMV MX Oa
phsB CMV MX Oa
phsC CMV MX Oa
neut CMV MX Oa
net CMV MX Oa
res CMV MX Oa
angRef ENUMERATED CF Va (0) | Vb (1) | Vc (2) | Aa (3) | Ab O VT_I4

(4) | Ac (5) | Vab (6) | Vbc (7) | Vca
(8) | Vother (9) | Aother (10)

STRING255
STRING255

STRING255

STRING255

STRING255
a. One or more of these items (1-6) must be present.
55

Users Guide
5.1.3.5. Delta (DEL)

The table below defines the common data class of delta. This class is a collection of
measurements of values in a three phase system that represent phase to phase values.
Table 5.1.3.5-1 Delta (DEL)
Value/ OPC Data

Name Type FC M/O
Value range Type
phsAB CMV MX Oa
phsBC CMV MX Oa
phsCA CMV MX Oa
angRef ENUMERATED CF Va (0) | Vb (1) | Vc (2) | Aa (3) | Ab O VT_I4

(4) | Ac (5) | Vab (6) | Vbc (7) | Vca
(8) | Vother (9) | Aother (10)

STRING255
STRING255

STRING255

STRING255

STRING255
a. One or more of these groups (1-3) must be present.
5.1.3.6. Sequence (SEQ)

The table below defines the common data class of sequence.
Table 5.1.3.6-1 Sequence (SEQ)
Value/ OPC Data

Name Type FC M/O
Value range Type
c1 CMV MX Oa
c2 CMV MX Oa
c3 CMV MX Oa
seqT ENUMERATED CF pos-neg-zero (0) | dir-quad-zero O VT_I4

(1)
phsRef ENUMERATED CF A (0) | B (1) | C (2) | VT_I4

STRING255
56
Users Guide
Table 5.1.3.6-1 Sequence (SEQ) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type
STRING255

STRING255

STRING255

STRING255
a. One or more of these groups (1-3) must be present.
5.1.4. Common data class specifications for controllable status

information
5.1.4.1. Controllable single point (SPC)

The table below defines the common data class of controllable single point.
Table 5.1.4.1-1 Controllable single point (SPC)
Value/ OPC Data

Name Type FC M/O
Value range Type
lastApplError ApplicationErro Refer to Section 5.1.9. Application VT_I4

rCode error codes
ctlVal BOOLEAN CO off (FALSE) | on (TRUE) M VT_BOOL
operTm TimeStamp CO O VT_DATE
origin Originator CO, ST
ctlNum INT8U CO, ST 0..255 O VT_I4
stVal BOOLEAN ST FALSE | TRUE M VT_BOOL
stSeld BOOLEAN ST FALSE | TRUE O VT_BOOL
subVal BOOLEAN SV FALSE | TRUE O VT_BOOL

STRIN64
pulseConfig PulseConfig CF O
57

Users Guide
Table 5.1.4.1-1 Controllable single point (SPC) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type
ctlModel ENUMERATED CF Status-only (0) | direct-with- M VT_I4

normal-security (1) | sbo-with-
normal-security (2) | direct-with-
enhanced-security (3) | sbo-with-
enhanced-security (4)
sboTimeout INT32U CF O VT_I4
sboClass ENUMERATED CF operate-once (0) | operate-many O VT_I4

(1)

STRING255
STRING255

STRING255

STRING255

STRING255
Mapping of controls:
Direct Control with Normal Security:
ctlVal: MMS Write.request to Oper structure with value.
SBO with Normal Security:

ctlVal: MMS Write.request to ctlVal with value. IEC61850 OPC
Server will do the select before operate.
Direct Control with Enhanced Security:

SBO with Enhanced Security:

ctlVal: MMS Write.request to ctlVal with value. IEC61850 OPC
Server will do the select before operate.
58
Users Guide
5.1.4.2. Controllable double point (DPC)

The table below defines the common data class of controllable double point.
Table 5.1.4.2-1 Controllable double point (DPC)
Value/ OPC Data

Name Type FC M/O
Value range Type
ctlSelOn AbbCommand M VT_I4

Bitmask
ctlSelOff AbbCommand M VT_I4

Bitmask
ctlOperOn AbbCommand M VT_I4

Bitmask
ctlOperOff AbbCommand M VT_I4

Bitmask
ctlCan AbbCommand M VT_I4

Bitmask
ctlOper AbbCommand M VT_I4

Bitmask

rCode error codes
ctlVal BOOLEAN CO off (FALSE) | on (TRUE) M VT_BOOL
origin Originator CO, ST O
stVal CODED ENUM ST intermediate-state (0) | off (1) | on M VT_I4

(2) | bad-state (3)
subVal CPT SV intermediate-state (0) | off (1) | on O VT_I4

(2) | bad-state (3)

STRING64
pulseConfig PulseConfig CF O
59

Users Guide
Table 5.1.4.2-1 Controllable double point (DPC) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type


(1)

STRING255
STRING255

STRING255

STRING255

STRING255
ctlOperOn: This attribute shall determine the control activity operation in direction
On/Close.
ctlOperOff: This attribute shall determine the control activity operation in direction
Off/Open.
ctlSelOn: This attribute shall determine the selection with direction On/Close.
ctlSelOff; This attribute shall determine the selection with direction Off/Open.
ctlCan: This attribute shall determine the cancellation of the selection
ctlOper: This attribute shall determine the selection with direction (direction got
from previous select). Only applicable for controls with SBO.
ctlSelOn: (not used)
ctlSelOff: (not used)
ctlOperOn: MS Write.request to Oper structure with value ON.
ctlOperOff: MMS Write.request to Oper structure with value OFF.
ctlCan: (not used)
ctlOper: (not used)
The ctlSelOn, ctlSelOff, ctlCan, selCause, cmdTermCause, stSeld and the
bits in ControlValues are not applicable.
60
Users Guide

ctlSelOn: MMS Read.request to SBO structure (to perform select).
ctlSelOff: MMS Read.request to SBO structure (to perform select).
ctlOperOn: MMS Write.request to Oper structure with value ON (to
operate).
ctlOperOff: MMS Write.request to Oper structure with value OFF (to
operate).
ctlCan: MMS Write.request ro Cancel structure
ctlOper: MMS Write.request to Oper structure with value ON/OFF
according to previous direction of select.

ctlSelOn: (not used)
ctlSelOff: (not used)
ctlOperOn: MMS Write.request to Oper structure with value ON.
ctlOper: (not used)

ctlSelOn: MMS Read.request to SBOw structure.
ctlSelOff: MMS Read.request to SBOw structure.
ctlOperOn: MMS Write.request to Oper structure with value ON.
ctlOper: MMS Write.request to Oper structure with value ON/OFF
according to previous direction of select.
5.1.4.3. Controllable integer status (INC)

The table below defines the common data class of controllable integer status.
Table 5.1.4.3-1 Controllable integer status (INC)
Value/ OPC Data

Name Type FC M/O
Value range Type

rCode error codes
ctlVal INT32 CO M VT_I4
orCat ENUMERATED O VT_I4
orIdent OCTET O VT_BSTR

STRING64
61

Users Guide
Table 5.1.4.3-1 Controllable integer status (INC) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type
stVal INT32 ST M VT_I4
subID VISIBLE SV Text O VT_BSTR

STRING64


(1)
minVal INT32 CF O VT_I4
maxVal INT32 CF O VT_I4
stepSize INT32U CF 1 ... (maxVal - minVal) O VT_I4

STRING255
STRING255

STRING255

STRING255

STRING255
62
Users Guide

IEC61850 OPC Server will do the select before operate.


5.1.4.4. Binary controlled step position information (BSC)

The table below defines the common data class of binary controlled step position
information.
Table 5.1.4.4-1 Binary controlled step position information (BSC)
Value/ OPC Data

Name Type FC M/O
Value range Type

rCode error codes
ctlVal ENUMERATED CO stop (0) | lower (1) | higher (2) | M VT_I4

reserved (3)
orCat ENUMERATED not-supported | bay-control | O VT_I4

station-control | remote-control |
automatic-bay | automatic-station |
automatic-remote | maintenance |
process
orIdent OCTET VT_BSTR

STRING64
valWTr.posVal INT8 ST M VT_I4
valWTr.transInd BOOLEAN ST M VT_BOOL
63

Users Guide
Table 5.1.4.4-1 Binary controlled step position information (BSC) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type
subID VISIBLE SV Text O VT_BSTR

STRING64


(1)

stepSize INT8 CF 1 ... (maxVal - minVal) O VT_I4

STRING255
STRING255

STRING255
STRING255

STRING255



64
Users Guide
5.1.4.5. Integer controlled step position information (ISC)

The table below defines the common data class of integer controlled step position
information.
Table 5.1.4.5-1 Integer controlled step position information (ISC)
Value/ OPC Data

Name Type FC M/O
Value range Type

rCode error codes
ctlVal INT8 CO -64 63 M VT_I4
orCat ENUMERATED not-supported | bay-control | O VT_I4

station-control | remote-control |
automatic-bay | automatic-station |
automatic-remote | maintenance |
process
orIdent OCTET O VT_BSTR

STRING64
valWTr.posVal INT8 ST M VT_I4
valWTr.transInd BOOLEAN ST M VT_BOOL
subID VisibleString SV Text O VT_BSTR


(1)
stepSize INT8 CF 1 ... (maxVal - minVal) O VT_I4
65

Users Guide
Table 5.1.4.5-1 Integer controlled step position information (ISC) (Continued)
Value/ OPC Data

Name Type FC M/O
Value range Type

STRING255
STRING255

STRING255

STRING255

STRING255



5.1.5. Common data class specifications for controllable analogue

information
5.1.5.1. Analogue set point (APC)

The table below defines the common data class of analogue set point.
Table 5.1.5.1-1 Analogue set point (APC)
Value/ OPC Data

Name Type FC M/O
Value range Type

rCode error codes
setMag AnalogueValue SP, MX M VT_R4
66
Users Guide
Table 5.1.5.1-1 Analogue set point (APC)
Value/ OPC Data

Name Type FC M/O
Value range Type
origin Originator SP, MX O
operTm TimeStamp SP O VT_DATE
ctlModel ENUMERATED CF direct-with-normal-security (1) M VT_I4
units Unit CF O
nfig
minVal AnalogueValue CF O VT_R4
maxVal AnalogueValue CF O VT_R4
stepSize AnalogueValue CF 1 ... (maxVal-minVal) O VT_R4

STRING255
STRING255

STRING255

STRING255

STRING255
setMag: MMS Write.request to Oper structure with value.



67

Users Guide
5.1.6. Common data class specifications for status settings
5.1.6.1. Single point setting (SPG)

The table below defines the common data class of single point setting.
Table 5.1.6.1-1 Single point setting (SPG)
Value/ OPC Data

Name Type FC M/O
Value range Type
setVal BOOLEAN SP off (FALSE) | on (TRUE) M VT_BOOL

STRING255
STRING255

STRING255

STRING255

STRING255
5.1.6.2. Integer status setting (ING)

The table below defines the common data class of integer status setting.
Table 5.1.6.2-1 Integer status setting (ING)
Value/ OPC Data

Name Type FC M/O
Value range Type
setVal INT32 SP M VT_I4
stepSize INT32 CF 1 (maxVal - minVal) O VT_I4

STRING255
STRING255

STRING255

STRING255

STRING255
68
Users Guide
5.1.7. Common data class specifications for analogue settings
5.1.7.1. Analogue setting (ASG)

The table below defines the common data class of analogue setting.
Table 5.1.7.1-1 Analogue setting (ASG)
Value/ OPC Data

Name Type FC M/O
Value range Type
setMag AnalogueValue SP M VT_I4
units Unit CF O
nfig
minVal AnalogueValue CF O VT_I4
maxVal AnalogueValue CF O VT_I4
stepSize AnalogueValue CF 1 (maxVal - minVal) O VT_I4

STRING255
STRING255

STRING255

STRING255

STRING255
5.1.7.2. Setting curve (CURVE)

The table below defines the common data class of setting curve.
Table 5.1.7.2-1 Setting curve (CURVE)
Value/ OPC Data

Name Type FC M/O
Value range Type
setCharact ENUMERATED SP M VT_I4
setParA FLOAT32 SP O VT_R4
setParB FLOAT32 SP O VT_R4
setParC FLOAT32 SP O VT_R4
setParD FLOAT32 SP O VT_R4
setParE FLOAT32 SP O VT_R4
setParF FLOAT32 SP O VT_R4
69

Users Guide
Table 5.1.7.2-1 Setting curve (CURVE)
Value/ OPC Data

Name Type FC M/O
Value range Type

STRING255
STRING255

STRING255

STRING255

STRING255
5.1.8. Common data class specifications for description information
5.1.8.1. Device name plate (DPL)

The table below defines the common data class of device name plate. Data of this
common data class are used to identify entities like primary equipment or physical
devices.
Table 5.1.8.1-1 Device name plate (DPL)
Value/ OPC Data

Name Type FC M/O
Value range Type
vendor VISIBLE DC M VT_BSTR

STRING255
hwRev VISIBLE DC O VT_BSTR

STRING255
swRev VISIBLE DC O VT_BSTR

STRING255
serNum VISIBLE DC O VT_BSTR

STRING255
model VISIBLE DC O VT_BSTR

STRING255
location VISIBLE DC O VT_BSTR

STRING255

STRING255
cdcName VISIBLE EX VT_BSTR

STRING255

STRING255
70
Users Guide
5.1.8.2. Logical node name plate (LPL)

The table below defines the common data class of logical node name plate. Data of
this common data class are used to identify logical nodes.
Table 5.1.8.2-1 Logical node name plate (LPL)
Value/ OPC Data

Name Type FC M/O
Value range Type
vendor VISIBLE DC M VT_BSTR

STRING255
hwRev VISIBLE DC M VT_BSTR

STRING255
d VISIBLE DC Text M VT_BSTR

STRING255
STRING255
configRev VISIBLE DC O VT_BSTR

STRING255
ldNs VISIBLE EX shall be included only in LLN0 O VT_BSTR

STRING255
lnNs VISIBLE EX O VT_BSTR

STRING255

STRING255

STRING255

STRING255
71

Users Guide
5.1.9. Application error codes

Command Error codes of lastApplError attribute. The attribute is valid only for
command data classes and its value presents the status of the last command. It is
updated when command responses are received from devices.
The status code is received by adding the additional status code to main status code.
Example: 1003 = Unknown, select failed
Table 5.1.9-1 Main status codes
0 OK
1000 Unknown
2000 Timeout test not ok
3000 Operator test not ok
Table 5.1.9-2 Additional status codes
0 Unknown
1 Not supported
2 Blocked by switching hierarchy
3 Select failed
4 Invalid position
5 Position reached
6 Parameter change in execution
7 Step limit
8 Blocked by mode
9 Blocked by process
10 Blocked by interlocking
11 Blocked by synchrocheck
12 Command already in execution
13 Blocked by health
14 1 of n control
15 Abortion by cancel
16 Time limit over
17 Abortion by trip
18 Object not selected
5.2. Attributes
In addition to attributes for process data (indications and commands), the OPC
Server also provides some attributes for controlling the devices and retrieving sta-
tus information from them. These attributes are available for the OPC access client.
72
Users Guide
5.2.1. Server attributes

Table 5.2.1-1 Server attributes

Name Description
Default
Version information Data type: Text

Protocol stack
Access: Read-only
version
The version information of the Protocol Stack
Configuration Access: Read-only

version
The version information of the current
configuration file.
By writing 1 the server Data type: Integer

is reset.
Access: No limitations
By writing 2 the log file
is cleared. Makes it possible for clients to reset the OPC
server. A reset means that the server
Other values are disconnects all clients and reloads the
Reset currently ignored. configuration file.
Note! When the last client is disconnected the

server usually shuts down. The server does not
shut down if it was not started by the COM
runtime or if it is running as a Windows service.
In that case the configuration file is not
reloaded.
Access: Read-only
File version
The file version number of the OPC server/
client exe file.
Access: Read-only
Product version
The version (revision) of the package that the
server/client belong to.
Timesync client
73

Users Guide
Table 5.2.1-1 Server attributes (Continued)
In use 0 = Not in use Data type: Integer
1 = In use Access: No limitations
Default: 1 Status of the integrated SNTP clients time

synchronization routine. Value is 0 when not in
use and 1 when in use. By writing 0 the client is
started and by writing 1 it is stopped. The client
can be started only if configuration parameters
are given in a configuration file.
Timesync status False = Not Data type: Boolean

synchronised
Access: Read-only
True = Synchronised
OK Status of the integrated SNTP client time
synchronization routine. Value is false when
synchronization is not received and true when
synchronization received and local time set
OK.
Timesync server
In use 0 = Not in use Data type: Integer
1 = In use Access: No limitations
Default: 1 Status of the integrated SNTP servers time

synchronization routine. Value is 0 when not in
use and 1 when in use. By writing 0 the client is
started and by writing 1 it is stopped.
Timesync status False = Failure Status of the integrated SNTP servers time
synchronization routine. Value is false when
True = OK operation fails and true when operating OK.
74
Users Guide
5.2.2. IEC 61850 line attributes

Table 5.2.2-1 IEC 61850 line attributes

Name Description
Default
0 = Not in use, the line Data type: Integer

communication is
stopped Access: No limitations
1 = In use The state of the line whether it is in use or not.

When a line is not in use, no data can be
Default: 1 transmitted on it, and no data is received from
it. When a line is stopped by setting the in use
In use
attribute to 0, all data transmission on the line
ceases and all open connections to the devices
will be closed. Single devices in use attribute
may be set to 1 and this operation also takes
the line in use. Now only the one device is in
use. If the line's in use is set to 1, the rest of the
devices are taken in use. The in use attribute
has no affect on devices in simulation mode.
89 = Initialize error Data type: Integer
90 = Not connected Access: Read-only
91 = Initializing Indicates the operating status of the device

Object status
100 = Ready
101 = Suspended
(=Not in use)
102 = Simulated
False = Diagnostic Data type: Boolean

events disabled
Diagnostic
events enabled
True = Diagnostic
events enabled Enables/disables diagnostic events
0 = Disabled Data Type: Integer
1 = Level1 (main Access: No limitations

operation and errors)
Sets the maximum level for events coming
2 = Level2 (+ time from devices. Limits the lower level events to
Diagnostic synchronization error) pass through.
events level
3 = Level3 (+ time See also System Event Level shown in Table
synchronization done) 3.3.2-1.
4 = Level4
5 = Level5
75

Users Guide
Table 5.2.2-1 IEC 61850 line attributes (Continued)
Diagnostic counters
Sent connection Data type: Integer

request
Connect requests sent to devices
Received Data type: Integer

connection
replies ok Access: No limitations
Successful connect replies from devices

connection
replies error Access: No limitations
Failed connect replies from devices

concludes
Connections closed by IEC 61850 OPC server

connection
concludes Access: No limitations
Received connection concludes

connection
aborts Access: No limitations
Connections refused and aborted by devices
Received rejects Data type: Integer
Request rejected by devices (usually if device

could not decode the request or they do not
support the used service)
Sent requests Data type: Integer
Request sent to devices
Received replies Data type: Integer

ok
Successful requests to devices (received

success responses)
76
Users Guide
Table 5.2.2-1 IEC 61850 line attributes (Continued)

error
Failed requests to devices (received error

responses)

variable read
Variable read success responses from devices

variable read
Variable read failure responses from devices

variable write
Variable write success responses from devices

variable write
Variable read failure responses from devices

information
reports Access: No limitations
Information reports received from devices
Received status Data type: Integer

requests
Unsolicited status requests received from

devices
77

Users Guide
5.2.3. IEC 61850 device attributes

Table 5.2.3-1 IEC 61850 device attributes

Name Description
Default
0 = Out of use Data type: Integer

1 = In use
Default: 1
The operational status of the device whether it
is in use or out of use. Taking the device out of
use with this attribute stops all data
communication with the device and closes the
In use
connection. All operations that would result in a
data exchange are disabled. Setting in use to 1
will take the device back in use and tries to
reestablish the connection to a physical device.
The device itself is not affected by the attribute,
only protocol stacks image of the device. The
in use attribute has no affect on devices in
simulation mode.
86 = Report control Data type: Integer

block initialization error
(restarting rcb init) Access: Read-only
88 = Configuration Indicates the operating status of the device

version error (device is
suspended)
89 = error (not
specified)
90 = Device not
Object status
connected
91 = Initializing
92 = Initializing rcb
(after error in reporting
init or information
report flow)
93 = Reinitialize (after
reconnection if init
done)
78
Users Guide
Table 5.2.3-1 IEC 61850 device attributes (Continued)
94 = Init (checking Data type: Integer

configuration version
for single rcb) Access: Read-only
95 = init (checking rcb Indicates the operating status of the device

attributes for single
rcb)
96 = Init (reading rcb

variable list for single
rcb)
97 = Init (enabling
reporting for single rcb)
98 = Init (rcb init ok for

single rcb)
100 = Ready
101 = Suspended (=
not in use)
102 = Device
simulated
False = Device Data type: Boolean

Device connection suspended
connection Access: Read-only
status True = Device
connection OK Indicates the status of the device connection.
False = Diagnostic Data type: Boolean

events disabled
Diagnostic
events enabled
True = Diagnostic
events enabled Enables/disables diagnostic events
79

Users Guide
0 = Disabled Data Type: Integer
1 = Level1 Access: No limitations

(main operation, error
replies, errors) Sets diagnostics event level
2 = Level2 See also System Event Level shown in Table

(+ Information Reports, 3.3.2.1-1.
OK replies, RCB init)
Diagnostic 3 = Level3
events level (+ sent requests
(connect,read,write),
transparent SPA
messages)
4 = Level4
(+ reported local
updates)
5 = Level5 (+ reported
unconfigured updates)
0.0.0.0 - Data type: Text

255.255.255.255
IP address Access: Read-only (configuration)
IP address of the physical device
Configuration Access: Read-only

version
The version information of the current
configuration for this device.
Transparent See Section 5.2.3.1. Transparent XSAT.

XSAT
Diagnostic counters

requests
Access: No limitation
Connection requests sent to device

connection
replies ok Access: No limitation
Success connection replies received from

device (connection accepted)
80
Users Guide

connection
replies error Access: No limitation
Failure connection replies received from device

(connection refused).

concludes
Connection to the device closed by IEC 61850

OPC Server.

connection
concludes Access: No limitation
Connections closed by device.
Sent requests Data type: Integer
Additional requests (variable list, access

attributes) sent to device

ok
Success replies to additional requests from

device.

error
Failure replies to additional requests from

device
Sent variable Data type: Integer

read requests
Variable read requests sent to device

variable read
Success replies to variable reads from device

variable read
Failure replies to variable reads from device
81

Users Guide
Sent variable Data type: Integer

write requests
Variable write requests sent to device

variable write
Success replies to variable write from device

variable write
Failure replies to variable write from device

information
reports Access: No limitation
Information reports received from device
Received status Data type: Integer

replies
Successful replies to Status requests received

from device
5.2.3.1. Transparent XSAT

The Transparent XSAT attribute can be used to read and write IEC 61850 attributes,
which are not configured to the OPC namespace of the IEC 61850 OPC Server. For
example, the transparent XSAT attribute can be used for setting group controlling.
The Transparent XSAT attribute is used through an OPC client. The attribute uses
the OPC data type BSTR, which is a variant of VT_BSTR data type.
The Transparent XSAT attribute passes on request the IEC 61850 servers and their
attributes outside the IEC 61850 OPC servers namespace. The IEC 61850 OPC
server does not check the outgoing attributes. Therefore the IEC 61850 OPC clients
which are using the Transparent XSAT attribute know what attributes they are
accessing. The Transparent XSAT attribute only supports read and write requests.
The Transparent XSAT attribute uses synchronic data access in the IEC 61850 OPC
server. When an IEC 61850 OPC client writes a request, the IEC 61850 OPC server
parses and sends the request to the IEC 61850 server.
The Transparent XSAT attribute returns and releases the request after it has received
reply from the IEC 61850 server. The reply is written in the Transparent XSAT
attribute as an XSAT string.
82
Users Guide
XSAT Read Request

Attribute Data Type Unknown
The attributes data type is not known, because it is not included in the IEC 61850
OPC Server configuration (SCL). The Transparent XSAT attribute asks first the
required data type, before reading the data from an IEC 61850 server.
If the Transparent XSAT attribute receives a success message, the data type is saved.
If the Transparent XSAT attribute receives an error message, an XSAT error string
is send to the IEC 61850 OPC client.
The IEC 61850 OPC server request for the data type with a ReadVariableData
service and results are written in the Transparent XSAT attribute as an XSAT string.
The XSAT string contains success and error messages.
Attribute Data Type Known
The attribute data type is known from a previous request or the attribute is included
in the IEC 61850 OPC Server configuration (SCL). The IEC 61850 OPC server
directly uses a ReadVariableData service to complete the request. The reply
message is written in the Transparent XSAT attribute as an XSAT string. The XSAT
string contains success and error messages.
XSAT Write Request

Attribute Data Type Unknown
The attributes data type is not known, because it is not included in the IEC 61850
OPC Server configuration (SCL). The Transparent XSAT attribute first asks the
required data type, before writing the data from an IEC 61850 server.
If the Transparent XSAT attribute receives a success message, the data type is saved.
If the Transparent XSAT attribute receives a error message, an XSAT error string is
sent to the IEC 61850 OPC client.
The IEC 61850 OPC server requests for the data type with a WriteVariableData
service and results are written in the Transparent XSAT attribute as an XSAT string.
The XSAT string contains success and error messages.
Attribute Data Type Known
The attribute data type is known from a previous request or the attribute is included
in the IEC 61850 OPC Server configuration (SCL). The IEC 61850 OPC server
directly uses a WriteVariableData service to complete the request. The reply
message is written in the Transparent XSAT attribute as an XSAT string. The XSAT
string contains success and error messages.
XSAT Formats
XSAT Read Request
XSAT Write Request
XSAT Read Reply
XSAT Write Reply
83

Users Guide
5.2.4. IEC 61850 logical device attributes

Table 5.2.4-1 IEC 61850 logical device attributes

Name Description
Default
Transparent The contents of a valid Data type: Text

SPA SPA request
Makes it possible to communicate with SPA

unit by sending SPA message and reading the
reply as text in SPA format from this item. The
communication is passed through a TCP/SPA
tunnel, where this attribute acts as an
independent TCP/SPA client and is connected
to a TCP/SPA server. The TCP/SPA server is
then responsible for forwarding the SPA
messages to and from the SPA devices. The
SPA/TCP client handles its own
communication separately from other
communication. No checks are done on
command or reply contents they are simply
passed on. This parameter is available only by
configuration.
This attribute must be enabled by setting the

Transparent SPA Address, see Table 3.3.2.2-1.
For example:
SPA address = 1
SPA command RF must we written in format
RF: and sent in format 1RF:. The reply is
received in format >1D:REF543 :.
5.3. IEC 61850 File Transfer

This section defines how the IEC 61850 file transfer services between the
IEC 61850 OPC Server and the IEC 61850 devices are used through OPC DA. Since
it is not possible to pass files through OPC, the IEC 61850 OPC Server is used as a
file storage. The received and sent files are stored locally in the computer running
the OPC server.
File transfer services are controlled by an OPC DA client through the OPC attributes
under the IED\Attributes\File transfer node. For more information about the file
transfer attributes, refer to Section 5.3.1. File Transfer attributes.
The supported file transfer services are GetFile, SetFile, DeleteFile,
GetFileAttributes, GetFileAttributesEx, RenameFile and Cancel. For more
information about the file transfer services, refer to Section 5.3.2. File Transfer
services.
Make sure that the devices support the file transfer services.
84
Users Guide
5.3.1. File Transfer attributes

Table 5.3.1-1 File transfer attributes

Name Description
Default
Remote file Data type: Text

name
File name of the remote file.
Remote file Data type: Text

directory
File directory of the remote directory.
Local file name Data type: Text
File name of the local file.
Local file Data type: Text

directory
File directory of the local directory.
File size in bytes Data type: Text
The remote files size is received in bytes.
Received bytes Data type: Integer
Current remote file size is received in bytes.

The IEC 61850 file transfer receives the file
part by part in maximum size of the MMS
messages. This attribute shows the size of the
file that has been received. Value increases
while the file transfer continues.
Status 1000 - 10000 Data type: Integer

For more information
about valid status Access: Read-only
values, refer to Section
5.3.3. File Transfer Status of the currently requested or last
service codes. finished service.
85

Users Guide
Table 5.3.1-1 File transfer attributes (Continued)

Name Description
Default
Output Data type: Text
Access: Read-only
The GetFileAttributeValues and

GetFileAttributeValuesEx services print the
requested file structures output to this
attribute. For more information about the
output format, refer to Section 5.3.2. File
Transfer services.
Control file 0 = Cancel Data type: Text

reception 1 = GetFile
2= Access: Write-only
GetFileAttributeValues
3= This attribute controls the file transfer services.
GetFileAttributeValuesEx For more information about control codes for
4 = RenameFile specific services, refer to Section 5.3.2. File
5 = SetFile Transfer services.
6 = DeleteFile
5.3.2. File Transfer services

The file transfer services are controlled through the OPC DA attributes, see Table
5.3.1-1. To initiate a service, first the required parameters are written to respective
OPC attributes and then the service is started by writing the service control code to
the file transfer control attribute.
The file transfer control attribute uses synchronous data access for OPC. When an
OPC client writes a service request, the corresponding IEC 61850 file transfer
service on the device is called. When the service is finished or an error occurs, the
OPC request is released.
The status of the latest service is available in the Status attribute. After a service is
started, the status changes to the specific service status code. If the service is
completed succesfully, the status code is set to Ready (see Table 5.3.3-2). For more
information about service failure status codes, refer to Table 5.3.3-3 and Table 5.3.3-
4. Only one service can be called at a time.
GetFile
You can copy a specified file from a remote device to the local file storage with the
GetFile service. Through IEC 61850, this is done in three phases. First, the remote
file is opened, then read, and finally closed. Remote file parameters identify the
remote file. During this operation, the Status, Received bytes and File size in bytes
attributes are updated as the file is moved (in max MMS message size parts). The
copied file is renamed and placed to the local file storage according to local file
parameters.
86
Users Guide
Required parameters: Remote file name

Remote file directory
Local file name
Local file directory
Control code: 1
Service status codes: 1110
1120
1130
Failure status codes: 91xx
The remote file name: Remote file directory + Remote file name
The local file name: Local file directory + Local file name
GetFileAttributeValues
The GetFileAttributeValues service obtains the name of a file or group of files in
the remote file storage. Received file attributes are printed to the Output attribute.
This service prints only file names.
Control code: 2
The remote file or directory name:Remote file directory + Remote file name
To request file attributes for a remote directory, set parameter

Remote file name to empty. For example, space and tabulator are
accepted as empty parameter.
Output
The format of the result string is printed to the Output attribute in the following
format:
{} = optional
filename1{, filename2{, filename3{}}}
Example:
StdOut.txt
StdOut.txt, Eventlog.log, config.icd
87

Users Guide
GetFileAttributeValuesEx
The GetFileAttributeValuesEx service obtains the name and the attributes of a file
or group of files in the remote file storage. Received file attributes are printed to the
Output attribute. This service prints the file names, file sizes and last modification
dates if these are available.
Control code: 3
The remote file or directory name:Remote file directory + Remote file name
To request file attributes for a remote directory, set parameter

Remote file name to empty. For example, space and tabulator are
accepted as empty parameter.
Output
The format of the result string is printed to the Output attribute in a following format:
{} = optional
filename1[size{;d.m.Y H:M:S}]{, filename2[size{;d.m.Y H:M:S}]{ ,fn3[]}}}
filename = string
size = bytes
d = Day of month as decimal number (01 - 31)
m = Month as decimal number (01 - 12)
Y = Year with century, as decimal number
H = Hour in 24-hour format (00 - 23)
M = Minute as decimal number (00 - 59)
S = Second as decimal number (00 - 59)
Example:
StdOut.txt[12445;02.03.2004]
StdOut.txt[12445], Eventlog.log[53422], config.icd[2773]
RenameFile
You can rename or move a file in the remote file storage with the RenameFile
service.
Local file name
Control code: 4
The remote file name to be renamed: Remote file directory + Remote file name
88
Users Guide
The new name for the remote file: Local file directory + Local file name
SetFile
The SetFile service initiates the remote device to obtain a file from the local file
storage to the remote file storage. The service triggers an IEC 61850 device to call
the IEC 61850 clients GetFile service and during this, the IEC 61850 client acts as
a file server. During this operation, the Status, Received bytes and File size in bytes
attributes are updated as the file is moved (in max MMS message size parts). The
local file parameters identify the local file and the copied file is placed to the remote
file storage according to remote file parameters.
Local file name
Control code: 5
1510
1520
1530
The local file name: Local file directory + Local file name
DeleteFile
You can delete a file from the remote file storage with the DeleteFile service.
Control code: 6
Cancel
You can cancel the current service with the Cancel service. The Cancel service sets
the status to Ready and clears for the following attribute values: File size in bytes,
Received bytes and Status
Control code: 0
89

Users Guide
5.3.3. File Transfer service codes

Status codes can be read from the Status attribute. The status indicates the current
service status and the service result.
Table 5.3.3-1 Service control codes

0 Cancel
1 GetFile
2 GetFileAttributeValues
3 GetFileAttributeValuesEx
4 Rename File
5 SetFile
6 DeleteFile
In the service status codes, the first number indicates success (1) or failure (9). The
second number indicates currently requested service (0 - 6). If a local service is
requested in multiple parts for the remote device, the third number indicates the
currently called remote service (1 - 3). The fourth number gives a detailed failure
code (0 - 3).
Example: 9601 = parameters error, remote file delete error
9123 = remote service error, remote file read error
Table 5.3.3-2 Success

1000 Ready
1110 Opening remote file
1120 Reading remote file
1130 Closing remote file
1200 Requesting remote directory file details
1300 Requesting remote directory file details
1400 Renaming remote file
1500 Requesting remote device to obtain local file
1510 Remote device requested to open local file
1520 Remote device requested to read local file
1530 Remote device requested to close local file
1600 Deleting remote file
1000 Service done
The failure status code indicates a failure in requested service. The failure status
code can also include a more detailed error code indicating the failure type, which
can be local or remote failure (see Table 5.3.3-4).
Table 5.3.3-3 Failure

9000 Unspecified error
9110 Remote file open error
9120 Remote file read error
9130 Remote file close error
9200 Remote directory details error
9300 Remote directory details error
9400 Remote file rename error
9500 Error in remote obtaining local file
9510 Error in remote opening local file
9520 Error in remote reading local file
90
Users Guide
Table 5.3.3-3 Failure

9530 Error in remote closing local file
9600 Remote file delete error
Table 5.3.3-4 Failure details

0 No error details
1 Service parameters error (user error)
Reason: required name attribute is empty
Recovery: check the attribute values and try again
2 Local service error (IEC 61850 OPC Server internal error)
Reason: not connected, too much network traffic, etc.
Recovery: check connection and try again
3 Remote service error (remote device error)
Reason: remote device is not supporting service, wrong parameters, no
such file, connection failed, etc.
Recovery: check remote device services support, check parameters (file
names), check connection and try again
5.4. ACSI conformance statement

This section defines the compliance to IEC 61850 in terms of service, modeling and
engineering interfaces and gives detailed explanation of IEC 61850 capabilities of a
product. ACSI conformance statement describes the abstract services interfaces,
which are normally mapped to certain SCSM (Specific communication service
mapping) and therefore indirectly stated in PICS (Protocol Implementation
Conformance Statement).
5.4.1. ACSI basic conformance statement

Table 5.4.1-1 ACSI basic conformance statement
Client/ Subscriber Server/ Publisher Value/ Comments
Client-Server roles
B11 Server side (of TWO-PARTY- - a

APPLICATION-ASSOCIATION)
B12 Client side of (TWO-PARTY- a - Supported

APPLICATION-ASSOCIATION)
SCSMs supported
B21 SCSM: IEC 6185-8-1 used Supported
B22 SCSM: IEC 6185-9-1 used Not Supported
B23 SCSM: IEC 6185-9-2 used Not Supported
B24 SCSM: other
Generic substation event model (GSE)
B31 Publisher side - O
B32 Subscriber side O - Not Supported
91

Users Guide
Table 5.4.1-1 ACSI basic conformance statement
Transmission of sampled value model (SVC)
B41 Publisher side - O
B42 Subscriber side O - Not Supported
a. Shall be M if support for LOGICAL DEVICE model has been declared.
5.4.2. ACSI models conformance statement

Table 5.4.2-1 ACSI models conformance statement
Server (If B1 side supported)
M1 Logical device a a Supported
M2 Logical node b b Supported
M3 Data c c Supported
M4 Data Set d d Supported
M5 Substitution O O Supported
M6 Setting group control O O Supported (through

Transparent XSAT)
Reporting
M7 Buffered report control O O Supported
M7-1 sequence-number
M7-2 report-time-stamp
M7-3 reason-for-inclusion
M7-4 data-set-name
M7-5 data-reference
M7-6 buffer-overflow
M7-7 EntryID
M7-8 BufTim
M7-9 IntgPd
M7-10 GI
M8 Unbuffered report control M M Supported
M8-1 sequence-number
92
Users Guide
Table 5.4.2-1 ACSI models conformance statement
M8-2 report-time-stamp
M8-3 reason-for-inclusion
M8-4 data-set-name
M8-5 data-reference
M8-6 BufTim
M8-7 IntgPd
Logging O O Not Supported
M9 Log control O O
Supported (through
Transparent XSAT)
M9-1 IntgPd
M10 Log O O Not Supported
M11 Control M M Supported
GSE (If B31/B32 is supported)
GOOSE O O Not Supported
M12-1 EntryID
M12-2 DataRefInc
M13 GSSE O O Not Supported
SVC (If 41/42 is supported)
M14 Multicast SVC O O Not Supported
M15 Unicast SVC O O Not Supported
M16 Time Supported

(Time source with
M M
required accuracy
shall be available)
M17 File Transfer O O Supported
a. Shall be M if support for LOGICAL NODE model has been declared.

b. Shall be M if support for DATA model has been declared.
c. Shall be M if support for DATA SET, Substitution, Report, Log Control, or Time model has been declared.
d. Shall be M if support for Report, GSE, or SMV models has been declared.
93

Users Guide
5.4.3. ACSI service conformance statement

The ACSI service conformance statement shall be as defined in Table 5.4.3-1
(depending on the statements in Table 5.4.1-1).
Table 5.4.3-1 ACSI service conformance statement
AA: TP/ Client Server

Comments
MC (C) (S)
Server
S1 ServerDirectory TP M
Application assosiation
S2 Associate M M Supported
S3 Abort M M Supported
S4 Release M M Supported
Logical device
S5 LogicalDeviceDirectory TP M M Supported
Logical node
S6 LogicalNodeDirectory TP M M Supported
S7 GetAllDataValues TP O M Not Supported
Data
S8 GetDataValues TP M M Supported
S9 SetDataValues TP O O Supported
S10 GetDataDirectory TP O M Supported
S11 GetDataDefinition TP O M Supported
Data Set
S12 GetDataSetValues TP O M Supported
S13 SetDataSetValues TP O O Not Supported
S14 CreateDataSet TP O O Supported
S15 DeleteDataSet TP O O Not Supported
S16 GetDataSetDirectory TP O O Supported
Substitution
S17 SetDataValues TP M M Supported
Setting group control
S18 SelectActiveSG TP O O Supported

(through Transparent XSAT)
S19 SelectEditSG TP O O Supported

94
Users Guide

Comments
MC (C) (S)
S20 SetSGValues TP O O Supported

S21 ConfirmEditSGValues TP O O Supported

S22 GetSGValues TP O O Supported

S23 GetSGCBValues TP O O Supported

Reporting
Buffered report control block (BRCB)
S24 Report TP a a Supported
S24-1 data-change (dchg)

S24-2 qchg-change (qchg)
S24-3 data-update (dupd)
S25 GetBRCBValues TP a a Supported
S26 SetBRCBValues TP a a Supported
Unbuffered report control block (URCB)
S27 Report TP a a Supported
S27-1 data-change (dchg)

S27-2 qchg-change (qchg)
S27-3 data-update (dupd)
S28 GetURCBValues TP a a Supported
S29 SetURCBValues TP a a Supported
Logging
Log control block
S30 GetLCBValues TP M M Supported

S31 SetLCBValues TP O M Supported

Log
S32 QueryLogByTime TP b M Not Supported
S33 QueryLogByEntry TP b M Not Supported
95

Users Guide

Comments
MC (C) (S)
S34 GetLogStatusValues TP M M Supported

Generic substation event model (GSE)
GOOSE-CONTROL-BLOCK
S35 SendGOOSEMessage MC c c Not Supported
S36 GetReference TP O d Not Supported
S37 GetGOOSEElementNumber TP O d Not Supported
S38 GetGoCBValues TP O O Supported

S39 SetGoCBValues TP O O Supported

GSSE-CONTROL-BLOCK
S40 SendGSSEMessage MC c c Not Supported
S41 GetReference TP O d Not Supported
S42 GetGSSEElementNumber TP O d Not Supported
S43 GetGsCBValues TP O O Supported

S44 SetGsCBValues TP O O Supported

Transmission of sampled value model (SVC)
Multicast SVC
S45 SendMSVMessage MC e e Not Supported
S46 GetMSVCBValues TP O O Supported

S47 SetMSVCBValues TP O O Supported

Unicast SVC
S48 SendUSVMessage TP e e Not Supported
S49 GetUSVCBValues TP O O Supported

S50 SetUSVCBValues TP O O Supported

Control
S51 Select M M Supported
S52 SelectWithValue TP M M Supported
96
Users Guide

Comments
MC (C) (S)
S53 Cancel TP O M Supported
S54 Operate TP M M Supported
S55 Command-Termination TP M M Supported
S56 TimeActivated-Operate TP O O Not Supported
File transfer
S57 GetFile TP O M Supported
S58 SetFile TP O O Supported
S59 DeleteFile TP O O Supported
S60 GetFileAttributeValues TP O M Supported
Time
T1 Time resolution of internal clock (nearest negative power of 2 in

seconds)
T2 Time accuracy of internal clock T0
T1
T2
T3
T4
T5
T3 supported TimeStamp resolution (nearest negative power of 2 in

seconds)
a. Shall declare support for at least one (BRCB or URCB).

b. Shall declare support for at least one (QueryLogByTime or QueryLogByEntry).
c. Shall declare support for at least one (SendGOOSEMessage or SendGSSEMessage).
d. Shall declare support if TP association is available.
e. Shall declare support for at least one (SendMSVMessage or SendUSVMessage).
97
Users Guide
6. Index
A
ACSI ......................................................................................................... 94
Activating Gateway .................................................................................. 35
Adding
Objects ................................................................................................ 15
AE ............................................................................................................. 10
Alarms and Events (AE) ............................................................................. 9
Analogue value ......................................................................................... 43
Configuration ...................................................................................... 43
Attribute .................................................................................................... 15
B
Binary Counter Reading (BCR) ............................................................... 51
C
CET ........................................................................................................... 10
Command handling
IEC commands ................................................................................... 14
Communication structure ................................................................... 15, 17
Configuring
Objects ................................................................................................ 20
Connectivity Packages .............................................................................. 15
D
DA ............................................................................................................ 10
Data Access (DA) ....................................................................................... 9
Data Object (DO) ................................................................................. 9, 16
Configuration ...................................................................................... 20
Types .................................................................................................. 29
Data Set ...................................................................................................... 9
Device ................................................................................................... 9, 15
Double Point Status (DPS) ....................................................................... 47
E
Engineering tasks ...................................................................................... 15
Event ........................................................................................................... 9
I
IEC 61850
Commands .......................................................................................... 14
Quality ................................................................................................ 41
Taking into use ................................................................................... 15
IED ............................................................................................................. 9
Integer Status (INS) .................................................................................. 48
Intelligent Electronic Device ...................................................................... 9
99
Users Guide
L
LD ............................................................................................................ 10
LN ............................................................................................................ 10
Logical Device (LD) ............................................................................ 9, 15
Logical Node (LN) ............................................................................... 9, 15
M
Mapping
Of AbbCommandBitmask .................................................................. 46
Of DetailedQuality ............................................................................. 42
Quality value to OPC ......................................................................... 42
O
Object Properties ...................................................................................... 30
Objects
Adding objects ................................................................................... 15
Object tree .......................................................................................... 15
OPC
Alarms and Events ............................................................................. 14
Data Access ........................................................................................ 14
Item ...................................................................................................... 9
Operating system time .............................................................................. 14
Originator ................................................................................................. 45
P
Preconfigurations ..................................................................................... 15
Property ...................................................................................................... 9
Protection Activation Information (ACT) ................................................ 49
Protection and control .............................................................................. 15
Pulse Configuration .................................................................................. 44
R
Range Configuration ................................................................................ 44
Report Control Block ............................................................................... 10
S
Sample Value (SAV) ................................................................................ 54
SCL .................................................................................................... 10, 13
Security Violation Counter (SEC) ........................................................... 51
Server features .......................................................................................... 14
Single Point Status (SPS) ......................................................................... 46
Step position with transient indication ..................................................... 44
Subnetwork .............................................................................................. 15
Substation Configuration Language ......................................................... 10
System supervision ................................................................................... 14
T
Time synchronization ............................................................................... 14
TimeStamp ............................................................................................... 45
100
Users Guide
U
Unit ........................................................................................................... 45
V
Vector ....................................................................................................... 45
101
1MRS755321 EN 02.2005
ABB Oy
Substation Automation Products
P.O. Box 699
FI-65101 Vaasa
FINLAND
Tel. +358 10 22 11
Fax. +358 10 224 1094
www.abb.com/substationautomation

IEC 61850 Master Protocol OPC ENb PDF

Uploaded by

Copyright:

Available Formats

IEC 61850 Master Protocol OPC ENb PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IEC 61850 Master Protocol OPC ENb PDF

Uploaded by

Copyright:

Available Formats

MicroSCADA Pro

IEC 61850 Master Protocol (OPC) *1.1

Copyright 2005 ABB Oy, Substation Automation Products, Vaasa, FINLAND 3

5.1.1. Common data attribute types .......................................... 41

5.1.5. Common data class specifications for controllable

1. About this manual

IEC 61850 Master Protocol (OPC) *1.1

1.4. Use of symbols

The information icon alerts the reader to relevant facts and

1.5. Document conventions

System prompts/messages and user responses/input are shown in the Courier

Alarm An abnormal state of a condition.

Device A physical device that behaves as its own communication node in

Event Change of process data or an OPC internal value. Normally, an

Logical Device Representation of a group of functions. Each function is defined as

Logical Node The smallest part of a function that exchanges data. A LN is an

OPC item Representation of connections to data sources, i.e., object

Property Named data item

IEC 61850 Master Protocol (OPC) *1.1

Substation XML-based description language for configurations of electrical

AE Alarms and Events

BRCB Buffered Report Control Block

CET Communication Engineering Tool

DMCD Data Message Code Definition

GW Gateway, component connecting two communication networks

IED Intelligent Electronic Device

OLE Object Linking and Embedding

OPC OLE for Process Control

SCL Substation Configuration Language defined by IEC 61850

SNTP Simple Network Time Protocol

SOAP Simple Object Access Protocol

RCB Report Control Block

URCB Unbuffered Report Control Block

XML eXtended Markup Language

1.8. Related documents

Title MRS number Description

MicroSCADA Pro 1MRS755385 Users Guide for engineering and

1.9. Document revisions

Version Revision number Date History

2.1. Product overview

Network Control Center

Communication Engineering Tool

COM 610 with

MicroSCADA Pro with

Protection and control devices

Fig. 2.1.-1 IEC 61850 OPC Server system overview

IEC 61850 Master Protocol (OPC) *1.1

2.2. IEC 61850 OPC Server features

3.1. Overview of engineering

Table 3.1.-1 IEC 61850 OPC Server related objects

IEC 61850 Object representing a physical subnetwork. IEC 61850 OPC

Attributes Predefined object that contains items for controlling or retrieving

Table 3.1.-1 IEC 61850 OPC Server related objects (Continued)

3.2. Building object tree

If you want to connect Device Connection Status events to device

3.2.1. Adding Gateway or Computer Node object

This applies similarly to the MicroSCADA Pro CET.

Fig. 3.2.1.-1 Adding a COM 610 Gateway object

3.2.2. Adding IEC 61850 OPC Server object