ABB COM600 series User manual

Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's
Manual

Contents:
1. About this manual .................................................................................. 7
1.1. Copyrights ...................................................................................... 7
1.2. Trademarks .................................................................................... 7
1.3. General .......................................................................................... 7
1.4. Document conventions .................................................................. 8
1.5. Use of symbols .............................................................................. 9
1.6. Terminology .................................................................................. 10
1.7. Abbreviations ............................................................................... 11
1.8. Related documents ...................................................................... 12
1.9. Document revisions ..................................................................... 12
2. Introduction ........................................................................................... 13
2.1. Functional overview ..................................................................... 13
2.2. DNP LAN Slave OPC Client features .......................................... 13
3. Configuration ........................................................................................ 14
3.1. About this section ......................................................................... 14
3.2. Overview of configuration ............................................................ 14
3.3. Building object tree ...................................................................... 16
3.3.1. General about building object tree ................................ 16
3.3.2. Adding DNP LAN Slave OPC Client object .................. 17
3.3.3. Adding Channel objects ................................................ 17
3.3.4. Adding DNP LAN IED object ........................................ 17
3.3.5. Adding data objects using Cross-References
function .......................................................................... 17
3.4. Configuring objects ...................................................................... 18
3.4.1. General about configuring objects ................................ 18
3.4.2. Configuring DNP LAN Slave OPC Client properties ..... 20
3.4.3. Configuring DNP LAN Channel properties .................... 20
3.4.4. Configuring DNP LAN IED properties ........................... 21
3.4.5. Configuring data objects ............................................... 23
3.4.5.1. General about configuring data objects ...... 23
3.4.5.2. Directional protection activation information
(ACD) .......................................................... 24
3.4.5.3. Protection activation information (ACT) ...... 25
3.4.5.4. Analog set point (APC) ............................... 26
3.4.5.5. Binary counter reading (BCR) .................... 26
3.4.5.6. Binary controlled step position information
(BSC) .......................................................... 27
3.4.5.7. Complex measured value (CMV) ............... 27
3.4.5.8. Delta (DEL) ................................................. 28
3.4.5.9. Controllable double point (DPC) ................. 29
3.4.5.10. Device Name Plate (DPL) .......................... 30
3.4.5.11. Double point status (DPS) .......................... 30
3
Station Automation COM600 3.41MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual
Issued: 10.3.2005
Version: F/06.11.2009

3.4.5.12. Controllable integer status (INC) ................ 31
3.4.5.13. Integer status (INS) .................................... 32
3.4.5.14. Integer controlled step position information
(ISC) ........................................................... 32
3.4.5.15. Logical Node Name Plate (LPL) ................. 33
3.4.5.16. Measured value (MV) ................................. 33
3.4.5.17. Controllable single point (SPC) .................. 34
3.4.5.18. Single point status (SPS) ........................... 35
3.4.5.19. WYE ........................................................... 35
4. Operation ............................................................................................... 37
4.1. About this section ......................................................................... 37
4.2. Activating COM600 with new configurations ............................... 37
4.3. DNP LAN Slave OPC Client diagnostics ..................................... 37
4.4. DNP LAN Channel diagnostics ................................................... 38
4.5. DNP LAN IED diagnostics ........................................................... 39
4.6. Signal diagnostics ........................................................................ 40
5. Technical reference .............................................................................. 42
5.1. About this section ......................................................................... 42
5.2. IEC 61850 data modeling ............................................................ 42
5.2.1. General about IEC 61850 data modeling ...................... 42
5.2.2. Single point status (SPS) .............................................. 42
5.2.3. Double point status (DPS) ............................................ 43
5.2.4. Integer status (INS) ....................................................... 43
5.2.5. Protection activation information (ACT) ........................ 43
5.2.6. Directional protection activation information (ACD) ...... 44
5.2.7. Binary counter reading (BCR) ....................................... 44
5.2.8. Measured value (MV) .................................................... 45
5.2.9. Complex measured value (CMV) .................................. 45
5.2.10. WYE .............................................................................. 45
5.2.11. Delta (DEL) ................................................................... 46
5.2.12. Controllable single point (SPC) ..................................... 47
5.2.13. Controllable double point (DPC) ................................... 47
5.2.14. Controllable integer status (INC) ................................... 48
5.2.15. Binary controlled step position information (BSC) ........ 48
5.2.16. Integer controlled step position information (ISC) ......... 48
5.2.17. Analogue set point (APC) ............................................. 49
5.3. Status codes ................................................................................ 49
5.3.1. Introduction ................................................................... 49
5.3.2. Link layer status codes ................................................. 49
5.3.3. Application layer status codes ...................................... 49
5.4. Attributes ...................................................................................... 50
5.4.1. General about attributes .............................................. 50
5.4.2. DNP LAN Slave OPC Client attributes .......................... 51
5.4.3. DNP LAN Channel attributes ........................................ 51
5.4.4. DNP LAN IED attributes ............................................... 52
4
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Appendix 1 ................................................................................................... 55
Device profile .......................................................................................... 55
Index .............................................................................................................. 81
5
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

