RER615 DNP3 Communication Protocol 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
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
Recloser Protection and Control RER615 1

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

1MRS757820 B Section 1
Introduction
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.

Section 1 1MRS757820 B
Introduction
1.3 Product documentation
1.3.1 Product documentation set
deinstallation & disposal

Decommissioning,
Commissioning
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 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.

Introduction
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.

Introduction
• 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.

DNP3 overview
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.

DNP3 overview
• 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.

DNP3 overview
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.

10
Vendor-specific implementation
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.

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 1 (binary input without status)
requested (default setting)
Change event object number 2
Change event variation reported when variation 2 (binary input change with time)
0 requested (default setting)
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:

• 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 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 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.

Table 6: Analog inputs

Description Values
Static (steady-state) object number 30
Static variation reported when variation 0 2 (16-bit analog input)
Change event object number 32
Change event variation reported when variation 4 (16-bit analog input change with time)
0 requested (default setting)
Table 7: Default Class assignment for analog input data

Point index Name/description Default deadband Default change event
assigned class (1, 2, 3 or
none)
See the point list manual. Configurable IED setting 2
3.2.3.1 Analog data scaling
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.
Ratio, multiplicative and divisor scaling methods

The PCM600 tool contains four value arguments related to the scaling methods:
sourceMinVal, sourceMaxVal, destMinVal and destMaxVal. The use of these
arguments differs depending on the scaling method.
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)
In multiplicative scaling, argument four destMaxVal becomes a scale constant and

argument three destMinVal becomes an offset.
DNPvalue = ( sourceValue × destMaxVal ) + destMinVal

GUID-4CB1987F-BDD8-48A2-9389-20B0B2EB271F V1 EN (Equation 2)

In divisor scaling, argument four destMaxVal becomes a scale constant and

argument three destMinVal becomes an offset.
 sourceValue 
DNPvalue =   + destMinVal
 destMaxVal 
GUID-01F26415-274B-4844-B861-DB7D6E56D91B V1 EN (Equation 3)
3.3 DNP points
3.3.1 Point configuration

The DNP3 point map is configurable in PCM600. All points in the IED are
unmapped as default. In PCM600, the unmapped points in the variables list on the
left may be inserted to the active point list on the right.
Point gaps may be inserted if wanted. Point gaps cannot be read by the client.
3.3.2 Class assignment

Class assignment allows the events generated in the IED to be reported as DNP3
events. Some configurations exceed the class assignment possibilities defined by
the standard.
Table 8: DNP3 point map configuration

Configuration Description
None Integrity class 0 scan returns gap.
Value is available only via static scan.
Point does not generate events.
Class 0 Point is returned in the class 0 scan.
Point does not generate events.
Class 0 and any class 1,2,3 Point is returned in the class 0 scan.
combination Point generates events for the selected class or classes.
Class 1, 2 or 3 combination Point is not returned in the class 0 scan.
Point generates events for the selected class or classes.
BOS points exist only if the corresponding CROB point has been inserted in the
active point list.
Class assignment cannot be performed on CROBs. They can only be performed on

the corresponding BOS points in a limited fashion; they may only be assigned
Class 0 or None and only affect the class 0 scan. This means they cannot be
configured to generate events. The BOS points, however, have been made available
as BI points, which can be configured to generate events.

3.3.3 Accessing of non-protocol-mapped data

The IED application includes a number of general-purpose I/O data. By default,
these data are mapped to this protocol. See the point list manual for the exact
mappings.
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.
It is possible to connect general-purpose outputs to physical outputs using the

Application Configuration tool. The general-purpose output can also be controlled
from the protocol.
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.
Any non-protocol-mapped internal signal can be freely connected to a general-

purpose input object via the Application Configuration tool. This object can then
be accessed by the legacy protocol as regular protocol application data.
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.
However, in some cases a better solution is to OR together several internal signals

into one general signal. This OR output can be connected to a general-purpose
input and accessed by the legacy protocol as regular protocol application data.

18
DNP3 parameters
Section 4 DNP3 parameters
4.1 Parameter descriptions
4.1.1 Link parameters

DNP physical layer configures DNP3 for the TCP/IP or serial channel.
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 confirm TO is the data link confirmation timeout in milliseconds.
Data link retries is the data link retry count from 0 to 65535.
Data Link Rx to Tx delay is the turnaround delay in milliseconds of the slave

replies. The timer starts at the trailing edge of the master's request.
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.
4.1.2 Application layer parameters

When App layer confirm is disabled, the IED requests application confirmation for
event messages only. When it is enabled, the IED also requests application
confirmations for all the sent application.
App confirm TO is the application layer confirmation timeout in milliseconds.

