DNP V3.00 Dpa: Functional Specification

GE HARRIS
Energy Control Systems Canada, Inc.
DNP V3.00 DPA

FUNCTIONAL
SPECIFICATION
Document Number: B021-0FS.WES
Version : 7.00
Date : 98.12.21
Submitted By: Authorized By:

Signature:
Name:
Date:
Classification: Restricted
Release: Full
NOTICE OF COPYRIGHT & PROPRIETARY RIGHTS
1998, GE HARRIS Energy Control Systems Canada, Inc. All rights reserved.
The contents of this manual are the property of GE HARRIS Energy Control Systems
Canada, Inc. No part of this work may be reproduced or transmitted in any form or by
any means, except as permitted by written license agreement with GE HARRIS Energy
Control Systems Canada, Inc.
GE HARRIS Energy Control Systems Canada, Inc. 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 GE HARRIS Energy Control Systems Canada, Inc.
Any attached hardware schematics and technical descriptions, or software listings that
disclose source code, are for information purposes only. Reproduction in whole or in
part to create working hardware or software for other than GE HARRIS Energy Control
Systems Canada, Inc. products is strictly prohibited, except as permitted by written
license agreement with GE HARRIS Energy Control Systems Canada, Inc.
TRADEMARK NOTICES
WESDAC is a registered trademark of GE HARRIS Energy Control Systems Canada,

Inc. All other brand and product names mentioned in this document are trademarks or
registered trademarks of their respective companies.
DNP V3.00 DPA Functional Specification

B021-0FS.WES, Version 7.00 i
GE HARRIS Energy Control Systems Canada, Inc.
ii B021-0FS.WES, Version 7.00
MODIFICATION RECORD
VERSION DATE INITIALS COMMENT
1.00 93.09.14 CL Revisions as per Paul Morton.
1.01 94.07.11 PM Added Appendix B. Format check, changed version

number on footers to read 1.01, removed DNP
copyright page and inserted HARRIS copyright
page, regenerated TOC.
2.00 94.07.14 AV Versioned up the document to 2.00 to match the

software version number.
2.01 94.11.15 GG 2.0, 2.2, 2.15, 2.17, 3.1.4, 4.1, 5.2 Added notes
about COS and SOE being sent when binary inputs
are Appendix B requested. Added storage objects.
Clarified discussions of IIN objects, READ function
code, and Silent Master mode. Extension now
.WES.
3.00 95.02.09 CT 3-8, 3-9 Clarified Section 3.1.13 Assign Classes

Function Code. Added description of retries to
Section 3.2 Communication Flow Control and
Reliability. Versioned up the document to 3.00 to
match software.
3.01 95.07.26 CT Section 2.3 Added description of online/offline

events in unsolicited responses.
Section 2.2, 2.4, 5.2 DPA no longer dumps
COS/SOE with binary input reads.
Section 2.15 Device watchdog IIN removed.
Section 3.1.8 DPA supports freezing and clearing
frozen counters.
Section 3.1.13 DPA supports disabling events from a
point by assigning to class 0.
Section 2.16 DPA supports cfg transfer to any
number of devices (i.e. device number in pathname
can be any size).
Sections 3.1, 3.1.14, 3.1.15, Table B-1 DPA
supports cold and warm restart.
Sections 2.5, 2.7 DPA reports object variation with a
flag when the variation without a flag is not
supported but specifically requested.
Sections 2.1, 2.8, 3.1.4, 3.1.6, Table B-2 DPA
partially supports 32-bit analog outputs.
Table A-1 DPA accepts single and multi-point events
while ignoring time-tags for all events except
DATA_CHANGE events.
Table A-2 DPA doesnt enable DEVICE_STATUS
reporting; DPA doesnt send FREEZE_CALL to WIN.
4.00 95.11.27 CT Updated entire document to meet version 400

requirements.

B021-0FS.WES, Version 7.00 iii
VERSION DATE INITIALS COMMENT
5.00 96.04.18 TW Updated document to include the following:

Local/Remote Input Point.
Unsolicited Response Event Reporting (Idle
reporting).
Analog Input/Output Scaling.
Analog Input Time-tag (Obj.32 Var.3 and 4).
Control allow for offlined points.
96.06.24 GG Holdoff time in milliseconds resolution.
Deleted Frozen Delta Counters.
5.01 96.10.10 GG Re-added Frozen Counter Events and Frozen Delta

Counters to Table B-3, indicating the DPA does
parse the requests even if it doesnt report them
correctly. Not added to rest of document.
6.00 98.07.01 TW Rev. up for a major revision of the software version.

No changes to the actual document.
98.01.27 SG (BOW Software Inc.)

Added the following:
If so configured, the DPA will not report static
objects which are simultaneously in the off-line
and remote forced state.
Conditional reporting of an object with or without
flag. Added support for the following objects:
32- and 16-Bit Binary and Delta Counter without
7.00 Flag, 32- and 16-Bit Frozen Counter without
Flag, and 32- and 16-Bit Analog Input without
Flag.
WIN_FORCE_DATA_EVENT and
WIN_UNFORCE_DATA_EVENT processing.
98.07.28 RJK Added SOE sorting, full analog 32 bit support, and
configuration download.
Integrated document B021-3FS with B021-0FS.

iv B021-0FS.WES, Version 7.00
TABLE OF CONTENTS
ABOUT THIS SPECIFICATION

PURPOSE OF THIS SPECIFICATION xiii
WHO SHOULD USE THIS SPECIFICATION xiii
HELP AND ADDITIONAL DOCUMENTATION xiv
CONVENTIONS USED IN THIS SPECIFICATION xiv
OVERVIEW xv
Chapter 1: DATA OBJECTS

1.1 LIST OF DATA OBJECTS SUPPORTED BY THE DNP DPA 1-2
1.2 CLASS 0, 1, 2 AND 3 DATA OBJECTS 1-4
1.3 UNSOLICITED RESPONSES 1-4
1.4 BINARY INPUT DATA OBJECTS 1-5
1.4.1 Forcing Binary Inputs 1-7
1.5 BINARY COUNTER DATA OBJECTS 1-8
1.6 FROZEN BINARY COUNTER DATA OBJECTS 1-10
1.7 ANALOG INPUT DATA OBJECTS 1-11
1.8 ANALOG OUTPUT DATA OBJECTS 1-14
1.9 DIGITAL OUTPUT DATA OBJECTS 1-16
1.9.1 Control Relay Output Block Object 1-17
1.9.2 Pattern Output Block Objects 1-18
1.10 ONLINE/OFFLINE STATUS CHANGES 1-18
1.11 TIME AND DATE DATA OBJECT 1-19
1.12 TIME AND DATE COMMON TIME OF OCCURRENCE 1-19
1.13 UNSYNCHRONIZED COMMON TIME AND DATE 1-19
1.14 TIME DELAY FINE 1-19
1.15 CLASS DATA OBJECTS 1-20
1.16 INTERNAL INDICATIONS 1-21

B021-0FS.WES, Version 7.00 v
1.17 FILE IDENTIFIER OBJECT 1-23
1.17.1 File Download Protocol Description 1-24
1.17.2 File Download DPA Processing Requirements 1-34
1.17.3 File Download Backward Compatability Issues 1-35
1.17.4 File Upload Protocol Description 1-39
1.17.5 File Upload DPA Processing Requirements 1-45
1.17.6 File Upload Backward Compatibility Issues 1-46
1.18 STORAGE OBJECTS 1-49
1.19 TIME ADJUSTMENT ANALOG INPUTS (CCU BASE ONLY) 1-51
1.20 RESTRICTIONS INHERENT TO THE DNP DPA 1-52
Chapter 2: PROTOCOL IMPLEMENTATION

2.1 FUNCTION CODES USED BY THE DNP DPA 2-2
2.1.1 CONFIRM Function Code 2-3
2.1.2 RESPONSE Function Code 2-3
2.1.3 UNSOLICITED RESPONSE Function Code 2-3
2.1.4 READ Function Code 2-4
2.1.5 WRITE Function Code 2-5
2.1.6 SELECT and OPERATE Function Codes 2-5
2.1.7 DIRECT OPERATE and DIRECT OPERATE - NO ACK Function Codes
2-6
2.1.8 IMMEDIATE FREEZE and IMMEDIATE FREEZE - NO ACK Function
Codes 2-7
2.1.9 FREEZE AND CLEAR and FREEZE AND CLEAR - NO ACK Function
Codes 2-8
2.1.10 COLD RESTART Function Code 2-9
2.1.11 WARM RESTART Function Code 2-9
2.1.12 START APPLICATION Function Code 2-9
2.1.13 STOP APPLICATION Function Code 2-9
2.1.14 SAVE CONFIGURATION Function Code 2-10
2.1.15 ENABLE/DISABLE SPONTANEOUS MESSAGE Function Codes 2-10
2.1.16 ASSIGN CLASSES Function Code 2-11
2.1.17 DELAY MEASUREMENT Function Code 2-11
2.2 COMMUNICATION FLOW CONTROL AND RELIABILITY 2-12
Chapter 3: SILENT MASTER OPERATING MODE

3.1 SILENT MASTER MODE WITH AUTO DATA DUMP 3-2

vi B021-0FS.WES, Version 7.00
Chapter 4: GENERAL FUNCTIONALITY TOPICS
4.1 ANALOG INPUT DEADBANDS 4-1
4.2 DIGITAL INPUT EVENTS 4-3
4.3 MODES OF OPERATION (CCU BASE ONLY) 4-4
4.3.1 SERVICE Mode 4-4
4.3.2 DNP DPA in STANDBY and DISABLE Mode 4-4
4.4 BINARY OUTPUT ENABLE (CCU BASE SYSTEM ONLY) 4-5
4.5 DYNAMIC CONFIGURATION CHANGES 4-6
4.6 COMMUNICATIONS FAIL OUTPUT 4-7
4.7 LOCAL/REMOTE INPUT 4-8
4.8 UNSOLICITED RESPONSE EVENT REPORTING 4-9
4.9 ANALOG INPUT SCALING 4-11
4.10 ANALOG OUTPUT SCALING 4-12
4.11 TIME TAGGED ANALOG INPUT EVENTS 4-13
Appendix A: DNP DPA WIN USAGE A-1
Appendix B: DNP DPA IMPLEMENTATION MATRIX B-1
Appendix C: DEVICE PROFILE DOCUMENT C-1
GLOSSARY OF TERMS G-1
LIST OF ACRONYMS AND ABBREVIATIONS L-1

B021-0FS.WES, Version 7.00 vii
viii B021-0FS.WES, Version 7.00
LIST OF FIGURES
Figure 1 EPA Layers For The DNP DPA xvii

Figure 2 Example of A System with Multiple DNP DPAs xviii
Figure 1-1 Single Message File Download Communication Sequence 1-25
Figure 1-2 Multiple Message File Download Communication Sequence 1-26
Figure 1-3 Passing A File Identifier Object via DNP Devices 1-33
Figure 1-4 File Download Backward Compatible Communication Sequence 1-35
Figure 1-5 Multiple Message File Download Communication Sequence 1-40
Figure 1-6 Single Message File Upload Communication Sequence 1-41
Figure 1-7 File Upload Backward Compatible Communication Sequence 1-46
Figure 4-1 Example of Absolute Integrating Analog Deadband 4-2
Figure 4-2 Unsolicited Response Event Reporting 4-10

B021-0FS.WES, Version 7.00 ix
x B021-0FS.WES, Version 7.00
LIST OF TABLES
Table 1-1 File Identifier Object WRITE 1-27

Table 1-2 File Identifier Object APPEND 1-29
Table 1-3 File Identifier Object RESPONSE 1-31
Table 1-4 Backward Compatible File Identifier Object WRITE 1-36
Table 1-5 Backward Compatible File Identifier Object RESPONSE 1-38
Table 1-6 File Identifier Object READ 1-42
Table 1-7 File Identifier Object RESPONSE 1-44
Table 1-8 Backward Compatible File Identifier Object READ 1-47
Table 1-9 Backward Compatible File Identifier Object RESPONSE 1-48
Table 4-1 Analog Input Event Reporting 4-13
Table A-1 Supported WIN Events A-1
Table A-2 Commands Sent To WIN A-3
Table B-1 Function Codes Supported by the DNP DPA B-1
Table B-2 Objects and Variations Supported by the DNP DPA B-3
Table B-3 Objects/Variations/Qualifiers/Function Codes supported by the DPA B-6

B021-0FS.WES, Version 7.00 xi
xii B021-0FS.WES, Version 7.00
ABOUT THIS SPECIFICATION
PURPOSE OF THIS SPECIFICATION
This document specifies the operation of the Distributed Network Protocol (DNP) Data
Processing Application (DPA). This software application runs on GE HARRIS D25, D20,
D200, and CPM hardware.
WHO SHOULD USE THIS SPECIFICATION
This document is for use by Programmers, Engineers and Quality Assurance personnel
who will review and use the DNP DPA. This document assumes that the reader is
reasonably familiar with the GE HARRIS software environment and the DNP V3.00
Protocol.

B021-0FS.WES, Version 7.00 xiii
HELP AND ADDITIONAL DOCUMENTATION
More detail on topics related to the application discussed in this document may be found
in the following sources:
! DNP V3.00 Application Layer Protocol Description (P009-0PD.APP)
! DNP V3.00 Data Object Library (P009-0BL)
! DNP V3.00 Data Link Layer Protocol Description (P009-0PD.DL)
! Introduction to the GE HARRIS D20 (GEN-0003)
CONVENTIONS USED IN THIS SPECIFICATION
There are a number of formatting conventions used in this specification to make it easier
to read and understand. They are as follows:
! New or special terms are highlighted in bold text.
! Chapter references are highlighted in bold text, with the chapter title in CAPITAL
LETTERS (for example, Chapter 2: SPECIAL REQUIREMENTS). Table
names are also bold (e.g. AXXX_CFG).
! References to main section titles are highlighted using italics, as are book and
document titles, and words used with special emphasis.
! Lists of procedural instructions are numbered in the order they should be performed.
Other lists of information are bulleted, like this list is.
! Specific keyboard keys are indicated in BOLD CAPITAL LETTERS like this:
<ENTER>, <ALT>, <BACK SPACE>.
! Words or instructions to be typed into your computer are indicated exactly as they
should be typed, in bold italics. (For example, type in the command diskcopy a: b:
and then press the <ENTER> key.)
! Specific function and field names are in CAPITAL LETTERS, but not bold.
(e.g. TRIP function, GROUP ADDRESS field).

xiv B021-0FS.WES, Version 7.00
OVERVIEW
The purpose of the Distributed Network Protocol (DNP) Data Processing Application
(DPA) is to allow a remote master station to retrieve and/or modify the information in the
database of GE HARRIS devices using the DNP V3.00 Application Layer Protocol. It
uses WIN to access the devices database.
The DNP DPA functionality includes the following:
! Responding to master requests.
! Automatically transmitting event data to the master when configured to do so
(unsolicited responses).
! Sending commands to WIN.
! Processing data events from WIN.
! Supporting binary inputs, binary outputs, counters (absolute and delta), frozen
counters, 16-bit analog inputs 16-bit analog outputs, 32-bit analog inputs, and 32-bit
analog output objects. The DNP DPA can report time-tagged (TT) analog inputs.
! Supporting Change-of-State (COS) or Sequence-of-Event (SOE) event objects on
binary inputs. All Sequence-of-Event objects are stored in order sorted
chronologically.
! Performing counter input processing and generating counter event objects.
! Performing analog deadband processing and generating analog event objects.
! Performing analog input and analog output scaling.
! Assigning event objects to a class of data (on a per point basis).
! Assigning online/offline status changes to a class of data.

B021-0FS.WES, Version 7.00 xv
! If so configured, static objects which are simultaneously in the off-line and remote
forced state are not reported.
! Supporting group controls and most control operations including trip/close,
select/operate and pattern masks.
! Supporting time synchronization.
! Accepting a configuration for a remote device and transferring it to a DNP DCA via
WIN.
! Reading a remote device's configuration from a DNP DCA via WIN.
! Supporting multiple Logical Remote Units (LRUs). Each LRU is a separate instance
of the DPA which has a unique address and configuration and runs independently of
the other instances.
! Supporting multiple communication ports per LRU via BridgeMAN.
! Indicating the current communications status through a binary output point.
! Enabling or disabling outputs on the basis of a local/remote status input point.
! Passing a configuration for the GE HARRIS device to the CCU/D25 Base System
where it is stored in either the local RTU or a remote standby RTU.
In addition, when running on the CCU Base System, the DNP DPA supports the
following:
! Detecting whether the RTU is in active or standby mode and behaving accordingly.
! Whenever possible, the majority of the DNP DPA run-time memory allocation is first
attempted from the global memory pool, then the local memory pool if the first
attempt was not successful.
L NOTE: Unless otherwise specified, all functionality of the DNP DPA is

supported on the D20, D25, and CCU Base Systems.
Figure 1 illustrates the applications and interfaces for DNP. The DNP software in the
GE HARRIS device is layered to be consistent with the International Electrotechnical
Commission (IEC) Enhanced Protocol Architecture (EPA). The EPA consists of a
Physical, Data Link and Application Layer. The DNP DPA implements the Application
Layer.

xvi B021-0FS.WES, Version 7.00
The DNP DPA interfaces to the HARRIS Bridge Manager (BridgeMAN). The EPA
model does not include a network layer for routing. BridgeMAN addresses this need by
providing the routing functions of a network layer without adding a network layer header
to outgoing messages. This allows GE HARRIS devices to communicate with devices
which do not have BridgeMAN.
BridgeMAN transports messages between the DNP DPA and a remote DNP host (e.g.
master station) using whatever data links or intermediate devices necessary, as configured
in its routing tables. Refer to the section Help and Additional Documentation for more
information on this application.
WESDAC Interface Node
APPLICATION LAYER DNP DPA

BridgeMAN Application
One or more Data Links (such

DATA LINK LAYER
as the DNP Data Link)
PHYSICAL LAYER Physical Layer
Figure 1 EPA Layers For The DNP DPA
More than one data link application can interface to BridgeMAN and more than one DPA
can interface to BridgeMAN. Figure 2 illustrates an example where several instances of
the DNP DPA interface to BridgeMAN. Each DPA requires a unique address and runs
independent of any other DPA. The BridgeMAN routes messages between one or more
data links to the DPAs. This functionality allows DNP DPAs to be redundantly ported (a
DPA may be accessed via more than one data link i.e. communication channel) and
multi-ported (more than one DNP master station can access the same data via multiple
DNP DPAs simultaneously and independently).

B021-0FS.WES, Version 7.00 xvii
WESDAC Interface Node
and Database
DNP V3.00 DPA DNP V3.00 DPA
BridgeMAN
Data Data Data

Link Link Link
DNP V3.00 DNP V3.00

Master Station Master Station
Figure 2 Example of A System with Multiple DNP DPAs

xviii B021-0FS.WES, Version 7.00
Chapter 1:
DATA OBJECTS
This chapter discusses the various data objects supported by this implementation of the
DNP DPA. It explains how the DNP DPA interprets objects and how data and commands
are converted from GE HARRIS device internal format to the DNP object format.
Reference should be made to the DNP V3.00 Data Object Library for detailed
descriptions of the objects.
A data object is an information element. It often contains data from the database of the
GE HARRIS device. Most data objects are read by the DNP master station while some
are written by the master station. For example, the 16-Bit Analog Input object is an object
read by the master station and the Control Relay Output Block object is an object written
to by the master station.
Each instance of the DNP DPA supports up to 65,536 (64K) points per data type. A DNP
DPA can reference system point numbers greater than 65,536.

