N00-324 DNP3 Protocol Technical Manual CAPM4-5

DNP3 Protocol
Technical Manual
For
Automatic Circuit Reclosers
And
Load Break Switches
With
CAPM-4/5 Controllers
Scope
This document describes the DNP3 Protocol and Database Implementation on
Schneider Electric (Australia) Pty Limited Automatic Circuit Reclosers and Load Break
Switches using CAPM-4/5 controllers.
Document Part No: N00-324

Document Revision Level: R54
Copyright Schneider Electric (Australia) Pty

Limited 2009
DNP3 Protocol Technical Manual
Schneider Electric (Australia) Pty Limited.

80 Schneider Road
Eagle Farm 4009
Queensland
Australia.
Tel +61 7 3635 7500
Fax +61 7 3635 7560
LIMITATIONS
This document is copyright and is provided solely for the use of the recipient. It is not to
be copied in any way, nor its contents divulged to any third party, nor to be used as the
basis of a tender or specification without the express written permission of Schneider
Electric (Australia) Pty. Limited.
This document discloses confidential intellectual property that belongs to Schneider
Electric (Australia) Pty. Limited. This document does not invest any rights to Schneider
Electric (Australia) Pty. Limited intellectual property in the recipient. Moreover the recipient
is required not to disclose any of the intellectual property contained in this document to
any other party unless authorised in writing by Schneider Electric (Australia) Pty. Limited.
Public Access: \stdprod\N00\N00-324R54.pdf

Source: \R&D\CAPM4\manuals\N00-324 DNP3 Protocol Technical Manual CAPM4-
5.doc.doc
N00-324 R54 i
Revision Control
Revision Author Date Comment

R18 LM 31/08/99 Added password protection section
Corrected the explanation to Analogue Input 11
R19 LM 06/09/99 Changed the defaults for DL Cf Reqd and DL Max
Retries
Changed the wording for CTS
Revised the wording for sections 7.3.3, 7.3.5, 7.4
R20 LM 08/09/99 Changed the Apl Cf TO maximum value
Corrected small Analogue set IO list classes to match
full.
R21 LM 22/11/99 Added OFF field to port selection
Fixed I and X terminology statement
Added W Series support details to appendices
Added Initialisation time to Appendix A Protocol
Timing
Added loop automation points to Appendices D and F
Changed Gas Pressure deadband to 5kPaG
R22 LM 09/12/99 Added in functionality for FORCED Unsolicited
Behaviour
Added Loop Automation ON/OFF control to appendix H.
Corrected Source Voltage Status terminology (App D BI
76)
R23 LM 31/01/00 Added new binary and counter object support to Device
Profile
Added Loop Automation Trip/Close Request to Appendix H
Added Dummy Circuit Breaker to Appendix H
R24 LM 18/02/00 Reworded protection data operation + loop auto
trip/close pending
R25 LM 02/03/00 Corrected/improved numerous point descriptions in
appendices
Reformatted/improved parameter setting descriptions
Corrected Max value for counter, kPa max to 300, PSI
max to 44
Added phase designation and power flow direction notes to
appendices
R26 LM 05/07/00 Changed ownership to Nulec Industries
Added High/Low threshold alarms for A, V, kW
Removed event log appendicies
R27 LM 25/07/00 Updated the DNP device profile and implementation
table
R28 LM 06/10/00 Added new Aux Fail Alarm to Binary Inputs in App D
Limited the max DNP3 addresses to 65519 (0xFFEF)
Added DNP3 VT objects and note to implementation
table
Added support for Collision Avoidance
Changed Pre-transmission lower limit to zero
Added support for limited unsolicited response retries
Added DNP3 analog input deadband object support
Added DNP3 technical bulletin support list to App C
R29 LM 30/01/01 Clarified DNP3 technical bulletin support list
Increased the resolution of Collision Avoidance
N00-324 R54 Page ii

Reworded analogue input deadband section

Clarified the analogue input alarm section
Configurable deadband low limit set to 1.
Added ACR Control Status online/offline support
Moved Tx Delay location and reworded for CA usage
Changed operation such that changing only the DNP3 addresses,
unsolicited mode and Analog set will result in warm restart of
protocol handler
Added Maximum average daily demand point
R30 RDM 17-Jan-2001 Added LBS Appendices and amended associated
wording
Extended support include CAPM5 controllers.
R31 LM 1-Mar-2001 Added IIN1-4 to device profile
Removed aux overvoltage BI from points list
R32 LM 7-Mar-2001 V25/26 Released
R33 LM 3-May-2001 Added comment note for analog phase-phase voltage
range
Corrected some LBS map comments
R34 LM 22-July-2001 Added work tag (hot line tag) trip to ACR binary input list
R36 LM 16-Sept-2001 Added Paknet interface to P8 RS-232 port
R37 DPC 20-Nov-2001 Corrections to Appendix P Paknet Call Procedures
R38 PJM 29-Jan-2002 Additions for Close flags, ACO and Live Load blocking.
R39 PJM 20-Feb-2002 Toggled meaning of ACO Mode Binary Status.
R40 DPC 14-Mar-2002 Added support for Generator Control
R41 DPC 17-Apr-2002 Add Apl Frag Size to a panel page.
Add Unsolicited Class Reporting option.
Removed ACO points from LBS(Appendix J, N).
Support upgrade to DNP 2001: Appendix C.
R42 DPC 17-May-2002 Added ACO Rank, corrected ACO Mode (Appendix H).
R43 DPC 17-Jun-2002 Added Protocol IOEX Control
Added more description to Power Flow Direction
Added BOTH option to Analog Alarm
Changes to Application Confirm Timeout
R44 DPC 18-Jul-2002 Changes to Application Confirm Timeout
Corrected default Post-Transmission Period to 35ms.
Added note about PAKNET screen visibility.
Changes to Unsolicited Response Retry Delay
Corrected the description of IOEX inputs in IO map
Added Output Control Mode
R45 PJM 12-Aug-2002 Added NPS support digital and analog points plus
analog
deadband setup
Updated Maximum Average Demand comments.
R46 PJM 10-Sep-2002 Removed Analog Set Selection for introduction
Configurable DNP
Put notes in all point appendices saying they are frozen at version 27-17 CAPM code
Small corrections after comparison with N00-331.
Improved description for unsolicited resp event buffering
Pre-Tx and Post-Tx times maximum now 3000ms.
Corrected clear conditions for Loop Auto, ACO, Generator Control.
Correct Unsolicited Response Class x Notification Max Count.
R47 PJM 26-Nov-2002 Added CTS Ignore/Dont Ignore field to communications
page 1
R48 LM 05-Mar-2003 Clarified CTS behaviour
N00-324 R54 Page iii

Added the map field to Database Configuration 2 page

R49 PJM 15-Oct-2003 Added Unsolicited Master setting field.
R50 RDM 09-May-2005 Draft enhancements: Sec 2.1 - 1mS resolution,
Sec 4.1.2 GMT Time
R51 RDM 10-Nov-05 Add note about Remote Class zero assignment & Power
ON/Reset.
R52 NCD 8-July-2009 Updated company name, address and phone numbers.
R53 RDM 30-July-2009 Add:-
REGENERATED/IDENTICAL Unsolicited Response
selection,
SBO Sequence Check ON/OFF, and
Analogue Input Event Mode BUFFER ALL/PRESENT
VALUE
(Refer:RFC12769).
R54 RDM 06-Nov-2009 Reinstate DNP3 point identifiers in Appendices.
N00-324 R54 Page iv

Contents
1. Introduction............................................................................................................... 1
2. Overview .................................................................................................................. 1
2.1. Status Points.................................................................................................. 1
2.2. Controls ......................................................................................................... 2
2.3. Data Configuration......................................................................................... 2
2.4. Password Protection ...................................................................................... 2
2.5. LBS vs ACR Point Mapping. .......................................................................... 2
3. Applicability............................................................................................................... 3
3.1. Control Cubicle Software ............................................................................... 3
3.2. DNP3 Protocol ............................................................................................... 3
3.3. Switchgear Type ............................................................................................ 3
3.4. Terminology ................................................................................................... 3
4. Protocol Configuration .............................................................................................. 4
4.1. Transmission Services Configuration ............................................................ 4
4.1.1. Overview........................................................................................................ 4
4.1.2. Transmission Services Parameters ............................................................... 4
4.1.3. Use of Application and Data Link Confirmation/Retries ................................. 7
4.2. Unsolicited Response Configuration.............................................................. 8
4.2.1. Overview........................................................................................................ 8
4.2.2. Unsolicited Response Parameters................................................................. 8
4.2.3. Event Buffering ............................................................................................ 12
4.3. Data Configuration....................................................................................... 13
4.3.1. Overview...................................................................................................... 13
4.3.2. Database Parameters .................................................................................. 13
4.3.3. Database Size Permutations ....................................................................... 16
4.3.4. Default Database Data Objects ................................................................... 16
4.3.5. Analogue Deadband Parameters................................................................. 17
4.3.6. Analogue Alarm Reporting........................................................................... 18
4.3.7. Analogue Alarm Parameters........................................................................ 18
5. Physical Layer ........................................................................................................ 21
5.1. Communications Ports Supported ............................................................... 21
5.2. RS-232 Communication Specifications........................................................ 21
5.2.1. RS-232 Hardware Signals ........................................................................... 21
5.2.2. RS-232 Character Definition ........................................................................ 21
5.2.3. RS-232 Configuration Parameters............................................................... 21
5.2.4. Carrier Detect .............................................................................................. 25
5.2.5. Transmitting a DNP3 Packet........................................................................ 25
5.2.6. DTR ............................................................................................................. 25
5.2.7. Dialling Modem Support............................................................................... 25
5.2.8. PAKNET Configuration ................................................................................ 26
5.3. V23 FSK Communication Specifications...................................................... 27
5.3.1. V23 Hardware Signals ................................................................................. 27
5.3.2. V23 Configuration Parameters..................................................................... 28
5.3.3. V23 Handshaking Signals............................................................................ 31
5.4. Communication Statistics............................................................................. 32
Appendix A Protocol Timings ............................................................................................ 33
Appendix B DNP3 Device Profile ...................................................................................... 34
Appendix C DNP3 Implementation Table.......................................................................... 37
Appendix D ACR - Binary Input Points (Status) ................................................................ 44
Appendix E ACR - Analogue Input Points (Status - Small Set) ......................................... 57
Appendix F ACR - Analogue Input Points (Status Full Set)............................................ 59
N00-324 R54 Page v

Appendix G ACR - Counter Point...................................................................................... 65

Appendix H ACR - Binary Output Points ........................................................................... 66
Appendix I ACR - Analogue Output Points........................................................................ 71
Appendix J LBS Binary Points Data (Status).................................................................. 72
Appendix K LBS - Analogue Input Points (Status - Small Set) .......................................... 80
Appendix L LBS - Analogue Input Points (Status Full Set)............................................. 82
Appendix M LBS - Counter Points..................................................................................... 86
Appendix N LBS - Binary Output Points ............................................................................ 87
Appendix O LBS - Analogue Output Points....................................................................... 91
Appendix P PAKNET Call Procedures .............................................................................. 92
Incoming Call (Poll or Control) Service Signals Disabled .................................... 92
Outgoing Call (Unsolicited CoS) Service Signals Disabled ................................. 92
Outgoing Call Failure and Retry Mechanism .......................................................... 92
Incoming Call (Poll or Control) Service Signals Enabled ..................................... 93
Outgoing Call (Unsolicited CoS) Service Signals Enabled .................................. 93
Outgoing Call Failure and Retry Mechanism .......................................................... 94
N00-324 R54 Page vi

1. Introduction
This document describes the Schneider Electric (Australia) Pty Limited DNP3
implementation for Automatic Circuit Reclosers (ACRs) and Load Break Switchs (LBS) on
Control and Protection Module types 4 and 5 (CAPM).
For more information about the Recloser mode or Load Break Switch refer to relevant
technical manual for your switchgear type.
This implementation is more complex than most telemetry protocols. It is essential to read
the Overview section in order to set up the SCADA system correctly.
2. Overview
The Schneider Electric (Australia) Pty Limited CAPM controller combines the functions of
protection relay and switchgear controller into a single intelligent electronic device (IED).
The controller provides a user friendly operator interface on a four line LCD control panel
that allows configuration and control of the switchgear.
In addition the controller generates time tagged events which are displayed on the
operator control panel. These events show the history of the switchgear operation for the
benefit of the operator and for post fault analysis.
Examples would be:
Operator Actions such as trip or close
Protection Pick up
Protection Trips
Fault Current Levels
Auto-reclose actions
These events are optimised to give the operator the most useful information.
Electricity supply utilities frequently link the controller into their SCADA systems as a
Remote Terminal Unit (RTU).
To make this simple the controller provides:
Mounting room for a radio or modem in the control cubicle.
Power supply for the radio or modem in the control cubicle.
Embedded protocol handler for the required SCADA protocol in the controller firmware.
The DNP3 protocol allows digital and analogue data to be sent from the controller to the
SCADA system with time tags attached. This facility has enabled Schneider Electric
(Australia) Pty Limited to provide a sophisticated SCADA system interface that not only
provides the SCADA system with status information but also allows the SCADA system to
re-create the Event Log display on the operator control panel.
2.1. Status Points
This implementation provides a set of status information about the switchgear that can be
used by a SCADA system to generate displays and events for operational purposes. This
data is called the Status Points. Refer to appendices D, E and F for ACR status points or
appendices J, K and L for LBS status points.
For example:
Open or Close Status
Lockout Status
Fault Flags
Line Currents and Voltages
Time tags are optional. If enabled, these status points are returned with time tags of 1
millisecond resolution.
N00-324 R54 1
2.2. Controls
A list of the controls supported by the protocol handler is detailed in Appendices H and N.
All controls have a corresponding binary status point. The master station must use these
status points to verify that the control action has been successful. Sometimes a control will
be rejected because of an underlying controller condition preventing the action. These
conditions are detailed in the table in the appendices.
The DNP3 protocol handler can trigger two events to be recorded in the controller event
log - DNP3 Trip Req and DNP3 Close Req. This event log reporting indicates only that
the protocol handler has requested a trip or a close from the controller. It does not
necessarily mean that the action has been taken. As detailed above, the request may be
over-ridden by operational conditions.
The DNP3 protocol handler is designated as a remote user. Refer to the equipment
manual for more information.
2.3. Data Configuration
Several means are provided to configure the data points required. These include:
Selection of three sets of analogue points full, small and none. Available with CAPM
software up to and including version 27.
Configurable map creation via an external tool available from CAPM software version 28
onwards.
Default data object type with/with out flag/time; analogue size
Point class assignment.
2.4. Password Protection
All DNP3 panel fields require password entry unless described as Display only or
otherwise stated.
For more information on operator control panel usage refer to the equipment manual.
2.5. LBS vs ACR Point Mapping.
The DNP3 protocol handler supports independent point maps for the ACR and LBS
switchgear types. The mapping for each is listed in the appendices. The type supported by
the protocol handler is firmware dependant and determined by the controller on power up.
If the incorrect configuration is supplied please refer to Schneider Electric (Australia) Pty
Limited or your distributor.
Use of DNP3 for LBS switchgear is only available with CAPM V25.01.00+ software.
N00-324 R54 2
3. Applicability
3.1. Control Cubicle Software
This document applies to Schneider Electric (Australia) Pty Limited pole top reclosers and
load break switches using a CAPM Controller which displays DNP3 Manual N00-
324R54+ on the controller capability pages.
To find these pages refer to the main equipment manual.
Some features described in this manual may only be available on later releases of the
software. In this case the manual will declare which version of software applies.
3.2. DNP3 Protocol
The protocol version implemented by Schneider Electric (Australia) Pty Limited is DNP3
and is described in the following documents: -
Basic Four Documentation Set :
DNP3 Application Layer, DNP3 User Group, dnpal.doc rev 0.03
DNP3 Transport Functions, DNP3 User Group, dnptf.doc rev 0.01
DNP3 Data Link Layer, DNP3 User Group, dnpdl.doc rev 0.02
DNP3 Data Object Library, DNP3 User Group, dnpdol.doc rev 0.02
Subset Definitions Document:
DNP3 Subset Definitions, DNP3 User Group, subset.wp6 rev 2.00
Technical Committee Bulletins:
Control Relay Output Block Control Codes, DNP3 User Group, TB2001-006.
Multiple Control Objects and Status Codes, DNP3 User Group, TB2001-001.
Control Relay Output Block Minimum Implementation, DNP3 User Group, 9701-002
DNP Confirmation and Retry Guidelines, DNP3 User Group, 9804-002
Cold/Warm Restart Sequence, DNP3 User Group, 9701-003
Analog Input Reporting Deadband, DNP3 User Group, 9809-001.
These documents are obtainable from the DNP3 users group, which can be contacted via
the web site http://www.dnp.org/.
3.3. Switchgear Type
Applicable to the following switchgear types.
N-Series ACR, all models with CAPM-4/5 controllers.
U-Series ACR, all models with CAPM-4/5 controllers
W-Series ACR, all models with CAPM-4/5 controllers
RL-Series LBS, all models with CAPM-4/5 controllers
3.4. Terminology
The terminology used in this document is that Earth Fault or Ground Fault is described as
Earth / Ground Fault and Sensitive Earth Fault (SEF) or Sensitive Ground Fault (SGF) is
described as SEF/SGF.
Also, bushing terminology used in this document is for U and W series switchgear ie I and
X for the switchgear terminals. On N or RL series switchgear the 1 side is described as I
and the 2 side is described as X.
Also note that the phase terminology is ABC and refers always to the phase set by the
Terminal Designation or Phasing option, never to the physical bushing or terminal on
the switchgear.
N00-324 R54 3
4. Protocol Configuration
The DNP3 protocol handler adds several pages to the System Status menus. The
additional pages fall into the following groups,
Transmission Services Configuration (refer Section 4.1)
Unsolicited Response Configuration (refer Section 4.2)
Data Configuration (refer Section 4.3)
Communications Configuration (refer Sections 5.2 and 5.3)
Communication Statistics (refer Section 5.4)
All protocol configuration parameters can be viewed, modified and stored on a personal
computer with the WSOS utility.
4.1. Transmission Services Configuration
4.1.1. Overview
The DNP3 protocol has a number of data link and application layer parameters that form
transmission service functions. The controller permits configuration of a number of these:
Data link layer confirmation
Data link time out
Application layer confirmation time out
Control select / operate time out period
Time Synchronisation request operation
GMT offset
4.1.2. Transmission Services Parameters
These pages allow the SCADA engineer to determine how the Data Link and Application
Layer of the DNP3 protocol handler transmits DNP3 data packets.
---- DNP Transmission Services 1 ----S

DL Cf Rqd SOMETIMES DL Cf TO 4000ms
DL Max Retries 2 Apl Cf TO 108000ms
Arm Select 10000ms Apl Frag Size 2048
---- DNP Transmission Services 2 ----S