Application layer confirmations received from the master after App confirm TO
has expired are not acknowledged by the IED.

DNP3 parameters
App layer fragment is the application layer fragment size in bytes.
CROB select timeout is the DNP3 selecting before operating timer.
4.1.3 Unsolicited mode parameters

UR mode Unsolicited responses mode may be set to enable or disable. If enabled,
the initial unsolicited message is sent when the master opens a connection to the
IED, the first time after a IED reboot. All other unsolicited response parameters are
irrelevant if UR mode is disabled.
Enabling UR mode on a serial multidrop line is not recommended.

Collisions will result from multiple IEDs reporting concurrent
events. Although the DNP3 application layer will recover, collision
recovery can create significant traffic.
UR retries is the number of times the slave will resend the unsolicited response if it
is not confirmed by the master station.
UR TO is the unsolicited response timeout period in milliseconds. This timeout

period starts after App confirm TO expires. A new unsolicited response is
transmitted when UR TO expires. Application layer confirmations received from
the master during the UR TO period are not acknowledged by the IED.
UR offline interval is the unsolicited message offline interval in minutes. Offline

interval starts after the last UR retry. Offline interval never starts when UR retries
= 65535 (0xFFFF).
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.
Legacy master UR allows non-standards compliant behavior.

DNP3 parameters
Legacy master SBO allows non-standards compliant behavior.
4.1.4 Additional parameters

Time format can be set to Local or UTC.
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.
Table 9: Default variation options for supported DNP object types

DNP Obj N Default variation option Variation description
1 Binary input
1 2 Binary input with status
1 Binary input event
2 2 Binary input event with time
1 32 bit analog input
2 16 bit analog input
3 32 bit analog input without flag
30 4 16 bit analog input without flag
1 32 bit analog input event
2 16 bit analog input event
3 32 bit analog input event with time
32 4 16 bit analog input event with time
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

DNP3 parameters
layer sequence of the operating command to be the selecting command sequence +

1 modulo 16. When enabled, the IED ignores the sequence number of the operating
command. This situation might occur when the master sends additional requests
between the selecting and operating commands.
4.2 Parameter list
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.
Table 10: DNP3 settings

Parameter Values (Range) Unit Step Default Description
DNP physical layer 1=Serial 2=TCP/IP DNP physical layer
2=TCP/IP
Unit address 1...65519 1 1 DNP unit address
Master address 1...65519 1 3 DNP master and UR address
Serial port 0=Not in use 0=Not in use COM port for serial interface, when
1=COM 1 physical layer is serial.
2=COM 2
Need time interval 0...65535 min 1 30 Period to set IIN need time bit
Time format 0=UTC 1=Local UTC or local. Coordinate with master.
1=Local
CROB select timeout 1...65535 sec 1 10 Control Relay Output Block select timeout
Data link confirm 0=Never 0=Never Data link confirm mode
1=Only Multiframe
2=Always
Data link confirm TO 100...65535 ms 1 3000 Data link confirm timeout
Data link retries 0...65535 1 3 Data link retries count
Data link Rx to Tx delay 0...255 ms 1 0 Turnaround transmission delay
Data link inter char delay 0...20 char 1 4 Inter character delay for incoming
messages
App layer confirm 1=Disable 1=Disable Application layer confirm mode
2=Enable
App confirm TO 100...65535 ms 1 5000 Application layer confirm and UR timeout
App layer fragment 256...2048 bytes 1 2048 Application layer fragment size
UR mode 1=Disable 1=Disable Unsolicited responses mode
2=Enable
UR retries 0...65535 1 3 Unsolicited retries before switching to
UR offline mode
UR TO 0...65535 ms 1 5000 Unsolicited response timeout
Table continues on next page

DNP3 parameters
Parameter Values (Range) Unit Step Default Description

UR offline interval 0...65535 min 1 15 Unsolicited offline interval
UR Class 1 Min events 0...999 1 2 Min number of class 1 events to
generate UR
UR Class 1 TO 0...65535 ms 1 50 Max holding time for class 1 events to
generate UR
generate UR
generate UR
generate UR
generate UR
Legacy master UR 1=Disable 1=Disable Legacy DNP master unsolicited mode
2=Enable support. When enabled relay does not
send initial unsolicited message.
Legacy master SBO 1=Disable 1=Disable Legacy DNP Master SBO sequence
2=Enable number relax enable
Default Var Obj 01 1...2 1 1 1=BI; 2=BI with status.
Default Var Obj 02 1...2 1 2 1=BI event; 2=BI event with time.
Default Var Obj 30 1...4 1 2 1=32 bit AI; 2=16 bit AI; 3=32 bit AI
without flag; 4=16 bit AI without flag.
Default Var Obj 32 1...4 1 4 1=32 bit AI event; 2=16 bit AI event;
3=32 bit AI event with time; 4=16 bit AI
event with time.

