Page 4
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.
Page 5
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.
Page 6
(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.
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 Documentation...................
Page 8
Table of contents 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..............
Section 1 1MRS757646 C Introduction Section 1 Introduction This manual The communication protocol manual describes a communication protocol supported by the protection relay. The manual concentrates on vendor-specific implementations. 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.
Document revision/date Product series version History A/2013-05-07 First release B/2015-12-11 2.0 FP1 Content updated to correspond to the product series version C/2019-06-19 2.0 FP1 Content updated Download the latest documents from the ABB Web site http://www.abb.com/substationautomation. 620 series Communication Protocol Manual...
1MRS757646 C Introduction 1.3.3 Related documentation 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. Symbols and conventions 1.4.1 Symbols The caution icon indicates important information or warning related to the concept discussed in the text.
Page 12
Section 1 1MRS757646 C Introduction 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. • This document assumes that the parameter setting visibility is "Advanced". 620 series Communication Protocol Manual...
Section 2 1MRS757646 C DNP3 overview Section 2 DNP3 overview 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.
Section 3 1MRS757646 C Vendor-specific implementation Section 3 Vendor-specific implementation 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.
Section 3 1MRS757646 C Vendor-specific implementation 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.
Section 3 1MRS757646 C Vendor-specific implementation 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.
Section 3 1MRS757646 C Vendor-specific implementation 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.
Section 3 1MRS757646 C Vendor-specific implementation • 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.
Section 3 1MRS757646 C Vendor-specific implementation 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.
Section 3 1MRS757646 C Vendor-specific implementation Use of TCP/IP connection keep-alive timeout only When the DNP3 link keep-alive mechanism is not used in TCP/IP case, the Ethernet stack TCP socket keep-alive mechanism is still in use. If there is a TCP socket keep- alive timeout, the protection relay closes the associated TCP socket connection and updates the DNP3 link status.
Section 3 1MRS757646 C Vendor-specific implementation The available DNP3 data objects are taken (mapped) entirely from the native IEC 61850 application data available in the protection relay. Mainly the IEC 61850 data that resides in IEC 61850 default dataset is included in the DNP3 object mapping. Objects within IEC 61850 datasets produce time tagged events.
Section 3 1MRS757646 C Vendor-specific implementation • The event buffering is handled by DNP3 object type, but a possible event overflow signal is in turn given from the DNP3 event class. If a class only contains a particular object type, the overflow occurs for that DNP3 object type. •...
Section 3 1MRS757646 C Vendor-specific implementation In case of making a DNP3 direct command to a SBO configured object, the desired behavior can be defined in the Communication Management tool. In case the direct control mode property is set to “Always allowed”, the DNP3 stack automatically performs the two needed commands to the native control object.
Section 3 1MRS757646 C Vendor-specific implementation Example 2 The legacy protocol default mappings are a selection of the most important signals produced by the IEC 61850-based protection relay 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.
Section 3 1MRS757646 C Vendor-specific implementation Binary inputs which are not of “Static-Only” type can be assigned to any DNP3 event class. Furthermore, it is possible to invert the signals if necessary, for example, generic input data. The default variation for all binary input values can be set with the Default Var Obj 01 parameter.
Section 3 1MRS757646 C Vendor-specific implementation Some DNP3 analog input points, such as CT/VT measurement values, support primary and secondary scaling. This selection can be done in PCM600 by selecting either "Primary value" or "Secondary value" for Representation. If the analog input object does not support primary and secondary scaling, the selection does nothing.
Section 3 1MRS757646 C Vendor-specific implementation resets and acknowledgements, can only be controlled using ON. However, there may also be single point objects that have two states, ON or OFF. Double point objects may be controlled using ON or OFF. 3.5.5.1 Control modes All DNP3 binary outputs support direct control at any time.
Section 3 1MRS757646 C Vendor-specific implementation The Analog Output Block DNP3 object group (41) is used for writing to a DNP3 analog output. Analog output can be also read from the protection relay, as object group 40. Reading an analog output returns the last written value to the object. Class events are generated for changed Analog Output values.
Section 3 1MRS757646 C Vendor-specific implementation The stored fault records are internally saved in indexes numbered 1...128. When the controlling station writes a value 1...128 to the “Select record” object, the entire set of fault record values belonging to that record is copied to the “Recorded” fault record DNP3 AI values.
Section 3 1MRS757646 C Vendor-specific implementation The latest record is stored at index (row) 1, and the oldest record at index 128. Records are stored in a FIFO buffer, that is, the oldest record is dropped out from index 128, and latest record always stored to index 1.
Section 4 1MRS757646 C DNP3 parameters Section 4 DNP3 parameters Parameter list The DNP3 parameters can be accessed with PCM600 or via the LHMI path Configuration/Communication/DNP3.0n. Some parameters are not visible in the “Basic” setting visibility mode. To view all parameters use “Advanced” setting visibility mode in Parameter Setting tool in PCM600 and LHMI.
Page 34
Section 4 1MRS757646 C DNP3 parameters Parameter Values (Range) Unit Step Default Description Time format 0=UTC 1=Local UTC or local. Coordinate with master. 1=Local CROB select timeout 1...65535 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...
Page 35
Section 4 1MRS757646 C DNP3 parameters Parameter Values (Range) Unit Step Default Description Default Var Obj 20 1=1:32bit Cnt 2=2:16bit Cnt 1=32 bit counter; 2=16 bit counter; 5=32 2=2:16bit Cnt bit counter without flag; 6=16 bit counter 5=5:32bit Cnt without flag. noflag 6=6:16bit Cnt noflag...
Section 4 1MRS757646 C DNP3 parameters Parameter Values (Range) Unit Step Default Description Default Var Obj 32 1=1:32bit AI evt 7=7:float AI 1=32 bit AI event; 2=16 bit AI event; 3=32 2=2:16bit AI evt evt&time bit AI event with time; 4=16 bit AI event 3=3:32bit AI with time;...
Section 5 1MRS757646 C Glossary Section 5 Glossary Start/pickup status 1. Application Configuration tool in PCM600 2. Trip status in IEC 61850 Analog input 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.
Page 38
Section 5 1MRS757646 C Glossary Transmission Control Protocol TCP/IP Transmission Control Protocol/Internet Protocol WHMI Web human-machine interface 620 series Communication Protocol Manual...