B021-0FS.WES, Version 7.00 1-1
1.1 LIST OF DATA OBJECTS SUPPORTED BY THE DNP DPA
The following data objects are supported by the DNP DPA. Refer to the DNP V3.00 Data
Object Library (P009-0BL) document for more information about the structure of the
objects.
Data Objects completely supported are:
! Binary Input with Status
! Single Bit Binary Input
! Binary Input Change without Time
! Binary Input Change with Time
! Binary Input Change with Relative Time
! Binary Output Status
! Control Relay Output Block
! Pattern Control Block
! Pattern Mask
! 32-Bit Binary Counter
! 32-Bit Binary Delta Counter
! 16-Bit Binary Delta Counter
! 32-Bit Binary Counter without Flag
! 32-Bit Delta Counter without Flag
! 16-Bit Delta Counter without Flag
! 32-Bit Frozen Counter
! 32-Bit Frozen Counter without Flag
! 32-Bit Counter Change Event without Time
! 16-Bit Counter Change Event with Time
! 32-Bit Delta Counter Change Event without Time
! 16-Bit Analog Input
! 16-Bit Analog Input without Flag
! 16-Bit Analog Change Event without Time
! 16-Bit Analog Change Event with Time
! 16-Bit Analog Output Status
! 16-Bit Analog Output Block
! 32-Bit Analog Input
! 32-Bit Analog Input without Flag

1-2 B021-0FS.WES, Version 7.00
! 32-Bit Analog Change Event without Time
! 32-Bit Analog Change Event with Time
! 32-Bit Analog Output Status
! Class 0 Data
! Class 1 Data
! Class 2 Data
! Class 3 Data
! Time and Date
! Time and Date Common Time of Occurrence
! Unsynchronized Common Time and Date
! Time Delay Fine
! Internal Indications
Data Objects partially supported are:
! File Identifier Object
! Storage Object
Custom Data Features only supported on the CCU Base System are:
! Time Adjustment Analog Inputs (using two analog input pseudo points reported using
the 32-Bit Analog Input Without Flag object)
! Binary Output Enable Object (using a binary output pseudo point)

1.2 CLASS 0, 1, 2 AND 3 DATA OBJECTS
The DNP protocol supports a data priority scheme where different Data Objects can be
assigned to different data Classes. The DNP DPA supports 4 Classes of data objects
(Class 0, 1, 2 and 3). Many data objects have an attribute enabling them to be assigned to
a particular class. The DNP master may poll for data from different Classes with different
frequencies. The 4 classes are therefore used to prioritize data.
A poll for Class 0 data always accesses non-event data. By definition, non-event data is
data which is always available for reading from the DNP DPA. For example, the current
value of an analog input is non-event data (e.g. 16-Bit Analog Input object). Conversely, a
time tagged digital input change (e.g. Binary Input Change with Time object) is event
data. By definition, event data is only available for reading after changes in the system
have caused change objects to be generated.
Class 1, 2 and 3 data is reserved for event data.
The configuration supports assigning online/offline status changes to class 1, 2 or 3 (i.e.
event data), or disabling online/offline change reporting altogether. However, because the
DNP protocol does not define an event object for online/offline status changes, the
information is reported using the corresponding static data objects.
1.3 UNSOLICITED RESPONSES
The DNP DPA can operate in a mode where Unsolicited Responses are sent from the
DNP DPA to the DNP master. When the DNP DPA is in this Unsolicited Response
mode, it automatically transmits event data to the master station as it occurs. In this mode
the master station does not need to poll for this data. The event data is transmitted
whenever a specific number of events are collected or the events have been held for a
specific time.
Upon GE HARRIS device startup, the DNP DPA is configured in its Non-Volatile
Random Access Memory (NVRAM) configuration file to enable or disable Unsolicited
Responses for each of Class 1, 2 and 3 data. Afterwards the DNP master station may
enable and disable Unsolicited Responses via commands to the DNP DPA. A system
constraint is that Unsolicited Responses are enabled or disabled for an entire Class of
data. Enabling and disabling Unsolicited Responses for sub-sets of a data Class is not
allowed.

1.4 BINARY INPUT DATA OBJECTS
The binary input data objects supported by the DNP DPA are:
! Binary Input with Status (Obj.1 Var.2)
! Single Bit Binary Input (Obj.1 Var.1)
! Binary Input Change without Time (Obj.2 Var.1)
! Binary Input Change with Time (Obj.2 Var.2)
! Binary Input Change with Relative Time (Obj.2 Var.3)
These objects report data stored in the Digital Input database in the GE HARRIS device.
The objects Binary Input with Status and Single Bit Binary Input are reported to the
master station in response to a DNP READ request. These objects are used for dumping
data about the state of digital inputs in the GE HARRIS device. These objects are always
Class 0 data. The DNP master station can request these objects:
! Directly (by reading the Object and Variation directly)
! By a read of Class 0 data
! By a read of Object 1 Variation 0
L NOTE: Regardless of the variation specified (Class 0, variation 0, with flag, or

without flag), the DNP DPA returns a binary input in the Single Bit
Binary Input variation if the binary input is online (i.e. the binary input
point flag equals 1). If the flag does not equal one, the Binary Input
with Status variation is used. The DPA may be configured to not report
any binary inputs or other STATIC objects which are simultaneously
in the off-line and remote forced state.
Changes in the WIN digital input points may generate events. These events are saved as
Binary Input Change Objects in the GE HARRIS device. These objects are reported:
! In response to a READ request of the Object and Variation. If no events are available,
the DNP DPA response contains the two byte Internal Indication object. No other
object data is returned in the response.
! In response to a READ request of the appropriate Class data.
! Automatically to the master station if Unsolicited Responses are enabled for the
points.

The objects Binary Input Change without Time (object 2, variation 1), Binary Input
Change with Time (object 2, variation 2) and Binary Input Change with Relative Time
(object 2, variation 3) are supported.
Each binary input point reported by the DNP DPA has a number of configuration
parameters. These configuration parameters are in the NVRAM configuration data of the
GE HARRIS device. The NVRAM configuration has a single record for each point. Each
record has the following elements:
Point Number - RTU System Point Number.
InvertFlag - Invert the binary input (i.e. normally open and normally closed inputs).
WithoutTime - Enables or Disables creation of Binary Input Change Without Time
objects when the input point changes state.
WithTime - Enables or Disables the creation of either a Binary Input Change With
Time or a Binary Input With Relative Time object when the input point
changes state. Only one of the two objects will be created at any one
time.
Class - Specifies a default Class for the point. This is the Class upon RTU
startup for the binary input event object.
L NOTE: A single point cannot be configured with WithoutTime = Enabled and

WithTime = Enabled. Either both are disabled or only one of them is
enabled.
For example, consider the configuration for 8 points below.

System Point Enable Object Enable Object Default Event DNP Point Number
Invert Flag
Number Without Time With Time Class (Not Configurable)
0 N Y N 1 0
11 N Y N 1 1
12 N Y N 1 2
15 N Y N 1 3
16 N Y N 2 4
17 N Y N 2 5
22 N N Y 2 6
25 N N Y 2 7

If the master issues a READ request for the Binary Input with Status object, range 2, then
data for WIN digital input point 12 is sent in the response. Note that range 2 specifies the
third record in the configuration table.
If the master sends a READ request for the Single Bit Binary Input object, range 0, then 1
bit of data containing the status of WIN digital input point 0 is sent in the response.
Entering a point number of -1 in the first element of a record sets the point as unused. It
will be reported as state 0 if read by the master station.
When time tagged binary input events are transmitted they are formatted as either Binary
Input with Time or Binary Input with Relative Time objects. If the DNP DPA has only one
event to transmit, the Binary Input with Time object is used. For two or more events, the
Binary Input with Relative Time objects are used (see Section 5.2: Digital Input Events
for more information). The DNP DPA always orders the transmitted objects so that the
oldest object is transmitted first through to the newest object.
For the previous example, consider WIN digital input point 22 changing state when no
other points change state. A READ of Class 2 data will cause a Binary input with Time
object to be returned in the response. If points 22 and 25 change state, a READ of Class 2
data causes both events to be formatted as Binary Input with Relative Time objects in the
same response.
1.4.1 Forcing Binary Inputs

A Binary Input With Status object can be written to the DNP DPA in order to force a
binary input to a specific state. When an input is forced, it remains in that state until it is
unforced.
To force a binary input, the master issues a DNP WRITE request containing a Binary
Input With Status object for a specific point. The Local Forced Data bit of the object
must be in state 1. The state to which the binary input point is forced equals the state in
the object if the input point is configured with InvertFlag = N. If InvertFlag = Y, the
forced state is the inverse of the state in the object.
To unforce a binary input, use the DNP WRITE request to send a Binary Input With
Status object for a specific point to the DNP DPA. The Local Forced Data bit of the
object must be in state 0. This clears the forced flag of the binary input point.

1.5 BINARY COUNTER DATA OBJECTS
The following NON FROZEN Binary Counter Objects are supported by the DNP DPA:
! 32-Bit Binary Counter (Obj.20 Var.1)
! 16-Bit Binary Counter (Obj.20 Var.2)
! 32-Bit Delta Counter (Obj.20 Var.3)
! 16-Bit Delta Counter (Obj.20 Var.4)
! 32-Bit Binary Counter without Flag (Obj.20 Var.5)
! 16-Bit Binary Counter without Flag (Obj.20 Var.6)
! 32-Bit Delta Counter without Flag (Obj.20 Var.7)
! 16-Bit Delta Counter without Flag (Obj.20 Var.8)
! 32-Bit Counter Change Event without Time (Obj.22 Var.1)
! 16-Bit Counter Change Event without Time (Obj.22 Var.2)
! 32-Bit Delta Counter Change Event without Time (Obj.22 Var.3)
! 16-Bit Delta Counter Change Event without Time (Obj.22 Var.4)
The 32- and 16-bit counters are functionally identical and only distinguished by the size
of the counter. The Delta Counter variations report the counts accumulated since the last
time the counter was reported to the master station. All other variation report the actual
value of the counter.
The Object 20 counters can be reported in 16- or 32-bit, absolute or delta format. These
objects contain STATIC data they are always read as Class 0 data. The DNP master
station can request these objects:
! Directly (by reading the Object and Variation directly)
! By a read of Class 0 data
! By a read of Object 20 Variation 0
The Object 22 counters report counter events. As with Object 20 counters, they can be
reported in 16- or 32-bit, absolute or delta format. These objects contain EVENT data -
they are read as Class 1, 2 and/or 3 data. These events are generated by the DNP DPA
when a counter exceeds its previously reported value by a certain amount (i.e. threshold).
These objects are sent to the DNP master station:
! In response to a READ request of the Object and Variation. If no events are available,
the DNP DPA response contains the two byte Internal Indication object. No other
object data is returned in the response.
! In response to a READ request of either Class 1, 2 or 3 data.
! Automatically if Unsolicited Responses are enabled for the points.

The NVRAM configuration for the DNP DPA contains a table for binary counters. Each
record in each table specifies a single counter and has the following elements:
Type - Specifies reporting of Transition or Pulse Counts.
Size - Selects the default counter size (16- or 32-bit) for reporting in a
response when a specific variation is not requested (e.g. a READ of
variation 0). This default is used for STATIC data (Object 20) and
EVENT data (Object 22).
Threshold - The threshold value, in counts, that the counter must exceed before an
event without time is created.
Class - Specifies a default class for the event without time. This is the class
upon RTU startup for the counter event objects.
A single configuration parameter for the entire DNP DPA specifies whether the absolute
or delta counter value is reported when a specific variation is not requested.
Spare points are created by setting element Point Number to -1.
A Threshold less than or equal to 0 disables counter events for the point.
If the DNP master reads Class 0 data or Object 20 Variation 0, each counter is transmitted
as either a 16- or 32-bit, absolute or delta counter without time (the default size and
whether to use absolute or delta values is specified by the configuration). Regardless of
the variation specified (Class 0, variation 0, with flag, or without flag), if a counter is
online (i.e. the counter point flag equals 1) the DPA returns the counter variation
corresponding to the one requested by the master which does not include the flag (e.g.
Object 20, variations 5-8). If the flag does not equal one, the DPA transmits the counter
using the corresponding variation which includes the flag. The DPA may be configured to
not report any counters or other STATIC objects which are simultaneously in the off-line
and remote forced state.
If the DNP master reads counter events (Object 22), only those counters which have
generated events are reported. They are reported in a format as specified by the variation
in the request, or using the default format specified by the configuration if a specific
variation is not requested.

For example, consider the configuration for 4 points below.
System Point Threshold For Event Default Event DNP Point Number
Type Size
Number Without Time Class (Not Configurable)
0 T 16 10 1 0
11 T 16 10 2 1
12 P 32 10 2 2
15 P 32 0 1 3
A response with Object 20 Variation 1 Range 2 contains the first of the 32-Bit Binary
Counter objects, namely the counter associated with RTU system Point 12.
A response with Object 20 Variation 2 Range 1 contains the second of the 16-Bit Binary
Counter objects, namely the counter associated with RTU system point 11.
1.6 FROZEN BINARY COUNTER DATA OBJECTS
The following FROZEN Binary Counter Objects are supported by the DNP DPA:
! 32-Bit Frozen Counter (Obj.21 Var.1)
! 16-Bit Frozen Counter (Obj.21 Var.2)
! 32-Bit Frozen Counter Without Flag (Obj.21 Var.9)
! 16-Bit Frozen Counter Without Flag (Obj.21 Var.10)
Frozen Counters are processed completely independently of the non-frozen (running)
counters. Frozen and running counters are different data categories and are not related
according to the DNP implementation.
The functionality of frozen counters and running counters are identical. The configuration
table format for frozen counters is the same as running counters. There is a separate
configuration table for frozen counters.

1.7 ANALOG INPUT DATA OBJECTS
The following analog input data objects are supported by the DNP DPA:
! 16-Bit Analog Input (Obj.30 Var.2)
! 16-Bit Analog Input Without Flag (Obj.30 Var.4)
! 16-Bit Analog Input Change Event Without Time (Obj.32 Var.2)
! 16-Bit Analog Input Change Event With Time (Obj.32 Var.4)
! 32-Bit Analog Input (Obj.30 Var.1)
! 32-Bit Analog Input Without Flag (Obj.30 Var.3)
! 32-Bit Analog Input Change Event Without Time (Obj.32 Var.1)
! 32-Bit Analog Input Change Event With Time (Obj.32 Var.3)
At present the internal WIN database only supports 16-bit analog values. When a 32-bit
value is sent to the DNP master station, the 32-bit value is assembled from two 16-bit
words stored in the WIN database. The 32-bit value is represented internally in the WIN
database with the most significant 16-bit word stored first followed immediately by the
least significant 16-bit word. The DNP DPA sends 32-bit values with the most significant
16-bit word first followed by the least significant 16-bit word.
The 16-Bit Analog Input and 32-Bit Analog Input objects are always Class 0 data. The
DNP master station can request these objects:
! Directly (by reading the Object and Variation directly).
! By reading Class 0 data.
! By reading Object 30 Variation 0 data.
The 16-Bit Analog Input Change Event Without Time and 32-Bit Analog Input Change
Event Without Time objects are used for reporting analog events when an analog point
exceeds a configured DEADBAND (See Section 4.1). These objects are reported:
! In response to a READ request of the Object and Variation.
points.

The 16-Bit Analog Input Change Event With Time and 32-Bit Analog Input Change Event
With Time objects are used for reporting analog events with their associated time tags
when the analog point exceeds the configured DEADBAND (See Section 4.1). The
particular time object reported will be determined in the configuration. Time objects
returned will be either absolute time of first event or current time. The Analog Input
Change Event With Time objects are reported:
! In response to a READ request of the Object and Variation.
points.
The NVRAM configuration for the DNP DPA contains a table for analog inputs. Each
record in the table specifies a single analog input and has the following elements:
Point Number - RTU System Point Number. Note that if the analog size is set to
32-bit, the system point number identifies the most significant 16
bit word, and the system point number plus one identifies the least
significant 16 bit word.
Size - Selects the default analog size (16- or 32-bit) for reporting in a
response when a specific variation is not requested (e.g. a READ
of variation 0). This default is used for STATIC data (Object 20)
and EVENT data (Object 22).
Deadband - The deadband value, in normalized RTU database counts, that the
analog must exceed before an event is created. Normalized
database counts are 32767.
Class - Specifies a default class for the point. This is the class upon RTU
startup for the analog event objects.
Time Tag - Specifies whether or not time tags will be returned for analog input
events for the point.
Range - Specifies a full scale DNP protocol value which can be reported to
the DNP master station.
Divisor - Specifies a full scale WIN analog input value required to achieve
the full scale DNP protocol value when scaling analog.
Offset - Specifies the analog input scaling offset.

For example, consider the following configuration for 4 points.
System Default
Analog Time DNP Point Number
Point Size Event Range Divisor Offset
Deadband Tag (Not Configurable)
Number Class
93 16 20 1 Enable 32000 32767 0 0
23 16 15 2 Enable 32000 32767 0 1
19 32 15 2 Disable 32767 32767 0 2
15 32 0 0 Disable 32767 32767 0 3
A response with Object 30 Variation 1 Index 2 contains the first of the 32-Bit Analog
Input objects, namely the analog associated with RTU system point 19.
A response with Object 30 Variation 2 Index 1 contains the second of the 16-Bit Analog
Input objects, namely the analog associated with RTU system point 23.
If the DNP master reads Class 0 or Object 30 Variation 0 data, each analog is transmitted
as either (but not both) a 16- or 32-bit analog input (the default size is specified by the
configuration). The Analog Input Event objects are not transmitted. Regardless of the
variation specified (Class 0, variation 0, with flag, or without flag), if an analog input is
online (i.e. the analog input point flag equals 1) the DPA returns the analog input
variation corresponding to the one requested by the master which does not include the
flag (e.g. Object 30, variations 3-4). If the flag does not equal one, the DPA transmits the
analog input using the corresponding variation which includes the flag. The DPA may be
configured to not report any analog inputs or other STATIC objects which are
simultaneously in the off-line and remote forced state.
Spare points are created by setting element Point Number to -1.
Setting Deadband = -1 disables deadband processing, i.e. the point never generates
Analog Input Event Without Time objects. Refer to Section 4.1 Analog Input Deadbands
for a detailed discussion of analog deadband processing.
Analog input events can be configured to report as time tagged or non-time tagged events.
If time tagged events are to be reported, the time object reported can be selected to
include the current time or the time of the first event. Refer to Section 4.11 Analog Input
Time Tag for a detailed discussion of how time-tagged analogs are reported.
The DNP DPA will scale analog input values before transmitting them to the DNP master
station. Refer to Section 4.9 Analog Input Scaling for a detailed discussion of analog
input scaling processing.

1.8 ANALOG OUTPUT DATA OBJECTS
The following Analog Output Data objects are supported by the DNP DPA:
! 16-Bit Analog Output Status (Obj. 40 Var. 2)
! 16-Bit Analog Output Block (Obj. 41 Var. 2)
! 32-Bit Analog Output Status (Obj.40 Var.1)
! 32-Bit Analog Output Block (Obj.41 Var.1)
The DNP master uses the SELECT and OPERATE or DIRECT OPERATE requests,
containing the 16-Bit Analog Output Block object, to the DNP DPA in order to set the
value of an analog output. The master can read the actual value of the analog output by
reading the 16-Bit Analog Output Status object:
! Via a read of Class 0 data.
! Via a read of Object 10 Variation 0.
L NOTE: The DPA may be configured to not report any analog output status or
other STATIC objects which are simultaneously in the off-line and
remote forced state.
At present the internal WIN database only supports 16-bit analog values. When a 32-bit
status is requested by the DNP master station, the DPA assembles the 32-bit value from
two 16-bit words stored consecutively in the WIN database. The 32-bit value is
represented internally in the WIN database with the most significant 16-bit word stored
first followed immediately by the least significant 16-bit word. The DNP DPA sends 32-
bit values with the most significant 16-bit word first followed by the least significant 16-
bit word.
The Analog Output Status objects are always Class 0 objects.

