ABB REC615 and RER615 2.0, Grid Automation Protection and Control, DNP3 Communication Protocol Operating instructions

Brand: ABB

Model: REC615 and RER615 2.0, Grid Automation Protection and Control, DNP3 Communication Protocol

Type: Operating instructions

This manual is also suitable for

—

RELION® PRODUCT FAMILY

Grid Automation

REC615 and RER615

DNP3 Communication Protocol

Manual

Document ID: 1MRS758757

Issued: 2018-08-31

Revision: A

Product version: 2.0

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

standard 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

Documentation................................................................................... 7

Section 3 Vendor-specific implementation....................................... 9

Protocol server instances................................................................... 9

Connection to clients..................................................................... 9

Protocol server attachment to a client......................................... 10

Several identical client connections.............................................10

Protocol data mapping to server instances................................. 11

Link modes....................................................................................... 11

Serial link mode........................................................................... 11

TCP/IP mode............................................................................... 12

Communication setup.......................................................................12

Communication modes................................................................12

DNP3 layer acknowledgements, retries and timeouts.................12

Polled mode.................................................................................13

Unsolicited reporting mode..........................................................13

Communication supervision and diagnostics.............................. 14

Communication supervision status.........................................14

Diagnostic communication counters.......................................15

Data objects......................................................................................15

Readable data objects.................................................................15

Class events................................................................................ 16

Writable data objects................................................................... 17

Control relay output block parameters................................... 17

Direct operate and select before operate............................... 17

Command blockings...............................................................18

Accessing of non-protocol-mapped data..................................... 18

Table of contents

REC615 and RER615 1

Communication Protocol Manual

Standard data object types ..............................................................19

Binary inputs................................................................................19

Double point inputs......................................................................20

Analog inputs...............................................................................20

Counter objects........................................................................... 21

Binary outputs and control relay output block..............................21

Control modes........................................................................ 22

Accessing of physical outputs................................................ 22

Control feedback.................................................................... 22

Analog outputs.............................................................................22

Fault records.....................................................................................23

Ev-Upd type objects.................................................................... 23

Record type objects.....................................................................23

Time stamp for record type objects............................................. 24

Additional fault record implementation details............................. 24

Troubleshooting................................................................................25

Section 4 DNP3 parameters...........................................................27

Parameter list................................................................................... 27

Monitored data..................................................................................30

Section 5 Glossary......................................................................... 31

Table of contents

2 REC615 and RER615

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.

1MRS758757 A Section 1

Introduction

REC615 and 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

Communication protocol manual

IEC 61850 Engineering guide

Point list manual

GUID-7414985D-2433-46E4-B77B-CCE64F6FC8D0 V2 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 version History

A/2018-08-31 2.0 First release

Download the latest documents from the ABB Web site

http://www.abb.com/substationautomation.

Section 1 1MRS758757 A

Introduction

4 REC615 and RER615

Communication Protocol Manual

1.3.3 Related documentation

Name of the document Document ID

Modbus Communication Protocol Manual 1MRS758758

IEC 60870-5-101/104 Communication Protocol Manual 1MRS758756

IEC 61850 Engineering Guide 1MRS757809

Engineering Manual 1MRS757810

Installation Manual 1MRS757799

Operation Manual 1MRS758754

Technical Manual 1MRS758755

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.

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.

1MRS758757 A Section 1

Introduction

REC615 and 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 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 "On" and "Off".

• 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 1MRS758757 A

Introduction

6 REC615 and 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.2 Documentation

This implementation of DNP3 is fully compliant with DNP3 Subset Definition Level

2, and contains significant functionality beyond Subset Level 2.

1MRS758757 A Section 2

DNP3 overview

REC615 and RER615 7

Communication Protocol Manual

Section 3 Vendor-specific implementation

3.1 Protocol server instances

The word "client" refers to the protocol master. The protection relay is

referred to as "server" or a slave device.

The protection relay can communicate with several protocol clients simultaneously.

Furthermore, it is possible to configure the protection relay to provide different

protocol data and data outlook for different clients. A protocol server communication

