ABB Relion 615 series User manual

Communication Protocol Manual
DNP 3.0
615 series

Document ID: 1MRS756709
Issued: 04.03.2009
Revision: A
Product version: 2.0
© Copyright 2009 ABB. All rights reserved

Copyright
This document and parts thereof must not be reproduced or copied without written
permission from ABB, 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.
Trademarks
ABB is a registered trademark of ABB Group. All other brand or product names
mentioned in this document may be trademarks or registered trademarks of their
respective holders.
Guarantee
Please inquire about the terms of guarantee from your nearest ABB representative.
ABB Oy
Distribution Automation
P.O. Box 699
FI-65101 Vaasa, Finland
Telephone: [phone]
Facsimile: [phone]
http://www.abb.com/substationautomation

Disclaimer
The data, examples and diagrams in this manual are included solely for the concept
or product description and are not to be deemed as a statement of guaranteed
properties. All persons responsible for applying the equipment addressed in this
manual must satisfy themselves that each intended application is suitable and
acceptable, including that any applicable safety or other operational requirements are
complied with. In particular, any risks in applications where a system failure and/or
product failure would create a risk for harm to property or persons (including but not
limited to personal injuries or death) shall be the sole responsibility of the person or
entity applying the equipment, and those so responsible are hereby requested to ensure
that all measures are taken to exclude or mitigate such risks.
This document has been carefully checked by ABB but deviations cannot be
completely ruled out. In case any errors are detected, the reader is kindly requested
to notify the manufacturer. Other than under explicit contractual commitments, in no
event shall ABB be responsible or liable for any loss or damage resulting from the
use of this manual or the application of the equipment.

Conformity
This product complies with the directive of the Council of the European Communities
on the approximation of the laws of the Member States relating to electromagnetic
compatibility (EMC Council Directive 2004/108/EC) and concerning electrical
equipment for use within specified voltage limits (Low-voltage directive 2006/95/
EC). This conformity is the result of a test conducted by ABB in accordance with
Article 10 of the directive in agreement with the product standards EN 50263 and EN
60255-26 for the EMC directive, and with the product standards EN 60255-6 and EN
60255-27 for the low voltage directive. The IED is designed in accordance with the
international standards of the IEC 60255 series.

Table of contents
Section 1 Introduction.......................................................................3
This manual........................................................................................3
Intended audience..............................................................................3
Protocol documentation......................................................................4
Product documentation set............................................................4
Document revision history.............................................................5
Related documentation..................................................................5
Document symbols and conventions..................................................6
Safety indication symbols..............................................................6
Document conventions..................................................................6
Section 2 DNP 3.0 overview.............................................................9
DNP 3.0 standard...............................................................................9
Documentation.................................................................................11
Section 3 Vendor-specific implementation.....................................13
DNP 3.0 link modes..........................................................................13
DNP 3.0 serial link mode.............................................................13
DNP 3.0 TCP/IP mode................................................................13
DNP 3.0 point list..............................................................................13
Binary input points.......................................................................13
Binary output status points and control relay output blocks........14
Analog inputs...............................................................................16
Analog data scaling................................................................17
Fault record timestamp...........................................................17
DNP points.......................................................................................18
Point configuration.......................................................................18
Class assignment........................................................................18
Section 4 DNP 3.0 parameters.......................................................21
Parameter descriptions.....................................................................21
Parameter list...................................................................................23
Section 5 Troubleshooting..............................................................25
Communication checklist..................................................................25
Section 6 Tolerances......................................................................27
DNP 3.0 timing considerations.........................................................27
Section 7 Glossary.........................................................................29
Table of contents
615 series 1
Communication Protocol Manual

2

Section 1 Introduction
1.1 This manual
Communication Protocol Manual describes a communication protocol supported by
the IED. The manual concentrates on vendor-specific implementations.
1.2 Intended audience
This manual addresses the communication system engineer or system integrator
responsible for pre-engineering and engineering for communication setup in a
substation from an IED perspective.
The system engineer or system integrator must have a basic knowledge of
communication in protection and control systems and thorough knowledge of the
specific communication protocol.
1MRS756709 A Section 1
Introduction
615 series 3
Communication Protocol Manual

