COM600 Station Automation Series DNP 3.0 LAN/WAN Slave … · 1.6. Terminology The following is a...

COM600 Station Automation SeriesDNP 3.0 LAN/WAN Slave (OPC) 3.2

User's Guide

Contents:

1. About this manual .................................................................................. 7

1.1. Copyrights ...................................................................................... 71.2. Trademarks .................................................................................... 71.3. General .......................................................................................... 71.4. Document conventions .................................................................. 81.5. Use of symbols .............................................................................. 91.6. Terminology .................................................................................. 101.7. Abbreviations ............................................................................... 111.8. Related documents ...................................................................... 121.9. Document revisions ..................................................................... 12

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

2.1. Product overview ......................................................................... 132.2. DNP LAN Slave OPC Client features .......................................... 13

3. Configuration ........................................................................................ 14

3.1. About this section ......................................................................... 143.2. Overview of configuration ............................................................ 143.3. Building object tree ...................................................................... 16

3.3.1. General about building object tree ................................ 163.3.2. Adding DNP LAN Slave OPC Client object .................. 173.3.3. Adding Channel objects ................................................ 173.3.4. Adding DNP LAN IED object ........................................ 183.3.5. Adding data objects ...................................................... 18

3.4. Configuring objects ...................................................................... 203.4.1. General about configuring objects ................................ 203.4.2. Configuring DNP LAN Slave OPC Client properties ..... 213.4.3. Configuring DNP LAN Channel properties .................... 223.4.4. Configuring DNP LAN IED properties ........................... 233.4.5. Configuring data objects ............................................... 24

3.4.5.1. General about configuring data objects ...... 243.4.5.2. Directional protection activation information

(ACD) .......................................................... 253.4.5.3. Protection activation information (ACT) ...... 263.4.5.4. Analog set point (APC) ............................... 273.4.5.5. Binary counter reading (BCR) .................... 273.4.5.6. Binary controlled step position information

(BSC) .......................................................... 283.4.5.7. Complex measured value (CMV) ............... 283.4.5.8. Delta (DEL) ................................................. 303.4.5.9. Controllable double point (DPC) ................. 313.4.5.10. Device Name Plate (DPL) .......................... 323.4.5.11. Double point status (DPS) .......................... 323.4.5.12. Controllable integer status (INC) ................ 33

3

DNP 3.0LAN/WAN Slave

(OPC) 3.2

COM600 Station Automation Series1MRS755496

User's GuideIssued: 10.3.2005Version: D/17.06.2008

3.4.5.13. Integer status (INS) .................................... 343.4.5.14. Integer controlled step position information

(ISC) ........................................................... 343.4.5.15. Logical Node Name Plate (LPL) ................. 353.4.5.16. Measured value (MV) ................................. 353.4.5.17. Controllable single point (SPC) .................. 373.4.5.18. Single point status (SPS) ........................... 373.4.5.19. WYE ........................................................... 38

3.4.6. Event definitions ............................................................ 403.4.7. Using scales .................................................................. 40

4. Operation ............................................................................................... 41

4.1. About this section ......................................................................... 414.2. Activating Gateway with new configurations ................................ 414.3. DNP LAN Slave OPC Client diagnostics ..................................... 414.4. DNP LAN Channel diagnostics ................................................... 424.5. DNP LAN IED diagnostics ........................................................... 434.6. Signal diagnostics ........................................................................ 44

5. Technical reference .............................................................................. 46

5.1. About this section ......................................................................... 465.2. IEC 61850 data modeling ............................................................ 46

5.2.1. General about IEC 61850 data modeling ...................... 465.2.2. Single point status (SPS) .............................................. 465.2.3. Double point status (DPS) ............................................ 475.2.4. Integer status (INS) ....................................................... 475.2.5. Protection activation information (ACT) ........................ 475.2.6. Directional protection activation information (ACD) ...... 485.2.7. Binary counter reading (BCR) ....................................... 485.2.8. Measured value (MV) .................................................... 495.2.9. Complex measured value (CMV) .................................. 495.2.10. WYE .............................................................................. 495.2.11. Delta (DEL) ................................................................... 505.2.12. Controllable single point (SPC) ..................................... 505.2.13. Controllable double point (DPC) ................................... 515.2.14. Controllable integer status (INC) ................................... 515.2.15. Binary controlled step position information (BSC) ........ 525.2.16. Integer controlled step position information (ISC) ......... 525.2.17. Analogue set point (APC) ............................................. 52

5.3. Status codes ................................................................................ 525.3.1. Introduction ................................................................... 525.3.2. Link layer status codes ................................................. 535.3.3. Application layer status codes ...................................... 53

5.4. Attributes ...................................................................................... 545.4.1. General about attributes .............................................. 545.4.2. DNP LAN Slave OPC Client attributes .......................... 545.4.3. DNP LAN Channel attributes ........................................ 55

4

1MRS755496COM600 Station Automation SeriesDNP 3.0LAN/WAN Slave(OPC) 3.2 User's Guide

5.4.4. DNP LAN IED attributes ............................................... 56

Appendix 1 ................................................................................................... 58

Device profile .......................................................................................... 58

Index .............................................................................................................. 85

5


(OPC) 3.2


User's Guide

About this manual1.

Copyrights1.1.

The information in this document is subject to change without notice and should not beconstrued as a commitment by ABB Oy. ABB Oy assumes no responsibility for anyerrors that may appear in this document.

In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB Oybe liable for incidental or consequential damages arising from use of any software orhardware described in this document.

This document and parts thereof must not be reproduced or copied without written per-mission from ABB Oy, and the contents thereof must not be imparted to a third partynor used for any unauthorized purpose.

The software or hardware described in this document is furnished under a license andmay be used, copied, or disclosed only in accordance with the terms of such license.

© Copyright 2006 ABB. All rights reserved.

Trademarks1.2.

ABB is a registered trademark of ABB Group. All other brand or product names men-tioned in this document may be trademarks or registered trademarks of their respectiveholders.

General1.3.

This manual provides thorough information on the OPC Client for DNP 3.0 LAN/WANSlave protocol (later in this manual DNP LAN Slave OPC Client) and the central conceptsrelated to it. You will find instructions on to take it into use. The basic operation proced-ures are also discussed.

Information in this user’s guide is intended for application engineers who need to con-figure DNP LAN Slave OPC Client to establish data transfer between the DNP mastersystem and process devices connected to COM600.

As a prerequisite, you should understand DNP protocol and the basic procedures inCOM600 Communication Engineering Tool (CET).

This user’s guide is divided into following sections:

7


(OPC) 3.2


User's Guide

Introduction

This section gives an overview of the DNP LAN Slave OPC Client and its features.

Configuration

In this section you will find an overview of the configuration tasks and instructionson how to create and configure DNP LAN Slave OPC Client related objects.

Operation

This section covers the basic operation procedures you can carry out when transferringor activating the Communication Gateway COM610 computer or Station Computer615 with new configurations.

You are also given instructions on how to monitor and control the DNP communica-tion.

Technical reference

This section describes the IEC 61850 data modeling, contains attributes and a list ofstatus codes.

Document conventions1.4.

The following conventions are used for the presentation of 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, press the ENTER key.• 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: MenuName > Menu-Item > CascadedMenuItem. For example: select File > New > Type.

• The Start menu name always refers to the Start menu on the Windows taskbar.• System prompts/messages and user responses/input are shown in the Courier font.

For example, if you enter a value out of range, the following message is displayed:

8


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 followsin the procedure:

MIF349• Variables are shown using lowercase letters:

sequence name

Use of symbols1.5.

This publication includes warning, caution, and information icons that point out safetyrelated conditions or other important information. It also includes tip icons to point outuseful information to the reader. The corresponding icons should be interpreted as follows.

The electrical warning icon indicates the presence of a hazardwhich could result in electrical shock.

The warning icon indicates the presence of a hazard whichcould result in personal injury.

The caution icon indicates important information or warningrelated to the concept discussed in the text. It might indicatethe presence of a hazard which could result in corruption ofsoftware or damage to equipment or property.

The information icon alerts the reader to relevant facts andconditions.

The tip icon indicates advice on, for example, how to designyour project or how to use a certain function.

9


(OPC) 3.2


User's Guide

Terminology1.6.

The following is a list of terms associated with the DNP LAN Slave OPC Client thatyou should be familiar with. The list contains terms that are unique to ABB or have ausage or definition that is different from standard industry usage.

DescriptionTerm

An abnormal state of a condition.Alarm

An OPC service for providing information about alarms andevents to OPC clients.

Alarms and Events; AE

An OPC service for providing information about process data toOPC clients.

Data Access; DA

Part of a logical node object representing specific information,e.g., status or measurement. From an object-oriented point ofview a data object is an instance of a class data object. DOs arenormally used as transaction objects; i.e., they are data struc-tures.

Data Object; DO

The data set is the content basis for reporting and logging. Thedata set contains references to the data and data attribute val-ues.

Data Set

A physical device that behaves as its own communication nodein the network, e.g. protection relay.

Device

Change of process data or an OPC internal value. Normally, anevent consists of value, quality and timestamp.

Event

A physical IEC 61850 device that behaves as its own commu-nication node in the IEC 61850 protocol.

Intelligent Electronic Device

Representation of a group of functions. Each function is definedas a logical node. A physical device consists of one or severalLDs.

Logical Device; LD

The smallest part of a function that exchanges data. A LN is anobject defined by its data and methods.

Logical Node; LN

A communication protocol developed by Echelon.LON

A proprietary method of ABB on top of the standard LON pro-tocol.

LON Application Guideline forsubstation automation; LAG

Series of standards specifications aiming at open connectivityin industrial automation and the enterprise systems that supportindustry.

OPC

Representation of a connection to the data source within theOPC server. An OPC item is identified by a string <objectpath>:<property name>. Associated with each OPC item areValue, Quality and Time Stamp.

OPC item

Named data item.Property

The report control block controls the reporting processes forevent data as they occur. The reporting process continues aslong as the communication is available.

Report Control Block

10


DescriptionTerm

ABB proprietary communication protocol used in substationautomation.

SPA

Protection and/or Control Product supporting the SPA protocolversion 2.5 or earlier.

SPA device

XML-based description language for configurations of electricalsubstation IEDs. Defined in IEC 61850 standard.

Substation Configuration Lan-guage; SCL

Abbreviations1.7.