entity which is configured to operate against a specific master or client is called an

instance.

There are three server instance scenarios.

1. One client - One protocol instance - One protocol mapping. The protection relay

is intended to operate toward one protocol client. The default protocol data

mapping or data outlook can be modified freely.

2. Several clients - Several protocol instances - One protocol mapping. The

protection relay is intended to operate toward several protocol clients. All the

clients should be able to access exactly similar data or similar data outlook. The

default protocol mapping or data outlook can be modified freely.

3. Several clients - Several protocol instances - Several protocol mappings. The

protection relay is intended to operate toward several protocol clients. Some or all

of the clients may want to access protocol data in a different manner. For this

purpose, several protocol mappings derived from the default protocol mapping

need to be prepared.

3.1.1 Connection to clients

In the protection relay, it is possible to activate up to five protocol server instances. A

function block represents the protocol on the protection relay’s application

configuration level. The block is named DNPLPRT1...5, depending on the instance in

use. For each connected client, an instance has to be activated by dragging the function

block to the configuration in the PCM600 Application Configuration tool.

DNPLPRT

STATUS

GUID-536D5DBA-B53F-475B-AD7D-25515895935C V1 EN

Figure 2: Function block

1MRS758757 A Section 3

Vendor-specific implementation

REC615 and RER615 9

Communication Protocol Manual

By default, instance 1 is always instantiated in the protection relay, but needs to be set

“On” to be activated. Since the protection relay’s native IEC 61850 data model

restricts client limit to five, the protection relay can have only five client connections

in total, regardless of the protocols to which the clients belong. This includes the MMS

clients and other communication protocol clients.

Protocol instances are identified with numbers 1...5. There are different and unique

setting and monitoring parameters for each instance in the HMI menu. Instance

numbers can be freely used. However, it is recommended to use the instances in the

numerical order. For example, instance 1 is to be used if there is only one client

connection and instances 1 and 2 when there are two clients.

3.1.2 Protocol server attachment to a client

After its activation, an instance should be attached to the intended client.

If the client is in a serial connection, the instance must be attached to the intended

serial port.

In case of a TCP client, the instance must be first attached to the physical Ethernet port.

If there are several TCP client connections, the protection relay must be able to

distinguish between the clients. There are two setting parameters in an instance.

• Client IP: When the client makes the TCP connection, its IP address is checked.

This instance is given to the client with this IP address. It is also possible to use

the address “0.0.0.0” if no client IP address is to be defined. In this case, the

client's IP address is ignored.

• TCP port: This parameter can be used in conjunction with the Client IP address

setting, thus allowing only a certain IP address at a specific TCP socket port

number.

3.1.3 Several identical client connections

If several clients access the same protocol data, the client connections must still be

kept apart. Also the number of each instance used for each client must be noted so that

if there are problems with the communication, the line diagnostic data for instances

follows the same instance number rule.

In case of sequential event data transaction and a TCP client connection, it is essential

that a reconnecting client is given back the same instance to which it was attached

before disconnecting. This way, the event reading resumes from the point where the

client left off, provided that no event overflow has occurred while the client was

absent. If multiple client connections are used, the distinguishing between different

client connections must be ensured by using the Client IP and TCP port parameters.

Section 3 1MRS758757 A

Vendor-specific implementation

10 REC615 and RER615

Communication Protocol Manual

3.1.4 Protocol data mapping to server instances

There are two different type of data mappings for the protocol. The mappings are

identified and numbered, starting from one. This number is not related to the protocol

instance number.

In PCM600, it is necessary to always define the mappings to be edited or viewed.

Each protocol instance has the setting parameter Mapping select, which defines the

protocol mappings to be used by this instance. Several protocol instances can use the

same mapping. By default, the Mapping select parameter for all the instances is set to

use the mapping number one.

Reboot the protection relay after changing the mapping number.

3.2 Link modes

DNP3 can be configured to operate in serial or Ethernet mode. The operation mode is

configured with the Port parameter.

3.2.1 Serial link mode

DNP3 serial can be assigned to a serial communication port in the protection relay.