1.3 Protocol documentation
1.3.1 Product documentation set
Planning & purchase
Engineering
Installing
Commissioning
Operation
Maintenance
Decommissioning deinstalling & disposal
Application manual
Operation manual
Installation manual
Service manual
Engineering manual
Commissioning manual
Communication protocol
manual
Technical manual
Planning & purchase
Engineering
Installing
Commissioning
Operation
Maintenance
Decommissioning deinstalling & disposal
Planning & purchase
Engineering
Installing
Commissioning
Operation
Maintenance
Decommissioning deinstalling & disposal
Application manualApplication manual
Operation manualOperation manual
Installation manualInstallation manual
Service manualService manual
Engineering manualEngineering manual
Commissioning manualCommissioning manual
Communication protocol
manual
Communication protocol
manual
Technical manualTechnical manual
en07000220.vsd
IEC07000220 V1 EN
Engineering Manual contains instructions on how to engineer the IEDs. The manual
provides instructions on how to use the different tools for IED engineering. It also
includes instructions on how to handle the tool component available to read
disturbance files from the IEDs on the basis of the IEC 61850 definitions. It further
introduces the diagnostic tool components available for IEDs and the PCM600 tool.
Installation Manual contains instructions on how to install the IED. The manual
provides procedures for mechanical and electrical installation. The chapters are
organized in chronological order in which the IED should be installed.
Commissioning Manual contains instructions on how to commission the IED. The
manual can also be used as a reference during periodic testing. The manual provides
procedures for energizing and checking of external circuitry, setting and
configuration as well as verifying settings and performing directional tests. The
chapters are organized in chronological order in which the IED should be
commissioned.
Section 1 1MRS756709 A
Introduction
4615 series
Communication Protocol Manual

Operation Manual contains instructions on how to operate the IED during normal
service once it has been commissioned. The manual can be used to find out how to
handle disturbances or how to view calculated and measured network data to
determine the cause of a fault.
Service Manual contains instructions on how to service and maintain the IED. The
manual also provides procedures for de-energizing, de-commissioning and disposal
of the IED.
Application Manual contains application descriptions and setting guidelines sorted
per function. The manual can be used to find out when and for what purpose a typical
protection function can be used. The manual can also be used when calculating
settings.
Technical Manual contains application and functionality descriptions and lists
function blocks, logic diagrams, input and output signals, setting parameters and
technical data sorted per function. The manual can be used as a technical reference
during the engineering phase, installation and commissioning phase, and during
normal service.
Communication Protocol Manual describes a communication protocol supported by
the IED. The manual concentrates on vendor-specific implementations.
Point List Manual describes the outlook and properties of the data points specific to
the IED. The manual should be used in conjunction with the corresponding
Communication Protocol Manual.
All manuals are not available yet.
1.3.2 Document revision history
Document revision/date Product series version History
A/04.03.2009 2.0 First release
Download the latest revision of the document from the ABB web site
http://www.abb.com/substationautomation.
1.3.3 Related documentation
Product-specific point list manuals and other product series- and product-specific
manuals can be downloaded from the ABB web site http://www.abb.com/
substationautomation .
1MRS756709 A Section 1
Introduction
615 series 5
Communication Protocol Manual

1.4 Document symbols and conventions
1.4.1 Safety indication symbols
This publication includes icons that point out safety-related conditions or other
important information.
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 might 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.
Although warning hazards are related to personal injury, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all warning and caution notices.
1.4.2 Document conventions
• Abbreviations and acronyms in this manual are spelled out in Glossary. Glossary
also contains definitions of important terms.
• Push button navigation in the LHMI menu structure is presented by using the
push button icons, for example:
To navigate between the options, use and .
• HMI menu paths are presented in bold, for example:
Select Main menu/Configuration/HMI.
• Menu names are shown in bold in WHMI, for example:
Click Information in the WHMI menu structure.
Section 1 1MRS756709 A
Introduction
6615 series
Communication Protocol Manual

