ABB Relion 620 Series User manual

—
RELION® PROTECTION AND CONTROL
620 series ANSI
DNP3 Communication Protocol Manual

Document ID: 1MAC459571-IB
Issued: 2019-05-29
Revision: C
Product version: 2.0
© Copyright 2019 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 and Relion are registered trademarks of the ABB Group. All other brand or product
names mentioned in this document may be trademarks or registered trademarks of their
respective holders.
Warranty
Please inquire about the terms of warranty from your nearest ABB representative.
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 product has been designed to be connected and communicate data and information
via a network interface which should be connected to a secure network. It is the sole
responsibility of the person or entity responsible for network administration to ensure a
secure connection to the network and to take the necessary measures (such as, but not
limited to, installation of firewalls, application of authentication measures, encryption of
data, installation of anti virus programs, etc.) to protect the product and the network, its
system and interface included, against any kind of security breaches, unauthorized access,
interference, intrusion, leakage and/or theft of data or information. ABB is not liable for
any such damages and/or losses.
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 Directive 2014/30/EU) and concerning electrical equipment for use
within specified voltage limits (Low-voltage directive 2014/35/EU). This conformity is
the result of tests conducted by ABB in accordance with the product standards EN 50263
and EN 60255-26 for the EMC directive, and with the product standards EN 60255-1 and
EN 60255-27 for the low voltage directive. The product is designed in accordance with the
international standards of the IEC 60255 series and ANSI C37.90. The DNP3 protocol
implementation in this product conforms to "DNP3 Intelligent Electronic Device (IED)
Certification Procedure Subset Level 2", available at www.dnp.org. This product
complies with the UL 508 certification.

Table of contents
Section 1 Introduction............................................................................3
This manual.............................................................................................. 3
Intended audience.................................................................................... 3
Product documentation.............................................................................4
Product documentation set..................................................................4
Document revision history................................................................... 4
Related documentation........................................................................5
Symbols and conventions.........................................................................5
Symbols...............................................................................................5
Document conventions........................................................................ 6
Section 2 DNP3 overview......................................................................7
DNP3 standard......................................................................................... 7
Documentation..........................................................................................9
Section 3 Vendor-specific implementation.......................................... 11
DNP3 link modes.................................................................................... 11
DNP3 data objects.............................................................................11
DNP3 serial link mode....................................................................... 11
DNP3 TCP/IP mode...........................................................................12
DNP3 point settings................................................................................ 12
Binary input points............................................................................. 12
Binary output status points and control relay output blocks.............. 12
Analog inputs.....................................................................................14
Analog data scaling...................................................................... 15
Fault record time stamp................................................................17
DNP3 points............................................................................................17
Point configuration.............................................................................17
Class assignment.............................................................................. 17
Section 4 DNP3 parameters................................................................19
Parameter descriptions...........................................................................19
Parameter list..........................................................................................22
Section 5 Tolerances...........................................................................25
DNP3 timing considerations................................................................... 25
Table of contents
620 series ANSI 1
Communication Protocol Manual

Section 6 Glossary.............................................................................. 27
Table of contents
2620 series ANSI
Communication Protocol Manual

Section 1 Introduction
1.1 This manual
The communication protocol manual describes a communication protocol supported by
the protection relay. 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 the communication setup in a substation
from a protection relay's 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.
1MAC459571-IB C Section 1
Introduction
620 series ANSI 3
Communication Protocol Manual

1.3 Product documentation
1.3.1 Product documentation set
Planning & purchase Engineering Installation Commissioning Operation Maintenance Decommissioning, deinstallation & disposal
Quick start guide
Quick installation guide
Brochure
Product guide
Operation manual
Installation manual
Connection diagram
Engineering manual
Technical manual
Application manual
Communication protocol manual
IEC 61850 engineering guide
Point list manual
Cyber security deployment guideline
GUID-06ED1128-B7CA-43DC-83B2-24A31B78D460 V1 EN
Figure 1: The intended use of documents during the product life cycle
Product series- and product-specific manuals can be downloaded from the
ABB Web site http://www.abb.com/relion.
1.3.2 Document revision history
Document revision/date Product series version History
A/2012-10-31 2.0 First release
B/2019-05-17 2.0 Content updated
C/2019-05-29 2.0 Content updated
Section 1 1MAC459571-IB C
Introduction
4620 series ANSI
Communication Protocol Manual