The NVRAM configuration for the DNP DPA contains a table for Analog Outputs. Each
record in the table specifies a single analog output and has the following elements:
Size - Selects the default analog size (16- or 32-bit).
Range - Specifies a full scale WESDAC analog output value.
Divisor - Specifies a full scale DNP protocol value required to provide a full
scale WESDAC analog output value.
Offset - Specifies the analog output scaling offset.
The DNP DPA will scale analog output values received from the DNP master. The scaled
analog output values will be used to perform analog output requests through the WIN
interface. Refer to Section 4.10 Analog Output Scaling for a detailed discussion of analog
output scaling processing.

1.9 DIGITAL OUTPUT DATA OBJECTS
The following data objects are supported by the DNP DPA in the GE HARRIS device:
! Control Relay Output Block (Obj. 12, Var. 1)
! Pattern Control Block (Obj. 12, Var. 2)
! Pattern Mask (Obj. 12, Var. 3)
! Binary Output Status (Obj. 10, Var. 2)
The master can read the current value of the binary output by reading the Binary Output
Status object:
! Via a read of Class 0 data.
! Via a read of Object 10 Variation 0.
L NOTE: The DPA may be configured to not report any binary output status or
other STATIC objects which are simultaneously in the off-line and
remote forced state.
The Binary Output Status objects are always Class 0 objects.

The other 3 binary output objects (Object 12) are used to select and operate binary output
points. When running on the CCU Base System, system binary output points owned by
the DPA may be assigned to a non-zero group. Control requests for such binary outputs
will fail unless the master has enabled binary output processing in the DPA. The master
station enables binary output processing by sending a special "get control" binary output
request to the DPA. This custom request is discussed in more detail in Section 4.4 Binary
Output Enable.

1.9.1 Control Relay Output Block Object
The DNP master station sends the Control Relay Output Block object in order to activate
control outputs in the GE HARRIS device or devices downstream of the GE HARRIS
device. The GE HARRIS device passes the control to the base software (via the WIN).
The control request is eventually routed to a device.
The Control Relay Output Block object is written to the DNP DPA using the DNP
SELECT and OPERATE or DIRECT OPERATE requests (discussed in Chapter 2). The
object is returned in the responses to these requests with the status of the operation as part
of the object.
The NVRAM configuration for the DNP DPA contains a table for Digital Outputs. Each
record in the table specifies a single digital output and has the following elements:
PairedPoint - Specifies a RTU System Point Number. When a control request is
addressed to Point Number, the control specified by PairedPoint is
automatically reset (i.e. any control operation in progress for this point
is reset). This is used to provide Raise/Lower control output
functionality.
For example, consider the following configuration:
Point Number Paired Point DNP Point Number (Not Configurable)
12 -1 0
13 -1 1
18 19 2
19 18 3
If the DNP master sends the Control Relay Output Block to Range 0, the control will go
to RTU System point 12. Sending the block to range 2 will cause a control to be sent to
RTU System point 18 and any currently executing control for RTU system point 19 is
reset. Sending the block to range 3 will cause a control to be sent to RTU system point 19
and any currently executing control for RTU system point 18 is reset. For this
configuration RTU system points 18 and 19 are a Raise/Lower pair.

1.9.2 Pattern Output Block Objects
The objects Pattern Control Block and Pattern Mask are always sent by the DNP master
to the DNP DPA in succession. Together they specify a digital output array.
Pattern Control outputs reference the same NVRAM configuration table as the Control
Relay Output Block object (see previous section). The elements Paired Point in the
configuration table are ignored when processing pattern controls.
1.10 ONLINE/OFFLINE STATUS CHANGES
When online/offline status changes are assigned to class 1, 2 or 3 in the DPA

configuration, each online/offline status change is considered an event. However, the
DNP protocol does not support event objects for such data, so the information is returned
using the corresponding static data object.
For example, consider the case where status changes are assigned to class 1 and a binary
output point goes offline. If the master requests class 1 data, the response will include a
binary output status object for the point. However, if the master first requests class 0 data
or reads the status of the binary output point via the binary output status object, the DPA
considers the status change to already be reported and will not include it in response to a
poll for class 1 data.
Because online/offline events are reported as static data, they only report the current
online/offline status of each point. Thus, if a point toggles online and offline repeatedly
before the change is reported, the binary output status object for the point is only reported
once.
Online/offline events are reported in response to a poll for the class data to which they are
assigned (i.e. class 1, 2 or 3). In addition, if unsolicited responses are enabled for the
class, the events are reported in an unsolicited response.
When online/offline events are included in a response (solicited or unsolicited), the
message contains the range of points which encompass the first and last points whose
online/offline status changed for each given data type. For example, if the fourth, eighth
and tenth binary output points go offline, the response includes the binary output status
for points four to ten.
L NOTE: Because this feature contradicts the rule that static data objects must be
in Class 0 only, some master stations may require this feature to be
turned off.

1.11 TIME AND DATE DATA OBJECT
The Time and Date object is written to the DNP DPA in order to set the time in the GE
HARRIS device. The DNP master station can also READ this object directly. It is not
implemented as Class data (i.e. cannot be read by issuing a Class Data request).
1.12 TIME AND DATE COMMON TIME OF OCCURRENCE
The Time and Date Common Time of Occurrence object represents the absolute time of
day. This object will be sent to the DNP master station before a group of Binary Input
Change with Relative Time objects, given that the GE HARRIS device is currently time
synchronized and was synchronized when the events occurred. The DNP DPA does not
use this object for any other purpose. Refer to Section 4.2 Digital Input Events for more
details.
1.13 UNSYNCHRONIZED COMMON TIME AND DATE
The Unsynchronized Common Time and Date object represents the absolute time of day.
This object will be sent to the DNP master station before a group of Binary Input Change
with Relative Time objects, given that the GE HARRIS device is currently not time
synchronized or was not synchronized when the events occurred. The DNP DPA does not
use this object for any other purpose.
1.14 TIME DELAY FINE
The Time Delay Fine object is returned by the DNP DPA to the master station in
responses to a number of requests. Its main use is in time synchronization. Refer to
section the document "DNP V3.00 Application Layer Protocol Description (P009-
0PD.APP)" for details.

1.15 CLASS DATA OBJECTS
The four Class Data Objects are Class 0, 1, 2, and 3 Data Objects. These objects are sent
in the READ request commands from the DNP master station. They instruct the DNP
DPA to respond with all data of the specified class.

1.16 INTERNAL INDICATIONS
Each Internal Indications object is 1 bit in size by definition. The DNP DPA supports up
to 48 bits of Internal Indications. The first 16 bits are defined in the DNP protocol to
communicate specific information to the DNP master station. These first 16 bits of IIN
follow the function code in all responses. When a request cannot be processed due to
formatting errors or the requested data is not available, the IIN is always returned with the
appropriate bits set.
Bits 16 to 47 of the Internal Indication objects are available to communicate special
system and GE HARRIS device specific information to the DNP master station. These
are OPTIONAL bits which may be used to customize a system. If any of these extra IIN
objects are enabled, they are not returned as part of the header of responses. The master
station may read these objects by making a READ request for Class 0 data or for the IIN
objects specifically.
The first 16 IIN objects are defined in the document "DNP V3.00 Application Layer
Protocol Description (P009-0PD.APP)".
The 17th to 48th Internal Indications objects are used to communicate special
information about the GE HARRIS device and its applications to the DNP master station.
Any number of bits (i.e. objects) in these four bytes of IIN objects, from 1 to 32 bits, can
be used. The assignment of the bits used is specified in the GE HARRIS device's
NVRAM configuration.
The NVRAM configuration for the DNP DPA enables the setting/resetting of individual
bits as the result of the following conditions:
! Digital Inputs in the GE HARRIS device being set and reset.
This feature may be used to report "software" or "pseudo" digital inputs which flag
some condition in the GE HARRIS device. Pseudo digital inputs are owned by DCAs
in the GE HARRIS device. The use and interpretation of each "pseudo" digital input
is completely specific to the DCA owning it.
As an example, a particular DCA may set a GE HARRIS device digital input (pseudo)
when it detects a buffer overflow at a remote device. Another DCA may use another
pseudo digital input to indicate a remote device restart. These pseudo digital inputs
may be configured in the DNP DPA to set/reset bits in the third to sixth bytes of the
Internal Indications object. When this object is sent to the DNP master station, the
master station can process bits to realize specific conditions have occurred in the GE
HARRIS device or devices connected downstream of the GE HARRIS device. The
master station may write to a bit in order to toggle its state.

! The time in the GE HARRIS device is changed by some application other than this
DNP DPA. In many GE HARRIS device systems, several applications commonly
have the capability to modify the internal GE HARRIS device time. A bit in the
Internal Indication object can be used to signal to the DNP master station that the GE
HARRIS device clock has been adjusted by some application other than this DNP
DPA. This information is very useful to the DNP master station and should prompt it
to set the time in the GE HARRIS device or read the new time. If this functionality is
not implemented, the time tagged objects from the DNP DPA could be misinterpreted
by the DNP master station. This bit is cleared when the master explicitly Writes a 0
into this bit of the Internal Indications object in the DNP DPA.
! An Internal Indication object may be enabled (via configuration) to signal that the GE
HARRIS device has gone from ACTIVE to SERVICE mode, or that the DNP DPA
was in SERVICE mode when spawned. This IIN object is set high when the GE
HARRIS device is in SERVICE mode, and cleared when in ACTIVE mode.
The NVRAM configuration for the DNP DPA contains a table enabling the user to
configure bits in the last four bytes of the Internal Indication object. Whenever a bit
changes state in any of the last four bytes of the Internal Indication, either:
! An Unsolicited Response with the entire Internal Indication object is sent to the
DNP master (if enabled).
! The Internal Indication object is buffered and available to be READ by the master
directly or via the next read of Class data.
The DNP master station must be programmed and configured to understand the bits in the
Internal Indication object. It may need to write 0 to some bits to clear them after they
have been read.
The DNP master station may not be able to process the last 4 bytes of the Internal
Indication object. If this is the case, they can be disabled in the DNP DPA's NVRAM
configuration. When disabled, the master station cannot read the last four bytes of the
Internal Indication object from the DNP DPA. The DNP DPA will only transmit the first
two bytes of the object.

1.17 FILE IDENTIFIER OBJECT
The File Identifier Object represents and/or contains 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.
The DNP DPA partially supports the File Identifier Object and its related functionality.
The DNP DPA allows configurations to be passed between a DNP master and a DNP
device either directly, or via one or more intermediate DNP devices.
The software application residing in the data concentrator that communicates with the
master station via DNP is referred to as an Outstation Application. This software is an
outstation with respect to the master. Similarly, the software application residing in the
data concentrator that communicates to an outstation is referred to as a Master
Application. This software is a master with respect to the outstation.
In the context of GE HARRIS devices, the DNP DPA is an Outstation Application, and
the DNP DCA is a Master Application.
Following are protocol descriptions of how the File Identifier Object is used by a master
and one or more data concentrators to perform file upload and file download, and
descriptions of specific processing requirements internal to GE HARRIS DNP devices.

1.17.1 File Download Protocol Description
A DNP master station can download a file to the Outstation Application on one or more
intermediate DNP devices for transfer to a remote device via the Master Application.
The master station must divide the contents of the file into a sequence of file records,
where each file record contains a number of file data bytes equalling the record size,
except for the final record. The final record contains a number of bytes ranging from zero
to one less than the record size. The master station must select a record size such that it
does not exceed the maximum size of the DATA field that the first File Identifier Object
in an application message can contain. Based on an application fragment size of 2K, the
maximum record size can be calculated as follows:
! 2K - request_header_size - object_header_size -
file_identifier_object_control_fields_size
For a File Identifier object with NAME_SIZE = 0, this value equates to 1999. The actual
maximum record size will be 1999 less the maximum number of characters contained in
any file name. The record size must be carefully selected to ensure that all file names will
never exceed the maximum number of characters expected in a file name.
The file records must be encapsulated one or more records at a time into File Identifier
Objects. The master station may either send the file as a single DNP WRITE application
message split into multiple fragments, or may send the file as multiple DNP WRITE
application messages where each message consists of a single fragment.
When sending the download file as a single application message, the APDU data portion
of the application message must consist of the entire download file encapsulated as file
records in sequential order within File Identifier Objects. Each File Identifier Object must
not be split across consecutive fragments. This method prevents the data concentrator
from receiving any other requests (such as controls) from the master station until the
entire file download completes.
When sending the download file in multiple application messages, each application
message must fit in a single fragment. The APDU data portion of each application
message must consist of one or more file records (which comprise only a portion of the
overall file) encapsulated in sequential order in one or more File Identifier Objects. Each
File Identifier Object must not be split across consecutive messages. This method permits
the data concentrator to receive and process any DNP requests received (such as controls)
from the master station during the file download.
In either case, the master station must set the status of the final File Identifier Object to
indicate end of file. In addition, either all File Identifier Objects sent by the master station
must have their File Function set to WRITE, or only the first File Identifier Object may
have its File Function set to WRITE with the remaining File Identifier Objects having
their File Function set to APPEND.

The following diagram illustrates the exchange of DNP messages during a single
application message file download between a master station and Outstation Application:
APPLICATION MESSAGE WRITE FRAGMENT

Application Object Header File Identifier Object
Message Header Object File
FIO
Application Group Qualifier Range Object
Header
Record Record
... Object
Identifier
Control Funciton = 0x46
Object
= 0x1B
or 0x2B
=
# of
Size
(File
Header
and
... Header
and
Size
FIR = 1 Code
Variation or 0x3B Objects
Function
Data Data
Object
FIN = 0 = WRITE = WRITE)
CFM = 1 = 0x01
Application Confirm
Application Message Header
Application
Control Funciton
Internal
FIR = 1 Code =
Indication
FIN = 1 CONFIRM
CFM = 0

Application Group Qualifier Range Object Record Record Object
... Identifier
Control Funciton = 0x46 = 0x1B = Size FIO Header
... Header Size
FIR = 0 Code Object
Variation
or 0x2B
or 0x3B
# of
Objects
Header and
Data
and
Data
Object
FIN = 0 = WRITE
CFM = 1 = 0x01
Application Confirm
Application
Control Funciton
Internal
FIR = 1 Code =
Indication
FIN = 1 CONFIRM
CFM = 0

Application Object Header File Identifier
File Identifier Object
Message Header Object Object
Application Group Qualifier Range Object Record Record
... Object
Control
FIR = 0
Funciton
Code
= 0x46
Object
= 0x1B
or 0x2B
=
# of
Size FIO
Header
Header
and
... Header
and
Size
FIO Header
Variation or 0x3B Objects Data Data STATUS = EOF
FIN = 1 = WRITE
CFM = 1 = 0x01
Application Confirm APPLICATION MESSAGE WRITE RESPONSE

Application Message Header Application Object Header File Identifier
Application
Control Funciton Range
Internal Application Group Qualifier Object
FIR = 1 Code = =
Indication Control Funciton = 0x46 = 0x1B Size
FIN = 1 CONFIRM # of FIO Header
FIR = 1 Code = Object or 0x2B
CFM = 0 Objects STATUS = OK
FIN = 1 RESPONSE Variation or 0x3B
=1
CFM = 0 = 0x01
Figure 1-1 Single Message File Download Communication Sequence

The following diagram illustrates the exchange of DNP application messages during a file
download consisting of multiple application messages between a master station and
Outstation Application:
APPLICATION MESSAGE WRITE REQUEST

FIO
Application Group Qualifier Range Object
Header
Record Record
... Object
Identifier
Control Funciton = 0x46
Object
= 0x1B
or 0x2B
=
# of
Size
(File
Header
and
... Header
and
Size
FIR = 1 Code
Variation or 0x3B Objects
Function
Data Data
Object
FIN = 1 = WRITE = WRITE)
CFM = 0 = 0x01
APPLICATION MESSAGE WRITE RESPONSE

Range
Application Group Qualifier Object
=
Control Funciton = 0x46 = 0x1B Size
# of FIO Header
Objects STATUS = OK
=1
CFM = 0 = 0x01

Application Group Qualifier Range Object Record Record Object
... Identifier
Control Funciton = 0x46 = 0x1B = Size FIO Header
... Header Size
FIR = 1 Code Object
Variation
or 0x2B
or 0x3B
# of
Objects
Header and
Data
and
Data
Object
FIN = 1 = WRITE
CFM = 0 = 0x01

Range
=
# of FIO Header
Objects STATUS = OK
=1
CFM = 0 = 0x01

File Identifier Object
Application Group Qualifier Range Object Record Record
... Object
Control
FIR = 1
Funciton
Code
= 0x46
Object
= 0x1B
or 0x2B
=
# of
Size FIO
Header
Header
and
... Header
and
Size FIO Header
STATUS = EOF
FIN = 1 = WRITE Variation or 0x3B Objects Data Data or OK
CFM = 0 = 0x01

Range
=
# of FIO Header
Objects STATUS = OK
=1
CFM = 0 = 0x01
Figure 1-2 Multiple Message File Download Communication Sequence

The following table describes the WRITE File Identifier Object:
Table 1-1 File Identifier Object WRITE
Field Name Value Notes
NAME_SIZE Varies Equals size of FILE_NAME, see below.
FILE_TYPE 0 = 8-Bit Binary
ATTRIBUTES 0 = REGULAR Not Used.
START_RECORD 0 based index of first file Will be 0 for the first File Identifier Object sent in file
record in remote file to download.
begin writing to.
END_RECORD 0 based index of last file END_RECORD = START_RECORD + (number of

record in remote file to records following File Identifier Object header - 1).
write to.
FILE_SIZE File size in bytes Not Used.
TIME_OF_CREATION Not Used.
PERMISSION Not Used.
FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.
FILE_FUNCTION 3 = WRITE WRITE is required for first File Identifier Object sent
in file download. Thereafter, either WRITE File
Identifier Objects or APPEND File Identifier Objects
may be sent.
STATUS 0 = OK The last File Identifier Object should set its STATUS
5 = EOF, End of File to EOF instead of OK, and all others should set their
STATUS to OK.

FILE_NAME /volume1:/devicename1 Means forward the WRITE file record(s) to the local
/volume2:/devicename2 file storage volume named volume1'. The local
/volume3:/directory1 volume in turn will forward the WRITE file record(s)
/directory2/filename to a remote device named devicename1'. The local
volume in turn forwards the file record(s) to a remote
device named devicename2', which then writes the file
record(s) to its local volume named volume3'.
Specifying the volume names are optional: volume1'
and volume2' default to DNP:, and volume3'
defaults to DBMR:. Specifying directory names are
optional.
/volume1:/devicename1 Means forward the WRITE file record(s) to the local

/volume2:/directory1 file storage volume named volume1'. The local
/directory2/filename volume in turn will forward the WRITE file record(s)
to a remote device named devicename1', which in turn
writes the file record(s) to its local volume named
volume2'. Specifying the volume names are optional:
volume1' defaults to DNP:, and volume2' defaults
to DBMR:. Specifying directory names are optional.
/volume1:/directory1 Means WRITE the file record(s) to the local file

/directory2/filename storage volume named volume1'. The local volume
will in turn write the file record(s) to the file identified
by filename. Specifying the volume1:' name is
optional, and defaults to DBMR:. Specifying
directory names are optional.
RECORD_SIZE 1 to MAX_RECORD_SIZE MAX_RECORD_SIZE is the maximum number of

bytes that may be in the DATA field such that the File
Identifier Object fits completely within a single
application layer fragment. The
MAX_RECORD_SIZE will be decreased by the
maximum size permitted for FILE_NAME.
DATA Varies Contains the binary contents of one file record.

The following table describes the APPEND File Identifier Object:
Table 1-2 File Identifier Object APPEND
START_RECORD 1 or Greater Number of records following the File Identifier

Object header.
END_RECORD Not Used.
FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.
FILE_FUNCTION 0 = APPEND APPEND File Identifier Objects may only be sent

