Document Revision History

DOCUMENT REVISION HISTORY
Name of Document: DNP V3:00 Data Object Library Network File Name: P009-OBL Original Author: Malcolm Smith/Michael Copps Date and Version of Preliminary Release: October 8, 1992 Version 0.00A Associated Software Release(s): DNP V3.00
Revisions Since Preliminary Release Date Oct. 08/92 Nov. 09/92 Nov. 23/92 Jun. 27/93 Jul. 01/93 Aug. 20/93 Sep. 01/93 Sep. 01/93 July. 08/97 Version 0.00A 0.00B 0.01 0.02 0.02 0.02 0.02 0.02 0.02 By Whom MS MS LA MS JB JB JB MCH S. Tessari Pages Affected All All All All All All All All All Reason for Changes Created using P020-0BL Revised after review and editorials. Reformatted to WI standards. Re-structure, addition of objects. Update and edit as per the review. Update and addition of new objects. Update and reformat. Check and revise format. Converted to MSWord 6.0
DNP Users Group

DNP PRODUCT DOCUMENTATION
DNP V3.00 DATA OBJECT LIBRARY
Document Version: 0.02 Internal File: P009-OBL Associated Software Release: DNP V3.00
NOTICE OF RIGHTS - DNP USERS GROUP

The contents of this manual are the property of the DNP Users Group. Revisions or additions to the definition and functionality of the Distributed Network Protocol cannot be made without express written agreement from the DNP Users Group or its duly authorized party. In addition, no part of this document may be altered or revised or added to in any form or by any means, except as permitted by written agreement with the DNP Users Group or a Party duly authorized by the DNP Users Group. As a Party, duly authorized by the DNP Users Group, Harris Corporation has made every reasonable attempt to ensure the completeness and accuracy of this document, however, the information contained in this manual is subject to change without notice, and does not represent a commitment on the part of Harris Corporation or the DNP Users Group. An update program for DNP documents is provided upon request by Harris Corporation on behalf of the DNP Users Group.
TRADEMARK NOTICES
Brand and product names mentioned in this document are trademarks or registered trademarks of their respective companies.
TABLE OF CONTENTS
ABOUT THIS DOCUMENT PURPOSE OF THIS SPECIFICATION WHO SHOULD USE THIS SPECIFICATION HELP AND ADDITIONAL DOCUMENTATION HOW THIS SPECIFICATION IS ORGANIZED CONVENTIONS USED IN THIS SPECIFICATION 1. OVERVIEW 2. DECLARATION RULES FOR INFORMATION ELEMENTS 2.1 GENERAL 3. GENERAL RULES 3.1 LIBRARY STRUCTURE 3.2 POINT NUMBERING 4. BINARY INPUT OBJECT DEFINITIONS 4.1 SINGLE-BIT BINARY INPUT 4.2 BINARY INPUT WITH STATUS 4.3 BINARY INPUT CHANGE WITHOUT TIME 4.4 BINARY INPUT CHANGE WITH TIME 4.5 BINARY INPUT CHANGE WITH RELATIVE TIME 5. BINARY OUTPUT OBJECT DEFINITIONS 5.1 BINARY OUTPUT 5.2 BINARY OUTPUT STATUS 5.3 CONTROL RELAY OUTPUT BLOCK 5.4 PATTERN CONTROL BLOCK 5.5 PATTERN MASK 6. COUNTER OBJECT DEFINITIONS 6.1 32-BIT BINARY COUNTER 6.2 16-BIT BINARY COUNTER 6.3 32-BIT DELTA COUNTER 6.4 16-BIT DELTA COUNTER 6.5 32-BIT COUNTER WITHOUT FLAG
DNP V3.00 Data Object Library (Version 0.02)
vi vi vi vi vii vii 1-1 2-1 2-1 3-1 3-1 3-4 4-1 4-1 4-3 4-4 4-6 4-8 5-1 5-1 5-2 5-3 5-7 5-8 6-1 6-1 6-3 6-5 6-6 6-7 i
6.6 16-BIT COUNTER WITHOUT FLAG 6.7 32-BIT DELTA COUNTER WITHOUT FLAG 6.8 16-BIT DELTA COUNTER WITHOUT FLAG 6.9 32-BIT FROZEN COUNTER 6.10 16-BIT FROZEN COUNTER 6.11 32-BIT FROZEN DELTA COUNTER 6.12 16-BIT FROZEN DELTA COUNTER 6.13 32-BIT FROZEN COUNTER WITH TIME OF FREEZE 6.14 16-BIT FROZEN COUNTER WITH TIME OF FREEZE 6.15 32-BIT FROZEN DELTA COUNTER WITH TIME OF FREEZE 6.16 16-BIT FROZEN DELTA COUNTER WITH TIME OF FREEZE 6.17 32-BIT FROZEN COUNTER WITHOUT FLAG 6.18 16-BIT FROZEN COUNTER WITHOUT FLAG 6.19 32-BIT FROZEN DELTA COUNTER WITHOUT FLAG 6.20 16-BIT FROZEN DELTA COUNTER WITHOUT FLAG 6.21 32-BIT COUNTER CHANGE EVENT WITHOUT TIME 6.22 16-BIT COUNTER CHANGE EVENT WITHOUT TIME 6.23 32-BIT DELTA COUNTER CHANGE EVENT WITHOUT TIME 6.24 16-BIT DELTA COUNTER CHANGE EVENT WITHOUT TIME 6.25 32-BIT COUNTER CHANGE EVENT WITH TIME 6.26 16-BIT COUNTER CHANGE EVENT WITH TIME 6.27 32-BIT DELTA COUNTER CHANGE EVENT WITH TIME 6.28 16-BIT DELTA COUNTER CHANGE EVENT WITH TIME 6.29 32-BIT COUNTER CHANGE EVENT WITHOUT TIME 6.30 16-BIT FROZEN COUNTER EVENT WITHOUT TIME 6.31 32-BIT FROZEN DELTA COUNTER EVENT WITHOUT TIME 6.32 16-BIT FROZEN DELTA COUNTER WITHOUT TIME 6.33 32-BIT FROZEN COUNTER EVENT WITH TIME 6.34 16-BIT FROZEN COUNTER EVENT WITH TIME 6.35 32-BIT FROZEN DELTA COUNTER EVENT WITH TIME 6.36 16-BIT FROZEN DELTA COUNTER EVENT WITH TIME 7. ANALOG INPUT OBJECT DEFINITIONS 7.1 32-BIT ANALOG INPUT 7.2 16-BIT ANALOG INPUT 7.3 32-BIT ANALOG INPUT WITHOUT FLAG 7.4 16-BIT ANALOG INPUT WITHOUT FLAG 7.5 32-BIT FROZEN ANALOG INPUT 7.6 16-BIT FROZEN ANALOG INPUT 7.7 32-BIT FROZEN ANALOG INPUT WITH TIME OF FREEZE 7.8 16-BIT FROZEN ANALOG INPUT WITH TIME OF FREEZE 7.9 32-BIT FROZEN ANALOG INPUT WITHOUT FLAG 7.10 16-BIT FROZEN ANALOG INPUT WITHOUT FLAG 7.11 32-BIT ANALOG CHANGE EVENT WITHOUT TIME 7.12 16-BIT CHANGE EVENT WITHOUT TIME 7.13 32-BIT ANALOG CHANGE EVENT WITH TIME 7.14 16-BIT ANALOG CHANGE EVENT WITH TIME ii
6-8 6-9 6-10 6-11 6-12 6-13 6-14 6-15 6-17 6-19 6-21 6-23 6-24 6-25 6-26 6-27 6-28 6-29 6-30 6-31 6-33 6-35 6-37 6-39 6-40 6-41 6-42 6-43 6-45 6-47 6-49 7-1 7-1 7-3 7-5 7-6 7-7 7-8 7-9 7-11 7-13 7-14 7-15 7-17 7-19 7-21
DNP Users Group
7.15 32-BIT FROZEN ANALOG EVENT WITHOUT TIME 7.16 16-BIT FROZEN ANALOG EVENT WITHOUT TIME 7.17 32-BIT FROZEN ANALOG EVENT WITH TIME 7.18 16-BIT FROZEN ANALOG EVENT WITH TIME 8. ANALOG OUTPUT OBJECT DEFINITIONS 8.1 32-BIT ANALOG OUTPUT STATUS 8.2 16-BIT ANALOG OUTPUT STATUS 8.3 32-BIT ANALOG OUTPUT BLOCK 8.4 16-BIT ANALOG OUTPUT BLOCK 9. TIME OBJECT DEFINITIONS 9.1 TIME AND DATE 9.2 TIME AND DATE WITH INTERVAL 9.3 TIME AND DATE CTO 9.4 UN-SYNCHRONIZED TIME AND DATE CTO 9.5 TIME DELAY COARSE 9.6 TIME DELAY FINE 10. CLASS OBJECT DEFINITIONS 10.1 CLASS 0 DATA 10.2 CLASS 1 DATA 10.3 CLASS 2 DATA 10.4 CLASS 3 DATA 11. FILE OBJECT DEFINITIONS 11.1 FILE IDENTIFIER 12. DEVICE OBJECT DEFINITIONS 12.1 INTERNAL INDICATIONS 12.2 STORAGE OBJECT 12.3 DEVICE PROFILE 12.4 PRIVATE REGISTRATION OBJECT 12.5 PRIVATE REGISTRATION OBJECT DESCRIPTOR 13. APPLICATION OBJECT DEFINITIONS 13.1 APPLICATION IDENTIFIER 14. ALTERNATE NUMERIC OBJECT DEFINITIONS 14.1 SHORT FLOATING POINT 14.2 LONG FLOATING POINT 14.3 EXTENDED FLOATING POINT 14.4 SMALL-PACKED BINARY CODED DECIMAL 14.5 MEDIUM-PACKED BINARY CODED DECIMAL 14.6 LARGE-PACKED BINARY CODED DECIMAL
7-23 7-25 7-27 7-29 8-1 8-1 8-3 8-4 8-5 9-1 9-1 9-2 9-4 9-5 9-6 9-7 10-1 10-1 10-2 10-3 10-4 11-1 11-1 12-1 12-1 12-2 12-4 12-7 12-8 13-1 13-1 14-1 14-1 14-4 14-6 14-8 14-9 14-10 iii
LIST OF ABBREVIATIONS AND ACRONYMS
iv
DNP Users Group
LIST OF TABLES
TABLE 2-1 DATA TYPES TABLE 2-2 BIT POSITIONS 2-1 2-2
ABOUT THIS DOCUMENT

PURPOSE OF THIS SPECIFICATION
This document defines coding specifications of Distributed Network Protocol (DNP) information elements or data objects used in the DNP Application Layer. The object syntax is specified as well as the semantics of each object. In the case of compound objects, the semantics of each component is described.
WHO SHOULD USE THIS SPECIFICATION

All programmers, implementers or engineers interested in the structure of application information objects used in the DNP Application Layer.
HELP AND ADDITIONAL DOCUMENTATION

The following documentation may be helpful. DNP V3.00 Data Link Layer (P009-0PD.DL). DNP V3.00 Application Layer (P009-0PD.APP) DNP V3.00 Transport Functions (P009-0PD.TF)
vi
DNP Users Group
HOW THIS SPECIFICATION IS ORGANIZED

This document is organized into 13 sections as outlined below. 1. OVERVIEW 2. DECLARATION RULES FOR INFORMATION ELEMENTS Covers the rules for construction and interpretation of the data objects. 3. GENERAL RULES Describes the rules governing each of the currently defined objects. The rest of the sections provide detailed definitions of each type of object. 4. BINARY INPUT OBJECT DEFINITIONS 5. BINARY OUTPUT OBJECT DEFINITIONS 6. COUNTER OBJECT DEFINITIONS 7. ANALOG INPUT OBJECT DEFINITIONS 8. ANALOG OUTPUT OBJECT DEFINITIONS 9. TIME OBJECT DEFINITIONS 10. CLASS OBJECT DEFINITIONS 11. FILE OBJECT DEFINITIONS 12. DEVICE OBJECT DEFINITIONS 13. APPLICATION OBJECT DEFINITIONS 14. ALTERNATE NUMERIC OBJECT DEFINITIONS LIST OF ABBREVIATIONS AND ACRONYMS
CONVENTIONS USED IN THIS SPECIFICATION

