DNP3 Abb Recloser
DNP3 Abb Recloser
PROJECT NO.:
August 3, 2006
PTMV
ABB Inc.
200 Regency Forest Drive, Suite 110,
Cary, North Carolina 27518-8695 USA
Telephone: (919) 856-3084
Fax: (919) 856-3068
Aug/3/2006 ii
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
The purpose of this document is to describe the specific implementation of the Distributed Network Protocol
(DNP), Version 3.0 on the ABB Power Control Device (PCD) and Switch Control Device (SCD). This
document, in conjunction with the DNP 3.0 Basic 4 Document Set, and the DNP Subset Definitions
Document, provides complete information on how to communicate with the PCD/SCD via the DNP 3.0
protocol.
iii Aug/3/2006
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
1.9 PCD2000 Release V2.20, Loop control functions added 06/11/2001 V.Gharpure D. Uy N. Simons
1.10 PCD Releases V2.40 & V2.50 03/21/2002 J. Vellore V. Gharpure C. LaPlace
1.11 PCD Release V2.60 10/18/2002 J. Vellore V. Gharpure K. Scherrer
1.20 PCD Release V2.70, TMW DNP Library Upgrade 2/3/2003 J. Vellore V. Gharpure K. Scherrer
1.30 PCD Release V3.00, Add 5 BI and 3 BO points 9/1/2004 J. Vellore V. Gharpure V.R.Ramanan
1.40 PCD Release V3.60, Added 2 BO points 8/3/2006 J. Vellore V. Gharpure V.R.Ramanan
Aug/3/2006 iv
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Table of Contents
1 INTRODUCTION............................................................................................................................................. 1
2 CONFIGURATION .......................................................................................................................................... 3
2.1 END-USER CONFIGURATION.......................................................................................................................................................................................................................................................3
2.2 SETTINGS.......................................................................................................................................................................................................................................................................................................12
3 DNP V3.0 DEVICE PROFILE....................................................................................................................... 13
v Aug/3/2006
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Aug/3/2006 vi
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
1 Introduction
The purpose of this document is to describe the specific implementation of the Distributed
Network Protocol (DNP), Version 3.0 on the ABB Power Control Device (PCD) and Switch
Control Device (SCD). This document, in conjunction with the DNP 3.0 Basic 4 Document Set,
and the DNP Subset Definitions Document, provides complete information on how to
communicate with the PCD/SCD via the DNP 3.0 protocol.
This implementation of DNP 3.0 is fully compliant with DNP 3.0 Subset Definition Level 2, with
additional features described in this document.
Historically, the PCD is a descendent of the ABB DPU-2000. Therefore, the implementation of
DNP 3.0 in the PCD is intended to be a superset, and essentially compatible with that of DNP
3.0 in the DPU-2000. In the field, this means that replacing a DPU-2000 with a PCD should
require minimal, if any, configuration or application changes to the master computer. To aid in
this matter, this document also provides a description of the DNP 3.0 implementation differences
between the PCD and the DPU-2000.
Page 1 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 2 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
2 Configuration
2.1 End-User Configuration
Through the front panel interface of the PCD, various operating parameters may be changed by
the end-user. The parameters that directly or indirectly configure the operation of DNP 3.0 are
listed in the table below and described in subsequent sections. The parameters are stored in non-
volatile memory and are therefore preserved even when the PCD is powered-down.
Default See
Label Description Range Units [out of range values] Section
Unit Address* network address 0 - 65535 (decimal) address 1 2.1.1
0 - FFFF (hex)
RP Baud* serial baud rate 300, 1200, 2400, 4800, baud 9600 2.1.2
9600, 19200
RP Frame* parity, data bits, stop bits N, 8, 1 E, 8, 1 O, 8, 1 parity, bits, N, 8, 1 2.1.3
N, 8, 2, E, 7, 1 O, 7, 1 bits
N, 7, 2.
RP Protocol* protocol selection ASCII (Modbus) ASCII 2.1.4
RTU (Modbus)
DNP3.0
Parameter 1 inter-character delay 1-255 10 50 (500 milliseconds) 2.1.5
milliseconds [0 ¼ disabled (not used)]
Parameter 2 data link confirmation timeout 1-255 100 30 (3 seconds) 2.1.6
milliseconds [0 ¼ 100 milliseconds]
Parameter 3 data link retries 0-255 retries 2 2.1.7
Parameter 4 transmission Delay 0-255 milliseconds 0 2.1.8
Parameter 5 class 0 scan group mask 0-255 (scan group 0-7) bit mask 255 (all groups enabled) 2.1.9
Parameter 6 class 0 scan group mask 0-255 (scan group 8-15) bit mask 255 (all groups enabled) 2.1.9
Parameter 7 class 0 scan group mask 0-255 (scan group 16-23) bit mask 255 (all groups enabled) 2.1.9
Parameter 8 class 0 scan group mask 0-255 (scan group 24-31) bit mask 255 (all groups enabled) 2.1.9
Parameter 9 application layer fragment size 1-8 frames 8 (2048 bytes) 2.1.10
[0 ¼ 1 frame, Greater
than 8 ¼ 8 frames]
Parameter 10 application layer confirmation 1-255 seconds 5 2.1.11
timeout [0 ¼ 1 second]
Parameter 11* unsolicited response 0-255 seconds 15 2.1.12
notification delay
Parameter 12* destination address 0-255 address 3 2.1.13
Parameter 13* minimum number of Class 1 0-255 events 10 2.1.14
events for unsolicited response
Parameter 14* minimum number of Class 2 0-255 events 25 2.1.15
events for unsolicited response
Parameter 15* minimum number of Class 3 0-255 events 50 2.1.16
events for unsolicited response
Parameter 16 write time interval 0-255 (0 = never) minutes 30 2.1.17
Parameter 17 data link confirmations 0 (never) 0 (never) 2.1.18
1 (only multi-frame) [Greater than 2 ¼ 2
2 (always) (always)]
Parameter 18 Unsolicited Offline Interval 1-255 minutes 15 2.1.19
Parameter 19 Link address size (octets) 1 or 2 1 2.1.20
IEC870
Parameter 20 ASDU common address size 1 or 2 2 2.1.21
(octets) IEC870
Parameter 21 Default Variation for Object 01 1- 4 4 2.1.22
& 02
DNP3.0
Parameter 22 Default Variation for Object 30 1-4 2 2.1.23
DNP3.0
Parameter 23 Default Variation for Object 32 1-4 2 2.1.24
DNP3.0
Parameter 24 Protocol Auto-Detect Feature Disabled Disabled 2.1.25
Enable Enabled
Page 3 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
2.1.1 Unit Address – This parameter specifies the “network” address of the PCD with respect
to all other devices communicating on the same physical network as the PCD. The value
is specified in both decimal and hexadecimal formats on the front panel, and may range
from between 0 and 65535, inclusive. Changing this value will cause a “warm” restart of
the DNP 3.0 communication process.
2.1.2 RP Baud – The serial baud rate for DNP communications. It can be set to one of: 300,
1200, 2400, 4800, 9600, or 19200. Changing this value will cause a “warm” restart of the
DNP 3.0 communication process.
2.1.3 RP Frame – The description of the parity, number of data bits, and number of stop bits.
The possible values are “N, 8, 1,” “E, 8, 1,” “O, 8, 1.” “N, 8, 2,” “E, 7, 1,” “O, 7, 1,” and
“N, 7, 2.” Typically, most DNP 3.0 devices use “N, 8, 1” - no parity, 8 data bits, and 1
stop bit. Changing this value will cause a “warm” restart of the DNP 3.0 communication
process.
2.1.4 RP Protocol – This parameter specifies the communication protocol selection for Rear
Port 1. It has three possible values: ASCII (for ASCII mode ModBus), RTU (for RTU
mode ModBus), and DNP 3.0 (the protocol this document describes).
2.1.5 Parameter 1 (Inter-character delay) – This value specifies the maximum time between
characters received within a data frame. It is specified in tens of milliseconds (hundredths
of a second), and may range from 1 to 255, inclusive. If this value is exceeded during a
frame read, then the frame will be deemed corrupted, and discarded. When another
character is finally received, it will be considered part of the next frame and tested as such.
Therefore, if this value is set too large, and if a corruption occurs but is not detected
because it is shorter than this parameter, portions of the next frame may be initially
considered part of the current frame. This additional corruption will eventually be
detected (using, at the lowest level, CRCs), and both frames will be discarded. However,
if this parameter is set smaller than the maximum expected inter-character delays
generated by the master computer, frames may be erroneously discarded. An out-of-
range value of 0 will disable the use of inter-character delay.
2.1.6 Parameter 2 (Data Link Confirmation Timeout) – This value specifies the data link layer
confirmation time-out. It is specified in hundreds of milliseconds (tenths of a second),
and may range from 1 to 255, inclusive. It is valid only when the PCD is acting as a data
Feb/3/2003 Page 4 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
link primary; i.e., when the PCD is transmitting a data frame with a request for a data link
layer confirmation from the master computer, or the PCD is transmitting a reset link
frame. Specifically, if a confirmation is not received or if the link is not reset within the
time specified by this parameter, then a data link error is indicated. If data link layer
retries are enabled (see Parameter 3 below), and if the maximum number of retries have
not been attempted, then another data link layer retry will be attempted; i.e., the frame will
be retransmitted. An out-of-range value of 0 will set the parameter to 1 (100
milliseconds).
2.1.7 Parameter 3 (Data Link Retries) – This value specifies the maximum number of data
link layer retries. Its range is from 0 to 255 inclusive. This is used when the PCD is
transmitting a data frame with a request for a data link layer confirmation from the master
computer, or when the PCD is transmitting a reset link frame. In these two cases, if the
time-out specified by Parameter 2 (described above) has elapsed without receiving a
confirmation or without detecting the link reset, the data frame will be re-transmitted the
number of times specified by this parameter. The default value of zero indicates that no
retries will be attempted.
2.1.8 Parameter 4 (Transmission Delay) – This value specifies the minimum time after a data
frame is received before a data frame is transmitted. It is specified in milliseconds, and
may range from 0 to 255, inclusive. This parameter is intended for physical network
environments using a multi-drop configuration such as RS485. In these environments,
many active receivers are allowed, but only one transmitter can be active, or else a
“collision” will occur and data transmission will be corrupted. This parameter allows
master computers, or other computers on the same physical network, time to turn off
their transmitter after transmitting a message. A similar configuration parameter should
exist on the other computers to allow the PCD time to turn off its transmitter after it has
finished transmitting. In environments where this functionality is not needed, this
parameter may be set to zero.
2.1.9 Parameters 5, 6, 7, and 8 (Class 0 Scan Group Masks) – These parameters specify the
data points that are returned by the PCD when requested by the master computer to
return Class 0, 1, 2, or 3 data. All of the data points in the PCD have been organized into
32 “Scan Type” groups, each group having a corresponding bit in these parameters. If
scan groups are to be returned by class scans, their respective bits in these parameters
must be turned on (set to 1). Since the front panel interface takes input in decimal, Table 2
(below) provides an aide for setting the parameters, along with the object type to which
the Scan Type Groups apply: To enable multiple groups within the same byte, the
decimal values must be added together.
Page 5 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
2.1.10 Parameter 9 (Application Layer Fragment Size) – This parameter is used to specify the
maximum size of a application layer response. It is specified in number of data link
frames and may range from 1 to 8. (Since, for the PCD, the data-link frames are 255
bytes, this signifies a range of maximum application fragment size of 256 to 2048 bytes.)
In a technical bulletin recently published by the DNP Users Group Technical Committee,
it was recommended that the application fragment size be reduced to the largest amount
that will fit in a single data link layer frame (the value of this parameter would be 1). As
part of the same recommendation, it was recommended that data link confirmations not
be used, and that application layer confirmations be used instead. The reasoning behind
this recommendation is that application layer confirmations are more robust and
informative, and that data link layer confirmations are redundant and useless if all
application layer fragments use only a single data link frame. However, if a response
message cannot fit in a single application layer fragment, the DNP implementation in the
PCD will respond with a multi-fragment response, and not all master computer DNP
implementations correctly parse multi-fragment responses. Therefore, if the master
computer cannot handle multi-fragment responses, this parameter must be set large
enough to hold the largest response message. For the PCD, an example large response
message would be the response to a Class 0 scan when all scan type groups are enabled.
Feb/3/2003 Page 6 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
An out-of-range value of 0 will set the parameter to 1 (1 frame). A value greater than 8
will set the parameter to 8 (8 frames).
2.1.11 Parameter 10 (Application Layer Confirmation Timeout) – This parameter specifies the
application layer confirmation time-out.. It is specified in seconds, and may range from 1
to 255, inclusive. Because application layer retries are not performed, this parameter is
used primarily when unsolicited messages are enabled. Specifically, unsolicited messages
will not be transmitted while waiting for an application layer confirmation requested by an
earlier transmission (either solicited or unsolicited). Also, while waiting for an application
layer confirmation requested by an earlier unsolicited response, no READ requests from
the master computer will be honored. This is per the DNP 3.0 Subset Definitions,
Section 4.9.1, and is intended to prevent the same event data being sent to the master
twice – once in the unsolicited response, and once in the READ response. However, all
other requests by the master received while waiting for an application layer confirmation
(i.e., non-READ requests while waiting for a confirmation of an unsolicited response, and
all requests while waiting for a confirmation of a solicited response) will be honored and
processed. An out-of-range value of 0 will set the parameter to 1.
2.1.13 Parameter 12 (Destination Address) – This parameter specifies the destination address
of the master computer. DNP queries from a device with this address will be responded
to and unsolicited responses will be directed to this address. It may range from 0 to 255.
Changing this value will cause a “warm” restart of the DNP 3.0 communication process.
2.1.14 Parameter 13 (Minimum Number of Class 1 Events for Unsolicited Response) – This
parameter specifies one condition under which unsolicited responses may be transmitted.
Specifically, an unsolicited response will be generated if unsolicited responses are enabled
by Mode Parameter 5 (Unsolicited Mode), if the PCD is not waiting for an application
layer confirmation of an earlier response, and if the number of class 1 events detected and
not yet reported or confirmed equals or exceeds this value. See Section 2.1.31 for more
details on the generation of unsolicited responses. This value may range from 0 to 255,
inclusive. Changing this value will cause a “warm” restart of the DNP 3.0 communication
process.
2.1.15 Parameter 14 (Minimum Number of Class 2 Events for Unsolicited Response) – This
parameter specifies one condition under which unsolicited responses may be transmitted.
Specifically, an unsolicited response will be generated if unsolicited responses are enabled
by Mode Parameter 5 (Unsolicited Mode), if the PCD is not waiting for an application
layer confirmation of an earlier response, and if the number of class 2 events detected and
not yet reported or confirmed equals or exceeds this value. See Section 2.1.31 for more
details on the generation of unsolicited responses. This value may range from 0 to 255,
inclusive. Changing this value will cause a “warm” restart of the DNP 3.0 communication
process.
Page 7 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
2.1.16 Parameter 15 (Minimum Number of Class 3 Events for Unsolicited Response) – This
parameter specifies one condition under which unsolicited responses may be transmitted.
Specifically, an unsolicited response will be generated if unsolicited responses are enabled
by Mode Parameter 5 (Unsolicited Mode), if the PCD is not waiting for an application
layer confirmation of an earlier response, and if the number of class 3 events detected and
not yet reported or confirmed equals or exceeds this value. See Section 2.1.31 for more
details on the generation of unsolicited responses. This value may range from 0 to 255,
inclusive. Changing this value will cause a “warm” restart of the DNP 3.0 communication
process.
2.1.17 Parameter 16 (Write Time Interval) – This parameter specifies how often the PCD will
request that the master computer execute a write time function to reset the date and time
of the PCD. The value is specified in minutes, and may range from 0 to 255 (4 hours, 15
minutes), inclusive. If 0, the PCD will never request that the master computer execute a
write-time function. The purpose of this functionality is to ensure synchronous time
between the master and all slave devices. The value of this parameter should represent
the minimum amount of time in which the clocks of the PCD and master computer
could become out-of-synchronization.
2.1.18 Parameter 17 (Data Link Confirmations) – This parameter has three possible values:
If data link confirmations are used, then the PCD will request a confirmation from the
master computer when transmitting data link frames. If a confirmation is not received
within the timeout specified by Parameter 2 (Data Link Confirmation Timeout), then an
error is indicated. If Parameter 3 (Data Link Retries) allows data link retries, and if the
maximum number of retries have not been attempted, then the PCD will attempt to
retransmit the data frame. Value 1 for this parameter is included for cases when the
functionality of confirmations is desired for each frame, but application layer confirmations
can only cover a whole fragment. An out-of-range value greater than 2 will set the
parameter equal to 2 (always).
2.1.19 Parameters 18 (Unsolicited Offline Interval) – This parameter specifies the offline
interval for unsolicited response retries. If the PCD does not receive an application layer
confirmation, for an unsolicited message, within the timeout period specified in
Parameter 10, the PCD will re-transmit the unsolicited message the number of times
specified in Parameter 25. After the number of retries has been exhausted, the PCD will
not re-transmit unsolicited messages for the interval specified in this parameter before
attempting to retry again.
2.1.20 Parameter 19 (IEC870 Link address size) - This parameter applies to the IEC 870
protocol implementation of the PCD and is not applicable to DNP implementation.
Feb/3/2003 Page 8 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
2.1.21 Parameter 20 (IEC870 ASDU common address size) - This parameter applies to the
IEC 870 protocol implementation of the PCD and is not applicable to DNP
implementation.
2.1.22 Parameter 21 (Default variation for Object 01 and Object 02) - This parameter specifies
the default variation number for Object numbers 01 and 02. The possible values are 1, 2,
3 or 4. If this parameter is set to 1, both Objects 01 and 02 have default variations of 1. If
this parameter is set to 2, both Objects 01 and 02 have default variations of 2. If this
parameter is set to 3, Object 01 has default variation of 2 and Object 02 has default
variation of 1. If this parameter is set to 4, Object 01 has default variation of 1 and Object
02 has default variation of 2. Default variations are responded when variation 0 is
requested and/or in class 0, 1, 2, or 3 scans.
2.1.23 Parameter 22 (Default variation for Object 30) - This parameter specifies the default
variation number for Object number 30. The possible values are 1, 2, 3 or 4. Default
variations are responded when variation 0 is requested and/or in class 0, 1, 2, or 3 scans.
2.1.24 Parameter 23 (Default variation for Object 32) - This parameter specifies the default
variation number for Object number 32. The possible values are 1, 2, 3 or 4. Default
variations are responded when variation 0 is requested and/or in class 0, 1, 2, or 3 scans.
2.1.25 Parameter 24 (Protocol Autodetect feature) - This parameter specifies if the protocol
autodetect feature is enabled or disabled. When this parameter is set to enabled the PCD
will interpret both Modbus and DNP commands when configured for DNP protocol
communications.
2.1.26 Parameter 25 (Unsolcited Maximum Retries) - This parameter specifies the maximum
number of unsolicited message retries if no application layer confirmation is received. If
this parameter is set to 255, the PCD will continue to retry indefinitely.
2.1.27 Mode Parameter 1 – This parameter is not currently used by the DNP 3.0
implementation.
2.1.28 Mode Parameter 2 (Application Layer Confirmations) – This parameter affects how the
PCD requests application layer confirmations when transmitting messages to the master
computer. It has these possible values:
Page 9 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
when the master computer requires flow control in order to provide time
to process the data within PCD transmitted fragments.
2.1.29 Mode Parameter 3 – This parameter is not currently used by the DNP 3.0
implementation.
2.1.30 Mode Parameter 4 – This parameter is not currently used by the DNP 3.0
implementation.
2.1.31 Mode Parameter 5 (Unsolicited Mode) – This parameter indicates whether unsolicited
responses can be transmitted by the PCD. Unsolicited messages contain only event data,
and will always request application layer confirms. If the value of this parameter is
“Enable”, unsolicited responses can be transmitted; if “Disable”, unsolicited responses
cannot be transmitted. The destination of the unsolicited responses is specified by
Parameter 12 (Destination Address). Even if this parameter allows unsolicited responses
to be transmitted, the master computer can still enable and disable unsolicited responses
for specific event classes through use of function codes 20 and 21 (decimal). If
unsolicited responses are allowed by this parameter, and if the PCD is not waiting for an
application layer confirmation of an earlier response, then an unsolicited response will be
generated when any one of the following conditions are true:
1. Any number of events for classes enabled by the master through function code 20
(decimal) have been detected and not yet reported or confirmed, and the time
specified by Parameter 11 (Unsolicited Response Notification Delay) (Section 2.1.12)
has elapsed
2. Class 1 events have been enabled by the master through function code 20 (decimal),
and the number of class 1 events detected and not yet reported or confirmed equals
or exceeds the value specified by Parameter 13 (Minimum Number of Class 1 Events
for Unsolicited Response) (Section 2.1.14).
3. Class 2 events have been enabled by the master through function code 20 (decimal),
and the number of class 2 events detected and not yet reported or confirmed equals
or exceeds the value specified by Parameter 14 (Minimum Number of Class 2 Events
for Unsolicited Response) (Section 2.1.15).
4. Class 3 events have been enabled by the master through function code 20 (decimal),
and the number of class 3 events detected and not yet reported or confirmed equals
or exceeds the value specified by Parameter 15 (Minimum Number of Class 3 Events
for Unsolicited Response) (Section 2.1.16).
If these conditions are constantly being met, the frequency of unsolicited messages is
limited by the confirmation, by the master, of previous unsolicited responses. Or, if the
master is not confirming the unsolicited responses, the conditions will be, by definition,
constantly met. In this unconfirmed case, the frequency of the unsolicited messages will
be limited by Parameter 10 (Application Layer Confirmation Timeout), Section 2.1.11.
Changing this value will cause a “warm” restart of the DNP 3.0 communication process.
2.1.32 Mode Parameter 6 (Legacy DNP master unsolicited mode support) – This parameter
controls the behavior of the unsolicited response in the PCD. In accordance with the
Feb/3/2003 Page 10 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
DNP 3.0 standard the PCD must receive an “Enable Unsolicited Response” message
from the master station in order for unsolicited messages to begin. This message also
contains the class data to be returned in the unsolicited messages. Mode parameter 6 may
be enabled in order to accommodate legacy DNP masters that do not adhere to the DNP
standards for initialization of unsolicited response (GE-Harris D20). By enabling this
parameter, the PCD will begin transmitting unsolicited messages in all classes without
receiving the “Enable Unsolicited Response” message from the master. Application layer
confirmation is still required from the master upon receipt of the unsolicited messages.
Note that this parameter must be disabled in order to meet the requirements for
certification of the DNP V3.00 IED under certification procedure 1.00 adopted by the
DNP users group. Operation of the PCD with this parameter enabled will result in a
failure of the certification test.
2.1.33 Mode Parameters 7 and 8 – These parameters are spares, and are not currently used by
the DNP 3.0 implementation.
Page 11 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
2.2 Settings
This section describes settings that are set in software, and are not configurable by the end-user.
2.2.1 Select/Operate Arm Timeout – If a operate function is not received after a select
function within the time specified by this parameter, it will not be honored. This value is
set, in software, to 10 seconds.
Feb/3/2003 Page 12 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
DNP V3.0
DEVICE PROFILE DOCUMENT
(Also see the DNP 3.0 Implementation Table in Section 4, beginning on page 17.)
Vendor Name: ABB, Inc.
Device Name: Power Control Device (PCD)
Highest DNP Level Supported: Device Function:
For static (non-change-event) object requests, request qualifier codes 00 and 01 (start-stop),
07 and 08 (limited quantity), and 17 and 28 (index) are supported in addition to request
qualifier code 06 (no range). Static object requests sent with qualifiers 00, 01, 06, 07, or 08,
will be responded with qualifiers 00 or 01. Static object requests sent with qualifiers 17 or 28
will be responded with qualifiers 17 or 28. For change-event object requests, qualifiers 17 or
28 are always responded.
16-bit and 32-bit Analog Change Events with Time may be requested.
The read function code for Object 50 (Time and Date), variation 1, is supported.
Analog Input Deadbands, Object 34, variations 1 through 3, are supported.
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
None None
Fixed Configurable
Configurable from 0 to 255
See Section 2.1.7, Page 5.
Page 13 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
DNP V3.0
DEVICE PROFILE DOCUMENT
(Also see the DNP 3.0 Implementation Table in Section 4, beginning on page 17.)
Requires Data Link Layer Confirmation:
Never
Always
Sometimes
Configurable as: Never, Only for multi-frame messages, or Always.
See Section 2.1.18, Page 8
Requires Application Layer Confirmation:
Never
Always
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Sometimes
Configurable as: “Only when reporting event data”, or “When reporting event data or
multi-fragment messages.” See Section 2.1.28, Page 9
Timeouts while waiting for:
Feb/3/2003 Page 14 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
DNP V3.0
DEVICE PROFILE DOCUMENT
(Also see the DNP 3.0 Implementation Table in Section 4, beginning on page 17.)
Sends/Executes Control Operations:
Never Never
Only time-tagged Binary Input Change With Time
Only non-time tagged Binary Input Change With Relative Time
Configurable to send both, one or the Configurable
other
Never Never
Configurable See Section 2.1.31, When Device Restarts
Page 10 When Status Flags Change
Only certain objects
Sometimes (attach explanation) No other options are permitted.
ENABLE/DISABLE UNSOLICITED
Function codes supported
Default Counter Object/Variation: Counters Roll Over at:
Page 15 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 16 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
REQUEST RESPONSE
OBJECT
(PCD will parse) (PCD will respond with)
Object Variation Function Qualifier Function Qualifier
Description
Number Number Codes (dec) Codes (hex) Codes (dec) Codes (hex)
1 0 Binary Input – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range)
07, 08 (limited qty)
17, 28 (index)
1 1 Binary Input 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
(default) 06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
1 2 Binary Input with Status 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
2 0 Binary Input Change – Any Variation 1 (read) 06 (no range)
07, 08 (limited qty)
2 1 Binary Input Change without Time 1 (read) 06 (no range) 129 (response) 17, 28 (index)
07, 08 (limited qty) 130(unsol. resp)
2 2 Binary Input Change with Time 1 (read) 06 (no range) 129 (response) 17, 28 (index)
(default) 07, 08 (limited qty) 130(unsol. resp)
2 3 Binary Input Change with Relative Time 1 (read) 06 (no range)
(parse only) 07, 08 (limited qty)
10 0 Binary Output Status – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range)
07, 08 (limited qty)
17, 28 (index)
10 1 Binary Output 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
10 2 Binary Output Status 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
(default) 06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
12 1 Control Relay Output Block 3 (select) 00, 01 (start-stop) 129 (response) echo of request
4 (operate) 07, 08 (limited qty)
5 (direct op) 17, 28 (index)
6 (dir. op, noack)
20 0 Binary Counter - Any Variation 1 (read) 00, 01 (start-stop)
7 (freeze) 06 (no range)
8 (freeze noack) 07, 08 (limited qty)
9 (freeze clear) 17, 28 (index)
10(frz. cl. noack)
Page 17 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
REQUEST RESPONSE
OBJECT
(PCD will parse) (PCD will respond with)
Object Variation Function Qualifier Function Qualifier
Description
Number Number Codes (dec) Codes (hex) Codes (dec) Codes (hex)
20 2 16-Bit Binary Counter (with Flag) 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
7 (freeze) 06 (no range) 17, 28 (index)
8 (freeze noack) 07, 08 (limited qty)
9 (freeze clear) 17, 28 (index)
10(frz. cl. noack)
20 6 16-Bit Binary Counter without Flag 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
(default) 7 (freeze) 06 (no range) 17, 28 (index)
8 (freeze noack) 07, 08 (limited qty)
9 (freeze clear) 17, 28 (index)
10(frz. cl. noack)
21 0 Frozen Counter - Any Variation 1 (read) 00, 01 (start-stop)
06 (no range)
07, 08 (limited qty)
17, 28 (index)
21 2 16-Bit Frozen Counter (with Flag) 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
21 10 16-Bit Frozen Counter without Flag 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
(default) 06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
22 0 Counter Change Event - Any Variation 1 (read) 06 (no range)
07, 08 (limited qty)
22 2 16-Bit Counter Change Event without 1 (read) 06 (no range) 129 (response) 17, 28 (index)
Time 07,08(limited qty) 130(unsol. resp)
22 6 16-Bit Counter Change Event With 1 (read) 06 (no range) 129 (response) 17, 28 (index)
(default) Time 07,08(limited qty) 130(unsol. resp)
23 0 Frozen Counter Event - Any Variation 1 (read) 06 (no range)
07, 08 (limited qty)
23 2 16-Bit Frozen Counter Event 1 (read) 06 (no range) 129 (response) 17, 28 (index)
07,08(limited qty) 130(unsol. resp)
23 6 16-Bit Frozen Counter Event With Time 1 (read) 06 (no range) 129 (response) 17, 28 (index)
(default) 07,08(limited qty) 130(unsol. resp)
Feb/3/2003 Page 18 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
REQUEST RESPONSE
OBJECT
(PCD will parse) (PCD will respond with)
Object Variation Function Qualifier Function Qualifier
Description
Number Number Codes (dec) Codes (hex) Codes (dec) Codes (hex)
32 3 32-Bit Analog Change Event with Time 1 (read) 06 (no range) 129 (response) 17, 28 (index
07, 08 (limited qty) 130(unsol. resp)
32 4 16-Bit Analog Change Event with Time 1 (read) 06 (no range) 129 (response) 17, 28 (index
07, 08 (limited qty) 130(unsol. resp)
34 0 Analog Input Deadband – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range)
07, 08 (limited qty)
17, 28 (index)
34 1 16-Bit Analog Input Deadband 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
(default) 06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
34 1 16-Bit Analog Input Deadband 2 (write) 00, 01 (start-stop)
07, 08 (limited qty)
17, 28 (index)
34 2 32-Bit Analog Input Deadband 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
34 2 32-Bit Analog Input Deadband 2 (write) 00, 01 (start-stop)
07, 08 (limited qty)
17, 28 (index)
40 0 Analog Output Status – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range)
07, 08 (limited qty)
17, 28 (index)
40 2 16-Bit Analog Output Status 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
(default) 06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
50 0 Time and Date 1 (read) 00, 01 (start-stop)
2 (write) 06 (no range)
07, 08 (limited qty)
17, 28 (index)
50 1 Time and Date 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
(default) 2 (write) 06 (no range) 17, 28 (index)
07, 08 (limited qty)
17, 28 (index)
52 2 Time Delay Fine 129 (response) 00, 01 (start-stop)
17, 28 (index)
60 0 Class 0, 1, 2, and 3 Data 1,20,21 (read) 06 (no range)
60 1 Class 0 Data 1 (read) 06 (no range)
60 2 Class 1 Data 1,20,21 (read) 06 (no range)
07, 08 (limited qty)
60 3 Class 2 Data 1,20,21 (read) 06 (no range)
07, 08 (limited qty)
60 4 Class 3 Data 1,20,21 (read) 06 (no range)
07, 08 (limited qty)
80 1 Internal Indications 2 (write) 00 (start-stop)
(index must =7)
No Object (function code only) 13 (code restart)
No Object (function code only) 23 (delay meas)
(Default variations are responded when variation 0 is requested and/or in class 0, 1, 2, or 3 scans.)
Page 19 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 20 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
The DNP Assignable Classes feature of the PCD allows the user to make class assignments
to the binary input points. By default, all binary input points are assigned CLASS 1. If a class
1 event poll is performed all binary input points that have changed state since the last event
poll will be reported. The class assignment for a given binary input point can be changed to
CLASS 2, 3 or NO CLASS by setting the appropriate value in the associated modbus
register. Refer to the "Modbus Protocol Implementation for the PCD" manual for details on
changing the class assignments.
Assignable Points
The DNP Assignable Point indexes feature of the PCD allows the user to reassign the point
indexes of binary input points. By default, the point indexes are as shown below. To change
the point index of a given binary input point the appropriate modbus register has to be
modified to the desired value. Refer to the "Modbus Protocol Implementation for the PCD"
manual for details on changing the class assignments. NOTE: The assigned point index may
not exceed the maximum number of binary input points.
The DNP Assignable Classes feature is available in PCD firmware release 2.40 and above, and
DNP Assignable Point Indexes feature is available in PCD firmware release 2.50 and above.
The scan period for binary inputs is set to 5 seconds by default. The event mode is SEQUENCE
OF EVENTS.
The PCD has a mechanism for taking snapshots of the status of several binary inputs. These
snapshots are taken more frequently that the scan period listed above. Events are generated at the
end of the current scan interval for the points that changed status. The default point index of
binary input points that are NOT included in the snapshots are:
The status of these points are checked at the scan interval listed above.
Page 21 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 22 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Page 23 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 24 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Page 25 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 26 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Page 27 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
1The Change Event Class Assignment may be changed off-line through configuration software.
2Type 1 Alarm - One minute delay to alarm indication for analog threshold alarms. Alarm is self-
resetting once the alarm conditions clear.
3Type 2 Alarm - Immediate indication once event counter reaches the threshold for digital inputs.
Alarm must be reset to clear. Immediate indication on next event occurrence unless counter is
reset.
4Sticky Point – Reset Alarm command is required to clear these points. Local settings change is
indicated when a save on exit is done through the front panel. Power was Cycled is indicated any
time power is restored to the unit.
5Pointwill return Off-Line status. It is not currently supported but is reserved for future
implementation.
6Point will return Off-Line status unless device is configured for per pole (Single Phase)
operation.
7Valid only if the device is an PCD.
8Valid only if the device is an SCD.
Feb/3/2003 Page 28 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
5.2 Binary Output Status Points and Control Relay Output Blocks
The following table lists both the Binary Output Status Points (Object 10) and the Control Relay
Output Blocks (Object 12). The status points are read-only, and represent the current status of
their corresponding control relay output block. For Trip and Close operations, points 32/33 and
34/35 can be thought to be organized in pairs: a trip command applying to an even numbered
point, and a close command applying to the following odd numbered point. The pairing
organization allows a close command applied to an even point, to actually be applied to the
following odd point.
Page 29 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 30 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Page 31 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
1Pulseon-time is fixed to the breaker trip fail time in the configuration settings; variable pulse on-
time widths specified in the control relay output block will be ignored, not rejected.
2UPS test is initiated by setting this binary output. Reading this binary output will always result in
a zero. The result of the test is available through object 30 point 90, UPS test delta voltage.
3Point will return Off-Line status unless device is configured for per pole (Single Phase)
operation.
4Valid only if the device is an PCD. Otherwise, will return Off-Line status.
5Valid only if the device is an SCD. Otherwise, will return Off-Line status.
Feb/3/2003 Page 32 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
5.3 Counters
The following table lists both Binary Counters (Object 20) and Frozen Counters (Object 21).
When a freeze function is performed on a Binary Counter point, the frozen value is available in
the corresponding Frozen Counter point.
PCD now supports change event reporting of Binary Counters (Object 22) and Frozen Counters
(Object 23). These events are reported as Class 3 events by default.
The scan period for binary counters and frozen counters is set to 5 seconds by default. The event
mode is MOST RECENT for binary counters and SEQUENCE OF EVENTS for frozen
counters.
Binary Counters
Static (Steady-State) Object Number: 20
Change Event Object Number: 22
Request Function Codes supported: 1 (read), 7 (freeze), 8 (freeze noack)
9 (freeze and clear), 10 (freeze and clear, noack)
Static Variation reported when variation 0 requested: 6 (16-Bit Binary Counter without Flag)
Change Event Variation reported when variation 0 requested: 2 (16-bit Counter Event w/o Time)
Frozen Counters
Static (Steady-State) Object Number: 21
Change Event Object Number: 23
Request Function Codes supported: 1 (read)
Static Variation reported when variation 0 requested: 10 (16-Bit Frozen Binary without Flag)
Change Event Variation reported when variation 0 requested: 2 (16-bit Frozen Counter Event w/o
Time)
Frozen Counter
Point Binary Counter (20)
Name/Description (21)
Index Scan Type Group
Scan Type Group
0 KSI Sum A Counter 14 15
1 KSI Sum B Counter 14 15
2 KSI Sum C Counter 14 15
1
3 Over Current Trip Counter 14 15
1
4 Breaker Operations Counter 14 15
1
5 Reclose Counter 1 (any operation) 14 15
st 1
6 1 Stage Reclose Counter 14 15
nd 1
7 2 Stage Reclose Counter 14 15
rd 1
8 3 Stage Reclose Counter 14 15
th 1
9 4 Stage Reclose Counter 14 15
1
10 Reclose Counter 2 14 15
1
11 Phase A, Overcurrent Trip Counter 14 15
1
12 Phase B, Overcurrent Trip Counter 14 15
1
13 Phase C, Overcurrent Trip Counter 14 15
1
14 Neutral, Overcurrent Trip Counter 14 15
1
15 Phase A, Operations Counter 14 15
1
16 Phase A, Reclose Counter 1 14 15
1
17 Phase A, Reclose Counter 2 14 15
1
18 Phase A, Stage 1 Reclose Counter 14 15
Page 33 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
1
19 Phase A, Stage 2 Reclose Counter 14 15
1
20 Phase A, Stage 3 Reclose Counter 14 15
1
21 Phase A, Stage 4 Reclose Counter 14 15
1
22 Phase B, Operations Counter 14 15
1
23 Phase B, Reclose Counter 1 14 15
1
24 Phase B, Reclose Counter 2 14 15
1
25 Phase B, Stage 1 Reclose Counter 14 15
1
26 Phase B, Stage 2 Reclose Counter 14 15
1
27 Phase B, Stage 3 Reclose Counter 14 15
1
28 Phase B, Stage 4 Reclose Counter 14 15
1
29 Phase C, Operations Counter 14 15
1
30 Phase C, Reclose Counter 1 14 15
1
31 Phase C, Reclose Counter 2 14 15
1
32 Phase C, Stage 1 Reclose Counter 14 15
1
33 Phase C, Stage 2 Reclose Counter 14 15
1
34 Phase C, Stage 3 Reclose Counter 14 15
1
35 Phase C, Stage 4 Reclose Counter 14 15
2
36 Total Faults Counter 27 27
2
37 Phase A Faults Counter 27 27
2
38 Phase B Faults Counter 27 27
2
39 Phase C Faults Counter 27 27
2
40 Neutral Faults Counter 27 27
2
41 Switch 1 Operations Counter 27 27
2
42 Switch 2 Operations Counter 27 27
2
43 Switch 3 Operations Counter 27 27
2
44 Switch 4 Operations Counter 27 27
1Valid only if the device is an PCD. Otherwise, will return Off-Line status.
2Valid only if the device is an SCD. Otherwise, will return Off-Line status.
Feb/3/2003 Page 34 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Assignable Classes
The DNP Assignable Classes feature of the PCD allows the user to make class assignments
to the analog input points. By default, all analog input points are assigned CLASS 2. If a class
2 event poll is performed all analog input points that have changed beyond the programmed
threshold since the last event poll will be reported. The class assignment for a given analog
input point can be changed to CLASS 1, 3 or NO CLASS by setting the appropriate value in
the associated modbus register. Refer to the "Modbus Protocol Implementation for the
PCD" manual for details on changing the class assignments.
Assignable Points
The DNP Assignable Point indexes feature of the PCD allows the user to reassign the point
indexes of analog input points. By default, the point indexes are as shown below. To change
the point index of a given analog input point the appropriate modbus register has to be
modified to the desired value. Refer to the "Modbus Protocol Implementation for the PCD"
manual for details on changing the class assignments. NOTE: The assigned point index may
not exceed the maximum number of analog input points.
The DNP Assignable Classes feature is available in PCD firmware release 2.40 and above, and
DNP Assignable Point Indexes feature is available in PCD firmware release 2.50 and above.
Analog Deadbands
PCD now supports setting of analog deadbands using Object 34. These values are NOT stored in
non-volatile memory and hence will have to be re-sent to the device after a power cycle. The
deadband thresholds may be set as a percentage of the last reported value or a count offset from
the last reported value.
To set the deadband for a point as a percentage of the last reported value, use positive integers for
values while performing a write function using Object 34. For example, to set the deadband of
point 8 to 10%, perform a write function of Object 34 with the value for point 8 set to 10.
To set the deadband for a point as a count offset from the last reported value, use negative integers
for values while performing a write function using Object 34. For example, to set the deadband of
point 9 to 4, perform a write function of Object 34 with the value for point 9 set to -4.
The scan period for analog inputs is set to 5 seconds by default. The event mode is MOST
RECENT.
Page 35 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Analog Inputs
Static (Steady-State) Object Number: 30
Change Event Object Number: 32
Request Function Codes supported: 1 (read)
Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input)
Change Event Variation reported when variation 0 requested: 2 (Analog Change Event w/o
Time)
3
Point User Name/Description Default User
Default
Index Assign Change Assign
Dead-
-ed Scaling Event -ed Scan
band
Point (representation Assigned Class Type
(see
Index of 32767) Class (1,2,3 Group
note
(1,2,3 or or
above)
none) none)
0 Ia (Load Current) 32767 Amps 2 16 10
1 Ib 32767 Amps 2 16 10
2 Ic 32767 Amps 2 16 10
3 In 32767 Amps 2 16 10
4 Van (Mag) 32767 Volts 2 16 10
5 Vbn (Mag) 32767 Volts 2 16 10
6 Vcn (Mag) 32767 Volts 2 16 10
7 Vab (Mag) 32767 Volts 2 16 10
8 Vbc (Mag) 32767 Volts 2 16 10
9 Vca (Mag) 32767 Volts 2 16 10
10 KW3 32767 KWatts 2 16 10
11 KWan 32767 KWatts 2 16 10
12 KWbn 32767 KWatts 2 16 10
13 KWcn 32767 KWatts 2 16 10
14 KVAR3 32767 KVAR 2 17 10
15 KVARan 32767 KVAR 2 17 10
16 KVARbn 32767 KVAR 2 17 10
17 KVARcn 32767 KVAR 2 17 10
18 KWHr3 32767 KWatt- 2 17 10
Hour
19 KVARHr3 32767 KVAR- 2 17 10
Hour
20 KWHra 32767 KWatt- 2 17 10
Hour
21 KWHrb 32767 KWatt- 2 17 10
Hour
22 KWHrc 32767 KWatt- 2 17 10
Hour
23 KVARHra 32767 KVAR- 2 17 10
Hour
24 KVARHrb 32767 KVAR- 2 17 10
Hour
25 KVARHrc 32767 KVAR- 2 17 10
Hour
26 Iavg 32767 Amps 2 18 10
27 Ia Angle 32767 degrees 2 18 10
28 Ib Angle 32767 degrees 2 18 10
29 Ic Angle 32767 degrees 2 18 10
30 In Angle 32767 degrees 2 18 10
Feb/3/2003 Page 36 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Analog Inputs
Static (Steady-State) Object Number: 30
Change Event Object Number: 32
Request Function Codes supported: 1 (read)
Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input)
Change Event Variation reported when variation 0 requested: 2 (Analog Change Event w/o
Time)
3
Point User Name/Description Default User
Default
Index Assign Change Assign
Dead-
-ed Scaling Event -ed Scan
band
Point (representation Assigned Class Type
(see
Index of 32767) Class (1,2,3 Group
note
(1,2,3 or or
above)
none) none)
31 Van (Ang) 32767 degrees 2 18 10
32 Vbn (Ang) 32767 degrees 2 18 10
33 Vcn (Ang) 32767 degrees 2 18 10
34 Vab (Ang) 32767 degrees 2 18 10
35 Vbc (Ang) 32767 degrees 2 18 10
36 Vca (Ang) 32767 degrees 2 18 10
37 I0 (Zero Sequence Current 32767 Amps 2 19 10
Magnitude)
38 I0 Angle (Zero Sequence 32767 degrees 2 19 10
Current Angle)
39 I1 (Positive Sequence Current 32767 Amps 2 19 10
Magnitude)
40 I1 Angle (Positive Sequence 32767 degrees 2 19 10
Current Angle)
41 I2 (Negative Sequence Current 32767 Amps 2 19 10
Magnitude)
42 I2 Angle (Negative Sequence 32767 degrees 2 19 10
Current Angle)
43 V1 32767 Volts 2 19 10
44 V1 Angle 32767 degrees 2 19 10
45 V2 32767 Volts 2 19 10
46 V2 Angle 32767 degrees 2 19 10
47 Frequency 327.67 Hz 2 20 10
48 Power Factor (signed) 327.67 2 20 10
(values will range from 0 to 100)
49 Power Factor leading/lagging 0=lagging, 2 20 10
1=leading
1
50 3-Phase Volt-Amps 32767 Volt-Amps 2 21 10
51 Demand Ia 32767 Amps 2 22 10
52 Demand Ib 32767 Amps 2 22 10
53 Demand Ic 32767 Amps 2 22 10
54 Demand In 32767 Amps 2 22 10
55 Demand KWan 32767 KWatts 2 22 10
56 Demand KWbn 32767 KWatts 2 22 10
57 Demand KWcn 32767 KWatts 2 22 10
58 Demand KW3 32767 KWatts 2 22 10
59 Demand KVARan 32767 KVAR 2 22 10
60 Demand KVARbn 32767 KVAR 2 22 10
61 Demand KVARcn 32767 KVAR 2 22 10
62 Demand KVAR3 32767 KVAR 2 22 10
Page 37 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Analog Inputs
Static (Steady-State) Object Number: 30
Change Event Object Number: 32
Request Function Codes supported: 1 (read)
Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input)
Change Event Variation reported when variation 0 requested: 2 (Analog Change Event w/o
Time)
3
Point User Name/Description Default User
Default
Index Assign Change Assign
Dead-
-ed Scaling Event -ed Scan
band
Point (representation Assigned Class Type
(see
Index of 32767) Class (1,2,3 Group
note
(1,2,3 or or
above)
none) none)
63 Max Ia 32767 Amps 2 22 10
64 Max Ib 32767 Amps 2 22 10
65 Max Ic 32767 Amps 2 22 10
66 Max In 32767 Amps 2 22 10
67 Max KWan 32767 KWatts 2 22 10
68 Max KWbn 32767 KWatts 2 22 10
69 Max KWcn 32767 KWatts 2 22 10
70 Max KW3 32767 KWatts 2 22 10
71 Max KVARan 32767 KVAR 2 22 10
72 Max KVARbn 32767 KVAR 2 22 10
73 Max KVARcn 32767 KVAR 2 22 10
74 Max KVAR3 32767 KVAR 2 22 10
75 Minimum Ia 32767 Amps 2 22 10
76 Minimum Ib 32767 Amps 2 22 10
77 Minimum Ic 32767 Amps 2 22 10
78 Minimum In 32767 Amps 2 22 10
79 Minimum KWan 32767 KWatts 2 22 10
80 Minimum KWbn 32767 KWatts 2 22 10
81 Minimum KWcn 32767 KWatts 2 22 10
82 Minimum KW3 32767 KWatts 2 22 10
83 Minimum KVARan 32767 KVAR 2 22 10
84 Minimum KVARbn 32767 KVAR 2 22 10
85 Minimum KVARcn 32767 KVAR 2 22 10
86 Minimum KVAR3 32767 KVAR 2 22 10
87 UPS Battery Voltage 655.34 Volts 2 22 10
88 UPS Battery Charging Current 655.34 Amps 2 22 -10
89 UPS Battery Temperature 327.67 C 2 22 10
90 UPS Battery Test Delta Voltage 655.34 Volts 2 22 10
91 Last Fault: Record Number 65534 2 23 1
92 Last Fault: Faulted Device See Table 5.4.1 2 23 1
93 Last Fault: Settings Group / See Table 5.4.2 2 23 1
Sequence Number
94 Last Fault: Line Parameter See Table 5.4.3 2 23 1
95 Last Fault: Year 32767 Years 2 23 1
96 Last Fault: Month 32767 Months 2 23 1
97 Last Fault: Day 32767 Days 2 23 1
98 Last Fault: Hour 32767 Hours 2 23 1
99 Last Fault: Minute 32767 Minutes 2 23 1
Feb/3/2003 Page 38 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Analog Inputs
Static (Steady-State) Object Number: 30
Change Event Object Number: 32
Request Function Codes supported: 1 (read)
Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input)
Change Event Variation reported when variation 0 requested: 2 (Analog Change Event w/o
Time)
3
Point User Name/Description Default User
Default
Index Assign Change Assign
Dead-
-ed Scaling Event -ed Scan
band
Point (representation Assigned Class Type
(see
Index of 32767) Class (1,2,3 Group
note
(1,2,3 or or
above)
none) none)
100 Last Fault: Second 32767 Seconds 2 23 1
101 Last Fault: Millisecond 32767 MilliSec. 2 23 1
102 Last Fault: Phase A Current 32767 Amps 2 23 1
Magnitude
103 Last Fault: Phase B Current 32767 Amps 2 23 1
Magnitude
104 Last Fault: Phase C Current 32767 Amps 2 23 1
Magnitude
105 Last Fault: Neutral Current 32767 Amps 2 23 1
Magnitude
106 Last Fault: Phase A Current 32767 degrees 2 23 1
Angle
107 Last Fault: Phase B Current 32767 degrees 2 23 1
Angle
108 Last Fault: Phase C Current 32767 degrees 2 23 1
Angle
109 Last Fault: Neutral Current Angle 32767 degrees 2 23 1
110 Last Fault: Zero Sequence 32767 Amps 2 23 1
Current Magnitude
111 Last Fault: Positive Sequence 32767 Amps 2 23 1
Current Mag.
112 Last Fault: Negative Sequence 32767 Amps 2 23 1
Current Mag.
113 Last Fault: Zero Sequence 32767 degrees 2 23 1
Current Angle
114 Last Fault: Positive Sequence 32767 degrees 2 23 1
Current Angle
115 Last Fault: Negative Sequence 32767 degrees 2 23 1
Current Angle
116 Last Fault: Phase A Voltage 32767 Volts 2 23 1
Magnitude
117 Last Fault: Phase B Voltage 32767 Volts 2 23 1
Magnitude
118 Last Fault: Phase C Voltage 32767 Volts 2 23 1
Magnitude
119 Last Fault: Phase A Voltage 32767 degrees 2 23 1
Angle
120 Last Fault: Phase B Voltage 32767 degrees 2 23 1
Angle
121 Last Fault: Phase C Voltage 32767 degrees 2 23 1
Angle
122 Last Fault: Positive Sequence 32767 Volts 2 23 1
Voltage Mag.
Page 39 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Analog Inputs
Static (Steady-State) Object Number: 30
Change Event Object Number: 32
Request Function Codes supported: 1 (read)
Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input)
Change Event Variation reported when variation 0 requested: 2 (Analog Change Event w/o
Time)
3
Point User Name/Description Default User
Default
Index Assign Change Assign
Dead-
-ed Scaling Event -ed Scan
band
Point (representation Assigned Class Type
(see
Index of 32767) Class (1,2,3 Group
note
(1,2,3 or or
above)
none) none)
123 Last Fault: Negative Sequence 32767 Volts 2 23 1
Voltage Mag.
124 Last Fault: Positive Sequence 32767 degrees 2 23 1
Voltage Angle
125 Last Fault: Negative Sequence 32767 degrees 2 23 1
Voltage Angle
126 Last Fault: Fault Location 3276.7 mi/km 2 23 1
127 Last Fault: Fault Impedance 32.767 ohms 2 23 1
(Real)
128 Last Fault: Fault Clearing Time 32.767 Sec. 2 23 1
129 Last Fault: Relay Time 32.767 Sec. 2 23 1
130 Firmware Version Number V327.67 2 24 1
(CPU)
131 Unit Serial Number 32767 2 24 1
132 Unit Information See Table 5.4.4 2 24 1
133 Voltage Source 1, Phase A 32767 V 2 26 10
magnitude
134 Voltage Source 1, Phase A N/A 2 26 10
2
angle
135 Voltage Source 1, Phase B 32767 V 2 26 10
magnitude
136 Voltage Source 1, Phase B N/A 2 26 10
2
angle
137 Voltage Source 1, Phase C 32767 V 2 26 10
magnitude
138 Voltage Source 1, Phase C N/A 2 26 10
2
angle
139 Voltage Source 2, Phase A 32767 V 2 26 10
magnitude
140 Voltage Source 2, Phase A N/A 2 26 10
2
angle
141 Voltage Source 2, Phase B 32767 V 2 26 10
magnitude
142 Voltage Source 2, Phase B N/A 2 26 10
2
angle
143 Voltage Source 2, Phase C 32767 V 2 26 10
magnitude
144 Voltage Source 2, Phase C N/A 2 26 10
2
angle
145 V0 32767 Volts 2 19 10
146 V0 angle 32767 degrees 2 19 10
Feb/3/2003 Page 40 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
1Pointwill return Off-Line status. It is not currently supported but is reserved for future
implementation.
2Point will return zero. Not currently supported, but is reserved for future implementation.
3The Change Event Class Assignment may be changed off-line through configuration software.
Page 41 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
47 ALT1 - Lockout
65 ALT2 - 1
66 ALT2 - 2
67 ALT2 - 3
68 ALT2 - 4
79 ALT2 - Lockout
2-7 : Reserved
Page 43 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Scaling
Point
Name/Description (representation Scan Type Group
Index
of 32767)
0 Communications Mode (Mode parameters 1 - 8) Ref. section 2.1 25
1 Communications Parameter 1 (Inter Character Delay) Ref. section 2.1 25
2 Communications Parameter 2 (Data link confirmation timeout) Ref. section 2.1 25
3 Communications Parameter 3 (Data link retries) Ref. section 2.1 25
4 Communications Parameter 4 (Transmission delay) Ref. section 2.1 25
5 Communications Parameter 5 (Class 0 scan group mask, 0-7) Ref. section 2.1 25
6 Communications Parameter 6 (Class 0 scan group mask, 8-15) Ref. section 2.1 25
7 Communications Parameter 7 (Class 0 scan group mask, 16-23) Ref. section 2.1 25
8 Communications Parameter 8 (Class 0 scan group mask, 24-31) Ref. section 2.1 25
9 Communications Parameter 9 (Application layer fragment size) Ref. section 2.1 25
10 Communications Parameter 10 (Application layer confirmation Ref. section 2.1 25
timeout)
11 Communications Parameter 11 (Unsolicited response notification Ref. section 2.1 25
delay)
12 Communications Parameter 12 (Destination address) Ref. section 2.1 25
13 Communications Parameter 13 (Minimum number of Class 1 events Ref. section 2.1 25
for unsolicited response)
14 Communications Parameter 14 (Minimum number of Class 2 events Ref. section 2.1 25
for unsolicited response)
15 Communications Parameter 15 (Minimum number of Class 3 events Ref. section 2.1 25
for unsolicited response)
16 Communications Parameter 16 Write time interval Ref. section 2.1 25
17 Communications Parameter 17 Data link confirmations Ref. section 2.1 25
18 Communications Parameter 18 Unsolicited offline interval Ref. section 2.1 25
19 Communications Parameter 19 (Reserved) Ref. section 2.1 25
20 Communications Parameter 20 (Reserved) Ref. section 2.1 25
21 Communications Parameter 21 Default variation for Object 02 Ref. section 2.1 25
22 Communications Parameter 22 Default variation for Object 30 Ref. section 2.1 25
23 Communications Parameter 23 Default variation for Object 32 Ref. section 2.1 25
24 Communications Parameter 24 Protocol Autodetect Enable Ref. section 2.1 25
25 Communications Parameter 25 Unsolicited Maximum Retries Ref. section 2.1 25
26 Unit Address 25
27 LCM Mode (0=Disable, 1=Sectionalizer, 2=Midpoint, 3=Tiepoint) 25
28 LCM Alt1 Select Enable (0= Disabled, 1=Enabled) 25
1
29 51P Min. Trip Current Index 25
1
30 51N Min. Trip Current Index 25
1 Refer to tables 5.5.1 and 5.5.2 for scaling information to convert minimum trip current index to
trip current in Amperes based on catalog number and tap settings. These values apply to the
currently active protection group, Primary, ALT1 or ALT2.
Feb/3/2003 Page 44 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Table 5.5.1: Minimum Trip Current Scale Factors (Points 29 and 30)
Table 5.5.2: Minimum Trip Current Scale Factors (Points 29 and 30)
Page 45 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Feb/3/2003 Page 46 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
6.1.1 Unsolicited responses – The PCD supports unsolicited responses; the DPU-2000 does
not. To configure unsolicited responses, Parameters 11 through 15, and Mode Parameter
5 are new to the PCD.
6.1.2 Writes to Counters – The PCD does not support write function codes to binary
counters. It is envisioned that this functionality is only necessary at device installation and
therefore that this be performed outside the scope of DNP.
6.1.3 Snapshot Event Logging – The PCD does not support reporting of snapshot event
logging through analog input points or analog input change event points. Therefore,
DPU-2000 Analog Input points 55 through 89 do not exist in the PCD. It is envisioned
that this functionality be replaced through use of the FILE-ID object.
6.1.4 Peaks and Minimums – The DPU-2000 documents these data as event data. Instead,
the PCD implements these data as standard Analog Inputs, and assigns them new point
numbers: 63 through 86.
6.1.5 Frozen Counters – The DPU-2000 documents that “Each freeze request will capture
one sample of the related static counter up to a maximum of 32 samples. Analog and
binary event data will be stored for up to 32 fault records and up to 128 operations
records.” The PCD does not explicitly follow this implementation; instead only the most
recent freeze of a binary counter is stored and reported through Object 21.
6.2.1 Parameter 2 (Data Link Confirmation Time-out) – Since the PCD does not perform
serial message collision detection or recovery, this value does not serve a dual-purpose in
any such algorithm.
6.2.2 Parameter 4 (Transmission Delay) – A value of zero is now allowed for this parameter.
If zero, then data may be transmitted immediately after a data frame has been received,
with the only possible delay being the compute-time necessary to build the transmitted
frame. This allows use of the PCD in a non-RS485 environment.
6.2.3 Parameters 5, 6, 7, and 8 (Class Scan Masks) – For clarity, the bit value for enabling and
disabling Scan Type Group 0 is, for the PCD, the same as all the other Scan Type
Page 47 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Groups: 1 to enable, and 0 to disable. This means that the default value for Parameter 5
is 1, not 0; similarly, to enable all groups in Parameter 5, the value is 255, not 254.
6.2.4 Parameters 9 and 10– Theses parameters are new to the PCD and are used to specify
application layer fragment size and application layer confirmation timeout.
6.2.5 Parameters 11 through 15 – These parameters are new to the PCD and are used to
configure unsolicited responses.
6.2.6 Parameters 16 – This parameter is new to the PCD and is used to configure the time
interval between requests for time synchronization from the master.
6.2.8 Mode Parameter 1 As describe above, this parameter has been replaced with Parameter
17, and is no longer used for the PCD.
6.2.9 Mode Parameter 2 (Application Confirmations) – For the DPU-2000, application layer
confirms could be completely disabled by using a value of 0 for this parameter. For the
PCD, completely disabling application layer confirmations is not allowed; a value of 0
specifies that application layer confirms be requested for messages containing event data.
For the DPU-2000 a non-zero value for this parameter specifies that application confirms
always be requested. For the PCD, requesting application layer confirmations for every
message is not allowed. Therefore, a non-zero value for this parameter specifies that
application layer confirmations be used only for fragments containing event data or for
fragments that are part of a multi-fragment response. See Section 2.1.28 on Page 9.
6.2.10 Mode Parameter 3 (Protocol Selection) – This parameter has been replaced on the
PCD with the “RP Protocol” parameter. Consequently Mode Parameter 3 is no longer
used for the PCD.
6.2.12 Mode Parameters 5 (Unsolicited Mode) – This parameter is new to the PCD and is
used to enable unsolicited response messages.
Feb/3/2003 Page 48 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
7 Revision History
Version: 1.0,
Date: March 1, 1998
Version: 1.1,
Date: August 19, 1998
SECTION DESCRIPTION
5.1 Added status points 142, 143, 144, 145 (27A, 27B, 27C, and LOAC)
5.1 Added status points 146, 147, 148, 149 (Remote Block, Ground Block, SEF Block, and Reclose Block)
5.1 Added status points 150 – 155 (Prim/ALT1/ALT2 Settings Active and Pending status)
5.2 Added control points 51, 52, 53 (Reclose Block, Ground Block, SEF Block)
5.2 Added control points 54 and 55 (ALT1 Enable, ALT2 Enable)
Version: 1.2,
Date: January 12, 1999
SECTION DESCRIPTION
5.2 Added control points 56 and 57 (Open Tag/Untag, Close Tag/Untag)
Version: 1.3,
Date: January 18, 1999
Correction to documentation.
SECTION DESCRIPTION
2.1.9 Associated scan type group 11 with binary inputs.
2.1 Added note on out-of-range values to parameters 1, 2, 9, 10, and 17.
2.1.5 Out-of-range value of zero disables inter-character timing.
2.1.6 Out-of-range value of zero sets parameter equal to 1.
2.1.10 Out-of-range value of zero sets parameter equal to 1. Value greater than 8 sets parameter equal to 8.
2.1.11 Out-of-range value of zero sets parameter equal to 1.
2.1 18 Out-of-range value greater than 2 sets parameter equal to 2.
Version: 1.4,
Date: May 10, 1999
SECTION DESCRIPTION
5.1 Added status points 156, 157, 158, 159 (59A, 59B, 59C, and 59-3P)
Page 49 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Version: 1.5,
Date: August 17, 1999
SECTION DESCRIPTION
5.1 Added status points 160 through 165 (PUTA, PUTB, PUTC, PUTN, PTA, and NTA)
5.4 Added analog points 91 through 130 (Last Fault Record and Version number)
5.4 Added tables 5.4.1 through 5.4.3 to support the above points.
Version: 1.6,
Date: October 27, 1999
SECTION DESCRIPTION
2.1 Changed Unit Address default from 5 to 1 (Table).
2.1 Changed RP Protocol default from RTU to ASCII (Table).
2.1 Placed "*" behind Parameter 11 to 15 labels to indicate a warm start of DNP3.0 will occur on a change of any of
these parameters (Table).
2.1.12-16 Added "DNP3.0 warm start" statement on the descriptions for Parameters 11 to 15.
5.1 Added status points 166 through 169 (TAGOPN, TAGCLS, OPNBLK, CLSBLK)
5.4 Analog points 0 to 62 are now assigned to class 2 (from none).
5.4 Added analog point 131 (Serial Number)
5.5 Added section to document new analog output points.
Version: 1.7
Date: April 20, 2000
Modifications in support of PCD2000 Release V2.00 (Single Phase Reclosing) and SCD2000
Release V1.00 (Switch Control Device).
SECTION DESCRIPTION
5.1 Added input points 170 – 198.
5.2 Added output points 58 – 78.
5.3 Added binary counters 11 – 44.
Version: 1.8
Date: November 16, 2000
Additional features were added to the DNP implementation. Support for unsolicited response to
legacy DNP master stations has been added and paired pulse points were added to control
features that were previously implemented using the latch function.
SECTION DESCRIPTION
2.1 Added Mode Parameter 6 to configuration options table.
2.1.25 Added description of Mode Parameter 6
5.2 Added pulse binary output points 79-92
Feb/3/2003 Page 50 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Version: 1.9
Date: June 11, 2001
Loop control option was added to the PCD2000 (Release V2.20), and corresponding points were
added to the DNP implementation.
SECTION DESCRIPTION
5.1 Added binary input points 197 – 206.
5.2 Added binary output points 93 – 102.
5.4 Added analog input points 133 – 144.
Version: 1.10
Date: March 21, 2002
Modifications in support of PCD Release V2.40 (DNP Enhancements and Protocol Autodetect).
SECTION DESCRIPTION
All Replaced PCD 2000 with PCD, SCD 2000 with SCD
2.1 Added Parameters 18 - 24 to configuration options table.
2.1.19 - Added description of Parameters 18 - 24.
2.1.25
4 Removed Object 1 Variation 2 from the Implementation table
5.1 Added columns for User Assigned Point Indexes and Classes.
5.4 Added analog input points 145 – 146.
Added columns for User Assigned Point Indexes and Classes.
Version: 1.11,
Date: October 18, 2002
SECTION DESCRIPTION
Title Page Used PTMV Document Number
Version: 1.20,
Date: February 3, 2003
SECTION DESCRIPTION
- The DNP library used in the PCD firmware was upgraded to Triangle Microworks DNP Slave Library V3.00.
This document was extensively revised to reflect the changes in the DNP protocol implementation.
Page 51 of 53 Feb/3/2003
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Version: 1.30
Date: September 1, 2004
SECTION DESCRIPTION
2.1 Added descriptions for Parameters 19 and 20.
5.1 Added binary input points 208 - 212.
5.2 Added binary output points 103 - 105.
Version: 1.40
Date: August 3, 2006
SECTION DESCRIPTION
2.1 Modified the range and default for Parameters 21.
2.1.22 Updated the description for Parameter 21.
5.2 Added binary output points 106 - 108.
5.4 Modified the description for point 48.
End of Document
Feb/3/2003 Page 52 of 53
DNP 3.0 Implementation Details for the ABB PCD/SCD
© ABB INC.
Page 53 of 53 Feb/3/2003