Serial communication ports are named COM1...COMn, depending on how many

serial ports the protection relay 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. These characteristics

are automatically configured by the protection relay's software when a serial port is

taken into use by DNP3. However, some characteristics of the serial port must be set:

baud rate, serial mode (RS-232, RS-485 2/4-wire) and fiber mode. They are located in

the serial port settings.

• Configuration/Communication/COMn/Fiber mode

• Configuration/Communication/COMn/Serial mode

• Configuration/Communication/COMn/Baud rate

For the serial port parameter settings and hardware setup, see the

technical manual.

1MRS758757 A Section 3

Vendor-specific implementation

REC615 and RER615 11

Communication Protocol Manual

The COM port connection type, optical ST or EIA-485 connection,

star or loop topology, idle state (light on or light off) and the bias and

bus termination are selected with the COM port jumpers.

3.2.2 TCP/IP mode

DNP3 TCP/IP link mode is supported by the protection relay.

The protection relay listens for a connection from a DNP3 client on port specified by

the user. Default values for TCP port number range from 20000...20004 depending on

instance number. A different port can be selected with the TCP Port parameter.

DNP3 TCP/IP link mode and UDP broadcast are supported by the protection relay.

UDP broadcast requires that there is an active TCP connection by the client.

Documentation on DNP3 TCP/IP communication is available on

www.dnp.org.

3.3 Communication setup

3.3.1 Communication modes

DNP3 communication can be set up in two alternative modes.

• Polled mode, called also “polled report by exception”. In this mode the DNP3

client always initiates the transaction with a read or write request to the DNP3

server. The server must reply with a response message.

• Unsolicited mode, called also “Unsolicited reporting mode”. In this mode the

DNP3 server may spontaneously send changed class events to the client. The

client can yet make additional read or write requests to the server.

By default, DNP3 operates in polled mode. Unsolicited reporting mode can be

activated with the UR mode parameter.

3.3.2 DNP3 layer acknowledgements, retries and timeouts

It is possible to set up acknowledgements on both DNP3 link layer and application

layer. The settings should be equal on both the client and the server sides of the

communication. The timeouts must be set so that the other side has enough time to

prepare a positive acknowledgement. If an acknowledgement is received after the

configured timeout, it is discarded.

Confirmations, retries and timeouts can be configured via parameters.

Section 3 1MRS758757 A

Vendor-specific implementation

12 REC615 and RER615

Communication Protocol Manual

• Configuration/Communication/DNP3.0/DNP3.0n/Data link confirm

• Configuration/Communication/DNP3.0/DNP3.0n/Data link confirm TO

• Configuration/Communication/DNP3.0/DNP3.0n/Data link retries

• Configuration/Communication/DNP3.0/DNP3.0n/App layer confirm

• Configuration/Communication/DNP3.0/DNP3.0n/App confirm TO

DNP3 link layer acknowledgements should not be used in TCP/IP link mode, since the

DNP3 message transport (link) is then encapsulated and secured by the Ethernet

protocol.

Link layer acknowledgements are seldom used in serial mode. The application layer

acknowledgements also cover the link layer acknowledgements. This means that if the

application message was successfully delivered, then the link layer must also have

been successful. Furthermore, it is easier to perform a whole application layer

retransmission rather than link layer retransmissions. Otherwise the application layer

timeout must be prepared to cover all the timeouts and retransmissions performed by

the link layer.

3.3.3 Polled mode

In the polled mode the client station initiates a connection and polls periodically for

static data (Class 0), and events (Class 1/2/3) from the server. Data must be polled

frequently enough, to prevent event overflow. If event overflow takes place, this is

indicated in the IIN bits in the response message. This means that events have been

lost.

3.3.4 Unsolicited reporting mode

Unsolicited mode can be enabled in the relay by the UR mode parameter. The

operating principle is that the server sends event data spontaneously to the client.

When the unsolicited mode has been activated by the setting parameter, the client

station must activate UR reporting by Enable unsolicited Application function (20).

After activation the server begins sending Class 1/2/3 events spontaneously.

Client must acknowledge unsolicited events reported by the server to ensure the