after the first WRITE File Identifier Object has been
sent.
STATUS 0 = OK The last File Identifier Object should set its STATUS
5 = EOF, End of File to EOF instead of OK (or optionally OK if the FIN bit
is being used by the DNP DPA to detect the end of
the file transfer). All other FIOs should have their
STATUS set to OK.

FILE_NAME /volume1:/devicename1 Means forward the APPEND file record(s) to the

/volume2:/devicename2 local file storage volume named volume1'. The local
/volume3:/directory1 volume in turn will forward the APPEND file
/directory2/filename record(s) to a remote device named devicename1'.
The local volume in turn forwards the file record(s) to
a remote device named devicename2', which then
writes the file record(s) to its local volume named
volume3'. Specifying the volume names are optional:
volume1' and volume2' default to DNP:, and
volume3' defaults to DBMR:. Specifying directory
names are optional.
/volume1:/devicename1 Means forward the APPEND file record(s) to the

/volume2:/directory1 local file storage volume named volume1'. The local
/directory2/filename volume in turn will forward the APPEND file
record(s) to a remote device named devicename1',
which in turn writes the file record(s) to its local
volume named volume2'. Specifying the volume
names are optional: volume1' defaults to DNP:, and
volume2' defaults to DBMR:. Specifying directory
names are optional.
/volume1:/directory1 Means APPEND the file record(s) to the local file

/directory2/filename storage volume named volume1'. The local volume
will in turn write the file record(s) to the file
identified by filename. Specifying the volume1:'
name is optional, and defaults to DBMR:.
Specifying directory names are optional.

bytes that may be in the DATA field such that the File
Identifier Object fits completely within a single

The following table describes the RESPONSE File Identifier Object:
Table 1-3 File Identifier Object RESPONSE

START_RECORD On success, 0 based index
of last file record
received.
On failure, equals 0.
END_RECORD On success, 0 based index END_RECORD = START_RECORD
of last file record
received.
FILE_SIZE On success, file size in Not Used.
bytes.
PERMISSION On failure, equals 0. Not Used.
FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.
FILE_FUNCTION 255 = RESPONSE
STATUS 0 = OK, success.
1 = File name does not
exist.
2 = Unable to store file.
3 = Invalid or disallowed
FILE_FUNCTION.
4 = Device offline, or
device busy.
FILE_NAME Same as WRITE or
APPEND request
FILE_NAME.
RECORD_SIZE 0
DATA N/A

The FILE_NAME field is designed so that File Identifier Objects containing
configurations can be downloaded to an end device via any number of intermediate DNP
devices.
L NOTE: The DNP master station must have detailed routing information in
order to construct the FILE_NAME field.
Figure 1-3 is a simple illustration of how the first File Identifier Object is passed
through the system from a master station to an end device via two intermediate DNP
devices.

FILE_NAME = /deviceA/deviceB/config1
DNP DPA invokes IFS

Open with FILE_NAME First Intermediate DNP device
Of DNP:/deviceA/
DNP DPA has Address 1
deviceB/config1"
DNP DCA configuration says

deviceA has DST = 22
DNP DCA addresses request
with the object to DST = 22
FILE_NAME = /deviceB/config1
DNP DPA invokes IFS

open with FILE_NAME deviceA:
Of DNP:/deviceB/config1" Second Intermediate DNP device
DNP DCA configuration says
deviceB has DST = 8
DNP DCA addresses request
with the object to DST = 8
FILE_NAME = /config1
deviceB:
End DNP device
Figure 1-3 Passing A File Identifier Object via DNP Devices

1.17.2 File Download DPA Processing Requirements
If the DPA receives a DNP Application Layer WRITE request, whose File Identifier
Object(s) meet the conditions outlined in the above tables, then, the following sequence
occurs for the first File Identifier Object in a Master Station request received by the DPA:
1. The DPA parses out the first /symbol from the FILE_NAME field.
2. If only a file name remains (i.e. no path is prepended, and no volume name is
supplied), then the DPA prepends a volume name of DBMR:.
3. If a path is prepended to the file name, and a volume name does not exist for the first
intermediate device name in the path, then the DPA prepends a volume name
DNP:.
4. If the File Function of the first File Identifier Object is set to WRITE, and its Start
Record is set to 0, then the DPA performs an Installable File System file open
operation utilizing the modified file name and a write access mode.
5. Next, the DPA performs an Installable File System file write operation based on the
contents of the file record(s) contained within the first File Identifier Object.
If the first File Object Identifier has already been received and processed as above, then
the DPA performs the following sequence for all except the last file record:
1. The DPA performs an Installable File System file write operation based on the
contents of the file record(s) contained within the next received File Identifier Object.
The DPA performs the following sequence for the last file record contained in the DNP
request:
1. The DPA performs an Installable File System file write operation based on the
contents of the file record(s) contained within the last File Identifier Object.
2. If the last File Identifier Object has a Status set to End of File, then the DPA performs
an Installable File System file close operation.
3. The DPA assembles and replies to the master station with a File Identifier Object
whose File Function is RESPONSE, with a Status set to OK.
Note that A GE HARRIS DNP device will not receive while it waits for a response from
a down stream device. It is "locked out" to master requests. Also, the DNP master station
must have a larger response timeout than the DNP DCA in the first GE HARRIS DNP
device, which in turn must have a larger response timeout than the DNP DCA in the next
GE HARRIS DNP device.

1.17.3 File Download Backward Compatability Issues
Special handling must be performed by the Outstation Application to ensure backward
compatability with older GE HARRIS implementations of file download. The method the
Outstation Application uses to determine whether or not to perform this special handling
is based on file name field of the File Identifier Object. If the file name begins with either
/DNPDCAx or /VOLUMEx, then the Outstation Application must perform special
handling to ensure backward compatibility. Otherwise, this section may be ignored.
Older GE HARRIS implementations consider each file to consist of only a single record.
Therefore the protocol communication expects a single File Identifier Object, and does
not use the EOF status to indicate end of file. Rather the STATUS is always set to OK.
The following diagram illustrates the exchange of DNP application messages that occurs
during a file download between a master station and an Outstation Application using an
older GE HARRIS file download implementation:

Message Header Object
Range FIO
Application Group
= Header Record
Control Funciton = 0x46 Qualifier Record
# of (File Header
FIR = 1 Code Object = 0x07 Data
Objects Function
FIN = 0 = WRITE Variation
=1 = WRITE)
CFM = 0 = 0x01

Range Object
Application Group
=
Control Funciton = 0x46 Qualifier
# of FIO Header
FIR = 1 Code = Object = 0x07
Objects STATUS = OK
FIN = 1 RESPONSE Variation
=1
CFM = 0 = 0x01
Figure 1-4 File Download Backward Compatible Communication Sequence

The following table describes the WRITE File Identifier Object:
Table 1-4 Backward Compatible File Identifier Object WRITE
START_RECORD 0 based index of file record in

remote file to write to.
END_RECORD 0 based index of file record in END_RECORD = START_RECORD

remote file to write to.
FILE_SIZE Memory address to store file Used only when downloading configuration from
record on destination DNP a master station directly to a data concentrators
device. operating system. In this case, the FILE_NAME
field will equal VOLUMEx.
FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.
FILE_FUNCTION 3 = WRITE
STATUS 0 = OK

FILE_NAME /DNPDCAx Means forward the WRITE file record to a

/DNPDCAy/filename remote device named DNPDCAx', where xis a
decimal value which identifies the DNP device to
forward through. Device DNPDCAxin turn
forwards the file record to remote device named
DNPDCAywhere yis a decimal value which
identifies the DNP device to forward through.
The end device DNPDCAyin turn stores the
file record to a local file named filename.
/DNPDCAx/filename Means forward the WRITE file record to a

remote device named DNPDCAx', where xis a
decimal value which identifies the DNP device to
forward through. Device DNPDCAxin turn
stores the file record to a local file named
filename.
/VOLUMEx Means write the file record to the local

configuration of the data concentrator. xis any
decimal value, currently ignored.
RECORD_SIZE 1 to MAX_RECORD_SIZE MAX_RECORD_SIZE is the maximum number

of bytes that may be in the DATA field such that
the File Identifier Object fits completely within a
single application layer fragment. The

START_RECORD On success, 0 based index

of last file record received.
END_RECORD On success, 0 based index END_RECORD = START_RECORD

of last file record received.
FILE_SIZE On success, file size in Not Used.

bytes.
FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.

1 = File name does not
exist.
2 = Unable to store file.
FILE_FUNCTION.
4 = Device offline, or
device busy.
FILE_NAME Same as WRITE request

FILE_NAME.
RECORD_SIZE 0
DATA N/A
Table 1-5 Backward Compatible File Identifier Object RESPONSE

1.17.4 File Upload Protocol Description
A DNP master station can upload a file from the Outstation Application residing on an
end device via one or more intermediate DNP devices.
The master station may ask to obtain the file one record at a time receiving multiple
responses, or may ask to receive all the file records in one single response message. Each
file record within a response will be encapsulated by one File Identifier Object. For each
request, the master station must create a single application message with its Function
Code set to Write, and with the APDU data portion consisting of a single File Identifier
Object whose File Function is set to READ.
When requesting the upload file in a single application message, the APDU data portion
of the application message response must consist of the entire upload file encapsulated as
single file records in sequential order within File Identifier Objects. Each File Identifier
Object must not be split across consecutive fragments. This method prevents the data
concentrator from responding to any other requests (such as controls) from the master
station until the entire file upload completes.
When requesting the upload file in multiple application messages, the APDU data portion
of each application message response must consist of one file record encapsulated in one
File Identifier Object. This method permits the data concentrator to respond to any DNP
requests received (such as controls) from the master station during the file upload.
In either case, the final record received by the master station will have its File Identifier
Object status set to End of File (EOF) to indicate to the master station that the entire file
has been successfully uploaded. Optionally, if the master station will not upload a file via
multiple application messages, the master station may set the status to OK (thereby
depending on the FIN bit in the final fragment to indicate the end of the file transfer).

upload consisting of multiple application write and write response messages (the file
contains n+1 records):

Range Object
= FIO Header
# of (File Function = READ
FIR = 1 Code Object or 0x2B
Objects START_RECORD = 0
FIN = 1 = WRITE Variation or 0x3B
=1 END_RECORD = 0)
CFM = 0 = 0x01

Range
Application Group Qualifier Object FIO Header Record
=
Control Funciton = 0x46 = 0x1B Size (STATUS = OK Header
# of
FIR = 1 Code = Object or 0x2B START_RECORD = 0 and
Objects
FIN = 1 RESPONSE Variation or 0x3B END_RECORD = 0) Data
=1
CFM = 0 = 0x01

Range Object
= FIO Header
Objects START_RECORD = 1
=1 END_RECORD = 1)
CFM = 0 = 0x01

Range
=
# of
Objects
=1
CFM = 0 = 0x01

Range
= FIO Header
Objects START_RECORD = n
=1 END_RECORD = n)
CFM = 0 = 0x01

Range
=
Control Funciton = 0x46 = 0x1B Size (STATUS = EOF Header
# of
FIR = 1 Code = Object or 0x2B START_RECORD = n and
Objects
FIN = 1 RESPONSE Variation or 0x3B END_RECORD = n) Data
=1
CFM = 0 = 0x01
Figure 1-5 Multiple Message File Download Communication Sequence

upload consisting of a single application write and single write response message (the file
contains n+1 records):

Application Group Qualifier Range = Object
Control Funciton = 0x46 = 0x1B # of Size FIO Header
FIR = 1 Code Object or 0x2B Objects (File Function = READ
FIN = 1 = WRITE Variation or 0x3B =1 START_RECORD = 0
CFM = 0 = 0x01 END_RECORD= 65535)
APPLICATION WRITE RESPONSE FRAGMENT

Range
=
# of
Objects
=1
CFM = 1 = 0x01
Application Confirm
Application
Control Funciton
Internal
FIR = 1 Code =
Indication
FIN = 1 CONFIRM
CFM = 0

Range
=
# of
Objects
=1
CFM = 1 = 0x01
Application Confirm
Application
Control Funciton
Internal
FIR = 1 Code =
Indication
FIN = 1 CONFIRM
CFM = 0

Range
=
Control Funciton = 0x46 = 0x1B Size (STATUS =EOF or OK Header
# of
FIR = 0 Code = Object or 0x2B START_RECORD = n and
Objects
FIN = 1 RESPONSE Variation or 0x3B END_RECORD = n) Data
=1
CFM = 1 = 0x01
Application Confirm
Application
Control Funciton
Internal
FIR = 1 Code =
Indication
FIN = 1 CONFIRM
CFM = 0
Figure 1-6 Single Message File Upload Communication Sequence

The following table describes the READ File Identifier Object:
Table 1-6 File Identifier Object READ
START_RECORD 0 based index of first file START_RECORD = record being read

record in remote file to (multiple requests) or
begin reading from. START_RECORD = 0
(single request)
END_RECORD 0 based index of last file END_RECORD = START_RECORD

record in remote file to (multiple requests) or
read from. END_RECORD = 65535
(single request)
FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.
FILE_FUNCTION 9 = READ
STATUS 0 = OK

FILE_NAME /volume1:/devicename1 Means forward the READ request to the local file
/volume2:/devicename2 storage volume named volume1'. The local volume in
/volume3:/directory1 turn will forward the READ request to a remote device
/directory2/filename named devicename1'. The local volume in turn forwards
the read request to a remote device named
devicename2', which then reads the requested file
record(s) from its local volume named volume3'.
and volume2' default to DNP:, and volume3' defaults
to DBMR:. Specifying directory names are optional.
/volume1:/devicename1 Means forward the READ request to the local file

/volume2:/directory1 storage volume named volume1'. The local volume in
/directory2/filename turn will forward the READ request to a remote device
named devicename1', which in turn writes the file
record(s) to its local volume named volume2'.
defaults to DNP:, and volume2' defaults to DBMR:.
Specifying directory names are optional.
/volume1:/directory1 Means READ the file record(s) from the local file
/directory2/filename storage volume named volume1'. The local volume will
in turn read the file record(s) from the file identified by
filename. Specifying the volume1:' name is optional,
and defaults to DBMR:. Specifying directory names are
optional.
RECORD_SIZE 0
DATA N/A

START_RECORD On success, 0 based index of

last file record received.
END_RECORD On success, 0 based index of END_RECORD = START_RECORD

FILE_SIZE On success, file size in bytes. Not Used.

FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.
STATUS 0= OK, success. For a successful file upload, STATUS must be OK,
1= File name does not exist. except for the File Identifier Object containing the
2= Unable to store file. last record of the file upload which should set its
3= Invalid or disallowed STATUS to EOF (or optionally OK if the FIN bit is
FILE_FUNCTION. being used to detect the end of the file transfer).
4 = Device offline, or device
busy.
5 = EOF, End of file.

FILE_NAME.

bytes that may be in the DATA field such that the
File Identifier Object fits completely within a single
Table 1-7 File Identifier Object RESPONSE

1.17.5 File Upload DPA Processing Requirements
If the DPA receives a DNP Application Layer WRITE request, whose File Identifier
Object(s) meet the conditions outlined in the above tables, then, the following sequence
occurs for the File Identifier Object in a Master Station request received by the DPA:
1. The DPA parses out the first / symbol from the FILE_NAME field.
2. If only a file name remains (i.e. no path is prepended, and no volume name is
supplied), then the DPA prepends a volume name of DBMR:.
3. If a path is prepended to the file name, and a volume name does not exist for the first
intermediate device name in the path, then the DPA prepends a volume name
DNP:.
4. If the file has not already been opened, the DPA performs an Installable File System
file open operation utilizing the modified file name and a read access mode.
5. The DPA performs an Installable File System file read operation for the first file
record requested by the master station File Identifier Object.
6. If this is the only record requested, then the DPA sends a complete DNP response
message. Otherwise, only the first fragment of the response message is sent. In either
case, the response message consists of a single File Identifier Object whose File
Function is set to RESPONSE, whose Status is set to OK, and whose Data contains
the file record.
7. If the file record is the last file record for the file being uploaded, then the DPA sets
the File Identifier Object status to End of File prior to sending the response, and the
DPA performs an Installable File System close operation.
If the first File Object Identifier has already been received and processed as above, then
the DPA performs the following sequence for all of the remaining file records requested
by the master station:
1. The DPA performs an Installable File System file read operation for each file record
requested by the master station File Identifier Object, and sends the next fragment of
the DNP response consisting of a single File Identifier Object encapsulating the next
file record.
2. If the file record is the last file record for the file being uploaded, then the DPA sets
the File Identifier Object status to End of File prior to sending the response, sends the
response as the final fragment, and then performs an Installable File System close
operation.

1.17.6 File Upload Backward Compatibility Issues
Special handling must be performed by the Outstation Application to ensure backward
compatibility with older GE HARRIS implementations of file upload. The method the
Outstation Application uses to determine whether or not to perform this special handling
is based on the file name field of the File Identifier Object. If the file name begins with
either /DNPDCAx or /VOLUMEx, then the Outstation Application must perform
special handling to ensure backward compatibility. Otherwise, this section may be
ignored.
The following diagram illustrates the exchange of DNP application messages that occurs
during a file upload between a master station and an Outstation Application using an
older GE HARRIS file upload implementation:

Range Object
Application Group
=
Control Funciton = 0x46 Qualifier FIO Header
# of
FIR = 1 Code Object = 0x07 (File Function =
Objects
FIN = 1 = WRITE Variation READ)
=1
CFM = 0 = 0x01

Application Object Header
Message Header File Identifier Object
Object
Range FIO
Application Group
=
Control Funciton = 0x46 Qualifier Header Record Record
# of
FIR = 1 Code = Object = 0x07 STATUS Header Data
Objects
FIN = 1 RESPONSE Variation = OK
=1
CFM = 0 = 0x01
Figure 1-7 File Upload Backward Compatible Communication Sequence
The protocol communication expects a single File Identifier Object in response, and does
not use the EOF status to indicate end of file. Rather, on success, the STATUS is always
set to OK.

The following table describes the READ File Identifier Object:
START_RECORD 0
END_RECORD 0 END_RECORD = START_RECORD
FILE_SIZE Not Used.
FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.
FILE_FUNCTION 9 = READ
STATUS 0 = OK
FILE_NAME /DNPDCAx Means forward the READ request to a remote device

/DNPDCAy/filename named DNPDCAx', where xis a decimal value
which identifies the DNP device to forward through.
Device DNPDCAxin turn forwards the READ
request to remote device named DNPDCAywhere
yis a decimal value which identifies the DNP
device to forward through. The end device
DNPDCAyin turn reads the file record from a local
file named filename.
/DNPDCAx/filename Means forward the READ request to a remote device

named DNPDCAx', where xis a decimal value
which identifies the DNP device to forward through.
Device DNPDCAxin turn reads the file record
from a local file named filename.
/filename Means read the file record from a local file named
filename.
RECORD_SIZE 0
DATA N/A
Table 1-8 Backward Compatible File Identifier Object READ

START_RECORD On success, 0 based index of

END_RECORD On success, 0 based index of END_RECORD = START_RECORD

FILE_SIZE On success, file size in bytes. Not Used.

FILE_ID Not Used.
OWNER_ID Not Used.
GROUP_ID Not Used.

1 = File name does not exist.
FILE_FUNCTION.
4 = Device offline, or device
busy.

FILE_NAME.

bytes that may be in the DATA field such that the
File Identifier Object fits completely within a single
Table 1-9 Backward Compatible File Identifier Object RESPONSE

1.18 STORAGE OBJECTS
The DNP DPA allows a master station to read two Storage Objects indicating the amount
of memory currently used by the DNP DPA to store Binary Input Change objects.
The Master must send a request using the READ function code and containing the
following object header:
Object Group Variation Qualifier
81 Either 1 or 0 6
Storage Objects Permitted No Range Field
(request all objects)
If the Master uses any qualifier other than 6, the DNP DPA does not respond with Storage
Objects, but sets the OUT OF RANGE Internal Indication in its response (Bit 2 of the
second octet).
L NOTE: The DNP DPA does not return the Storage Objects in response to a
poll for Class Data (Group 60, Variations 1 to 4). It only does so in
response to a specific request for Storage Objects, as described above.