• LHMI messages are shown in Courier font, for example:
To save the changes in non-volatile memory, select Yes and press .
• Parameter names are shown in italics, for example:
The function can be enabled and disabled with the Operation setting.
• Parameter values are indicated with quotation marks, for example:
The corresponding parameter values are "On" and "Off".
• IED input/output messages and monitored data names are shown in Courier font,
for example:
When the function starts, the START output is set to TRUE.
1MRS756709 A Section 1
Introduction
615 series 7
Communication Protocol Manual

8

Section 2 DNP 3.0 overview
2.1 DNP 3.0 standard
The DNP 3.0 protocol was developed by Westronic based on the early versions of
the IEC 60870-5 standard telecontrol protocol specifications. Now the protocol
specification is controlled by the DNP Users Group at www.dnp.org .
The ISO/OSI based model supported by this protocol specifies physical, data link and
application layers only. This reduced protocol stack is referred to as EPA. However,
to support advanced RTU functions and messages larger than the maximum frame
length as defined by the IEC document 60870-5-1, the DNP 3.0 data link is intended
to be used with a transport pseudo-layer. As a minimum, this transport layer
implements message assembly and disassembly services.
Physical layer
There are two physical layer modes specified; serial and serial tunneled over TCP/
IP.
Additional information on the DNP 3.0 physical layer is available at the DNP Users
Group at www.dnp.org .
Data link layer
The DNP 3.0 data link layer is designed to operate with connection-oriented and
connectionless asynchronous or synchronous bit serial physical layers. Fully balanced
transmission procedures were adopted to support spontaneous transmissions from
outstations.
Data link functions:
• Performing message data link retransmissions.
• Synchronizing and handling of the FCB in the control octet.
• Setting and clearing the DFC bit based on buffer availability.
• Packing user data into the defined frame format, include CRC checksums and
transmitting the data to the physical layer.
• Unpacking the data link frame received from the physical layer into user data,
check and remove CRC checksums.
• Controlling all aspects of the physical layer.
• Responding to all valid frames received from the physical layer.
Data link responsibilities:
1MRS756709 A Section 2
DNP 3.0 overview
615 series 9
Communication Protocol Manual

• Exchange of SDUs between peer DNP 3.0 data links
• Error notification to data link user
• Sequencing of SDUs
• SDU delivery quality.
Link-layer confirm usage is deprecated. See DNP Technical Bulletin TB1998-0402,
section 3 for details at www.dnp.org .
Transport pseudo-layer
To support advanced RTU functions and messages exceeding the maximum data link
frame length, a transport pseudo-layer which implements message assembly and
disassembly services was adopted. This pseudo-layer is actually a super-data link
transport protocol, which is normally included in some OSI protocol data links.
Transport functions:
• Fragmenting user data into one or more data link frames and transmitting the
data to the data link layer
• Assembling the data link frames received from the data link layer into user data
• Controlling all aspects of the data link excluding data link configuration.
Transport responsibilities:
• Exchange of SDUs between peer DNP 3.0 transport pseudo layers
• Error notification to transport user
• Sequencing of SDUs.
Application layer
The application layer is responsible for performing operations on data objects defined
by the device or on the device itself. These operations can be: returning actual values
(read function), assigning new values (write function) if the object represents control
points, arming and energizing the output point (select, operate or direct operate
functions) and if counters are used, storing actual values (freeze functions) and
clearing the counters.
Many objects may be assigned to event classes. The DNP 3.0 protocol defines four
classes; 0 for static data and 1, 2 and 3 for event data.
Binary inputs and analog inputs may be assigned to class 0. Binary events and analog
events may be assigned to classes 1, 2, or 3. If a binary event or analog event is in
class 1, 2, or 3, the corresponding input should be in class 0. The configuration
GUI provides this behavior. Any point which is not in class 0 will not be returned in
a class 0 scan, however, its static value may be read explicitly.
In the present implementation, the binary output object may not be assigned to
generate events in classes 1, 2 or 3. Instead, the outputs are available as binary inputs,
which may then be assigned to generate events. The actual status of the binary outputs
can be read from the binary inputs. A read of the binary outputs returns the last value
Section 2 1MRS756709 A
DNP 3.0 overview
10 615 series
Communication Protocol Manual