communication is fully operative. If the server does not receive acknowledgement in

time, defined by the UR TO and App confirm TO parameters, it does a count of resends

defined by the parameter UR retries. If the client station does not respond

acknowledgement during the count of retries, the server goes to offline mode. This

means that spontaneous events are not sent for a period of time. The length of this

period is defined by the parameter UR offline interval, (default 15 minutes). If it is not

wanted that the server goes to offline mode, limitless retries can be achieved by setting

the UR retries to “65535”.

Class event reporting can be buffered in the unsolicited mode by setting the

parameters UR Class x Min event and UR Class x TO. The event parameter UR Class

x Min defines how many events must be buffered in the device before unsolicited

report is sent out. The UR Class x TO parameter in turn defines the minimum waiting

1MRS758757 A Section 3

Vendor-specific implementation

REC615 and RER615 13

Communication Protocol Manual

time the device buffers events before sending them out, after occurrence of an event.

These parameters are useful for controlling the flow of events from the device and

combining them into bigger reports.

Legacy master UR provides compatibility to some older DNP3 clients. When set to

disabled, the server follows the DNP3 standard, sending its first unsolicited message

after a connection has been established following relay reboot. The client is expected

to send the Enable/Disable Unsolicited messages command to the relay. When Legacy

master UR is enabled, the relay does not send the initial unsolicited message.

Unsolicited responses are sent without the need of the Enable Unsolicited command.

The client still needs to open a connection for the server to start sending unsolicited

messages.

Unsolicited reporting mode is not recommended in half-duplex (RS-485 2-wire mode

or optical ST mode) serial bus due to possibility of collisions in the serial bus.

Especially in a system where event reporting is frequent, collisions can cause failed

DNP3 requests/responses and thus retransmissions. If unsolicited mode is used,

application level confirmations should be enabled to ensure that transmission is

successful. In half-duplex serial bus, polled mode is recommended.

3.3.5 Communication supervision and diagnostics

3.3.5.1 Communication supervision status

The DNP3 protocol provides a link to a keep-alive mechanism which can be used in

both Ethernet (TCP/IP) and serial communication modes. When the client has

successfully established connection to the protection relay, keep-alive messages are

sent periodically by the client or protection relay, depending on which one has a lower

keep-alive interval setting. Keep-alive timer is also restarted by any normal DNP3

frame, so keep-alive messages are only being transmitted after a longer idle time

between frames. In the protection relay, the keep-alive timeout can be set with the Link

keep-alive (seconds) parameter.

Default value “0” means that no keep-alive messages are sent by the protection relay.

Keep-alive requests sent by the client are still responded to. If a keep-alive message is

not responded to, the connection is considered broken. In case of TCP/IP connection

the protection relay closes the associated TCP socket connection, and a new

connection must be initiated by the client.

The DNP3 link status (True/False) is updated in the Monitoring data Status, which

also can be also used in Application Configuration tool in PCM600 for additional

logic connection, for example, to a LED. DNP3 link status exists separately for each

DNP3 protocol instance. True (value 1) means that the connection is active. False

(value 0) means the connection has timed out. The status can be found via

Monitoring/Communication/DNP3.0/DNP3.0n/Status.

On Application Configuration tool level, the DNP3 protocol instance is represented

by a function block DNPLPRTn, where n is the protocol instance number 1…5.

Section 3 1MRS758757 A

Vendor-specific implementation

14 REC615 and RER615

Communication Protocol Manual

Page is loading ...

ABB REC615 and RER615 2.0, Grid Automation Protection and Control, DNP3 Communication Protocol Operating instructions

Brand: ABB

Model: REC615 and RER615 2.0, Grid Automation Protection and Control, DNP3 Communication Protocol

Type: Operating instructions

This manual is also suitable for

Download PDF

report

ABB REC615 and RER615 2.0, Grid Automation Protection and Control, DNP3 Communication Protocol Operating instructions

This manual is also suitable for

ABB REC615 and RER615 2.0, Grid Automation Protection and Control, DNP3 Communication Protocol Operating instructions

Related papers

Other documents