If the format of the request is correct the DNP DPA sends a response containing two
objects, as described below:
Group Var. Qualifier Range Status Group Var. Status Group Var.
81 1 7 2 % Full, 2 1 % Full, 2 2
Storage Range is an Two Overflow Binary Change Overflow Binary Change
Objects 8-Bit objects Bit Input Without Bit Input With
Quantity follow Change Time Change Time
(COS) (SOE)
One object describes the amount of memory currently used for storing Binary Input
Change with Time events, also known as Sequence of Events (SOE) indications. The
other object describes the amount of memory currently used for storing Binary Input
Change Without Time events, also known as Change of State (COS) indications.
L NOTE: The DNP DPA returns both storage objects even if no memory was
configured for either type of event. If no memory was configured, the
PERCENTAGE field of the appropriate storage object is returned as 0
and the OVERFLOW bit is clear (0).

1.19 TIME ADJUSTMENT ANALOG INPUTS (CCU BASE ONLY)
When running on the CCU Base System, the DNP DPA supports returning a custom time
adjustment object as analog input points 65534 and 65535. The points do not contain an
absolute time, but the time adjustment which occurred when the WESDAC device last
received a time synchronization. Both are signed values and are calculated by subtracting
the old time from the new time. Both points contain signed values and are returned in the
following format:
! Date (Analog Input point 65535) Bit 31 - 16: year, A.D.
Bit 15 - 8: month (1-12).
Bit 7 - 0: day (1-31).
! Time (Analog Input point 65534) Bit 31 - 0: millisecond ticks.
These objects are never included in response to a class 0 data poll, or in response to a read
request for all analog inputs. They can always be read by a master request for points
65534 and 65535 of the 32-Bit Analog Input Without Flag object (Object 30, Variation
3). In addition, the objects can be assigned to class 1, 2 or 3 in the configuration.
Then, whenever the WESDAC device is time synchronized, the objects become an event
available to be read in a class data poll, or included in an unsolicited response. The DPA
reports the event using the 32-Bit Analog Input Without Flag object.

1.20 RESTRICTIONS INHERENT TO THE DNP DPA
The above described functionality and configuration imposes some restrictions on the
system. These restrictions simplify the software and make configuration easier. The
inherent restrictions are:
! The objects and variations always start at RANGE equals 0. In order to start at a non
zero range, configuration tables needs to be padded with SPARE records (i.e. records
where the System Point number is set to -1). This is wasteful of NVRAM. Wasting
NVRAM in this way is not advised as it reduces the NVRAM available for buffering
DNP change events and usage by other applications installed in the GE HARRIS
device.
! Unsolicited Responses can be enabled on a class basis - not a point basis.
! Class 0 is reserved for non-event or non-change data. Event data cannot be returned as
Class 0 data. Non-event data cannot be returned as anything other than Class 0 data.
! Multi-fragment requests are not supported.
! The analog input and counter input events are not buffered. When these events are
read, they report the current value of the data point.

Chapter 2:
PROTOCOL IMPLEMENTATION
This chapter discusses the limitations and assumptions of the DNP V3.00 protocol
implementation for the DNP DPA. A detailed discussion of the protocol transactions is
not included in this document. Refer to the DNP V3.00 Application Layer Protocol
Description for more information. The DNP DPA follows the implementation described
in the protocol description document except for the limitations discussed in this chapter.
In the case of contention between these documents, the DNP DPA functions as specified
in this document.

2.1 FUNCTION CODES USED BY THE DNP DPA
The following function codes are supported by the DNP DPA:

! CONFIRM (Function code 0)
! READ (Function Code 1)
! WRITE (Function Code 2)
! SELECT (Function Code 3)
! OPERATE (Function Code 4)
! DIRECT OPERATE (Function Code 5)
! DIRECT OPERATE - NO ACKNOWLEDGEMENT (Function Code 6)
! IMMEDIATE FREEZE (Function Code 7)
! IMMEDIATE FREEZE - NO ACK (Function Code 8)
! FREEZE AND CLEAR (Function Code 9)
! FREEZE AND CLEAR - No ACK (Function Code 10)
! COLD RESTART (Function Code 13)
! WARM RESTART (Function Code 14)
! START APPLICATION (Function Code 17)
! STOP APPLICATION (Function Code 18) - Partially Supported
! SAVE CONFIGURATION (Function Code 19) - Partially Supported
! ENABLE SPONTANEOUS MESSAGES (Function Code 20)
! DISABLE SPONTANEOUS MESSAGES (Function Code 21)
! ASSIGN CLASSES (Function Code 22)
! DELAY MEASUREMENT (Function Code 23)
! RESPONSE (Function Code 129)
! UNSOLICITED RESPONSE (Function Code 130)
The following function codes are not supported by the DNP DPA:
! FREEZE WITH TIME (Function Code 11)
! FREEZE WITH TIME - NO ACK (Function Code 12)
! INITIALIZE DATA (Function Code 15)
! INITIALIZE APPLICATION (Function Code 16)
The DNP DPA treats a received message as a duplicate if the message length, the
application sequence number, and the message function code are the same as in the
previous request.

2.1.1 CONFIRM Function Code
The DNP DPA automatically transmits the CONFIRMation response using the
CONFIRM function code whenever a message is received from the DNP master station
and this message indicates it wants a CONFIRMation (bit CON in the Application
Control field is set). Note that the CONFIRMation response (and ALL other responses)
include the Internal Indication (IIN) field.
If the received message has format errors or cannot be processed by the DNP DPA, the
CONFIRMation response is transmitted but the IIN field will have one of bits 0 to 2 in
the second byte of the IIN set. This is effectively a NON-CONFIRMation response. It
tells the master station that the DNP DPA will do no further processing of the request.
The CONFIRMation response from the DNP DPA always has bit CON = 0. This means
that the DNP DPA never expects a confirmation of its CONFIRM response.
2.1.2 RESPONSE Function Code

The RESPONSE Function Code is used in the DNP DPA responses to most DNP master
station requests.
L NOTE: The CON bit is always set in responses from the DNP DPA that
contain data event objects. That is, the DNP DPA expects a
CONFIRMation response from the DNP master station for any DPA
READ response or Unsolicited Response containing event objects. The
only exception to this rule is explained in Chapter 3: SILENT
MASTER MODE. The DNP DPA can be configured to perform
retries if it times out waiting for the CONFIRMation response (refer to
Section 2.2 Communication Flow Control and Reliability).
2.1.3 UNSOLICITED RESPONSE Function Code

The UNSOLICITED RESPONSE Function Code is used in the DNP DPA for
spontaneous responses to the DNP master station. The master station does not poll for
Unsolicited Responses; they are automatically sent from the GE HARRIS device.
The DNP DPA always requests CONFIRMations for its Unsolicited Responses (one
exception is explained in Chapter 3). The DNP DPA can be configured to perform retries
if it times out waiting for the CONFIRMation response (refer to Section 2.2
Communication Flow Control and Reliability).

2.1.4 READ Function Code
The READ request from the DNP master station can request one or more objects from the
DNP DPA. The DPA response uses the RESPONSE function code. Multi-fragment
responses are supported. The DPA sets the CON bit in each response that contains event
objects (i.e. it always expects a CONFIRMation message from the DNP master station).
In addition, the CON bit is set when reporting static data objects such as delta counters
(this is required to know when to reset the delta being reported). However, the CON bit is
never set when the DNP DPA is configured to operate in Silent_Master Operating Mode
(discussed in Chapter 3).
If the DNP master station sends a READ request where some of the objects are defined in
the DNP DPA and some are not defined, the DPA response contains data for the valid
objects. The invalid objects are ignored. Bits 1 and 2 in the second octet of the IIN in the
response indicate that some objects are not defined in the DNP DPA.
The DNP master station generally attempts to READ data event objects from the DNP
DPA. Data event objects are objects like the Binary Input with Time object. These event
objects do not exist unless a data change has occurred to create them. It is therefore likely
that the DNP DPA occasionally will not have objects available to be READ by the DNP
master station.
The DNP DPA does not support READ requests with Qualifier Codes 3, 4, 5 and 11.
These codes are absolute address identifiers and the variable array qualifier code.
The DNP DPA never returns the following objects in a READ response. For example, the
Control Relay Output Block is only used in control requests. As another example, a
request to read the Class 0 Data object does not return the Class 0 Data object, but all of
the data objects assigned to class 0.
! Pattern Control Block
! Pattern Mask
! Class 0, 1, 2 and 3 Data
! Time and Date with Interval
! Time Delay Fine

2.1.5 WRITE Function Code
The WRITE function code is used for moving objects from the DNP master station to the
DNP DPA. The following objects may be written to the DNP DPA by the DNP master
station using the WRITE request:
! Internal Indication (for clearing bits)
! Binary Input with Status
! Time and Date Object
2.1.6 SELECT and OPERATE Function Codes

The SELECT request is used to select (or Arm) one or more control relay outputs and
analog outputs in the GE HARRIS device. The following OPERATE request will activate
the selected outputs. The DNP master station may send the following objects in the
SELECT and OPERATE requests:
! 16-Bit Analog Output
! 32-Bit Analog Output (if most significant 16 bits are not used)
The format of the SELECT and OPERATE request are identical except for the Function
Code. The SELECT and OPERATE requests must be received by the DNP DPA within a
configurable time and must contain the same objects and data in order for the operation to
be successful. If a request other than an OPERATE request follows a SELECT request,
the SELECT is automatically canceled.
Regardless whether the control point requested is on-line or off-line, a control operation
will be attempted by the DNP DPA.
The DPA responses to the SELECT and OPERATE requests are almost identical to the
requests except:
! The Response Header is different to the Request Header, with the IIN bytes included
and using the RESPONSE Function Code.
! Any Control Relay Output Block, 16-Bit Analog Output Block, or 32-Bit Analog
Output Block objects in the response have their STATUS field filled in by the DNP
DPA. This field reflects the success or non-success of the control operation.
On the CCU Base System, binary outputs owned by the DPA may be assigned to a group.
In this case, a SELECT or OPERATE request will always fail if binary outputs have not
been enabled for the DPA. Refer to Section 4.4 Binary Output Enable for details.

2.1.7 DIRECT OPERATE and DIRECT OPERATE - NO ACK Function
Codes
The DIRECT OPERATE request does not require a previous SELECT request. It is
functionally identical to the OPERATE request except that it may also include Pattern
Control Block and Pattern Mask objects.
The DIRECT OPERATE - NO ACKNOWLEDGEMENT request is the same as the
DIRECT OPERATE request except the DNP DPA will not respond to the request.

2.1.8 IMMEDIATE FREEZE and IMMEDIATE FREEZE - NO ACK
Function Codes
The IMMEDIATE FREEZE request makes the GE HARRIS device copy specified
objects to a freeze buffer. The DNP DPA only supports the freezing of counter objects.
The IMMEDIATE FREEZE request specifies data objects to be frozen as part of the
request. The following objects can be included in the request:
! Object 20, Variation 0 (all counters)
L NOTE: Although the DPA accepts a request to freeze frozen counter objects,
the recommended procedure is to issue a request to freeze counter
objects.
The frozen counters are available for reading via the 32-Bit Frozen Binary Counter, 32-
Bit Frozen Binary Counter without Flag, 16-Bit Frozen Binary Counter, and 16-Bit
Frozen Binary Counter without Flag objects.
The DNP DPA response to a IMMEDIATE FREEZE request uses the RESPONSE
Function Code.
The IMMEDIATE FREEZE - NO ACKNOWLEDGEMENT request is identical in
format and function to the IMMEDIATE FREEZE request. The DNP DPA does not
respond to this request.
L NOTE: FREEZE requests cannot be routed through the DNP DPA to a DCA to
pass to a downstream device. FREEZE requests are local to the GE
HARRIS device only.

2.1.9 FREEZE AND CLEAR and FREEZE AND CLEAR - NO ACK
Function Codes
The FREEZE AND CLEAR request makes the DNP DPA copy specified objects to a
freeze buffer. The value of the objects is then cleared. The DNP DPA only supports the
freezing and clearing of counter objects.
The FREEZE AND CLEAR request specifies data objects to be frozen and cleared as part
of the request. The following objects can be included in the request:
! Object 20, Variation 0 (all counters)
L NOTE: Although the DPA accepts a request to freeze and clear frozen counter
objects, the recommended procedure is to issue a request to freeze and
clear counter objects.
The frozen counters are available for reading via the Frozen Counter objects. After the
counters are frozen, they are automatically cleared to zero. The clearing of counters
automatically makes the DNP DPA generate one of the following counter event objects
for each counter point (when the counter is configured to generate events):
These objects may be READ by the DNP master station or will be automatically reported
to the DNP master station as Unsolicited Responses.
The FREEZE AND CLEAR - NO ACKNOWLEDGEMENT request is identical in
format and function to the FREEZE AND CLEAR request. The DNP DPA does not
respond to this request.
L NOTE: FREEZE AND CLEAR requests cannot be routed through the DNP
DPA to a DCA to pass to a downstream device. FREEZE AND
CLEAR requests are local to the GE HARRIS device only.

2.1.10 COLD RESTART Function Code
The DPA responds with a positive acknowledgement to the request including a Time
Delay Coarse object telling the master station how long to wait for the GE HARRIS
device to complete its restart sequence. Once the response has been transmitted, the DPA
clears any buffered COS/SOE in NVRAM and forces the GE HARRIS device to reset.
2.1.11 WARM RESTART Function Code

The DPA processes this request by clearing all buffered events. This includes COS, SOE,
analog, counter, and frozen counter events. In addition, it resets its communication
parameters (i.e. it clears any pending request and resets the next expected sequence
number).
2.1.12 START APPLICATION Function Code

The DPA responds with a positive acknowledgement to the request including a Time
Delay Coarse object telling the master station how long to wait for the GE HARRIS
device to complete its restart sequence. Once the response has been transmitted, the DPA
clears any buffered COS/SOE in NVRAM and forces the GE HARRIS device to reset.
2.1.13 STOP APPLICATION Function Code

When running on the CCU Base System, the DNP DPA processes the STOP
APPLICATION request by sending a command to the WIN to put the GE HARRIS
device (i.e. all applications) into SERVICE mode. The DPA does not process objects sent
in the request. The STOP APPLICATION request must be sent to the DPA before the
master station attempts to download a new configuration. Refer to Section 4.3
Configuration Download and System Restart for details.
If the CCU Base System is not in use, the DNP DPA sends a dummy response to the
STOP APPLICATION request but does nothing else.

2.1.14 SAVE CONFIGURATION Function Code
When running on the CCU Base System, the DPA processes the SAVE
CONFIGURATION request by sending a command to the WIN to cause configuration
transfer from the RTU to a redundant RTU (if it exists). Any data objects within the
SAVE CONFIGURATION request are not processed by the DPA. Refer to Section 4.3
Configuration Download and System Restart for details.
If the CCU Base System is not in use, the DPA sends a dummy response to this request
with a Time Delay Fine object containing a time of zero.
2.1.15 ENABLE/DISABLE SPONTANEOUS MESSAGE Function

Codes
The ENABLE SPONTANEOUS MESSAGE and DISABLE SPONTANEOUS
MESSAGE requests enable and disable the spontaneous reporting of objects specified in
the object header. These objects are reported as Unsolicited Messages.
The DNP DPA is constrained such that spontaneous reporting can only be
enabled/disabled on a Class basis. The DNP master station must send an object header
specifying class data. Individual objects, variation and information element ranges cannot
be enabled/disabled.

2.1.16 ASSIGN CLASSES Function Code
In its configuration, the DNP DPA requires the user to assign a class to each event object
associated with a static data object. Assigning the event object to class 0 disables the
generation of event objects on the point. A DNP master station can send an ASSIGN
CLASSES request to change the class an event object for a particular data point is
assigned to.
The request specifies a Class 1, 2 or 3 object header and the header of a static object for
the appropriate data point(s). For example, if the first eight binary input points are
enabled for COS, the master can assign COS events on these points to Class 2 by sending
an ASSIGN CLASSES request containing the following object headers:
! Class 2 (Obj. 60, Var. 3)
! Binary Input (Obj. 1, Var. 0, Indices 0-7)
Such a request does not mean the static objects now belong to Class 2; static objects
belong to Class 0 by definition. Instead, the static objects represent the data points
themselves, and the request means all event objects generated by the data points belong to
the specified Class.
The DPA supports assigning Classes right down to a range of information elements
within an object and variation. For example, three 16-Bit Counter Change Event without
Time objects could be assigned sequentially to Class 1, Class 2 and Class 3 data.
The DPA is constrained so that Class 0 is reserved for non-event or non-change data
objects (e.g. Binary Input with Status objects). Thus, if the ASSIGN CLASSES request
assigns a range of points to class 0, this disables the generation of events on the specified
points.
The DPA does not support using the ASSIGN CLASSES function code to change the
class of online/offline status changes or time adjustment changes.
2.1.17 DELAY MEASUREMENT Function Code

The DELAY MEASUREMENT function code is used in time synchronization. The DPA
responds to the delay measurement request with a Time Delay Fine object. This object
contains the amount of time between the GE HARRIS device receiving the first bit of the
first byte of the request and the time of transmission of the first bit of the first byte of the
response.

2.2 COMMUNICATION FLOW CONTROL AND RELIABILITY
The flow of requests and responses between the DNP master station and the DNP DPA is
specified in the document "DNP V3.00 Application Layer Protocol Description (P009-
0PD.APP)".
The DNP DPA supports message retries at the application layer. A configurable
parameter allows the user to set the maximum number of times the DPA attempts to send
a message. The DPA performs retries when:
! A requested CONFIRMation Response is not received before a timeout interval
expires.
! The data link returns a transmit status failure indicating the message could not be
successfully sent.
These cases apply to both solicited and unsolicited responses.
The DNP DPA also has a configurable parameter for determining whether or not it
requests the data link to transmit messages using the data link confirm service.

Chapter 3:
SILENT MASTER OPERATING MODE
The DNP DPA is sometimes installed in an operating environment where

CONFIRMation Responses are not sent by the master station in reply to Responses from
the DNP DPA. This mode of operation (called SILENT MASTER Operating Mode) is
suited to transmission environments where communication delay overheads are large.
A radio switched packet network may take many seconds, possibly several minutes, to
transport data from a GE HARRIS device to a master station. If CONFIRMation of
responses was required in this situation, the throughput of the system would be greatly
reduced. For example, without CONFIRMations a GE HARRIS device may send
Unsolicited Responses to the master station as often as required. If CONFIRMations were
required, Unsolicited Responses could not be sent more frequently than the turnaround
time for the GE HARRIS device to master message plus the master to GE HARRIS
device CONFIRMation response.
In the SILENT MASTER operating mode the DNP DPA always has Unsolicited
Responses automatically enabled.
An obvious disadvantage of not having CONFIRMations for Unsolicited Responses is
that if an Unsolicited Response is not received by the master station, the DNP DPA will
not re-transmit events that were in that Unsolicited Response. The DNP DPA can be
configured to always dump its database as part of the Unsolicited Response. If an
Unsolicited Response is lost, the static state of the GE HARRIS device data is available
in the next Unsolicited Response.
Thus, even if events are lost, the master station will always know the actual static state of
the GE HARRIS device data when it correctly receives the next Unsolicited Response.

