ABB Relion RER615 DNP3 User manual

Relion® product family
Grid Automation
Recloser Protection and Control RER615
DNP3 Communication Protocol Manual

Document ID: 1MRS757820
Issued: 2015-03-06
Revision: B
Product version: 1.1
© Copyright 2015 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.
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 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 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 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.

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..................................................................5
Section 2 DNP3 overview.................................................................7
DNP3 standard...................................................................................7
Physical layer................................................................................7
Data link layer................................................................................7
Transport pseudo-layer.................................................................8
Application layer............................................................................8
Communication modes..................................................................9
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....................................................................11
DNP3 point list..................................................................................12
Binary input points.......................................................................12
Binary output status points and control relay output blocks........12
Analog inputs...............................................................................14
Analog data scaling................................................................15
DNP points.......................................................................................16
Point configuration.......................................................................16
Class assignment........................................................................16
Accessing of non-protocol-mapped data.....................................17
Section 4 DNP3 parameters...........................................................19
Parameter descriptions.....................................................................19
Link parameters...........................................................................19
Application layer parameters.......................................................19
Unsolicited mode parameters......................................................20
Table of contents
Recloser Protection and Control RER615 1
Communication Protocol Manual

Additional parameters..................................................................21
Parameter list...................................................................................22
Section 5 Glossary.........................................................................25
Table of contents
2Recloser Protection and Control RER615
Communication Protocol Manual

Section 1 Introduction
1.1 This manual
The 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.
1MRS757820 B Section 1
Introduction
Recloser Protection and Control RER615 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 Engineering Guide
Communication protocol manual
IEC 61850 Engineering guide
Point list manual
GUID-7414985D-2433-46E4-B77B-CCE64F6FC8D0 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 Website http://www.abb.com/relion.
1.3.2 Document revision history
Document revision/date Product version History
A/2013-09-17 1.0 First release
B/2015-03-06 1.1 Content updated to correspond to the
product version
Download the latest documents from the ABB Website
http://www.abb.com/substationautomation.
Section 1 1MRS757820 B
Introduction
4Recloser Protection and Control RER615
Communication Protocol Manual

1.3.3 Related documentation
Name of the document Document ID
Application Engineering Guide 1MRS757818
Modbus Communication Protocol Manual 1MRS757819
IEC 60870-5-101/104 Communication Protocol Manual 1MRS757821
IEC 61850 Engineering Guide 1MRS757809
Engineering Manual 1MRS757810
Installation Manual 1MRS757799
Operation Manual 1MRS757816
Technical Manual 1MRS757817
Product-specific point list manuals and other product series- and product-specific
manuals can be downloaded from the ABB Website
http://www.abb.com/substationautomation.
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.
1.4.2 Document conventions
A particular convention may not be used in this manual.
1MRS757820 B Section 1
Introduction
Recloser Protection and Control RER615 5
Communication Protocol Manual

• Abbreviations and acronyms are spelled out in the glossary. The glossary also
contains definitions of important terms.
• The example figures illustrate the IEC display variant.
• Menu paths are presented in bold.
Select Main menu/Settings.
• LHMI messages are shown in Courier font.
To save the changes in non-volatile 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 "On" and "Off".
• IED input/output messages and monitored data names are shown in Courier font.
When the function starts, the START output is set to TRUE.
Section 1 1MRS757820 B
Introduction
6Recloser Protection and Control RER615
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.
2.1.1 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.
2.1.2 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.
1MRS757820 B Section 2
DNP3 overview
Recloser Protection and Control RER615 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.
2.1.3 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
2.1.4 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 include
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 1MRS757820 B
DNP3 overview
8Recloser Protection and Control RER615
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.
2.1.5 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.
1MRS757820 B Section 2
DNP3 overview
Recloser Protection and Control RER615 9
Communication Protocol Manual

10

Section 3 Vendor-specific implementation
3.1 DNP3 link modes
3.1.1 DNP3 data objects
The DNP3 protocol in 615 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 615 series IEDs have a
predefined IEC 61850 data set configuration. In other words, it is predefined which
internal data object changes the 615 series IEDs detect.
The available DNP3 data objects in the 615 series IEDs are selected from the
objects predefined in the IEC 61850 data sets. Consequently, all the available
DNP3 data points can be freely configured for DNP3 Class event reporting.
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 615 series IED hosts.
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.
3.1.3 DNP3 TCP/IP mode
DNP3 TCP/IP link mode is supported by the IED.
The IED listens for a connection from a DNP3 master on port 20000.
Documentation concerning DNP3 TCP/IP communication is available from
www.dnp.org.
1MRS757820 B Section 3
Vendor-specific implementation
Recloser Protection and Control RER615 11
Communication Protocol Manual

3.2 DNP3 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 points
Description Value
Static (steady-state) object number 1
Static variation reported when variation 0
requested (default setting)
1 (binary input without status)
Change event object number 2
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.
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:
Section 3 1MRS757820 B
Vendor-specific implementation
12 Recloser Protection and Control RER615
Communication Protocol Manual

• 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.
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/CBXCBR1/Control_model.
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
1MRS757820 B Section 3
Vendor-specific implementation
Recloser Protection and Control RER615 13
Communication Protocol Manual

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 events though other channels, for example, LHMI, WHMI and
other communication protocols.
There are four scaling options associated with analog input reporting.
• None: the reported value is the process value.
• Multiplication: the process value is multiplied by a constant. An offset is
added producing the reported value.
• Division: the process value is divided by a constant. An offset is added
producing the reported value.
• Ratio:
• Configuration-time ratio scaling: Find R for new set of {in_min, in_max,
out_min, out_max}
R = (out_max - out_min)/(in_max - in_min)
• Runtime ratio scaling: Reported value = (inval - in_min) * R + out_min
The analog input event buffer size is set to 150. Events that occur after buffer
overflow are discarded.
Section 3 1MRS757820 B
Vendor-specific implementation
14 Recloser Protection and Control RER615
Communication Protocol Manual