written to that output, not its present value. For this reason, the binary outputs are not
typically mapped to class 0.
Communication modes
The common DNP 3.0 communication modes are:
• Polled static mode, meaning that the master polls for class 0 or static data only
• Polled report by exception mode, where the Master polls for change events (class
1,2,3) and occasionally makes integrity polls (class 1, 2, 3, 0)
2.2 Documentation
This implementation of DNP 3.0 is fully compliant with DNP 3.0 Subset Definition
Level 2, and contains significant functionality beyond Subset Level 2.
1MRS756709 A Section 2
DNP 3.0 overview
615 series 11
Communication Protocol Manual

12

Section 3 Vendor-specific implementation
3.1 DNP 3.0 link modes
3.1.1 DNP 3.0 serial link mode
DNP 3.0 serial can be assigned to a serial communication port in the IED. Serial
communication ports are named COM1...COMn, depending on how many serial ports
the 615 series IED hosts..
DNP 3.0 protocol ignores any parity setting in the COM settings
group; DNP 3.0 is defined as an 8 bit/no parity protocol with a 16-bit
CRC every 16 bytes. This provides better error detection than parity.
3.1.2 DNP 3.0 TCP/IP mode
DNP 3.0 TCP/IP link mode is supported by the IED.
The IED listens for a connection from a DNP 3.0 master on port 20000.
Documentation concerning DNP 3.0 TCP/IP communication is available from
www.dnp.org .
3.2 DNP 3.0 point list
3.2.1 Binary input points
The binary input event buffer size is set to allow 200 events. Events that occur after
buffer overflow are discarded.
Table 1: Binary input poins
Description Value
Static (steady-state) object number 1
Change event object number 2
Static variation reported when variation 0
requested (default setting)
1 (binary input without status)
Change event variation reported when variation 0
requested (default setting)
2 (binary input change with time)
1MRS756709 A Section 3
Vendor-specific implementation
615 series 13
Communication Protocol Manual

Table 2: Default Class assignment for Binary Input points
Point index Name/description Default change event assigned class (1, 2, 3
or none)
See the point list manual. 1
3.2.2 Binary output status points and control relay output blocks
The BOS points (object 10) and the CROBs (object 12) are provided in the
configuration-specific point list.
While BOS points are included here for completeness, that is they are required by the
DNP 3.0 standard, they are not often polled by DNP 3.0 Masters. The DNP 3.0
standard recommend that BOS points represent the most recent DNP 3.0 commanded
value for the corresponding CROB point. Because many, if not most, CROB points
are controlled internally through pulse mechanisms, the value of the output status
may be meaningless.
As an alternative, the actual status values of CROB points have been looped around
and mapped as BIs and in the case of the breaker, as AI. BOS points that relate to
physical binary outputs are in this implementation looped back and mapped as binary
inputs. The actual status value, as opposed to the commanded status value, is the value
of the actuated control. For example, a DNP 3.0 control command may be blocked
through hardware or software mechanisms; in this case, the actual status value would
indicate the control failed because of the blocking. Looping CROB actual status
values as BIs has several advantages:
• it allows actual statuses to be included in class 0 polls,
• it allows change event reporting of the actual statuses, which is a more efficient
and time-accurate method of communicating control values,
• and it allows reporting of time-based information associated with controls,
including any delays before controls are actuated, and any durations if the
controls are pulsed.
BOS points that relate to some kind of software binary output points, that is reset- or
acknowledge points, are not looped back as binary inputs.
The default select/control buffer size is large enough to hold 10 of the largest select
requests possible.
DNP 3.0 pulse commands, and associated count, off-time and on-time, are not
supported in this implementation.
From the IED's perspective, there are two types of CROB points. Most are internally
mapped to IEC 61850 SPC, while the breaker control is mapped to 61850 DPC.
SPC based CROB, for example, physical outputs and LEDs:
Section 3 1MRS756709 A
Vendor-specific implementation
14 615 series
Communication Protocol Manual