The SILENT MASTER operating mode is designed for distributed automation
environments where quick reporting of events is not needed. The DNP DPA operates in
such a way that it is not necessary for the DNP master station to ever poll for data. Except
for the occasional control request (binary output, analog output, time synchronization,
etc.) the master station is silent.
3.1 SILENT MASTER MODE WITH AUTO DATA DUMP
When the DNP DPA configuration parameter called SILENT MASTER is set to
ENABLED, Unsolicited Responses are automatically enabled for all Class 1, 2 and 3
Data and the DNP DPA will not expect CONFIRMation Responses from the DNP master
station for anything it sends to it.
When the configuration parameter AUTO DATA DUMP is also ENABLED, the DNP
DPA will additionally perform the following actions:
! Upon RTU startup and when the RTU database is initialized, it will automatically
transmit data objects to the DNP Master as part of an Unsolicited Response. These
objects will initialize the DNP master station's database. Typically, objects such as the
Single-Bit Binary Input (if the point flag equals 1) or Binary Input with Status (if the
point flag does not equal 1) and 16-Bit Analog Input Without Flag (if the point flag
equals 1) or 16-Bit Analog Input (if the point flag does not equal 1) objects are
transmitted. The DPA may be configured to not report static objects which are
simultaneously in the off-line and remote forced state.
! When Binary Input event objects (e.g. Binary Input Change without Time objects) are
sent in an Unsolicited Response to the DNP master station, a Single-Bit Binary Input
or Binary Input with Status object is included in the Unsolicited Response for each
binary input point mapped to the DNP DPA.
! When Analog Input event objects (e.g. 16-Bit Analog Change Event without Time
objects) are sent in an Unsolicited Response to the DNP master station, a 16-Bit
Analog Input, 16-Bit Analog Input Without Flag, 32-Bit Analog Input or 32-Bit
Analog Input Without Flag object is included in the Unsolicited Response for each
analog input point mapped to the DNP DPA.
! When Counter Input event objects (e.g. 16-Bit Counter Change Event Without Time
objects) are sent in an Unsolicited Response to the DNP master station, a 16-Bit
Binary Counter, 16-Bit Binary Counter Without Flag, 32-Bit Binary Counter or 16-
Bit Binary Counter Without Flag object is included in the Unsolicited Response for
each counter input point mapped to the DNP DPA.

! When Frozen Counter Input event objects (e.g. 16-Bit Frozen Counter Change Event
Without Time objects) are sent in an Unsolicited Response to the DNP master station,
a 16-Bit Frozen Counter, 16-Bit Frozen Counter Without Flag, 32-Bit Frozen
Counter or 32-Bit Frozen Counter Without Flag object is included in the Unsolicited
Response for each frozen counter input points mapped to the DNP DPA.

Chapter 4:
GENERAL FUNCTIONALITY TOPICS
4.1 ANALOG INPUT DEADBANDS
Analog inputs are processed at a configured frequency to detect variations in their values.
When the variations for a given point exceed its configured deadband the DPA generates
an event.
The DNP DPA implements two analog deadband schemes for generating analog events.
The user configures the type of deadband scheme used.
Using the absolute change deadband scheme, the DPA scans the current values of the
analog inputs in the WESDAC database at the configured interval. If the difference
between the current value of an analog input and the last value reported to the master
exceeds the configured deadband, the DPA generates an event (16-Bit Analog Change
Event Without Time or 32-Bit Analog Change Event Without Time object).
Using the absolute integrating deadband scheme, the DPA scans the current values of
the analog inputs in the WESDAC database at the configured interval. The difference
between the current value of an analog input and the last value reported to the master is
added to the current delta_value for the input. If the delta_value exceeds the configured
deadband, the DPA generates an event. Figure 4-1 illustrates the absolute integrating
deadband scheme.
In Figure 4-1, the DPA is configured to check its analogs every second. The analog is
reported to the master at time t = 0. Given that the deadband for the analog input is 40
counts, it will exceed the deadband at time t = 5 seconds. At this point, an Analog Input
Event object is generated.

0 1 2 3 4 5 TIME (s)
50
40
ANALOG
VALUE 30
20
10
40
INTEGRATED 30
DELTA 20
10
0
Figure 4-1 Example of Absolute Integrating Analog Deadband
L NOTE: Configuring the analog scan frequency to zero means the DPA
performs its analog deadband algorithm on an analog input point when
it receives notification of a change in value from WIN. However, in
this case the absolute integrating deadband does not perform an
integration over time.
Configuring the analog scan frequency to -1 disables the DPA from
generating analog events.

4.2 DIGITAL INPUT EVENTS
The DNP DPA transmits either Binary Input with Time or Binary Input with Relative
Time objects when RTU digital input points change state and binary input change with
time events are enabled for the points. When the DPA receives a binary input event from
the WIN, it buffers the event. If unsolicited responses are enabled, the DPA starts a timer
after receiving its first event. Often binary input events continue to arrive from the WIN.
When either a specific number of events (configured) have arrived or the timer reaches a
specific value (configured), all buffered events (including binary input events) are
formatted into objects for transmitting to the master.
A configuration parameter specifies whether binary input events are stored in RAM or
NVRAM (Non-Volatile RAM). When stored in NVRAM, these objects are preserved in
the case of a power failure. They are reported to the DNP master station after system
restart.
Binary input change with time events are transmitted in different formats depending on
different conditions.
1. RTU Time Synchronized, one event object to send. The object is transmitted as a
Binary Input with Time object.
2. RTU Time Synchronized, several event objects to send. The Time and Date
Common Time of Occurrence object is transmitted followed by several Binary Input
with Relative Time objects. The time in the Time and Date Common Time of
Occurrence object is the time of the oldest object. The relative times start at 0 (for the
oldest object) and range upwards relative to the Date and Time object.
3. RTU Time NOT Synchronized, one or more event objects to send. The
Unsynchronized Common Time and Date object is transmitted followed by one or
more Binary Input with Relative Time objects. The time in the Time and Date
Common Time of Occurrence object is the time of the oldest object. The relative
times start at 0 (for the oldest object) and range upwards relative to the Time and Date
object.
Binary Input event objects are transmitted at the following times:
! In response to a poll for the specific Binary Input Change objects.
! In response to a Class data poll for the class that the binary input events are
configured for.
! In Unsolicited Responses, if enabled for the appropriate Class of data.

4.3 MODES OF OPERATION (CCU BASE ONLY)
On the CCU Base System, the DNP DPA supports multiple modes of operation:
ACTIVE, SERVICE, STANDBY, and DISABLE. Normally, it operates in ACTIVE
mode. In ACTIVE mode the DPA supports all the functionality described in this
document.
4.3.1 SERVICE Mode

The DNP DPA can be put in SERVICE mode when it is spawned and at any time when it
is in ACTIVE mode. Once in SERVICE mode it stays there. The GE HARRIS device
must be reset to remove the DPA from SERVICE mode. When in SERVICE mode the
DPA does the following:
! Generates a Service Mode Internal Indication (if configured) on transition from
ACTIVE to SERVICE mode or if the DNP DPA is in SERVICE mode when it is
spawned (refer to Section 1.16 Internal Indications).
! Processes WRITE requests to reset the RTU Restart Internal Indication bit.
! Processes WRITE requests of File Identifier Objects containing database download
data.
! Processes COLD RESTART requests.
! Processes STOP_APPLICATION requests.
! Responds to all other requests with the response header (containing the IIN bits) only.
4.3.2 DNP DPA in STANDBY and DISABLE Mode

When the RTU is in STANDBY or DISABLE mode, the operating system does not
spawn the DNP DPA.

4.4 BINARY OUTPUT ENABLE (CCU BASE SYSTEM ONLY)
Before a DNP DPA can process SELECT or OPERATE requests containing Control
Relay Output Block objects, the master station must ENABLE the DPA to process these
requests. This ENABLE request is implemented in the DNP DPA using a special
DIRECT OPERATE request to a particular pseudo binary output point.
There may be several binary output groups in a GE HARRIS device - only one
application may be ENABLED to operate binary outputs within a single group at any one
time. All the binary output points mapped to a single DNP DPA must be in the same
binary output group (as configured in the WIN configuration).
The point number of the pseudo binary output point is 0x7FFFFFFF (hexadecimal). The
data in the Control Relay Output Block object is not processed by the DNP DPA. The
DPA responds by echoing the request with the status field in the Control Relay Output
Block object equal to 0 if the ENABLE request is successful. If the request fails, the DPA
sets the status field equal to 7. This is a custom status not defined in the DNP V3.00
protocol definition.
Whenever a SELECT, OPERATE, DIRECT OPERATE or DIRECT OPERATE - NO
ACK request is processed by the DPA, it checks parameters in the WIN database to
ensure its binary outputs are enabled. If enabled, the DPA processes the request. If not
enabled, the DPA responds by echoing the request with the status field in the Control
Relay Output Block object equal to 7.
Another software application resident in the GE HARRIS device may ENABLE a group
of binary outputs at any time. This will automatically disable binary outputs for all other
software applications using this same group. Only one application in the GE HARRIS
device may have binary output requests enabled in a single group at any time.
L NOTE: The DNP DPA binary output points may be configured in the WIN to
be in group 0. If this is the case, binary output requests are always
enabled.
When the DPA is not running on the CCU Base System, the DPA
binary output points are by default in group 0.

4.5 DYNAMIC CONFIGURATION CHANGES
The DNP DPA can alter some of its parameters dynamically while the GE HARRIS
device is running. The following parameters can be altered:
! Change the Class of an event object (refer to Section 2.1.16 Assign Classes Function
Code).
! Enable or disable Unsolicited Responses on a Class by Class basis (refer to Section
2.1.15 Enable/Disable Spontaneous Message Function Codes).
These parameters are not altered in the NVRAM configuration of the GE HARRIS device
(or in the redundant GE HARRIS device if it exists). If the GE HARRIS device restarts,
the parameters initialize to the defaults specified in the NVRAM configuration.

4.6 COMMUNICATIONS FAIL OUTPUT
The DNP DPA supports configuring a binary output point which is LATCHED ON when
the DPA detects a communications failure, and LATCHED OFF once communication is
restored.
The output point is LATCHED OFF on startup by the DPA. A communications failure is
detected under the following conditions:
! The DPA fails to transmit a response (either solicited or unsolicited). The underlying
data link could not deliver the response to the requested destination. Both the data
link and the DPA have exhausted all configured retries.
! The DPA fails to receive a requested application confirm to either a solicited or
unsolicited response within the configured timeout interval. It has exhausted all
configured retries.
! The DPA has not received any message from the master station within a configurable
period of time.
Communication is considered to be restored after the DPA receives a message, or after
the DPA successfully transmits an unsolicited response.
L NOTE: The DNP DPA always attempts to transmit a solicited or unsolicited

response on the BridgeMAN channel it last received a message on.
The DPA does not initiate failover. Therefore, although the DPA
detects a communications failure it may still be possible for the master
station to communicate with the DPA over an alternate data link
channel configured in BridgeMAN. In this case, the control output
only indicates that a communications failure has occurred. It does not
indicate on which channel the failure occurred.

4.7 LOCAL/REMOTE INPUT
The DNP DPA allows the user to configure a Local/Remote Input feature. When the DNP
DPA is operating in Local mode, all output operations requested by the DNP master
station will not be performed. The DNP DPA will set its Internal Indication (IIN) local bit
to one (1) and respond to the DNP master indicating failure of the output request. The
Local/Remote Input feature can be enabled or disabled through configuration using the
following user defined parameters:
! Local/Remote Status Input
! Local Mode State
The combination of these two parameter defines the mode (Local or Remote) the DNP
DPA is currently operating. Outputs are not allowed when the DNP DPA is operating in
the local mode. Outputs are allowed when the DNP DPA is operating in the remote
mode. The Local/Remote Input feature can be disabled through configuration. When the
Local/Remote Input feature is disabled, the DNP DPA is always assumed to be operating
in the remote mode.
While DPA is operating in local mode, the DNP DPA will perform the DNP master
requests as follow:
! Any select requests received will be responded with the IIN local indication bit set
and the status field of the output object set to indicate hardware problem.
! Any operate or direct operate requests received will not operate any outputs, the DNP
DPA will respond to the DNP master with the IIN local indication bit set and the
status field of the output object set to indicate hardware problem.
! The on-line bits of all binary output status or analog output status read will be cleared
to zero (0) to indicate off-line condition.
! All other requests (not listed) will be performed normally as described in Chapter 2
Protocol Implementation.
If outputs are not inhibited, all output requests received by the DNP DPA will be
performed normally as described in Section 2.1.6 Select and Operate Function Codes and
Section 2.1.7 Direct Operate and Direct Operate - No ACK Function Codes.

4.8 UNSOLICITED RESPONSE EVENT REPORTING
The DNP DPA allows the user to choose a scheme for reporting events as they occur.
One manner in which events are reported by the DNP DPA is through the use of
unsolicited responses. When the unsolicited responses are initiated will be determined by
the following user defined parameters:
! maximum hold time
! maximum hold count
! idle report period
The maximum hold time defines the maximum period the DNP DPA will be allowed to
hold its events (since the first event) before reporting them to the DNP master station.
Whenever the maximum hold time has elapsed since the first event occurred, the DNP
DPA will report to the DNP master station all events accumulated up to then. This
parameter is defined in terms of milliseconds.
The maximum hold count defines the maximum number of events (since the first event)
the DNP DPA will be allowed to hold before reporting them to the DNP master station.
Whenever the maximum hold count threshold is reached, the DNP DPA will report to the
DNP master station, all events accumulated up to that point.
The idle report period is a performance enhancement parameter. It is used to provide
efficient reporting of events to the DNP master station. When events occur, the DNP
DPA determines a time gap between any two events. If the time gap between two events
exceeds the configured idle report period, the DNP DPA will initiate an unsolicited
response to the DNP master station containing all events accumulated prior to expiration
of the idle report period. The idle report period is defined in terms of milliseconds, and it
is typically much shorter than the maximum hold time period.
If unsolicited response is enabled, the DNP DPA will initiate an unsolicited response to
report events whenever any of the following three conditions is satisfied. The priority of
these conditions are exactly equal. Figure 4-2 illustrates when events are reported for all
three cases.
! When the idle report period has expired.
! When the maximum hold time is reached.
! When the maximum hold count threshold is reached.

idle report idle report
period period
idle report
period
idle report idle report idle report
period period period
idle report
period maximum hold time expired at t4
Max hold count reached at t5
8th to nth events
1st 2nd 3rd 4th 5th 6th 7th

event event event event event event event
TIME
t0 t1 t2 t3 t4 t5
1st report at t2 2nd report at t4 3rd report at t5
Figure 4-2 Unsolicited Response Event Reporting

4.9 ANALOG INPUT SCALING
The DNP DPA provides the flexibility for the users to scale analog input values before
reporting them to the DNP master station. The DNP DPA supports either 16-bit or 32-bit
analog values. The WESDAC system analog inputs are formatted as 16-bit twos
complement values. Therefore, WESDAC analogs will be scaled to either 16-bit or 32-bit
DNP protocol values according to the following configurable scaling factors:
! Analog Scaling Range
! Analog Scaling Divisor
! Analog Value Offset
Analog scaling is configurable on a per-point basis. The Analog Scaling Range defines
the maximum DNP protocol value that will be reported when the WESDAC analog input
reaches its full-scale value. The Analog Scaling Divisor defines the WESDAC analog
input full scale value. The analog scaling factor is determined by the combination of the
Analog Scaling Range and the Analog Scaling Divisor. The Analog Value Offset is a
compensation factor which can be added to the resultant scaled value. This value is
typically zero. The DNP protocol value that the DPA will report is determined by the
following equation:
Range x WESDAC Value

DNP Protocol Value = + Offset
Divisor
L NOTE: Resolution does not improve when scaling a 16-bit WESDAC analog
input value to a 32-bit DNP protocol value. The resolution of analog
input values is dictated by the WESDAC input value.
When the resulting scaled value exceeds the value range defined by the analog input size
or the DNP master request, the DPA will set the over-range flag bit of the analog input
object and set the value to either positive or negative maximum, as appropriate.

4.10 ANALOG OUTPUT SCALING
The DNP DPA provides the flexibility for the users to scale analog output values received
from the DNP master station. The DNP DPA supports both 16-bit or 32-bit analog
values. The WESDAC system analog output values are formatted as 16-bit twos
complement values. Therefore, WESDAC analog output values will be scaled from either
16-bit or 32-bit DNP protocol values according to the following configurable scaling
factors:
! Analog Scaling Range
! Analog Scaling Divisor
! Analog Value Offset
Analog output scaling is configurable on a per-point basis. The Analog Scaling Range
defines the maximum WESDAC analog output value that will be performed with when
the DNP protocol value reaches its full-scale value. The Analog Scaling Divisor defines
the DNP protocol analog output full scale value. The analog scaling factor is determined
by the combination of the Analog Scaling Range and the Analog Scaling Divisor. The
Analog Value Offset is a compensation factor which can be added to the resultant scaled
analog output value. This value is typically zero. The WESDAC analog output value is
determined by the following equation.
Range x DNP Protocol Value

WESDAC Value = + Offset
Divisor
L NOTE: Analog output resolution will be lost when scaling a 32-bit DNP
protocol value to a 16-bit WESDAC analog output value.
If the resulting scaled value exceeds the limit of the maximum WESDAC analog output
values, the DNP DPA will reject the output request and set the status field of the output
object to indicate hardware problem.

4.11 TIME TAGGED ANALOG INPUT EVENTS
The DNP DPA provides the flexibility for the users to report time tagged or non-time
tagged analog input events on a per point basis. When time tag is enabled for the analog
input point, the DNP DPA will report both the analog input value and the associated time
tag to the DNP master station. The particular value and time reported will be dependent
on whether the DNP DPA is configured to report analogs with the Current Value and
Time or the First Event Value and Time. When time tag is disabled for the analog input
point, the DNP DPA will report only the analog input value (without time tag) to the
DNP master station. Also, the particular value reported will be dependent on whether the
DNP DPA is configured to report analogs with the Current Value and Time or the First
Event Value and Time. Table 4-1 tabulates the various methods for reporting analog
events.
Time
Analog Reporting Method Description of Analog Events Reported
Tag
Current Value and Time The current analog value and time for those analogs exceeding the
Enable deadband will be returned to the master station at the time of
reporting.
The current analog value (without time) for those analogs exceeding
Disable the deadband will be returned to the master station at the time of
reporting.
First Event Value and Time The analog value and time associated with the first event for those
Enable
analogs exceeding the deadband will be reported.
The analog value (without time) associated with the first event for
Disable
those analogs exceeding the deadband will be reported.
Table 4-1 Analog Input Event Reporting
L NOTE: When unsolicited reporting is used for analog input events, the
behavior of the two different analog reporting methods will be very
similar because the unsolicited reports are generated very soon after
the event occurred, hence the first event time and current time may be
very close to the same.

Appendix A:
DNP DPA WIN USAGE
This section describes the WIN events and commands that the DNP DPA processes and
sends. Refer to Tables A-1 and A-2 for WIN supported Events and Commands.
Table A-1 Supported WIN Events
SINGLE_PNT
TIME_ Affected WIN
WIN Event Type or Usage
TAGGED Data Type(s)
MULTI_PNT
DATA_UPDATE Both single and Don't Care BINARY_INPUT Sent to DPA after DCA has
multi pnt BINARY_OUTPUT initialized the database. The
COUNTER DPA will not attach to
ANALOG_INPUT BridgeMAN until
ANALOG_OUTPUT DATA_UPDATE events
are received for all DNP
points.
OFF_LINE Both single and Don't Care BINARY_INPUT Sent for all types on power
multi pnt BINARY_OUTPUT up or when the device goes
COUNTER offline. Sent for specific
ANALOG_INPUT data points when they
ANALOG_OUTPUT cannot be successfully
DEVICE_STATUS scanned or controlled. If
configured, they generate
offline events.
ON_LINE Both single and Don't Care BINARY_INPUT Sent for all types when the
multi pnt BINARY_OUTPUT device goes online. Sent for
COUNTER specific data points when
ANALOG_INPUT an offline point can be
ANALOG_OUTPUT successfully scanned or
DEVICE_STATUS controlled. If configured,
they generate online events.