Download the latest documents 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.
The purpose of this document is to describe specific configuration and interoperability
information for an implementation of the Distributed Network Protocol, Version 3.0. This
document, in conjunction with the DNP3 Basic 4 Document Set, and the DNP Subset
Definitions Document, provides complete information on how to communicate via the
DNP3 protocol.
1.4 Symbols and conventions
1.4.1 Symbols
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 of important 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 is necessary to understand that
under certain operational conditions, operation of damaged equipment may result in
degraded process performance leading to personal injury or death. Therefore, comply
fully with all warning and caution notices.
1MAC459571-IB C Section 1
Introduction
620 series ANSI 5
Communication Protocol Manual

1.4.2 Document conventions
A particular convention may not be used in this manual.
• Abbreviations and acronyms are spelled out in the glossary. The glossary also
contains definitions of important terms.
• Push button navigation in the LHMI menu structure is presented by using the push
button icons.
To navigate between the options, use and .
• Menu paths are presented in bold.
Select Main menu/Settings.
• WHMI menu names are presented in bold.
Click Information in the WHMI menu structure.
• LHMI messages are shown in Courier font.
To save the changes in nonvolatile memory, select Yes and press .
• Parameter names are shown in italics.
The function can be enabled and disabled with the Operation setting.
• Parameter values are indicated with quotation marks.
The corresponding parameter values are "Enabled" and "Disabled".
• Input/output messages and monitored data names are shown in Courier font.
When the function picks up, the PICKUP output is set to TRUE.
• Dimensions are provided both in inches and mm. If it is not specifically mentioned,
the dimension is in mm.
Section 1 1MAC459571-IB C
Introduction
6620 series ANSI
Communication Protocol Manual

Section 2 DNP3 overview
2.1 DNP3 standard
The DNP3 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 DNP3 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 specified physical layer modes; serial and Ethernet.
Additional information on the DNP3 physical layer is available at the
DNP Users Group at www.dnp.org.
Data link layer
The DNP3 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 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.
1MAC459571-IB C Section 2
DNP3 overview
620 series ANSI 7
Communication Protocol Manual

• Controlling all aspects of the physical layer.
• In unsolicited reporting mode, performing collision avoidance/detection procedures
to ensure reliable transfer of data across the physical link.
• Responding to all valid frames received from the physical layer.
Data link responsibilities:
• Exchange of SDUs between peer DNP3 data links
• Error notification to data link user
• Sequencing of SDUs
• SDU delivery quality.
Link-layer confirm usage is deprecated.
See the 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 DNP3 transport pseudo layers
• Error notification to transport users
• 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.
Section 2 1MAC459571-IB C
DNP3 overview
8620 series ANSI
Communication Protocol Manual

Many objects may be assigned to event classes. The DNP3 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 written to that
output, not its present value. For this reason, the binary outputs are not typically mapped
to class 0.
Communication modes
The IED supports three DNP communication modes.
• 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)
• Unsolicited report by exception mode, where the slave reports change events
spontaneously without being polled by the master. Master occasionally makes
integrity polls (class 1, 2, 3, 0).
2.2 Documentation
This implementation of DNP3 is fully compliant with DNP3 Subset Definition Level 2,
and contains significant functionality beyond Subset Level 2.
1MAC459571-IB C Section 2
DNP3 overview
620 series ANSI 9
Communication Protocol Manual

10

