Hitachi Relion 670 Series User manual

Relion 670 SERIES
DNP, 670 series
Version 2.2
Communication protocol manual

Document ID: 1MRK511391-UUS
Issued: June 2023
Revision: L
Product version: 2.2
© 2017 - 2023 Hitachi Energy. All rights reserved

Copyright
This document and parts thereof must not be reproduced or copied without written permission from
Hitachi Energy, and the contents thereof must not be imparted to a third party, nor used for any
unauthorized purpose.
The software and hardware described in this document is furnished under a license and may be used or
disclosed only in accordance with the terms of such license.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(https://www.openssl.org/). This product includes cryptographic software written/developed by: Eric
Young ([email protected]) and Tim Hudson ([email protected]).
Trademarks
ABB is a registered trademark of ABB Asea Brown Boveri Ltd. Manufactured by/for a Hitachi Energy
company. 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 Hitachi Energy representative.

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 document has been carefully checked by Hitachi Energy, 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 Hitachi Energy 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 Hitachi Energy 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 and ANSI C37.90. The DNP protocol implementation in
the IED conforms to "DNP3 Intelligent Electronic Device (IED) Certification Procedure Subset Level 2",
available at www.dnp.org.

Table of contents
Section 1 Introduction.........................................................................................................3
1.1 This manual.................................................................................................................................3
1.2 Intended audience.......................................................................................................................3
1.3 Product documentation............................................................................................................... 3
1.3.1 Product documentation set........................................................................................................3
1.3.2 Document revision history......................................................................................................... 4
1.3.3 Related documents................................................................................................................... 5
1.4 Document symbols and conventions...........................................................................................7
1.4.1 Symbols.....................................................................................................................................7
1.4.2 Document conventions..............................................................................................................7
Section 2 DNP3 overview....................................................................................................9
2.1 DNP3 standard............................................................................................................................9
2.2 Documentation...........................................................................................................................11
Section 3 Vendor-specific implementation..................................................................... 13
3.1 DNP3 link modes.......................................................................................................................13
3.1.1 DNP3 TCP/IP mode................................................................................................................ 13
3.2 DNP3 UDP-only mode.............................................................................................................. 14
3.3 Internal indications.................................................................................................................... 14
3.4 Event reporting.......................................................................................................................... 15
3.4.1 Event buffers........................................................................................................................... 15
3.5 Command handling................................................................................................................... 15
3.5.1 Automation bits........................................................................................................................15
3.5.2 Apparatus control.................................................................................................................... 16
3.5.3 Binary output status points and control relay output blocks.................................................... 16
3.6 Time synchronization.................................................................................................................17
3.7 Analog inputs.............................................................................................................................17
3.7.1 Analog data scaling................................................................................................................. 17
3.7.2 Analog input signal scaling for DNP3 master presentation..................................................... 18
3.8 DNP3 points.............................................................................................................................. 20
3.8.1 Point configuration...................................................................................................................20
3.8.2 Class assignment.................................................................................................................... 21
3.9 Fault record............................................................................................................................... 21
Section 4 DNP3 parameters..............................................................................................23
4.1 Parameter descriptions............................................................................................................. 23
4.1.1 Serial optical and RS485 communication channel settings.....................................................26
4.2 Parameter list............................................................................................................................ 27
1MRK511391-UUS Rev. L Table of contents
DNP, 670 series 1
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

4.2.1 Parameter list for optical and RS485 communication channel................................................27
4.2.2 Parameter list for TCP/IP........................................................................................................ 32
Section 5 Glossary............................................................................................................ 43
5.1 Glossary.................................................................................................................................... 43
Table of contents 1MRK511391-UUS Rev. L
2DNP, 670 series
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

Section 1 Introduction
1.1 This manual GUID-AB423A30-13C2-46AF-B7FE-A73BB425EB5F v21
The communication protocol manual describes the communication protocols supported by the IED. The
manual concentrates on the vendor-specific implementations.
1.2 Intended audience GUID-C9B8127F-5748-4BEA-9E4F-CC762FE28A3A v11
This manual is intended for the communication system engineer or system integrator responsible for pre-
engineering and engineering the 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.
1.3 Product documentation
1.3.1 Product documentation set GUID-3AA69EA6-F1D8-47C6-A8E6-562F29C67172 v16
IEC07000220-4-en.vsd
Planning & purchase
Engineering
Installing
Commissioning
Operation
Maintenance
Decommissioning
Deinstalling & disposal
Application manual
Operation manual
Installation manual
Engineering manual
Communication
protocol manual
Cyber security
deployment guideline
Technical manual
Commissioning manual
IEC07000220 V4 EN-US
Figure 1: The intended use of manuals throughout the product lifecycle
1MRK511391-UUS Rev. L Section 1
Introduction
DNP, 670 series 3
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

The engineering manual contains instructions on how to engineer the IEDs using the various tools
available within the PCM600 software. The manual provides instructions on how to set up a PCM600
project and insert IEDs to the project structure. The manual also recommends a sequence for the
engineering of protection and control functions, as well as communication engineering for IEC 61850.
The installation manual contains instructions on how to install the IED. The manual provides procedures
for mechanical and electrical installation. The chapters are organized in the chronological order in which
the IED should be installed.
The commissioning manual contains instructions on how to commission the IED. The manual can also be
used by system engineers and maintenance personnel for assistance during the testing phase. The
manual provides procedures for the checking of external circuitry and energizing the IED, parameter
setting and configuration as well as verifying settings by secondary injection. The manual describes the
process of testing an IED in a substation which is not in service. The chapters are organized in the
chronological order in which the IED should be commissioned. The relevant procedures may be followed
also during the service and maintenance activities.
The operation manual contains instructions on how to operate the IED once it has been commissioned.
The manual provides instructions for the monitoring, controlling and setting of the IED. The manual also
describes how to identify disturbances and how to view calculated and measured power grid data to
determine the cause of a fault.
The application manual contains application descriptions and setting guidelines sorted per function. The
manual can be used to find out when and for what purpose a typical protection function can be used. The
manual can also provide assistance for calculating settings.
The technical manual contains operation principle descriptions, and lists function blocks, logic diagrams,
input and output signals, setting parameters and technical data, sorted per function. The manual can be
used as a technical reference during the engineering phase, installation and commissioning phase, and
during normal service.
The communication protocol manual describes the communication protocols supported by the IED. The
manual concentrates on the vendor-specific implementations.
The cyber security deployment guideline describes the process for handling cyber security when
communicating with the IED. Certification, Authorization with role based access control, and product
engineering for cyber security related events are described and sorted by function. The guideline can be
used as a technical reference during the engineering phase, installation and commissioning phase, and
during normal service.
1.3.2 Document revision history GUID-34B323E4-1319-4D42-80CE-29B0F2D36E2C v8
Document
revision
Date Product version History
- 2017–05 2.2.0 First release for product version 2.2
A 2017–10 2.2.1 Ethernet ports with RJ45 connector added.
B 2018–03 2.2.1 Document enhancements and corrections
C 2018–06 2.2.2 Technical data updated for PSM. Case dimensions
updated.
Table continues on next page
Section 1 1MRK511391-UUS Rev. L
Introduction
4DNP, 670 series
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

Document
revision
Date Product version History
D 2018–11 2.2.3 Functions CHMMHAI, VHMMHAI, DELVSPVC,
DELISPVC and DELSPVC added. Updates/
enhancements made to ZMFPDIS, ZMFCPDIS,
CCRBRF, REALCOMP, PTRSTHR and FNKEYMDx.
Ordering section updated.
E 2019-05 2.2.3 PTP enhancements and corrections
F Document not released
G Document not released
H Document not released
J 2020-09 2.2.4 Minor document enhancements and corrections
K 2021-06 2.2.5 Minor document enhancements and corrections
L 2023-062.2.6 Minor document enhancements and corrections
1.3.3 Related documents GUID-94E8A5CA-BE1B-45AF-81E7-5A41D34EE112 v10
Documents related to REB670 Document numbers
Application manual ANSI: 1MRK505370-UUS
Commissioning manual ANSI: 1MRK505372-UUS
Product guide 1MRK505373-BEN
Technical manual ANSI: 1MRK505371-UUS
Type test certificate ANSI: 1MRK505373-TUS
Documents related to REC670 Document numbers
Application manual ANSI: 1MRK511401-UUS
Commissioning manual ANSI: 1MRK511403-UUS
Product guide 1MRK511404-BEN
Technical manual ANSI: 1MRK511402-UUS
Type test certificate ANSI: 1MRK511404-TUS
Documents related to RED670 Document numbers
Application manual ANSI: 1MRK505376-UUS
Commissioning manual ANSI: 1MRK505378-UUS
Product guide 1MRK505379-BEN
Technical manual ANSI: 1MRK505377-UUS
Type test certificate ANSI: 1MRK505379-TUS
1MRK511391-UUS Rev. L Section 1
Introduction
DNP, 670 series 5
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

Documents related to REG670 Document numbers
Application manual ANSI: 1MRK502071-UUS
Commissioning manual ANSI: 1MRK502073-UUS
Product guide 1MRK502074-BEN
Technical manual ANSI: 1MRK502072-UUS
Type test certificate ANSI: 1MRK502074-TUS
Documents related to REL670 Document numbers
Application manual ANSI: 1MRK506369-UUS
Commissioning manual ANSI: 1MRK506371-UUS
Product guide 1MRK506372-BEN
Technical manual ANSI: 1MRK506370-UUS
Type test certificate ANSI: 1MRK506372-TUS
Documents related to RET670 Document numbers
Application manual ANSI: 1MRK504163-UUS
Commissioning manual ANSI: 1MRK504165-UUS
Product guide 1MRK504166-BEN
Technical manual ANSI: 1MRK504164-UUS
Type test certificate ANSI: 1MRK504166-TUS
Documents related to RES670 Document numbers
Application manual ANSI: 1MRK511407-UUS
Commissioning manual ANSI: 1MRK511409-UUS
Product guide 1MRK511410-BEN
Technical manual ANSI: 1MRK511408-UUS
Type test certificate ANSI: 1MRK511410-TUS
Documents related to RER670 Document numbers
Application manual
Commissioning manual
Product guide 1MRK506378-BEN
Technical manual
Type test certificate
Section 1 1MRK511391-UUS Rev. L
Introduction
6DNP, 670 series
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

1.4 Document symbols and conventions
1.4.1 Symbols GUID-2945B229-DAB0-4F15-8A0E-B9CF0C2C7B15 v13
The electrical warning icon indicates the presence of a hazard which could result in electrical
shock.
The warning icon indicates the presence of a hazard which could result in personal injury.
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. It is important that the user fully complies with all warning and
cautionary notices.
1.4.2 Document conventions GUID-96DFAB1A-98FE-4B26-8E90-F7CEB14B1AB6 v9
• Abbreviations and acronyms in this manual are spelled out in the glossary. The glossary also
contains definitions of important terms.
• Parameter names are shown in italics.
For example, the function can be enabled and disabled with the Operation setting.
• Each function block symbol shows the available input/output signal.
• the character ^ in front of an input/output signal name indicates that the signal name may be
customized using the PCM600 software.
• the character * after an input signal name indicates that the signal must be connected to
another function block in the application configuration to achieve a valid application
configuration.
• Dimensions are provided both in inches and millimeters. If it is not specifically mentioned then the
dimension is in millimeters.
1MRK511391-UUS Rev. L Section 1
Introduction
DNP, 670 series 7
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

8

Section 2 DNP3 overview
GUID-9CDAE3C1-07F5-493F-A1F1-196C2F48DB16 v2
DNP3 is a communication protocol used between components in process automation systems. Its main
use is in utilities such as electric and water companies. Usage in other industries is not common,
although technically possible. Specifically, it was developed to facilitate communications between various
types of data acquisition and control equipment. It plays a crucial role in SCADA systems, where it is
used by SCADA master stations (aka Control Centers), RTUs, and IEDs.
GUID-F3F7289C-3344-492F-8779-D63CBF6B469A V1 EN-US
Figure 2: DNP3 communication schematic representation
1SCADA master station / control center
2 External control points
3 Communication links (radio, microwave, spread-spectrum, twisted-pair, fiber-optics, dial-up, leased line)
4 Remote substation (station computer and IED)
2.1 DNP3 standard AMU0600507 v15
The DNP3 protocol was developed by Westronic based on the early versions of the IEC 60870-5
standard telecontrol protocol specifications. DNP is now governed by IEEE Std 1815-2012 IEEE
Standard for Electric Power Systems Communications - Distributed Network Protocol (DNP3)
www.dnp.org.
The protocol is based on the EPA, a simplified model of the ISO/OSI model. It specifies the data link
layer, the application layer and a transport pseudo-layer. 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 the mentioned transport pseudo-layer. As a minimum, this transport
layer implements message assembly and disassembly services.
Physical layer
Even though the standard does not specify the physical layer, it does however specify how to operate in
a networked environment and also suggests how to avoid collisions between simultaneously sending
devices.
Many implementations use serial communication based on RS-232, RS-485 or even fiber optics.
1MRK511391-UUS Rev. L Section 2
DNP3 overview
DNP, 670 series 9
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

DNP3 can also be used over packet-oriented networks such as TCP/IP and UDP in which, for example,
Ethernet may be used. In this case DNP3 can be said to be tunneled over TCP/IP or UDP.
Additional information on the DNP3 physical layer is available at the DNP Users Group at
www.dnp.org.
Data link layer
The DNP3 data link layer is designed to operate with asynchronous or synchronous bit serial physical
layers. Fully balanced transmission procedures were adopted to support spontaneous transmissions
from remotes.
Data link functions include:
• Performing message data link retransmissions.
• Packing user data into the defined frame format includes CRC and transmitting the data to the
physical layer.
• Unpacking the data link frame received from the physical layer into user data, checking and
removing CRC.
• Controlling 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 Service data units (SDUs) between peer DNP3 data links
• Error notification to data link user
• Sequencing of SDUs
• SDU delivery quality.
Link-layer confirm usage is not recommended and the implementation is optional. The IED does not
request data-link layer confirmations for TCP/IP communication.
See the DNP technical bulletin TB1998-0402, section 3 for details at www.dnp.org.
Transport pseudo-layer
To support advanced RTU functions and messages exceeding the maximum data link frame length, a
transport pseudo-layer which implements message assembly and disassembly services was adopted.
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
Section 2 1MRK511391-UUS Rev. L
DNP3 overview
10 DNP, 670 series
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

Application layer
The application layer is responsible for performing operations on data objects defined by the device or on
the device itself. These operations 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, reading actual values and clearing the
counters. DNP3 uses the term point to identify an entity, and these entities can be categorized into point-
types, such as analogs or binaries. Points are addressed by giving them an index number and an object
is a formatted representation of data from a point. These objects can be assigned to classes in order to
organize events and current values into categories. The DNP3 protocol defines four data classes to
organize data reporting.
Communication modes
The IED supports four DNP3 communication modes.
• Quiescent operation
• Unsolicited report-by-exception operation
• Polled report-by-exception operation
• Polled static operation
2.2 Documentation GUID-7966A3BB-DC5A-47CF-B78D-D8BF1373C308 v1
This implementation of DNP3 is fully compliant with DNP3 Subset Definition Level 2, and contains
significant functionality beyond Subset Level 2. See the device profile for further information.
1MRK511391-UUS Rev. L Section 2
DNP3 overview
DNP, 670 series 11
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

12

Section 3 Vendor-specific implementation
3.1 DNP3 link modes
3.1.1 DNP3 TCP/IP mode GUID-6257BE0D-01CA-44C7-92A6-A4B20BF79DBB v4
DNP3 TCP/IP link mode is supported by the IED. This implementation supports up to four different
masters communicating simultaneously with the IED. The IED is a listening endpoint implementation and
listens for connections from DNP3 masters on a configurable port, TCPIPLisPort. The IED does not
connect to masters, meaning that it is not a dual-endpoint implementation.
It is possible to use both the connection establishment method based on the master IP address, and the
connection establishment method based on the port number. The identification and association of the
master is based both on the IP address of the master and the port number it connects to. It is essential to
make sure that the parameters TCPIPLisPort, MasterIP-Addr, MasterIPNetMask, SlaveAddress and
MasterAddress uniquely identifies one master from the other masters.
The above is an important concept to grasp during commissioning so that no conflicts occur. Therefore, it
is strongly recommended not to change the MasterIPNetMask parameter to anything else than its default
255.255.255.255 unless necessary. The parameter should not be mixed up with the subnet mask of the
IP configuration. The MasterIPNetMask can be used to allow to accept connections from masters that do
have dynamic IP addresses within a known range.
For example, if a master changes its IP address dynamically in the range of 10.10.10.1 and
10.10.10.254, the MasterIPNetMask could be set to 255.255.255.0 to allow for connections from this
range. If two masters share this dynamic range or share the same IP address, it is necessary to separate
them by having them connect to separate ports, for example, 20000 and 20001 respectively.
Also, SlaveAddress and MasterAddress must be correctly configured for each master. Otherwise, the
previously accepted connection is closed upon the reception of the first DNP3 message.
The IED supports the requirements of the standard to receive UDP broadcast messages on the ports
configured by UDPPortAccData.
As a default, the IED sends a keep-alive message in every 10 seconds according to the value of the
tKeepAliveT parameter. The time can be changed, and setting it to zero means that no keep-alive
messages are sent. It is important to know the hazards of disabling the keep-alive, and it is not
recommended to do so unless necessary. If the keep-alive messages are unwanted, it is better to
increase the value of tKeepAliveT so that it exceeds the master's poll rate.
If a master crashes or the communication links are broken and the master restarts, the TCP/IP makes
the IED believe that the connection still exists. Since the IED conforms to the recommendations of the
standard not to accept new connections when a connection already exists to the particular master, the
master will never be allowed to connect again. Another parameter that concerns the TCP/IP connection
status is tBrokenConTout. It determines how long a session is active after a TCP/IP connection has been
broken. After the time period, the session becomes inactive and events are not stored. If the parameter is
set to 0, events are stored until the sequential buffers overflow. Note that if the parameter is set to zero,
all events from start-up until the sequential buffers overflow are saved even though no connection would
have been established.
Further documentation concerning DNP3 TCP/IP communication is available in the IP Networking
document Volume 7, from www.dnp.org.
1MRK511391-UUS Rev. L Section 3
Vendor-specific implementation
DNP, 670 series 13
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved

3.2 DNP3 UDP-only mode GUID-2605E868-4438-49C6-A307-1D18F8022F1F v1
DNP3 UDP-only mode is supported by the IED. When operating in UDP-only mode the parameters
UDPPortInitNUL and UDPPortCliMast must be configured.
If the parameter UDPPortCliMast is set to 0 the port number and master IP address is taken from the
previous request. It is important to have in mind when using this functionality that the parameters
MasterIP-Addr and MasterIPNetMsk need to be set to values that match the network setup.
The system will only consider IP-address included in the range defined by MasterIP-Addr and the
MasterIPNetMsk as valid addresses to use then when responding.
3.3 Internal indications GUID-2CDB2CDE-28F5-4E07-8BB7-A3537888058D v3
Internal indications give information on certain status and error conditions within the outstation. They
contain 2 octets of data and are found in the application layer on an outstation response.
Each octet has 8 bit fields numbered 0 through 7 where bit 0 is the least significant bit. A code is used to
reference or specify a particular bit:
IINx.b - where x is a 1 for the first octet and x is a 2 for the second. b identifies the bit number.
Thus, IIN2.0 refers to the first bit in the second octet.
See the DNP3 Specification Volume 3 Application Layer (Section 5 Detailed IIN Bit Descriptions) for
more detailed descriptions of IIN bits.
Table 1: Default class assignment for internal indications
Bit index Descriptions and conditions Writable
IIN1.0 All stations – set after a broadcast message (any message using a destination
address of 0xfff0 or above) has been received. Does not indicate an error condition
No
IIN1.1 Class 1 event data available. Can be set at any time and does not indicate an error
condition.
No
IIN1.2 Class 2 event data available. Can be set at any time and does not indicate an error
condition
No
IIN1.3 Class 3 event data available. Can be set at any time and does not indicate an error
condition
No
IIN1.4 Time synchronization required from master. Can be set at any time and does not
indicate an error condition. This bit is set according to the PST setting
“tSyncTimeout” when time synchronization is via DNP3.
No
IIN1.5 Local mode. Set if some points are uncontrollable via DNP3. No
IIN1.6 Device trouble. Set if the IED has detected device problems. This bit is set when the
IED’s “Internal Fail” flag is set.
No
IIN1.7 Device restart. Set only under specific conditions. Does not indicate an error
condition
Yes
IIN2.0 Function unknown. Generally means that the function code (octet 2 of the request
header) cannot be processed.
No
IIN2.1 Object unknown. Generally means that the function code could be processed but the
object group / variation could not be processed
No
Table continues on next page
Section 3 1MRK511391-UUS Rev. L
Vendor-specific implementation
14 DNP, 670 series
Communication protocol manual
© 2017 - 2023 Hitachi Energy. All rights reserved