24
Glossary
Section 5 Glossary
615 series Series of numerical IEDs for low-end protection and

supervision applications of utility substations, and industrial
switchgear and equipment
AI Analog input
BI Binary input
BOS Binary output status
CB Circuit breaker
CRC Cyclical redundancy check
CROB Control relay output block
DFC Data flow control
DNP3 A distributed network protocol originally developed by
Westronic. The DNP3 Users Group has the ownership of
the protocol and assumes responsibility for its evolution.
DPC Double-point control
EMC Electromagnetic compatibility
EPA Enhanced performance architecture
Ethernet A standard for connecting a family of frame-based
computer networking technologies into a LAN
FCB 1. Flow control bit
2. Frame count bit
GUI Graphical user interface
IEC International Electrotechnical Commission
IEC 60870-5 IEC standard for telecontrol equipment and systems. Part
5 defines transmission protocols.
IEC 61850 International standard for substation communication and
modeling
IEC 61850-8-1 A communication protocol based on the IEC 61850
standard series
IED Intelligent electronic device
ISO International Standard Organization
LHMI Local human-machine interface
OSI Open systems interconnection

Glossary
PCM600 Protection and Control IED Manager

RTU Remote terminal unit
SDU Service data unit
TCP/IP Transmission Control Protocol/Internet Protocol
UR Unsolicited response
WHMI Web human-machine interface

27
Contact us
1MRS757820 B © Copyright 2015 ABB. All rights reserved.

ABB Oy
Medium Voltage Products,
Distribution Automation
P.O. Box 699
FI-65101 VAASA, Finland
Phone +358 10 22 11
Fax +358 10 22 41094
www.abb.com/substationautomation

RER615 DNP3 Communication Protocol Manual

Uploaded by

Copyright:

Available Formats

RER615 DNP3 Communication Protocol Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RER615 DNP3 Communication Protocol Manual

Uploaded by

Copyright:

Available Formats

Relion® product family

© Copyright 2015 ABB. All rights reserved

The software or hardware described in this document is furnished under a license

Section 2 DNP3 overview.................................................................7

Section 3 Vendor-specific implementation.....................................11

Section 4 DNP3 parameters...........................................................19

Recloser Protection and Control RER615 1

2 Recloser Protection and Control RER615

1.1 This manual

The communication protocol manual describes a communication protocol

1.2 Intended audience

This manual addresses the communication system engineer or system integrator

The system engineer or system integrator must have a basic knowledge of

Recloser Protection and Control RER615 3

1.3 Product documentation

1.3.1 Product documentation set

deinstallation & disposal

Product series- and product-specific manuals can be downloaded

1.3.2 Document revision history

Download the latest documents from the ABB Website

4 Recloser Protection and Control RER615

1.3.3 Related documentation

1.4 Symbols and conventions

The caution icon indicates important information or warning related

The information icon alerts the reader of important facts and

Although warning hazards are related to personal injury, it is necessary to

1.4.2 Document conventions

Recloser Protection and Control RER615 5

6 Recloser Protection and Control RER615

Section 2 DNP3 overview

2.1 DNP3 standard

2.1.1 Physical layer

Additional information on the DNP3 physical layer is available at

2.1.2 Data link layer

Data link functions:

• Performing message data link retransmissions.

Recloser Protection and Control RER615 7

• Controlling all aspects of the physical layer.

Data link responsibilities:

• Exchange of SDUs between peer DNP3 data links

Link-layer confirm usage is deprecated.

See the DNP technical bulletin TB1998-0402, section 3 for details

2.1.3 Transport pseudo-layer

• Exchange of SDUs between peer DNP3 transport pseudo layers

2.1.4 Application layer

8 Recloser Protection and Control RER615

2.1.5 Communication modes

This implementation of DNP3 is fully compliant with DNP3 Subset Definition

Recloser Protection and Control RER615 9

Section 3 Vendor-specific implementation

3.1 DNP3 link modes

3.1.1 DNP3 data objects

3.1.2 DNP3 serial link mode

DNP3 protocol ignores any parity setting in the COM settings

3.1.3 DNP3 TCP/IP mode

Recloser Protection and Control RER615 11

3.2 DNP3 point list

3.2.1 Binary input points

Table 1: Binary input points

Table 2: Default Class assignment for Binary Input points