This document deviates from the IEC conventions for bit position numbering. Bit positions are numbered from 0 through n, with 0 to the top right and n to the bottom left.
vii
viii
DNP Users Group
1. OVERVIEW
The intelligent devices which use the DNP Application Layer protocol are capable of monitoring, controlling and/or producing a large number of different pieces of data both at the hardware and software levels. These pieces of data, called information elements (IEC 870-5-3: General Structure of Application Data), are processed and stored as information objects and these can be packaged for transmission as application data units. All devices provide stored information elements as information objects in the same format. These formats are described within this document. This document will be revised and new information elements or objects will be added as necessary, and as authorized by the DNP User's Group.
1-1
1-2
DNP Users Group
2. DECLARATION RULES FOR INFORMATION ELEMENTS

2.1 GENERAL
This section describes the basic rules for the declaration of information elements. These rules have been derived from the IEC TC57 870 series of standards or drafts. These rules provide an unambiguous means of describing and representing data irrespective of its origin. Device profile documents are used to indicate the exact origin and meaning of the data object for each telecontrol device. 2.1.1 Data Types All data can be described in its most elemental form as a data type. Data types are recognized as standard constructs used in most language compilers. DNP information elements use constructs, as supported by the IEC 870-5-4, as the basis of its descriptions. Table 2-1 lists the available data types and their meaning.
Data Type 1. UNSIGNED INTEGER 2. INTEGER 3. UNSIGNED FIXED POINT 4. FIXED POINT 5. REAL 6. BITSTRING 7. OCTETSTRING Symbol UI I UF F R BS OS Meaning Positive whole number Positive or negative whole number Positive fixed point number Positive or negative fixed point number Positive or negative floating-point number Assembly of independent bits Assembly of octets
1
Table 2-1 Data Types 2.1.2 Data Size
BOOLEAN is a BITSTRING of size 1.
2-1
Each information element is composed of a data type and a size. Data size i, is noted after the data type symbol notation, and is a cardinal number that specifies the length of the data field in bits or octets as appropriate. An example is: BS12 specifies a BITSTRING of 12 bits. 2.1.3 Bit Position In defining information objects, which are a combination of information elements, the position of individual bits can be significant. The bit position of a specified field of data size i is denoted in square brackets [p1..pn], where p1 and pn denote the first and the last bits of the field. The order of bits is shown in Table 2-2, below.
BITS OCTETS 1 2 . . j 7 15 . . 8j-1 6 14 . . 8j-2 5 13 . . 8j-3 7 6 5 4 3 2 1 0
Data Size i 4 12 . . 8j-4 3 11 . . 8j-5 2 10 . . 8j-6 1 9 . . 8j-7 0 8 . . 8j-8
Table 2-2 Bit Positions
2.1.4 Element Value If applicable, a selected range and a selected code of values of the declared data field is denoted within angle brackets: <v1..vn code>. In general this is declared by the range of admitted values and by a term that identifies the used code. Terms that identify codes are: binary code (BIN), binary coded decimal (BCD), ASCII (ASCII), etc. The default code declaration is binary if no term is used. 2.1.5 Compound Elements Compound data fields are information elements composed of different data fields with successive bit allocations. Compound data fields are declared by listing individual data fields separated by commas or listed in a column, within curly brackets. A following list declares the data types, the sizes, the bit allocations and the functional purpose of the individual data fields. The first declared data field begins with bit position 0, the other fields use successive bit allocations: 'Information Element = CPi {data field 1, data field 2,...} or {data field 1 = data type 1 size i1[0..i-1] = function 1 2-2
DNP Users Group
data field 2 = data type 2 size i2[i1..i1+i2-1] = function 2 etc.} 2.1.6 Sequence Elements Sequence data fields are information elements composed of different data fields. Sequences of data fields are declared as compound data fields, however each field begins bit allocation 0: 'Information Element = SQi {data field 1, data field 2, ...} or {data field 1 size i1[1..i1] = function 1 data field 2 size i2[1..i2] = function 2 etc.}
2-3
2-4
DNP Users Group
3. GENERAL RULES
This section will describe the general rules that apply to the DNP data objects. These rules apply to all the current objects (except where noted) and all future objects.
3.1 LIBRARY STRUCTURE

The DNP application layer has an 8-bit object and an 8-bit variation field used to denote the data object. The 8-bit object denotes a general type of data such as static binary data. The variation of this object gives a different representation of the same data point, such as the size of the object or whether or not the object has flag information. There are generally four different categories of data within each data type, as outlined below: Static Objects: The objects which reflect the current value of the field point or software point. Event Objects: The objects which are generated as a result of data changing or some other stimulant. These are historical objects reflecting the value of data at some time in the past. Frozen Static Objects: The objects which reflect the current frozen value of the field point or software point. Data is frozen as a result of the data freeze requests. (Refer to the DNP V3.00 Application Layer, P009-0PD.APP.) Frozen Event Objects: The objects which are generated as a result of frozen data changing or some other stimulant. These are historical objects reflecting the value of changed data at some time in the past.
Each category should be represented with a different object. All the classes of a different data type should also be organized in the same range of object numbers. So far, the following groupings have been created for all traditional SCADA/DA data types and several non-traditional data types. These are as follows: 3.1.1 Binary Input The binary input grouping contains all objects that represent binary (status or Boolean) input information. The objects 1 - 9 are reserved for these objects.
3-1
3.1.2 Binary Output The binary output grouping contains all objects that represent binary output or relay control information. The objects 10 - 19 are reserved for these objects. 3.1.3 Counters The counter grouping contains all objects that represent counters. The objects 20 - 29 are reserved for these objects. 3.1.4 Analog Input The analog input grouping contains all objects that represent analog input information. The objects 30 - 39 are reserved for these objects. 3.1.5 Analog Output The analog output grouping contains all objects that represent analog output information. The objects 40 - 49 are reserved for these objects. 3.1.6 Time The time grouping contains all objects that represent time in absolute or relative form in any resolution. The objects 50 - 59 are reserved for these objects. 3.1.7 Class The class grouping contains all objects that represent data classes or data priority. The objects 60 - 69 are reserved for these objects. 3.1.8 Files The files grouping contains all objects that represent files or a file system. The objects 70 - 79 are reserved for these objects. 3.1.9 Devices The devices grouping contains all objects that represent device (rather than point) information. The objects 80 - 89 are reserved for these objects. 3.1.10 Applications The applications grouping contains all objects that represent software applications or operating system processes. The objects 90 - 99 are reserved for these objects. 3.1.11 Alternate Numeric
3-2
DNP Users Group
The alternate numeric grouping contains all objects that represent alternate or custom numeric representations. The objects 100 - 109 are reserved for these objects. 3.1.12 Future Expansion The future expansion grouping is reserved for future or custom expansion of the DNP protocol. The objects 110 - 254 are reserved for these objects. 3.1.13 Reserved The objects 0 and 255 are permanently reserved and should not be used to denote any DNP object. Applications which use these object numbers may not be compatible with future versions of DNP.
3-3
3.2 POINT NUMBERING

The following rules apply to the interpretation of the object point number (DNP Application Layer range field) in conjunction with objects and variations. Rule 1: Point i of object x, variation y represents the same physical point as point i, object x, variation z, where y and z are variations of object x. For example: A device has 16 running counters (object 20) numbered 0 to 15. Point 5 can be asked for in four different ways: Obj 20, var 1, range 5 returns the running value of counter 5 in 32-bit format. Obj 20, var 2, range 5 reports the same information, only in 16-bit format. Obj 20, var 3, range 5 returns the number of counts accumulated in counter 5 since the last time it was reported, again in 32-bit format. Obj 20, var 4, range 5 reports the same information, only in 16-bit format. RULE 2: Point i of object x can be reported in one of many variations (i.e. it can be a 16-bit or 32bit counter). When reported as an event, point i can be returned in either one of the variations for that object. The exact variation to return is an application specific decision, however an application should report only ONE event object in any one variation for each event. When responding to a request for Class data or variation 0 of object x, there should be only one variation of the object returned. RULE 3: Point i within different objects of the same grouping are not necessarily unique, however, within each of the binary input, binary output, analog input, analog output and counter groupings the following rules apply. (a) (b) Point i in the static object is the same physical point as point i in the event object. Point i in the frozen object is the same physical point as point i in the frozen event object.
For example: For binary inputs, point i in obj 1 var 1 and 2 is the same point as point i in obj 2 var 1, 2 and 3 (static and event correlation). For counters, point i in obj 20 var 1, 2, 3, and 4 is the same point as point i in obj 22 var 1, 2, 3, 4, 5, 6, 7, and 8 (static and event correlation). In addition, point i in obj 21 var 1, 2, 3, 4, 5, 6, 7, and 8 is the same point as point i in obj 23 var 1, 2, 3, 4, 5, 6, 7, and 8 (frozen and frozen static correlation). NOTE: Point i in obj 20 and point i in obj 21 are NOT necessarily the same point. There is no direct correlation between frozen and non-frozen objects.
Rule 4: 3-4
DNP Users Group
Object groupings which can by definition or due to device limitation have only one point per object or where the point number is not needed should use the range number 0 or quantity equals to 1, when using a message format that requires a point number.
3-5
3-6
DNP Users Group
4. BINARY INPUT OBJECT DEFINITIONS

This section defines the binary input data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
4.1 SINGLE-BIT BINARY INPUT

Data Object 01 - Variation: 01 Type: Static
Description: The single-bit binary input object is used to represent the state of a digital input point (hardware or software). Object Coding:
0
BS1 [0..0] State = BS1 [0] <0,1 BIN> Narrative: This single-bit binary input representation is used to transmit binary input states in a packed format. Transmission of the data object is always performed in complete octets with unoccupied bit positions set to zero. The following example illustrates the packing of n of these data objects.
7 15 6 14 5 13 4 12 3 11 2 10 1 9 0 8
n-1
n-2
n-3
n-4
4-1
NOTE:
This variation contains no point status information. For example, on-line, restart, etc. bits which are part of the binary input with status variation, are not part of this variation. The use of the single-bit binary input variation implies that the point is on-line and all other status bits are clear. (i.e. restart, communication lost, etc. bits are cleared).
4-2
DNP Users Group
4.2 BINARY INPUT WITH STATUS

Description: The binary input with status object is used to represent the state of a digital input point (hardware or software), and also indicates the status of the point as follows: The on-line bit indicates that the binary input point has been read successfully. If this field is set to off-line, the state of the digital point may not be correct. The restart bit indicates that the field device that originated the data object is currently restarting. This device may be the device reporting this data object. The communication lost bit indicates that the device reporting this data object has lost communication with the originator of the data object. The remote forced data bit indicates that the state of the binary input has been forced to its current state at a device other than the end device. The local forced data bit indicates that the state of the binary input has been forced to its current state at the end device. The chatter filter bit indicates that the binary input point has been filtered in order to remove unneeded transitions in the state of the point. The state bit indicates the current state of the binary input point. Object Coding:
7 6 5 4 3 2 1 0
BS8 [0..7] On-line Restart Communication lost Remote forced data Local forced data Chatter filter Reserved State
= = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1 [5] <0, normal; 1, filter on> BS1 [6] <0> BS1 [7] <0, 1 BIN>
4-3
4.3 BINARY INPUT CHANGE WITHOUT TIME

Data Object 02 - Variation: 01 Type: Event
Description: The binary input change without time object is used to represent the changed state of a digital input point (hardware or software) and also indicates the status of the point as follows: The on-line bit indicates that the binary input point has been read successfully. If this field is set to off-line, the state of the digital point may not be correct. The restart bit indicates that the field device that originated the data object has been re-started. This device may be the device reporting this data object. The communication lost bit indicates that the device reporting this data object has lost communication with the originator of the data object. The remote forced data bit indicates that the state of the binary input has been forced to its current state at the originating device. The local forced data bit indicates that the state of the binary input has been forced to its current state at the device reporting this data object. The chatter filter bit indicates that the binary input point has been filtered in order to remove unneeded transitions in the state of the point. The state bit indicates the current changed state of the binary input point.
4-4
DNP Users Group
Object Coding:
7 6 5 4 3 2 1 0
BS8 [0..7] On-line Restart Communication lost Remote forced data Local forced data Chatter filter Reserved State
= = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1 [5] <0, normal; 1, filter on> BS1 [6] <0> BS1 [7] <0,1 BIN>
Narrative: This object is only reported when the current value is different than the last recorded or measured value. If the chatter filter is on, this object may only be reported when the new state has remained constant for a certain period of time.
4-5
4.4 BINARY INPUT CHANGE WITH TIME