B021-0FS.WES, Version 7.00 A-1
SINGLE_PNT
TIME_ Affected WIN
WIN Event Type or Usage
TAGGED Data Type(s)
MULTI_PNT
DATA_CHANGE Single pnt Yes BINARY_INPUT Sent by a DCA when data

changes. Causes SOE.
No BINARY_INPUT Sent by a DCA when data

COUNTER changes. Binary Input
causes COS. Counter may
cause events.
FREEZE_DATA_CMD Multi pnt Don't Care COUNTER Sent to the DPA when
counters are frozen.
Prompts DPA to process
for frozen counter events.
CLEAR_DATA_CMD Multi pnt Don't Care COUNTER Sent to the DPA when
counters are cleared. May
cause Unsolicited reporting
of counters.
ADJUST_TIME Neither Yes SYSTEM_DATA Notifies DPA that system

(CCU Base only) clock has been adjusted.
SERVICE_MODE Neither No SYSTEM_STATUS Notifies DPA that DPA is

(CCU Base only) now in SERVICE mode.
DOWNLOAD_ Neither No SYSTEM_DATA Notifies DPA when a

COMPLETE download request is
(CCU Base only) complete.
FORCE_DATA Single pnt Don't Care BINARY_INPUT Remote Force Data and
BINARY_OUTPUT Off-Line can disable
COUNTER reporting if configured;
ANALOG_INPUT Otherwise, just updates flag
ANALOG_OUTPUT bits.
UNFORCE_DATA Single pnt Don't Care BINARY_INPUT Remote Unforce Data can
BINARY_OUTPUT enable reporting if
COUNTER configured; Otherwise, just
ANALOG_INPUT updates flag bits.
ANALOG_OUTPUT

A-2 B021-0FS.WES, Version 7.00
Table A-2 Commands Sent To WIN
WIN Command Type WIN Data Type Options Usage
REPORT_ENABLE BINARY_INPUT Sets up the functions for

BINARY_OUTPUT processing system events from
COUNTER the WIN.
ANALOG_INPUT
ANALOG_OUTPUT
REPORT_ENABLE SYSTEM_STATUS Sets up the functions for

(CCU Base only) SYSTEM_DATA processing system events from
the WIN.
FREEZE_CALL COUNTER_INPUT Sets up a function for

processing system events from
WIN. The events processed are
FREEZE and CLEAR events.
DPA_READY Signals to the WIN that the

DPA is ready to run.
OUTPUT_REQUEST BINARY_OUTPUT Supports linked lists, For operating one or more

T/C, pulse, latched, digital output points (when the
RE_QUEUE, points are in group 0).
RESET_QUEUE,
repeat counts.
ANALOG_OUTPUT Supports linked lists. For operating one or more

analog output points.
FREEZE_DATA COUNTER_INPUT Sent by the DPA when

counters need to be frozen.
CLEAR_DATA COUNTER_INPUT Sent by the DPA when

counters need to be cleared.
PUT_CONFIG DEVICE_STATUS Used to transfer a

configuration to a DCA.
GET_CONFIG DEVICE_STATUS Used to get a configuration

from a DCA.
SERVICE_MODE_ SYSTEM_STATUS Make OS put RTU or

REQUEST redundant RTU into SERVICE
(CCU Base only) mode.
DOWNLOAD_ SYSTEM_DATA To pass database blocks to OS.

REQUEST
(CCU Base only)
SYSTEM_RESET_ SYSTEM_STATUS Make OS reset the RTU or the

REQUEST redundant RTU.
(CCU Base only)
DBASE_SYNC_ SYSTEM_DATA Make OS send config. to

REQUEST redundant RTU.
(CCU Base only)

B021-0FS.WES, Version 7.00 A-3
WIN Command Type WIN Data Type Options Usage
GET_GROUP_ BINARY_OUTPUT Gets binary output group

OWNERSHIP ownership for the DPA.
(CCU Base only)
FORCE_DATA BINARY_INPUT Force a binary input to disable

(CCU Base only) event generation.
UNFORCE BINARY_INPUT Unforce a binary input.

(CCU Base only)
OUTPUT_GROUP BINARY_OUTPUT Supports linked lists, For operating one or more

(CCU Base only) T/C, pulse, latched, binary output points (when the
RE_QUEUE, points are not in group 0).
RESET_QUEUE,
repeat counts.
GET_GROUP_ BINARY_OUTPUT Identifies which application

OWNERSHIP_ID presently has ownership of a
(CCU Base only) specified binary output group.
CCU_STATUS SYSTEM_STATUS Identifies the operating mode

(CCU Base only) of the RTU (e.g. ACTIVE or
SERVICE).
The DNP DPA also uses the win_read function call to read positive and negative
acknowledgements (ACKs and NACKs) from the WIN. These are returned to the DPA in
response to OUTPUT_REQUEST, PUT_CONFIG and GET_CONFIG WIN commands.
Note that the DNP DPA has a configurable parameter which specifies whether event data
handling should be optimized for processing speed or memory usage. This parameter
applies to all data change events, including binary input, analog input, and counter input
change events.

A-4 B021-0FS.WES, Version 7.00
Appendix B:
DNP DPA IMPLEMENTATION MATRIX
This appendix details the HARRIS DNP DPA implementation of the DNP V3.00
protocol. The tables in this appendix precisely describe the interaction of the function
codes, objects and qualifier codes used by the DPA.
Table B-1 Function Codes Supported by the DNP DPA
Function Code Command Supported by the DPA ?
0 CONFIRM YES
1 READ YES
2 WRITE YES
3 SELECT YES
4 OPERATE YES
5 DIRECT OPERATE YES
6 DIRECT OPERATE - No ACK YES
7 IMMEDIATE FREEZE YES
8 IMMEDIATE FREEZE - No ACK YES
9 FREEZE AND CLEAR YES
10 FREEZE AND CLEAR - No ACK YES
11 FREEZE WITH TIME NO
12 FREEZE WITH TIME - No ACK NO
13 COLD RESTART YES

B021-0FS.WES, Version 7.00 B-1
Function Code Command Supported by the DPA ?
14 WARM RESTART YES
15 INITIALIZE DATA NO
16 INITIALIZE APPLICATION NO
17 START APPLICATION YES

(CCU Base only)
18 STOP APPLICATION YES

(CCU Base only)
19 SAVE CONFIGURATION YES

(CCU Base only)
20 ENABLE SPONTANEOUS MESSAGES YES

(Class 1, 2, 3)
21 DISABLE SPONTANEOUS MESSAGES YES

(Class 1, 2, 3)
22 ASSIGN CLASSES YES
23 DELAY MEASUREMENT YES
129 RESPONSE YES
130 UNSOLICITED RESPONSE YES
L NOTE: Just because a Function Code is supported does not mean that all
possible objects are accessible using that Function Code. Table B-1
Function Codes Supported by the DNP DPA must be read in
combination with all other tables in this appendix in order to
understand the implementation.

B-2 B021-0FS.WES, Version 7.00
Table B-2 Objects and Variations Supported by the DNP DPA
Obj Var Description Supported by the DPA ?
1 1 SINGLE-BIT BINARY INPUT YES
1 2 BINARY INPUT WITH STATUS YES
2 1 BINARY INPUT CHANGE WITHOUT TIME YES
2 2 BINARY INPUT CHANGE WITH TIME YES
2 3 BINARY INPUT CHANGE WITH RELATIVE TIME YES
10 1 BINARY OUTPUT NO
10 2 BINARY OUTPUT STATUS YES
12 1 CONTROL RELAY OUTPUT BLOCK YES
12 2 PATTERN CONTROL BLOCK YES
12 3 PATTERN MASK YES
20 1 32-BIT BINARY COUNTER YES
20 2 16-BIT BINARY COUNTER YES
20 3 32-BIT DELTA COUNTER YES
20 4 16-BIT DELTA COUNTER YES
20 5 32-BIT BINARY COUNTER WITHOUT FLAG YES
20 6 16-BIT BINARY COUNTER WITHOUT FLAG YES
20 7 32-BIT DELTA COUNTER WITHOUT FLAG YES
20 8 16-BIT DELTA COUNTER WITHOUT FLAG YES
21 1 32-BIT FROZEN COUNTER YES
21 2 16-BIT FROZEN COUNTER YES
21 3 32-BIT FROZEN DELTA COUNTER NO
21 4 16-BIT FROZEN DELTA COUNTER NO
21 5 32-BIT FROZEN COUNTER WITH TIME OF FREEZE NO
21 6 16-BIT FROZEN COUNTER WITH TIME OF FREEZE NO
21 7 32-BIT FROZEN DELTA COUNTER WITH TIME OF NO
FREEZE
21 8 16-BIT FROZEN DELTA COUNTER WITH TIME OF NO
FREEZE
21 9 32-BIT FROZEN COUNTER WITHOUT FLAG YES
21 10 16-BIT FROZEN COUNTER WITHOUT FLAG YES
21 11 32-BIT FROZEN DELTA COUNTER WITHOUT FLAG YES
21 12 16-BIT FROZEN DELTA COUNTER WITHOUT FLAG YES
22 1 32-BIT COUNTER CHANGE EVENT WITHOUT TIME YES

22 2 16-BIT COUNTER CHANGE EVENT WITHOUT TIME YES
22 3 32-BIT DELTA COUNTER CHANGE EVENT YES
WITHOUT TIME
22 4 16-BIT DELTA COUNTER CHANGE EVENT YES
WITHOUT TIME
22 5 32-BIT COUNTER CHANGE EVENT WITH TIME NO
22 6 16-BIT COUNTER CHANGE EVENT WITH TIME NO
22 7 32-BIT DELTA COUNTER CHANGE EVENT WITH NO
TIME
22 8 16-BIT DELTA COUNTER CHANGE EVENT WITH NO
TIME
23 1 32-BIT FROZEN COUNTER EVENT WITHOUT TIME NO
23 2 16-BIT FROZEN COUNTER EVENT WITHOUT TIME NO
23 3 32-BIT FROZEN DELTA COUNTER EVENT WITHOUT NO
TIME
23 4 16-BIT FROZEN DELTA COUNTER EVENT WITHOUT NO
TIME
23 5 32-BIT FROZEN COUNTER EVENT WITH TIME NO
23 6 16-BIT FROZEN COUNTER EVENT WITH TIME NO
23 7 32-BIT FROZEN DELTA COUNTER EVENT WITH NO
TIME
23 8 16-BIT FROZEN DELTA COUNTER EVENT WITH NO
TIME
30 1 32-BIT ANALOG INPUT YES
30 2 16-BIT ANALOG INPUT YES
30 3 32-BIT ANALOG INPUT WITHOUT FLAG YES, if on-line
30 4 16-BIT ANALOG INPUT WITHOUT FLAG YES, if on-line
31 1 32-BIT FROZEN ANALOG INPUT NO
31 2 16-BIT FROZEN ANALOG INPUT NO
31 3 32-BIT FROZEN ANALOG INPUT WITH TIME OF NO
FREEZE
31 4 16-BIT FROZEN ANALOG INPUT WITH TIME OF NO
FREEZE
31 5 32-BIT FROZEN ANALOG INPUT WITHOUT FLAG NO
31 6 16-BIT FROZEN ANALOG INPUT WITHOUT FLAG NO
32 1 32-BIT ANALOG CHANGE EVENT WITHOUT TIME YES
32 2 16-BIT ANALOG CHANGE EVENT WITHOUT TIME YES
32 3 32-BIT ANALOG CHANGE EVENT WITH TIME YES

32 4 16-BIT ANALOG CHANGE EVENT WITH TIME YES
33 1 32-BIT FROZEN ANALOG EVENT WITHOUT TIME NO
33 2 16-BIT FROZEN ANALOG EVENT WITHOUT TIME NO
33 3 32-BIT FROZEN ANALOG EVENT WITH TIME NO
33 4 16-BIT FROZEN ANALOG EVENT WITH TIME NO
40 1 32-BIT ANALOG OUTPUT STATUS YES
40 2 16-BIT ANALOG OUTPUT STATUS YES
41 1 32-BIT ANALOG OUTPUT BLOCK YES
41 2 16-BIT ANALOG OUTPUT BLOCK YES
50 1 TIME AND DATE YES
50 2 TIME AND DATE WITH INTERVAL NO
51 1 TIME AND DATE CTO YES
51 2 UN-SYNCHRONIZED TIME AND DATE CTO YES
52 1 TIME DELAY COARSE YES
52 2 TIME DELAY FINE YES
60 1 CLASS 0 DATA YES
70 1 FILE IDENTIFIER Partial
80 1 INTERNAL INDICATIONS YES
81 1 STORAGE OBJECT Partial
82 1 DEVICE PROFILE NO
83 1 PRIVATE REGISTRATION OBJECT NO
83 2 PRIVATE REGISTRATION OBJECT DESCRIPTOR NO
90 1 APPLICATION IDENTIFIER NO
100 1 SHORT FLOATING POINT NO
100 2 LONG FLOATING POINT NO
100 3 EXTENDED FLOATING POINT NO
101 1 SMALL-PACKED BINARY CODED DECIMAL NO
101 2 MEDIUM-PACKED BINARY CODED DECIMAL NO
101 3 LARGE-PACKED BINARY CODED DECIMAL NO

L NOTE: Just because an object is supported does not means that it is accessible
using all Function Codes. Table B-2 Objects and Variations
Supported by the DNP DPA must be read in combination with all
other tables in this appendix in order to understand the
implementation.
Table B-3 explains which objects/variations are used with which Function Codes and
Qualifier Codes by the HARRIS DNP DPA implementations.
To understand the tables, consider the second row of Table B-3. This row specifies how
object 1, variation 2 (Binary Input With Status) is accessed. To access this type of object,
the DPA will process a request using Function Code 1 (READ) with a Qualifier Code in
the range of 00 to 09 inclusive. The DPA will respond with Function Code 129
(RESPONSE), Qualifier Code 01. The DPA will also produce responses using Function
Code 130 (UNSOLICITED RESPONSE), Qualifier Code 01.
Table B-3 Objects/Variations/Qualifiers/Function Codes supported by the DPA

Request Response
Request Response
Qualifier Qualifier
Obj. Var. Description Function Function
Codes Codes
Code Code
(Hexadecimal) (Hexadecimal)
1 1 SINGLE-BIT BINARY 1 00 - 09 129 01
INPUT
1 2 BINARY INPUT WITH 1 00 - 09 129 01
STATUS
130 01
(Report when
points go
online, offline &
when event
buffers
overflow)
1 2 BINARY INPUT WITH 2 00 - 02, 129 Not Used
STATUS 07 - 09
2 1 BINARY INPUT CHANGE 1 06 - 09 129, 130 28
WITHOUT TIME
WITH TIME
WITH RELATIVE TIME

Request Response
Request Response
Qualifier Qualifier
Codes Codes
Code Code
10 1 BINARY OUTPUT 1 00 - 09 129 01
10 2 BINARY OUTPUT STATUS 1 00 - 09 129 01
130 01
(Reported when
points go online
and offline)
12 1 CONTROL RELAY OUTPUT 3, 4, 5, 6 x7 - x9 where 129 Echo of request
BLOCK 1 <= x <= 3 qualifier codes
12 2 PATTERN CONTROL 5, 6 06 or 07 - 09 129 Echo of request
BLOCK where quantity qualifier codes
=1
12 3 PATTERN MASK 5, 6 00 - 02 129 Echo of request
qualifier codes
20 1 32-BIT BINARY COUNTER 1, 7, 8, 9, 00 - 09 129 01
10
10
130 01
(Reported when
points go online
and offline)
20 3 32-BIT DELTA COUNTER 1 00 - 09 129 01
130 01
(Reported when
points go online
and offline)
WITHOUT FLAG 10
WITHOUT FLAG 10
130 01
(Reported when
points go online
and offline)
WITHOUT FLAG
WITHOUT FLAG
130 01
(Reported when
points go online
and offline)

Request Response
Request Response
Qualifier Qualifier
Codes Codes
Code Code
21 1 32-BIT FROZEN COUNTER 1, 7, 8, 9, 00 - 09 129 01
10
10
130 01
(Reported when
points go online
and offline)
21 3 32-BIT FROZEN DELTA 1 00 - 09 Not Used Not Used
COUNTER
COUNTER
21 5 32-BIT FROZEN COUNTER Not Used Not Used Not Used Not Used
WITH TIME OF FREEZE
WITH TIME OF FREEZE
21 7 32-BIT FROZEN DELTA Not Used Not Used Not Used Not Used
COUNTER WITH TIME OF
FREEZE
COUNTER WITH TIME OF
FREEZE
WITHOUT FLAG 10
WITHOUT FLAG 10
130 01
(Reported when
points go online
and offline)
COUNTER WITHOUT FLAG
COUNTER WITHOUT FLAG
22 1 32-BIT COUNTER CHANGE 1 06 - 09 129, 130 28
EVENT WITHOUT TIME
22 2 16-BIT COUNTER CHANGE 1 06 - 09 129, 130 28
EVENT WITHOUT TIME

Request Response
Request Response
Qualifier Qualifier
Codes Codes
Code Code
22 3 32-BIT DELTA COUNTER 1 06 - 09 129, 130 28
CHANGE EVENT WITHOUT
TIME
22 4 16-BIT DELTA COUNTER 1 06 - 09 129, 130 28
CHANGE EVENT WITHOUT
TIME
22 5 32-BIT COUNTER CHANGE Not Used Not Used Not Used Not Used
EVENT WITH TIME
22 6 16-BIT COUNTER CHANGE Not Used Not Used Not Used Not Used
EVENT WITH TIME
22 7 32-BIT DELTA COUNTER Not Used Not Used Not Used Not Used
CHANGE EVENT WITH
TIME
22 8 16-BIT DELTA COUNTER Not Used Not Used Not Used Not Used
CHANGE EVENT WITH
TIME
23 1 32-BIT FROZEN COUNTER 1 06 - 09 Not Used Not Used
EVENT WITHOUT TIME
23 2 16-BIT FROZEN COUNTER 1 06 - 09 Not Used Not Used
EVENT WITHOUT TIME
COUNTER EVENT
WITHOUT TIME
COUNTER EVENT
WITHOUT TIME
EVENT WITH TIME
EVENT WITH TIME
COUNTER EVENT WITH
TIME
COUNTER EVENT WITH
TIME

Request Response
Request Response
Qualifier Qualifier
Codes Codes
Code Code
30 1 32-BIT ANALOG INPUT 1 00 - 09 129 01
30 2 16-BIT ANALOG INPUT 1 00 - 09 129 01
130 01
(Reported when
points go online
and offline)
30 3 32-BIT ANALOG INPUT 1 00 - 09 129 01
WITHOUT FLAG
30 4 16-BIT ANALOG INPUT 1 00 - 09 129 01
WITHOUT FLAG
130 01
(Reported when
points go online
and offline)
31 1 32-BIT FROZEN ANALOG Not Used Not Used Not Used Not Used
INPUT
INPUT
INPUT WITH TIME OF
FREEZE
INPUT WITH TIME OF
FREEZE
INPUT WITHOUT FLAG
INPUT WITHOUT FLAG
32 1 32-BIT ANALOG CHANGE 1 06 - 09 129, 130 28
EVENT WITHOUT TIME
EVENT WITHOUT TIME
EVENT WITH TIME
EVENT WITH TIME
EVENT WITHOUT TIME
EVENT WITHOUT TIME