Section 3 Vendor-specific implementation
3.1 DNP3 link modes
Serial and TCP/IP modes are available. They are mutually exclusive.
3.1.1 DNP3 data objects
The DNP3 protocol in 620 series IEDs is built on top of the internal IEC 61850 data model.
Thus, the DNP3 application data objects and Class events are derived from IEC 61850
data objects and data set reporting. The 620 series IEDs have a predefined IEC 61850 data
set configuration. In other words, it is predefined which internal data object changes the
620 series IEDs detect.
The available DNP3 data objects in the 620 series IEDs are selected from the objects
predefined in the IEC 61850 data sets. IEC 61850 data set reporting and DNP3 Class event
reporting are basically identical.
For a list of the available data objects, see the point list manual.
3.1.2 DNP3 serial link mode
DNP3 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
620 series IED hosts.
If this protocol does not operate as expected, check that other serial
protocols are not using the COM port also.
DNP3 protocol ignores any parity setting in the COM settings group;
DNP3 is defined as an 8 bit/no parity protocol with a 16-bit CRC every 16
bytes. This provides better error detection than parity.
1MAC459571-IB C Section 3
Vendor-specific implementation
620 series ANSI 11
Communication Protocol Manual

3.1.3 DNP3 TCP/IP mode
DNP3 TCP/IP link mode is supported by the protection relay.
The protection relay listens for a connection from a DNP3 master on port 20000. A single
DNP3 session can be run concurrently with IEC 61850, Modbus Serial and/or Modbus
TCP. Documentation concerning DNP3 TCP/IP communication is available from
www.dnp.org.
3.2 DNP3 point settings
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 points
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)
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
DNP3 standard, they are not often polled by DNP3 Masters. The DNP3 standard
recommends that BOS points represent the most recent DNP3 command 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.
Section 3 1MAC459571-IB C
Vendor-specific implementation
12 620 series ANSI
Communication Protocol Manual

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 command status value, is the value of the actuated
control. For example, a DNP3 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.
DNP3 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:
• Operation is blocked unless the IED is in the remote switch position.
• Timeout selection is configurable.
• SPC points support both DIRECT (Direct Operate) and SBO (Select-Before-
Operate).
LED output points only support latch off and trip commands. An error will
be returned by the IED if latch on or close is sent to an LED output.
DPC based CROB, for example, breaker control:
• Operation is blocked unless IED is in the remote switch position.
• Timeout selection is configurable.
• DPC point DIRECT/SBO behavior is determined by the Control_model parameter in
Configuration/Control/52(2)/Control_model.
1MAC459571-IB C Section 3
Vendor-specific implementation
620 series ANSI 13
Communication Protocol Manual

1. The DNP stack accepts SBO commands if the Control_model parameter is
configured for "sbo-with-enhanced-security".
2. DIRECT commands are accepted if the parameter is set to "direct-with-normal-
security".
3. Otherwise, the command violates the Control_model, and is rejected.
Table 3: Binary output status points
Description Value
Object number 10
Default variation reported when variation 0
requested (default setting)
2 (BOS)
Table 4: Control relay output blocks
Description Value
Object number 12
Table 5: CROB fields supported
Point index Name/description Supported CROB fields
See the point list manual. All1)
1) In this IED implementation the pulse-on time cannot be commanded from the DNP3 master. A value in the
variable pulse-on time field in the CROB command is ignored, but the command is accepted. It should be
noticed that control pulse lengths for CB controls in this IED are configurable via PCM600. Pulse lengths for
other types of outputs are in internally fixed.
3.2.3 Analog inputs
The following table lists analog inputs (object 30). It is important to note that 16 bit and
32 bit variations of analog inputs are transmitted through DNP3 as signed numbers.
The original DNP3 analog value is the same value as the IEC 61850 value
generated for the same point. Measurands in IEC 61850 are expressed as
floating point values while DNP3 analog values are integers. Therefore, it
may be necessary to scale the original DNP3 values in order to include
possible decimals in the DNP3 integer value.
The deadband is not configured in DNP3. It is configured at the device level. The analog
change events are therefore generated by the device functions, not DNP3. The analog
change event time stamp will inherently be accurate and consistent with the reporting of
Section 3 1MAC459571-IB C
Vendor-specific implementation
14 620 series ANSI
Communication Protocol Manual