Description: The binary input change with time object is used to represent the changed state of a digital input point (hardware or software) and the time at which the state changed. It also indicates the status of the point as follows: The on-line bit indicates that the binary input point has been read successfully. If this field is set to off-line, the state of the digital point may not be correct. The restart bit indicates that the field device that originated the data object has been re-started. This device may be the device reporting this data object. The communication lost bit indicates that the device reporting this data object has lost communication with the originator of the data object. The remote forced data bit indicates that the state of the binary input has been forced to its current state at the originating device. The local forced data bit indicates that the state of the binary input has been forced to its current state at the device reporting this data object. The chatter filter bit indicates that the binary input point has been filtered in order to remove unneeded transitions in the state of the point. The state bit indicates the current changed state of the binary input point. The Time of Occurrence indicates the absolute time at which the telecontrol device detected the change of state. The accuracy of this time will depend on the accuracy of the individual device.
4-6
DNP Users Group
Object Coding:
FLAG 7 6 5 4 3 2 1 0
TIME OF OCCURRENCE 7 15 23 31 39 47 6 14 22 30 38 46 5 13 21 29 37 45 4 12 20 28 36 44 3 11 19 27 35 43 2 10 18 26 34 42 1 9 17 25 33 41 0 8 16 24 32 40
SQ2
{FLAG = Time of Occurrence = } FLAG On-line Restart Communication lost Remote forced data Local forced data Chatter filter Reserved State } ={ = = = = = = = =
BS8 [0..7] UI48 [0..47] <248 -1 ms>
BS8 [0..7] BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1 [5] <0, normal; 1, filter on> BS1 [6] <0> BS1 [7] <0,1 BIN>
Narrative: Time of occurrence is recorded as milliseconds since midnight, January 1st, 1970, at zero hours, zero minutes, seconds, and milliseconds.
4-7
4.5 BINARY INPUT CHANGE WITH RELATIVE TIME

Description: The binary input change with relative time object is used to represent the changed state of a digital input point (hardware or software), and the relative time at which the state changed. It also indicates the status of the point as follows: The on-line bit indicates that the binary input point has been read successfully. If this field is set to off-line, the state of the digital point may not be correct. The restart bit indicates that the field device that originated the data object has been re-started. This device may be the device reporting this data object. The communication lost bit indicates that the device reporting this data object has lost communication with the originator of the data object. The remote forced data bit indicates that the state of the binary input has been forced to its current state at the originating device. The local forced data bit indicates that the state of the binary input has been forced to its current state at the device reporting this data object. The chatter filter bit indicates that the binary input point has been filtered in order to remove unneeded transitions in the state of the point. The state bit indicates the current changed state of the binary input point. The MSEC field indicates the relative time at which the telecontrol device detected the change of state. The accuracy of this time will depend on the accuracy of the individual device.
4-8
DNP Users Group
Object Coding:
FLAG 7 6 5 4 3 2 1 0
MSEC 7 15 6 14 5 13 4 12 3 11 2 10 1 9 0 8
SQ2
{FLAG MSEC } FLAG On-line Restart Communication lost Remote forced data Local forced data Chatter filter Reserved State }
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = =
BS8 [0..7] BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1 [5] <0, normal; 1, filter on> BS1 [6] <0> BS1 [7] <0,1 BIN>
Narrative: This object MUST be preceded by an absolute time object (common time object or CTO) or an unsynchronized CTO in the DNP Application Layer message. The CTO is used as an absolute time base for all following binary input change with relative time objects. The relative time in each binary input object is added to the CTO absolute time to give the absolute time at which the binary input change was detected by the device.
4-9
4-10
DNP Users Group
5. BINARY OUTPUT OBJECT DEFINITIONS

This section defines the binary output data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
5.1 BINARY OUTPUT

Description: The binary output object is used to control a digital output point (hardware or software). The state bit indicates the desired logic state of the digital output point. Object Coding:
0
BS1 [0..0] State = BS1 [0] <0,1 BIN> Narrative: Transmission of the data object is always pre-formed in complete octets, with unoccupied bit positions set to zero. The following example illustrates the packing of n of these data objects:
7 15 6 14 5 13 4 12 3 11 2 10 1 9 0 8
n-1
n-2
n-3
n-4
5-1
5.2 BINARY OUTPUT STATUS

Description: The binary output status object is used to indicate the current state of a controlled digital point and the status of that point as follows: The on-line bit indicates that the device controlling the binary output point is operating correctly. A binary output command to this point should work correctly. If this field is set to off-line, a binary output command to this point would be unsuccessful. The restart bit indicates that the field device that originated the data object has been re-started. This device may be the device reporting this data object. The communication lost bit indicates that the digital output point could not be controlled because communications have been lost with the controlled device. The remote forced data bit indicates that the digital output point has been controlled at the originating device and the current state is in the state bit. The local forced data bit indicates that the digital output point has been controlled at this device and the current state is in the state bit. The state bit indicates the current state of the binary output point. Object Coding:
7 6 5 4 3 2 1 0
BS8 [0..7] On-line Restart Communication lost Remote forced data Local forced data Reserved Reserved State
= = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1 [5] <0> BS1 [6] <0> BS1 [7] <0,1 BIN>
5-2
DNP Users Group
5.3 CONTROL RELAY OUTPUT BLOCK