The following is a list of abbreviations associated with the DNP LAN Slave OPC Clientthat you should be familiar with. See also 1.6, Terminology.

DescriptionAbbreviation

Alarms and EventsAE

Application Service Data UnitASDU

Buffered Report Control BlockBRCB

Communication Engineering ToolCET

Data AccessDA

Data Message Code DefinitionDMCD

Data ObjectDO

Gateway, component connecting two communication networks togetherGW

Human Machine InterfaceHMI

International Electrotechnical CommissionIEC

Intelligent Electronic DeviceIED

LON Application Guideline for substation automationLAG

Local Area NetworkLAN

Logical DeviceLD

LonMark interoperable device communicating in LonWorks network. Inthis document the term is used for devices that do not support the ABBLON/LAG communication.

LMK

Logical NodeLN

LON SPA GatewayLSG

Network Control CenterNCC

Network VariableNV

Object Linking and EmbeddingOLE

OLE for Process ControlOPC

Protection & ControlP&C

11


(OPC) 3.2


User's Guide

DescriptionAbbreviation

Request To SendRTS

Substation AutomationSA

Substation Configuration LanguageSCL

Single Line DiagramSLD

Simple Network Time ProtocolSNTP

Simple Object Access ProtocolSOAP

Report Control BlockRCB

Unbuffered Report Control BlockURCB

eXtended Markup LanguageXML

Related documents1.8.

MRS numberName of the manual

1MRS756125COM600 User’s Guide

Document revisions1.9.

HistoryProduct revisionDocument version/date

Document created1.0A/10.3.2005

Document revised3.0B/16.10.2006

Document revised3.1C/21.12.2007

Document revised3.2D/17.06.2008

12


Introduction2.

Product overview2.1.

The DNP protocol slave interface of the Communication Gateway COM610 and theStation Computer COM615 enables master systems communicating with DNP protocolto receive data from and deliver commands to P&C devices connected to the GW. TheDNP slave is implemented as an OPC client, which transfers and converts data betweenthe DNP slave protocol interface and the OPC servers of the COM600. See COM600User's Guide for more details.

The DNP LAN Slave OPC Client is configured using the Communication EngineeringTool (CET). Communication Engineering Tool (CET) can also be used for diagnosingand controlling the operation of the DNP LAN Slave OPC Client. COM610/615 has aweb server that can be used for remote diagnostic of the Gateway including the DNPLAN Slave OPC Client.

The DNP LAN Slave OPC Client uses TCP/IP communication over the LAN interface.Before you can start using the DNP LAN Slave OPC Client, at least one OPC server hasto be configured to provide access to the process devices. In this manual, the term “Device” is used for a virtual station in the COM610/615 representing the slave stationsvisible to the master system. In this guide, the term "DNP LAN IED" is used for a virtualstation in COM610/615 representing the slave stations visible to the DNP master system.

DNP LAN Slave OPC Client features2.2.

The DNP LAN Slave OPC Client supports the following features:• OPC Data Access Client v. 1.0/2.0 for accessing data from the OPC servers• OPC Alarms and Events specifications v. 1.10 for diagnostic and control purposes• IEC 61850 data modeling• System supervision:

• NCC connection supervision• DNP 3.0 subset level 2 and level 3 support.

13


(OPC) 3.2


User's Guide

Configuration3.

About this section3.1.

This section guides you in the configuration tasks required before you can start usingthe DNP LAN Slave OPC Client. For information on the IEC 61850 data modeling, referto the COM600 User's Guide.

First you need to start Communication Engineering Tool (CET) to open a project whereat least one OPC server has been configured. You can also open and name a new project,where you configure at least one OPC server.

1. Select File > Open/Manage Project....2. In the Open/Manage Project dialog, select the required location for the project:

• Projects on my computer• Projects on network

3. Select New Project on the left.• Enter a Project Name. The Description is optional.

4. Click Create5. Click Open Project

Overview of configuration3.2.

Before you can start using the DNP LAN Slave OPC Client, you need to build and con-figure an object tree in Communication Engineering Tool (CET) to define the Commu-nication structure within the Gateway object.

• DNP LAN Slave OPC Client• DNP LAN Channel• DNP LAN IED• Data objects

Figure 3.2-1 shows an example view of Communication Engineering Tool (CET)including an object tree in the communication structure on the left and Object Propertieswindow displaying the object properties on the right.