DNP Address 5 Time Dly Rq 0min
GMT Time Disabled GMT Hours +10.0
Operate Seq Chk ON
Parameter Description
DL Cf Rqd Data Link Confirm Required
On some communications links it is required to have extra
communications integrity to ensure that all data link frames are
successfully received by the master station.
If NEVER, the protocol handler will not request acknowledgment
messages from the master station for data link frame transmissions. It
assumes all data link frames are received by the master station and
relies solely on application layer message integrity checking.
N00-324 R54 4
If SOMETIMES, the protocol handler requests a data link
acknowledge response from the master station only on multi-frame
DNP3 messages.
If ALWAYS, the protocol handler will expect a data link
acknowledgment message from the master station to all data link
frame transmissions.
Range: NEVER, SOMETIMES, ALWAYS.
Factory default is SOMETIMES
DL Cf TO Data Link Confirm Timeout
When the controller DNP3 data link layer transmits a frame that
requires an acknowledge response from the master station, it starts a
timer. The timer is triggered upon negation of RTS at the end of post
transmission.
If an acknowledge frame is not received from the master station with-
in the data link confirm time out period, DL Cf TO, then the frame is
resent.
If the communications link has failed then the controller will continue
retransmissions until DL Max Retries failures occur after which it
informs the application layer of the failure.
Range: 50 to 65535 ms.
Factory default is 4000 ms
DL Max Data Link Maximum Retries
Retries Maximum number of times a frame is re-sent before communication
failure is identified.
Range: 0 255.
Factory default is 2
Apl Cf TO Application Layer Confirm Timeout
When the controller transmits some DNP3 messages, such as
application layer messages that contain change of state data, a DNP3
application layer confirm message is expected from the master
station. When the last byte of one these messages is transmitted by
the controller a timer is started.
If an application layer confirm message is not received from the
master station with-in the time out period then the message is deemed
failed. Refer to section 4.2.3 for more information regarding failed
application layer message handling.
If the application layer message is too large for a single data link
frame then the protocol handler segments the application message
into multiple data link frames. The application confirm timeout period
must therefore allow for multiple data link frames.
If DL Cf Rqd is set to either SOMETIMES or ALWAYS, then setting
the confirm timeout Apl Cf TO using the following formulae is
recommended:
If Apl Frag Size >= 249,
Apl Cf TO >= ((DL Max Retries + 1) x DL Cf TO x Apl Frag Size /
249)
If Apl Frag Size < 249,
Apl Cf TO >= ((DL Max Retries + 1) x DL Cf TO)
WSOS will offer this value to the user if entering a value outside these
formulae.
If DL Cf Rqd is set to NEVER then the minimum Apl Cf TO is 0ms.
Range: 0 or (Apl Cf TOCalculated) to 3600000 ms.
N00-324 R54 5
Arm Select Arm Select Timeout
Maximum time permitted, in milliseconds, between receiving a select
command message and an operate command message from the
master station for the control action to be deemed valid.
Factory default is 10,000 ms
Apl Frag Size Application Layer Maximum Fragment Size
Note 1 Defines the maximum size of the application layer fragment that can
be sent at any one time. Multiple application fragments will be created
if the CAPM data to be transmitted exceeds this size.
For high noise environments, reducing the size of the transmitted data
link frame can result in improved communication reliability. This can
be done by setting the Apl Frag Size value to less than 249. However,
it should be noted that this increased reliability will result in increased
turn around time for large CAPM data transmission.
For more information refer to the DNP3 User Group Technical Bulletin
9804-002 DNP Confirmation and Retry Guidelines Section 4.2.
If WSOS DNP communications is to be used then it is recommended
that this value be set to 2048.
Range: 50 to 2048 bytes.
Factory default is 2048 bytes
DNP Address DNP3 Station Address
The station address of the controller on the communication link.
Changing this parameter will cause the DNP3 handler task to perform
a warm restart. This will mean a re-initialisation of all communication
parameters such as FCB, sequence numbers, restart internal
indication etc. A temporary loss of communications with the master
station may occur. Also, any queued events will be deleted.
This field is not configurable via WSOS if DNP3 Modem/Radio
communications is used.
Range: 0 to 65519
Time Dly Rq Time Synchronisation Request Delay
The DNP3 protocol allows for the master station to send time
synchronisation messages independently or at the request of the
controller or both.
Time Dly Rq is the amount of time, in minutes, after the last master
station time synchronisation message that the controller will wait
before setting the Time Synchronisation Required internal indication
bit (IIN1-4). This bit is sent to the master station in every controller
DNP3 message.
If this field is set to 0 then the internal indication bit is never set and
the master station solely determines time synchronisation operation.
Range: 0 65535 minutes
Factory default is 0 minutes
GMT Time GMT Time Stamp Selection
Note 2 Enables the controller to transmit GMT time stamped messages via
the DNP SCADA link translated from the controllers local time setting
used to time stamp events within the event log.
Range: Enabled/Disabled
Factory default is Disabled
N00-324 R54 6
GMT Hours GMT Time Hours (offset)
Note 2 The GMT time stamp adjustment made to DNP3 SCADA link time
stamps sent up the communications link when the GMT Time stamp
setting is selected Enabled. (The GMT Hours value is applied to the
controllers native local time setting).
Range: -12.0+12.0 in 0.5-hour steps.
Factory default is +10.0
Operate Seq ON: the controller requires DNP3 Select-Before-Operate (SBO)
Chk requests to be contiguously sequenced, i.e. if the select sequence
number is N in the Application Layer sequence, then the operate
Application Layer message request sequence number must be N+1
(within the application layer sequence number range).
A setting of OFF allows the controller to accept out of sequence

Operate requests.
Either way - the operate Application Layer request message must be

received within the Select/Operate Timeout period to activate the
selected control.
Range: ON/OFF
Factory default is ON
Applicable to version V28 from V28-37.00 onwards.
Note
The maximum number of DNP application sequence numbers permitted per report attempt
is limited to 16. It is therefore possible that if Apl Frag Size is set low and the number of
available events is large then not all available event data will be reported in a single
message sequence. If Unsolicited responses are not enabled then the master station must
monitor event availability in controller using the class data available internal indicators and
perform multiple poll attempts to read all data.
When GMT Time is set Enabled all master station time reads/writes are treated as GMT
time values and are translated accordingly within the controller upon
reception/transmission by DNP.
4.1.3. Use of Application and Data Link Confirmation/Retries

The use of application and data link confirmations and retries depends upon the nature of
data transfer on the communications link ie whether controller unsolicited responses are
used or the master frequently polls for data.
When the controller is configured to transmit unsolicited response messages, it is
recommended that only the controller be configured to use of data link confirmations and
retries. It is the controllers responsibility to ensure that data is successfully transmitted to
the master station so it will attempt to retry sending a message if it detects a failure. If the
master station also performs integrity polls on the same communications link then it should
do so infrequently to limit collision problems.
Alternatively, if a master station polls the controller frequently and the controllers
unsolicited responses are not enabled then it is recommended that the controller not be
configured to use data link retries and the data link confirmation mode be set to
SOMETIMES. It is the master stations responsibility to gather data. If the master station
detects a communication failure then it can choose to either move on and poll the next
N00-324 R54 7
device on a multi-drop communication link or perform a poll retry on the failed device. A
controller retry at this stage increases the probability of collisions.
For more information refer to the DNP3 User Group Technical Bulletin 9804-002 DNP
Confirmation and Retry Guidelines.
4.2. Unsolicited Response Configuration
4.2.1. Overview
The protocol handlers DNP3 event processing informs the master station that a change in
a binary input has occurred or an analogue input has exceeded its deadband range.
The transmission of event data can be performed using two methods:
Master initiated polling for event data.
Controller initiated transmissions called Unsolicited Responses.
Events can be reported in three data classes:
Class 1 - high priority event class
Class 2 - medium priority event class, and
Class 3 - low priority event class
The event class of DNP3 binary and analogue points can be configured using a tool
embedded in WSOS.
Note: the fourth DNP3 data class, Class 0, is not an event class. It is used in the reporting
of current (static) value of data and not change of state events. Setting a point to class 0
will prevent the protocol handler from reporting change of state events for that point to the
master station. The point will remain accessible via static data polls.
The following controller display pages allow configuration of Unsolicited Response
behaviour.
4.2.2. Unsolicited Response Parameters
--------- DNP Unsolicited 1 --------S

Unsolicited OFF Master Addr 3
Unsol Retries 255 Unsol Dly 110s
Send Class READY Unsol -- -- --

C1 Count 1 C1 Delay 1s

C1 Timeout 0s C1 Buffered 0
N00-324 R54 8
--------- DNP Unsolicited 4 ---------S

Unsol REGENERATED
Unsolicited Enable/Disable Unsolicited Responses
Note 1 If OFF, change of state events are buffered but only sent as
responses to event polls from the master. Any Enable or Disable
Unsolicited Messages commands received by the controller will
result in the controller responding with its Function Code Not
Implemented internal indication bit set.
If ON or FORCED, change of state events are buffered and are
transmitted when:-
A class count is exceeded, or
A class notification delay timer expires, or
As a response to a master station event poll.
When a class count is exceeded, or class notification delay timer
expires, then the number and type of events transmitted is
determined by Send Class.
If the master station issues an Enable or a Disable Unsolicited
Messages command to the controller after the controller has sent
its initial unsolicited Null message then the mode of the controller
will be overridden regardless of ON or FORCED setting.
Note:
If ON, the unsolicited reporting ability in the controller is enabled.
The controller will inform the master station of this ability via an
initial unsolicited Null message and will only transmit unsolicited
response change of state events after it receives an Enable
Unsolicited Messages command from the master station.
Setting this field to ON will mean that the controller DNP3
implementation is compliant with the DNP3-1999+
specification.
If FORCED, the controller will transmit unsolicited response
change of state events immediately without waiting for the Enable
Unsolicited Messages command from the master station.
Setting this field to FORCED will cause the controller DNP3
implementation to be non-compliant with the DNP3-1999+
specification and is not recommended. This parameter setting
has been provided for compatibility with legacy master station
implementations that are in conflict with the specification.
The status of the controller with respect to master station
Enable/Disable Unsolicited Messages commands can be seen
in the Unsol C1 C2 C3 field.
Range: OFF, ON, FORCED.
Factory default is OFF
Master Addr DNP3 Master Station Address
Note 1 This is the DNP3 address to which the unsolicited responses are
sent.
N00-324 R54 9
If the controller is set up to communicate with WSOS using DNP3
Radio communications then it is recommended that this field
should not be set to the WSOS DNP3 master address.
Range: 0 to 65519
Factory default is 3.
Unsol Retries Unsolicited Response Number of Retries
Maximum number of attempts to re-transmit an unsolicited
response without getting a confirmation from the master.
Refer to section 4.2.3 below for more information.
This limitation does not apply to an initial unsolicited Null
message. (A DNP3-2000 requirement.)
A value of 0 means that only a single transmission is made and
no re-transmits are attempted.
A value of 255 means unlimited retries ie maximum limit is
disabled.
Range: 0 to 255
Unsol Dly Unsolicited Response Retry Delay
If the controller has not received a confirmation from the master
station to an unsolicited response within Apl Cf TO period then
this parameter determines when the next unsolicited response will
be sent.
The Apl Cf TO timer and Unsol Dly timers are started at the same
time ie started immediately after the transmission of the last byte
of a controller message that expects a response from the master.
If Unsol Dly is greater than Apl Cf TO then it will wait until Unsol
Dly seconds after transmission of last message before sending a
retry.
Unsol Dly should never be set to less than Apl Cf TO.
Range: 1 to 86400 seconds
Factory default is 110s
Send Class Unsolicited Response Class Reporting
Used to control which classes are transmitted in the unsolicited
response message when a class count is exceeded or a class
notification delay timer expires.
If READY then only the events of that class are reported.
If ALL then all available events, irrespective of class, will be
included in the unsolicited message.
If PRIORITY then any events available of equal or higher priority
are sent. For example, if Class 2 events are ready to be sent and
Class 1 events are available but not ready then both classes will
automatically be sent. Any available Class 3 events will not be
included.
Note that if set to READY or PRIORITY then the reported
unsolicited message may have internal indicator bits (IINs) set to
indicate data available in other classes. Some master stations,
upon seeing these bits set, will immediately send a poll for the
unreported data. In this case, ALL is recommended for greater
communication efficiency.
Range: READY, ALL, PRIORITY
Factory default is READY
Unsol Unsolicited Response Status
N00-324 R54 10
The status of the controller with respect to master station
Enable/Disable Unsolicited Messages commands.
C1 C2 C3 If C1, C2 and/or C3 then the class has been enabled by
-- -- -- master.
If -- then the class has been disabled by master.
For FORCED mode the controller will initialise to C1 C2 C3.
For OFF mode the controller will show -- -- --
(Display only)
C1 Count Unsolicited Response Class 1 Notification Max Count
The number of events (Binary and Analogue) of type Class 1 that
must occur before an unsolicited response message is triggered.
Range: 1 to 450
Factory default is 1 event.
Range: 1 to 450
Factory default is 3 events.
Range: 1 to 450
Factory default is 5 events.
C1 Delay Unsolicited Response Class 1 Notification Delay
The maximum time an event in this class will wait to be reported.
Factory default is 1s.
C1 Timeout Unsolicited Response Class 1 Notification Time
The number of seconds remaining before an unsolicited response
class 1 transmission. (Display only)
C1 Buffered Unsolicited Response Class 1 Buffered Events
The total number of queued class 1 events in protocol handler
event buffers (Binary and Analogue).
(Display only)
The total number of queued class 2 events in the protocol handler
N00-324 R54 11
(Display only)
The total number of queued class 3 events in the protocol handler
(Display only)
Unsol Selects the Unsolicited Response retry type that is transmitted
(REGENERATED / when an unsolicited response is Unconfirmed by the master
IDENTICAL) station and a retransmission is required by the out-station.
Note 1
The octets of a REGENERATED unsolicited response retry - may
contain some or all of the data from the previous unsolicited
response, and may also include updated data, new data and
changed IIN octets. The sequence number in the application
control octet is incremented from the previously transmitted
unsolicited response.
An IDENTICAL unsolicited response retry - is a repeat, octet-for-

octet of the previously transmitted unsolicited response. The
sequence number appearing in the application control octet of an
identical retry and the previous unsolicited messages are the
same.
Range: Unsol REGENERATED / IDENTICAL

Factory default is REGENERATED
Applicable to version V28 for Release V28-37.00 onwards.
Refer DNP3Spec-V2-Part1-ApplicationLayer-20071215.pdf
Section 6.0
Note
Changing this parameter will cause the DNP3 handler task to perform a warm restart. This
will mean a re-initialisation of all communication parameters such as FCB, sequence
numbers, restart internal indication etc. A temporary loss of communications with the
master station may occur. Also, any queued events will be deleted.
4.2.3. Event Buffering
Multiple DNP3 change of state events can be transmitted in the same message. For
unsolicited messages, the change of state events included can be configured (Send
Class).
When events are transmitted, the software tags them as sent and retains them in the
event buffer. All messages containing events require an application layer confirm
response from the master station.
If the application layer receives an confirm response within the application layer
confirmation time out period (Apl Cf TO), then the tagged events are deleted from the
buffer.
If a confirm message is not received within the application layer confirm time out period
(Apl Cf TO) then all tagged events are untagged and are retained in the event buffer and
the protocol handler behaves as follows:
If unsolicited response messages are not enabled then the events are retransmitted when
next requested by the master station.
If unsolicited response messages are enabled then the protocol handler waits for the retry
delay timer (Unsol Dly) to expire before attempting to send another unsolicited response.
N00-324 R54 12
Selection of REGENERATED- or IDENTICAL- unsolicited response-retries is an

operator setting, Refer 4.2.2 Unsolicited Response Parameters Unsol.
If the maximum unsolicited response retry limit is enabled then after Unsol Retries the
protocol handler will cease attempting to send unsolicited responses until either:-
a successful application layer message, of any function code, addressed to it is received
from the master station, or
a new event is queued in the buffer.
the default (non configurable) Offline time-out expires.
If the 250 binary event buffer, or the 200 analogue event buffer, is full then the oldest
queued event will be over-written by a new event. Both event buffers reside in volatile
RAM.
4.3. Data Configuration
4.3.1. Overview
Data configuration is available for: -
Assigning default dead bands and high/low alarming to match the line conditions, these
are set separately for
Phase Currents (A, B, C)
Earth / Ground Current
Phase Voltages (A, B, C)
System Power (kVA, kVAR, kW)
Selection of analogue point sets (full, small, none, configured) based on the operational
requirements and transmission bandwidth available, particularly during an integrity poll.
Refer to appendices for points lists.
Enabling / Disabling event points.
Point class assignment. The classes shown in the appendices are factory defaults. The
class of each point can be assigned using the WSOS utility on a PC or via a DNP3
Assign Class commands from the master station.
The protocol does not allow class 0 (Zero) to be assigned remotely.

Data configurations, class assignments etc made remotely will revert to default/mapped
values upon a controller Power ON/Reset event.
4.3.2. Database Parameters

These pages allow the SCADA engineer to determine the type of data object reported in a
class event or integrity poll.
----- DNP Database Configuration 1 ---S

Analog Alarm OFF Analog Evts BUF ALL
Binary Time ON Analogue Time OFF
Analogue Size 16bit Analogue Flag OFF
N00-324 R54 13
----- DNP Database Configuration 2 ---S

Binary Output OFF Output Ctrl NORMAL
Standard ACR
Analog Alarm Analogue Alarming Operation
This field determines if analogue threshold alarming is enabled
or disabled. If enabled there are two behaviours.
If OFF, alarms are disabled. All binary alarm points are cleared.
Refer to section 0 for more information.
If BINARY, the operation of binary alarm points are enabled. All
alarms are independent of the protocol handler analogue
configuration. eg The event class of the analogues does not
effect alarm operation. Similarly binary alarming is not effected
by whether the analogues are in the configured Analogue Pnts
set.
If BOTH, then both binary and analogue data is reported to the
master station. When an alarm is set, or cleared, then the
current value of all related analogs are buffered for reporting as
well as the binary alarm point.
Range: OFF, BINARY, BOTH.
Analog Evts Select the Analog event reporting mode for Analog classes 1, 2
or 3 input change events.
Class 1,2 or 3 Analog input change events can be reported in

BUF ALL mode (Buffer-All, every evented change is reported).
Or in PRESENT-value mode, one event per point (when a
change is detected, the report of the change contains the
present-value at the time the event is reported -- not when the
change was detected).
Range: BUF ALL / PRESENT.

Factory default is BUF ALL
Applicable to version V28 from V28-37.00 onwards.
Binary Time Binary Time Tag Usage
Determines whether or not a time tag is included with DNP3
binary change of state events transmitted to a master station by
the controller.
Range: ON, OFF
Factory default is ON.
Analogue Time Analogue Time Tag Usage
Determines whether or not a time tag is included with DNP3
analogue change of state events transmitted to a master station
by the controller.
Range: ON, OFF
Analogue Size Default Analogue Data Object Size
Determines the size of the controller DNP3 default analogue
N00-324 R54 14
objects. This size is transmitted by the CAPM for all static and
event data responses where the master does not explicitly ask
for data size.
Range: 16, 32 bits (signed)
Factory default is 16 bit
Analogue Flag Analogue Flag Reporting
Determines whether or not a byte containing the analogues
status data is included with its value in a controller response to a
static data scan.
If ON, the controller will always send a flag of either 0x01 (point
online) or 0x21 (point online and overrange). It is recommended
that this field should only be set ON if the use of the analogue
flag bits is a master station requirement.
Range: ON, OFF
Binary Outputs Binary Output Status Reporting
Determines whether or not the Binary Output status data is
included in a controller response to an integrity poll.
If ON, the controller will always include the Binary Output status
data to the end of an integrity poll response.
Range: ON, OFF
DNP Output Control Mode
This field is used to interpret the controller mode
(Local/Remote).
Output Ctrl
NORMAL LOCAL controller mode disables
only explicitly documented binary
outputs eg. Close, Work Tag.
REMOTE controller mode places all binary outputs online.
Analogue outputs are always
Output Ctrl enabled.
SCADA
LOCAL controller mode places all binary and analogue outputs offline.
REMOTE controller mode places all binary and analogue
outputs online.
Note: Only the operation of DNP outputs is affected. Operation

of Local/Remote for Panel, WSOS, IOEX, FTI will remain as
documented in the standard equipment Technical Manuals.
Range: NORMAL, SCADA

Factory default is NORMAL
Loading DNP3 IO Map Status
mapping... Shows the status of the current IO map.
Standard ACR If map in currently loading then Loading mapping is shown
Standard LBS If map is invalid an ERROR: xxxxx message is shown where
xxxxx identifies the cause of error.
If map is valid then the name of the map is shown.
N00-324 R54 15
4.3.3. Database Size Permutations

To enable optimisation of communication bandwidth a configuration tool is available as
part of WSOS that gives the user the ability to select which analogue, digital and
accumulator data will be reported and controlled (refer to Configurable DNP Tool manual
N00-718) as a mapping loaded into the controller. The selection of this map determines
the size of the logical database used by the controllers DNP3 protocol handler and thus
determines the size of an integrity poll response.
Use of the DNP configuration tool is only available with CAPM software V28-01+. All
previous software used predefined data maps like those listed in the appendices. The
appendices of this manual reflect to the default map which is the one for CAPM software
V27-11. V28+ DNP map points are required to be added by the user via the tool.
4.3.4. Default Database Data Objects
When master stations perform change of state or integrity data polling then the reported
data object variation is typically not specified. The request simply asks for any data for a
specific DNP3 class type and it is left to the controllers protocol handler to determine
which DNP3 object variation is to be transmitted. The controller determined object
variations are referred to in this manual as the Default object variation. Some default data
object variations can be configured. The table below lists the selectable variations and
identifies the relevant configuration parameter required.
Controller Configuration Field

DNP3 Data Object Binary Analogue Analogue Analogue
Time Time Tag Size Flag
Tag
Binary Input Change without time
OFF
(Object 2 Variation 1)
Binary Input Change with time
ON
32 Bit Analogue Input
32 ON
16 Bit Analogue Input
16 ON
32 Bit Analogue Input without flag
32 OFF
16 Bit Analogue Input without flag
16 OFF
32 Bit Analogue Change Event
OFF 32
without time (Object 32 Variation 1)
16 Bit Analogue Change Event
OFF 16
without time (Object 32 Variation 2)
32 Bit Analogue Change Event with
ON 32
time (Object 32 Variation 3)
16 Bit Analogue Change Event with
ON 16
time (Object 32 Variation 4)
16 Bit Analogue Input Deadband
16
32 Bit Analogue Input Deadband
32
The rest of the default data objects used by the controller are:
Binary input status (Object 01 variation 01),
N00-324 R54 16
Binary counter status (Object 20 variation 05),

Frozen counter status (Object 21 variation 09), and
Binary output status (Object 10 variation 02).
These object types are not configurable.
4.3.5. Analogue Deadband Parameters

All the protocol handlers analogue inputs have a non-volatile default deadband value -
refer to Appendix E, Appendix F, Appendix K and Appendix L for the values. Some
default deadbands can be configured. These configurable deadbands are listed in the
table below. Upon controller startup, protocol handler restart, or a default deadband
setting change, the protocol handler copies all default settings to volatile memory over-
riding any previous settings. The protocol handler uses the volatile values in its deadband
reporting logic.
All volatile analogue input deadbands are configurable from the DNP3 master station on
a per point basis. If volatile deadband changes are to be maintained after the protocol
handler has restarted then it is the master stations responsibility for re-sending any
updated deadband values.
Deadband values are not reported in integrity or event polling. They are only available via
reads and writes of DNP3 analogue input deadband objects.
All deadbands supported by the protocol handler are fixed value format - ie the deadband
value represents an analogue inputs absolute value difference between the last reported
value and the threshold value that the current value must exceed in order to generate an
analogue change of state event.
For more information on DNP3 analogue deadband objects and behaviour refer to the
DNP3 User Group Technical Bulletin 9809-001 Analogue Input Reporting Deadband.
-------- DNP Default Deadbands -------S