Description: The control relay output Block information object contains digital output control parameters. These parameters define the type and duration of the digital output. The control code field indicates the control function to perform. The applicability of this code will depend on the type of hardware used in the end device. The count field indicates the number of times that the control operation should be performed in succession. The on-time field specifies the amount of time the digital output is to be turned on (may not apply to all control types). The off-time field specifies the amount of time the digital output is to be turned off (may not apply to all control types).
5-3
Object Coding:
Control Code 7 6 5 4 3 2 1 0
Count 7 6 5 4 3 2 1 0
On Time 31 Off Time 31 Status 7 6 5 4 3 2 1 0 0 0
SQ4
{Control code Count On-time Off-time Status Reserved } Control code Code Queue Clear Trip/Close } ={ = = = =
= = = = = =
BS8 [0..7] UI8 [0..7] <0..255> UI32 [0..31] <0..232-1, ms> UI32 [0..31] <0..232-1, ms> UI7 [0..6] <0..127> [0..0] <0..1>
BS4 [0..3] <0..15> BS1 [4] <0, normal; 1, requeued> BS1 [5] <0, normal; 1, clear> BS2 [6..7] <00, NUL; 01, Close; 10, Trip>
Narrative: Trip/Close:
This field determines which control relay to activate in a system where a trip and close relay pair is used to energize and de-energize the field points. The NUL value in this field can be used to activate the field point select relay only without activating the trip or close relays. In a system without field point select relays, the NUL value would not perform any control operation. In a system without trip/close relays, this field should always be NUL to indicate a normal digital control operation where the exact control point is inherently known. This field does not support having both the trip and close attributes simultaneously, as this is an illegal operation for the system. The Count field determines how many times the control is executed. If the count is 0, do not execute the control. When the count reaches 0, the control is complete.
DNP Users Group
Count:
5-4
Code:
The control block can be used with devices which support control queuing on a point per point basis or devices which have other control mechanisms. In the former, any control command should be queued for the particular point in question. In the latter, each control is performed until completion before the next control is accepted for that point. If the control code is NUL then no control operation is queued, and the queue is cleared of all controls including the presently running control if the clear attribute is set. When the control function is executed and completed, it is removed from the queue. If the control block for that operation had the queue attribute set, the control operation is re-queued (to the back of the queue) for that point.
Queue:
Clear:
If the control operation has the clear attribute set, all control operations are removed from the queue including the presently running control and this control operation is performed.
The meaning of the code field and the operation to perform is determined by the following: 0: 1: NUL operation. No operation specified. Only the R attribute is processed. Pulse On - The point(s) is turned on for the specified on-time, turned off for the specified off-time and left in the off state. Pulse Off - The point(s) is turned off for the specified off-time, then turned on for the specified on-time and left in the on state. Latch On - This latches the point(s) on. Latch Off - This latches the point(s) off. Undefined. Place operation at the back of the control queue when complete. Cancel currently running operation and remove queued operations on affected points immediately before activating this new operation (if not NUL). The reserved bit of the control point after the operation can be determined if the control output is on. The success or failure of the requested control operation is returned in the status field. The meaning of this field is determined as follows:
2:
3: 4: 5 - 15: Queue: Clear:
5-5
0: 1:
Request accepted, initiated, or queued. Request not accepted as the operate message was received after the arm timer timed out. The arm timer was started when the select operation for the same point was received. No previous matching select message (i.e. an operate message was sent to activate a control point that was not previously armed with the select message. Request not accepted as there were formatting errors in the control request (either select, operate, or direct operate). Control operation not supported for this point. Request not accepted, as the control queue is full or the point is already active. Request not accepted because of control hardware problems.
2:
3:
4: 5:
6:
7 - 127:Undefined.
5-6
DNP Users Group
5.4 PATTERN CONTROL BLOCK

Description: The pattern control block (PCB) object contains digital output control parameters for pattern type controls. These parameters define the type and duration of the digital output for each of the affected points. The PCB object defines all the parameters for the subsequent pattern mask objects which follow this object in the message. These parameters contained in the PCB influence all the pattern mask object(s) that immediately follow the PCB object, until the next PCB in the message. The combination of this object and the pattern mask objects that follow will specify a number (0 or more) of control operations to perform (i.e. the same operation on different points). All these controls must be performed in parallel. The meaning of all fields, attributes, and parameters are identical to the control relay output block except that the queuing attributes are not valid. This is, the pattern control is not meant to be re-queued. Object Coding:
Control Code 7 6 5 4 Count 7 6 5 4 3 2 1 0 3 2 1 0
On Time 31 Off Time 31 Status 7 6 5 4 3 2 1 0 0 0
5-7
5.5 PATTERN MASK

Description: The pattern mask object is used to select from a range of possible control points that have to be executed in parallel. This object is used in conjunction with the PCB object to specify both the control points to operate and the parameters that determine the control operation. If the mask bit is set to active, then the parameters specified in the preceding PCB are applied to a specified point for each pattern mask object and a control operation is generated for the point. Object Coding:
M
BS1 [0..0] Mask = BS1 [0] <0, inactive; 1, active> Narrative: This single-bit pattern mask is typically sent in groups. Transmission of the data object is always performed in complete octets with unoccupied bit positions set to zero. The following example illustrates the packing of n of these data objects.
7 15 6 14 5 13 4 12 3 11 2 10 1 9 0 8
n-1
n-2
n-3
n-4
5-8
DNP Users Group
6. COUNTER OBJECT DEFINITIONS

This section defines the counter data objects using the rules established in section 2.. DECLARATION RULES FOR INFORMATION ELEMENTS.
6.1 32-BIT BINARY COUNTER

Description: The 32-bit binary counter represents an accumulated value. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments indefinitely until a counter clear operation is performed in which case the value is reset to 0. The flag field has the same meaning as in previous objects, with the following inclusion: When set, the roll-over bit indicates that the accumulated value has exceeded the last reported recordable value (232-1). The counter value has been reset to 0 upon the rollover and counting has resumed as normal. This bit is cleared when the counter value (plus the roll-over state) is reported.
6-1
Object Coding:
FLAG 7 6 5 4 3 2 1 0
Value 31 0
SQ2
{FLAG Value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI32 [0..31] <0..232-1>
={ = = = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1 [4] <0, normal; 1, roll-over> BS1 [5] <0, normal; 1, roll-over> BS1 [6] <0> BS1 [7] <0>
6-2
DNP Users Group
6.2 16-BIT BINARY COUNTER

Description: The 16-bit binary counter represents an accumulated value. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments indefinitely until a counter clear operation is performed in which case the value is reset to 0. The flag field has the same meaning as in previous objects, with the following inclusion: When set, the roll-over bit indicates that the accumulated value has exceeded the maximum possible recordable value (216-1). The counter value has been reset to 0 upon roll-over, and counting has resumed as normal. This bit is cleared when the counter value (plus the roll-over state) is reported.
6-3
Object Coding:
FLAG 7 6 5 4 3 2 1 0
Value 15 0
SQ2
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = = =
6-4
DNP Users Group
6.3 32-BIT DELTA COUNTER

Description: The 32-bit delta counter represents a value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments until it is reported at which point it is reset to 0. The flag field has the same meaning as in previous objects, with the following inclusion: When set, the roll-over bit indicates that the accumulated value has exceeded the maximum possible recordable value (232-1). The counter value has been reset to 0 upon roll-over, and counting has resumed as normal. This bit is cleared when the counter value (plus the roll-over state) is reported. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Value 31 0
SQ2
= =
BS8 [0..7] UI32 [0..31] <0..232-1>
={ = = = = = = = = =
6-5
6.4 16-BIT DELTA COUNTER

Description: The 16-bit delta counter represents a value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments until it is reported at which point it is reset to 0. The flag field has the same meaning as in previous objects, with the following inclusion: When set, the roll-over bit indicates that the accumulated value has exceeded the maximum possible recordable value (216-1). The counter value has been reset to 0 upon the roll-over and counting has resumed as normal. This bit is cleared when the counter value (plus the roll-over state) is reported. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Value 15 0
SQ2
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = = =
6-6
DNP Users Group
6.5 32-BIT COUNTER WITHOUT FLAG

Description: The 32-bit binary counter represents an accumulated value. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments indefinitely until a counter clear operation is performed in which case the value is reset to 0. Object Coding:
Value 31 0
SQ2
{Value = }
UI32 [0..31] <0..232-1>
NOTE:
The use of this variation implies that the input point is on-line and that all other flag bits are normal (i.e. this variation implies that flag = 1).
6-7
6.6 16-BIT COUNTER WITHOUT FLAG

Description: The 16-bit binary counter represents an accumulated value. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments indefinitely until a counter clear operation is performed in which case the value is reset to 0. Object Coding:
Value 15 0
SQ2
{Value = }
UI16 [0..15] <0..216-1>
NOTE:
6-8
DNP Users Group
6.7 32-BIT DELTA COUNTER WITHOUT FLAG

Description: The 32-bit delta counter represents a value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments until it is reported at which point it is reset to 0. Object Coding:
Value 31 0
SQ2
{Value = }
UI32 [0..31] <0..232-1>
NOTE:
6-9
6.8 16-BIT DELTA COUNTER WITHOUT FLAG

Description: The 16-bit delta counter represents a value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the current value of the counter at the time of reporting or last reported value from the originating device. This value increments until it is reported at which point it is reset to 0. Object Coding:
Value 15 0
SQ2
{Value = }
UI16 [0..15] <0..216-1>
NOTE:
6-10
DNP Users Group
6.9 32-BIT FROZEN COUNTER

Data Object 21 - Variation: 01 Type: Frozen Static
Description: The 32-bit frozen counter is a compound information object which contains information about a counter which was previously frozen. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen Value 31 0
SQ2
{FLAG Frozen Value FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= = ={ = = = = = = = = =
BS8 [0..7] UI32 [0..31] <0..232-1>
6-11
6.10 16-BIT FROZEN COUNTER

Description: The 16-bit frozen counter is a compound information object that contains information about a counter that was previously frozen. The counter accumulates pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen Value 15 0
SQ2
{FLAG Frozen Value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = = =
6-12
DNP Users Group
6.11 32-BIT FROZEN DELTA COUNTER

Description: The 32-bit frozen delta counter represents a frozen value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen Value 31 0
SQ2
{FLAG Frozen Value FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= = ={ = = = = = = = = =
BS8 [0..7] UI32 [0..31] <0..232-1>
6-13
6.12 16-BIT FROZEN DELTA COUNTER

Data Object 21 - Variation: 04 Description: The 16-bit frozen delta counter represents a frozen value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Type: Frozen Static
Frozen Value 15 0
SQ2
{FLAG Frozen Value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = = =
6-14
DNP Users Group
6.13 32-BIT FROZEN COUNTER WITH TIME OF FREEZE

Description: The 32-bit frozen counter with time of freeze is a compound information object which contains information about a counter which was previously frozen. The counter accumulates pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the time was time of freeze. The time of freeze field contains a time that this object was frozen. This time corresponds to the frozen value so that the current value of this object at time of freeze is frozen value. The flag field has the same meaning as in previous objects.
6-15
Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen Value 31 Time of Freeze 47 0 0
SQ4
{FLAG Frozen value Time of Freeze } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= = =
BS8 [0..7] UI32 [0..31] <0..232-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1[4] <0, normal; 1, roll-over> BS1 [5] <0, normal; 1, roll-over> BS1 [6] <0> BS1 [7] <0>
Narrative: Time of freeze is recorded as milliseconds since midnight, January 1st, 1970, at zero hours, zero minutes, seconds, and milliseconds.
6-16
DNP Users Group
6.14 16-BIT FROZEN COUNTER WITH TIME OF FREEZE

Description: The 16-bit frozen counter with time of freeze is a compound information object which contains information about a counter which was previously frozen. The counter accumulates pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the time was time of freeze. The time of freeze field contains a time that this object was frozen. This time corresponds to the frozen value so that the current value of this object at time of freeze is frozen value. The flag field has the same meaning as in previous objects.
6-17
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
= = =
BS8 [0..7] UI16 [0..15] <0..216-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1[4] <0, normal; 1, roll-over> BS1 [5] <0, normal; 1, roll-over> BS1 [6] <0> BS1 [7] <0>
6-18
DNP Users Group
6.15 32-BIT FROZEN DELTA COUNTER WITH TIME OF FREEZE

Description: The 32-bit frozen delta counter with time of freeze represents a frozen value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the time was time of freeze. The time of freeze field contains a time that this object was frozen. This time corresponds to the frozen value so that the current value of this object at time of freeze is frozen value. The flag field has the same meaning as in previous objects.
6-19
Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen value 31 Time of Freeze 47 0 0
SQ4
= = =
BS8 [0..7] UI32 [0..31] <0..232-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
6-20
DNP Users Group
6.16 16-BIT FROZEN DELTA COUNTER WITH TIME OF FREEZE

Description: The 16-bit frozen delta counter with time of freeze represents a frozen value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the time was time of freeze. The time of freeze field contains a time that this object was frozen. This time corresponds to the frozen value so that the current value of this object at time of freeze is frozen value. The flag field has the same meaning as in previous objects.
6-21
Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen value 15 Time of Freeze 47 0 0
SQ4
= = =
BS8 [0..7] UI16 [0..15] <0..216-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
6-22
DNP Users Group
6.17 32-BIT FROZEN COUNTER WITHOUT FLAG

Description: The 32-bit frozen counter is a compound information object which contains information about a counter which was previously frozen. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. Object Coding:
Frozen Value 31 0
SQ2
{Frozen Value = }
UI32 [0..31] <0..232-1>
NOTE:
6-23
6.18 16-BIT FROZEN COUNTER WITHOUT FLAG

Description: The 16-bit frozen counter is a compound information object which contains information about a counter which was previously frozen. The counter accumulates pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. Object Coding:
Frozen Value 15 0
SQ2
{Frozen Value }
UI16 [0..15] <0..216-1>
NOTE:
6-24
DNP Users Group
6.19 32-BIT FROZEN DELTA COUNTER WITHOUT FLAG

Description: The 32-bit frozen delta counter represents a frozen value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. Object Coding:
Frozen Value 31 0
SQ2
{Frozen Value = }
UI32 [0..31] <0..232-1>
NOTE:
6-25
6.20 16-BIT FROZEN DELTA COUNTER WITHOUT FLAG

Description: The 16-bit frozen delta counter represents a frozen value that has accumulated since the last value was reported. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter when the last counter freeze was performed at the originating device. Object Coding:
Frozen Value 15 0
SQ2
{Frozen Value = }
UI16 [0..15] <0..216-1>
NOTE:
6-26
DNP Users Group
6.21 32-BIT COUNTER CHANGE EVENT WITHOUT TIME

Description: The 32-bit counter change event without time represents a counter value that, since last reported, has exceeded a configured count. This can be accumulated pulses or transitions from a hardware or software point. The current value field shows the value of the counter which generated the event. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Current value 31 0
SQ4
{FLAG Current value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI32 [0..31] <0..232-1>
={ = = = = = = = = =
6-27

Description: The 16-bit counter change event without time represents a counter value that has exceeded a configured deadband. This can be accumulated pulses or transitions from a hardware or software point. The current value field shows the value of the counter which generated the event. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Current value 15 0
SQ4
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = = =
6-28
DNP Users Group
6.23 32-BIT DELTA COUNTER CHANGE EVENT WITHOUT TIME

Description: The 32-bit delta counter change event without time represents a delta counter value that has exceeded a configured deadband. This can be accumulated pulses or transitions from a hardware or software point. The delta value field shows the change of the counter which generated the event. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Delta value 31 0
SQ4
= =
BS8 [0..7] UI32 [0..31] <0..232-1>
={ = = = = = = = = =
6-29
6.24 16-BIT DELTA COUNTER CHANGE EVENT WITHOUT TIME

Description: The 16-bit delta counter change event without time represents a delta counter value that has exceeded a configured deadband. This can be accumulated pulses or transitions from a hardware or software point. The delta value field shows the change of the counter which generated the event. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Delta value 15 0
SQ4
{FLAG Current value FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= = ={ = = = = = = = = =
BS8 [0..7] UI32 [0..16] <0..216-1>}
6-30
DNP Users Group
6.25 32-BIT COUNTER CHANGE EVENT WITH TIME

Description: The 32-bit counter change event with time represents a counter value that has exceeded a configured deadband. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the value of the counter which generated the event. The Time field contains the time that processing generated the event. The flag field has the same meaning as in previous objects.
6-31
Object Coding:
FLAG 7 6 5 4 3 2 1 0
Value 31 Time 47 0 0
SQ4
{FLAG Value Time } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= = =
BS8 [0..7] UI32 [0..31] <0..232-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
Narrative: Time is recorded as milliseconds since midnight, January 1st, 1970, at zero hours, zero minutes, seconds, and milliseconds.
6-32
DNP Users Group
6.26 16-BIT COUNTER CHANGE EVENT WITH TIME

Description: The 16-bit counter change event with time represents a counter value that has exceeded a configured deadband. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the value of the counter which generated the event. The time field contains the time that processing generated the event. The flag field has the same meaning as in previous objects.
6-33
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
= = =
BS8 [0..7] UI16 [0..15] <0..216-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
6-34
DNP Users Group
6.27 32-BIT DELTA COUNTER CHANGE EVENT WITH TIME

Description: The 32-bit delta counter change event with time represents a delta counter value that has exceeded a configured deadband. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the value of the change which generated the event. The time contains the time that processing generated the event. The flag field has the same meaning as in previous objects.
6-35
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
= = =
BS8 [0..7] UI32 [0..31] <0..232-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
6-36
DNP Users Group
6.28 16-BIT DELTA COUNTER CHANGE EVENT WITH TIME

Description: The 16-bit delta counter change event with time represents a delta counter value that has exceeded a configured deadband. This can be accumulated pulses or transitions from a hardware or software point. The value field shows the value of the change which generated the event. The time field contains the time that processing generated the event. The flag field has the same meaning as in previous objects.
6-37
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
= = =
BS8 [0..7] UI16 [0..15] <0..216-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
6-38
DNP Users Group

Data Object 23 - Variation: 01 Type: Frozen Event
Description: The 32-bit frozen counter event without time object represents a frozen counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen value field shows the value at the time of freezing. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen value 31 0
SQ4
{FLAG Frozen value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI32 [0..31] <0..232-1>
={ = = = = = = = = =
6-39
6.30 16-BIT FROZEN COUNTER EVENT WITHOUT TIME

Description: The 16-bit frozen counter event without time represents a frozen counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen value field shows the value at the time of freezing. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen value 15 0
SQ4
{FLAG Frozen value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = = =
6-40
DNP Users Group
6.31 32-BIT FROZEN DELTA COUNTER EVENT WITHOUT TIME

Description: The 32-bit frozen delta counter event without time represents a frozen delta counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen delta value field shows the change in counter value at the time of freezing. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen delta value 31 0
SQ4
{FLAG Frozen delta value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI32 [0..31] <0..232-1>
={ = = = = = = = = =
6-41
6.32 16-BIT FROZEN DELTA COUNTER WITHOUT TIME

Description: The 16-bit frozen delta counter event without time represents a frozen delta counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen delta value field shows the change in counter value at the time of freezing. The flag field has the same meaning as in previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Frozen delta value 15 0
SQ4
{FLAG Frozen delta value } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= =
BS8 [0..7] UI16 [0..15] <0..216-1>
={ = = = = = = = = =
6-42
DNP Users Group
6.33 32-BIT FROZEN COUNTER EVENT WITH TIME

Description: The 32-bit frozen counter event with time represents a frozen counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter at time of freeze. The time of freeze contains the time that the object was frozen. The flag field has the same meaning as in previous objects.
6-43
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
{FLAG Frozen Value Time of Freeze } FLAG On-line Restart Communication lost Remote forced data Local forced data Roll-over Roll-over Reserved Reserved }
= = =
BS8 [0..7] UI32 [0..31] <0..232-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
6-44
DNP Users Group
6.34 16-BIT FROZEN COUNTER EVENT WITH TIME

Description: The 16-bit frozen counter event with time represents a frozen counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the value of the counter at time of freeze. The time of freeze contains the time that the object was frozen. The flag field has the same meaning as in previous objects.
6-45
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
= = =
BS8 [0..7] UI16 [0..15] <0..216-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
Narrative: Time is recorded as milliseconds since midnight, January 1st, 1970 at zero hours, zero minutes, seconds and milliseconds.
6-46
DNP Users Group
6.35 32-BIT FROZEN DELTA COUNTER EVENT WITH TIME

Description: The 32-bit frozen delta counter event with time represents a frozen delta counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the change in the counter at time of freeze. The time of freeze contains the time that the object was frozen. The flag field has the same meaning as in previous objects.
6-47
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
= = =
BS8 [0..7] UI32 [0..31] <0..232-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
Narrative: Time is recorded as milliseconds since midnight, January 1st, 1970 at zero hours, zero minutes, seconds and milliseconds.
6-48
DNP Users Group
6.36 16-BIT FROZEN DELTA COUNTER EVENT WITH TIME

Description: The 16-bit frozen delta counter event with time represents a frozen delta counter value that is reported as an event. This can be accumulated pulses or transitions from a hardware or software point. The frozen value shows the change in the counter at time of freeze. The time of freeze contains the time that the object was frozen. The flag field has the same meaning as in previous objects.
6-49
Object Coding:
FLAG 7 6 5 4 3 2 1 0
SQ4
= = =
BS8 [0..7] UI16 [0..15] <0..216-1> UI48 [0..47] <248 -1 ms>
={ = = = = = = = = =
6-50
DNP Users Group
7. ANALOG INPUT OBJECT DEFINITIONS

This section defines the analog input data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
7.1 32-BIT ANALOG INPUT

Description: The 32-bit Analog Input is an information object used to represent a hardware or software analog point. The 32-bit signed value could represent a digitized signal or calculated value. The Value field shows the current value of the analog input at the time of reporting or the last reported value from the originating device. The flag field has the same meaning as previous objects, with these additions: The out of range field indicates that the digitized signal or calculation has exceeded +231 -1 positively, or -231 negatively. The actual value will be +231 -1 or -231 if it is overrange or under-range. The reference check field indicates that the reference signal used to digitize the analog input is not stable and the resulting digitized value may not be correct.
7-1
Object Coding:
FLAG 7 Current value 31 0 0
SQ2
{FLAG Current value } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= =
BS8 [0..7] I32 [0..31] <231-1..-231>
={ = = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0, normal; 1, forced> BS1 [5] <0, normal; 1, over-range> BS1 [6] <0, normal; 1, error> BS1 [7] <0>
7-2
DNP Users Group
7.2 16-BIT ANALOG INPUT

Description: The 16-bit analog input is an information object used to represent a hardware or software analog point. The 16-bit signed value could represent a digitized signal or calculated value. The value field shows the current value of the analog input at the time of reporting, or the last reported value from the originating device. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +215 1 positively, or -215 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable and the resulting digitized value may not be correct.
7-3
Object Coding:
SQ2
= =
BS8 [0..7] I16 [0..15] <215-1..-215>
={ = = = = = = = =
7-4
DNP Users Group
7.3 32-BIT ANALOG INPUT WITHOUT FLAG

Description: The 32-bit analog input is an information object used to represent a hardware or software analog point. The 32-bit signed value could represent a digitized signal or calculated value. The value field shows the current value of the analog input at the time of reporting, or the last reported value from the originating device. Object Coding:
Current value 31 0
SQ2
{Current value = }
I32 [0..31] <231-1..-231>
NOTE:
7-5
7.4 16-BIT ANALOG INPUT WITHOUT FLAG

Description: The 16-bit analog input is an information object used to represent a hardware or software analog point. The 16-bit signed value could represent a digitized signal or calculated value. The current value field shows the current value of the analog input at the time of reporting, or the last reported value from the originating device. Object Coding:
Current value 15 0
SQ2
{Current value = }
I16 [0..15] <215-1..-215>
NOTE:
7-6
DNP Users Group
7.5 32-BIT FROZEN ANALOG INPUT

Description: The 32-bit frozen analog input is an information object used to represent a frozen hardware or software analog point. The 32-bit signed value could represent a digitized signal or calculated value. The frozen value shows the value of the analog input at the time the last freeze command was performed on this point. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +231 1 positively, or -231 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct. Object Coding:
FLAG 7 Frozen value 31 0 0
SQ2
= =
BS8 [0..7] I32 [0..31] <231-1..-231>
={ = = = = = = = =
7-7
7.6 16-BIT FROZEN ANALOG INPUT

Description: The 16-bit frozen analog input is an information object used to represent a frozen hardware or software analog point. The 16-bit signed value could represent a digitized signal or calculated value. The frozen value shows the value of the analog input at the time the last freeze command was performed on this point. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +215 1 positively, or -215 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct. Object Coding:
SQ2
= =
BS8 [0..7] I16 [0..15] <215-1..-215>
={ = = = = = = = =
7-8
DNP Users Group
7.7 32-BIT FROZEN ANALOG INPUT WITH TIME OF FREEZE

Description: The 32-bit frozen analog input with time of freeze is an information object used to represent a frozen hardware or software analog point. The 32-bit signed value could represent a digitized signal or calculated value. The frozen value shows the value of the analog input at the time specified in time of freeze. The time of freeze field shows the time at which the frozen value was equal to the current value of the analog input. These values are equated on reception of a freeze analog command. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +231 1 positively, or -231 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable and the resulting digitized value may not be correct.
7-9
Object Coding:
Time of Freeze 47 0
SQ2
{FLAG Current value Time of Freeze } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= = =
BS8 [0..7] I32 [0..31] <231-1..-231> UI48[0..47] <0 .. 2 48 >
={ = = = = = = = =
7-10
DNP Users Group
7.8 16-BIT FROZEN ANALOG INPUT WITH TIME OF FREEZE

Description: The 16-bit frozen analog input with time of freeze is an information object used to represent a frozen hardware or software analog point. The 16-bit signed value could represent a digitized signal or calculated value. The frozen value shows the value of the analog input at the time specified in time of freeze. The time of freeze field shows the time at which the frozen value was equal to the current value of the analog input. These values are equated on reception of a freeze analog command. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +215 -1 positively, or -215 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct.
7-11
Object Coding:
Time of Freeze 47 0
SQ2
{FLAG Time of freeze Current value } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= = =
BS8 [0..7] UI48[0..47] <0 .. 2 48 -1> I16 [0..15] <215-1..-215>
={ = = = = = = = =
7-12
DNP Users Group
7.9 32-BIT FROZEN ANALOG INPUT WITHOUT FLAG

Description: The 32-bit frozen analog input is an information object used to represent a frozen hardware or software analog point. The 32-bit signed value could represent a digitized signal or calculated value. The frozen value shows the value of the analog input at the time the last freeze command was performed on this point. Object Coding:
Frozen value 31 0
SQ2
{Current value = }
I32 [0..31] <231-1..-231>
NOTE:
7-13
7.10 16-BIT FROZEN ANALOG INPUT WITHOUT FLAG

Description: The 16-bit frozen analog input is an information object used to represent a frozen hardware or software analog point. The 16-bit signed value could represent a digitized signal or calculated value. The frozen value shows the value of the analog input at the time the last freeze command was performed on this point. Object Coding:
Frozen value 15 0
SQ2
{Current value = }
I16 [0..15] <215-1..-215>
7-14
DNP Users Group
7.11 32-BIT ANALOG CHANGE EVENT WITHOUT TIME

Description: The 32-bit analog change event without time is an information object used to represent a changed hardware or software analog point. The 32-bit signed value could represent a digitized signal or calculated value. The current value field shows the current value of the analog input at the time of reporting, or the last reported value from the originating device. This object will only be reported if the current value and the last reported value differ by a configurable deadband value. This filtering is commonly known as deadbanding. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +231 -1 positively, or -231 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct.
7-15
Object Coding:
SQ2
= =
BS8 [0..7] I32 [0..31] <231-1..-231>
={ = = = = = = = =
7-16
DNP Users Group
7.12 16-BIT CHANGE EVENT WITHOUT TIME

Description: The 16-bit analog change event without time is an information object used to represent a changed hardware or software analog point. The 16-bit signed value could represent a digitized signal or calculated value. The current value field shows the current value of the analog input at the time of reporting, or the last reported value from the originating device. This object will only be reported if the current value and the last reported value differ by a configurable deadband value. This filtering is commonly known as deadbanding. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +215 -1 positively, or -215 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct.
7-17
Object Coding:
SQ2
= =
BS8 [0..7] I16 [0..15] <215-1..-215>
={ = = = = = = = =
7-18
DNP Users Group
7.13 32-BIT ANALOG CHANGE EVENT WITH TIME

Description: The 32-bit analog change event with time is an information object used to represent a changed hardware or software analog point. The 32-bit signed value could represent a digitized signal or calculated value. The current value shows the value of the analog input at the time specified in time. The time field shows the time at which the processing caused the event. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +231 -1 positively, or -231 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct.
7-19
Object Coding:
FLAG 7 Value 31 Time 47 0 0 0
SQ2
{FLAG Time Value } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= = =
BS8 [0..7] UI48[0..47] <0 .. 2 48 -1> I32[0..31] <231-1..-231>
={ = = = = = = = =
7-20
DNP Users Group
7.14 16-BIT ANALOG CHANGE EVENT WITH TIME

Description: The 16-bit analog change event with time is an information object used to represent a changed hardware or software analog point. The 16-bit signed value could represent a digitized signal or calculated value. The current value shows the value of the analog input at the time specified in time. The time field shows the time at which the processing caused the event. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +215 -1 positively, or -215 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct.
7-21
Object Coding:
FLAG 7 Value 15 Time 47 0 0 0
SQ2
{FLAG Time Value } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= = =
BS8 [0..7] UI48 [0..47] <0 .. 2 48 -1> I16 [0..15] <215-1..-215>
={ = = = = = = = =
7-22
DNP Users Group
7.15 32-BIT FROZEN ANALOG EVENT WITHOUT TIME

Description: The 32-bit frozen analog event without time is an information object used to represent a frozen hardware or software analog point that is reported as an event. The 32-bit signed value could represent a digitized signal or calculated value. The frozen value field shows the value of the analog input at the time of freeze. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +231 -1 positively, or -231 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct.
7-23
Object Coding:
SQ2
{FLAG Frozen value } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= =
BS8 [0..7] I32 [0..31] <231-1..-231>
={ = = = = = = = =
7-24
DNP Users Group
7.16 16-BIT FROZEN ANALOG EVENT WITHOUT TIME

Description: The 16-bit frozen analog event without time is an information object used to represent a frozen hardware or software analog point that is reported as an event. The 16-bit signed value could represent a digitized signal or calculated value. The frozen value field shows the value of the analog input at the time of freeze. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +215 -1 positively, or -215 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct.
7-25
Object Coding:
SQ2
{FLAG Frozen value } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= =
BS8 [0..7] I16 [0..15] <215-1..-215>
={ = = = = = = = =
7-26
DNP Users Group
7.17 32-BIT FROZEN ANALOG EVENT WITH TIME

Description: The 32-bit frozen analog event with time is an information object used to represent a frozen hardware or software analog point that is reported as an event. The 32-bit signed value could represent a digitized signal or calculated value. The frozen value field shows the value of the analog input at the time of a freeze. The flag field has the same meaning as previous objects, with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +231 -1 positively, or -231 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct. The time of freeze field shows the time at which the frozen value was equal to the current value of the analog input. These values are equated on reception of a freeze analog command.
7-27
Object Coding:
Time of Freeze 47 0
SQ2
{FLAG Frozen value Time of Freeze } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= = =
BS8 [0..7] I32 [0..31] <231-1..-231> UI48[0..47] <0 .. 2 48 -1>
={ = = = = = = = =
7-28
DNP Users Group
7.18 16-BIT FROZEN ANALOG EVENT WITH TIME

Description: The 16-bit frozen analog event with time is an information object used to represent a frozen hardware or software analog point that is reported as an event. The 16-bit signed value could represent a digitized signal or calculated value. The frozen value field shows the value of the analog input at the time of a freeze. The Flag field has the same meaning as previous objects with these additions: The over-range field indicates that the digitized signal or calculation has exceeded +215 -1 positively, or -215 negatively. The actual value field can be ignored as its value is not defined. The reference check field indicates that the reference signal used to digitize the analog input is not stable, and the resulting digitized value may not be correct. The time of freeze field shows the time at which the frozen value was equal to the current value of the analog input. These values are equated on reception of a freeze analog command.
7-29
Object Coding:
Time of Freeze 47 0
SQ2
{FLAG Frozen value Time of Freeze } FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
= = =
BS8 [0..7] I16 [0..15] <215-1..-215> UI48[0..47] <0 .. 2 48 -1>
={ = = = = = = = =
7-30
DNP Users Group
8. ANALOG OUTPUT OBJECT DEFINITIONS

This section defines the analog output data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
8.1 32-BIT ANALOG OUTPUT STATUS

Description: The 32-bit analog output status information object represents the actual value of an analog output or software point and associated status. The actual value field contains the current value of the analog output. The flag field has the same meaning as previous objects.
8-1
Object Coding:
FLAG 7 6 5 4 3 2 1 0
Current value 31 0
SQ3
{FLAG Current value } FLAG On-line Restart Communication lost Remote forced data Reserved Reserved Reserved Reserved }
= =
BS8 [0..7] I32 [0..31] <231-1..-231>
={ = = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, unlock; 1, forced> BS1 [4] <0> BS1 [5] <0> BS1 [6] <0> BS1 [7] <0>
Narrative: This object can be returned after an analog output operation is performed in order to determine the success of the operation.
8-2
DNP Users Group
8.2 16-BIT ANALOG OUTPUT STATUS

Description: The 16-bit analog output status information object represents the actual value of a hardware DAC analog output or software point and associated status. The actual value field contains the current value of the analog output. The flag field has the same meaning as previous objects. Object Coding:
FLAG 7 6 5 4 3 2 1 0
Current value 15 0
SQ3
{FLAG Current value } FLAG On-line Restart Communication lost Remote forced data Reserved Reserved Reserved Reserved }
= =
BS8 [0..7] I16 [0..15] <215-1..-215>
={ = = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, unlock; 1, forced> BS1 [4] <0> BS1 [5] <0> BS1 [6] <0> BS1 [7] <0>
Narrative: This object can be returned after an analog output operation is performed in order to determine the success of the operation.
8-3
8.3 32-BIT ANALOG OUTPUT BLOCK

Description: The 32-bit analog output information object represents the desired value of a hardware DAC analog output or software point. The value represented is merely logical, as the value may be scaled and/or manipulated before any output level is set. The requested value field contains the desired value of the analog output. The actual value of the analog output is returned in the analog output status object. The control status field indicates the status of the analog control operation, in the same way that the control delay output block does. The definition of this field is the same as the control relay output block. Object Coding:
Requested value 31 Control Status 7 0 0
Requested value = I32 [0..31] <231-1..-231> Status = I8 [0..7] <0..255> This is used in a control request/response.
8-4
DNP Users Group
8.4 16-BIT ANALOG OUTPUT BLOCK

Description: The 16-bit analog output block information object represents the desired value of a hardware DAC analog output or software point. The value represented is merely logical, as the value may be scaled and/or manipulated before any output level is set. The requested value field contains the desired value of the analog output. The actual value of the analog output is returned in the analog output status object. The control status field indicates the status of the analog control operation in the same way as the control relay output block. The definition of this field is the same as the control relay output block. Object Coding:
Requested value 15 Control Status 7 0 0
I16 I8
Requested value Status
= =
I16 [0..15] <215-1..-215> I8 [0..7] <0..255>
8-5
9. TIME OBJECT DEFINITIONS

This section defines the time data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
9.1 TIME AND DATE

Data Object 50 - Variation: 01 Description: The time and date object is an information object that represents the absolute time of day and date. This object should be used for time-synchronization. Object Coding:
Absolute Time 7 15 23 31 39 47 6 14 22 30 38 46 5 13 21 29 37 45 4 12 20 28 36 44 3 11 19 27 35 43 2 10 18 26 34 42 1 9 17 25 33 41 0 8 16 24 32 40
Absolute Time=
UI48 [0..47] <0..248-1, msec>
Narrative: Absolute Time is recorded as milliseconds since midnight, January 1st, 1970, at zero hours, zero minutes, zero seconds, and milliseconds.
9-1
9.2 TIME AND DATE WITH INTERVAL

Data Object 50 - Variation: 02 Description: The time and date with interval represents both an absolute time and an interval time. The absolute time represents a starting time (or base time), and the interval time is a positive offset from the base time. The interval could be applied several times to the base time in order to specify a sequence of periodic times. For example, this can be used to specify a sequence of times for periodic freezing of objects. The absolute time field specifies the base time. This time is the real time-of-day. The interval field specifies the periodic interval or offset from the base time.
9-2
DNP Users Group
Object Coding:
Absolute time 7 15 23 31 39 47 6 14 22 30 38 46 5 13 21 29 37 45 4 12 20 28 36 44 3 11 19 27 35 43 2 10 18 26 34 42 1 9 17 25 33 41 0 8 16 24 32 40
Interval 7 15 23 31 6 14 22 30 5 13 21 29 4 12 20 28 3 11 19 27 2 10 18 26 1 9 17 25 0 8 16 24
SQ2
{Absolute time Interval }
= =
UI48 [0..47] <0..248 -1, msec> UI32 [0..31] <0..232-1, msec>
Narrative: Absolute time is recorded as milliseconds since midnight, January 1st, 1970, at zero hours, zero minutes, zero seconds, and milliseconds.
9-3
9.3 TIME AND DATE CTO

Data Object 51 - Variation: 01 Description: The time and date CTO (common time of occurrence) object is an information object that represents the absolute time of day. This object should be used in conjunction with other objects that contain time references. This object is a base time to which a relative (incremental) time can be added, or from which it can be subtracted, in order to obtain another absolute time reference. Object Coding:
Absolute Time 7 15 23 31 39 47 6 14 22 30 38 46 5 13 21 29 37 45 4 12 20 28 36 44 3 11 19 27 35 43 2 10 18 26 34 42 1 9 17 25 33 41 0 8 16 24 32 40
Absolute time =
UI48 [0..47] <0..248-1, msec>
Narrative: Absolute time is recorded as milliseconds since midnight, January 1st, 1970, at zero hours, zero minutes, zero seconds, and milliseconds.
9-4
DNP Users Group
9.4 UN-SYNCHRONIZED TIME AND DATE CTO

Data Object 51 - Variation: 02 Description: The un-synchronized time and date CTO object is an information object that represents the relative-absolute time of day. This object should be used in conjunction with other objects that contain time references. This object is a relative base time to which a relative (incremental) time can be added, or from which it can be subtracted, in order to obtain another relative-absolute time reference. The real absolute time can be calculated by the message receiver, based on the reception time of the message containing this object. Any objects that follow this object, and come before the next common-time object that contains relative time, must be corrected using this relative-absolute time value. Relative-absolute time is the un-synchronized time-of-day at the station sending this object (i.e. the responding station). Object Coding:
Relative Absolute Time 7 15 23 31 39 47 6 14 22 30 38 46 5 13 21 29 37 45 4 12 20 28 36 44 3 11 19 27 35 43 2 10 18 26 34 42 1 9 17 25 33 41 0 8 16 24 32 40
Relative-absolute time
UI48 [0..47] <0..248-1, msec>
Narrative: Relative-absolute time is recorded as milliseconds since midnight, January 1st, 1970, at zero hours, zero minutes, zero seconds, and milliseconds.
9-5
9.5 TIME DELAY COARSE

Data Object 52 - Variation: 01 Description: The time delay coarse information object represents a relative time that indicates a time period starting from the time of message reception. Object Coding: Seconds 7 15 6 14 5 13 4 12 3 11 2 10 1 9 0 8
Seconds =
UI16 [0..15] <0..65,535, seconds>
9-6
DNP Users Group
9.6 TIME DELAY FINE

Data Object 52 - Variation: 02 Description: The time delay fine information object represents a relative time that indicates a time period starting from the time of message reception. This object can be used in timesynchronization to perform path delay measurement calculations or other functions that require time-based calibration. Object Coding:
Milliseconds 7 15 6 14 5 13 4 12 3 11 2 10 1 9 0 8
Milliseconds =
UI16 [0..15] <0..65,535, milliseconds>
9-7
9-8
DNP Users Group
10. CLASS OBJECT DEFINITIONS

This section defines the class data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
10.1 CLASS 0 DATA

Data Object 60 - Variation: 01 Description: The class 0 data object is an object place-holder that specifies a class of zero or more information elements. These elements can be entire object types, a specific variation, certain points of the variation, or any combination of these. The data specified by this object type is configurable within the responding station. Class 0 data is potentially any information object not assigned to class 1, 2, or 3. That is, class 0 data is non-priority data. Object Coding: None. Narrative: The class 0 data object does not carry any information in itself, and therefore does not have an object coding. Class 0 is a null class to which all data objects not assigned to other classes can belong by default.
10-1
10.2 CLASS 1 DATA

Data Object 60 - Variation: 02 Description: The class 1 data object is an object place-holder that specifies a class of zero or more information elements. These elements can be entire object types, a specific variation, certain points of the variation, or any combination of these. The data specified by this object type is configurable within the responding station. The responding station does not send the class 1 data object, as it does not contain any actual information, but is simply an identifier for other objects. Object Coding: None. Narrative: The class 1 data object is used to request a configured group, usually changes, of information objects from a responding station. This data object does not carry any information in itself, and therefore does not have an object coding. Typically, class 1 data has higher priority than class 2, class 3, and class 0 data.
10-2
DNP Users Group
10.3 CLASS 2 DATA

Data Object 60 - Variation: 03 Description: The class 2 data object is an object place-holder that specifies a class of zero or more information elements. These elements can be entire object types, a specific variation, certain points of the variation, or any combination of these. The data specified by this object type is configurable within the responding station. The responding station does not send the class 2 data object, as it does not contain any actual information, but is simply an identifier for other objects. Object Coding: None. Narrative: The class 2 data object is used to request a configured group, usually changes, of information objects from a responding station. This data object does not carry any information in itself, and therefore does not have an object coding.
10-3
10.4 CLASS 3 DATA

Data Object 60 - Variation: 04 Description: The class 3 data object is an object place-holder that specifies a class of zero or more information elements. These elements can be entire object types, a specific variation, certain points of the variation, or any combination of these. The data specified by this object type is configurable within the responding station. The responding station does not send the class 3 data object, as it does not contain any actual information, but is simply an identifier for other objects. Object Coding: None. Narrative: The class 3 data object is used to request a configured group, usually an event, of information objects from a responding station. The data object does not carry any information in itself, and therefore does not have an object coding.
10-4
DNP Users Group
11. FILE OBJECT DEFINITIONS

This section defines the file data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
11.1 FILE IDENTIFIER

Data Object 70 - Variation: 01 Description: The file identifier object is an information object that represents information about a file in a network file system. This object is intended to be used for transferring large blocks of data that do not follow the format of an existing data object. In particular, this object is suitable for uploading and downloading configuration files to remote devices or data concentrators. File operations are defined for this object to allow copying, deleting, etc. of a file. The contents of the file object and the exact procedure to perform on the file will not be interpreted by the Application Layer, and so must be performed by the user of the Application Layer. Networking Capability: The File_Name field defines a logical name of a file or device. The receiving application should interpret this name as a network file name. The root (or /) represents the root of the host file system or receiving node. Sub-directories off of the root are interpreted as branches off of the root. A branch can be a new directory, or more importantly, the directory can be a remote file system which resides in a remote device that is accessible from the current node. When an application receives a file that specifies a directory or file that does not reside in the current file system, the application must do whatever is necessary to obtain the file from the specified device. If the remote device is a DNP 3 device, then the following rules apply: On reception of a non-local file request, the application shall forward the request (in its entirety) to the appropriate DNP 3 device.
11-1
The File_Name field will be modified so that the root of the remote device is specified by the File_Name field. This means stripping off any paths that were used to actually derive the name of the remote device. For example, an IED configuration is sent from a host through two data concentrators DC1 and DC2. The name from the Host to DC1 is: \DC2\IED\config1 The name from the DC1 to DC2 is: \IED\config1 The name from the DC2 to IED is: \config1 In this case DC2 and IED were logical directories which specified remote devices and config1 was the name of a physical file. Object Coding: This is not a fixed format object, but it is a variable format/sized object. This part of the object is sent in a request.
31 Attributes End_Record File_Size Time_Of_Creation Permission File_ID Owner_ID Group_ID Status X File_Name File_Function 0 24 23 16 15 File_Type 87 Name_Size Start_Record 0
11-2
DNP Users Group
The File_Name field consists of 0 .. x bits where x = Name_Size * 8 and Name_Size = 0 .. 65535. The file identifier object is sent in a DNP application request message to a remote device using the Application Layer WRITE request function code. A device responds to a request (or spontaneously reports) the file identifier object with an Application Layer RESPONSE or UNSOLICITED RESPONSE function code (where appropriate). File_Name: Name of file to perform operation on. Consists of 1 or more of the characters A .. Z, a..z, 0 .. 9, ".", "_", "\" and "-" ONLY, where " is a delimiter, and where the hyphen cannot be used as the first character of the file name. The size of this field is determined by the Name_Size field below. The name can contain all path information starting from the root (i.e. "\" of the file system. The name can contain spaces ONLY to separate the file path/name from program arguments. Number of characters in File_Name above. Function to perform on specified records of file or on file system at user layer. Includes the following: APPEND, DELETE, INSERT, WRITE, ERASE, INFO, CWD, PWD, EXECUTE and READ. The following values are defined: Add data records specified at END of file. The Start_Record field indicates the number of records to append to the file and also the number of data records following the file identifier header in the message. The data records that follow the header are described in the WRITE function code (below). The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE, and the status field set to the status of the requested operation. Remove the specified records from the file (i.e. file shrinks). The Start_Record indicates the first record to delete and the End_Record indicates the last record to delete. There are no data records with this request. The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE, and the status field set to the status of the requested operation.
Name_Size: File_Function:
0 = APPEND:
1 = DELETE:
11-3
2 = INSERT:
Insert these records at the place specified by the Start_Record field and continuing to End_Record field (i.e. the file grows in size). The number of data records following the file identifier header in the message is End_Record - Start_Record + 1. The data records that follow the header are described in the WRITE function code (below). The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE, and the status field set to the status of the requested operation. Place these records at the place specified by Start_Record field and continuing to End_Record field (i.e. the file can potentially grow, and previous data is replaced by these records). The number of data records following the file identifier header in the message is End_Record Start_Record + 1. The data records that follow the header are described below. The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE, and the status field set to the status of the requested operation.
Record_Size
3 = WRITE:
Data x 0 15
Where:
x = Record_Size * 8 Record_Size = 0 .. 65535
4 = ERASE:
Clear (to NUL) or ERASE all records specified in Start and End record fields (i.e. the file stays same size, BUT data is cleared). There are no data records in this message. The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE, and the status field set to the status of the requested operation.
11-4
DNP Users Group
5 = INFO:
This request is used to obtain INFORMATION on the specified file. The device should respond with the file identifier object header with all fields filled in, the File_Function set to RESPONSE and the status field set to the status of the requested operation. The File_Name field can be set to the special name "/" which indicates ALL files. The device should respond with file identifier object headers for each file in the device's file system. If the device has only one file (and no directories) then this one file's file identifier object header should be returned. Change working directory (CWD) to path specified in File_Name. The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE, the File_Name field set to the new working directory, and the status field set to the status of the requested operation. Return the present working directory (PWD) in File_Name. The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE, the File_Name field set to the current working directory, and the status field set to the status of the requested operation. Start or EXECUTE the application specified by File_Name and pass it parameters that follow the file name portion of File_Name (separated by spaces). The device should respond with the file identifier object with all available fields filled in, the File_Function field set to RESPONSE and the status field set to the status of the requested operation.
6 = CWD:
7 = PWD:
8 = EXEC:
11-5
9 = READ:
Read the specified records of file. The Start_Record specifies the first record to READ, and the End_Record specifies the last record to READ. If the Start_Record field is 0, and the End_Record field is 65535, then the device should respond with all available records. The File_Size field in the response should indicate the total size of the file. The device should respond with the file identifier object with all available fields filled in, and all requested data records (if possible), the File_Function field set to RESPONSE, the Start_Record and End_Record should be set to the beginning and end data records returned in the response, and the status field set to the status of the requested operation. The number of data records following the file identifier header in the message is End_Record Start_Record + 1. The data records that follow the header are described above under the WRITE function code. This function code is used to indicate a response to a request. The contents of this message are defined by the function code in the request message. The permission field specifies the READ, WRITE, and EXECUTE privileges for the file owner, the file owner's group and the world (all others). The READ privilege gives the user the right to read the file (READ, PWD, CWD, INFO request). The WRITE privilege gives the user the right to change the file (APPEND, DELETE, INSERT, WRITE, ERASE). The EXECUTE privilege gives the user the right to run the specified application (EXEC request). Indicates to a receiving application how to interpret the contents of the file object. Valid types are: 8-bit binary, 8-bit ASCII, 7-bit ASCII, EBCDIC, BCD, Baudot, International Baudot. The following values are associated:
255 = RESP:
Permission:
File_Type:
0 = 8-bit binary (un-coded octets of binary) 1 = 8-bit ASCII (extended ASCII characters) 2 = 7-bit ASCII (ASCII characters) 3 = EBCDIC (extended binary coded decimal) 4 = BCD (binary coded decimal) 5 = Baudot (5-bit Baudot) 6 = International Baudot (6-bit Baudot)
11-6
DNP Users Group
Attributes:
File attributes consisting of: regular, temporary, directory, or FIFO. The following values are associated: Regular file is a real PERMANENT file. Temporary file is TEMPORARY and MUST be saved if changes are to be kept. Directory is a file of files (cannot be read). FIFO is a first-in-first-out queue and can be used for inter-process communication (analogous to a socket or pipe). The status of the requested operation, consisting of: OK, Doesn't_exist, Out_of_Space, No_Permission and File_Busy. The following values are associated:
0: 1:
2: 3:
Status:
0: 1:
OK indicates that the requested operation was successful. Doesn't_exist indicates that the file name is not contained in the file system. Out_of_Space indicates that the file operation caused the file to exceed its maximum size as determined by the User ID, Group ID, and Permission. No_Permission indicates that the file owner does not have enough privileges for the operation requested. File_Busy indicates that the file could not be delivered to the destination. Number of total bytes in file specified by File_Name. The start record number of file. A start record of 0 indicates the start of the file, and a start record of 65535 indicates the last record. The end record number of file, similar to the Start_record. An end record of 65535 combined with a start record of 0 in a READ request indicates the entire file. Size in bytes of each individual data record excluding Record_Size field. Time that the file was created or last modified. This field has the same format as Object 50 Variation 1. Unique identifier for the owner of the file. 11-7
2:
3:
4: File_Size: Start_Record:
End_Record:
Record_Size:
Time_of_Creation:
Owner_ID:
Group_ID: File_ID:
Unique identifier for the owner's group. Unique integer identifier for the file. This field can also be used to hold the error check (typically 16-bit CRC) for the file. In this case, the File_ID is only unique when concatenated with the File_Name and the Time_Of_Creation. Actual data bytes that make up the file record. These 8-bit objects are interpreted according to the File_Type field. The contents of the Data field will not be interpreted by the DNP Application Layer.
Data:
11-8
DNP Users Group
12. DEVICE OBJECT DEFINITIONS

This section defines the device data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
12.1 INTERNAL INDICATIONS

Data Object 80 - Variation: 01 Description: The internal indications is an information element used to convey internal states and diagnostic results of a responding station. This information can be used by a receiving station to perform error recovery or other functions. The number of internal indications objects sent in a message is device-dependent. Object Coding:
0
BS1 [0..0] State = BS1 [0] <0,1> Narrative: Transmission of the data object is always performed in complete octets, with unoccupied bit positions set to zero. The following example illustrates the packing of n of these data objects.
7 15 6 14 5 13 4 12 3 11 2 10 1 9 0 8
n-1
n-2
n-3
n-4
12-1
12.2 STORAGE OBJECT

Data Object 81 - Variation: 01 Description: The storage object is an information element used to convey the status of internal buffers and storage areas for specific data types. The group field indicates the group (or data type) that the status field corresponds to. The variation field indicates the variation of the object that the status field corresponds to. The group and variation fields together specify the exact data type. The status field shows what percentage of the buffer space allocated for this data type is currently used up. The overflow bit indicates that the buffer space for the specified data type has been over-utilized, and data objects have been lost.
12-2
DNP Users Group
Object Coding:
STATUS 7 6 5 4 3 2 1 0
GROUP 7 VARIATION 7 0 0
Storage Object
={ Status Group Variation } ={ Percent= Overflow }
= = =
BS8 [0..7] UI8 [0..7] <0..255> UI8 [0..7] <0..255>
Status
BS7 [0..6] <0..100> = BS1 [7] <0, 1; Overflow>
Narrative: The storage object is used to indicate the status of buffer, queues, or other storage areas within the sending device. The object is generated by the device as configured in the device and described in the particular device profile.
12-3
12.3 DEVICE PROFILE

Data Object 82 - Variation: 01 Description: The device profile object provides for inter-operability between different DNP devices which use only a sub-set of the DNP Application Layer function codes and data objects. This object describes the station acting as a DNP master, and the valid function codes and objects that the slave device supports. In addition, the range of indices for each object/variation is also given so that configuration can be done on a dynamic basis. Principle of operation: The device profile object is intended to be sent by a slave device ONLY when the request sent by the master is not recognizable, un-parsable, or objects referenced in the request are not supported. Coincident with this message would be internal indications indicating a problem with parsing. Alternately, if the slave is configured in a quiescent environment, the slave could report (spontaneously) the device profile object upon start-up. The master, upon reception of this object, can change its polling scheme, poll request message, limit or expand the assumed functionality of the slave, or re-configure the master database with objects specified in this object. If the master station is less sophisticated, the slave station can be marked off-line, and manual re-configuration would be necessary to obtain proper communications again. The device profile object consists of two sections. The first section, functions, specifies the supported DNP Application Layer function codes. The second section, objects, specifies the range of indices valid for each object/variation combination. Essentially, the objects section is a sample master poll object header for each object/variation. It is implied by the type of object what type of operation (function) can be performed on it so there is no need to map each function code to a set of objects. The functions field is an array of bits indicating support or non-support for each function code. The bit positions 0 .. 63 correspond to DNP Application Layer function codes 0 to 63. For request function codes beyond 63, another functions field can follow the ObjectHeaders. The NumObjects field specifies how many sample object headers follow. The ObjectHeader fields have the same form as a DNP Application Layer object header. As a minimum, the header consists of the object, variation, qualifier, and 8-bit quantity. This means that to describe most object variations, only four bytes are needed.
12-4
DNP Users Group
Object Coding:
Functions 63 NumObjects (n) 15 ObjectHeader 1 Quantity 7 0 7 Qualifier 0 7 Variation 0 7 Object 0 0 0
ObjectHeader 2 Quantity 7 0 7 Qualifier 0 7 Variation 0 7 Object 0
ObjectHeader n Quantity 7 0 7 Qualifier 0 7 Variation 0 7 Object 0
SQ2
{Functions = NumObjects = }
BS64 [0..63] UI16 [0.15] <0..65535>
Each object header that follows has a variable format determined by the rules for constructing Application Layer object headers. Some sample headers are: Object Header = SQ4 { Object Variation Qualifier Quantity }
= = = =
UI8 [0..7] <0..255> UI8 [0..7] <0..255> UI8 [0..7] <0..255> UI8 [0..7] <0..255>
12-5
Object Header = SQ5 { Object Variation Qualifier Start Stop } Object Header = SQ5 { Object Variation Qualifier Start Stop }
= = = = =
UI8 [0..7] <0..255> UI8 [0..7] <0..255> UI8 [0..7] <0..255> UI8 [0..7] <0..255> UI8 [0..7] <0..255>
= = = = =
UI8 [0..7] <0..255> UI8 [0..7] <0..255> UI8 [0..7] <0..255> UI16 [0..15] <0..65535> UI16 [0..15] <0..65535>
12-6
DNP Users Group
12.4 PRIVATE REGISTRATION OBJECT

Data Object 83 - Variation: 01 Type: Static\Event\Frozen Static\Frozen Event
Description: This private registration object (PRO) object type is reserved for vendor-specific definition. The object consists of a fixed header to provide for transparent data transfer, and a unique registration number of the following object. The description of the contents is entirely at the discretion of the vendor. The Vendor field is a four-byte ASCII vendor name. The Private Registration Number (PRN) field is a vendor designated object I.D. The Len field contains the length of the Data Objects field in octets. The Data Objects field contains the vendor's data (variable size and format) as described by the PROD object. Object Coding:
VENDOR 31 PRN 15 LEN 15 DATA OBJECTS 0 0 0 0
SQx
{Vendor PRN LEN SQn }
= = = =
U132 [0..232-1] U116[0..216-1] U116 [0..216-1] Length of objects in <octets> sequence of n basic DNP objects
12-7
12.5 PRIVATE REGISTRATION OBJECT DESCRIPTOR

Description: This object type is reserved for vendor private registration object description. The object is matched one-to-one with its PRO object. The object consists of a fixed header to provide for transparent data transfer, and a unique registration number of the following object. The description of the contents is entirely at the discretion of the vendor. The private registration object description (PROD) object maintains a one-to-one relationship with the PRO object, and can be used to parse the PRO into basic DNP Objects for processing. The PROD consists of one element for each corresponding element of the PRO. Each element consists in turn of a set of DNP object and variation numbers. The Vendor field is a four-byte ASCII vendor name. The Private Registration Number (PRN) field is a vendor designated object I.D. The Count field specifies the number of object definitions that follow this field. Each object definition consists of the three fields: quantity, object and variation. The Quantity field specifies the number of objects, specified by the object and variation fields, which will be found in the PRO object.
12-8
DNP Users Group
Object Coding:
VENDOR 31 PRN 15 COUNT 15 QUANTITY 15 OBJECT 7 VARIATION 7 QUANTITY 15 OBJECT 7 VARIATION 7 QUANTITY 15 OBJECT 7 VARIATION 7 0 0 0 0 0 0 0 0 0 0 0 0
SQx
{Vendor PRN COUNT SQn
= = = = {
UI32 [0..232-1] UI16 [0..216-1] UI16 [0..216-1] Sequence of n basic DNP object definitions Object = U18 [0..28-1] Variation = U18 [0..28-1] Quantity = U18 [0..216-1]
} }
12-9
The following illustrations serve as examples for more clarification: PROD:

(blank) B B 0 0 A 16 3 2 1 2 2 21 2 5 30 1
In the above example: B, B, and A, represent the vendor name. PRN is private object #16 for vendor A B B. Count specifies that three definitions follow, with each definition consisting of quantity, object, and variation.
12-10
DNP Users Group
The corresponding PRO object is:

(blank) B B 0 0 A 16 33 binary input 1 binary input 2 Counter 1 Counter 2 Analog 1 Analog 2 Analog 3 Analog 4 Analog 5
12-11
13. APPLICATION OBJECT DEFINITIONS

This section defines the application data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
13.1 APPLICATION IDENTIFIER

Data Object 90 - Variation: 01 Description: The application identifier object is an information object used to represent an application or operating system process within a device. This object is used in conjunction with the application functions of the application layer to control software applications. This object has no defined format and is simply used as a place holder. The free-format qualifier of the application layer should be used to identify the application in question, or if the application is unknown, the ALL qualifier should be used to specify all relevant applications.
13-1
14. ALTERNATE NUMERIC OBJECT DEFINITIONS

This section defines the alternate or custom numeric representation data objects using the rules established in section 2. DECLARATION RULES FOR INFORMATION ELEMENTS.
14.1 SHORT FLOATING POINT

Data Object 100 - Variation: 01 Description: The short floating point information object represents a calculated or measured scientific value. The format of this object complies with the IEEE-754 standard for floating-point number representation. The value field holds the actual floating point number and follows the format for a short real as specified by the IEEE-754 standard. The flag field holds information about the point and has the same meaning as previous objects. The units field determines the units of the value field. This is the scientific or engineering units associated with the measured or calculated quantity.
14-1
Object Coding:
Units 7 0 Value Sign 0 0 7 Exponent 0 Significant 22 0 7 Flag 0
FLAG On-line Restart Communication lost Remote forced data Local forced data Over-range Reference check Reserved }
={ = = = = = = = =
BS1 [0] <0, off-line; 1, on-line> BS1 [1] <0, normal; 1, restart> BS1 [2] <0, normal; 1, lost> BS1 [3] <0, normal; 1, forced> BS1 [4] <0> BS1 [5] <0, normal; 1, over-range> BS1 [6] <0, normal; 1, error> BS1 [7] <0>
Narrative: The absolute value can be derived from the value field as follows: Absolute_Value where: Sign: Exponent: Significant: si = = 1.s0 s1 s2 s3 s4 .. s22 x 2 (Exp -127) Significant[i..i] and Exp= Exponent[0..7]
0 if number is positive, and 1 if the number is negative. Power of 2 applied to 1. Significant. Significant binary digits in value.
14-2
DNP Users Group
The units field has the following defined values: 0: Volts p-p (peak-to-peak voltage) 1: Amperes p-p (peak-to-peak current) 2: Volts RMS 3: Amperes RMS 4: KW or kilowatts (real power or volt-amps resistive) 5: KVA or kilo volt-amps (volt-amps total) 6: KVAR or kilovars (imaginary power or volt-amps reactive) 7: KwH (kilowatt hours) 8: KVARH (kiloVAR hours) 9: PF (power factor) 10: Hz (frequency in cycles per second) 11: w (frequency in radians) 12: C (degrees Celsius) 13: F (degrees Fahrenheit) 14: K (degrees Kelvin) 15: N (force in Newtons) 16: kg (mass in kilograms) 17: m/s2 (acceleration) 18: N/m2 (pressure in Newtons per square meter) 19: N*m (torque in Newton-meters)
14-3
14.2 LONG FLOATING POINT

Data Object 100 - Variation: 02 Description: The long floating point information object represents a calculated or measured scientific value. The format of this object complies with the IEEE-754 standard for floating-point number representation. The value field holds the actual floating point number and follows the format for a long real as specified by the IEEE-754 standard. The flag field holds information about the point and has the same meaning as previous objects. The units field determines the units of the value field. This is the scientific or engineering units associated with the measured or calculated quantity. Object Coding:
Units 7 0 Value Sign 0 0 Exponent 10 0 Significant 51 0 7 Flag 0
={ = = = = = = = =
14-4
DNP Users Group
14-5
14.3 EXTENDED FLOATING POINT

Data Object 100 - Variation: 03 Description: The extended floating point information object represents a calculated or measured scientific value. The format of this object complies with the IEEE-754 standard for floating-point number representation. The value field holds the actual floating point number and follows the format for a temp real as specified by the IEEE-754 standard. The flag field holds information about the point and has the same meaning as previous objects. The units field determines the units of the value field. This is the scientific or engineering units associated with the measured or calculated quantity. Object Coding:
Units 7 0 Value Sign 0 0 Exponent 14 0 Significant 63 0 7 Flag 0
={ = = = = = = = =
14-6
DNP Users Group
14-7
14.4 SMALL-PACKED BINARY CODED DECIMAL

Data Object 101 - Variation: 01 Description: The small-packed binary coded decimal information object represents a sequence of BCD digits. Each BCD digit can represent a variety of information from control outputs to analog inputs. Object Coding:
Digit 4 3 0 3 Digit 3 0 3 Digit 2 0 3 Digit 1 0
SPBCD
= SQ4 { Digit1 Digit2 Digit3 Digit4 }
= = = =
UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10>
14-8
DNP Users Group
14.5 MEDIUM-PACKED BINARY CODED DECIMAL

Data Object 101 - Variation: 02 Description: The medium-packed binary coded decimal information object represents a sequence of BCD digits. Each BCD digit can represent a variety of information from control outputs to analog inputs. Object Coding:
Digit 8 3 0 3
Digit 7 0 3
Digit 6 0 3
Digit 5 0
MPBCD =
SQ8 { Digit1 Digit2 Digit3 Digit4 Digit5 Digit6 Digit7 Digit8 }
= = = = = = = =
UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10>
14-9
14.6 LARGE-PACKED BINARY CODED DECIMAL

Data Object 101 - Variation: 03 Description: The large-packed binary coded decimal information object represents a sequence of BCD digits. Each BCD digit can represent a variety of information from control outputs to analog inputs. Object Coding:
Digit 8 3 0 3
Digit 7 0 3
Digit 6 0 3
Digit 5 0
Digit 12 3 0 3
Digit 11 0 3
Digit 10 0 3
Digit 9 0
Digit 16 3 0 3
Digit 15 0 3
Digit 14 0 3
Digit 13 0
LPBCD
SQ16 { Digit1= Digit2= Digit3= Digit4= Digit5= Digit6= Digit7= Digit8= Digit9= Digit10= Digit11= Digit12= Digit13= Digit14= Digit15= }
UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10> UI4 [0..3] <0..10>
14-10
DNP Users Group
LIST OF ABBREVIATIONS AND ACRONYMS

ASCII BCD BIN BS CRC CTO CTO CWD DA DAC DNP EBCDIC EXEC F FIFO I ID IEC IEEE LEN LPBCD MPBCD MSEC OS American Standard Code for Information Interchange binary coded decimal bit string cyclic redundancy check common time object common time of occurrence change working directory distributed automation data acquisition and control Distributed Network Protocol extended binary coded decimal execute fixed point first-in-first-out integer identification International Electrotechnical Commission Institute of Electrical and Electronics Engineers length large-packed binary coded decimal medium-packed binary coded decimal millisecond octet string
PCB PRN PRO PROD PWD R RESP RMS SCADA SPBCD UF UI
pattern control block private registration number private registration object private registration object description (return to) present working directory real response root mean squared supervisory control and data acquisition small-packed binary coded decimal unsigned fixed point unsigned integer
DNP Users Group

Document Revision History

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Document Revision History

Загружено:

Авторское право:

Доступные форматы

DOCUMENT REVISION HISTORY

DNP Users Group

DNP V3.00 DATA OBJECT LIBRARY

NOTICE OF RIGHTS - DNP USERS GROUP

DNP Users Group

LIST OF ABBREVIATIONS AND ACRONYMS

DNP Users Group

DNP V3.00 Data Object Library (Version 0.02)

ABOUT THIS DOCUMENT

WHO SHOULD USE THIS SPECIFICATION

HELP AND ADDITIONAL DOCUMENTATION

DNP Users Group

HOW THIS SPECIFICATION IS ORGANIZED

CONVENTIONS USED IN THIS SPECIFICATION

DNP V3.00 Data Object Library (Version 0.02)

DNP Users Group

DNP V3.00 Data Object Library (Version 0.02)

DNP Users Group

2. DECLARATION RULES FOR INFORMATION ELEMENTS

Table 2-1 Data Types 2.1.2 Data Size

BOOLEAN is a BITSTRING of size 1.

DNP V3.00 Data Object Library (Version 0.02)

Data Size i 4 12 . . 8j-4 3 11 . . 8j-5 2 10 . . 8j-6 1 9 . . 8j-7 0 8 . . 8j-8

Table 2-2 Bit Positions

DNP V3.00 Data Object Library (Version 0.02)

DNP Users Group

3.1 LIBRARY STRUCTURE

DNP V3.00 Data Object Library (Version 0.02)

DNP Users Group

DNP V3.00 Data Object Library (Version 0.02)

3.2 POINT NUMBERING

DNP V3.00 Data Object Library (Version 0.02)

DNP Users Group

4. BINARY INPUT OBJECT DEFINITIONS

4.1 SINGLE-BIT BINARY INPUT

DNP V3.00 Data Object Library (Version 0.02)

DNP Users Group

4.2 BINARY INPUT WITH STATUS

DNP V3.00 Data Object Library (Version 0.02)

4.3 BINARY INPUT CHANGE WITHOUT TIME

DNP Users Group

DNP V3.00 Data Object Library (Version 0.02)

4.4 BINARY INPUT CHANGE WITH TIME

DNP Users Group

BS8 [0..7] UI48 [0..47] <248 -1 ms>

DNP V3.00 Data Object Library (Version 0.02)

4.5 BINARY INPUT CHANGE WITH RELATIVE TIME

DNP Users Group

BS8 [0..7] UI16 [0..15] <0..216-1>

DNP V3.00 Data Object Library (Version 0.02)

DNP Users Group

5. BINARY OUTPUT OBJECT DEFINITIONS

5.1 BINARY OUTPUT

DNP V3.00 Data Object Library (Version 0.02)

5.2 BINARY OUTPUT STATUS

DNP Users Group

5.3 CONTROL RELAY OUTPUT BLOCK

DNP V3.00 Data Object Library (Version 0.02)

On Time 31 Off Time 31 Status 7 6 5 4 3 2 1 0 0 0

3: 4: 5 - 15: Queue: Clear:

DNP Users Group

5.4 PATTERN CONTROL BLOCK

On Time 31 Off Time 31 Status 7 6 5 4 3 2 1 0 0 0