6

About this manual1.
Copyrights1.1.
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any
errors that may appear in this document.
In no event shallABB Oy be liable for direct, indirect, special, incidental, or consequential
damages of any nature or kind arising from the use of this document, nor shallABB Oy
be liable for incidental or consequential damages arising from use of any software or
hardware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB Oy, and the contents thereof must not be imparted to a third party
nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
©Copyright 2006 ABB. All rights reserved.
Trademarks1.2.
ABB is a registered trademark ofABB Group. All other brand or product names men-
tioned in this document may be trademarks or registered trademarks of their respective
holders.
General1.3.
This manual provides thorough information on the OPC Client for DNP 3.0 LAN/WAN
Slave protocol (later referred to as DNP LAN Slave OPC Client) and the central concepts
related to it.You find instructions on to take it into use. The basic operation procedures
are also discussed.
Information in this user’s manual is intended for application engineers who configure
DNP LAN Slave OPC Client to establish data transfer between the DNP master system
and process devices connected to COM600.
As a prerequisite, you should understand DNP protocol and the basic procedures in
Station Automation Builder 600 (later referred to as SAB600).
This user’s manual is divided into following sections:
7
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Introduction
This section gives an overview of the DNP LAN Slave OPC Client and its features.
Configuration
In this section you find an overview of the configuration tasks and instructions on
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 transferring
or activating Station Automation COM600 (later referred to as COM600) 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 of
status 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 theWindows 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
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Entered value is not valid. The value must be 0 - 30 .
•You can be asked to enter the string MIF349 in a field. The string is shown as follows
in the procedure:
MIF349
•Variables are shown using lowercase letters:
sequence name
Use of symbols1.5.
This publication includes warning, caution, and information icons that point out safety-
related conditions or other important information. It also includes tip icons to point out
useful information to the reader. The corresponding icons should be interpreted as follows.
The electrical warning icon indicates the presence of a hazard
which could result in electrical shock.
The warning icon indicates the presence of a hazard which
could result in personal injury.
The caution icon indicates important information or warning
related to the concept discussed in the text. It may indicate
the presence of a hazard which could result in corruption of
software or damage to equipment or property.
The information icon alerts the reader to relevant facts and
conditions.
The tip icon indicates advice on, for example, how to design
your project or how to use a certain function.
9
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Terminology1.6.
The following is a list of terms associated with COM600 that you should be familiar
with. The list contains terms that are unique toABB or have a usage 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 and
events to OPC clients.
Alarms and Events; AE
An OPC service for providing information about process data to
OPC clients.
Data Access; DA
Part of a logical node object representing specific information,
for example, status, or measurement. From an object-oriented
point of view, a data object is an instance of a class data object.
DOs are normally used as transaction objects; that is, they are
data structures.
Data Object; DO
The data set is the content basis for reporting and logging. The
data set contains references to the data and data attribute val-
ues.
Data Set
A physical device that behaves as its own communication node
in the network, for example, protection relay.
Device
Change of process data or an OPC internal value. Normally, an
event 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 defined
as a logical node. A physical device consists of one or several
LDs.
Logical Device; LD
The smallest part of a function that exchanges data. An LN is
an object 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 for
substation automation; LAG
Series of standards specifications aiming at open connectivity
in industrial automation and the enterprise systems that support
industry.
OPC
Representation of a connection to the data source within the
OPC server. An OPC item is identified by a string <object
path>:<property name>. Associated with each OPC item are
Value, Quality, and Time Stamp.
OPC item
Named data item.Property
The report control block controls the reporting processes for
event data as they occur. The reporting process continues as
long as the communication is available.
Report Control Block
10
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