When configuring OPC servers the following characters cannotbe used in object names: \ ` ' ' #

14


DNP_Slave_LANWAN_configuration_overview.bmp

Figure 3.2-1 Example view of Communication Engineering Tool (CET)

The configuration work can basically be divided into two separate tasks:1. building an object tree, and2. configuring object properties.

First, you need to build an object tree. This is done by adding objects to the object tree,see 3.3.1, General about building object tree and 3.3.5, Adding data objects.

Figure 3.2-1 shows an example of how the object tree may look like after it has beenbuilt. In the example tree you can see the DNP LAN Slave OPC Client object and itschild objects like channels, devices, and data objects. Indentation is used to indicate theparent-child relationship between the objects.

After you have added the necessary objects to the object tree in the communicationstructure, you need to configure them, see 3.4.1, General about configuring objects.

Table 3.2-1 describes the objects shown in the object tree (Figure 3.2-1).

Table 3.2-1 DNP LAN Slave OPC Client related objectsDescriptionObject

An object representing the DNP LAN Slave OPC Client.DNP LAN Slave OPC Client

An object representing the channelDNP LAN Channel

15


(OPC) 3.2


User's Guide

DescriptionObject

A DNP LAN IED is used for a virtual station in theCOM610/615 representing the slave stations visible tothe DNP master system.

DNP LAN IED

A data object is an instance of one of the IEC Commondata classes, for example single point status, measuredvalue etc. Depending on the class, each data object hasa set of attributes for monitoring and controlling the object,for instance value, quality and control. Data objects areconnected from OPC servers to the DNP LAN Slave OPCClient with the cross reference function. They are shownas child objects of the DNP LAN IED object in the objecttree.

Data Object (DO)

Event definitions are used for the diagnostic OPC A&EServer.

Event Definitions

Building object tree3.3.

General about building object tree3.3.1.

The object tree is built in the Communication structure of the COM600 EngineeringTool, see Figure 3.2-1. It is built by adding objects in a logical order starting from theDNP LAN Slave OPC Client object.

Before the DNP LAN Slave OPC Client can be taken into use, an OPC server has to beconfigured for the process communication. For more information on creating an OPCserver, refer to COM600 User's Guide.

You have several possible ways to add objects to the object tree in the Communicationstructure:• You can right-click the object to which you want to add a child object.• You can copy the object.

Add the objects in the following order:1. DNP LAN Slave OPC Client2. DNP LAN Channel3. DNP LAN IED4. Data objects

For information on building a substation structure, refer to COM605, COM615 HMIConfiguration Manual.

16


Adding DNP LAN Slave OPC Client object3.3.2.

To start building the object tree, add the DNP LAN Slave OPC Client object in theCommunication structure by selecting the Gateway object, right-click it and select New> DNP > DNP LAN Slave OPC Client, see Figure 3.3.2-1 .

A040342.jpg

Figure 3.3.2-1 Adding a new DNP LAN Slave OPC Client object

Adding Channel objects3.3.3.

After the DNP LAN Slave OPC Client object has been successfully added, you cancontinue building the object tree by adding a DNP LAN Channel object.

To add DNP LAN Channel object:1. Select a DNP LAN Slave OPC Client object and right-click it.2. Add a DNP LAN Channel object.3. Rename the new object. Note that the names of the DNP LAN Channel objects

within a DNP LAN Slave OPC Client have to be unique.

17


(OPC) 3.2


User's Guide

Adding DNP LAN IED object3.3.4.

After a channel object has been successfully added, you can continue building thestructure by adding the DNP LAN Channel object. All the data can be connected to onedevice or divided to several slave devices. Before dividing data to several slave devices,it must be checked that the current protocol mode and the master system support thefeature.

To add DNP LAN IED object:1. Select a DNP LAN Channel object.2. Add a DNP LAN IED object.3. Rename the new object. Note that the names within DNP LAN Channel have to be

unique.

Adding data objects3.3.5.

Data objects are added somewhat differently than the upper level objects. Basically, youdrag and drop the data objects you need from an OPC server to the DNP LAN SlaveOPC Client.

To add data objects:1. Select DNP LAN IED object and right-click it.2. Select Cross References. The Cross References window appears (Figure 3.3.5-1).3. In the Project Explorer, select now a logical node within an OPC server, from which

you want to connect the data objects to the DNP LAN Slave OPC Client.Note that you can also select an upper level (server, channel, etc.) object and dragand drop it into the Cross Reference window. As a result, all the data objects withinthe selected object appear now in the Cross References window and can be connectedto the DNP LAN Slave OPC Client.

4. Drag and drop the logical node into the Cross References window. The data objectswithin the logical node appear now in the Cross References window.Note that only data objects that have been given a non zero information value in theCross References table will be connected to the DNP LAN IED.

5. At this point, click Apply to create the cross references (to connect the data objectsto the DNP LAN IED).

18


A040343.jpg

Figure 3.3.5-1 The Cross References window

How to use the Cross References window

In the Cross References window, you can use a filter file to leave out some of the dataobjects to be connected to DNP LAN IED. Select the filter file to be used from the drop-down menu Active Filter (see Figure 3.3.5-1). If there are no filter files listed in the drop-down menu, you can create your own filter file by clicking Modify Filter File. You canalso modify an existing filter file to meet your needs.

The Cross References table allows you to view the data objects by type. Use the tabs inthe upper part of the table to do this. Under the General tab, you can see all the dataobjects and their property values. Here you can sort the data objects by clicking thecolumn heading (Object Name, Description, Common Data Class , etc.).

There is a possibility to export the cross references table to Microsoft Excel and to importthe table from Microsoft Excel.

Clicking Apply connects the data objects to the DNP LAN IED . After clicking Apply,you can change the data object values either in the Object Properties window or in theCross References window. For more detailed instructions on configuring the data objectproperties in the Cross References window, see 3.4.5.1, General about configuring dataobjects .

19


(OPC) 3.2


User's Guide

Configuring objects3.4.

General about configuring objects3.4.1.

After the objects have been added, you need to configure the object properties. Fig-ure 3.4.1-1 shows an example of how to use Communication Engineering Tool (CET)to configure the object properties for DNP LAN Slave OPC Client.

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. The properties

and their values can be viewed as shown in Figure 3.4.1-1.

ObjProp.jpg

Figure 3.4.1-1 Example of object properties in the Objects Properties window

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 menu, or• entering a text string or a numerical value in a text field.

20


The available properties for different objects are listed in the following subsections.

Configuring DNP LAN Slave OPC Client properties3.4.2.

Table 3.4.2-1 lists the configurable DNP LAN Slave OPC Client properties and valueranges for them. The actual configuration by using the COM600 CommunicationEngineering Tool (CET) is performed as described in 3.4.1, General about configuringobjects.

Table 3.4.2-1 DNP LAN Slave OPC Client propertiesDescriptionValue or Value range/ DefaultProperty / Para-

meter

Basic

Specifies the maximum time in secondsthat any connected (configured) OPCServer requires to retrieve all its initialdata.

0...65535

Default: 5

Maximum OPCServer InitializationTime

Instance identification of diagnostic OPCalarm and event server.

Prog ID AE

Instance identification of diagnostic OPCdata access server.

ProgID DA

The value of this property in minutes isadded to the synchronization time receivedfrom a DNP master.

-720...720

Default: 0

Time Zone Correc-tion

Station/RemoteSwitch

Specifies if a position check for the stationremote switch is going to be made.

Do not check Station/Remoteswitch position.

Check Station/Remote switchposition.

Default: Do not check Sta-tion/Remote switch position.

Station/RemoteSwitch Handling

Defines command handling if the positionis bad or unknown.

Reject commands if positionbad or unknown.

Allow commands if position bador unknown.

Default: Reject commands ifposition bad or unknown

Station/RemoteSwitch Error

21


(OPC) 3.2


User's Guide

Configuring DNP LAN Channel properties3.4.3.

The DNP LAN channel properties that can be configured and value ranges for them canbe found in Table 3.4.3-1. The actual configuration by using the CET is performed asdescribed in 3.4.1, General about configuring objects.

Table 3.4.3-1 DNP LAN Channel propertiesDescriptionValue or Value range/ DefaultProperty / Para-

meter

Basic

Specifies whether the channel is in use ornot.

In use

Not in use

Default: In use

In Use

ProtocolDNP Slave over LAN interfaceProtocol

CommunicationPort

The IP address which is locally used.Default: 127.0.0.1Local Address

CommunicationControl

Specifies if incoming connection requestsare checked.

True

False

Default: False

Check ConnectionRequest

ConnectionTypeDescDefault: TCP/IPConnection Type

Determines whether the link layer confirm-ations are in use.

In use Not in use Default: Inuse

Link Layer Confirma-tions Enabled

Maximum length of a data link fragment.50...249

Default: 230

Maximum MessageLength

Delay in milliseconds between the testfunction of link commands. If the value isset to zero, the test function of a link com-mand is not sent.

0...65535

Default: 500

Test Function ofLink Interval

Specifies the time in seconds that the DNP3.0 link waits for the end of the receivedmessage.

0...255

Default: 2

Response Timeout

Specifies if “Test Function for Link” isenabled.

True

False

Default: False

Test Function ForLink

22


Configuring DNP LAN IED properties3.4.4.

Table 3.4.4-1 lists the configurable properties for DNP LAN IED and value ranges forthese properties. The actual configuration by using the CET is performed as describedin 3.4.1, General about configuring objects.

Table 3.4.4-1 DNP LAN IED propertiesDescriptionValue/Value rangeName

Basic

Specifies whether diagnostic AE eventsare sent for the station.

True

False

Default: False

Diagnostics Enabled

Defines if the IED is in use or not.In use

Not in use

Default: In use

In Use

Defines the subset level that is currentlyused.

Subset 2

Subset 3

Default: Subset 2

Subset

Addresses

The IP address of the remote host.Default: 127.0.0.1Internet Address

The station address of the master station.0...65535

Default: 1

Master Address

The station address of the DNP 3.0 slavestation.

0...65535

Default: 1

Slave Address

CommunicationControl

Sending messages while waiting for aconfirmation.

True

False

Default: True

Sending Messages

Variations in response messages.True

False

Default: True

Use Variations

Command Hand-ling

The object address of the bitstream pro-cess object.

0...65535

Default: 32000

Command Address

23


(OPC) 3.2


User's Guide

DescriptionValue/Value rangeName

The maximum time in seconds that theslave waits for an execute command afterreceiving an operator command.

0...65

Default: 30

Execute WaitingTime after Select

Lengths

The length of a data object address usedin the DNP 3.0 messages.

1...3

Default: 2

Information AddressLength

Time Handling

Determines the behavior of the slavedevice when it receives a time synchroniz-ation message.

Handled, time set Positiveacknowledged, time not set

Negative acknowledged, timenot set

Default: Handled, time set

Time Synchroniza-tion

Queues

Defines a threshold (percent of the queuecapacity) which causes that update of ameasurement removes the oldest entry ofthe same measurement from the queue.

1...100

Default: 95

MeasurementQueue Threshold

Maximum number of measurement pro-cess data changes that are stored intern-ally in a queue in the client.

0...65535

Default: 0

MeasurementsUpdate Queue

Maximum number of state indication pro-cess data changes that are stored intern-ally in a queue in the client.

0...65535

Default: 0

State IndicationsUpdates Queue

Configuring data objects3.4.5.

General about configuring data objects3.4.5.1.

You can configure data objects either in the Object Properties window or in the CrossReferences window.

The actual configuration in Object Properties window by using the COM600 Commu-nication Engineering Tool (CET) is performed as described in 3.4.1, General aboutconfiguring objects.

To configure the data objects in Cross References window:

1. Select the IED object in the object tree and right-click it.2. Choose the Cross References window from the context menu.3. Change the values in cross references table by simply writing the new value in table

cell with the desired property.4. Finally, click Apply to save the changes.

24


The parameters are stored in Object properties in the COM600 Communication Engin-eering Tool (CET) (see the tables for each data object type).

Clicking Apply connects the data objects to the IED. The connected data objects willappear as child objects for the IED. The cross reference information can then be alsomodified by selecting the data object and using the object properties window.

When configuring address values for DNP IED data objects,the valid address range is 0 to 65535. If the value is -1, thenthe address is not available.

Note that if you make changes in the object names or structuring of objects of OPCServer, which are connected to the IED, you must re-open the cross reference tool andverify that the changes are correctly handled and then click Apply to update the config-uration accordingly.

DNP OPC Client supports data objects for status, measurements, controllable status andcontrollable analog information. The following subsections list the configurable dataobject properties for the DNP OPC Client.

Directional protection activation information (ACD)3.4.5.2.

Table 3.4.5.2-1 Configurable ACD properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic

Common data class according to IEC61850.

ACDCommon DataClass

Addresses

General Index-1 to 65535

Default: -1

General Index

Neutral Index-1 to 65535

Default: -1

Neutral Index

Phase A Index-1 to 65535

Default: -1

Phase A Index

Phase B Index-1 to 65535

Default: -1

Phase B Index

Phase C Index-1 to 65535

Default: -1

Phase C Index

25


(OPC) 3.2


User's Guide

DescriptionValue or Value range/ DefaultProperty/ Para-meter

Data Class Spe-cific

Object number for indication.Binary input (1, 2)

Binary output (10)

Default: Binary input (1, 2)

Indication Object

Protection activation information (ACT)3.4.5.3.

Table 3.4.5.3-1 Configurable ACT properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


ACTCommon DataClass

Addresses

General Index-1 to 65535

Default: -1

General Index

-1 to 65535

Default: -1

Neutral Index


Default: -1

Phase A Index


Default: -1

Phase B Index


Default: -1

Phase C Index

-1 to 65535

Default: -1



Binary output (10)


Indication Object

26


Analog set point (APC)3.4.5.4.

Table 3.4.5.4-1 Configurable APC properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


APCCommon DataClass

Addresses

Control index.-1 to 65535

Default: -1

Control Index


Variation for control0 to 65535

Default: 2

Control Variation

Binary counter reading (BCR)3.4.5.5.

Table 3.4.5.5-1 Configurable BCR properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


BCRCommon DataClass

Addresses

Indication index.-1 to 65535

Default: -1

Indication Index


Object number for counter.Binary counter (20)

Frozen counter (21)

Default: Binary counter (20)

Counter Object

Specifies the multiplier for current SI unit.Default: DekaMultiplier

SI unit for measurement as described inIEC61850

Default: DimensionlessUnit

27


(OPC) 3.2


User's Guide

Binary controlled step position information (BSC)3.4.5.6.

Table 3.4.5.6-1 Configurable BSC properties for OPC clientDescriptionValue or Value range/

DefaultProperty/ Parameter

Basic

Common data class according to IEC 61850.BSCCommon Data Class

Addresses


Default: -1

Control Index


Default: -1

Indication Index

Data Class Specific

Qualifier for control.Momentary

Latched

Pulsed

Default: Momentary

Control Code Qualifier

Variation for control0 to 65535Control Variation

Specifies using two-step, select-before-operatemethod for issuing control request or not.

Direct Operate

Select Before Operate

Default: Direct Operate

Operate

Scale and Unit

Scale to be used with this type.Default: NoneScale

Complex measured value (CMV)3.4.5.7.

Table 3.4.5.7-1 Configurable CMV properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


CMVCommon DataClass

Addresses


Default: -1

Index

28



Sub-Type

MV sub-typeSimpleSubtype


Object number for indication.Analog input (30, 32)

Analog output (40)

Default: Analog input (30, 32)

Indication Object

Scale and Unit


Specifies the number of decimals shownin HSI. (0 to 9)

Default: 0Phase Number ofDecimals




Limit Value Super-vision

Maximum value for measurementMax

Minimum value for measurementMin

Table 3.4.5.7-2 Additional configurable properties for Sub-Type Limit CheckDescriptionValue or Value range/ DefaultProperty/ Para-

meter

MVSubTypeDescriptionLimit CheckSub-Type


High limit for measurement. Event is cre-ated when value crosses the limit.

Default: 0High

High-high limit for measurement. Event iscreated when value crosses the limit.

Default: 0High-High

Low limit for measurement. Event is cre-ated when value crosses the limit.

Default: 0Low

Low-low limit for measurement. Event iscreated when value crosses the limit.

Default: 0Low-Low

29


(OPC) 3.2


User's Guide

Delta (DEL)3.4.5.8.

Table 3.4.5.8-1 Configurable DEL properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


DELCommon DataClass

Addresses

Phase AB Index-1 to 65535

Default: -1

Phase AB Index

Phase BC Index-1 to 65535

Default: -1

Phase BC Index

Phase CA Index-1 to 65535

Default: -1

Phase CA Index

Sub-Type

DEL SubtypeDEL SimpleSubtype



Analog output (40)


Indication Object

Scale and Unit

Specifies the multiplier for current SI unit.Default: DekaPhase Multiplier

Specifies the number of decimals shownin HSI.

0 to 9

Default: 0

Phase Number ofDecimals




Table 3.4.5.8-2 Additional configurable properties for Sub-Type Limit CheckDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Sub-type of current data objectDEL FullSub-Type



Default: 0High

30




Default: 0High-High


Default: 0Low


Default: 0Low-Low

Controllable double point (DPC)3.4.5.9.

Table 3.4.5.9-1 Configurable DPC properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


DPCCommon DataClass

Addresses

Index for Control Close command.-1 to 65535

Default: -1

Control Index Close

Index for Control Open command.-1 to 65535

Default: -1

Control Index Open

Index for 52a.-1 to 65535

Default: 11

Index 52a

Index for 52b.-1 to 65535

Default: 12

Index 52b

Index for Breaker Failure Indication.-1 to 65535

Default: 12

Index BFI


Qualifier for control.Momentary

Latched

Pulsed

Default: Momentary

Control Code Quali-fier

Object number for control.Binary control output block(12).

Control Object

Variation for control0 to 65535Control Variation

31


(OPC) 3.2


User's Guide



Binary output (10)


Indication Object

DNP direct operate of SBO (function codeconfiguration).

True

False

Default: True

Operate

Device Name Plate (DPL)3.4.5.10.

Table 3.4.5.10-1 Configurable LPL properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic

61850 Data ObjectDPL61850 Data Object


Text string describing hardware revision.1.0Hardware revision

Text string describing location.User defined

Default: Vaasa

Location

Text string describing serial number.User defined.

Default: ABB123456789

Serial number

Text string describing software revision.Default: 1.0Software Revision

Text string describing vendor.ABBVendor

Double point status (DPS)3.4.5.11.

Table 3.4.5.11-1 Configurable DPS properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


DPSCommon DataClass

Addresses

32



Index for 52a.-1 to 65535

Default: -1

Index 52a

Index for 52b.-1 to 65535

Default: -1

Index 52b

Index for Breaker Failure Indication.-1 to 65535

Default: -1

Index BFI


Object number for indication.Binaryinput(1,2)

Binaryoutput(10)

Default: Binaryinput(1,2)

Indication Object

Controllable integer status (INC)3.4.5.12.

Table 3.4.5.12-1 Configurable INC properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic

Common data class according to IEC61850

INCCommon DataClass

Addresses


Default: -1

Control Index

Index.-1 to 65535

Default: -1

Index


Object number for control.Default: Analog control outputblock (41).

Control Object

Variation for control.0 to 65535

Default: 2

Control Variation


Analog output (40)


Indication Object

33


(OPC) 3.2


User's Guide


Scale and Unit


Integer status (INS)3.4.5.13.

Table 3.4.5.13-1 Configurable INS properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


INSCommon DataClass

Addresses

Index.-1 to 65535

Default: -1

Index



Analog output (40)


Indication Object

Scale and Unit


Integer controlled step position information (ISC)3.4.5.14.

Table 3.4.5.14-1 Configurable ISC properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


ISCCommon DataClass

Addresses


Default: -1

Control Index

34




Default: -1

Indication Index


Object number for control.Default: Analog control outputblock (41).

Control Object


Default: 2

Control Variation


Analog output (40)


Indication Object

Scale and Unit


Logical Node Name Plate (LPL)3.4.5.15.

Table 3.4.5.15-1 Configurable LPL properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic

61850 Data ObjectLPL61850 Data Object


Text string describing serial number.User defined.

Default: ABB123456789

Serial number

Text string describing software revision.Default: 1.0Software Revision

Text string describing vendor.ABBVendor

Measured value (MV)3.4.5.16.

Table 3.4.5.16-1 Configurable MV properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic

35


(OPC) 3.2


User's Guide



MVCommon DataClass

Addresses


Default: -1

Index

Sub-Type

MV Sub-typeSimpleSubtype


Data object number for indication.Analog input (30, 32)

Analog output (40)


Indication Object

Scale and Unit


Specifies the number of decimals shownin HSI. (0..9)

Default: 0Phase Number ofDecimals

Scale to be used with this typeDefault: NoneScale




Maximum value for measurementMax

Minimum value for measurementMin

Table 3.4.5.16-2 Additional configurable properties for Sub-Type MV Limit CheckDescriptionValue or Value range/ DefaultProperty/ Para-

meter

MVSubTypeDescriptionMV Limit CheckSub-Type



Default: 0High


Default: 0High-High


Default: 0Low


Default: 0Low-Low

36


Controllable single point (SPC)3.4.5.17.

Table 3.4.5.17-1 Configurable SPC properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


SPCCommon DataClass

Addresses


Default: -1

Control Index


Default: -1

Indication Index


Momentary

Pulse

Latch

Default: Momentary

Control Code Quali-fier

Object number for control.Default: Binary control outputblock (12).

Control Object


Default: 1

Control Variation


Binary output (10)


Indication Object

Specifies using two-step, select-before-operate method for issuing control requestor not.

Direct Operate

Select Before Operate

Default: Direct Operate

Operate

Single point status (SPS)3.4.5.18.

Table 3.4.5.18-1 Configurable SPS properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic

37


(OPC) 3.2


User's Guide


Common data class according to IEC61850

SPSCommon DataClass

Addresses

Index.-1 to 65535

Default: -1

Index


Object number for indication.Binaryinput(1,2)

Binaryoutput(10)

Default: Binaryinput(1,2)

Indication Object

WYE3.4.5.19.

Table 3.4.5.19-1 Configurable WYE properties for OPC clientDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Basic


WYECommon DataClass

Sub-Type

Subtype of WYEWYE SimpleSubtype

Addresses

Neutral Index-1 to 65535

Default: -1

Neutral Index


Default: -1

Phase A Index


Default: -1

Phase B Index


Default: -1

Phase C Index


38




Analog output (40)


Indication Object

Scale and Unit

Specifies the multiplier for the current SIunit.

Default: DekaNeutral Multiplier

Scale for neutral to be used with this dataobject.

Default: NoneNeutral Scale

Unit for Neutral phaseDefault: DimensionlessNeutral Unit

Specifies the number of decimals shownin HSI

0 to 9

Default: 0

Neutral Number ofDecimals

Specifies the multiplier for the current SIunit.

Default: DekaPhase Multiplier

Scale for phases to be used with this dataobject.

Default: NonePhase Scale

Unit for phasesDefault: DimensionlessPhase Unit

Specifies the number of decimals shownin HSI

0 to 9

Default: 0

Phase Number ofDecimals

Phase Limit ValueSupervision

Maximum value for measurement.Default: 20000Max

Minimum value for measurement.Default: 0Min

Neutral Limit ValueSupervision

Maximum value for measurement.Default: 20000Max

Minimum value for measurement.Default: 0Min

Table 3.4.5.19-2 Additional configurable properties for Sub-Type WYE FullDescriptionValue or Value range/ DefaultProperty/ Para-

meter

Subtype of WYEWYE FullSub-Type

Phase Limit ValueSupervision


Default: 0High


Default: 0High-High

39


(OPC) 3.2


User's Guide



Default: 0Low


Default: 0Low-Low

Neutral Limit ValueSupervision


Default: 0High


Default: 0High-High


Default: 0Low


Default: 0Low-Low

Event definitions3.4.6.

For information on event definitions, refer to COM600 User’s Guide.

Using scales3.4.7.

For information on using scales, refer to COM600 User’s Guide.

40


Operation4.


This section describes the basic operation procedures you can carry out after the objectproperties for the DNP LAN Slave OPC Client have been configured.

After this, you can, for example, monitor and control the condition of connections innetwork. This is done by using the Online diagnostics function in CommunicationEngineering Tool (CET).

Activating Gateway with new configurations4.2.

For information on activating Gateway with new configurations, refer to COM600 User’sGuide.

DNP LAN Slave OPC Client diagnostics4.3.

To view version information on DNP LAN Slave OPC Client or to monitor and controlthe state of the client, right-click the DNP LAN Slave OPC Client object and selectOnline diagnostics, see Figure 4.3-1.

A040346.jpg

Figure 4.3-1 DNP LAN Slave OPC Client Online diagnostics

In Online diagnostics box you can:• reset DNP LAN Slave OPC Client• view the event log file, see Figure 4.3-2• clear the event log file

41


(OPC) 3.2


User's Guide

A040347.jpg

Figure 4.3-2 Event log file

DNP LAN Channel diagnostics4.4.

The DNP LAN Channel activity can be monitored with the Online diagnostics function.

You can also take a channel into use or out of use as described in this section.

To monitor and control DNP LAN Channel activity:1. Select the channel you want to monitor in the object tree of Communication

Engineering Tool (CET).2. Right-click the channel.3. Select Online diagnostics.

A040348.jpg

Figure 4.4-1 DNP LAN Channel Online diagnostics

In the Diagnostic counters field, you can monitor the channel activity. The availableattributes can be seen in Figure 4.4-1. To reset Diagnostic counters, click Reset counters.

42


You can take a DNP LAN Channel into use by marking the In use check box. If youunmark the check box, the channel is taken out of use. To manually update diagnosticcounters, click Refresh.

DNP LAN IED diagnostics4.5.

The DNP LAN IED communication can be monitored with the Online diagnosticsfunction. You can also take a device into use or out of use as described in this section.

To monitor and control DNP LAN IED communication:1. Select the device you want to monitor in the object tree of the Communication

Engineering Tool (CET).2. Right-click the device.3. Select Online diagnostics.

In the Status information field, you can monitor the device status.

The Diagnostic counters field provides information on device activity. To reset diagnosticcounters, click Reset counters.

You can take a DNP LAN IED into use by marking the In use check box. If you unmarkthe check box, the device is taken out of use. To manually update diagnostic counters,click Refresh.

43


(OPC) 3.2


User's Guide

A040349.jpg

Figure 4.5-1 DNP LAN IED Online diagnostics

Signal diagnostics4.6.

The DNP LAN Slave OPC client has a diagnostic function which makes it possible tomonitor the flow of process data changes and commands. The diagnostic function isactivated by marking the Diagnostic Events Enabled check box, located in the Onlinediagnostics function of the DNP LAN IED. When the diagnostic function is activated,the DNP OPC Client Alarm & Event server generates events with information aboutdata changes and commands.

To view the event list:1. Select the DNP LAN Slave OPC Client object in the object tree of the Communica-

tion Engineering Tool (CET).

44


2. Right-click the DNP LAN Slave OPC Client.3. Select Diagnostic AE client (see Figure 4.6-1)

A040350.jpg

Figure 4.6-1 DNP LAN Slave OPC Client Diagnostic AE client

Detailed information about field values (ASDU types, qualifier values etc.) can be foundin the DNP standard documentation.

45


(OPC) 3.2


User's Guide

Technical reference5.


This section provides reference information about the following issues:• IEC 61850 data modeling• Attributes• Status codes.

IEC 61850 data modeling5.2.

General about IEC 61850 data modeling5.2.1.

The relationship between the IEC 61850 data modeling and DNP LAN Slave OPC Clientis described in this section.

For each data class, there is a table giving a detailed description about the relation betweenthe DNP data and IEC 61850 data object attributes and services. The tables also describehow 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/service.• Type specifies the IEC 61850 type of the attribute.• Value/ Value range specifies the allowed values and ranges of the attribute/service.• Mandatory/Optional specifies whether the attribute is considered as mandatory or

optional according to the IEC 61850 standard.• DNP information element specifies the DNP information element related to the

attribute/service.• OPC data types specify the OPC data type used for the OPC item.

Single point status (SPS)5.2.2.

OPC data typesProtocol informa-tion element

Mandat-ory/Optional

Value/Value rangeTypeName

VT_BOOLstate (1=ON,0=OFF)

MTRUE | FALSEBOOLEANstVal

VT_I4DNP statusMQualityq

VT_DATE<none> | Time ofoccurence

MTimeStampt

46


Double point status (DPS)5.2.3.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_I4state (0=OFF,1=ON)

MIntermediate-state(0)

off (1)

on (2)

bad-state (3)

ENUMERATEDstVal



MTimeStampt

Integer status (INS)5.2.4.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_I4Current valueMINTEGERstVal



MTimeStampt

Protection activation information (ACT)5.2.5.

ACT phases information is mapped in the same way as SPS stVal.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_BOOLstate (0=OFF,1=ON)

MBOOLEANgeneral


OBOOLEANphsA


OBOOLEANphsB


OBOOLEANphsC


OBOOLEANneut

DNP statusMQualityq

47


(OPC) 3.2


User's Guide


Mandat-ory/Optional

Value/ Valuerange

TypeName

<none> | Time ofoccurence

MTimeStampt

Directional protection activation information (ACD)5.2.6.

The ACT related directional protection activation information is processed like ACT.


Mandat-ory/Optional

Value/ Valuerange

TypeName


MBOOLEANgeneral


OBOOLEANphsA


OBOOLEANphsB


OBOOLEANphsC


OBOOLEANneut

DNP statusMQualityq

<none> | Time ofoccurence

MTimeStampt

Binary counter reading (BCR)5.2.7.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_I4Value | Frozenvalue | Currentvalue

MINTEGERactVal



MTimeStampt

48


Measured value (MV)5.2.8.

OPC data typesProtection inform-ation element

Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_R4CurrentValueMAnalogueValuemag



MTimeStampt

Complex measured value (CMV)5.2.9.

CMV is configured in the same way as MV. The only difference is that, instead of a magtag, there is a cVal node containing a mag tag in the OPC namespace structure.

OPC data typeProtocol informa-tion element

Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_R4CurrentValueMAnalogueValuecVal.mag


VT_DATE<none> | Time ofoccurrence

MTimeStampt

WYE5.2.10.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_R4

VT_I4

VT_DATE

Phase A CurrentValue

DNP status

<none> | Time ofoccurrence

M

M

M

AnalogueValue

Quality

TimeStamp

phsA.cVal.mag

phsA.q

phsA.t

VT_R4

VT_I4

VT_DATE

Phase B CurrentValue

DNP status

<client provided ifnone>

O

O

O

AnalogueValue

Quality

TimeStamp

phsB.cVal.mag

phsB.q

phsB.t

49


(OPC) 3.2


User's Guide


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_R4

VT_I4

VT_DATE

Phase C CurrentValue

DNP status


O

O

O

AnalogueValue

Quality

TimeStamp

phsC.cVal.mag

phsC.q

phsC.t

VT_R4

VT_I4

VT_DATE

Neutral CurrentValue

DNP status


O

O

O

AnalogueValue

Quality

TimeStamp

neut.cVal.mag

neut.q

neut.t

Delta (DEL)5.2.11.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_R4

VT_I4

VT_DATE

Phase AB CurrentValue

DNP status


M

M

M

AnalogueValue

Quality

TimeStamp

phsAB. cVal.mag t

phsAB.q

phsAB.t

VT_R4

VT_I4

VT_DATE

Phase BC CurrentValue

DNP status


M

M

M

AnalogueValue

Quality

TimeStamp

phsBC.cVal.mag q

phsBC.q

phsBC.t

VT_R4

VT_I4

VT_DATE

Phase CA CurrentValue

DNP status


M

M

M

AnalogueValue

Quality

TimeStamp

phsCA.cVal.mag q

phsCA.q

phsCA.t

Controllable single point (SPC)5.2.12.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_BOOLControl CodeMSPIctlVal

50



Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_BOOLState (0=OFF,1=ON)

MFALSE | TRUEstVal



MTimeStampt

Controllable double point (DPC)5.2.13.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_BOOLControl CodeOFALSE | TRUESPIctlOperOn

VT_BOOLControl CodeOFALSE | TRUEctlOperOff

VT_BOOLControl CodeOFALSE | TRUEctlSelOn

VT_BOOLControl CodeOFALSE | TRUEctlSelOff

VT_I4State (0=OFF,1=ON)

Mintermediate-state(0)

off (1)

on (2)

bad-state (3)

ENUMERATEDstVal



MTimeStampt

VT_BOOL-OFALSE | TRUEBOOLEANctlCan

VT_BOOLState (0=OFF,1=ON)

OFALSE | TRUEBOOLEANstSeld

Controllable integer status (INC)5.2.14.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_I4Control ValueMINTEGERctlVal

VT_I4Current ValueMINTEGERstVal



MTimeStampt

51


(OPC) 3.2


User's Guide

Binary controlled step position information (BSC)5.2.15.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_I1Control ValueMstop (0)

lower (1)

higher (2)

reserved (3)

ENUMERATEDctlVal

VT_I4StateMValWithTransvalWTr



MTimeStampt

Integer controlled step position information (ISC)5.2.16.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_I1Control ValueM-64 ... 63INTEGERctlVal

VT_I4StateMValWithTransvalWTr

V_I4DNP statusMQualityq

V_DATE<none> | Time ofoccurrence

MTimeStampt

Analogue set point (APC)5.2.17.


Mandat-ory/Optional

Value/ Valuerange

TypeName

VT_R4Control ValueMAnalogueValuespMag

Status codes5.3.

Introduction5.3.1.

The following status codes are defined for the DNP slave protocol. Some typical reasonsfor some of the status codes are also given.

52


Link layer status codes5.3.2.

The Data Flow Control ( DFC) bit of the messages from the master is set formore than 15 seconds.

17650

The DCD or CTS signal or the end of the transmitted message is not receivedin correct time.

17651

Timeout while waiting for an acknowledgement to a request.17652

The application level sends a command before the communication betweenthe master and the slave is established.

17654

The Data Flow Control bit of the messages from the master is set for too long.17655

The slave does not receive a reply from the master.17656

The channel has been set in use.17657

The channel has been set out of use.17658

The protocol stack out of buffers error.17659

The value written to one of the channel properties is incorrect.17670

Application layer status codes5.3.3.

The value set to a property of the device is incorrect.13901

No more events can be written to one of the unsolicited message queuessince the queue is full.

13904

Internal message buffer full error.13905

Internal message filling error.13906

The used data object type is not supported.13907

Internal data overflow error.13909

The device is in the suspended state. The reason for this can be that the linkis not properly established (for example incorrect cable wiring) or the masterstation does not respond.

13910

Internal message sending error.13911

A command is sent to a channel with a non-established communication.13913

Internal out of buffers error.13914

The device has been set out of use.13918

The device has been set in use.13919

Internal buffer error.13924

There is not any preceding command with the address given when confirminga command. Either the address is incorrect or the command has not beenreceived.

13925

Internal software error.13926

The channel to which the device is created is incorrect.13927

The CODE item of a received control block message is unknown.13931

53


(OPC) 3.2


User's Guide

Attributes5.4.

General about attributes5.4.1.

In addition to item tags for process data (indications and commands), the OPC serversand clients also provide some item tags for controlling the devices and retrieving statusinformation from them.These item tags are called attributes.

There are three categories of attributes: DNP LAN Slave OPC Client attributes, DNPLAN Channel attributes and DNP LAN IED attributes. These attributes are describedin the subsections below.

The attributes are not updated automatically by the server according to the update rateof the OPC group. Instead, it is required that the client explicitly refreshes the group orrequests a read of single attributes to retrieve the latest values. This does not matter formost attributes, since they do not change value spontaneously. The exceptions are thediagnostic counters and object status attributes. Object status attributes are updatedautomatically by system messages, so in practice only diagnostic counters are affectedby this rule. It was introduced to avoid overloading the communication link between theprotocol stack and OPC server.

DNP LAN Slave OPC Client attributes5.4.2.

Table 5.4.2-1 DNP LAN Slave OPC Client attributesDescriptionValue or Value range/ DefaultProperty / Para-

meter

Data type: Text

Access: Read-only

The version information of the ProtocolStack.

Value: Version informationProtocol Stack Ver-sion

54


DNP LAN Channel attributes5.4.3.

Table 5.4.3-1 DNP LAN Channel attributesDescriptionValue or Value range/ DefaultProperty / Para-

meter

Data type: Integer

Access: No limitations

The state of the channel - whether it is inuse or not. When a channel is not in use,no data can be transmitted on it, and nodata is received from it. The channelattributes can be read as usual. Generally,a channel must be taken out of use bysetting this attribute to 0 before the chan-nel attributes can be written.

When a channel is stopped by setting theIn use attribute to 0, all data transmissionon the channel ceases. However, beforethat, the protocol stack executes to theend all on-going data transactions. Forexample, the polling of the station in turnis completed.

0 = Not in use, the channelcommunication is stopped

1 = In use

Default: 0

In Use

Diagnostic Coun-ters (TCP/IP,UDP/IP channel)

Data type: Integer


Default: TCP/IP

The number of transmitted telegrams.Transmitted Tele-grams

The number of failed transmissions.Failed Transmis-sions

The number of transmitted commands.Transmitted Com-mands

The number of transmitted replies.Transmitted Replies

The number of received data messages.Received Messages

The number of times there has been abuffer overflow.

Buffer OverflowErrors

Incremented each time a TCP connectrequest is received.

TCP Connect

Incremented each time a TCP connectrequest is accepted.

TCP Accept

Incremented each time a TCP connectionis closed.

TCP Close

55


(OPC) 3.2


User's Guide

DNP LAN IED attributes5.4.4.

Table 5.4.4-1 DNP LAN IED attributesDescriptionValue or Value range/ DefaultProperty / Para-

meter

Data type: Integer


The operational status of the device - inuse or out of use. Taking the device outof use with this attribute stops all datacommunication with the device. All opera-tions that would result in a data exchangeare disabled. The device itself is notaffected by the attribute, only the protocolstack’s image of the device. Setting In useto 1 is allowed only if the device addressis legal.

0 = Out of use

1 = In use

Default: 0

In Use

Data type: Integer


Indicates the detailed information aboutthe station device status. Writing to theObject Status attribute (Object Status = 1)of a device makes the protocol stack tore-transmit the latest system messagecaused by the device. Possible "Stopped"and "Suspended" messages cause oldmarking of OPC items. By reading theObject Status attribute, the status code ofthe system message can be read.

When written:

1 = Re-transmit system mes-sage

When read:

A status code, e.g.

0 = OK (communication worksproperly)

13910 = Device suspended

For more information, see5.3.2, Link layer status codesand 5.3.3, Application layerstatus codes.

Object Status

Data type: Boolean

Access: Read-only

Indicates the status of the device connec-tion.

(Does not exist in Configuring Micro-SCADA for DNP slave.)

True = Device connection OK

False = Device connectionsuspended

Device ConnectionStatus

Diagnostic Coun-ters

Data type: Integer


Indicates the number of times the connec-tion has been suspended.

Suspension Counter

56


DescriptionValue or Value range/ DefaultProperty / Para-meter

The number of transmitted data messages.Transmitted DataMessages

The number of transmitted commandmessages.

Transmitted Com-mand Messages

The number of transmitted confirmationmessages.

Transmitted Confirm-ation Messages

The number of received data messages.Received DataMessages

The number of received command mes-sages.

Received CommandMessages

The number of received confirmationmessages.

Received Confirma-tion Messages

The number of unknown messagesreceived.

Received UnknownMessages

Queue Diagnostics

Data type: Integer


Size of APDU in-queue

Size of APDU out-queue

Size of TSDU in-queue

Size of TSDU out-queue

Size of WAIT CON-FIRM queue

Size of OPC Clienttransition queue

Size of Confirmationtransition queue

Size of Select trans-ition queue

Size of Free APDUqueue

Size of Free eventsqueue

Size of Free OPCClient transitionsqueue

57


(OPC) 3.2


User's Guide

Appendix 1

Device profile

Table A1-1 Device profile describing the implementation of DNP V3.00 slave pro-tocol in COM610/615 SUBSET 2: the default subset

DNP V3.00DEVICE PROFILE DOCUMENT

Vendor Name: ABB Oy Substation Automation Products

Device Name: COM610/615

Highest DNP Level Supported:

Device Function:

[ ] Master [x] Slave

For Requests: Subset Level 2

For Responses: Subset Level 2

Notable objects, functions, and/or qualifiers supported inaddition to the Highest DNP Levels Supported

(the complete list is described in the attached table):

Additions to level 2 are shaded in the accompanying imple-mentation tables.

Maximum Application Fragment Size (octets):Maximum Data Link Frame Size (octets):

Transmitted: 255...2048Transmitted: 58...292

Received : 2048Received: (must be 292)

Maximum Application Layer Re-tries:Maximum Data Link Re-tries:

[ ] None[ ] None

[ ] Fixed at _______________________

[x] Configurable, range 0 to 5[x] Configurable, range 0 to 10

Requires Data Link Layer Confirmation:

[ ] Never

[ ] Always

[ ] Sometimes If 'Sometimes', when? ______________________________________________

[x] Configurable

Requires Application Layer Confirmation:

[ ] Never

[ ] Always (not recommended)

[ ] When reporting Event Data (Slave devices only)

[ ] When sending multi-fragment responses (Slave devices only)

[ ] Sometimes. If 'Sometimes', when? ______________________________________________

58



[x] Configurable

Timeouts while waiting for:

Data Link Confirm

[x] Configurable[ ] Variable[ ] Fixed at _________[ ] None

Complete Appl. Fragment


Application Confirm


Complete Appl. Response


Others:

Retransmission after a collision

Complete data link frame

Sends/Executes ControlOperations:

WRITE Binary Outputs

[ ] Configurable[ ] Sometimes[ ] Always[x] Never


SELECT/OPERATE

[ ] Configurable[ ] Sometimes[x] Always[ ] Never

DIRECT OPERATE


DIRECT OPERATE - NO ACK


Count > 1


Pulse On


Pulse Off


Latch On


59


(OPC) 3.2


User's Guide

Sends/Executes ControlOperations:

Latch Off


Queue


Clean Queue


FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICESONLY:

Reports time-tagged Binary Input Change Events whenno specific variation requested:

Reports Binary Input Change Events when no specificvariation requested:

[ ] Never[ ] Never

[ ] Binary Input Change With Time[ ] Only time-tagged

[ ] Binary Input Change With Relative Time[ ] Only non-time-tagged

[x] Configurable, depends on data point initialization[x] Configurable to send one or the other, depends on datapoint init

Sends Static Data in Unsolicited Responses:Sends Unsolicited Responses:

[X] Never[ ] Never

[ ] When Device Restarts (depends on data point initialization)[x] Configurable, depends on data point initialization

[ ] When Status Flags Change (depends on data point initializ-ation)

[ ] Only certain objects

No other options are permitted[ ] Sometimes (attach explanation)

[ ] ENABLE/DISABLE UNSOLICITED function codes supported

Counters Roll Over at:Default Counter Object/ Variation:

[ ] No Counters Reported[ ] No Counters Reported

[ ] Configurable (attach explanation)[x] Configurable, depends on data point initialization

[ ] 16 bit[ ] Default Object________________________

[x] 32 Bits, roll-over bits not set[ ] Default Variation______________________

[ ] Other Value__________________________________[ ] Point-by-point list attached

[ ] Point-by-point list attached

Sends Multi-Fragment Responses:

[x] Yes

[ ] No

Supported function codes

60


Table A1-2 Supported function codesSupportedDESCRIPTIONFUNCTIONCODE

Transfer Function Codes

YesMessage fragment confirmation

No response

Confirm0

YesRequest objects from outstation

Respond with requested objects

Read1

YesStore the specified objects to out-station.

Respond with status of operation

Write2

Control Function Codes

YesSelect the output point of outstation

Respond with status of controlpoint

Select3

YesSet the output that has previouslybeen selected


Operate4

YesSet the output directly


Direct operate5


No respond

Direct operate

- no ack

6

Freeze Function Codes

YesCopy the specified objects tofreeze buffer


ImmediateFreeze

7


No respond

ImmediateFreeze

-no ack

8

YesCopy the specified objects tofreeze buffer and clear objects


Freeze andClear

9


No respond

Freeze andClear

-no ack

10

61


(OPC) 3.2


User's Guide

SupportedDESCRIPTIONFUNCTIONCODE

NoCopy the specified objects tofreeze buffer at specified time


Freeze with time11


No respond

Freeze with time

-no ack

12

Application Control FunctionCodes

YesPerform desired reset sequence

Respond with a time object

Cold Restart13

YesPerform desired partial reset oper-ation


Warm Restart14

NoInitialize the specified data todefault


Initialize Data toDefaults

15

NoPrepare the specified applicationto run


Initialize Applica-tion

16

NoStart the specified application torun


Start Application17

NoStop the specified application torun


Stop Application18

Configuration Function Codes

NoSave the configuration


Save configura-tion

19

NoEnable Unsolicited Messages


Enable Unsoli-cited Messages

20

NoDisable Unsolicited Messages


Disable Unsoli-cited Messages

21

NoAssign specified objects to a class


Assign Class22

Time Synchronization FunctionCodes

62



YesPerform propagation delay meas-urement

Delay Measure-ment

23

YesUsed in a network application toallow the Master station and theOutstation to record their time atthe same instant

Record currenttime

24

Response Function Codes

YesMessage fragment confirmationConfirm0

YesResponse to requested messageResponse129

YesSpontaneous message withoutrequest

Unsolicited Mes-sage

130

Supported objects

Table A1-3 Supported objectsQual Codes(hex)

RESPONSE(master mustparse)

Func Codes

QualCodes(hex)

REQUEST(slave mustparse)

Func Codes(dec)

DescriptionVarOBJECT

Obj

061Binary Input - AllVariations

01

00, 01129, 13000,01,061Binary Input11

00, 01129, 13000,01,061Binary Input withStatus

21

06,07,081Binary InputChange - AllVariations

02

17, 28129, 13006,07,081Binary InputChange withoutTime

12

17, 28129, 13006,07,081Binary InputChange withTime

22

17, 28129, 13006,07,081Binary InputChange withRelative Time

32

061Binary Output -All Variations

010

Binary Output110

00, 01129, 13000,01,061Binary OutputStatus

210

63


(OPC) 3.2


User's Guide

Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

Control Block -All Variations

012

echo of request+ status

12917, 27,283, 4, 5, 6Control RelayOutput Block

112

Pattern ControlBlock

212

Pattern Mask312

061, 7, 8, 9, 10Binary Counter -All Variations

020

00, 01129, 13000,01,06132-Bit BinaryCounter

120

00, 01129, 13016-Bit BinaryCounter

220

00, 01129, 13032-Bit DeltaCounter

320

00, 01129, 13016-Bit BinaryCounter

420

00, 01129, 13000,01,06132-Bit BinaryCounter withoutFlag

520

00, 01129, 13016-Bit BinaryCounter withoutFlag

620

00, 01129, 13032-Bit DeltaCounter withoutFlag

720

00, 01129, 13016-Bit DeltaCounter withoutFlag

820

061Frozen Counter- All Variations

021

00, 01129, 13032-Bit FrozenCounter

121

00, 01129, 13016-Bit FrozenCounter

221

32-Bit FrozenDelta Counter

321

16-Bit FrozenDelta Counter

421

64


Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

32-Bit FrozenCounter withTime of Freeze

521


621

32-Bit FrozenDelta Counterwith Time ofFreeze

721


821

00, 01129, 13032-Bit FrozenCounter withoutFlag

921

00, 01129, 13016-Bit FrozenCounter withoutFlag

1021

32-Bit FrozenDelta Counterwithout Flag

1121


1221

06,07,081Counter ChangeEvent - All Vari-ations

022

17, 28129, 13032-Bit CounterChange Eventwithout Time

122

17, 28129, 13016-Bit CounterChange Eventwithout Time

222

32-Bit DeltaCounter ChangeEvent withoutTime

322

65


(OPC) 3.2


User's Guide

Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

16-Bit DeltaCounter ChangeEvent withoutTime

422

32-Bit CounterChange Eventwith Time

522


622

32-Bit DeltaCounter ChangeEvent with Time

722


822

Frozen CounterEvent - All Vari-ations

023

32-Bit FrozenCounter Eventwithout Time

123

16-Bit FrozenCounter Eventwithout Time

223

32-Bit FrozenDelta CounterEvent withoutTime

323

16-Bit FrozenDelta CounterEvent withoutTime

423

32-Bit FrozenCounter Eventwith Time

523


623

32-Bit FrozenDelta CounterEvent with Time

723

66


Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj


823

061Analog Input -All Variations

030

00, 01129, 13032-Bit AnalogInput

130

00, 01129, 13000,01,06116-Bit AnalogInput

230

00, 01129, 13032-Bit AnalogInput withoutFlag

330

00, 01129, 13000,01,06116-Bit AnalogInput withoutFlag

430

Frozen AnalogInput - All Vari-ations

031

32-Bit FrozenAnalog Input

131


231

32-Bit FrozenAnalog Inputwith Time ofFreeze

331


431

32-Bit FrozenAnalog Inputwithout Flag

531


631

06,07,081Analog ChangeEvent - All Vari-ations

032

67


(OPC) 3.2


User's Guide

Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

17,28129,13032-Bit AnalogChange Eventwithout Time

132

17,28129,13016-Bit AnalogChange Eventwithout Time

232

32-Bit AnalogChange Eventwith Time

332


432

Frozen AnalogEvent - All Vari-ations

033

32-Bit FrozenAnalog Eventwithout Time

133


233

32-Bit FrozenAnalog Eventwith Time

333


433

061Analog OutputStatus - All Vari-ations

040

32-Bit AnalogOutput Status

140

00, 01129, 13016-Bit AnalogOutput Status

240

Analog OutputBlock - All Vari-ations

041

32-Bit AnalogOutput Block

141

echo of request+ status

12917, 283, 4, 5, 616-Bit AnalogOutput Block

241

68


Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

Time and Date -All Variations

050

06

07

quantity = 1

2Time and Date150

Time and Datewith Interval

250

Time and DateCTO - All Vari-ations

051

07, quantity=1129, 130Time and DateCTO

151

07, quantity=1129, 130UnsynchronizedTime and DateCTO

251

Time Delay - AllVariations

052

07, quantity=1129Time DelayCoarse

152

07, quantity=1129Time Delay Fine252

060

061Class 0 Data160

06,07,081Class 1 Data260

06,07,081Class 2 Data360

06,07,081Class 3 Data460

File Identifier170

All

00,index=7

1

2

Internal Indica-tions

180

Storage Object181

Device Profile182

Private Registra-tion Object

183

Private Registra-tion ObjectDescriptor

283

69


(OPC) 3.2


User's Guide

Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

Application Iden-tifier

190

Short FloatingPoint

1100

Long FloatingPoint

2100

Extended Float-ing Point

3100

Small PackedBinary-CodedDecimal

1101

Medium PackedBinary-CodedDecimal

2101

Large PackedBinary-CodedDecimal

3101

13No Object

23No Object

Table A1-4 Device profile describing the implementation of DNP V3 slave protocolin COM610/615 SUBSET 3: the used subset is selected using the IED's subsetproperty


Vendor Name: ABB Oy Substation Automation Products

Device Name: COM610/615

Device Function:Highest DNP Level Supported:

[ ] Master [x] SlaveFor Requests: Subset Level 3

For Responses: Subset Level 3

Notable objects, functions, and/or qualifiers supported inaddition to the Highest DNP Levels Supported

(the complete list is described in the attached table):

Additions to level 3 are shaded in the accompanying imple-mentation tables. Default subset is 2, but if the master makesa subset request, the used subset level is automatically raised.

Maximum Application Fragment Size (octets):Maximum Data Link Frame Size (octets):

Transmitted: 255...2048Transmitted: 58...292

70



Received : 2048Received: (must be 292)

Maximum Application Layer Re-tries:Maximum Data Link Re-tries:

[ ] None[ ] None

[ ] Fixed at _______________________

[x] Configurable, range 0 to 5[x] Configurable, range 0 to 10


[ ] Never

[ ] Always

[ ] Sometimes If 'Sometimes', when? ______________________________________________

[x] Configurable

Requires Application Layer Confirmation:

[ ] Never

[ ] Always (not recommended)

[ ] When reporting Event Data (Slave devices only)

[ ] When sending multi-fragment responses (Slave devices only)

[ ] Sometimes. If 'Sometimes', when? ______________________________________________

[x] Configurable


Data Link Confirm

[x] Configurable[ ] Fixed at _________

[ ] Variable

[ ] None

Complete Appl. Fragment


[ ] Variable

[ ] None

Application Confirm


[ ] Variable

[ ] None

Complete Appl. Response


[ ] Variable

[ ] None

Others:

Retransmission after a collision

71


(OPC) 3.2


User's Guide


Complete data link frame

Sends/Executes Control Operations:

WRITE Binary Outputs

[ ] Configurable[ ] Always

[ ] Sometimes

[x] Never

SELECT/OPERATE

[ ] Configurable[x] Always

[ ] Sometimes

[ ] Never

DIRECT OPERATE


[ ] Sometimes

[ ] Never

DIRECT OPERATE - NO ACK


[ ] Sometimes

[ ] Never

Count > 1


[ ] Sometimes

[x] Never

Pulse On


[ ] Sometimes

[ ] Never

Pulse Off


[ ] Sometimes

[ ] Never

Latch On


[ ] Sometimes

[ ] Never

Latch Off


[ ] Sometimes

[ ] Never

Queue


[ ] Sometimes

[x] Never

72



Clear Queue


[ ] Sometimes

[x] Never

FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICESONLY:

Reports time-tagged Binary Input Change Events whenno specific variation requested:

Reports Binary Input Change Events when no specificvariation requested:

[ ] Never[ ] Never

[ ] Binary Input Change With Time[ ] Only time-tagged

[ ] Binary Input Change With Relative Time[ ] Only non-time-tagged

[x] Configurable, depends on data point initialization.[x] Configurable to send one or the other, depends on datapoint initialization.

Sends Static Data in Unsolicited Responses:Sends Unsolicited Responses:

[x] Never[ ] Never

[ ] When Device Restarts (depends on data point initialization)[x] Configurable, depends on data point initialization

[ ] When Status Flags Change (depends on data point initializ-ation)

[ ] Only certain objects

No other options are permitted[ ] Sometimes (attach explanation)

[x] ENABLE/DISABLE UNSOLICITED function codes suppor-ted

Counters Roll Over at:Default Counter Object/ Variation:

[ ] No Counters Reported[ ] No Counters Reported

[ ] Configurable (attach explanation)[x] Configurable, depends on data point initialization

[ ] 16 bit[ ] Default Object________________________

[x] 32 Bits, roll-over bits not set[ ] Default Variation______________________

[ ] Other Value__________________________________[ ] Point-by-point list attached

[ ] Point-by-point list attached

Sends Multi-Fragment Responses:

[x] Yes

[ ] No

Table A1-5 Supported function codesSupportedDESCRIPTIONFUNCTIONCODE

Transfer Function Codes

73


(OPC) 3.2


User's Guide


YesMessage fragment confirmation

No response

Confirm0

YesRequest objects from outstation

Respond with requested objects

Read1

YesStore the specified objects to out-station.


Write2

Control Function Codes

YesSelect the output point of outstation


Select3

YesSet the output that has previouslybeen selected


Operate4



Direct operate5


No respond

Direct operate

- no ack

6

Freeze Function Codes



ImmediateFreeze

7


No respond

ImmediateFreeze

-no ack

8



Freeze andClear

9


No respond

Freeze andClear

-no ack

10



Freeze with time11

74




No respond

Freeze with time

-no ack

12

Application Control FunctionCodes

YesPerform desired reset sequence


Cold Restart13

YesPerform desired partial reset oper-ation


Warm Restart14

NoInitialize the specified data todefault


Initialize Data toDefaults

15

NoPrepare the specified applicationto run


Initialize Applica-tion

16

NoStart the specified application torun


Start Application17

NoStop the specified application torun


Stop Application18

Configuration Function Codes

NoSave the configuration


Save configura-tion

19

YesEnable Unsolicited Messages


Enable Unsoli-cited Messages

20

YesDisable Unsolicited Messages


Disable Unsoli-cited Messages

21

YesAssign specified objects to a class


Assign Class22

Time Synchronization FunctionCodes

YesPerform propagation delay meas-urement

Delay Measure-ment

23

75


(OPC) 3.2


User's Guide


YesUsed in a network application toallow the Master station and theOutstation to record their time atthe same instant

Record currenttime

24

Response Function Codes

YesMessage fragment confirmationConfirm0

YesResponse to requested messageResponse129

YesSpontaneous message withoutrequest

Unsolicited Mes-sage

130

Supported objects

Table A1-6 Supported objectsQual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

00,01,061,22Binary Input - AllVariations

01

00, 01129, 13000,01,061Binary Input11

00, 01129, 13000,01,061Binary Input withStatus

21

06,07,081Binary InputChange - AllVariations

02

17, 28129, 13006,07,081Binary InputChange withoutTime

12

17, 28129, 13006,07,081Binary InputChange withTime

22

17, 28129, 13006,07,081Binary InputChange withRelative Time

32

00,01,061Binary Output -All Variations

010

Binary Output110

00, 01129, 13000,01,061Binary OutputStatus

210

Control Block -All Variations

012

76


Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

echo of request12917, 27,283, 4, 5, 6Control RelayOutput Block

112

echo of request12917, 285, 6Pattern ControlBlock

212

echo of request12900,015, 6Pattern Mask312

00,01,061, 7, 8, 9, 10, 22Binary Counter -All Variations

020


120


220

00, 01129, 13000,01,06132-Bit DeltaCounter

320


420


520


620

00, 01129, 13000,01,06132-Bit DeltaCounter withoutFlag

720

00, 01129, 13000,01,06116-Bit DeltaCounter withoutFlag

820

00,01,061,22Frozen Counter- All Variations

021

00, 01129, 13000,01,06132-Bit FrozenCounter

121

00, 01129, 13000,01,06116-Bit FrozenCounter

221

00, 01129, 13000,01,06132-Bit FrozenDelta Counter

321

00, 01129, 13000,01,06116-Bit FrozenDelta Counter

421

77


(OPC) 3.2


User's Guide

Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj


521


621


721


821

00, 01129, 13000,01,06132-Bit FrozenCounter withoutFlag

921

00, 01129, 13000,01,06116-Bit FrozenCounter withoutFlag

1021


1121


1221

06,07,081Counter ChangeEvent - All Vari-ations

022

17, 28129, 13006,07,08132-Bit CounterChange Eventwithout Time

122

17, 28129, 13006,07,08116-Bit CounterChange Eventwithout Time

222

17, 28129, 13006,07,08132-Bit DeltaCounter ChangeEvent withoutTime

322

78


Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

17, 28129, 13006,07,08116-Bit DeltaCounter ChangeEvent withoutTime

422


522


622


722


822

06,07,081Frozen CounterEvent - All Vari-ations

023

17, 28129, 13006,07,08132-Bit FrozenCounter Eventwithout Time

123

17, 28129, 13006,07,08116-Bit FrozenCounter Eventwithout Time

223

17, 28129, 13006,07,08132-Bit FrozenDelta CounterEvent withoutTime

323

17, 28129, 13006,07,08116-Bit FrozenDelta CounterEvent withoutTime

423


523


623


723

79


(OPC) 3.2


User's Guide

Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj


823

00,01,061,22Analog Input -All Variations

030

00, 01129, 13000,01,06132-Bit AnalogInput

130

00, 01129, 13000,01,06116-Bit AnalogInput

230


330


430

Frozen AnalogInput - All Vari-ations

031


131


231


331


431


531


631

06,07,081Analog ChangeEvent - All Vari-ations

032

80


Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

17, 28129,13006,07,08132-Bit AnalogChange Eventwithout Time

132

17, 28129,13006,07,08116-Bit AnalogChange Eventwithout Time

232


332


432

Frozen AnalogEvent - All Vari-ations

033


133


233


333


433

00,01,061Analog OutputStatus - All Vari-ations

040

00, 01129, 13000,01,06132-Bit AnalogOutput Status

140

00, 01129, 13000,01,06116-Bit AnalogOutput Status

240

00, 0112917, 283, 4, 5, 632-Bit AnalogOutput Block

141

echo of request12917, 283, 4, 5, 616-Bit AnalogOutput Block

241

Time and Date -All Variations

050

81


(OPC) 3.2


User's Guide

Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

07 quantity = 112907 quantity = 1

07 quantity = 1

2 (see 4.14)

1

Time and Date150

Time and Datewith Interval

250

Time and DateCTO - All Vari-ations

051

07, quantity=1129, 130Time and DateCTO

151

07, quantity=1129, 130UnsynchronizedTime and DateCTO

251

Time Delay - AllVariations

052

07, quantity=1129Time DelayCoarse

152

07, quantity=1129Time Delay Fine252

060

061Class 0 Data160

06,07,08

06

1

20, 21, 22

Class 1 Data260

06,07,08

6

1

20, 21, 22

Class 2 Data360

06,07,08

06

1

20, 21, 22

Class 3 Data460

File Identifier170

00,01

00 index = 7

1

2

Internal Indica-tions

180

Storage Object181

Device Profile182

Private Registra-tion Object

183

Private Registra-tion ObjectDescriptor

283

82


Qual Codes(hex)


Func Codes

QualCodes(hex)


Func Codes(dec)


Obj

Application Iden-tifier

190

Short FloatingPoint

1100

Long FloatingPoint

2100

Extended Float-ing Point

3100

Small PackedBinary-CodedDecimal

1101

Medium PackedBinary-CodedDecimal

2101

Large PackedBinary-CodedDecimal

3101

13No Object

23No Object

83


(OPC) 3.2


User's Guide

Index

Aactivation information

properties ....................................................................................................... 26adding

channel object ................................................................................................ 17data object ..................................................................................................... 18device object .................................................................................................. 18OPC client ...................................................................................................... 17

analog set pointproperties ....................................................................................................... 27

application layer ................................................................................................. 53attributes

channel .......................................................................................................... 55client .............................................................................................................. 54DNP serial IED ............................................................................................... 56

BBinary controlled step position information (BSC)

IEC 61850 data modeling ................................................................................ 52properties ....................................................................................................... 28

Binary counter reading (BCR)IEC 61850 data modeling ................................................................................ 48properties ....................................................................................................... 27

Cchannel

attributes ........................................................................................................ 55configuring ..................................................................................................... 22diagnostics ..................................................................................................... 42

channel objectadding ........................................................................................................... 17

clientattributes ........................................................................................................ 54

Complex measured value (CMV)IEC 61850 data modeling ................................................................................ 49properties ....................................................................................................... 28

configuringchannel .......................................................................................................... 22data object ..................................................................................................... 24object ............................................................................................................. 20

Controllable double point (DPC)properties ....................................................................................................... 31

Controllable integer status (INC)

85


(OPC) 3.2


User's Guide


Controllable single point (SPC)IEC 61850 data modeling ................................................................................ 50properties ....................................................................................................... 37

Ddata object

adding ........................................................................................................... 18configuring ..................................................................................................... 24

Delta (DEL)IEC 61850 data modeling ............................................................................... 50properties ....................................................................................................... 30

devicediagnostics ..................................................................................................... 43profile ............................................................................................................ 58

device name plateproperties ....................................................................................................... 32

device objectadding ........................................................................................................... 18

diagnosticschannel .......................................................................................................... 42device ............................................................................................................ 43OPC client ...................................................................................................... 41signal ............................................................................................................. 44

Directional protection activation information (ACD)IEC 61850 data modeling ................................................................................ 48properties ....................................................................................................... 25

DNP LAN IEDproperties ....................................................................................................... 23

DNP serial IEDattributes ........................................................................................................ 56

Double point status (DPS)IEC61860 data modeling ................................................................................. 47properties ....................................................................................................... 32

FFilter File

Active Filter .................................................................................................... 19

IIEC 61850 data modeling

Binary counter reading (BCR) .......................................................................... 48Complex measured value (CMV) ..................................................................... 49Controllable integer status (INC) ...................................................................... 51Controllable single point (SPC) ........................................................................ 50Delta (DEL) .................................................................................................... 50

86


Directional protection activation information (ACD) ............................................ 48Double point status (DPS) ............................................................................... 47Integer status (INS) ......................................................................................... 47Measured value (MV) ...................................................................................... 49Protection activation information (ACT) ............................................................ 47Single point status (SPS) ................................................................................ 46WYE .............................................................................................................. 49

Integer controlled step position (ISC)properties ....................................................................................................... 34

Integer status (INS)IEC 61850 data modeling ................................................................................ 47properties ....................................................................................................... 34

Llink layer ............................................................................................................ 53logical node name plate

properties ....................................................................................................... 35

MMeasured value (MV)


Oobject

configuring ..................................................................................................... 20OPC client

adding ........................................................................................................... 17diagnostics ..................................................................................................... 41features ......................................................................................................... 13properties ....................................................................................................... 21

Pproperties

activation information ...................................................................................... 26analog set point .............................................................................................. 27Binary controlled step position (BSC) ............................................................... 28Binary counter reading (BCR) .......................................................................... 27Complex measured value (CMV) ..................................................................... 28Controllable double point (DPC) ...................................................................... 31Controllable integer status (INC) ...................................................................... 33Controllable single point (SPC) ........................................................................ 37Delta (DEL) .................................................................................................... 30device name plate .......................................................................................... 32Directional protection activation information (ACD) ............................................ 25DNP LAN IED ................................................................................................. 23

87


(OPC) 3.2


User's Guide

Double point status (DPS) ............................................................................... 32Integer controlled step position (ISC) ............................................................... 34Integer status (INS) ......................................................................................... 34logical node name plate .................................................................................. 35Measured value (MV) ...................................................................................... 35OPC client ...................................................................................................... 21Single point status (SPS) ................................................................................ 37WYE .............................................................................................................. 38

Protection activation information (ACT)IEC 61850 data modeling ................................................................................ 47

Ssignal

diagnostics ..................................................................................................... 44Single point status (SPS)


status codesapplication layer ............................................................................................. 53link layer ........................................................................................................ 53

supported objects ............................................................................................... 63

WWYE


88


1MR

S755

496

D/1

7.06

.200

8

ABB Inc.ABB Oy655 Century PointDistribution AutomationLake Mary, Florida 32746P.O. Box 699USAFI-65101 VAASA

FINLAND Tel: +1 407 732 2000Tel. +358 10 22 11 Fax: +1 407 732 2335Fax. +358 10 22 1094www.abb.com/substationautomation

COM600 Station Automation Series DNP 3.0 LAN/WAN Slave … · 1.6. Terminology The following is a...

Documents

Transcript of COM600 Station Automation Series DNP 3.0 LAN/WAN Slave … · 1.6. Terminology The following is a...