Phase Current 10A Phase Voltage 100V
Earth Current 5A System Power 250
NPS Current 5A
Phase Current Phase Current Default Deadband
The A, B and C phase current analogue inputs will have their
deadband set to this value.
Range: 1 to 999A
Factory default is 10A.
Phase Voltage Phase Voltage Default Deadband
The A, B, and C phase voltage analogue inputs will have their
deadband set to this value. All phase-phase as well as phase-
earth/ground voltages are effected.
Range: 1 to 38000V
Factory default is 100V.
Earth/Gnd Earth/Ground Current Default Deadband
Current The earth/ground current analogue input will have its deadband
set to this value.
Range: 1 to 999A
N00-324 R54 17
System Power System Power Default Deadband

All power analogue inputs will have their deadband set to this
value i.e. KVA, KVAR, and KW.
Range: 1 54000 units
Factory default is 250 units.
NPS Current NPS Current Default Deadband
The NPS current analogue input will have its deadband set to
this value.
Range: 1 to 999A
4.3.6. Analogue Alarm Reporting
A/V/kW
H1
HIGH HI ALARM
LOW + 90% H2
HI ALARM
Time
LOW + 10% (HIGH LOW

L2
LOW LOW
L

The protocol handler has four configurable alarm analogue types: phase voltage, phase
current, earth current and system power. Each analogue type has a configurable high
alarm threshold value as well as a configurable low alarm threshold value.
Each of these analogue types also has a pair of binary alarm points in the protocol handler
database. If an analogue value passes the alarm threshold (eg H1 or L1 above) the binary
alarm becomes active. A binary alarm change of state event is put into the DNP3 event
buffers for reporting to the master station.
If, after a HI Alarm, all analogues of the same type are below the high alarm reset
threshold (eg H2 above), then the HI binary alarm is turned off and a binary alarm change
of state is put into the DNP3 event buffers for reporting to the master station.
If, after a LOW Alarm, the analogues of the same type are above the low alarm reset
threshold (eg L2 above), and all other, then the LOW binary alarm is turned off and a
binary alarm change of state is put into the DNP3 event buffers for reporting to the master
station.
Alarming is enabled/disabled via configuration of the protocol handlers Analogue Alarms
field.
4.3.7. Analogue Alarm Parameters

These pages allow the SCADA engineer to determine the high and low alarms for phase
current, phase voltage, ground current and system power.
N00-324 R54 18
---- DNP High Alarm Configuration ---S

NPS Current 999A
Phase Current Phase Current High Alarm
The A, B and C phase current analogue inputs will have their
high alarm threshold set to this value.
Range: 1 to 999A
Phase Voltage Phase Voltage High Alarm
high alarm threshold set to this value.
The type of voltage monitored, phase-phase or phase-
earth/ground, is determined by the configuration of the controller.
Refer to the equipment manual for more information.
Range: 1 to 38000V
Earth/Gnd Earth/Ground Current High Alarm
Current The earth/ground current analogue input will have its high alarm
threshold set to this value.
Range: 1 to 999A
System Power System Power High Alarm
All power analogue inputs will have their high alarm threshold
set to this value i.e. KVA, KVAR, and KW.
NPS Current NPS Current High Alarm
The NPS current analogue input will have its high alarm
Range: 1 to 999A
Note: If a high alarm threshold is set lower than, or equal to, its corresponding low alarm
threshold then the protocol handler will automatically reset the high threshold back to its
previous value.
---- DNP Low Alarm Configuration ----S

NPS Current 0A
Phase Current Phase Current Low Alarm
The A, B and C phase current analogue inputs will have their low
N00-324 R54 19
alarm threshold set to this value.

Range: 0 to 998A
Phase Voltage Phase Voltage Low Alarm
low alarm threshold set to this value.
The type of voltage monitored, phase-phase or phase-
earth/ground, is determined by the configuration of the controller.
Refer to the equipment manual for more information.
Range: 0 to 37999V
Earth/Gnd Earth/Ground Current Low Alarm
Current The earth/ground current analogue input will have its low alarm
Range: 0 to 998A
System Power System Power Low Alarm
All power analogue inputs will have their low alarm threshold set
to this value i.e. KVA, KVAR, and KW.
NPS Current NPS Current Low Alarm
The NPS current analogue input will have its low alarm threshold
set to this value.
Range: 0 to 998A
Note: If a low alarm threshold is set higher than, or equal to, its corresponding high alarm
threshold then the protocol handler will automatically reset the low threshold back to its
previous value.
N00-324 R54 20
5. Physical Layer
5.1. Communications Ports Supported
The controller can communicate to the Master station via one of the following ports.
RS-232 Port P8 (refer to section 5.2)
V23 FSK Port P10 (refer to section 5.3)
5.2. RS-232 Communication Specifications
The RS-232 communications on P8 can be configured to in one of three modes:
P8 RS-232 for direct or PSTN/radio modem communications
P8 PAKNET for communications to a PAD on a X.25 network (no service signals)
P8 PAKNET SS for communications to a PAD on a X.25 network using service signals
5.2.1. RS-232 Hardware Signals
P8 Pin Direction Description
2 From controller Tx Data (TxD)
3 To controller Rx Data (RxD)
4 From controller Request To Send (RTS)
5 To controller Clear To Send (CTS)
7 - Signal Ground
8 To controller Carrier Detect (CD)
20 From controller Data Terminal Ready (DTR)
The controller uses RTS/CTS hardware handshaking by default. If not supported by the
master then user must either put a loop back is required at the controller end of the
communications link or disable via the CTS Ignore field.
For P8 RS-232 the DTR is set upon protocol handler start up kept permanently asserted.
For P8 PAKNET and P8 PAKNET SS the DTR line is toggled as described below.
Also, the controller does not support any XON/XOFF software handshaking.
5.2.2. RS-232 Character Definition
RS-232 characters are 8 bit, 1 stop bit, no parity
5.2.3. RS-232 Configuration Parameters
The following communications configuration pages allow the user to specify parameters
required for operation of the physical link between the recloser and the master station.
-------- DNP Communications 1 ------S

P8 RS-232 RUNNING
Pre-Tx 250ms Post-Tx 35ms
Baud 9600 CTS Dont Ignore

Dialling DISABLED
Pre-amble DISABLED First Char 0x55
Repeat First 3 Last Char 0xFF
N00-324 R54 21

DCD Ignore CA Delay 1000ms
Tx Delay 0ms
None of these fields are configurable via WSOS if DNP3 Modem/Radio communications
is used.
Port Selection
This field selects the communications medium the DNP3 protocol
uses for transmission.
OFF When OFF is selected, the protocol handler is disabled.
P8 RS-232 When P8 RS 232 is selected, the protocol uses the P8 serial

port for all data. Also, the DNP Communications 1 and 2 pages
are automatically updated to reflect relevant RS-232 data as
detailed below.
P8 PAKNET
When P8 PAKNET is selected, the protocol handler uses the P8
serial port to communicate through an X.25 network via a
PAKNET Pad without using the Service Signals.
P8 PAKNET SS
When P8 PAKNET SS is selected, the protocol handler uses the
P8 serial port to communicate through an X.25 network via a
P10 V23 FSK PAKNET Pad using the Service Signals.
When P10 V23 FSK is selected, the protocol uses the built in
V23 modem on P10. Also, the DNP Communications 1 and 2
pages are automatically updated to reflect relevant FSK data.
Refer to section 5.3 for the P10 configuration details.
Range: OFF, P8 RS-232, P8 PAKNET, P8 PAKNET SS,
P10 FSK V23
Factory default is P8 RS 232
Protocol Status
Indication of the current status of the communications. (Display
only)
RUNNING RUNNING means that the protocol handler has connected to the
communication port (P8 or P10) and is running.
INACTIVE INACTIVE means that the protocol handler has been disabled via
the OFF state above or has been unable to connect to a
communication port. This is usually caused by another
application already having exclusive access to the port.
Range: INACTIVE, RUNNING
Pre-Tx Pre-Transmission Period
The time delay between asserting RTS to when the message
N00-324 R54 22
starts.
Note: CTS must be asserted for transmission to occur else
message is held until it is asserted.
Post-Tx Post-Transmission Period
The time after the last character is sent before RTS is negated.
Baud Communications Baud Rate
Range: 300, 600, 1200, 2400, 4800, 9600 or 192001 baud.
Factory default is 9600 Baud
CTS Usage
CTS Ignore If the modem does not support a Clear To Send (CTS) signal
and/or the cabling has no CTS wiring this parameter should be
set to CTS Ignore.
When set to this mode, the protocol asserts RTS as normal but
CTS Dont does not check for a returned CTS input signal.
Ignore If the modem supports a Clear To Send (CTS) signal this
parameter can be set to CTS Dont Ignore. When set to this
mode, the protocol will only transmit data when CTS is asserted.
Range: CTS Ignore, CTS Dont Ignore

Factory default is CTS Dont Ignore
PSTN Dial Up Number
Dialup Number The PSTN number that the protocol handler will call when it
needs to send an Unsolicited response. This field supports a
Dialling maximum of 18 digits.
DISABLED If this field is set to Dialling DISABLED then the protocol will not
try to dial the modem.
Factory is Dialling DISABLED with default number field blank
Pre-amble Preamble Usage
Determines whether the protocol transmits some preamble
characters prior to the start of a protocol message. The message
itself is not otherwise modified. Some modems require these
characters to assist with message reception and synchronisation
at the master station. Start of frame filtering at the master station
ENABLED ensures identification of the protocol message.
DISABLED ENABLED means that the preamble characters are transmitted
prior to a protocol message.
DISABLED means that protocol message are transmitted without
any preamble characters.
Range: ENABLED, DISABLED
Factory default is DISABLED
First Char Preamble First Character
This is the first character to be transmitted as a preamble. The
character is specified by entering its ASCII code in hexadecimal
format.
Range: is 0 to FF hexadecimal.
Factory default is 0x55
1
19200 baud is only available with CAPM5 controllers.
N00-324 R54 23
Repeat First Number of Preamble First Characters
This is the number of times the first character will be repeated as
part of the preamble.
Eg if all preamble settings are at default values then the
preamble sent is 0x55, 0x55, 0x55, 0xFF
Range: 0 to 20.
Last Char Last Preamble Character
This is the last char that will be sent as part of the preamble. The
format.
Factory default is 0xFF
DCD Usage
DCD Ignore If the modem does not support a Data Carrier Detect (DCD)
signal this parameter should be set to DCD Ignore.
Even if the modem does support a DCD signal this parameter is
usually set to DCD Ignore. This is because most point-point
systems using conventional modems run as full duplex so that
the DCD is always asserted during normal operation.
When set to this mode, the protocol uses any received data to
build an incoming packet irrespective of DCD input signal. Also
DCD Dont the protocol will transmit irrespective of the DCD input signal.
Ignore If the modem supports a Data Carrier Detect (DCD) signal this
parameter can be set to DCD Dont Ignore. When set to this
mode, the protocol will only read data and build an incoming
protocol packet when DCD is asserted. In addition, the protocol
will not transmit when DCD is asserted. This is necessary for
multi-dropped systems or ones shared with voice users or some
radio-modems.
Range: DCD Ignore, DCD Dont Ignore
Factory default is DCD Ignore
CA Delay Collision Avoidance Delay
On a multidrop communications link this parameter can be used
to provide priority access.
If the controller prepares to transmit and finds the link busy (DCD
asserted), it waits until it is no longer busy, then waits a back off
time as follows:
Back off time = CA Delay + ([random delay with range 0.0 to 1.0]
x CA Delay)
After the back off time the device tries again. If still unsuccessful
then the controller will continue in an indefinite loop until
successful.
If radio modems are used then Tx Delay must be configured to a
value slightly larger than the master stations post-transmission
time. This is necessary to ensure that the incoming messages
tail does not trigger back off operation.
If the DCD usage is configured to DCD Ignore then the back off
time is disabled.
Range: 0 to 180000 milliseconds
N00-324 R54 24
Tx Delay Transmission Delay
Additional time in milliseconds between receiving a request and
sending the response.
This field is used when the master station requires time to
disable its transmitter. If collision avoidance delay, CA Delay, is
configured then this field should be set to a value slightly greater
than the master stations post-transmission period.
5.2.4. Carrier Detect
When DCD Ignore is configured, the Data Carrier Detect (DCD) input is not used. All
data is received and transmitted irrespective of the state of the DCD signal.
When DCD Dont Ignore is configured, the controller will not begin to transmit a packet
until DCD is negated, and will only receive data when DCD is asserted. Refer to the DCD
Usage parameter description for more information.
When Dialup Number is configured, the DCD input is used exclusively by the dialling
modem and the DCD Ignore/Dont Ignore parameter is not used. Refer to section 5.2.7
for more information.
5.2.5. Transmitting a DNP3 Packet
Using default settings the controller transmission of a DNP3 packet follows the steps
below:
RTS line is asserted
Controller waits until the pre-transmission delay expires (Delay set from the panel)
and checks that CTS has been asserted.
The pre-amble is transmitted (Optional. Set from the panel).
Checks CTS is still asserted.
The DNP3 packet is transmitted
Waits until the post-transmission delay expires (Delay set from the panel)
RTS is negated
If CTS Ignore is set then the above CTS assertion checks are skipped.
5.2.6. DTR
DTR is asserted by the protocol handler at power-up or upon P8 selection.
5.2.7. Dialling Modem Support
The controller can support a Hayes compatible modem with dialling / auto answer
capability on port P8 for remote dial up access using DNP3. The protocol uses dialling
modem support mode if the dialling field is DNP Communications 2 shows a telephone
number. If modem is active then the DCD Ignore parameter is ignored. The protocol
handler uses the state of the DCD input from the modem to determine the modems
status. If DCD is asserted the modem is online. If DCD is negated the modem is
considered offline.
The modem must be setup to auto answer any call. It should not return results codes nor
echo commands.
When the modem is online (DCD asserted) the protocol will examine the data being
received and decode it as DNP3 packets.
When the protocol needs to transmit data it will first check if the modem is currently online.
If the modem is online the protocol will send the data immediately. If the modem is offline
the protocol will first dial to the master station.
N00-324 R54 25
To connect to the master station the protocol handler sends ATDT and then the phone
number setup on the status page above to the modem. The protocol handler will then wait
up to 90 seconds for the modem to assert the DCD line. If the modem fails to assert the
DCD line within 90 seconds the current packet will be discarded. The protocol handler will
try to connect again when the Unsolicited retry timer expires.
The protocol handler will hang up the modem after a delay of 30 seconds with no valid
packet received or transmitted. To hang up the modem the protocol handler will:-
Wait 1 second
Send +++
Wait 1 second
And then send ATH
Wait 5 second
The protocol handler will then check to ensure the modem has negated the DCD line.
If this sequence fails to disconnect the line the protocol handler will turn the radio power
supply off (AUX+) for 1 minute to disconnect power from the modem and reset it.
5.2.8. PAKNET Configuration
required for X.25 based communications between the recloser and the master station. In
this configuration, the controllers interface to the X.25 network is via a PAKNET Radio
PAD. The PAKNET PADs conform to a subset of the V.24 and X.28 standards.
Users should consult the PADs Configuration Guide to ensure that its parameters are
configured in a manner that is compatible with the controller.
The following screens are only visible if P8 PAKNET or P8 PAKNET SS is the selected
port.
X.25 Connection Parameters
-------- DNP PAKNET Settings -------

DTR Low Time 500ms Tx on line 5s
NUA Address 0
DTR Low Time
DTR Low Time The time that DTR is held low in order to clear a call
Range: 10 to 5000 ms
NUA Address PAKNET NUA Address
PAKNET NUA Address for dialing. Supports both short and long
address schemes.
Range: 0 to 99999999999999
Tx on line Tx on line Time
The time the call is maintained after the last character is
transmitted. The call is cleared by lowering DTR for a period of
time specified by the DTR Low Time parameter. Calls are only
cleared by the controller if it initiated the call.
Range: 0 to 120 seconds.
N00-324 R54 26
Factory default is 5 seconds
Communications Retry Parameters
----- DNP PAKNET Call-Out Timers ----

Min Retry 60s Max Retry 3600s
Multiplier X 2
Timeout 12s
Minimum Retry Time
Min Retry The initial time between retries if a call-out sequence to the master
station fails.
Max Retry Maximum Retry Time
The maximum time allowed between retries if call-out sequences
to the master station continue to fail.
Multiplier Retry Multiplier
The factor by which the current retry interval is multiplied to obtain
the new retry interval. For example if the multiplier is set to 2 and
the retry interval is initially set to 60 then the second retry will
occur after 120 seconds, the third after 240 seconds etc until the
Max Retry Interval is reached.
Range: 1 to 10
Timeout Retry Timeout
The number of seconds remaining before the retry timer expires.
Note: P8 PAKNET assumes immediate low level connection, so
this low-level timeout is unlikely to be used. Higher level DNP
timeouts come into play if there is not a valid P8 PAKNET
connection (eg.DL Cf To).
The delay between retry countdowns is due to multiples of 5sec
waits and DTR low times.
(Display only).
5.3. V23 FSK Communication Specifications

5.3.1. V23 Hardware Signals
Standard Cable P10 Pin Direction Use

Type N03-530
15 Way D Female
5 5 - Signal Ground
N00-324 R54 27
4 4 To controller Receive, 10kOhm impedance

Sensitivity 0.1V to 2V pk-pk
15 15 From controller Press To Talk (PTT)
11 11 From controller Transmit(Tx), 600 Ohm impedance
Level 2.5V pk-pk
6 6 To controller Busy, 10kOhm impedance
Signal frequencies conform to V23 standard.

The protocol only supports half duplex (ie receive and transmit can not occur at the same
time) when using the V23 port.
Baud rate is fixed at 1200 Baud.
5.3.2. V23 Configuration Parameters
required for operation of the physical link between the recloser and the master station.

P10 V23 FSK RUNNING
Pre-Tx 250ms Post-Tx 35ms
Busy Sense LOW

Tx NORMAL Rx IDLE
Pre-amble DISABLED First Char 0x55
Repeat First 3 Last Char 0xFF

DCD Dont Ignore CA Delay 1000ms
Tx Delay 0ms
Port Selection
This field selects the communications medium the DNP3
protocol handler uses for transmission.
OFF When OFF is selected, the protocol handler is disabled.
P8 RS-232 When P8 RS 232 is selected, the protocol uses the P8 serial

port for all data. Also, the DNP Communications 1 and 2 pages
are automatically updated to reflect relevant RS-232 data. Refer
to section 5.2 for the P8 configuration details.
P8 PAKNET
When P8 PAKNET is selected, the protocol handler uses the P8
N00-324 R54 28
serial port to communicate through an X.25 network via a
PAKNET Pad without using the Service Signals. Refer to
section 5.2 for the P8 configuration details.
P8 PAKNET SS
When P8 PAKNET SS is selected, the protocol handler uses the
P8 serial port to communicate through an X.25 network via a
PAKNET Pad using the Service Signals. Refer to section 5.2 for
P10 V23 FSK the P8 configuration details.
When P10 V23 FSK is selected, the protocol uses the built in
V23 modem on P10. Also, the DNP Communications 1 and 2
pages are automatically updated to reflect relevant FSK data as
detailed below.
Range: OFF, P8 RS-232, P8 PAKNET, P8 PAKNET SS,
P10 V23 FSK
Factory default is P8 RS-232
Protocol Status
Indication of the current status of the communications. (Display
only)
RUNNING RUNNING means that the protocol handler has connected to
the communication port (P8 or P10) and is running.
INACTIVE INACTIVE means that the protocol handler has been disabled
via the OFF state above or has been unable to connect to a
communication port. This is usually caused by another
application already having exclusive access to the port.
Range: INACTIVE, RUNNING
Pre-Tx Pre-Transmission Period
The time delay between keying PTT to when the data is
transmitted.
During this period the carrier is transmitted on the Tx line.
Post-Tx Post-Transmission Period
The time after the last character is sent before PTT is negated.
During this period the carrier is transmitted on the Tx line.
Busy Sense Polarity of Busy Signal
This field determines the polarity of the input signal from the
radio (P10 pin 6) that the controller uses as BUSY.
LOW LOW means that a low input signal will assert BUSY.
HIGH HIGH means that a high input signal will assert BUSY.
Range: LOW, HIGH
Factory default is Busy Sense LOW.
Transmission Mode
This field can be used to test the radio transmitter.
Tx NORMAL Tx NORMAL means that the protocol handler controls the radio
for normal DNP3 transmissions.
Tx TEST Tx TEST means that the protocol handler will send continuous
text strings of TX TEST. This string is transmitted as an
asynchronous message with 8 bit, no parity, 1 stop bit, 1 start bit
format.
N00-324 R54 29
Range: Tx NORMAL, Tx TEST
Factory default is Tx NORMAL.
BUSY Signal Status
The status of the BUSY signal into the controller (Display only)
Rx IDLE, Rx IDLE indicates that the signal is in the not BUSY state.
Rx BUSY Rx BUSY Asserted indicates that the signal is in the BUSY
state. This usually means that the radio squelch has opened.
Range: Rx IDLE, Rx BUSY
Pre-amble Preamble Usage
ENABLED When ENABLED the protocol handler inserts a string of
characters in front of a message packet. The message frame is
otherwise not affected. Start of frame filtering at the master
station will ensure identification of the message. This parameter
DISABLED is sometimes required for modems to aid with their keying.
When DISABLED the protocol handler does not insert any
preamble characters.
Range: ENABLED, DISABLED
Factory default is DISABLED
First Char Preamble First Character
This is the first character to be transmitted as a preamble. The
format.
Factory default is 0x55
Repeat First Number of Preamble First Characters
This is the number of times the first character will be repeated
as part of the preamble.
Eg if all preamble settings are at default values then the
preamble sent is 0x55, 0x55, 0x55, 0xFF
Range: 0 to 20.
Last Char Last Character of Preamble
This is the last char that will be sent as part of the preamble.
The character is specified by entering its ASCII code in
hexadecimal format.
Factory default is 0xFF
DCD Usage
DCD Ignore The DCD Ignore mode is used when there is no busy signal
available. eg A twisted pair link. To operate in this mode the
Busy Sense needs to be set to HIGH so that the receiver is
busy at all times. When set to this mode, the protocol uses any
DCD Dont Ignore received data to build a DNP3 packet. The protocol is able to
transmit at any time.
The DCD Dont Ignore mode is the normal operating mode for
radio systems that have a busy signal available. When set to
this mode, the protocol will only read data and build a DNP3
packet when busy is asserted. Also, the protocol will not
transmit when busy is asserted. This reduces clashes with voice
users.
Factory default is DCD Dont Ignore
CA Delay Collision Avoidance Delay
N00-324 R54 30
On a multidrop communications link this parameter can be used
to provide priority access.
If the controller prepares to transmit and finds the link busy
(DCD asserted), it waits until it is no longer busy, then waits a
back off time as follows:
Back off time = CA Delay + ([random delay with range 0.0 to

1.0] x CA Delay)
After the back off time the device tries again. If still unsuccessful
then the controller will continue in an indefinite loop until
successful.
If radio modems are used then Tx Delay must be configured to a
value slightly larger than the master stations post-transmission
time. This is necessary to ensure that the incoming messages
tail does not trigger back off operation.
If the DCD usage is configured to DCD Ignore then the back off
time is disabled.
Range: 0 to 180000 milliseconds
Tx Delay Transmission Delay
Additional time in milliseconds between receiving a request and
sending the response.
This field is used when the master station requires time to
disable its transmitter. If collision avoidance delay, CA Delay, is
configured then this field should be set to a value slightly greater
than the master stations post-transmission period.
5.3.3. V23 Handshaking Signals

The protocol can operate in two separate modes depending on the state of the DCD
Ignore flag.
DCD Dont Ignore
When the BUSY line gets asserted, the controller will scan for a valid DNP3 packet. When
BUSY gets negated, then the Rx data is no longer read.
The sensing of the BUSY line can be setup on the controller panel to be Busy Sense
LOW or Busy Sense HIGH.
The controller checks the status of the BUSY line before transmission. If the BUSY line is
negated the CAPM is free to transmit.
The controller then asserts the PTT line before it begins transmission. The controller waits
until the pre-transmission timer expires, then waits for the optional pre-amble to be
transmitted, then immediately begins transmission. After transmission, the protocol waits
for the post-transmission timer to expire, and then negates PTT.
DCD Ignore
The protocol receives any characters coming in on the RX line and attempts to decode
these as DNP3 packets.
The controller is free to transmit at any time.
The controller then asserts the PTT line before it begins transmission. The controller waits
until the pre-transmission timer expires, waits for the optional pre-amble to be transmitted,
N00-324 R54 31
begins transmission. After transmission, the protocol waits for the post-transmission timer
to expire, and then negates PTT.
5.4. Communication Statistics
The communication statistics give communication information, such as octets not being
sent, received or processed or frames being incorrectly addressed. The communication
statistics page appears as below:
---- DNP Communication Statistics ---S

Tx Count 946 Rx Count 582
Rx Length Error 0 Rx CRC Error 0
Statistic Description
Tx Count Transmission Message Count
The number of DNP3 datalink messages transmitted from this
controller into the DNP3 link.
Range: 0 to 32768
Rx Count Receive Message Count
The number of DNP3 datalink messages received by this
controller from the DNP3 link.
Range: 0 to 32768
Rx Length Error Receive Message Length Error Count
The number of message packets received with a length error
Range: 0 to 999
Rx CRC Error Receive Message CRC Error Count
The number of message packets received with a CRC error
Range: 0 to 999
All of the above counters are zeroed when: the controller is reset; a DNP3 cold or warm
restart message is received; or a configuration parameter is changed that triggers a DNP3
handler warm restart; or the reset all button is selected in Windows SOS.
Any field can be cleared via the operator control panel by selecting it and pressing either
the left or right keys.
All communication statistic parameters are not password protected.
N00-324 R54 32
Appendix A Protocol Timings

Initialisation Time
The protocol handler will not respond to master station requests for about 10 seconds
after power up whilst it waits for the controller database to be initialised and for high
priority boot up tasks to be completed.
Turnaround Time
The turnaround time for the protocol, from the end of receiving a message until the start of
the pre-transmission time, is typically < 40 milliseconds with a range of 5 to 100
milliseconds.
Latency of Data
The protocol task examines the real-time database every 500 ms to see if anything has
changed and to construct the underlying protocol database which is sent to the master
station. This introduces a delay between the actual event and updating the protocol
database of up to 500 milliseconds. This is the data latency.
Accuracy of Time Tags
For points tagged to 500 milliseconds accuracy, the time tag accuracy is 10 / + 500 ms
relative to controller processor clock.
For points tagged to 10 millisecond accuracy, the points correspond to those in the
operator panel event record.
N00-324 R54 33
Appendix B DNP3 Device Profile

The controller implementation complies with the DNP3 Subset Definitions document.
Additional implementation information is given in this section.
The DNP3 device profile defines the mapping of all data points used, in the standard
format recommended by the DNP3 users group.
N00-324 R54 34
DNP3 Device Profile
DNP3 Device Profile
Vendor Name: Device Name: CAPM-4/5 Controller

Schneider Electric (Australia) Pty Limited,
Brisbane, Australia
Highest DNP3 Level Supported

For Requests: 2 Device Function: Slave
For Responses: 2
Conforms to DNP3 level 2 subset definition requirements with many additional level 3 features built
in. Refer to the shaded areas of Appendix C DNP3 Implementation Table, for additional level 3
features built in.
Also, the following functions are included:

Function codes 7, 8, 9, 10 for Binary Counters (Object 20 Variation 6)
Function code 14 - Warm Restart
Function code 20 - Enable Unsolicited Messages
Function code 21 - Disable Unsolicited Messages
Function code 22 - Assign Data Classes
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted: 292 Transmitted: Configurable (50 to 2048)
Received: 292 Received: 249
Maximum Data Link Retries: Maximum Application Layer Retries:
Configurable 0..255 None
Requires Data Link Layer Confirmation:
Configurable, 3 settings Never, Always, Sometimes (on multi frame fragments only)
Requires Application Layer Confirmation:
Sometimes (only when reporting event data or when sending multifragment responses)
Timeouts while waiting for:

Data Link Confirm: Configurable
Application Confirm: Configurable
Need Time Delay: Configurable (on power up, an additional device start up
delay applies. Refer to appendix A).
Select Operate Delay: Configurable
Unsolicited Response Notification: Configurable
Unsolicited Response Retry Delay: Configurable
Timeouts not supported:
Complete Appl. Fragment: None
Complete Appl Response: None
N00-324 R54 35
Executes Control Operations:

WRITE Binary Outputs: Never
SELECT/OPERATE:
Always Count > 1: Never
DIRECT OPERATE: Pulse On: Always
Always Pulse Off: Always (Legacy
DIRECT OPERATE - NO ACK: support)
Always Latch On: Always
Max number of controls that can operate Latch Off: Always
simultaneously: 1 Trip/Close: Sometimes
Pattern control operations are not Raise/Lower: Never
supported Queue: Never
Clear Queue: Never
Pulse On and Pulse Off times are

WRITE Analogue Outputs: ignored
Never
SELECT/OPERATE:
Always
DIRECT OPERATE:
Always
DIRECT OPERATE - NO ACK:
Always
Max number of outputs that can operate
simultaneously: 1
Maximum Select/Operate Delay
Time:
Configurable 1 .. 65535 ms
Reports Binary Input Change Events Reports time tagged Binary Input
when no specific variation requested: Change Events when no specific
Configurable with / without time variation requested:
Binary Input Change with Time
Sends Unsolicited Responses: Static Data in Unsolicited Responses:
Enable/Disable Unsolicited supported Never
Supports Collision Avoidance: Collision Avoidance Detection Method:
Configurable DCD
Default Counter Object: Counter Roll Over at:
Default Object: 20 65535
Default Variation: 06
Sends Multi-Fragment Responses: Yes
N00-324 R54 36
Appendix C DNP3 Implementation Table
CAPM DNP3 Implementation Table

OBJECT REQUEST RESPONSE
(slave must parse) (master must parse)
Obj Var Description Func Codes Qual Codes Func Qual Codes
(dec) (hex) Codes (hex)
1 0 Binary Input - All Variations 1 22 00, 01 06 N/A N/A
07, 08, 17, 28
1 1 Binary Input 1, 22 00, 01, 06, 129 00, 01

07, 08, 17, 28
17, 28 Note 4
1 2 Binary Input With Status 1, 22 00, 01, 06, 129 00, 01
07, 08,
17, 28
17, 28
Note 4
2 0 Binary Input Change - Default 1 06, 07, 08 N/A N/A
2 1 Binary Input Change without Time 1 06, 07, 08 129, 130 17, 28
2 2 Binary Input Change with Time 1 06, 07, 08 129, 130 17, 28
2 3 Binary Input Change with Relative 1 06, 07, 08 N/A N/A
Time
10 0 Binary Output - All Variations 1 00, 01 06 N/A N/A
07, 08, 17, 28
10 2 Binary Output Status 1 00, 01, 06, 129 00, 01
07, 08, 17, 28
17, 28 Note 4
12 1 Control Relay Output Block 3, 4, 5, 6 00, 01, 07, 08 129 Echo of
17, 28 request
20 0 Binary counter Default 1, 7, 8, 9, 10 00, 01 06 N/A N/A
07, 08, 17, 28
20 1 32 Bit Binary Counter with flag 1, 7, 8, 9, 10 00, 01, 06, 129 00, 01
07, 08, 17, 28
17, 28 Note 4
20 2 16 Bit Binary Counter with flag 1, 7, 8, 9, 10 00, 01, 06, 129 00, 01
07, 08, 17, 28
17, 28 Note 4
20 5 32 Bit Binary Counter without flag 1, 7, 8, 9, 10 00, 01, 06, 129 00, 01
07, 08, 17, 28
17, 28 Note 4
20 6 16 Bit Binary Counter without flag 1, 7, 8, 9, 10 00, 01, 06, 129 00, 01
07, 08, 17, 28
17, 28 Note 4
21 0 Frozen Counter Default 1 00, 01 06 N/A N/A
07, 08, 17, 28
21 1 32 Bit Frozen Counter with flag 1 00, 01, 06, 129 00, 01
07, 08,
17, 28
17, 28
Note 4
21 2 16 Bit Frozen Counter with flag 1 00, 01, 06. 129 00, 01
N00-324 R54 37

07, 08, 17, 28
17, 28 Note 4
21 9 32 Bit Frozen Counter without flag 1 00, 01, 06. 129 00, 01
07, 08, 17, 28
17, 28 Note 4
21 10 16 Bit Frozen Counter without flag 1 00, 01, 06. 129 00, 01
07, 08, 17, 28
17, 28 Note 4
30 0 Analogue Input - Default 1 22 00, 01 06 N/A N/A
07, 08, 17, 28
30 1 32 Bit Analogue Input 1, 22 00, 01, 06, 129 00, 01
07, 08,
17, 28
17, 28
Note 4
30 2 16 Bit Analogue Input 1, 22 00, 01, 06, 129 00, 01
07, 08,
17, 28
17, 28
Note 4
30 3 32 Bit Analogue Input without 1, 22 00, 01, 06, 129 00, 01
Flag 07, 08,
17, 28
17, 28
Note 4
30 4 16 Bit Analogue Input without 1, 22 00, 01, 06, 129 00, 01
Flag 07, 08,
17, 28
17, 28
Note 4
32 0 Analogue Change Event - Default 1 06, 07, 08 N/A N/A
32 1 32 Bit Analogue Change Event 1 06, 07, 08 129, 130 17, 28
without Time
without Time
with Time
with Time
34 0 Analogue Input Reporting 1 00, 01, 06, N/A N/A
Deadband Default 07, 08,
Note 6 17, 28
34 1 16 bit Analogue Input Deadband 1 00, 01, 06, 129, 130 17, 28
reporting 07, 08,
Note 6 17, 28
2 00, 01,
07, 08,
17, 28
34 2 32 bit Analogue Input Deadband 1 00, 01, 06, 129, 130 17, 28
reporting 07, 08,
Note 6 17, 28
2 00, 01,
07, 08,
17, 28
40 0 Analogue Output Status - Default 1 00, 01 06 N/A N/A
N00-324 R54 38

07, 08, 17, 28
40 1 32 Bit Analogue Output Status 1 00, 01, 06, 129 00, 01
07, 08, 17, 28
17, 28 Note 4
40 2 16 Bit Analogue Output Status 1 00, 01, 06, 129 00, 01
07, 08,
17, 28
17, 28
Note 4
41 1 32 Bit Analogue Output Block 3, 4, 5, 6 00, 01, 07, 08, 129 Echo of
17, 28 request
41 2 16 Bit Analogue OutputBlock 3, 4, 5, 6 00, 01, 07, 08, 129 Echo of
17, 28 request
50 0 Time and Date 1 00, 01, 06 129 00, 01
07, 08, 17, 28
17, 28, Note 4
50 1 Time and Date 1 00, 01, 06 129 00, 01
08, 17, 28 17, 28
07 Note 4
(quantity = 1)
2 00, 01, 06
08, 17, 28,
07
(quantity = 1)
52 2 Time Delay Fine N/A N/A 129 07,
(quantity 1)
60 0 Class 0, 1, 2, and 3 Data 1, 20, 21 06
60 1 Class 0 Data 1 06 N/A N/A
20, 21
60 2 Class 1 Data 1 06, 07, 08 N/A N/A
20, 21 06
60 3 Class 2 Data 1 06, 07, 08 N/A N/A
20, 21 06
60 4 Class 3 Data 1 06, 07, 08 N/A N/A
20, 21 06
80 1 Internal Indications 2 00 index = 7 N/A N/A
112 Virtual Terminal Output Block 2 00, 01, 07, N/A N/A
Note 5 08, 17, 28
113 Virtual Terminal Event Data 1 06, 07, 08 129 17, 28
No Object 13 14 23 N/A N/A N/A
Note
All shaded areas are the additional level 3 or above function, objects, variations and/or qualifiers supported by
controller.
Bold italics response function codes represent controller default objects. These are the object variations that
the controller will issue as in its response to an event (class 1, 2, 3) poll, an integrity (class 1, 2, 3, 0) poll, in a
response to a variation 0 read request, or in an unsolicited response message. Where more than one data
object variation is highlighted then default object can be configured. Selection of default objects is explained in
section 4.3.
All Request and Response options marked N/A are Not Applicable.
N00-324 R54 39
For static (non-change-event) objects, qualifiers 17 or 28 are only responded when a request is sent with
qualifiers 17 or 28, respectively. Otherwise, static object requests sent with qualifiers 00, 01, 06, 07, or 08, will
be responded with qualifiers 00 or 01. (For change-event objects, qualifiers 17 or 28 are always responded.)
The Virtual Terminal Objects (112 and 113) are used to transport SOS data between WSOS and the controller.
No other data is supported.
A write with an analogue input deadband value of zero will be rejected. The response will have the parameter
in qualifier, range or data field not valid or out of range internal indicator bit (IIN2-2) set.
DNP3 Function Codes

Request Response
Function Description Function Description Function Description
Code Code Code
1 Read 9 Freeze and Clear 129 Response
2 Write 10 Freeze and Clear, No 130 Unsolicited
Ack Response
3 Select 13 Cold Restart (Note 1)
4 Operate 14 Warm Restart (Note 1)
5 Direct Operate 20 Enable Unsolicited Msgs
6 Direct Operate, No Ack 21 Disable Unsolicited Msgs
7 Immediate Freeze 22 Assign Class
8 Immediate Freeze, No 23 Delay Measurement
Ack
Note
When a cold or warm restart command is received by the controller it will restart the DNP3 protocol handler
only. The CAPM itself does not restart.
It is recommended by the DNP3 User Group that master stations do not ask for a data link acknowledgement
nor an application confirm on restart commands (refer to Cold/Warm Restart Sequence, Technical Bulletin
9701-003)
The controller reports a time object of 500ms for both restart types. The master station should not initiate any
message sequences for this period. However, if the controller has unsolicited messages configured ON then it
will automatically establish communications on restart. This may be within the 500ms period.
DNP3 Qualifiers
Qualifier Use in a Request Use in a Response
(Hex)
00, 01 A range of static points, or a single point with a Static Objects
point number.
Object headers use either 8 bit (Q=00) or 16 bit
(Q=01) start and stop range indices.
06 All points. Not valid
Object headers and data sizes are determined
by controller configured parameters.
07, 08 A limited quantity of events or a single point A single point with no number (eg Time and
with no number (eg Time and Date). Date)
Object headers have either 8 bit quantity fields
(Q=07) or 16 bit quantity fields (Q=08).
17, 28 Controls (usually one or more unrelated points) Event objects (usually one or more unrelated
Object headers have either 8 bit quantity field points)
with 8 bit indices (Q=17) or 16 bit quantity field
with 16 bit indices (Q=28)
DNP3 Internal Indication Bits

The following DNP3 response internal indication bits are not supported.
N00-324 R54 40
IIN1-6 Device trouble. For system health status refer to the Abnormal Operator Conditions binary input point
that is described in Error! Reference source not found..
IIN2-4 Request already executing.
IIN2-5 Corrupt Configuration
DNP3 Object Status Flags

Binary Inputs.
Only the on-line and status bits are supported. This means that, depending upon the points status, the
reported flag will always be either 0x01 or 0x81 since the controller always regards its points as on-line.
Binary Outputs.
Only the on-line and status bits are supported. Refer to the relevant binary output appendix for on/offline
condition information.
Analogue Inputs
Only the on-line and over-range bits are supported. Since the controller always regards its points as on-line,
the flag will always be reported as either 0x01 or 0x21.
DNP3 Control Operation

The success or failure of control operation is returned in the control response message. The controller support for
control success is shown below.
Response
Controller Control Response Description
Status Value
0 Control request accepted
1 Control request denied. Select/Operate timed out. The time out parameter is configurable.
2 Control request denied. Operate without select message OR operate/select application sequence
number mis-match.
3 Control request denied. Formatting error
4 Control request denied. Control operation not supported
Examples:
Trip control sent to a point that supports only Pulse or Latch operations. The supported operations
are indicated on a per point basis in the table in Appendix H or Appendix N.
The binary output (or analogue output) point number is out of range.
The analogue output value is out of range.
5 Control request denied. Already Active
6 Control request denied. Hardware Error.
7 Control request denied. Control rejected by controller because set to Local Control on.
The outputs affected by Local Control are controlled by Output Control (See Database
Parameters).
8 Control request denied. Control rejected by controller because too many operations have been
requested.
9 Control request denied. Control rejected by controller because of an underlying condition
preventing the action. These conditions are indicated on a per point basis in the table in Appendix
H or Appendix N.
127 Control request denied. Control rejected by controller because of some other undefined reason.
All binary output points have a matching binary input status point. The master station must
always use the corresponding binary status for the control to verify the success of the
action.
DNP3 Technical Bulletins
Technica Description Manual Comment

l Bulletin Version
2001-001 Multiple Control Objects and N00-324R41
N00-324 R54 41
Status Codes
2000-006 Control Relay Output Block Control N00-324R41
Codes
2000-005 Reset of User Process Function N00-324R41 Note 3
Codes
2000-004 Application Layer Confirmation N00-324R41
Messages
2000-003 Change Management - Note 1
2000-002 Control Retries N00-324R28
2000-001 Sequential File Transfer Objects - Not Applicable. Note 2
9912-003 Broadcast Message Confirmation N00-324R33
and Address Reservation
9912-002 Unsolicited Event Reporting; Retry N00-324R28
Configuration
9905-001 Qualifier Code 11 - Not Applicable. Note 2
9809-001 Analogue Input Reporting N00-324R28
Deadband
9804-008 Unissued Object and Variation N00-324R20
Numbers
9804-007 Clarification of Collision Avoidance N00-324R28
Procedure
9804-006 Analogue Object Floating Point - Not Applicable. Note 2
Variations
9804-005 8 Bit Unsigned Integer Object 102 - Not Applicable. Note 2
9804-004 Virtual Terminal Objects 112 and N00-324R27
113
9804-003 Recommended Layer Terminology N00-324R20
9804-002 DNP3 Confirmation and Retry N00-324R20
Guidelines
9804-001 Rules for Synchronising N00-324R20
Application Sequence Numbers
9704-007 Implementation for Reset Link N00-324R20
Frames
9701-006 Extension of Engineering Units for - Not Applicable. Note 2
Floating Point Objects
9701-004 Octet String Objects 110 and 111 - Not Applicable. Note 2
9701-003 Cold/Warm Restart Sequence N00-324R20
9701-002 Control Relay Output Block N00-324R20
Minimum Implementation
9701-001 Datalink Restart Recovery N00-324R20
Note:
It is Schneider Electric (Australia) Pty Limited policy that all technical bulletin rules that are
required for the controller to be DNP3 level 2 compliant are implemented.
The following data types are not used by the controller:-
File transfer objects
String objects
Analogue input floating point and analogue output floating point objects
Variable arrays objects
8 bit unsigned integer objects
N00-324 R54 42
The Reset User Process(1) function code should not be used. If the Reset User
Process(1) function code is used in the Control byte, then the response function code will
be Link Not Used(15).
N00-324 R54 43
DNP3 Protocol Technical Manual (ACR)
Appendix DACR - Binary Input Points (Status)

NOTE: This set is frozen in CAPM software version 27-17.00.
This is the default map in CAPM software version 28 onwards. Refer to the
Configurable DNP3 Tool Manual (N00-718) for more information.
Time resolution is as shown. Refer to Appendix A for more information on timing.

W series support is indicated below by a Y. If indicated as N then value is always OFF.
The phase designation A, B, C is determined by the user, refer to the equipment manual
Phase and terminal terminology is explained in section 3.4.
DNP3 Implementation
Static: Object 01 Variation 01 Single Bit Binary Input
Event: Configurable refer to section 4.3
Request Function Code: 01 Read
ACR Binary Input Points (Status)
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
0 Abnormal Y 1 For any of the None of the This flag shows that the
Operator following conditions:- specified conditions operator has the ACR in an
Settings Trip or Close are true. abnormal state such as work
Isolated, tag applied. This means that it
will operate differently to its
ACR
normal mode of operation.
Mechanically
locked open (if 500ms
applicable)
Work Tag
Applied
1 ACR Tripped Y 1 ACR Tripped ACR not Tripped These are repeats of the
(open) mechanism travel switches.
2 ACR Closed Y 1 ACR Closed ACR not Closed When the ACR is disconnected
from the control cubicle they are
both cleared.
500ms
3 Controller Y 2 LOCAL control LOCAL Control The controller is either in
Mode Disabled Enabled LOCAL or Remote Controller
Remote control Remote Control Mode. This affects the closing
Enabled Disabled command the permission to
set/remove work tag.
500ms
4 Maintenance Y 1 For any of the No maintenance The controller has detected one
Required following conditions:- required or more conditions which
Battery not require maintenance.
normal This point cannot become Set
Capacitor charge until at least five minutes after
failure controller start.
Low power mode 500ms
SF6 gas
pressure Low or
Invalid (if
N00-324 R54 44
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
applicable)
ACR data not
valid (includes
connection to an
invalid switch
type)
Any vacuum
interrupter
contact life is
less than 20%
Mechanical
failure
5 Work Tag Y 2 Work Tag Applied Work Tag Removed The controller can have a work
tag. This affects the closing
command
500ms
6 Prot A Active Y 2 Protection Group A is Protection Group A is not
active active
7 Prot B Active Y 2 Protection Group B is Protection Group B is not
active active
8 Prot C Active Y 2 Protection Group C is Protection Group C is not Only one protection group is
active active active at any one time.
9 Prot D Active Y 2 Protection Group D is Protection Group D is not
active active
10 Prot E Active Y 2 Protection Group E is Protection Group E is not 500ms
active active
11 Prot F Active Y 2 Protection Group F is Protection Group F is not
active active
12 Prot G Active Y 2 Protection Group G is Protection Group G is
active not active
13 Prot H Active Y 2 Protection Group H is Protection Group H is not
active active
14 Prot I Active Y 2 Protection Group I is Protection Group I is not
active active
15 Prot J Active Y 2 Protection Group J is Protection Group J is not
active active
16 Earth / Ground N 2 Earth / Ground Earth / Ground 500ms
Protection Protection ON Protection OFF
Enabled
17 SEF/SGF N 2 SEF/SGF protection SEF/SGF protection 500ms
Protection ON OFF
Enabled
18 Auto Reclose Y 2 Auto Reclose ON Auto Reclose OFF 500ms
19 Cold Load Idle Y 2 Cold Load is Idle or is Cold load is NOT Idle. 500ms
turned off. This means that the
This means that the threshold multiplier is
threshold multiplier is being raised by the cold
not being affected by load pickup function in
the cold load order to pick up cold
function. load.
N00-324 R54 45
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
20 High Current Y 2 High Current Lockout High Current Lockout 500ms
Lockout Protection ON Protection OFF
21 Loss of Phase N 2 Loss of Phase Loss of Phase Protection 500ms
Protection Protection ON OFF
22 Sequence Y 2 Sequence Control Sequence Control OFF 500ms
Control ON
23 Live Load Y 2 Live Load blocking Live Load blocking OFF 500ms
blocking ON
24 Protection Y 2 Protection Enabled Protection turned OFF 500ms
enable
25 Switchgear Y 3 Set for Load Break Clear For Recloser
Family Switch 500ms
26 Power Flow Y 2 Source X, Load I Source I, Load X The power flow direction
Direction (source/load designation) is
(Source and determined by the user. Refer
Load to the Power Flow Direction
Bushings) binary output for more
Note 2 information
500ms
Protection Trip Operation Flags
This group of points indicates what happened in the last protection sequence. For example the
recloser may have tripped, closed, tripped again and locked out. Or it may have tripped, closed
and stayed closed because the fault was cleared.
In both cases the flags below are set to show the causes of the trips and whether the lockout
state has been reached or not.
A set of flags is available for each trip in a protection sequence.
In addition analogue data is available which shows the fault currents which occurred during the
sequence and the number of trips which took place (refer Appendix F)
Note that a sequence starts when there is a protection trip or a sequence advance.
Most of these flags are cleared either by protocol command or when the switchgear is
tripped/closed by the operator or when a new protection sequence starts.
This data is volatile i.e. it is zeroed on controller software reset.
General Protection Flags
27 Sequence in Y 1 Start of sequence This shows that a protection
Progress That is a protection sequence has started and not
trip or sequence yet completed.
advance has End of sequence. Either Note that operator trip does not
occurred. lockout or reclaim. cause a sequence in progress.
Event time is the time of the trip
or sequence advance.
10ms
N00-324 R54 46
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
28 Protection Y 1 End of sequence, All fault flags are cleared This shows that the protection
Data Valid either lockout or by one of the following sequence is over and the other
reclaim actions :- flags are set.
Reset Fault Flags This could be used to drive an
and Currents operator alarm at the SCADA
protocol control system to alert him to the fact
command that a protection sequence has
Any Operator Close occurred. Note that operator trip
action alone does not cause a
Controller software protection data valid
reset (data is Event time is the time of lockout
volatile) or reclaim.
At the time of the
next trip the flags 10ms
29 Single Shot Y 1 Single Shot are refreshed atOne flag only provided because
Protection Protection was active this time old flags
a single shot trip forces lockout.
at the time of the trip. are cleared and the
Event time is the time of the
cause of the mostpickup.
recent protection 10ms
operation set.
30 Loss Of Phase Y 1 Trip was caused by One flag only provided because
Trip Loss of Phase Protection turned LOP protection forces lockout.
Protection OFF
Event time is the time of the trip.
10ms
31 Loss Of Phase Y 1 Phase A was lost at Set if A Phase is lost at time of
- Phase A time of Loss of Phase Loss of Phase trip
trip 10ms
32 Loss Of Phase N 1 Phase B was lost at Set if B Phase is lost at time of
- Phase B time of Loss of Phase Loss of Phase trip
trip 10ms
33 Loss Of Phase N 1 Phase C was lost at Set if C Phase is lost at time of
-Phase C time of Loss of Phase Loss of Phase trip
trip 10ms
34 High Current Y 1 All fault flags are cleared One flag only because High
Lockout by one of the following Current Lockout forces lockout
actions :- Time stamp as for flags above.
Reset Fault Flags Event time is the time of the
and Currents lockout event.
The high current
lockout function protocol control 10ms
forced the controller command
to lockout during the Any Operator Close
last protection action
sequence Controller software
reset (data is
volatile)
Start of a new
sequence
35 Lockout Y 1 The controller is in Cleared by: This flag shows that the
lockout Any close action controller is in lockout.
Reset fault flags Therefore no auto-reclosing will
and currents take place.
N00-324 R54 47
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
protocol command If the ACR is closed this flag will
be clear. Therefore when this
flag is clear and the ACR is
closed it indicates that the
protection sequence cleared the
fault. Event time is the time of
the trip
10ms
36 Operator Trip Y 1 The most recent trip Cleared by any close One flag only because operator
was caused by a action trip forces lockout.
local or remote
Event time is the time of the trip
operator (eg IOEX,
Protocol, or panel) 10ms
Protection Trip 1
37 Phase Over Y 0 Trip was caused by All fault flags are cleared
Current Trip Phase Overcurrent by one of the following
Protection actions :-
Reset Fault Flags 10ms
and Currents
protocol control
command
38 Earth / Ground N 0 Trip was caused by
Over Current Earth / Ground Any Operator Close
10ms
Trip Overcurrent action
Protection
39 SEF/SGF N 0 Trip was caused by controller software
Over Current Sensitive Earth / reset (data is
Trip volatile) 10ms
Ground Fault
Protection Protection OFF.
40 Sequence Y 0 Sequence advance Start of a new
10ms
Advance occurred. sequence
Protection Trip 2
41 Phase Over Y 0 Trip was caused by All fault flags are cleared
Current Trip Phase Overcurrent by one of the following
Protection actions :-
Reset Fault Flags 10ms
and Currents
protocol control
command
10ms
Protection
43 SEF/SGF N 0 Trip was caused by
controller software
Over Current Sensitive Earth /
reset (data is 10ms
Trip Ground Fault
volatile)
Protection
10ms
Protection Trip 3
N00-324 R54 48
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
45 Phase Over Y 0 All fault flags are cleared
Current Trip by one of the following
Trip was caused by actions :-
Phase Overcurrent Reset Fault Flags 10ms
Protection and Currents
protocol control
command
10ms
Protection
controller software
reset (data is 10ms
Trip Ground Fault
volatile)
Protection
10ms
Protection Trip 4
49 Phase Over Y 0 All fault flags are cleared
Current Trip by one of the following
Trip was caused by actions :-
Phase Overcurrent Reset Fault Flags 10ms
Protection and Currents
protocol control
command
10ms
Protection
controller software
reset (data is 10ms
Trip Ground Fault
volatile)
Protection
52 Reserved N 0 Start of a new
Always 0
sequence
Accumulated Protection Trip Operation Flags
Multiple Flags can be set in this section because they accumulate all the trips in the sequence
53 Phase Over Y 1 One or more trips All fault flags are cleared
Current Trip were caused by by one of the following .
Phase Overcurrent actions :- 10ms
Protection Reset Fault Flags
54 Earth / Ground N 1 One or more trips and Currents
Over Current were caused by protocol control
Trip Earth / Ground command 10ms
Overcurrent Any Operator Close
Protection action
55 SEF/SGF N 1 One or more trips controller software
Over Current were caused by reset (data is
Trip Sensitive Earth / volatile) 10ms
Ground Fault
Start of a new
Protection
N00-324 R54 49
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
56 Sequence Y 1 One or more sequence
Advance sequence advances 10ms
occurred.
End of Protection Flags
57 Close Isolate Y 2 Close Isolate Switch Close Isolate Switch Shows the state of the Trip &
OFF/ISOLATE(i.e. ON/ENABLE (i.e. Close Close isolate switches on the
Close is disabled) is enabled) control panel
58 Trip Isolate Y 1 Trip Isolate Switch Trip Isolate Switch 10ms
OFF (i.e. Trip is ON(i.e. Trip is enabled)
disabled)
59 Locked Y 1 ACR Locked Open ACR not locked open Shows that the ACR is
mechanically and electrically
locked in the open position. Not
supported on the N-Series
where it will always be zero.
10ms
60 ACR Memory Y 2 ACR Memory Data ACR Memory Data Valid Shows that the controller has
Data Invalid not valid retrieved the data from the ACR
memory. When invalid the
switchgear attributes and the
gas pressure are zeroed,
500ms
61 Auxiliary Y 2 Auxiliary supply has Auxiliary supply is 500ms
Supply failed normal
Fail
62 Switchgear Y 2 Switch disconnected Switch connected from Shows the connection state of
Connection from control cubicle. control cubicle. the cable between the
switchgear and the controller.
When connected to the ACR
Trip, Close and Locked
indications are valid.
When disconnected from the
ACR data will be forced invalid
500ms
63 SF6 Gas N 2 Gas pressure Low or Gas Pressure Normal, or Only set when switchgear is
Pressure Low Invalid Not Known, or Not a connected and ACR memory
or Invalid switchgear which has data is valid and switchgear
SF6. type has SF6.
500ms
64 Battery Supply Y 2 Battery supply not Battery supply normal 500ms
normal.
This includes :-
Battery Off
Battery Overvolt
Battery Low Volts
65 Contacts Life Y 2 When any vacuum When all vacuum 500ms
Low interrupter contact life interrupters have contact
is less than 20%. life >= 20%
66 Reserved N 2
N00-324 R54 50
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
67 Capacitor Y 2 Capacitor Charge Capacitor Charge OK The Trip/Close Capacitors have
Charge Failed failed to charge
Failure 500ms
68 Mechanism Y 2 Mechanism Failure Mechanism OK The switchgear has failed to
Failure Trip or Close electrically
500ms
69 Phase Ai Live Y 1 Phase is live Phase is dead Shows if the phase bushings
70 Phase Bi Live N 1 are above or below the live line
71 Phase Ci Live N 1 threshold.
72 Phase Ax Live Y 1
Note 3
73 Phase Bx Live N 1
Note 3
74 Phase Cx Live N 1 10ms
Note 3
75 Source Y 1 Shows that any of the All of the source side are Note that these points are
Voltage Status three phases of the Terminals dead different to the Load/Source
76 Load Voltage Y 1 designated Source Live/Dead events in the
side or Load side are All of the load side are controller event record
Status
live. Terminal dead
Note 3 10ms
77 Load Current Y 1 Current of 2.5A or Current of less than 2.5A
On more is flowing in at is flowing in all three 10ms
least one phase phases
78 Loop Auto On Y 2 Loop Automation is Loop Automation is Off Note 1
On 500ms
79 Loop Auto Y 2 Loop Auto Restore is Loop Auto Restore is Off Note 1
Restore On On 500ms
80 Loop Auto Y 2 The Tie recloser is The Tie Recloser will Note 1, 2
Tie Restore configured to restore only restore supply to its 500ms
On supply in both Load side or the
directions Recloser type is not set
to Tie
81 Loop Auto Y 2 Recloser type is set Recloser type is not set Note 1
Type Feeder to Feeder to Feeder 500ms
Type Midpoint to Midpoint to Midpoint 500ms
Type Tie to Tie to Tie 500ms
84 Reserved N Reserved Reserved
85 Reserved N Reserved Reserved

86 Loop Auto Y 2 Set when Loop Normal state, cleared on Note 1
Trip Request Automation issues a next internal scan after 10ms
Trip Request. set
87 Loop Auto Y 2 Set when Loop Normal state, cleared on Note 1
Close Request Automation issues a next internal scan after 10ms
Close Request. set
N00-324 R54 51
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
88 Dummy Circuit Y 2 DCB Closed DCB Not Closed The dummy circuit breaker is
Breaker an internal point useful for
Closed SCADA system testing. The
value of the DCB is non-volatile.
500ms
89 Automatic Y 2 APGS is ON APGS is OFF 500ms
Protection
Group
Selection
90 Supply Y 2 Supply Outage Supply Outage 500ms
Outage Measurement ON Measurement OFF
Measurement
91 Door Open Y 2 Cubicle Door Open Cubicle Door Closed This point only valid if hardware
option installed.
10ms
92 Phase Current Y 2 Phase Current Alarm Phase Current Alarm 500ms
HI Alarm ON OFF
93 Phase Current Y 2 Phase Current Alarm Phase Current Alarm 500ms
LOW Alarm ON OFF
94 Phase Voltage Y 2 Phase Voltage Alarm Phase Voltage Alarm 500ms
HI Alarm ON OFF
95 Phase Voltage Y 2 Phase Voltage Alarm Phase Voltage Alarm 500ms
LOW Alarm ON OFF
96 Earth Current N 2 Earth Current HI Earth Current HI Alarm 500ms
HI Alarm Alarm ON OFF
97 Earth Current N 2 Earth Current LOW Earth Current LOW 500ms
LOW Alarm Alarm ON Alarm OFF
98 System Power Y 2 System Power HI System Power HI Alarm 500ms
HI Alarm Alarm ON OFF
99 System Power Y 2 System Power LOW System Power LOW 500ms
100 Auxiliary Y 2 Auxiliary Supply has Auxiliary Supply has 500ms
Supply Fail failed for more than been restored for more
(Delayed) 120 seconds than 20 seconds
101 Most Recent Y 1 Set if the most recent All fault flags are cleared 10ms
Trip Phase A trip was caused by a by one of the following
Overcurrent A Phase Overcurrent actions :-
Protection Trip Reset Fault Flags
102 Most Recent Y 1 Set if the most recent and Currents 10ms
Trip Phase B trip was caused by a protocol control
Overcurrent B Phase Overcurrent command
Protection Trip Any Operator Close
103 Most Recent Y 1 Set if the most recent action 10ms
Trip Phase C trip was caused by a Protection turned
Overcurrent C Phase Overcurrent OFF
Protection Trip
N00-324 R54 52
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
104 Instantaneous Y 1 The peak current for At the time of next 10ms
Most Recent the most recent trip trip - the flags are
Trip was greater than the refreshed and cause
instantaneous setting of the most recent
protection operation
set.
Controller Software
Reset.
105 Under Y 1 Under frequency Under frequency Note 4. 500ms
Frequency protection ON protection OFF
106 Over Y 1 Over frequency Over frequency Note 4. 500ms
Frequency protection ON protection OFF
107 Normal Y 1 Enable Normal Enable Normal Note 4. 500ms
Frequency Frequency Close Frequency Close
Close protection ON protection OFF
108 Source Dead Y 1 Source Dead Source Dead Protection Note 5 500ms
Protection Protection ON OFF
109 Source Dead Y 1 Set if a lockout Cleared by: Note 5 10ms
Lockout caused by the Dead protocol command
Lockout feature
any operator close
occurred.
or operator trip. This
includes remote
control commands.
Start of a new
sequence.
110 Work Tag Trip Y 1 Work Tag Protection All fault flags are cleared One flag only provided because
was active at the time by one of the following a work tag trip forces lockout.
of the trip. actions :- Event time is the time of the
Reset Fault Flags pickup.
and Currents 10ms
protocol control
command
Any Operator Close
action
controller software
reset (data is
volatile)
Start of a new
sequence
111 IOEX Input 1 Y 1 Input asserted Input not asserted IOEX inputs represent the raw
state
112 IOEX Input 2 Y 1 Input asserted Input not asserted of the IOEX module after a
30ms
113 IOEX Input 3 Y 1 Input asserted Input not asserted debounce
114 IOEX Input 4 Y 1 Input asserted Input not asserted
N00-324 R54 53
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
123 Most recent Y 1 Set if the most recent Cleared by one of the One flag only provided because
trip Under trip was caused by following: there is no auto reclose after a
Frequency an Under Frequency 'Reset Flags and frequency trip.
condition Currents' protocol Unavailable on CAPM4.
124 Most recent Y 1 Set if the most recent command 10ms
trip Over trip was caused by Protection turned
Frequency an Over Frequency OFF
condition any operator close
or operator trip. This
includes remote
control commands.
Start of a new
sequence.
125 Operator Y 1 Set if the most recent Cleared by: 10ms
Close close caused by local 'Reset Flags
or remote panel close
and Currents'
request.
protocol
126 IOEX Close Y 1 Set if the most recent 10ms
close caused by an command
IOEX close input. Controller
127 Protocol Close Y 1 Set if the most recent Software Reset 10ms
close caused by a (data is volatile)
protocol close At the time of
request. the next Close
128 Automation Y 1 Set if the most recent 10ms
Close close caused by a
Distributed
Automation close
request (ie Loop
Automation, Auto
Changeover,
Generator Control).
129 Normal Y 1 Set if the most recent 10ms
Frequency close caused by
Close Normal Frequency
close request
N00-324 R54 54
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
130 External Close Y 1 Set if any of the 10ms
following caused the
most recent close
CCEM external
button on N-
Series
Mechanical
action. The
switchgear
detected as
closed without a
close request
Electrical action
(only available
on the Advanced
controller)
131 ACO Y 2 ACO Autorestore ON ACO Autorestore Whether to automatically
Autorestore OFF change back to master supply if
it returns live.
500ms
132 Auto Y 2 Auto-changeover is Auto-changeover is Turn ACO on/off
Changeover enabled disabled 500ms
Enable
133 Auto Y 2 Break before Make. Make before Break.
Changeover 500ms
Mode
134 ACO Rank Y 2 ACO Master ACO Slave 500ms
135 Live Load Y 1 Set if the most recent Cleared by: 10ms
Block close request was 'Reset Flags
Occurred blocked due to a Live
and Currents'
Load condition.
protocol
command
Controller Software
Reset (data is
volatile)
At the time of the
next Close
136 Generator Y 2 Generator Control Generator Control OFF 500ms
Control ON
N00-324 R54 55
Cleared = 0
Comment
Accuracy
W Series
DNP3 ID
Set = 1
Name
Class
Time
and
137 Output Control Y 2 Mode = SCADA Mode = NORMAL
Mode LOCAL controller LOCAL controller 500ms
mode places all mode disables only
binary and analogue
explicitly
outputs offline.
REMOTE controller
documented binary
mode places all outputs eg. Close,
binary and analogue Work Tag.
outputs online. REMOTE controller
Note 1. mode places all
binary outputs
online.
Analogue outputs
are always
enabled.
138 to Reserved
255
Note:
1. These point are only valid when the Loop Automation option is enabled for the current
configuration and are otherwise always reported as OFF (0).
2. The power flow direction (source/load designation) is determined by the user. Refer to
the Power Flow Direction binary input for status and binary output for control. See
Section 4.4 Terminology.
3. Not available on standard U-series ACR without external CVTs, value will always be 0.
4. Not available on CAPM4 controllers
5. Only available in Version 26 onwards.
N00-324 R54 56
Appendix E ACR - Analogue Input Points (Status - Small Set)

This is the reduced set of analogue status points available from the controller.
All analogue points have 500ms accuracy time tags. Refer to Appendix A for more
information on timing.
All analogues in the small analogue data set can fit in a signed 16-bit DNP3 data object
except where noted.
W series support is indicated below by a Y. If indicated as N then value is always 0.
This analogue set is fixed and will not be changed. Any new points will be added to the full
set only.
DNP3 Implementation
Static: Configurable Object 30 Variation 1, 2, 3, or 4 (refer to section 4.3)
Event: Configurable Object 32 Variation 1, 2, 3, or 4 (refer to section 4.3)
Deadband: Configurable Object 34 Variation 1, 2 (refer to section 4.3)
ACR Analogue Input Points (Small)

W Series
DNP3 ID
Default
Name
Class
Band
Units
Dead
Max
Min
Line Currents and System Power

0 A Current Y 0 16000 1A 10 A. 1
1 B Current N 0 16000 1A 10 A. 1
2 C Current N 0 16000 1A 10 A. 1
3 Earth / Ground Current N 0 16000 1A 5 A. 1
4 System kVA Note 2 Y 0 1.9GVA 1 kVA 250 kVA. 1
5 System kVAR Note 2 Y 0 1.9GVAR 1 kVAR 250 kVAR. 1
6 Operations Counter Y 0 65535 1 1 2
Operation Operation
Cumulative Protection Sequence Data
These points show all sources that record a max current event in the event log during a protection sequence. If the
same source has more than one max current event then the value in the point will be the max current from the last
trip of the sequence.
All fault currents are cleared to zero by one of the following actions:-
Reset Fault Flags and Currents protocol control command
Any Operator Close action
controller reset (data is volatile)
Start of a new sequence
7 A Fault Current Written on Y 0 16000 1A 1A 1
an A-Max event.
8 B Fault Current Written on N 0 16000 1A 1A 1
a B-Max event.
N00-324 R54 57
ACR Analogue Input Points (Small)
W Series
DNP3 ID
Default
Name
Class
Band
Units
Dead
Max
Min
9 C Fault Current Written N 0 16000 1A 1A 1
on a C-Max event.
10 Earth / Ground Fault N 0 16000 1A 1A 1
Current - Written on a G-
Max event. This includes
SEF/SGF Fault currents.
11 During a protection Y 1 4 1 1 1
sequence the value
increments indicating the
current trip or sequence
advance.
After a protection sequence
the final trip or sequence
advance that occurred.
12 Protection Group that was Y 0 9 1 1 1
in service at the start of the
sequence
0 = Group A
1 = Group B

9 = Group J
Voltage Measurements
Voltage measurements are provided for all terminals with voltage measurements. This varies depending upon
the model of ACR.
All x side voltages are not available in standard U-series ACR without external CVTs. Value always zero.
The source/load designation of the voltages is determined by the user. Refer to the Power Flow Direction
binary input for status and binary output for control.
13 Ai Phase-(Earth / Ground) Y 0 30000 1V 100 V. 2
Voltage
14 Bi Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Voltage
15 Ci Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Voltage
16 Ax Phase-(Earth / Ground) Y 0 30000 1V 100 V. 2
Volts Note 3
17 Bx Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Volts Note 3
18 Cx Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Volts Note 3
Note
1. The deadband for all analogue points can be configured, refer section 4.3.5 for more
information.
2. These points may exceed the 16 bit limit and can be obtained using 32 bit analogue
input objects.
N00-324 R54 58
Appendix F ACR - Analogue Input Points (Status Full Set)

This is the complete set of analogue status points available from the controller.
All analogue points have 500ms resolution time tags. Refer to Appendix A for more
All analogues in the full analogue data set can fit in a signed 16-bit DNP3 data object
except where noted.
DNP3 Implementation
ACR Analogue Input Points (Full)
Dead Band
DNP3 ID
W Series
Default
Class
Units
Max
Min
Name
System Line Currents and Power

0 A-Phase Current Y 0 16000 1A 10 A. 1
1 B-Phase Current N 0 16000 1A 10 A. 1
2 C-Phase Current N 0 16000 1A 10 A. 1
3 (Earth / Ground) Current N 0 16000 1A 5 A. 1

4 System kVA Note 2 Y 0 1.9GVA 1 kVA 250 kVA. 1
5 System kVAR Note 2 Y 0 1.9GVAR 1 kVAR 250 1
kVAR.
6 Operations Counter Y 0 65535 1 1 2
Operation Operation
Cumulative Protection Sequence Data
These points show all sources that record a max current event in the event log
during a protection sequence. If the same source has more than one max
current event then the value in the point will be the max current from the most
recent trip of the sequence.
All fault currents are cleared to zero by one of the following actions:-
Reset Fault Flags and Currents protocol control command
Any Operator Close action
controller reset (data is volatile)
Start of a new sequence
7 A Fault Current Written Y 0 16000 1A 1A 1
on an A-Max event.
Note 10
N00-324 R54 59
Dead Band
DNP3 ID
W Series
Default
Class
Units
Max
Min
Name
8 B Fault Current Written N 0 16000 1A 1A 1
on a B-Max event.
Note 10
on a C-Max event.
Note 10
11 During a protection Y 1 4 1 1 1
sequence the value
increments indicating the
current trip or sequence
advance.
After a protection sequence
the final trip or sequence
advance that occurred.
12 Protection Group that was Y 0 9 1 1 1
in service at the start of the
sequence
0 = Group A
1 = Group B

9 = Group J
Voltage Measurements
Voltage measurements are provided for all terminals with voltage measurements. This varies
depending upon the model of ACR.
All x side voltages are not available in standard U-series ACR without external CVTs. Value always
zero.
The source/load designation of the voltages is determined by the user. Refer to the Power Flow
Direction binary input for status and binary output for control.
All voltages have a common deadband which can be configured (refer section 4.3.5).
13 Ai Phase-(Earth / Ground) Y 0 30000 1V 100 V. 2
Voltage
14 Bi Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Voltage
15 Ci Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Voltage
16 Ax Phase-(Earth / Ground) Y 0 30000 1V 100 V. 2
Volts
Note 10
17 Bx Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Volts
Note 10
18 Cx Phase-(Earth / Ground) N 0 30000 1V 100 V. 2
Volts
Note 10
19 A-Bi Phase-Phase Voltage N 0 38000 1V 100 V. 2
Note 2
20 B-Ci Phase-Phase Voltage N 0 38000 1V 100 V. 2
Note 2
N00-324 R54 60
Dead Band
DNP3 ID
W Series
Default
Class
Units
Max
Min
Name
21 C-Ai Phase-Phase Voltage N 0 38000 1V 100 V. 2
Note 2
22 A-Bx Phase-Phase Volts N 0 38000 1V 100 V. 2
Note 2, 10
23 B-Cx Phase-Phase Volts N 0 38000 1V 100 V. 2
Note 2, 10
24 C-Ax Phase-Phase Volts N 0 38000 1V 100 V. 2
Note 2, 10
System Status
25 System Power (kW) Y -1.9GW 1.9GW 1 kW 250kW. 1
This can be a signed
quantity that indicates
direction of power flow, or
an unsigned quantity that is
always positive regardless
of the direction of the power
flow. This is determined by
the controller configuration
Note 2
26 System Power Factor Y 0.0 1.0 0.1 0.1 1
Note 6
27 Gas Pressure, kPag. N -100 300 1 kPaG 5kPaG 2
Note 3, 9
28 Gas Pressure, psi N -14 44 1 psi 1psi 2
Note 3, 9
29 Code Version Y 0 9,999,999 1 1 0
Note 2, 4
30 Configuration Number Y 0 99,999 1 1 0
Note 2, 5
31 CAPM Serial Number Y 0 2147483647 1 1 0
32 ACR Serial Number Y 0 2147483647 1 1 2
Note 2
33 I Contact Life Y 0.0 100.0 0.1 % 0.1 % 2
Note 7
34 II Contact Life N 0.0 100.0 0.1 % 0.1 % 2
Note 7
35 III Contact Life N 0.0 100.0 0.1 % 0.1 % 2
Note 7
36 Protection setting selection Y 0 9 1 1 1
0 = Group A
1 = Group B

9 = Group J
37 Transmitted frame count Y 0 32768 1 1 0
38 Received frame count Y 0 32768 1 1 0
39 Received message length Y 0 999 1 1 0
error
40 Received message CRC Y 0 999 1 1 0
error
N00-324 R54 61
Dead Band
DNP3 ID
W Series
Default
Class
Units
Max
Min
Name
Protection Sequence Data
These analogue points record data about the protection sequence including maximum fault
currents. These are derived from the max current events that are seen in the Operator Control
Panel event record and record the current for each phase and for earth/ground.
For any one protection trip or sequence advance more than one fault current
can be set. For example a Phase/Phase fault might set an A-Phase current and
a B-Phase current.
Other data recorded includes the number of trips in the protection sequence and
the Protection Group that was active at the time of the protection operation.
Data is cleared to zero by the following actions:-
Reset Fault Current remote control command defined below
Any Operator Close or Trip action
Start of a new sequence.
This data is volatile, ie they are zeroed on controller software reset.
Protection Trip 1
on an A-Max event.
on a B-Max event.
on a C-Max event.
Protection Trip 2

on an A-Max event.
on a B-Max event.
on a C-Max event.
Protection Trip 3

on an A-Max event.
on a B-Max event.
on a C-Max event.
N00-324 R54 62
Dead Band
DNP3 ID
W Series
Default
Class
Units
Max
Min
Name
Protection Trip 4

on an A-Max event.
on a B-Max event.
on a C-Max event.
Miscellaneous
57 Loop automation time Y 0 1800 1 second 10 second 2
remaining prior to a trip or
close action occurring. For
no action pending value is
zero.
Note 8
58 Maximum Average Current Y 0 16000 1A 10A 1
of all phases for the
previous day ending at
24:00 (2sec filter window)
59 Frequency N 45 65 1Hz 0.1Hz 2
Note 11
60 Auto-Changeover Status N 0 18 1 1 1
0 Auto-Changeover OFF
1 Auto-Changeover ON
2 ACO load MASTER
3 ACO load SLAVE
4 ACO No SLAVE comms
5 ACO abort - status 1
N00-324 R54 63
Dead Band
DNP3 ID
W Series
Default
Class
Units
Max
Min
Name
61 Generator Control State Y 0 8 1 1 1
0 Generator Control OFF

1 Switch Closed
2 Line Dead Check
3 Wait Switch Open
4 Wait Generator Live
5 Generator Running
6 Line Live Check
7 Wait Generator Off
8 Wait Switch Closed
62 Reserved
Note
1. The deadband for all analogue points can be configured, refer section 4.3.5 for more
information.
2. These points may exceed the 16 bit limit and can be obtained using 32 bit analogue
input objects.
3. If ACR Memory Data Invalid binary status is set then value is 0
4. The code version is an seven digit number that has the form XXX-XX.XX with the dash
and point formatting removed.
5. The configuration number is a five digit number that has the form XXXXX. It identifies
the configuration loaded into the controller database.
6. Power factor has a built in scale factor of 10 i.e. range 0.0 to 1.0 with resolution 0.1 is
transmitted as 0 to 10 with resolution 1.
7. Contact life has a built in scale factor of 10 i.e. range of 0.0% to 100.0% with resolution
0.1% is transmitted as 0 to 1000 with resolution 1.
8. This point is only valid when the Loop Automation option is enabled for the current
configuration and is otherwise always reported as zero.
9. Not available on U-series ACR, value will always be 0.
11. Frequency has a built in scale factor of 10 i.e. range 45 to 65 with resolution 0.1 is
transmitted as 450 to 650 with resolution 1. This option unsupported on CAPM 4
controllers.
N00-324 R54 64
Appendix G ACR - Counter Point


DNP3 Implementation
Binary Counters
Static Object: Object 20 Variation 05 32 Bit Binary Counter without Flag
Request Function Codes: 01 Read, 07 Immediate Freeze,
08 Immediate Freeze, No Ack, 09 Freeze and Clear
10 Freeze and Clear, No Ack
Frozen Counters
Static Object: Object 21 Variation 9 32 Bit Frozen Counter without Flag
ACR Counter Points

W Series
DNP3 ID
Name
Units
Max
Min
0 KWH Cumulative Note 1 Y 0 2147483647 KWH

1 Source Outages Note 2, 3 Y 0 2147483647 Counts
2 Source Outage Duration Y 0 2147483647 Seconds
Note 2, 3
3 Load Outages Note 2, 3 Y 0 2147483647 Counts
4 Load Outage Duration Y 0 2147483647 Seconds
Note 2, 3
Note:
1. This accumulates the total kWH flowing through the ACR.
If the controller is set for Power Flow Unidirectional then the cumulative total increases
irrespective of the direction of power flow to show the total power that has passed
through the device.
If the controller is set for Bi-Directional power flow then the cumulative total can
increase or decrease reflecting the nett power flow.
2. Resetting any Outage counter via a protocol counter reset command will result in the
resetting of all outage counters.
Power Flow Direction Binary Input for status and Binary Output for control.
N00-324 R54 65
Appendix H ACR - Binary Output Points

Changing some of these settings affects the currently active protection group. The change
is put into effect immediately and is permanent for that group. In other words, it is the
equivalent to selecting that protection group on the operator control panel, changing the
setting and then putting the change into service.
All binary output points have a matching binary input status point. The controller can
optionally return binary output object status in response to a class 0 or an integrity poll. It
is recommended that the master station use the controls corresponding binary input
status to verify the success of an action.
If W series is indicated as Y below then point is supported otherwise no action is taken.
DNP3 Implementation
Binary Output Status
Static Object: Object 10 Variation 02 Binary Output Status
The status of the offline/online bits is determined by the reject conditions shown in
the table below, or Output Control (See Database Parameters). A point is reported
offline if it cannot be forced to the alternate state due to condition listed. Note that
not all conditions that prevent a control from succeeding are listed. Some conditions
(eg mechanical failure) may be undetermined at time of read.
Request Function Code: 01- Read
Relay Control Block
Control Object: Object 12 Variation 01 Control Relay Output Block
Control relay output block parameters supported:
Control types are accepted on per point basis as shown in the table below.
TC = Trip/Close, P = Pulse ON/OFF, L = Latch ON/OFF.
Set (1) = Close, Pulse ON, Latch ON
Cleared (0) = Trip, Pulse OFF, Latch OFF
Recommended control types is shown in bold font.
Note: Pulse OFF is not supported on most master station systems, or the most
recent DNP3 Standard.
The count, on-time, off-time, queue, and clear parameters are ignored.
Multiple controls in the one message are not recommended.
Request Function Codes: 03 Select, 04 Operate, 05 Direct Operate,
06 Direct Operate, No Ack
Response Codes: Refer to Appendix C for a table of reported status values
ACR Binary Output Points

Cleared =
W Series
DNP3 ID
Set = 1
Control
Name
Type
0
0 Earth / Ground Fault N Enable Earth / Ground Earth / Ground L, P

protection Protection Protection OFF and
Rejected if: SEF/SGF Protection
earth/ground fault OFF
OFF is not allowed. Rejected if:
earth/ground fault
N00-324 R54 66
Cleared =
W Series
DNP3 ID
Set = 1
Control
Name
Type
0
OFF is not allowed.
1 SEF/SGF protection N SEF/SGF protection Disable SEF/SGF L, P
ON and protection
Earth / Ground
Protection ON
Rejected if:
SEF/SGF is not
available
2 Auto Reclose Y Auto Reclose ON Auto Reclose OFF L, P
3 ACR Control Y Close Trip TC,
Rejected if: Rejected if: L, P
Close coil is Trip coil is isolated
isolated SF6 gas pressure
controller is in is low (if applicable)
LOCAL control AND low gas
mode lockout is ON
SF6 gas pressure Switchgear data
is low (if applicable) invalid
AND low gas
lockout is ON
Work Tag is
applied
Switchgear data
invalid
Mechanically
interlocked (if
applicable)
Live load blocking
ON AND any load
side terminal live
Trip and/or Close
capacitors are
charging or failed
Generator Control
has close blocking
on
4 Work Tag Y Applies Work Tag. Removes Work Tag. L, P
Rejected if: Rejected if:
controller is in controller is in
LOCAL Mode LOCAL Mode.
5 Cold Load Idle/Max Y Set cold load time to its Set cold load time to L, P
maximum value. This zero. This means that
means that the cold the threshold multiplier
load threshold current will not be affected by
will be set to its the cold load function.
maximum value Rejected if:
Rejected if: Cold load support
Cold load support is OFF
is OFF
6 High Current Lockout Y Enable High Current Disable High Current L, P
Lockout Lockout
N00-324 R54 67
Cleared =
W Series
DNP3 ID
Set = 1
Control
Name
Type
0
7 Loss of Phase Protection N Enable Loss of Phase Disable Loss of Phase L, P
Rejected if: Protection Protection
LOP and Loop Auto
linked.
Single Phase switchgear.
8 Sequence Control Y Enable Sequence Disable Sequence L, P
Control Control
9 Live Load Blocking Y Live Load blocking ON Live Load blocking OFF L, P
10 ` Reset Fault Y Resets all Object 30 No Action L, P
Flags and Currents Fault Currents to zero
Note 1 and clears all Object 01
protection trip flags
11 Protection Control Y Enable Protection Turn ALL Protection L, P
OFF
Rejected if:
protection OFF is
not allowed
12 Power Flow Direction Note 4 Y Source X, Load I Source I, Load X L, P
(Source and Load Bushings) Note 7
13 Protection Group A Note 1, 3 Y Group A ON Note 5 No Action L, P
14 Protection Group B Note 1, 3 Y Group B ON Note 5 No Action L, P
15 Protection Group C Note 1, 3 Y Group C ON Note 5 No Action L, P
16 Protection Group D Note 1, 3 Y Group D ON Note 5 No Action L, P
17 Protection Group E Note 1, 3 Y Group E ON Note 5 No Action L, P
18 Protection Group F Note 1, 3 Y Group F ON Note 5 No Action L, P
19 Protection Group G Note 1, 3 Y Group G ON Note 5 No Action L, P
20 Protection Group H Note 1, 3 Y Group H ON Note 5 No Action L, P
21 Protection Group I Note 1, 3 Y Group I ON Note 5 No Action L, P
22 Protection Group J Note 1, 3 Y Group J ON Note 5 No Action L, P
23 Loop Automation Control Y Loop Automation ON Loop Automation OFF L, P
Note 2 Rejected if:
Loop automation
capability not
available
Trip coil isolated
Close coil isolated
Mechanism fail
Switchgear data
invalid
Battery not normal
SF6 Gas Pressure
is low (if applicable)
AND Low Gas
Lockout is ON
Tripped AND
(Midpoint OR
Feeder)
U Series AND no
external CVTs
AND (TIE OR Auto
N00-324 R54 68
Cleared =
W Series
DNP3 ID
Set = 1
Control
Name
Type
0
Restore ON)
Generator Control
available
Auto-Changeover
is enabled.
24 Dummy Circuit Breaker Y DCB Close DCB Trip TC,
L, P
25 Automatic Protection Group Y APGS ON APGS OFF L, P
Selection Rejected if:
APGS ON is Not
Allowed
26 Supply Outage Measurement Y Supply Outage Supply Outage L, P
Control Measurement ON Measurement OFF
27 Supply Outage Measurement Y Resets all Supply No Action L, P
Reset Outage counters
values.
28 Under Frequency Protection Y Enable under frequency Disable under L, P
protection frequency protection
CAPM4 CAPM4
29 Over Frequency Protection Y Enable over frequency Disable over frequency L, P
protection protection
CAPM4 CAPM4
30 Normal Frequency Close Y Enable normal Disable normal L, P
Protection frequency close frequency close
protection protection
CAPM4 CAPM4
31 Source Dead Protection Y Enable Disable L, P
Rejected if:
No X side voltage
measurement
possible and power
flow direction is X
to I side.
32 Protocol IOEX control 1 Y Sets IOEX output that is Clears IOEX output that
33 Protocol IOEX control 2 Y mapped to this point. is mapped to this point.
34 Protocol IOEX control 3 Y Used for protocol Used for protocol
control. control.
35 Protocol IOEX control 4 Y
36 Protocol IOEX control 5 Y TC,
Note: The Control Type Note: The Control Type L, P
37 Protocol IOEX control 6 Y depends on the depends on the
38 Protocol IOEX control 7 Y assignment in the IOEX assignment in the IOEX
39 Protocol IOEX control 8 Y mapping. mapping.
40 ACO Auto Restore Y ACO Auto Restore ON. ACO Auto Restore L, P
Rejected if: OFF. Rejected if:
Switch is LBS Switch is LBS
ACO feature is not ACO feature is not
available available
N00-324 R54 69
Cleared =
W Series
DNP3 ID
Set = 1
Control
Name
Type
0
41 ACO Enable Y ACO ON. Rejected if: ACO OFF. Rejected if: L, P
ACO feature is not
available
Generator Control
is available
Loop Automation is
available
42 ACO Mode Y ACO Mode = Break ACO Mode = Make L, P
before Make. Rejected before Break. Rejected
if: if:
available available
43 Generator Control Y Turn Generator Control Turn Generator Control L, P
ON OFF
Rejected if:
Generator Control
is not available
Loop Automation is
available
Auto-Changeover
is enabled
44 ACO Rank Note 6 Y Set ACO rank to be Set ACO rank to be L, P
master. Rejected if: slave. Rejected if:
available. available.
Switchgear is open Switchgear is
ACO is enabled closed
ACO is enabled
Note:
1. The response for binary output status for these points will always be 0.
configuration otherwise No Action is taken.
3. Only one protection group can be active at any one time. Activating any of these
protection groups will automatically reset the previously active setting.
4. Changing the Source/Load direction affects the following aspects of the operation of
the controller:
Whether the source or load corresponds to 1/I side or 2/X side on the voltage
measurements
Which side is the source or load for the Live Load Blocking
Which side is the source or load for the Directional Blocking
Which direction is positive power flow for the System Power Analogue Input
Power Flow Direction Binary Input status
5. The number of protection groups available in the controller is configurable. If a control
is not available because the protection set is not supported then it is rejected.
6. Refer to N00-529 Technical Manual Auto Changeover for correct sequence of
events required for remotely changing ACO Rank.
N00-324 R54 70
7. See Section 4.4 Terminology.

Appendix I ACR - Analogue Output Points
Changing some of these settings affects the currently active protection group. The change
equivalent to selecting that protection group on the operator control panel, changing the
All analogue output points have a matching analogue input point. The controller does not
return analogue output object status in response to a class 0 or and integrity poll. It is
recommended that the master station use the outputs corresponding analogue input
If W series is indicated as Y below then point is supported otherwise no action is taken.
DNP3 Implementation
Analogue Output Status
Static Object: Object 40 Variation 02 16 Bit Analogue Status
The status of the offline/online bits is determined by Output Control (See Database
Parameters). A point is reported offline if it cannot be forced to the alternate state.
Analogue Output Block

Control Object: Object 41 Variation 02 16 Bit Analogue Output Block
Response Codes: Refer to Appendix C for a table of reported status values.
ACR Analogue Output Point

W Series
DNP3 ID
Name
Units
Max
Min
0 Protection Group Selection 0 9 N/A

0 = Group A Note 1
1 = Group B

9 = Group J
Note:
1. The number of protection groups available in the controller is configurable. If the
analogue output block value is not available because the protection set is not
supported then it is rejected.
N00-324 R54 71
DNP3 Protocol Technical Manual (LBS)
Appendix J LBS Binary Points Data (Status)

Time resolution is as shown. Refer to Appendix A for more information on timing.

DNP3 Implementation
Static: Object 01 Variation 01 Single Bit Binary Input
Event: Configurable refer to section 4.3
LBS Binary Input Points (Status)
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
0 Abnormal Operator 1 For any of the following None of the specified This flag shows that the
conditions conditions:- conditions are true operator has the LBS in
Trip or Close an abnormal state such
Isolated, as work tag applied.
This means that it will
LBS Mechanically
operate differently to its
locked open (if
normal mode of
applicable)
operation.
Work Tag Applied
500ms
1 LBS Tripped (open) 1 LBS Tripped LBS not Tripped These are repeats of the
mechanism travel
switches. When the LBS
is disconnected from the
2 LBS Closed 1 LBS Closed LBS not Closed control cubicle they are
both cleared.
10ms
3 Controller Mode 2 LOCAL control Disabled LOCAL Control The controller is either in
Remote control Enabled LOCAL or Remote
Enabled Remote Control Controller Mode. This
Disabled affects the closing
command the
permission to
set/remove work tag.
500ms
4 Maintenance 1 For any of the following No maintenance The controller has
Required conditions:- required detected one or more
Battery NOT normal conditions which require
maintenance.
Capacitor charge
failure This point cannot
become Set until at least
Low power mode
five minutes after
Low SF6 gas controller start.
pressure LBS data 500ms
N00-324 R54 72
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
not valid (includes
connection to an
invalid switch type)
Any contact life is
less than 20%
Mechanical failure
5 Work Tag 2 Work Tag Applied Work Tag Removed The controller can have
a work tag. This affects
the closing command
500ms
6 Detection A Active 2 Detection Group A is Detection Group A is not These flags indicate
active active the active protection
7 Detection B Active 2 Detection Group B is Detection Group B is not group. If neither A nor
active active B is active (eg.
Because C is active)
then flags will be clear
and the analogue value
point must be used to
determine the active
group.
500ms
8 Detection C Active 2 Detection Group C is Detection Group C is not Only one detection
active active group is active at any
one time.
9 Detection D Active 2 Detection Group D is Detection Group D is not
active active
10 Detection E Active 2 Detection Group E is Detection Group E is not 500ms
active active
11 Detection F Active 2 Detection Group F is Detection Group F is not
active active
12 Detection G Active 2 Detection Group G is Detection Group G is not
active active
13 Detection H Active 2 Detection Group H is Detection Group H is not
active active
14 Detection I Active 2 Detection Group I is Detection Group I is not
active active
15 Detection J Active 2 Detection Group J is Detection Group J is not
active active
16 Power Flow 2 Source X, Load I Source I, Load X The power flow direction
Direction Note 2 (source/load
(Source and Load designation) is
Bushings) determined by the user.
Refer to the Power Flow
Direction binary output
for more information
500ms
17 Close Isolate 2 Close Isolate Switch Close Isolate Switch Shows the state of the
OFF/ISOLATE(i.e. Close ON/ENABLE (i.e. Close Trip & Close isolate
is disabled) is enabled) switches on the control
18 Trip Isolate 1 Trip Isolate Switch OFF Trip Isolate Switch panel
(i.e. Trip is disabled) ON(i.e. Trip is enabled) 10ms
N00-324 R54 73
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
19 Locked 1 LBS Locked Open LBS not locked open Shows that the LBS is
mechanically and
electrically locked in the
open position.
Not supported on
Nseries.
10ms
20 LBS Memory Data 2 LBS Memory Data not LBS Memory Data Valid Shows that the controller
Invalid valid has retrieved the data
from the LBS memory.
When invalid the
switchgear attributes and
the gas pressure are
zeroed,
500ms
21 Auxiliary Supply 2 Auxiliary supply has Auxiliary supply is 500ms
Fail failed normal
22 Switchgear 2 Switchgear Switchgear is connected Shows the connection
Connection disconnected from to control cubicle. state of the cable
control cubicle. between the switchgear
and the controller. When
connected to the LBS
Trip, Close and Locked
indications are valid.
When disconnected from
the LBS data will be
forced invalid
500ms
23 SF6 Gas Pressure 2 Gas pressure Low or Gas Pressure Normal, Only set when
Low or Invalid Invalid or Not Known, or Not a switchgear is connected
switchgear which has and LBS memory data is
SF6. valid and switchgear
type has SF6.
500ms
24 Battery Supply 2 Battery supply not Battery supply normal 500ms
normal.
This includes :-
Battery Off
Battery Overvolt
Battery Low Volts
25 Switchgear Family 3 Set for Load Break Clear For Recloser
Switch 500ms
26 Contacts Life Low 2 When any contact life is When all contacts have 500ms
less than 20%. contact life >= 20%
27 Capacitor Charge 2 Capacitor Charge Failed Capacitor Charge OK The Trip/Close
Failure Capacitors have failed to
charge. (where relevant)
500ms
N00-324 R54 74
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
28 Mechanism Failure 2 Mechanism Failure Mechanism OK The switchgear has
failed to Trip or Close
electrically
500ms
29 Phase Ai Live 1 Phase is live Phase is dead Shows if the phase
30 Phase Bi Live 1 bushings are above or
below the live line
31 Phase Ci Live 1
threshold.
32 Phase Ax Live 1
33 Phase Bx Live 1 10ms
34 Phase Cx Live 1
35 Source Voltage 1 Shows that any of the All of the source side are Note that these points
Status three phases of the Terminals dead are different to the
designated Source side Load/Source Live/Dead
36 Load Voltage 1 or Load side are live. All of the load side are events in the controller
Status Terminal dead event record
10ms
37 Load Current On 1 Current of 2.5A or more Current of less than 2.5A
is flowing in at least one is flowing in all three 10ms
phase phases
38 Dummy LBS 2 Dummy LBS Closed Dummy LBS not closed. This point represents an
Closed internal dummy LBS.
This is an internal point
useful for SCADA
system testing. The
value of the dummy LBS
is non-volatile.
500ms
39 Supply Outage 2 Supply Outage Supply Outage 500ms
Measurement Measurement ON Measurement OFF
40 Door Open 2 Door Open. Door Closed.
41 Phase Current HI 2 Phase Current Alarm Phase Current Alarm 500ms
Alarm ON OFF
42 Phase Current 2 Phase Current Alarm Phase Current Alarm 500ms
LOW Alarm ON OFF
43 Phase Voltage HI 2 Phase Voltage Alarm Phase Voltage Alarm 500ms
Alarm ON OFF
44 Phase Voltage 2 Phase Voltage Alarm Phase Voltage Alarm 500ms
LOW Alarm ON OFF
45 Earth Current HI 2 Earth Current HI Alarm Earth Current HI Alarm 500ms
Alarm ON OFF
46 Earth Current LOW 2 Earth Current LOW Earth Current LOW 500ms
Alarm Alarm ON Alarm OFF
47 System Power HI 2 System Power HI Alarm System Power HI Alarm 500ms
Alarm ON OFF
48 System Power 2 System Power LOW System Power LOW 500ms
N00-324 R54 75
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
49 Auxiliary Supply 2 Auxiliary Supply has Auxiliary Supply has 500ms
Fail (Delayed) failed for more than 120 been restored for more
seconds than 20 seconds
Operator/Detection Flags
These flags show the status of the operator controls and some of the detection flags.
They are equivalent to the indications available on the Operator Control Panel of the controller.
50 Phase Detection 2 Phase Detection ON Phase Detection OFF 500ms
Enabled
51 Earth/Ground 2 Earth/Ground Detection Earth/Ground Detection 500ms
Detection Enabled ON OFF
52 SEF/SGF 2 SEF/SGF Detection ON SEF/SGF Detection 500ms
Detection Enabled OFF
53 Sectionaliser Auto 2 Sectionaliser Auto ON Sectionaliser OFF (Load 500ms
Break Switch)
54 Cold Load Auto 2 Cold Load auto-mode is Cold Load pickup is
armed. OFF.
This means the Cold This means that the cold
Load function is enabled load function is 500ms
and may, or may not, be completely disabled.
affecting the threshold See Cold Load Idle
multiplier. (below)
55 Cold Load Idle 2 Cold Load is Idle or is Cold load is NOT Idle.
turned off. This means that the
This means that the threshold multiplier is 500ms
threshold multiplier is not being raised by the cold
being affected by the load pickup function.
cold load function.
56 Live Load Blocking 2 Live Load Blocking ON Live Load Blocking OFF 500ms
57 Automatic 2 Automatic Detection Automatic Detection 500ms
Detection Group Group Selection is ON Group Selection is OFF
Selection
(Code Version 025-
01 and later)
Detection Flags
This group of points indicates what happened in the most recent fault detection. Unlike the ACR, these flags dont
attempt to reconstruct a fault sequence. The flags are not cumulative, they are cleared as each new fault is
detected. For example, if there is an earth fault followed by a phase fault, the earth fault flag will be cleared when
the phase fault flag is set.
In addition analogue data is available which shows the fault currents.
Most of these flags are cleared either by protocol command or when the switchgear is tripped/closed by the
operator or when a new fault is detected.
This data is volatile, i.e. it is zeroed on controller software reset.
If there is more than one protocol running simultaneously in the controller this data is replicated between the
protocols so that each master station can clear its data independently from the others.
58 Sequence in 2 Start of sequence. A Sectionaliser Trip. This shows that a
Progress detection trip or Sequence Reset. Detection sequence has
sequence advance has started and not yet
occurred. completed.
Note that operator trip
does not cause a
N00-324 R54 76
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
sequence in progress
10ms
59 A Phase 2 A Phase Overcurrent Cleared by These flags show which
Overcurrent Fault Fault Operator trip elements were picked up
since last clear action
60 B Phase 2 B Phase Overcurrent Any close
Overcurrent Fault Fault 10ms
Reset Flags
61 C Phase 2 C Phase Overcurrent Protocol Command
Overcurrent Fault Fault
62 Earth/Ground 2 Earth/Ground
Overcurrent Fault Overcurrent Fault
63 SEF/SGF 2 SEF/SGF Overcurrent
Overcurrent Fault Fault
64 Supply Interrupt 1 Supply Interrupt Set if a supply interrupt
occurred after the most
recent fault.
10ms
65 Sectionaliser Trip 1 Sectionaliser Trip Set if switch trips to
sectionalise
10ms
66 1 Input asserted Input not asserted IOEX inputs represent
IOEX Input 1
the
67 IOEX Input 2 1 Input asserted Input not asserted raw state of the IOEX
68 IOEX Input 3 1 Input asserted Input not asserted module after a 30ms
69 IOEX Input 4 1 Input asserted Input not asserted debounce.
70 IOEX Input 5 1 Input asserted Input not asserted
78 1 Set if the most recent Cleared by: 10ms
close caused by local or 'Reset Flags and
Operator Close Currents' protocol
remote panel close
request. command
79 1 Set if the most recent Controller 10ms
IOEX Close close caused by an Software Reset
IOEX close input. (data is volatile)
At the time of the
80 1 Set if the most recent next Close 10ms
Protocol Close close caused by a
protocol close request.
Operator Trip
N00-324 R54 77
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
81 External Close 1 Set if any of the following 10ms
caused the most recent
close
Mechanical action.
The switchgear
detected as closed
without a close
request
CCEM external
button on N-Series
Electrical action
(only available on
the Advanced
controller)
82 Live Load Block 1 Set if the most recent Cleared by: 10ms
Occurred close was blocked due 'Reset Flags
to a Live Load condition
and Currents'
protocol
command
Controller
Software Reset
(data is volatile)
At the time of
the next Close
83 Generator Control 2 Generator Control ON Generator Control 500ms

OFF
84 Reserved
85 Reserved
86 Reserved
87 Reserved
88 Output Control 2 Mode = SCADA Mode = NORMAL
Mode LOCAL controller mode LOCAL controller 500ms
places all binary and mode disables only
analogue outputs offline.
explicitly
REMOTE controller
mode places all binary
documented binary
and analogue outputs outputs eg. Close,
online. Work Tag.
Note 1. REMOTE
controller mode
places all binary
outputs online.
Analogue outputs
are always
enabled.
N00-324 R54 78
Cleared = 0
Resolution
Comment
DNP3 ID
Set = 1
Name
Class
Time
and
89
Reserved
93
Note:
1. Only available on CAPM-5 controller
N00-324 R54 79
Appendix K LBS - Analogue Input Points (Status - Small Set)

This is the reduced set of analogue status points available from the controller.
All analogues in the small analogue data set can fit in a signed 16-bit DNP3 data object
except where noted.
This analogue set is fixed and will not be changed. Any new points will be added to the full
set only.
DNP3 Implementation
LBS Analogue Input Points (Small)
Dead Band
DNP3 ID
Default
Name
Class
Units
Max
Min
Line Currents and System Power

0 A Current 0 16000 1A 10 A. 1
1 B Current 0 16000 1A 10 A. 1
2 C Current 0 16000 1A 10 A. 1
3 Earth / Ground Current 0 16000 1A 5 A. 1
4 System kVA Note 2 0 1.9 1 kVA 250 kVA. 1
GVA
5 System kVAR Note 2 0 1.9 1 kVAR 250 kVAR. 1
GVAR
6 Operations Counter 0 65535 1 1 Operation 2
Operation
Voltage Measurements (Earth/Ground)
Voltage measurements are provided for all terminals with voltage measurements.
The source/load designation of the voltages is determined by the user. Refer to the Power Flow
Direction binary input for status and binary output for control.
Ai Phase-(Earth / Ground)
7 0 30000 1V 100 V. 2
Voltage
Bi Phase-(Earth / Ground)
8 0 30000 1V 100 V. 2
Voltage
Ci Phase-(Earth / Ground)
9 0 30000 1V 100 V. 2
Voltage
Ax Phase-(Earth / Ground)
10 0 30000 1V 100 V. 2
Voltage
Bx Phase-(Earth / Ground)
11 0 30000 1V 100 V. 2
Voltage
N00-324 R54 80
LBS Analogue Input Points (Small)
Dead Band
DNP3 ID
Default
Name
Class
Units
Max
Min
Cx Phase-(Earth / Ground)
12 0 30000 1V 100 V. 2
Voltage
Fault Detection Data
These analogue points record data about the fault detection including maximum fault currents.
These are derived from the max current events, which are seen in the Operator Control Panel event
record and record the current for each phase and for earth/ground.
For any one fault more than one fault current can be set. For example a Phase/Phase fault might set
an A-Phase current and a B-Phase current.
Other data recorded includes the supply interrupt count and the Detection Group which was active at
the time of the fault detection.
Fault Detection Data is cleared to zero by the following actions :-
New fault detected
This data is volatile, that is they are zeroed on controller software reset.
If there is more than one protocol running simultaneously in the controller this data is replicated
between the protocols so that each master station can clear its data independently from the others.
Active Detection Group
13 The number of the Detection 0 9 1 1 1
Group active during the
sequence.
Supply Interrupt Count
14 The number of Supply 1 10 1 1
Interrupts Counted.
Most Recent A-Phase Fault
15 Written on a Max Current event 0 16000 Amps 1A 1
for A Phase
Most Recent B-Phase Fault
for B Phase
Most Recent C-Phase Fault
for C Phase
Most Recent Earth/Ground
Fault Current - Written on an E-
18 0 16000 Amps 1A 1
19
-
Reserved
29
Note
1. The deadband for all analogue points can be configured, refer section 4.3.5 for
more information.
2. These points may exceed the 16 bit limit and can be obtained using 32 bit
analogue input objects.
N00-324 R54 81
Appendix L LBS - Analogue Input Points (Status Full Set)

This is the complete set of analogue status points available from the controller.
All analogues in the full analogue data set can fit in a signed 16-bit DNP3 data object
except where noted.
DNP3 Implementation
LBS Analogue Input Points (Status Full Set)
Dead Band
DNP3-ID
Default
Name
Class
Units
Max
Min
System Line Currents and Power

0 A-Phase Current 0 16000 1A 10 A. 1
1 B-Phase Current 0 16000 1A 10 A. 1
2 C-Phase Current 0 16000 1A 10 A. 1
3 (Earth / Ground) Current 0 16000 1A 5 A. 1
1.9
4 System kVA Note 2 0 1 kVA 250 kVA. 1
GVA
1.9
5 System kVAR Note 2 0 1 kVAR 250 kVAR. 1
GVAR
1
6 Operations Counter 0 65535 1 Operation 2
Operation
Voltage Measurements (Earth/Ground)
Voltage measurements are provided for all terminals with voltage measurements.
The source/load voltage designation is determined by the user. Refer to the Power Flow Direction
binary input for status and binary output for control.
All voltages have a common deadband which can be configured (refer section 4.3.5).
7 Ai Phase-(Earth/ Ground) 0 30000 1V 100 V 2
Voltage
8 Bi Phase-(Earth / Ground) 0 30000 1V 100 V 2
Voltage
9 Ci Phase-(Earth / Ground) 0 30000 1V 100 V 2
Voltage
10 Ax Phase-(Earth / Ground) 0 30000 1V 100 V 2
Voltage
11 Bx Phase-(Earth / Ground) 0 30000 1V 100 V 2
Voltage
N00-324 R54 82
Dead Band
DNP3-ID
Default
Name
Class
Units
Max
Min
12 Cx Phase-(Earth / Ground) 0 30000 1V 100 V 2
Voltage
Fault Detection Data
These analogue points record data about the fault detection including maximum fault currents.
These are derived from the max current events, which are seen in the Operator Control Panel event
record and record the current for each phase and for earth/ground.
For any one fault more than one fault current can be set. For example a Phase/Phase fault might set
an A-Phase current and a B-Phase current.
Other data recorded includes the supply interrupt count and the Detection Group which was active at
the time of the fault detection.
Fault Detection Data is cleared to zero by the following actions :-
New fault detected
This data is volatile, that is they are zeroed on controller software reset.
If there is more that one protocol running simultaneously in the controller this data is replicated
between the protocols so that each master station can clear its data independently from the others.
13 Active Detection Group 0 9 1 1 1
The number of the Detection
Group which was active during
the sequence.
14 Supply Interrupt Count 1 10 1 1
The number of Supply
Interrupts Counted.
15 Most Recent A-Phase Fault 0 16000 Amps 1A 1
Written on a Max Current event
for A Phase
16 Most Recent B-Phase Fault 0 16000 Amps 1A 1
for B Phase
17 Most Recent C-Phase Fault 0 16000 Amps 1A 1
for C Phase
18 Most Recent Earth/Ground 0 16000 Amps 1A 1
Fault Current Written on an
E-Max event. This includes
Voltage Measurements (Phase/Phase)
19 A-Bi Phase-Phase Voltage 0 38000 1V 100 V 2
Note 2
20 B-Ci Phase-Phase Voltage 0 38000 1V 100 V 2
Note 2
21 C-Ai Phase-Phase Voltage 0 38000 1V 100 V 2
Note 2
22 A-Bx Phase-Phase Voltage 0 38000 1V 100 V 2
Note 2
23 B-Cx Phase-Phase Voltage 0 38000 1V 100 V 2
Note 2
N00-324 R54 83
Dead Band
DNP3-ID
Default
Name
Class
Units
Max
Min
24 C-Ax Phase-Phase Voltage 0 38000 1V 100 V 2
Note 2
System Status
25 System Power (kW) - 1.9GW 1 kW 250kW. 1
This can be a signed quantity 1.9
that indicates direction of power GW
flow, or an unsigned quantity
that is always positive
regardless of the direction of
the power flow. This is
determined by the controller
configuration
Note 2
26 System Power Factor 0.0 1.0 0.1 0.1 1
Note 6
27 Gas Pressure, kPag. - 300 1 kPaG 5kPaG 2
Note 3 100
28 Gas Pressure, psi Note 3 -14 44 1 psi 1psi 2
29 Code Version Note 2, 4 0 99,999,999 1 1 0
30 Configuration Number Note 2, 5 0 99,999 1 1 0
31 CAPM Serial Number 0 2147483647 1 1 0
32 LBS Serial Number Note 2 0 2147483647 1 1 2
33 I/U Contact Life Note 7 0.0 100.0 0.1 % 0.1 % 2
34 II/V Contact Life Note 7 0.0 100.0 0.1 % 0.1 % 2
35 III/W Contact Life Note 7 0.0 100.0 0.1 % 0.1 % 2
36 Transmitted frame count 0 32768 1 1 0
37 Received frame count 0 32768 1 1 0
38 Received message length error 0 999 1 1 0
39 Received message CRC error 0 999 1 1 0
Detection State
40 Cold Load 0 480 1 Min 1 Min 2
Value is zero when Cold Load
is Idle or OFF. When Cold Load
is not idle this shows the
operational cold load time, i.e.
the current time being used to
calculate the operational cold
load threshold multiplier.
41 Detection Group currently 0 9 1 1 2
selected
0 = Detection Group A
1 = Detection Group B
n = Other Detection Group
Miscellaneous
42 Maximum Average Current of 0 16000 1A 10A 1
all phases for the previous day
ending at 24:00 (2sec filter
window)
N00-324 R54 84
Dead Band
DNP3-ID
Default
Name
Class
Units
Max
Min
43 Generator Control State 0 8 1 1 2
0 Generator Control OFF
1 Switch Closed
2 Line Dead Check
3 Wait Switch Open
4 Wait Generator Live
5 Generator Running
7 Line Live Check
8 Wait Switch Closed
47
- Reserved
53
Note
1. The deadband for all analogue points can be configured, refer section 4.3.5 for
more information.
2. These points may exceed the 16 bit limit and can be obtained using 32 bit
analogue input objects.
3. If LBS Memory Data Invalid binary status is set then value is 0
4. The code version is an eight digit number that has the form XXX-XXX.XX with the
dash and point formatting removed.
5. The configuration number is a five digit number that has the form XXXXX. It
identifies the configuration loaded into the controller database.
6. Power factor has a built in scale factor of 10 i.e. range 0.0 to 1.0 with resolution
0.1 is transmitted as 0 to 10 with resolution 1.
7. Contact life has a built in scale factor of 10 i.e. range of 0.0% to 100.0% with
resolution 0.1% is transmitted as 0 to 1000 with resolution 1.
configuration and is otherwise always reported as zero.
N00-324 R54 85
Appendix M LBS - Counter Points

DNP3 Implementation
Binary Counters
Static Object: Object 20 Variation 05 32 Bit Binary Counter without Flag
Request Function Codes: 01 Read, 07 Immediate Freeze,
08 Immediate Freeze, No Ack, 09 Freeze and Clear
10 Freeze and Clear, No Ack
Frozen Counters
Static Object: Object 21 Variation 9 32 Bit Frozen Counter without Flag
LBS Counter Points

DNP3 ID
Name
Units
Max
Min
0 KWH Cumulative Note 1 0 2147483647 KWH

1 Source Outages Note 2, 3 0 2147483647 Counts
2 Source Outage Duration 0 2147483647 Seconds
Note 2, 3
3 Load Outages Note 2, 3 0 2147483647 Counts
4 Load Outage Duration 0 2147483647 Seconds
Note 2, 3
Note:
1. This accumulates the total kWH flowing through the LBS.
If the controller is set for Power Flow Unidirectional then the cumulative total increases
irrespective of the direction of power flow to show the total power that has passed
through the device.
If the controller is set for Bi-Directional power flow then the cumulative total can
increase or decrease reflecting the nett power flow.
2. Resetting any Outage counter via a protocol counter reset command will result in the
resetting of all outage counters.
Power Flow Direction Binary Input for status and Binary Output for control.
N00-324 R54 86
Appendix N LBS - Binary Output Points

Changing some of these settings affects the currently active Detection group. The change
equivalent to selecting that Detection group on the operator control panel, changing the
All binary output points have a matching binary input status point. The controller can
optionally return binary output object status in response to a class 0 or an integrity poll. It
is recommended that the master station use the controls corresponding binary input
DNP3 Implementation
Binary Output Status
Static Object: Object 10 Variation 02 Binary Output Status
The status of the offline/online bits is determined by the reject conditions shown in
the table below, or Output Control (See Database Parameters). A point is reported
offline if it cannot be forced to the alternate state due to condition listed. Note that
not all conditions that prevent a control from succeeding are listed. Some conditions
(eg mechanical failure) may be undetermined at time of read.
Request Function Code: 01- Read
Relay Control Block
Control Object: Object 12 Variation 01 Control Relay Output Block
Control relay output block parameters supported:
Control types are accepted on per point basis as shown in the table below.
TC = Trip/Close, P = Pulse ON/OFF, L = Latch ON/OFF.
Set (1) = Close, Pulse ON, Latch ON
Cleared (0) = Trip, Pulse OFF, Latch OFF
Recommended control types is shown in bold font.
Note: Pulse OFF is not supported on most master station systems, or the most
recent DNP3 Standard.
The count, on-time, off-time, queue, and clear parameters are ignored.
Multiple controls in the one message are not recommended.
Response Codes: Refer to Appendix C for a table of reported status values
LBS Binary Output Points

Cleared =
DNP3 ID
Set = 1
Control
Name
Type
0
0 LBS Control Close Trip TC,

Rejected if: Rejected if: L, P
Close coil is Trip coil is isolated
isolated SF6 gas pressure is
controller is in low (if applicable)
LOCAL control Switchgear data
mode
N00-324 R54 87
Cleared =
DNP3 ID
Set = 1
Control
Name
Type
0
SF6 gas pressure invalid
is low (if Mechanically
applicable) AND interlocked.
low gas lockout is
ON
Work Tag is
applied
Switchgear data
invalid
Mechanically
interlocked
Live load blocking
ON AND any load
side terminal live
Trip and/or Close
capacitors are
charging or failed
Generator Control
has close blocking
on
1 Work Tag Applies Work Tag. Removed the Work L, P
Rejected if: Tag.
controller is in Rejected if:
LOCAL Mode controller is in
LOCAL Mode.
2 Cold Load Idle/Max Set cold load time to its Set cold load time to L, P
maximum value. This zero. This means that
means that the cold the threshold multiplier
load threshold current will not be affected by
will be set to its the cold load function.
maximum value Rejected if:
Rejected if: Cold load support is
Cold load support OFF
is OFF
3 Live Load Blocking Live Load blocking ON Live Load blocking OFF L, P
4 Reset Fault Resets all Object 30 No Action L, P
Flags and Currents Fault Currents to zero
Note 1 and clears all Object 01
Detection trip flags
5 Power Flow Direction Note 4 Source X, Load I Source I, Load X L, P
(Source and Load Bushings) Note 6
6 Detection Group A Note 1, 3 Group A ON Note 5 No Action L, P
7 Detection Group B Note 1, 3 Group B ON Note 5 No Action L, P
8 Detection Group C Note 1, 3 Group C ON Note 5 No Action L, P
9 Detection Group D Note 1, 3 Group D ON Note 5 No Action L, P
10 Detection Group E Note 1, 3 Group E ON Note 5 No Action L, P
11 Detection Group F Note 1, 3 Group F ON Note 5 No Action L, P
12 Detection Group G Note 1, 3 Group G ON Note 5 No Action L, P
13 Detection Group H Note 1, 3 Group H ON Note 5 No Action L, P
14 Detection Group I Note 1, 3 Group I ON Note 5 No Action L, P
N00-324 R54 88
Cleared =
DNP3 ID
Set = 1
Control
Name
Type
0
15 Detection Group J Note 1, 3 Group J ON Note 5 No Action L, P
16 Dummy Circuit Breaker DCB Close DCB Trip TC,
L, P
17 Automatic Detection Group APGS ON APGS OFF L, P
Selection Rejected if:
APGS ON is Not
Allowed
Loop Auto ON
18 Supply Outage Measurement Supply Outage Supply Outage L, P
Control Measurement ON Measurement OFF
19 Supply Outage Measurement Resets all Supply No Action L, P
Reset Outage counters
values.
20 Sectionaliser Auto Turn Sectionalising ON Turn Sectionalising L, P
OFF.
21 Protocol IOEX control 1 Sets IOEX output that Clears IOEX output that
22 Protocol IOEX control 2 is mapped to this point. is mapped to this point.
23 Protocol IOEX control 3 Used for protocol Used for protocol
control. control.
24 Protocol IOEX control 4
TC,
25 Protocol IOEX control 5 Note: The Control Note: The Control Type L, P
26 Protocol IOEX control 6 Type depends on the depends on the
27 Protocol IOEX control 7 assignment in the assignment in the IOEX
IOEX mapping. mapping.
28 Protocol IOEX control 8
29 Reserved
30 Reserved
31 Reserved
32 Generator Control Turn Generator Control Turn Generator Control L, P
On Off
Switch is ACR Switch is ACR
Generator Control
is not available
Loop Automation is
available.
Auto-Changeover
is enabled.
Note:
1. The response for binary output status for these points will always be 0.
configuration otherwise No Action is taken.
3. Only one Detection group can be active at any one time. Activating any of these
Detection groups will automatically reset the previously active setting.
4. Changing the Source/Load direction affects the following aspects of the operation of
the controller:
N00-324 R54 89
Whether the source or load corresponds to I side or X side on the voltage

measurements
Which side is the source or load for the Live Load Blocking
Which side is the source or load for the Directional Blocking
Which direction is positive power flow for the System Power Analogue Input
Power Flow Direction Binary Input status
5. The number of protection groups available in the controller is configurable. If a control
is not available because the protection set is not supported then it is rejected.
N00-324 R54 90
Appendix O LBS - Analogue Output Points

Changing some of these settings affects the currently active Detection group. The change
equivalent to selecting that Detection group on the operator control panel, changing the
All analogue output points have a matching analogue input point. The controller does not
return analogue output object status in response to a class 0 or and integrity poll. It is
recommended that the master station use the outputs corresponding analogue input
DNP3 Implementation
Analogue Output Status
Static Object: Object 40 Variation 02 16 Bit Analogue Status
The status of the offline/online bits is determined by Output Control (See Database
Parameters). A point is reported offline if it cannot be forced to the alternate state.
Analogue Output Block
Control Object: Object 41 Variation 02 16 Bit Analogue Output Block
Response Codes: Refer to Appendix C for a table of reported status values.
LBS Analogue Output Point

DNP3 ID
Name
Units
Max
Min
0 Detection Group Selected 0 9 N/A

0 = Group A
1 = Group B

9 = Group J
Note:
1. The number of protection groups available in the controller is configurable. If the
analogue output block value is not available because the protection set is not
supported then it is rejected.
N00-324 R54 91
Appendix P PAKNET Call Procedures

The PAKNET is a private X.25 network. There are a number of ways of accessing the
network. The mechanism most commonly used by remote devices such as the CAPMs is
via a radio PAD.
When the master station wishes to communicate with a particular device, it must first
establish an X.25 connection to the device. Similarly, when the IED requires the master
station to poll it for changes, it must establish a connection with the master station.
Most X.25 based systems are configured so as to minimise call costs and connection
costs. They generally operate on a slow scan rate and rely on the outgoing call
mechanism (described below) to achieve responsiveness.
There are two options described for monitoring and controlling the PADs. The first has the
PADs service signals disabled. The second option has service signals enabled.
Incoming Call (Poll or Control) Service Signals Disabled
Incoming Calls (from the CAPMs viewpoint) are those calls that are initiated by the Master
Station. The master stations routine polls and control requests fit into this category and
require that the master station establish an X.25 connection to the PAD to which the
CAPM is connected.
In order that the CAPM and its associated PAD can accept incoming calls at any time, the
CAPM maintains DTR asserted at all times. It only lowers DTR to clear an out-going call
(see below).
The sequence for are incoming call is as follows:
1. DTR is asserted.
2. The master station establishes the X.25 connection.
3. Initialise / Data Request or Control / Poll sequence is transmitted by the master
station.
4. The CAPM transmits the requested data.
5. Steps 2 and 3 are repeated until poll / control is completed.
6. The call is cleared by the master station.
Outgoing Call (Unsolicited CoS) Service Signals Disabled

The DNP protocol does not support unsolicited data transfer to the master station.
However, unsolicited behaviour is emulated by taking advantage of the DNP address
resolution mechanism using a broadcast scan. With this technique, the IED dials-in to the
master station (or, in the case of the PAKNET, establishes an X.25 connection). The
master station, on detecting an incoming call for an IED, transmits a broadcast message.
From the IEDs reply to this broadcast, the master station determines its address and then
commences a conventional scan sequence.
The CAPM performs an outgoing call whenever is has a change of state to report.
The outgoing call procedure is as follows:
1. DTR is asserted.
2. The CAPM establishes an X.25 connection to the master station.
3. The master station sends an INITIALISE with a Broadcast address.
4. The CAPM transmits the INITIALISE reply with its IED address to the master.
5. The master station sends data requests and a POLL
6. The CAPM replies with the requested data.
7. Steps 6 and 7 are repeated until all data requests are complete.
8. The call is cleared by the Master Station.
Outgoing Call Failure and Retry Mechanism

If the CAPM fails to establish communication with the master station when an outgoing call
is made, then the outgoing call is retried. The retry sequence is as follows:
N00-324 R54 92
1. The CAPM sends the call connection sequence to the PAD.

2. The CAPM waits for the Tx on-line period. If a valid scan has not been received by
the CAPM, the call is cleared down.
3. The CAPM waits for the Retry Timer to expire.
4. Adjust the Retry Timer by the multiplier factor. If the Retry Timer exceeds the Max
Retry Interval then set the Retry Timer equal to the Max Retry Interval.
5. Go to step 1.
Incoming Call (Poll or Control) Service Signals Enabled
Incoming Calls (from the CAPMs viewpoint) are those calls that are initiated by the Master
Station. The master stations routine polls and control requests fit into this category and
require that the master station establish an X.25 connection to the PAD to which the
CAPM is connected.
In order that the CAPM and its associated PAD can accept incoming calls at any time
without having to monitor RI, the CAPM maintains DTR asserted at all times. It only
lowers DTR to clear an out-going call (see below).
1. DTR is asserted.
2. The master station establishes the X.25 connection.
3. The CAPM strips off the leading NUA and COM characters.
4. Initialise / Data Request or Control / Poll sequence is transmitted by the master
station.
5. CAPM transmits the requested data.
6. Steps 4 and 5 are repeated until poll / control is completed.
Outgoing Call (Unsolicited CoS) Service Signals Enabled

The DNP protocol does not support unsolicited data transfer to the master station.
However, unsolicited behaviour is emulated by taking advantage of the DNP address
resolution mechanism using a broadcast scan. With this technique, the IED dials-in to the
master station (or, in the case of the PAKNET, establishes an X.25 connection). The
master station, on detecting an incoming call for an IED, transmits a broadcast message.
From the IEDs reply to this broadcast, the master station determines its address and then
commences a conventional scan sequence.
The CAPM performs an outgoing call whenever is has a change of state to report.
The outgoing call procedure is as follows:
1. DTR is asserted.
2. The CAPM sends a <CR> character to the PAD and waits for a prompt (*)
character from the PAD. (See below for a description of the failure sequence).
3. At the prompt character, the CAPM will transmit the master stations NUA followed
by the <CR> character.
4. The PAD returns the connected NUA followed by COM when the connection has
been established. (See below for a description of the failure sequence).
5. When the master station sees a connection established from a IED, it sends an
INITIALISE with a Broadcast address.
6. The CAPM transmits the INITIALISE reply with its IED address to Master.
7. The master station sends data requests and a POLL
8. The CAPM replies with the requested data.
9. Steps 6 and 7 are repeated until all data requests are complete.
N00-324 R54 93
Outgoing Call Failure and Retry Mechanism

If the CAPM fails to establish communication with the master station when an outgoing call
is made or it fails to establish the X.25 connection, various retry mechanisms are invoked.
The retry sequences are as follows:
1. The CAPM sends a <CR> character to the PAD and waits for a prompt (*)
character from the PAD.
2. If it fails to receive a prompt it will send another <CR> character after 5 seconds. If
it still fails to receive a prompt character after three attempts it will drop DTR and
repeat the sequence.
3. After sending the NUA followed by <CR> to the PAD, the CAPM waits for
connection acknowledgment consisting of the called NUA followed by COM.
4. If the CAPM fails to see COM after the Tx On-line period, it will drop DTR (for DTR
Low Time seconds) and then retry steps 1 to 3.
5. If the CAPM receives COM but fails to see any communication from the Master
Station after the Tx On-line period, it will drop DTR (for DTR Low Time seconds)
and initiate and application retry sequence.
6. The CAPM waits for the Retry Timer to expire.
7. The CAPM adjusts the Retry Timer by the multiplier factor. If the Retry Timer
exceeds the Max Retry Interval then set the Retry Timer equal to the Max Retry
Interval.
8. Go to step 1.
N00-324 R54 94

N00-324 DNP3 Protocol Technical Manual CAPM4-5

Uploaded by

Document Information

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

N00-324 DNP3 Protocol Technical Manual CAPM4-5

Uploaded by

Copyright:

Available Formats

DNP3 Protocol

Document Part No: N00-324

Copyright Schneider Electric (Australia) Pty

Schneider Electric (Australia) Pty Limited.

Public Access: \stdprod\N00\N00-324R54.pdf

Revision Author Date Comment

N00-324 R54 Page ii

Reworded analogue input deadband section

N00-324 R54 Page iii

Added the map field to Database Configuration 2 page

N00-324 R54 Page iv

N00-324 R54 Page v

Appendix G ACR - Counter Point...................................................................................... 65

N00-324 R54 Page vi

---- DNP Transmission Services 1 ----S

---- DNP Transmission Services 2 ----S

A setting of OFF allows the controller to accept out of sequence

Either way - the operate Application Layer request message must be

4.1.3. Use of Application and Data Link Confirmation/Retries

--------- DNP Unsolicited 1 --------S

--------- DNP Unsolicited 2 --------S

--------- DNP Unsolicited 3 --------S

--------- DNP Unsolicited 4 ---------S

An IDENTICAL unsolicited response retry - is a repeat, octet-for-

Range: Unsol REGENERATED / IDENTICAL

Selection of REGENERATED- or IDENTICAL- unsolicited response-retries is an

The protocol does not allow class 0 (Zero) to be assigned remotely.

4.3.2. Database Parameters

----- DNP Database Configuration 1 ---S

----- DNP Database Configuration 2 ---S

Class 1,2 or 3 Analog input change events can be reported in

Range: BUF ALL / PRESENT.

Note: Only the operation of DNP outputs is affected. Operation

Range: NORMAL, SCADA

4.3.3. Database Size Permutations

Controller Configuration Field

Binary counter status (Object 20 variation 05),

4.3.5. Analogue Deadband Parameters

-------- DNP Default Deadbands -------S

System Power System Power Default Deadband

LOW + 10% (HIGH LOW

4.3.7. Analogue Alarm Parameters

---- DNP High Alarm Configuration ---S

---- DNP Low Alarm Configuration ----S

alarm threshold set to this value.

-------- DNP Communications 1 ------S

-------- DNP Communications 2 ------S

-------- DNP Communications 3 ------S

P8 RS-232 When P8 RS 232 is selected, the protocol uses the P8 serial

Range: CTS Ignore, CTS Dont Ignore

X.25 Connection Parameters

-------- DNP PAKNET Settings -------

Communications Retry Parameters

----- DNP PAKNET Call-Out Timers ----

5.3. V23 FSK Communication Specifications

Standard Cable P10 Pin Direction Use

4 4 To controller Receive, 10kOhm impedance

Signal frequencies conform to V23 standard.

-------- DNP Communications 1 ------S

-------- DNP Communications 2 ------S

-------- DNP Communications 3 ------S

OFF When OFF is selected, the protocol handler is disabled.

P8 RS-232 When P8 RS 232 is selected, the protocol uses the P8 serial

Back off time = CA Delay + ([random delay with range 0.0 to