DescriptionTerm
ABB proprietary communication protocol used in substation
automation.
SPA
Protection and/or Control Product supporting the SPA protocol
version 2.5 or earlier.
SPA device
XML-based description language for configurations of electrical
substation IEDs. Defined in IEC 61850 standard.
Substation Configuration Lan-
guage; SCL
Abbreviations1.7.
The following is a list of abbreviations associated with COM600 that you should be
familiar with. See also 1.6, Terminology.
DescriptionAbbreviation
Alarms and EventsAE
Application Service Data UnitASDU
Buffered Report Control BlockBRCB
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. In
this document, the term is used for devices that do not support the ABB
LON/LAG communication.
LMK
Logical NodeLN
LON SPA GatewayLSG
Network Control CenterNCC
Norwegian User ConventionNUC
Network VariableNV
Object Linking and EmbeddingOLE
OLE for Process ControlOPC
Protection & ControlP&C
11
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

DescriptionAbbreviation
Request To SendRTS
Substation AutomationSA
Station Automation Builder 600SAB600
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 Manual
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.6.2008
Document revised3.3E/13.2.2009
Document revised3.4F/06.11.2009
12
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Introduction2.
Functional overview2.1.
The DNP protocol slave interface of COM600 enables master systems communicating
with DNP protocol to receive data from and deliver commands to P&C devices connected
to the GW. The DNP slave is implemented as an OPC client, which transfers and converts
data between the DNP slave protocol interface and the OPC servers of COM600. See
COM600 User's Manual for more details.
The DNP LAN Slave OPC Client is configured using SAB600. SAB600 can also be
used for diagnosing and controlling the operation of the DNP LAN Slave OPC Client.
COM600 has a web server that can be used for remote diagnostic of the Gateway
including the DNP LAN 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, configure at least one OPC
server to provide access to the process devices. In this user's manual, the term "DNP
LAN IED" is used for a virtual station in COM600 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
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Configuration3.
About this section3.1.
This section guides you in the configuration tasks required before you can start using
the DNP LAN Slave OPC Client. For information on the IEC 61850 data modeling, refer
to COM600 User's Manual.
Start Station Automation Builder 600 (later referred to as SAB600) to open a project
where at 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 Create.
5. 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 SAB600 to define the Communication 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 SAB600 including an object tree in the commu-
nication structure on the left and Object Properties window displaying the object properties
on the right.
When configuring OPC servers the following characters cannot
be used in object names: \ ` ' ' #
14
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

DNP_Slave_LANWAN_configuration_overview.bmp
Figure 3.2-1 Example view of SAB600
The configuration work can basically be divided into two separate tasks:
1. building an object tree, and
2. 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 using Cross-
References function.
Figure 3.2-1 shows an example of how the object tree may look like after it has been
built. In the example tree you can see the DNP LAN Slave OPC Client object and its
child objects like channels, devices, and data objects. Indentation is used to indicate the
parent-child relationship between the objects.
After you have added the necessary objects to the object tree in the communication
structure, 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).
15
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Table 3.2-1 DNP LAN Slave OPC Client related objects
DescriptionObject
An object representing the DNP LAN Slave OPC Client.DNP LAN Slave OPC Client
An object representing the channelDNP LAN Channel
A DNP LAN IED is used for a virtual station in COM600
representing the slave stations visible to the DNP master
system.
DNP LAN IED
A data object is an instance of one of the IEC Common
data classes, for example single point status, measured
value etc. Depending on the class, each data object has
a set of attributes for monitoring and controlling the object,
for instance value, quality and control. Data objects are
connected from OPC servers to the DNP LAN Slave OPC
Client with the cross reference function. They are shown
as child objects of the DNP LAN IED object in the object
tree.
Data Object (DO)
Event definitions are used for the diagnostic OPC A&E
Server.
Event Definitions
Building object tree3.3.
General about building object tree3.3.1.
The object tree is built in the Communication structure of SAB600, see Figure 3.2-1. It
is built by adding objects in a logical order starting from the DNP LAN Slave OPC Client
object.
Before the DNP LAN Slave OPC Client can be taken into use, configure an OPC server
for the process communication. For more information on creating an OPC server, refer
to COM600 User's Manual.
You have several possible ways to add objects to the object tree in the Communication
structure:
•You can right-click the object to which you want to add a child object.
•You can copy the object.
Add the objects in the following order:
1. DNP LAN Slave OPC Client
2. DNP LAN Channel
3. DNP LAN IED
4. Data objects
16
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Adding DNP LAN Slave OPC Client object3.3.2.
To add the OPC client object:
1. Add the DNP LAN Slave OPC Client object in the Communication structure by
selecting the Gateway object.
2. Right-click the Gateway object and select New > DNP > DNP LAN Slave OPC
Client.
Adding Channel objects3.3.3.
After the DNP LAN Slave OPC Client object has been successfully added, you can
continue 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. The names of the DNP LAN Channel objects within a DNP
LAN Slave OPC Client have to be unique.
Adding DNP LAN IED object3.3.4.
After a channel object has been successfully added, you can continue building the
structure by adding the DNP LAN Channel object.All the data can be connected to one
device 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 the
feature.
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. The names within DNP LAN Channel have to be unique.
Adding data objects using Cross-References function3.3.5.
Data objects are added somewhat differently than the upper level objects. Basically, you
drag and drop the data objects you need from an OPC server to the DNP LAN Slave
OPC Client.
To add data objects:
1. Select DNP LAN IED object and right-click it.
2. Select Cross-References. The Cross References function 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.
17
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Note that you can also select an upper level (server, channel, etc.) object and drag
and drop it into the Cross-References function.As a result, all the data objects within
the selected object appear now in the Cross-References function and can be connected
to the DNP LAN Slave OPC Client.
4. Drag and drop the logical node into the Cross-References function. The data objects
within the logical node appear now in the Cross-References function.
Note that only data objects that have been given a non zero information address in
the Cross-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 objects
to the DNP LAN IED).
DNP_LAN_Slave_Cross_References.bmp
Figure 3.3.5-1 The Cross References window
For more detailed information about the Cross-References function, see Cross-References
function in COM600 User's Manual.
Configuring objects3.4.
General about configuring objects3.4.1.
After the objects have been added, configure the object properties. Figure 3.4.1-1 shows
an example of how to use SAB600 to configure the object properties for DNP LAN
Slave OPC Client.
18
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

To configure an object:
1. Select an object in the object tree of the communication structure.
a. The object properties appear now in the Object Properties window. The proper-
ties 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
2. 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.
The available properties for different objects are listed in the following subsections.
19
Station Automation COM600 3.4
1MRS755496
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Configuring DNP LAN Slave OPC Client properties3.4.2.
Table 3.4.2-1 lists the configurable DNP LAN Slave OPC Client properties and value
ranges for them. The actual configuration by using SAB600 is performed as described
in 3.2, Overview of configuration.
Table 3.4.2-1 DNP LAN Slave OPC Client properties
DescriptionValue or Value range/ DefaultProperty / Para-
meter
Basic
Specifies the maximum time in seconds
that any connected (configured) OPC
Server requires to retrieve all its initial
data.
0...65535
Default: 5
Maximum OPC
Server Initialization
Time
Instance identification of diagnostic OPC
alarm and event server.
Prog ID AE
Instance identification of diagnostic OPC
data access server.
ProgID DA
The value of this property in minutes is
added to the synchronization time received
from a DNP master.
-720...720
Default: 0
Time Zone Correc-
tion
Station/Remote
Switch
Specifies if a position check for the station
remote switch is going to be made.
Do not check Station/Remote
switch position.
Check Station/Remote switch
position.
Default: Do not check Sta-
tion/Remote switch position.
Station/Remote
Switch Handling
Defines command handling if the position
is bad or unknown.
Reject commands if position
bad or unknown.
Allow commands if position bad
or unknown.
Default: Reject commands if
position bad or unknown
Station/Remote
Switch Error
Configuring DNP LAN Channel properties3.4.3.
The DNP LAN channel properties that can be configured and value ranges for them can
be found in Table 3.4.3-1. The actual configuration by using the SAB600 is performed
as described in 3.4.1, General about configuring objects.
20
1MRS755496
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual