RER615 DNP3 Communication Protocol Manual
RER615 DNP3 Communication Protocol Manual
RER615 DNP3 Communication Protocol Manual
Grid Automation
Recloser Protection and Control RER615
DNP3 Communication Protocol Manual
Document ID: 1MRS757820
Issued: 2015-03-06
Revision: B
Product version: 1.1
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
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
Additional parameters..................................................................21
Parameter list...................................................................................22
Section 5 Glossary.........................................................................25
Section 1 Introduction
Maintenance
Engineering
Planning &
Installation
Operation
purchase
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-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.1 Symbols
The tip icon indicates advice on, for example, how to design your
project or how to use a certain function.
• 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.
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.
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:
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.2 Documentation
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.
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.
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:
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.
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.
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.
The four scaling options associated with analog input data reporting are None,
Ratio, Multiplicative and Divisor. The selection None means that no scaling is
performed on the source IEC 61850 value. The value is reported as such to DNP3.
The ratio, multiplicative and divisor scaling methods use the first two arguments,
souceMinVal and sourceMaxVal, to define the source value range inside which the
object is to be used. The complete value range of the object is usually wanted even
though the user could freely define the source range.
Arguments three and four, destMinVal and destMaxVal, define the destination
value range. In ratio scaling, arguments destMinVal and destMaxVal define the
corresponding range of the scaled, reported DNP3 value.
DNPvalue=
(destMaxVal-destMinV Val)
(sourceValue - sourceMinVal) (sourceMaxVal - sourceMinVal) +destMinVal
GUID-9F985816-2268-412A-AE24-ED90EAC44AD7 V2 EN (Equation 1)
sourceValue
DNPvalue = + destMinVal
destMaxVal
GUID-01F26415-274B-4844-B861-DB7D6E56D91B V1 EN (Equation 3)
Point gaps may be inserted if wanted. Point gaps cannot be read by the client.
BOS points exist only if the corresponding CROB point has been inserted in the
active point list.
The general-purpose objects can be connected to any internal object in the IED
configuration application using the Application Configuration or Signal Matrix
tool. This gives additional opportunities for the protocols.
Example 1
Due to security reasons, protocols do not contain mappings for the direct control of
physical outputs. This way, the client cannot accidentally write a change to a
physical output.
Example 2
The legacy protocol default mappings are a selection of the most important signals
produced by the IEC 61850-based IED applications. The manufacturer’s selection
of important signals may not always serve every customer.
Example 3
The basic IEC 61850 application model of the IED produces a great amount of
information. In some cases, this is more than what is feasible to transport through a
legacy protocol. Via the PCM600/Communication Management tools, unnecessary
data objects can be excluded from the legacy protocol.
Unit address is the slave 16 bit link address. This value should be set between 1
and 65519, since DNP3 reserves the top 16 addresses. All DNP3 devices sharing
the same network should have unique addresses.
Master address is the 16 bit link address at which the initial unsolicited message is
sent. The value should be unique, between 1 and 65519.
Serial port configures DNP3 for the selected serial channel only if DNP3 physical
layer is set for Serial. The serial port speed is set under Communication/COM1
and Communication/COM2.
Data link confirm enables or disables the data link confirmation. Options are:
never, only for multi-frame, messages or always. Option never is recommended in
DNP Technical Bulletin 1998 0402.
Data link retries is the data link retry count from 0 to 65535.
Data Link inter char delay is the allowed inter character delay for incoming
messages. The timer starts with the reception of each character. When the timer
expires because no additional characters have been received, the IED regards the
incoming message complete. The unit of measure is a character time at the selected
baud rate.
UR retries is the number of times the slave will resend the unsolicited response if it
is not confirmed by the master station.
UR Class 1,2,3 Min events are the class 1, 2 or 3 number of events that must
accumulate before they are sent as unsolicited messages, unless the UR Class 1,2,3
TO expires causing the transmission of the events.
UR Class 1,2,3 TO is the time in ms, that class 1, 2 or 3 events are delayed before
being sent out, unless a count of UR Class 1,2,3 Min events have accumulated
causing the transmission of the events.
Legacy master UR provides compatibility to some older DNP3 masters. When set
to disabled, the slave follows the DNP3 standard, sending its first unsolicited
message after a connection has been established following IED reboot. The master
is expected to send the Enable/Disable Unsolicited messages command to the IED.
When Legacy master UR is enabled, the IED does not send the initial unsolicited
message. Unsolicited responses are sent without the need of the Enable Unsolicited
command. The master still needs to open a connection for the slave to start sending
unsolicited messages. Unsolicited mode needs to be enabled for this parameter to
be operational.
Need time interval is the interval in minutes for setting the need time bit in the IIN.
The IIN need time bit requests the DNP3 master to send a time synchronization to
the IED. When set to 0, the need time IIN bit is never set, and DNP3 time
synchronization is never requested. The time synchronization source needs to be
set to DNP3 to allow the DNP3 time synchronization. The DNP3 delay
measurement can have an adverse effect on time synchronization accuracy, and it
should be avoided for TCP/IP.
Default Variation Obj N is the variation with which the slave replies when the
master asks for DNP Object type N variation 0. It is also the variation in which
class events are reported.
Deadbanding of the analog static values cannot be set in DNP3. Event generation is
dependent on the functions employed in the IED, and the execution loops to which
these functions belong. See the IED’s technical manual for setting deadbands.
As a result of the event generation mechanism in the IED, the events reported by
DNP3 are very accurate and are the same events that can be retrieved over the
WHMI or other protocols such as IEC 61850-8-1.
Legacy master SBO provides compatibility to some older DNP3 masters for the
Select Before Operate command. When disabled, DNP3 expects the application
The DNP3 parameters can be accessed with PCM600 or via the LHMI path
Configuration/Communication/DNP3.0.
Power must be cycled to the unit after making changes to the DNP3
parameters. The LHMI or WHMI do not notify that this action must
be taken.
Section 5 Glossary
www.abb.com/substationautomation