Request Response
Request Response
Qualifier Qualifier
Codes Codes
Code Code
EVENT WITH TIME
EVENT WITH TIME
40 1 32-BIT ANALOG OUTPUT 1 00 - 09 129 01
STATUS
40 2 16-BIT ANALOG OUTPUT 1 00 - 09 129 01
STATUS
130 01
(Reported when
points go online
and offline)
41 1 32-BIT ANALOG OUTPUT 3, 4, 5, 6 x7 - x9 where 129 Echo of request
41 2 16-BIT ANALOG OUTPUT 3, 4, 5, 6 x7 - x9 where 129 Echo of request
50 1 TIME AND DATE 1, 2 06 or 07 - 09 129 07,
where quantity Quantity = 1
=1
50 2 TIME AND DATE WITH Not Used Not Used Not Used Not Used
INTERVAL
51 1 TIME AND DATE CTO Not Used Not Used 129, 130 07,
Quantity = 1
51 2 UN-SYNCHRONIZED TIME Not Used Not Used 129, 130 07,
AND DATE CTO Quantity = 1
52 1 TIME DELAY COARSE Not Used Not Used 129 07,
Quantity = 1
52 2 TIME DELAY FINE Not Used Not Used 129 07,
Quantity = 1
60 1 CLASS 0 DATA 1 06 Not Used 1
60 2 CLASS 1 DATA 1 06 - 09 Not Used Not Used
20, 21, 22 06
20, 21, 22 06
20, 21, 22 06

Request Response
Request Response
Qualifier Qualifier
Codes Codes
Code Code
70 1 FILE IDENTIFIER 2 07 or 1B, 2B, 129 07 or 1B, 2B,
3B 3B
80 1 INTERNAL INDICATIONS 1 00 - 09 129, 130 00
2 00 - 02
81 1 STORAGE OBJECT 1 06 129 07,
Quantity = 2
82 1 DEVICE PROFILE Not Used Not Used Not Used Not Used
83 1 PRIVATE REGISTRATION Not Used Not Used Not Used Not Used
OBJECT
83 2 PRIVATE REGISTRATION Not Used Not Used Not Used Not Used
OBJECT DESCRIPTOR
90 1 APPLICATION IDENTIFIER Not Used Not Used Not Used Not Used
100 1 SHORT FLOATING POINT Not Used Not Used Not Used Not Used
100 2 LONG FLOATING POINT Not Used Not Used Not Used Not Used
100 3 EXTENDED FLOATING Not Used Not Used Not Used Not Used
POINT
101 1 SMALL-PACKED BINARY Not Used Not Used Not Used Not Used
CODED DECIMAL
101 2 MEDIUM-PACKED BINARY Not Used Not Used Not Used Not Used
CODED DECIMAL
101 3 LARGE-PACKED BINARY Not Used Not Used Not Used Not Used
CODED DECIMAL

Appendix C:
DEVICE PROFILE DOCUMENT
The following document is used in conjunction with Appendix B: DNP DPA

Implementation Matrix to summarize the HARRIS DNP DPA implementation of the
DNP V3.00 protocol.
Several items in the Device Profile Document require additional explanation. All
timeouts used by the DNP DPA are configurable. However, because the DPA only
implements the application layer of the DNP V3.00 protocol, most timing considerations
are handled by the underlying data link(s). For example, if the DPA is configured to
request the data link send-confirm service, the underlying data link is responsible for
detecting data link confirm timeouts. The timeout is a configurable parameter in the DNP
V3.00 Data Link.
There is no direct DNP DPA application fragment timeout. However, it is likely the data
link receiving and building an incoming message will not wait indefinitely for a message
to be received. The DNP V3.00 Data Link uses its configurable timeout not only for
receiving confirms, but also as the timeout between frames of a multi-frame message.
The DNP DPA has a configurable parameter specifying the turnaround time of the master
station. This time is intended to account for the worst-case time it takes the master station
to process a message from the DPA before sending an application confirm. When the
DPA requests an application layer confirmation, it passes this parameter to the underlying
data link and requests notification from the data link if a timeout occurs. It is the
responsibility of the data link to add any additional time to account for delays on the
physical link.
Each binary input point configured in the DNP DPA can also be monitored for binary
input change events. The user configures whether to monitor the point for time-tagged or
non-time-tagged binary events, or no events at all.

B021-0FS.WES, Version 7.00 C-1
Unsolicited responses in the DNP DPA are enabled and disabled on a per class basis
(class 1, class 2 and class 3). This can be done in the configuration or during run-time
with the enable/disable unsolicited message function codes.
If unsolicited responses are enabled for one or more classes, the following IIN exceptions
generate unsolicited responses: device restart, need time synchronization, and binary
event buffer overflow. In addition, a change in any custom extended IIN bit configured by
the user is considered an event reported in the next unsolicited response.
If the user configures the DNP DPA to operate in silent master mode, the DPA dumps all
of its data in an unsolicited response on start-up. In subsequent unsolicited responses
reporting event data, the DPA includes the corresponding static data. For example, if the
DPA has some binary input events to report, the unsolicited response contains both the
events as well as a complete dump of all binary inputs owned by the DPA.
Online/offline status changes can be assigned to class 1, 2 or 3, or detecting these changes
can be disabled altogether. Because there are no corresponding event objects in the DNP
V3.00 protocol, each change is reported using the appropriate static data object with the
flag indicating the online/offline status of the point. Because this feature contradicts the
rule that static objects must be in class 0 only, some masters may require this feature to be
disabled.
The DNP DPA may be configured to not report any static data objects which are
simultaneously in the off-line and remote forced state. The conditional reporting applies
to polled data as well as data returned as part of an Auto Data Dump.
The buffer storage objects are only returned when specifically requested, i.e. they are not
returned in response to a class 0 data poll.
The DNP DPA decides whether to report a static data object with or without flag.
Regardless of the variation specified (Class 0, variation 0, with flag, or without flag), if
the static data object is online (i.e. the point flag equals 1) the DNP DPA returns the
object variation corresponding to the one requested by the master which does not include
the flag. If the flag does not equal one, the DPA transmits the object using the
corresponding variation which includes the flag.

C-2 B021-0FS.WES, Version 7.00
The DNP DPA allows the user to configure absolute or delta counters. In addition, each
counter is configured as either a 16-bit or 32-bit counter. In this way, the user defines the
default counter object reported by the DPA. Whether to report a counter variation with or
without flag is not configurable (see explanation above). The following objects are
supported:
! 32-Bit Binary Counter (Object 20, Variation 1)
! 16-Bit Binary Counter (Object 20, Variation 2)
! 32-Bit Delta Counter (Object 20, Variation 3)
! 16-Bit Delta Counter (Object 20, Variation 4)
! 32-Bit Binary Counter without Flag (Object 20, Variation 5)
! 16-Bit Binary Counter without Flag (Object 20, Variation 6)
! 32-Bit Delta Counter without Flag (Object 20, Variation 7)
! 16-Bit Delta Counter without Flag (Object 20, Variation 8)
The DNP DPA never sets the rollover flag of a counter, it just reports its current state in
the internal database. The DCA which owns the counter may set the rollover flag at any
time.

DNP V3.00
DEVICE PROFILE DOCUMENT
This document must be accompanied by a table having the following headings:
Object Group Request Function Codes Response Function Codes
Object Variation Request Qualifiers Response Qualifiers
Object Name (optional)
Vendor Name: HARRIS Controls Distributed Automation Products
Device Name: D25, D20, D200 or CPM GE HARRIS device, using DNP V3.00 Data Link
Highest DNP Level Supported: Device Function:

For Requests Level 3 G Master O Slave
For Responses Level 3
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported
(the complete list is described in the attached table):
Forcing binary inputs with a WRITE request.
Optionally assigning online/offline events to class 1, 2 or 3 (reported as static objects).
Optionally preventing static objects, which are simultaneously in the off-line and
remote forced state, from being reported.
Optionally running in silent master mode in which static data is returned in unsolicited
responses.
Time tagged analog inputs optionally returned.
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted 292_________ Transmitted 100 - 64K (configurable)
Received (must be 292) Received 100 - 64K (must be > 249)
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
G None G None
G Fixed at ______________________ O Configurable, range __0_ to __32767___
O Configurable, range __0_ to _255__ (Fixed is not permitted)

Requires Data Link Layer Confirmation:
G Never
G Always
G Sometimes If 'Sometimes', when? ____________________________________________
O Configurable If 'Configurable', how? User enables/disables data link send-confirm service
Requires Application Layer Confirmation:
G Never
G Always (not recommended)
O When reporting Event Data (Slave devices only)
O When sending multi-fragment responses (Slave devices only)
O Sometimes If 'Sometimes', when? When reporting Static Data such as delta counters.
O Configurable If 'Configurable', how? Enabling silent master mode means the DPA never requests
a confirmation
Timeouts while waiting for:
Data Link Confirm G None G Fixed at _________ G Variable O Configurable

Complete Appl. Fragment O None G Fixed at _________ G Variable G Configurable
Application Confirm G None G Fixed at _________ G Variable O Configurable
Complete Appl. Response O None G Fixed at _________ G Variable G Configurable
Others __________________________________________________________________________
Attach explanation if 'Variable' or 'Configurable' was checked for any timeout
Sends/Executes Control Operations:
WRITE Binary Outputs G Never O Always G Sometimes G Configurable

SELECT/OPERATE G Never O Always G Sometimes G Configurable
DIRECT OPERATE G Never O Always G Sometimes G Configurable
DIRECT OPERATE - NO ACK G Never O Always G Sometimes G Configurable
Count > 1 G Never O Always G Sometimes G Configurable

Pulse On G Never O Always G Sometimes G Configurable
Pulse Off G Never O Always G Sometimes G Configurable
Latch On G Never O Always G Sometimes G Configurable
Latch Off G Never O Always G Sometimes G Configurable
Queue G Never O Always G Sometimes G Configurable

Clear Queue G Never O Always G Sometimes G Configurable
Attach explanation if 'Sometimes' or 'Configurable' was checked for any operation.

FILL OUT THE FOLLOWING ITEM FOR MASTER DEVICES ONLY:
Expects Binary Input Change Events:
G Either time-tagged or non-time-tagged for a single event

G Both time-tagged and non-time-tagged for a single event
G Configurable (attach explanation)
FILL OUT THE FOLLOWING ITEMS FOR SLAVE DEVICES ONLY:
Reports Binary Input Change Events when no Reports time-tagged Binary Input Change Events when
specific variation requested: no specific variation requested:
G Never G Never
G Only time-tagged O Binary Input Change With Time
G Only non-time-tagged O Binary Input Change With Relative Time
O Configurable to send both, one or the other G Configurable (attach explanation)
(attach explanation)
Sends Unsolicited Responses: Sends Static Data in Unsolicited Responses:
G Never G Never
O Configurable (attach explanation) O When Device Restarts
G Only certain objects O When Status Flags Change
G Sometimes (attach explanation)
No other options are permitted.
O ENABLE/DISABLE UNSOLICITED
Function codes supported
Default Counter Object/Variation: Counters Roll Over at:
G No Counters Reported G No Counters Reported

O Configurable (attach explanation) O Configurable (attach explanation)
G Default Object ______________ G 16 Bits
Default Variation ______________ G 32 Bits
G Point-by-point list attached G Other Value _____________
G Point-by-point list attached
Sends Multi-Fragment Responses: O Yes G No

GLOSSARY OF TERMS
ox A numerical prefix indicating that the number

following is a hexadecimal number.
application A piece of software (a program) consisting of one or

more processes and supporting functions.
ASCII American Standard Code for Information

Interchange. A seven-bit code that standardizes a set
of characters representing letters and numbers for
international use.
base system In WESDAC equipment, the system software and

all the necessary base-application programs. Does
not include any custom applications.
binary A number system having only two symbols (1 and

0), and where values are expressed in the base two
number system.
bit Abbreviation of binary digit. The smallest unit of

information in a binary system. Has a value of either
one (1) or zero (0).
byte A group of eight adjacent bits that function as a

single unit. Defined as an octet by the International
Electrotechnical Commission (IEC).

B021-0FS.WES, Version 7.00 G-1
change of state A significant change (as defined by a particular
system) in the condition of a point being monitored,
for example, a change in flow rate, temperature,
voltage, etc. Usually associated with dual-state
status (that is, alarm/normal conditions).
Abbreviated as COS.
char The name of a data-type in the C programming

language. Stands for character, or a group of eight
bits that function as a single unit.
communication processor module An intelligent device that functions as a data

translator from one data format to another.
Abbreviated as CPM.
custom application A piece of software (a program) designed to address

a particular need of a particular user. Contrast with
base-system application, which addresses a need
common to most users.
data-collection application A software application that acquires data from and

sends data to various intelligent electronic devices.
Abbreviated as DCA.
data-processing application A software application that requests and processes

data as it is required by (usually) a master station.
Abbreviated as DPA.
decimal A number system having ten symbols, and where

values are expressed in the base ten number system.
hexadecimal A number system having 16 symbols, and where

values are expressed in the base 16 number system.
Commonly used to abbreviate binary data.
Sometimes referred to as hex. Hexadecimal
numbers are often preceded by the prefix ox.
host The client or host station/computer, with which the

RTU equipment communicates. Also called a
master or master station.

G-2 B021-0FS.WES, Version 7.00
input/output A type or types of hardware device(s) used to
achieve human-to-machine or machine-to-machine
communication. Abbreviated as I/O.
logical remote unit An RTU existing in software, but not physically.

LRUs are created by software partitioning of a
single physical RTU so that it appears to the master
station as two or more RTUs. This technique is
usually employed as a means by which to overcome
the point-addressing limitations of a particular
protocol, or to form a logical grouping of data.
Abbreviated as LRU.
master The client or host station or computer, with which

the RTU equipment communicates. Also referred to
as a host or host computer.
master remote unit An intelligent electronic device that acts as a data

concentrator or master to other intelligent electronic
devices. (That is, an MRU acquires data from and
sends data to other intelligent electronic devices.)
Also referred to as a sub-master or remote master.
Abbreviated as MRU.
non-volatile A semi-permanent type of data storage (memory)

random-access memory that is backed up by batteries to maintain stored data
even if system power is lost. Can be both read and
changed by the system. Abbreviated as NVRAM.
port An interface point connecting a communications

channel and a device.
random-access memory A type of temporary data storage (memory) that can

be read and changed while the computer is in use.
Data stored in random-access memory is lost if the
system loses power. Abbreviated as RAM.
read-only memory A type of permanent data storage (memory) that can

be read but not altered by the system. Data stored in
read-only memory is not affected by power loss to
the system. Abbreviated as ROM.

B021-0FS.WES, Version 7.00 G-3
remote terminal unit A piece of equipment located at a distance from a
master station to monitor and control the status of
outlying equipment, and to communicate the
information back to the master station or host.
Abbreviated as RTU.
sequence of events A time-tagged change of state, logged as part of a

chronological record of significant changes in the
condition of a particular point or points being
monitored. Abbreviated as SOE.
source code A piece of code that has not yet been compiled or
assembled (that is, it is still in the language it was
programmed in) and so cannot yet run on a
machine.
sub-remote unit A physical device (for example peripheral boards,

D20 RTUs, non-D20 RTUs, meters, or other
intelligent electronic device) that collects data,
processes it in some way, and communicates it to a
master remote unit (MRU). SRUs (also called slave
units) are able to respond to commands from
MRUs. Abbreviated as SRU.
system points A list of points owned by a data-collection

application or a data-translation application. System
points may include hardware points, and pseudo-
points.
trip/close A type of digital output that stops or starts an action.

Trip/close outputs utilize two relays: a master relay
and a select relay. Abbreviated as T/C.
WESDAC Interface Node A module of software that manages the transfer,

storage, and manipulation of data between data-
collection applications (DCA), data-processing
applications (DPA) and data-translation applications
(DTA). Abbreviated as WIN.

G-4 B021-0FS.WES, Version 7.00
LIST OF ACRONYMS
AND ABBREVIATIONS
ACK acknowledgement
ASCII American Standard Code for Information Interchange
BridgeMAN Bridge Manager
CCU central control unit

COS change of state
CPM communication processor module
DBMR database manager

DCA data-collection application
DNP distributed network protocol
DPA data-processing application
EOF end of file

EPA enhanced protocol architecture
I/O input/output
ID identification number
IEC International Electrotechnical Commission
IIN internal indication
LRU logical remote unit
MRU master remote unit

B021-0FS.WES, Version 7.00 L-1
NACK negative acknowledgement
NVRAM non-volatile random-access memory
OS operating system
RAM random-access memory

ROM read-only memory
RTU remote terminal unit
SOE sequence of events

SRU sub-remote unit
T/C trip/close
TT time-tagged
WESDAC WESDAC Data Acquisition and Control

WESMAINT WESDAC Maintenance Facility
WIN WESDAC Interface Node

L-2 B021-0FS.WES, Version 7.00

DNP V3.00 Dpa: Functional Specification

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DNP V3.00 Dpa: Functional Specification

Uploaded by

Copyright:

Available Formats

GE HARRIS

Energy Control Systems Canada, Inc.

DNP V3.00 DPA

Submitted By: Authorized By:

WESDAC is a registered trademark of GE HARRIS Energy Control Systems Canada,

DNP V3.00 DPA Functional Specification

VERSION DATE INITIALS COMMENT

1.00 93.09.14 CL Revisions as per Paul Morton.

1.01 94.07.11 PM Added Appendix B. Format check, changed version

2.00 94.07.14 AV Versioned up the document to 2.00 to match the

3.00 95.02.09 CT 3-8, 3-9 Clarified Section 3.1.13 Assign Classes

3.01 95.07.26 CT Section 2.3 Added description of online/offline

4.00 95.11.27 CT Updated entire document to meet version 400

DNP V3.00 DPA Functional Specification

5.00 96.04.18 TW Updated document to include the following:

5.01 96.10.10 GG Re-added Frozen Counter Events and Frozen Delta

6.00 98.07.01 TW Rev. up for a major revision of the software version.

98.01.27 SG (BOW Software Inc.)

GE HARRIS Energy Control Systems Canada, Inc.

ABOUT THIS SPECIFICATION

Chapter 1: DATA OBJECTS

DNP V3.00 DPA Functional Specification

Chapter 2: PROTOCOL IMPLEMENTATION

Chapter 3: SILENT MASTER OPERATING MODE

GE HARRIS Energy Control Systems Canada, Inc.

Appendix A: DNP DPA WIN USAGE A-1

Appendix B: DNP DPA IMPLEMENTATION MATRIX B-1

Appendix C: DEVICE PROFILE DOCUMENT C-1

GLOSSARY OF TERMS G-1

LIST OF ACRONYMS AND ABBREVIATIONS L-1

DNP V3.00 DPA Functional Specification

Figure 1 EPA Layers For The DNP DPA xvii

DNP V3.00 DPA Functional Specification

Table 1-1 File Identifier Object WRITE 1-27

DNP V3.00 DPA Functional Specification

PURPOSE OF THIS SPECIFICATION

WHO SHOULD USE THIS SPECIFICATION

DNP V3.00 DPA Functional Specification

CONVENTIONS USED IN THIS SPECIFICATION

GE HARRIS Energy Control Systems Canada, Inc.

DNP V3.00 DPA Functional Specification

L NOTE: Unless otherwise specified, all functionality of the DNP DPA is

GE HARRIS Energy Control Systems Canada, Inc.

WESDAC Interface Node

APPLICATION LAYER DNP DPA

One or more Data Links (such

PHYSICAL LAYER Physical Layer

Figure 1 EPA Layers For The DNP DPA

DNP V3.00 DPA Functional Specification

DNP V3.00 DPA DNP V3.00 DPA

Data Data Data

DNP V3.00 DNP V3.00

Figure 2 Example of A System with Multiple DNP DPAs

GE HARRIS Energy Control Systems Canada, Inc.

DNP V3.00 DPA Functional Specification

GE HARRIS Energy Control Systems Canada, Inc.

DNP V3.00 DPA Functional Specification

1.3 UNSOLICITED RESPONSES

GE HARRIS Energy Control Systems Canada, Inc.

L NOTE: Regardless of the variation specified (Class 0, variation 0, with flag, or

DNP V3.00 DPA Functional Specification

L NOTE: A single point cannot be configured with WithoutTime = Enabled and

For example, consider the configuration for 8 points below.