N00 324rev39

NU-LEC INDUSTRIES PTY LTD
A Schneider Electric Company
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
Nu-Lec Automatic Circuit Reclosers and Load Break Switches using CAPM-4/5
controllers.
Preliminary
Document Part No:
N00-324
Document Revision Level: R39
COPYRIGHT NU-LEC INDUSTRIES PTY LTD 2001
DNP V3.00 Protocol Technical Manual
Nu-Lec Industries Pty Ltd.

ACN 085 972 425
37 South Street,
Lytton,
QLD 4178,
Australia.
Tel +61 7 3249 5444
Fax +61 7 3249 5888
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 Nu-Lec
Industries Pty Ltd.
This document discloses confidential intellectual property that belongs to Nu-Lec
Industries P/L. This document does not invest any rights to Nu-Lec Industries 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 Nu-Lec Industries Pty Ltd.
Public Access: \stdprod\N00\N00-324R39.pdf
Source: \R&D\CAPM4\manuals\N00-324.doc
N00-324 R39

Revision Control
Revision
R18
Author Date
LM
31/08/99
Comment
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
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
N00-324.doc R39
Page ii

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
R31
LM
1-Mar-2001
Added IIN1-4 to device profile
Extended support include CAPM5 controllers.

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.
N00-324.doc R39
Page iii
Contents
1
2
3
4
Introduction............................................................................................................... 1
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
2.6 Year 2000 Compliance Statement...................................................................... 2
SCADA System Design ............................................................................................ 3
Applicability............................................................................................................... 4
4.1 Control Cubicle Software .................................................................................... 4
4.2 DNP3 Protocol.................................................................................................... 4
4.3 Switchgear Type................................................................................................. 4
4.4 Terminology........................................................................................................ 4
Protocol Configuration .............................................................................................. 5
5.1 Transmission Services Configuration ................................................................. 5
5.1.1 Overview ............................................................................................................. 5
5.1.2 Transmission Services Parameters..................................................................... 5
5.1.3 Use of Application and Data Link Confirmation/Retries....................................... 7
5.2 Unsolicited Response Configuration................................................................... 8
5.2.1 Overview ............................................................................................................. 8
5.2.2 Unsolicited Response Parameters ...................................................................... 8
5.2.3 Event Buffering.................................................................................................. 12
5.3 Data Configuration............................................................................................ 12
5.3.1 Overview ........................................................................................................... 12
5.3.2 Database Parameters ....................................................................................... 13
5.3.3 Database Size Permutations............................................................................. 14
5.3.4 Default Database Data Objects......................................................................... 15
5.3.5 Analogue Deadband Parameters ...................................................................... 16
Analogue Alarm Reporting ......................................................................................... 17
5.3.7 Analogue Alarm Parameters ............................................................................. 18
Physical Layer ........................................................................................................ 20
6.1 Communications Ports Supported .................................................................... 20
6.2 RS-232 Communication Specifications ............................................................ 20
6.2.1 RS-232 Hardware Signals................................................................................. 20
6.2.2 RS-232 Character Definition ............................................................................. 20
6.2.3 RS-232 Configuration Parameters .................................................................... 20
6.2.4 Carrier Detect.................................................................................................... 24
N00-324.doc R39
Page iv

6.2.5 Transmitting a DNP3 Packet ............................................................................. 24
6.2.6 DTR................................................................................................................... 25
6.2.7 Dialling Modem Support .................................................................................... 25
6.2.8 PAKNET Configuration ..................................................................................... 25
6.3 V23 FSK Communication Specifications .......................................................... 27
6.3.1 V23 Hardware Signals ...................................................................................... 27
6.3.2 V23 Configuration Parameters .......................................................................... 28
6.3.3 V23 Handshaking Signals ................................................................................. 32
6.4 Communication Statistics ................................................................................. 32
Appendix A Protocol Timings ............................................................................................ 34
Appendix B DNP3 Device Profile ...................................................................................... 35
Appendix C DNP3 Implementation Table.......................................................................... 38
Appendix D ACR - Binary Input Points (Status) ................................................................ 44
Appendix E ACR - Analogue Input Points (Status - Small Set) ......................................... 56
Appendix F ACR - Analogue Input Points (Status Full Set)............................................ 58
Appendix G ACR - Counter Point...................................................................................... 64
Appendix H ACR - Binary Output Points ........................................................................... 65
Appendix I ACR - Analogue Output Points........................................................................ 70
Appendix J LBS Binary Points Data (Status).................................................................. 71
Appendix K LBS - Analogue Input Points (Status - Small Set) .......................................... 77
Appendix L LBS - Analogue Input Points (Status Full Set)............................................. 80
Appendix M LBS - Counter Points..................................................................................... 84
Appendix N LBS - Binary Output Points ............................................................................ 85
Appendix O LBS - Analogue Output Points....................................................................... 88
Appendix P PAKNET Call Procedures .............................................................................. 89
Incoming Call (Poll or Control) Service Signals Disabled .................................... 89
Outgoing Call (Unsolicited CoS) Service Signals Disabled ................................. 89
Outgoing Call Failure and Retry Mechanism .......................................................... 90
Incoming Call (Poll or Control) Service Signals Enabled ..................................... 90
Outgoing Call (Unsolicited CoS) Service Signals Enabled .................................. 90
Outgoing Call Failure and Retry Mechanism .......................................................... 91
N00-324.doc R39
Page v
1 Introduction
This document describes the Nu-Lec 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 Nu-Lec 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 Nu-Lec 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
N00-324 R39

Line Currents and Voltages
Time tags are optional. If enabled, these status points are returned with time tags of either
10 or 500 millisecond resolution.
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.
Default data object type with/with out flag/time; analogue size
Point class assignment.
2.4 Password Protectio n

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 Nulec Industries or your distributor.
Use of DNP3 for LBS switchgear is only available with CAPM V25.01.00+ software.
2.6 Year 2000 Complia nce Statement

The DNP3 protocol software complies with rules 1, 2, 3 and 4 of the British Standards
Institute Year 2000 Conformity Requirement (DISC PD2000-1 A Definition of Year 2000
Conformity Requirements). A copy of this statement can be found on the Nu-Lec
Industries Pty Ltd web site (http://www.nulec.com.au/).
N00-324.doc R39
Page 2
3 SCADA System Design

It is recommended that the SCADA system engineer reads the rest of this manual and
discusses the options for implementation that this protocol implementation provides with
the operations staff.
Some SCADA system implementation options are.
Build Screens using the Status Points and use their time tags to generate SCADA
system events.
Build Screens using the Status Points and use the Event Points to generate the
SCADA system events. This means that the SCADA system event log will
replicate the controller event log.
Build Screens using the Status Points and use their time tags to generate SCADA
system events.
There are many other configuration parameters for the protocol such as data rate, device
address etc. refer to section 5.
The controller has a fixed set of functionality and the point mapping has been
implemented to reflect this by providing the sets of data points described in the
appendices. The SCADA engineer has the ability to select from a variety of points sets
and to configure some aspects of the point mapping as described in section 5.3.
N00-324.doc R39
Page 3
4 Applicability
4.1 Control Cubicle So ftware
This document applies to Nu-Lec pole top reclosers and load break switches using a
CAPM Controller which displays DNP3 Manual N00-324R39+ 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.
4.2 DNP3 Protocol

The protocol version implemented by Nu-Lec 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 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/.
4.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
4.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.doc R39
Page 4
5 Protocol Configuration
The DNP3 protocol handler adds several pages to the System Status menus.
additional pages fall into the following groups,
The
Transmission Services Configuration (refer Section 5.1)

Unsolicited Response Configuration (refer Section 5.2)
Data Configuration (refer Section 5.3)
Communications Configuration (refer Sections 6.2 and 6.3)
Communication Statistics (refer Section 6.4)
All protocol configuration parameters can be viewed, modified and stored on a personal
computer with the WSOS utility.
5.1 Transmission Serv ices Configuration

5.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
5.1.2 Transmission Serv ices 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
84000ms
Arm Select 10000ms
---- DNP Transmission Services 2

DNP Address
5 Time Dly Rq
Parameter
DL Cf Rqd
N00-324.doc R39
----S
0min
Description
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.
Page 5

Parameter
Description
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.
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 transmission of the last byte of a
frame.
If an acknowledge frame is not received from the master station within 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
Retries
Data Link Maximum 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 a
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 5.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 for correct
operation of the confirm timeouts Apl Cf TO must be set using the
N00-324.doc R39
Page 6

Parameter
Description
following formula:
Apl Cf TO >= ((DL Max Retries + 1) x DL Cf TO x 7)
The controller calculates this value and automatically overwrites a
value that is entered which is less than the calculated value.
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.
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
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 Nulec DNP3
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
5.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.
N00-324.doc R39
Page 7

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 controller 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 slaves frequently and controller unsolicited
responses are not used then it is recommended that only the master be configured to use
data link confirmations and retries. It is the master stations responsibility to gather data. If
the master station detects a communication failure and moves on to poll the next device
on a multi-drop communication link whilst the controller is performing retries then collisions
will occur.
For more information refer to the DNP3 User Group Technical Bulletin 9804-002 DNP
Confirmation and Retry Guidelines.
5.2 Unsolicited Respon se Configuration

5.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

Note that 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.
The event class of DNP3 binary and analogue points can be configured using WSOS.
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.
5.2.2 Unsolicited Respon se Parameters
--------- DNP Unsolicited 1 --------S

Unsolicited
OFF Master Addr
3
Unsol Retries
255 Unsol Dly
90s
N00-324.doc R39
Page 8
--------C1 Count
C2 Count
C3 Count
DNP Unsolicited 2
1 C1 Delay
3 C2 Delay
5 C3 Delay
--------S
1s
5s
10s
--------- DNP Unsolicited 3 --------S

C1 Timeout
0s C1 Buffered
0
C2 Timeout
0s C2 Buffered
0
C3 Timeout
0s C3 Buffered
0
Parameter
Unsolicited
Note 1
Description
Enable/Disable Unsolicited Responses
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 only the events for that class are transmitted. Any
other classs events remain stored in the controllers buffer.
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:
1. 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.
2. 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.
N00-324.doc R39
Page 9

Parameter
Description
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.
Range: OFF, ON, FORCED.
Factory default is OFF
Master Addr
Note 1
DNP3 Master Station Address

This is the DNP3 address to which the unsolicited responses are
sent.
If the controller is set up to communicate with WSOS using Nulec
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 5.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 90s
C1 Count
Unsolicited Response Class 1 Notification Max Count

The number of events which must occur in Class 1 before they
will be reported.
N00-324.doc R39
Page 10

Parameter
Description
Range: 1 to 255
Factory default is 1 event.
C2 Count

will be reported.
Range: 1 to 255
Factory default is 3 events.
C3 Count

will be reported.
Range: 1 to 255
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.
C2 Delay

C3 Delay

C1 Timeout
Unsolicited Response Class 1 Notification Time

The number of seconds remaining before an unsolicited response
class 1 transmission. (Display only)
C2 Timeout

C3 Timeout

C1 Buffered
Unsolicited Response Class 1 Buffered Events

The number of queued events in the unsolicited response class 1
buffer. (Display only)
C2 Buffered

C3 Buffered

N00-324.doc R39
Page 11

Note
1. 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.
5.2.3 Event Buffering

Multiple DNP3 change of state events can be transmitted in the same message. 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 either waits for
the retry delay timer (Unsol Dly) to expire before attempting to send another unsolicited
response. The new unsolicited response message is not an identical retry of the failed
message but may contain the same data. All message identification parameters (eg
sequence numbers) are incremented.
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.

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.
5.3 Data Configuration

5.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) based on the operational
requirements and transmission bandwidth available, particularly during an integrity
poll. Refer to appendices for points lists.
Enabling / Disabling event points.
N00-324.doc R39
Page 12
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.
5.3.2 Database Paramete rs

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

Analogue Alarms OFF
Binary Time
ON
Analogue Size 16bit
Configuration 1 ---S
Analogue Pnts SMALL
Analogue Time
OFF
Analogue Flag
OFF
----- DNP Database Configuration 2 ---S

Binary Output OFF
Parameter
Description
Analogue Alarms
Analogue Alarming Operation

This field determines if analogue threshold alarming is enabled
or disabled.
If ON, 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 alarming is not effected by
whether the analogues are in the configured Analogue Pnts set.
If OFF, alarms are disabled. All binary alarm points are cleared.
Refer to section 5.3.6 for more information.
Range: OFF, ON
Analogue Pnts
Analogue Point Set

This field determines which, if any, of the analogue point
mapping sets are included in the controllers DNP3 Points list. A
summary of all the available mapping permutations is given in
section 5.3.3.
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
N00-324.doc R39
Page 13

Parameter
Description
queued events will be deleted.
Range: OFF, SMALL, FULL
Factory default is SMALL.
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
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
5.3.3 Database Size Perm utations

To enable optimisation of communication bandwidth, three binary and analogue input
point sets are available. The selection of a set will determine the size of the logical
N00-324.doc R39
Page 14

database used by the controllers DNP3 protocol handler and thus determine the size of
an integrity poll response.
ACR
Analogue
Points
Binary Point Table(s)
Analogue Point Table(s)
OFF
Appendix D
No analogues
SMALL
Appendix D
Appendix E
FULL
Appendix D
Appendix F
LBS
Analogue
Points
Binary Point Table(s)
Analogue Point Table(s)
OFF
Appendix J
No analogues
SMALL
Appendix J
Appendix K
FULL
Appendix J
Appendix L
5.3.4 Default Database D ata 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 Input Change without time
(Object 2 Variation 1)
Binary Input Change with time
Binary
Time Tag
Analogue
Time Tag
Analogue
Size
Analogue
Flag
32
ON
16
ON
32
OFF
16
OFF
OFF
ON
32 Bit Analogue Input

32 Bit Analogue Input without flag
16 Bit Analogue Input without flag
32 Bit Analogue Change Event without time
OFF
32
16 Bit Analogue Change Event without time

OFF
16
N00-324.doc R39
Page 15

Controller Configuration Field
DNP3 Data Object
Binary
Time Tag
Analogue
Time Tag
Analogue
Size
32 Bit Analogue Change Event with time

ON
32
16 Bit Analogue Change Event with time

ON
16
16 Bit Analogue Input Deadband

32 Bit Analogue Input Deadband
Analogue
Flag
16
32
The rest of the default data objects used by the controller are:
Binary input status (Object 01 variation 01),
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.
5.3.5 Analogue Deadban d 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
N00-324.doc R39
Page 16

Parameter
Description
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 phaseearth/ground voltages are effected.
Range: 1 to 38000V
Factory default is 100V.
Earth/Gnd
Current
Earth/Ground Current Default Deadband

The earth/ground current analogue input will have its deadband
set to this value.
Range: 1 to 999A
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.
5.3.6 Analogue Alarm Re porting

A/V/kW
H1
HIGH THRESHOLD
LOW + 90% (HIGHLOW)
HI ALARM ON
H2
HI ALARM OFF
Time
LOW ALARM OFF
LOW + 10% (HIGHLOW)

LOW THRESHOLD
L2
L1
LOW ALARM ON
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.
N00-324.doc R39
Page 17

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.
5.3.7 Analogue Alarm Pa rameters

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

Phase Current 999A Phase Voltage 38000V
Earth Current 999A System Power
54000
Parameter
Description
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 phaseearth/ground, is determined by the configuration of the controller.
Refer to the equipment manual for more information.
Range: 1 to 38000V
Earth/Gnd
Current
Earth/Ground Current High Alarm

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.
N00-324.doc R39
Page 18

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

Phase Current
0A Phase Voltage
Earth Current
0A System Power
Parameter
----S
0V
0
Description
Phase Current
Phase Current Low Alarm

The A, B and C phase current analogue inputs will have their low
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 phaseearth/ground, is determined by the configuration of the controller.
Refer to the equipment manual for more information.
Range: 0 to 37999V
Earth/Gnd
Current
Earth/Ground Current Low Alarm

The earth/ground current analogue input will have its low alarm
threshold set to this value.
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.
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.doc R39
Page 19
6 Physical Layer
6.1 Communications P orts Supported
The controller can communicate to the Master station via one of the following ports.
RS-232 Port P8 (refer to section 6.2)

V23 FSK Port P10 (refer to section 6.3)
6.2 RS-232 Communic ation 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
6.2.1 RS-232 Hardware S ignals

P8 Pin
Direction
Description
From controller
Tx Data (TxD)
To controller
Rx Data (RxD)
From controller
Request To Send (RTS)
To controller
Clear To Send (CTS)
Signal Ground
To controller
Carrier Detect (CD)
20
From controller
Data Terminal Ready (DTR)
The controller uses RTS/CTS hardware handshaking. If not supported by the master then
a loop back is required at the controller end of the communications link.
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.
6.2.2 RS-232 Character D efinition

RS-232 characters are 8 bit, 1 stop bit, no parity
6.2.3 RS-232 Configurati on 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

P8 RS-232
RUNNING
Pre-Tx
250ms Post-Tx
Baud
9600
N00-324.doc R39
------S
35ms
Page 20

Dialling
DISABLED
Pre-amble DISABLED First Char
Repeat First
3 Last Char
------S

DCD Ignore
CA Delay
Tx Delay
0ms
------S
1000ms
0x55
0xFF
None of these fields are configurable via WSOS if Nulec DNP3 communications is used.
Parameter
OFF
Description
Port Selection
This field selects the communications medium the DNP3 protocol
uses for transmission.
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
P10 V23 FSK
N00-324.doc R39
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.
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 6.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
Page 21

Parameter
RUNNING
INACTIVE
Protocol Status
Indication of the current status of the communications. (Display
only)
RUNNING means that the protocol handler has connected to the
communication port (P8 or P10) and is running.
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
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, 1200, 2400, 4800, 9600 or 192001 baud.
Factory default is 9600 Baud
Dialup Number
Dialling
DISABLED
Pre-amble
ENABLED
DISABLED
Description
PSTN Dial Up Number

The PSTN number that the protocol handler will call when it
needs to send an Unsolicited response. This field supports a
maximum of 18 digits.
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
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
ensures identification of the protocol message.
ENABLED means that the preamble characters are transmitted
prior to a protocol message.
DISABLED means that protocol message are transmitted without
any preamble characters.
19200 baud is only available with CAPM5 controllers.
N00-324.doc R39
Page 22

Parameter
Description
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
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 Ignore
DCD Dont
Ignore
CA Delay
N00-324.doc R39
DCD Usage
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
the protocol will transmit irrespective of the DCD input signal.
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
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
Page 23

Parameter
Description
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.
6.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 6.2.7
for more information.
6.2.5 Transmitting a DNP 3 Packet

Transmission of a DNP3 packet follows the steps below
1. RTS line is asserted
2. Controller waits until the pre-transmission delay expires (Delay set from the panel)
and CTS is asserted.
3. The pre-amble is transmitted (Optional. Set from the panel).
4. Checks CTS is asserted.
5. The DNP3 packet is transmitted
6. Waits until the post-transmission delay expires (Delay set from the panel)
N00-324.doc R39
Page 24

7. RTS is negated
6.2.6 DTR
DTR is asserted by the protocol handler at power-up or upon P8 selection.
6.2.7 Dialling Modem Su pport

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.
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.
6.2.8 PAKNET Configura tion

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.
6.2.8.1
X.25 Connection Parameters
N00-324.doc R39
Page 25
-------- DNP PAKNET Settings ------DTR Low Time 500ms Tx on line

5s
NUA Address
0
Parameter
DTR Low Time
Description
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.
Factory default is 5 seconds
6.2.8.2
Communications Retry Parameters
----- DNP PAKNET Call-Out Timers ---Min Retry

60s Max Retry
3600s
Multiplier
X 2
Timeout
12s
N00-324.doc R39
Page 26

Parameter
Min Retry
Description
Minimum Retry Time
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).
6.3 V23 FSK Communi cation Specifications

6.3.1 V23 Hardware Sign als
Standard Cable
Type N03-530
15 Way D Female
P10 Pin
Direction
Use
Signal Ground
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
N00-324.doc R39
Page 27

Level 2.5V pk-pk
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.
6.3.2 V23 Configuration Parameters

required for operation of the physical link between the recloser and the master station.
Parameter

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

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

DCD Dont Ignore
CA Delay
Tx Delay
0ms
------S
1000ms
35ms
Description
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 6.2 for the P8 configuration details.
N00-324.doc R39
Page 28

Parameter
P8 PAKNET
P8 PAKNET SS
P10 V23 FSK
RUNNING
INACTIVE
Description
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. Refer to
section 6.2 for the P8 configuration details.
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 6.2 for
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 means that the protocol handler has connected to
the communication port (P8 or P10) and is running.
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 means that a low input signal will assert BUSY.
HIGH means that a high input signal will assert BUSY.
Range: LOW, HIGH
LOW
HIGH
N00-324.doc R39
Page 29

Parameter
Description
Factory default is Busy Sense LOW.
Tx TEST
Transmission Mode
This field can be used to test the radio transmitter.
Tx NORMAL means that the protocol handler controls the radio
for normal DNP3 transmissions.
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.
Range: Tx NORMAL, Tx TEST
Factory default is Tx NORMAL.
Rx IDLE,
Rx BUSY
BUSY Signal Status

The status of the BUSY signal into the controller (Display only)
Rx IDLE indicates that the signal is in the not BUSY state.
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
Tx NORMAL
Pre-amble
ENABLED
DISABLED
Preamble Usage
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
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
N00-324.doc R39
Page 30

Parameter
Description
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
received data to build a DNP3 packet. The protocol is able to
DCD Dont Ignore 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

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
N00-324.doc R39
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.
Page 31

Parameter
Description
6.3.3 V23 Handshaking S ignals

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,
begins transmission. After transmission, the protocol waits for the post-transmission timer
to expire, and then negates PTT.
6.4 Communication St atistics

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
recloser into the DNP3 link.
Range: 0 to 32768
Rx Count
Receive Message Count

The number of DNP3 datalink messages received by this
recloser from the DNP3 link.
Range: 0 to 32768
N00-324.doc R39
Page 32

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.doc R39
Page 33
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.doc R39
Page 34
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.doc R39
Page 35
DNP3 Device Profile
DNP3 Device Profile
Vendor Name: Nu-Lec Industries P/L,

Brisbane, Australia
Highest DNP3 Level Supported
For Requests: 2
For Responses: 2
Device Name: CAPM-4 Controller
Device Function: Slave
Conforms to DNP3 level 2 subset definition requirements with many additional level 3 features built
in.
These extra features include the parsing of read requests (FC 1) for the following objects and/or
qualifiers:
Binary Input (Object 1 Variations 0 Qualifiers 00, 01,07,08,17,28)
Binary Input (Object 1 Variation 1 Qualifiers 00, 01, 06,07,08,17,28)
Binary Output (Object 10 Variation 0 Qualifiers 00, 01, 07, 08, 17, 28)
Binary Output (Object 10 Variation 2, Qualifiers 00, 01, 06, 07, 08, 17, 28)
Binary Counter (Object 20 Variation 6 Qualifiers 00, 01, 06, 07, 08, 17, 28)
Frozen Counter (Object 21 Variation 10 Qualifiers 00, 01, 06, 07, 08, 17, 28)
Analogue Input (Object 30 Variation 0, Qualifiers 00, 01, 07, 08, 17, 28)
Analogue Input (Object 30 Variations 1, 2, 3, 4 Qualifiers 00, 01, 06,07,08,17,28)
Analogue Change Event (Object 32 Variations 1, 2, 3, 4 Qualifiers 06, 07, 08)
Analogue Input Deadband (Object 34 Variations 1, 2, Qualifiers 00, 01, 06,07,08,17,28)
Analogue Output Status (Object 40 Variation 1, 2 Qualifiers 00, 01,07,08,17,28)
Analogue Output Block (Object 41 Variation 1, 2 Qualifiers 00, 01, 07, 08, 17, 28)
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):
Transmitted: 292
Received: 292
Maximum Data Link Retries:
Configurable 0..255
Requires Data Link Layer Confirmation:
Maximum Application Fragment Size (octets):

Transmitted: 2048
Received: 249
Maximum Application Layer Retries:
None
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)
N00-324.doc R39
Page 36

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
Executes Control Operations:
WRITE Binary Outputs:
Never
SELECT/OPERATE:
Always
DIRECT OPERATE:
Always
Count > 1:
Never
DIRECT OPERATE - NO ACK: Always
Pulse On:
Always
Max number of controls that can operate
Pulse Off:
Always
simultaneously: 1
Latch On:
Always
Pattern control operations are not supported
Latch Off:
Always
Trip/Close:
Sometimes
Raise/Lower: Never
Queue:
WRITE Analogue Outputs:
Never
SELECT/OPERATE:
Always
DIRECT OPERATE:
Always
Never
Clear Queue: Never

Pulse On and Pulse Off times are ignored
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 when
no specific variation requested:
Configurable with / without time
Sends Unsolicited Responses:
Enable/Disable Unsolicited supported
Supports Collision Avoidance:
Configurable
Default Counter Object:
Default Object: 20
Default Variation: 06
Reports time tagged Binary Input Change

Events when no specific variation requested:
Binary Input Change with Time
Static Data in Unsolicited Responses:
Never
Collision Avoidance Detection Method:
DCD
Counter Roll Over at:
65535
Sends Multi-Fragment Responses: Yes
N00-324.doc R39
Page 37
Appendix C DNP3 Implementation Table

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

1
Binary Input
00, 01, 06,

07, 08,
17, 28
129
Binary Input With Status
00, 01, 06,

07, 08,
17, 28
129
17, 28
Note 4
Binary Input Change - All

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

OBJECT
Obj
Var
21
REQUEST
(slave must parse)
Description
16 Bit Frozen Counter with flag
Func Codes
(dec)
1
00, 01, 06.

07, 08,
17, 28
00, 01, 06.
07, 08,
17, 28
129
00, 01
06
07, 08, 17, 28
00, 01, 06,
07, 08,
17, 28
N/A
N/A
129
00, 01
00, 01, 06,

07, 08,
17, 28
129
17, 28
Note 4
00, 01
00, 01, 06,

07, 08,
17, 28
129
17, 28
Note 4
00, 01
00, 01, 06,

07, 08,
17, 28
129
17, 28
Note 4
00, 01
06, 07, 08
N/A
N/A
06, 07, 08
129, 130
17, 28
06, 07, 08
129, 130
17, 28
06, 07, 08
129, 130
17, 28
06, 07, 08
129, 130
17, 28
00, 01, 06,

07, 08,
17, 28
00, 01, 06,
07, 08,
17, 28
00, 01, 06,
07, 08,
17, 28
N/A
N/A
129, 130
17, 28
129, 130
17, 28
00, 01
06
07, 08, 17, 28
N/A
N/A
32 Bit Frozen Counter without flag
21
10
16 Bit Frozen Counter without flag
30
Analogue Input - All Variations
30
30
30
32 Bit Analogue Input without

Flag
16 Bit Analogue Input without

Flag
Analogue Change Event - All

Variations
32 Bit Analogue Change Event
without Time
without Time
with Time
with Time
32
32
32
32
32
34
Analogue Input Reporting

Deadband All Variations
Note 6
34
16 bit Analogue Input Deadband

reporting
Note 6
1, 2
34
32 bit Analogue Input Deadband

reporting
Note 6
1, 2
40
Analogue Output Status - All

Variations
N00-324.doc R39
Qual
Codes
(hex)
129
Func
Codes
00, 01, 06.

07, 08,
17, 28
21
30
Qual Codes
(hex)
RESPONSE
(master must parse)
22
129
00, 01
17, 28
Note 4
00, 01
17, 28
Note 4
00, 01
17, 28
Note 4
17, 28
Note 4
Page 39

OBJECT
REQUEST
(slave must parse)
Obj
Var
Description
Func Codes
(dec)
40
32 Bit Analogue Output Status
40
16 Bit Analogue Output Status
41
32 Bit Analogue Output Block
3, 4, 5, 6
41
16 Bit Analogue OutputBlock
3, 4, 5, 6
50
Time and Date
50
Time and Date
Qual Codes
(hex)
RESPONSE
(master must parse)
Func
Codes
Qual
Codes
(hex)
00, 01, 06,

07, 08,
17, 28
00, 01, 06,
07, 08,
17, 28
129
00, 01, 07, 08,

17, 28
00, 01, 07, 08,
17, 28
129
Echo of
request
129
Echo of
request
00, 01, 06
07, 08,
17, 28,
00, 01, 06
08, 17, 28
07
(quantity = 1)
00, 01, 06
08, 17, 28,
07
(quantity = 1)
129
00, 01
17, 28
Note 4
00, 01
17, 28
Note 4
129
00, 01
17, 28
Note 4
129
00, 01
17, 28
Note 4
00, 01
17, 28
Note 4
129
52
Time Delay Fine
N/A
N/A
129
07,
(quantity 1)
60
Class 0 Data
06
N/A
N/A
60
Class 1 Data
06, 07, 08
N/A
N/A
60
Class 2 Data
06, 07, 08
N/A
N/A
60
Class 3 Data
1
20,,21
1
20,,21, 22
1
20, 21, 22
1
20, 21, 22
06, 07, 08
N/A
N/A
80
Internal Indications
00 index = 7
N/A
N/A
00, 01, 06,

08, 17, 28
06, 07, 08
N/A
N/A
129
17, 28
N/A
N/A
N/A
112
Virtual Terminal Output Block

Note 5
Virtual Terminal Event Data
113
No Object
2
1
13
14
23
Note
1.
All shaded areas are the additional level 3 or above function, objects, variations and/or qualifiers supported
by controller.
2.
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 5.3.
3.
All Request and Response options marked N/A are Not Applicable.
4.
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,
N00-324.doc R39
Page 40

07, or 08, will be responded with qualifiers 00 or 01. (For change-event objects, qualifiers 17 or 28 are
always responded.)
5.
The Virtual Terminal Objects (112 and 113) are used to transport SOS data between WSOS and the
controller. No other data is supported.
6.
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
Function
Code
Description
Response
Function
Code
Description
Function
Code
Description
Read
Freeze and Clear
129
Response
Write
10
Freeze and Clear, No Ack
130
Select
13
Cold Restart (Note 1)
Unsolicited
Response
Operate
14
Warm Restart (Note 1)
Direct Operate
20
Enable Unsolicited Msgs
Direct Operate, No Ack
21
Disable Unsolicited Msgs
Immediate Freeze
22
Assign Class
Immediate Freeze, No Ack
23
Delay Measurement
Note
1.
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
(Hex)
00, 01
Use in a Request
Use in a Response
A range of static points, or a single point with a

point number.
Static Objects
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 with

no number (eg Time and Date).
A single point with no number (eg Time and 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)

Object headers have either 8 bit quantity field with
8 bit indices (Q=17) or 16 bit quantity field with 16
bit indices (Q=28)
N00-324.doc R39
Event objects (usually one or more unrelated

points)
Page 41

DNP3 Internal Indication Bits
The following DNP3 response internal indication bits are not supported.
IIN1-6
Device trouble. For system health status refer to the Abnormal Operator Conditions binary input
point that is described in Appendix D.
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
Status Value
Controller Control Response Description
Control request accepted
Control request denied. Select/Operate timed out. The time out parameter is configurable.
Control request denied. Operate without select message OR operate/select application

sequence number mis-match.
Control request denied. Formatting error
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.
Control request denied. Already Active
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.
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

Technical
Bulletin
Description
N00-324.doc R39
Nulec Manual
Version
Comment
Page 42

2000-004
Application Layer Confirmation Messages
N00-324R20
2000-003
Change Management
2000-002
Control Retries
N00-324R28
2000-001
Sequential File Transfer Objects
9912-003
Broadcast Message Confirmation and

Address Reservation
N00-324R33
9912-002
Unsolicited Event Reporting; Retry

Configuration
N00-324R28
9905-001
Qualifier Code 11
9809-001
Analogue Input Reporting Deadband
N00-324R28
9804-008
Unissued Object and Variation Numbers
N00-324R20
9804-007
Clarification of Collision Avoidance

Procedure
N00-324R28
9804-006
Analogue Object Floating Point Variations
Not Applicable. Note 2
9804-005
8 Bit Unsigned Integer Object 102
9804-004
Virtual Terminal Objects 112 and 113
N00-324R27
9804-003
Recommended Layer Terminology
N00-324R20
9804-002
DNP3 Confirmation and Retry Guidelines
N00-324R20
9804-001
Rules for Synchronising Application

Sequence Numbers
N00-324R20
9704-007
Implementation for Reset Link Frames
N00-324R20
9701-006
Extension of Engineering Units for

Floating Point Objects
9701-004
Octet String Objects 110 and 111
9701-003
Cold/Warm Restart Sequence
N00-324R20
9701-002
Control Relay Output Block Minimum

Implementation
N00-324R20
9701-001
Datalink Restart Recovery
N00-324R20
Note 1
Note:
1) It is Nulec policy that all technical bulletin rules that are required for the controller to be DNP33 level 2
compliant are implemented.
2) 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.doc R39
Page 43
DNP V3.00 Protocol Technical Manual (ACR)
Appendix D ACR - Binary Input Points (Status)

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 4.4.
DNP3 Implementation
Static: Object 01 Variation 01 Single Bit Binary Input
Event: Configurable refer to section 5.3
Request Function Code: 01 Read
ACR Tripped
(open)
ACR Closed
Time
Accuracy
Comment
and
Cleared = 0
Set = 1
Class
Abnormal
Operator
conditions
Name
DNP3 ID
W Series
ACR Binary Input Points (Status)
None of the specified

conditions are true
This flag shows that the

operator has the ACR in an
abnormal state such as work
tag applied. This means that it
will operate differently to its
normal mode of operation.
500ms
For any of the

following conditions: Trip or Close
Isolated,
ACR
Mechanically
locked open (if
applicable)
Work Tag
Applied
ACR Tripped
ACR not Tripped
ACR Closed
ACR not Closed
LOCAL Control
Enabled
Remote Control
Disabled
These are repeats of the

mechanism travel switches.
When the ACR is disconnected
from the control cubicle they are
both cleared.
500ms
The controller is either in
LOCAL or Remote Controller
Mode. This affects the closing
command the permission to
set/remove work tag.
500ms
The controller has detected one
or more conditions which
require maintenance.
This point cannot become Set
until at least five minutes after
controller start.
500ms
Controller
Mode
LOCAL control
Disabled
Remote control
Enabled
Maintenance
Required
No maintenance
For any of the
following conditions:- required
Battery not
normal
Capacitor charge
failure
Low power mode
Low SF6 gas
pressure (if
applicable)
ACR data not
valid (includes
connection to an
N00-324 R39
44
Time
Accuracy
Comment
and
Cleared = 0
Set = 1
Class
W Series
Name
DNP3 ID
invalid switch
type)
Any vacuum
interrupter
contact life is
less than 20%
Mechanical
failure
Work Tag Applied
Work Tag Removed
Protection Group A is
active
Protection Group B is
active
Protection Group C is
active
Protection Group D is
active
Protection Group E is
active
Protection Group F is
active
Protection Group G is
active
Protection Group H is
active
Protection Group I is
active
Protection Group J is
active
Earth / Ground
Protection ON
Protection Group A is not

active
Protection Group B is not
active
Protection Group C is not Only one protection group is
active
active at any one time.
Protection Group D is not
active
Protection Group E is not
500ms
active
Protection Group F is not
active
Protection Group G is
not active
Protection Group H is not
active
Protection Group I is not
active
Protection Group J is not
active
Earth / Ground
500ms
Protection OFF
Work Tag
Prot A Active
Prot B Active
Prot C Active
Prot D Active
10
Prot E Active
11
Prot F Active
12
Prot G Active
13
Prot H Active
14
Prot I Active
15
Prot J Active
16
Earth / Ground
Protection
Enabled
SEF/SGF
Protection
Enabled
Auto Reclose
Cold Load Idle
SEF/SGF protection
ON
SEF/SGF protection
OFF
500ms
Y
Y
2
2
Auto Reclose OFF

Cold load is NOT Idle.
This means that the
threshold multiplier is
being raised by the cold
load pickup function in
order to pick up cold
load.
High Current Lockout
Protection OFF
Loss of Phase Protection
OFF
500ms
500ms
Auto Reclose ON
Cold Load is Idle or is
turned off.
This means that the
not being affected by
the cold load
function.
Protection ON
Loss of Phase
Protection ON
17
18
19
20
21
High Current
Lockout
Loss of Phase
Protection
N00-324.doc R39
The controller can have a work

tag. This affects the closing
command
500ms
500ms
500ms
Page 45
24
25
26
Power Flow
Direction
Time
Accuracy
Comment
and
Cleared = 0
Sequence
Control
Live Load
blocking
Protection
enable
Switchgear
Family
Set = 1
Class
23
W Series
22
Name
DNP3 ID
Sequence Control
ON
Live Load blocking
ON
Protection Enabled
Sequence Control OFF
500ms
Live Load blocking OFF
500ms
Protection turned OFF
500ms
Set for Load Break

Switch
Clear For Recloser
Source X, Load I
Source I, Load X
500ms
The power flow direction
(source/load designation) is
determined by the user. Refer
to the Power Flow Direction
binary output for more
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
Progress
N00-324.doc R39
Start of sequence
That is a protection
trip or sequence
advance has
occurred.
End of sequence. Either

lockout or reclaim.
This shows that a protection

sequence has started and not
yet completed.
Note that operator trip does not
cause a sequence in progress.
Event time is the time of the trip
or sequence advance.
10ms
Page 46
Single Shot
Protection
30
Loss Of Phase Y
Trip
31
Loss Of Phase Y
- Phase A
32
Loss Of Phase N
- Phase B
33
Loss Of Phase N
-Phase C
34
High Current
Lockout
35
Lockout
N00-324.doc R39
All fault flags are cleared

by one of the following
actions : Reset Fault Flags
and Currents
protocol control
command
Any Operator Close
action
Controller software
reset (data is
volatile)
At the time of the
next trip the flags
are refreshed at
this time old flags
are cleared and the
cause of the most
recent protection
operation set.
Protection turned
ON
Time
Accuracy
29
End of sequence,
either lockout or
reclaim
Comment
and
Cleared = 0
Set = 1
Class
Protection
Data Valid
Name
28
DNP3 ID
W Series
This shows that the protection

sequence is over and the other
flags are set.
This could be used to drive an
operator alarm at the SCADA
system to alert him to the fact
that a protection sequence has
occurred. Note that operator trip
alone does not cause a
protection data valid
Event time is the time of lockout
or reclaim.
10ms
One flag only provided because
a single shot trip forces lockout.
Event time is the time of the
pickup.
10ms
Trip was caused by
LOP protection forces lockout.
Loss of Phase
Protection
Event time is the time of the trip.
10ms
Set if A Phase is lost at time of
Phase A was lost at
Loss of Phase trip
time of Loss of Phase
trip
10ms
Set if B Phase is lost at time of
Phase B was lost at
Loss of Phase trip
trip
10ms
Set if C Phase is lost at time of
Phase C was lost at
Loss of Phase trip
trip
10ms
All fault flags are cleared One flag only because High
by one of the following Current Lockout forces lockout
Time stamp as for flags above.
actions :Event time is the time of the
Reset Fault Flags
lockout event.
and Currents
The high current
10ms
protocol
control
lockout function
command
forced the controller
Any Operator Close
to lockout during the
action
last protection
sequence
Controller software
reset (data is
volatile)
Start of a new
sequence
The controller is in
Cleared by any close
lockout
action
controller is in lockout.
Therefore no auto-reclosing will
take place.
Single Shot
Protection was active
at the time of the trip.
Page 47
Time
Accuracy
Comment
and
Cleared = 0
Set = 1
Class
W Series
Name
DNP3 ID
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
The most recent trip

was caused by a
local or remote
operator (eg IOEX,
Protocol, or panel)
Cleared by any close

action
Trip was caused by

Phase Overcurrent
Protection

and Currents
protocol control
command
One flag only because operator

trip forces lockout.
Event time is the time of the trip
10ms
Protection Trip 1
37
38
39
Phase Over
Current Trip
SEF/SGF
Over Current
Trip
Sequence
Advance
Protection Trip 2
42
43
Earth / Ground N
Over Current
Trip
40
41
Phase Over
Current Trip
Earth / Ground N
Over Current
Trip
SEF/SGF
Over Current
Trip
Sequence
Advance
Protection Trip 3
44
N00-324.doc R39
Trip was caused by

Earth / Ground
Overcurrent
Protection
Trip was caused by
Sensitive Earth /
Ground Fault
Protection
Sequence advance
occurred.
Trip was caused by
Phase Overcurrent
Protection
Trip was caused by

Earth / Ground
Overcurrent
Protection
Trip was caused by
Sensitive Earth /
Ground Fault
Protection
Sequence advance
occurred.
10ms
Any Operator Close

action
10ms
controller software
reset (data is
volatile)
10ms
Start of a new
sequence
10ms

and Currents
protocol control
command
10ms
Any Operator Close

action
10ms
controller software
reset (data is
volatile)
10ms
Start of a new
sequence
10ms
Page 48
Trip was caused by

Phase Overcurrent
Protection
46
47
Earth / Ground N
Over Current
Trip
SEF/SGF
Over Current
Trip
48
Sequence
Advance
Protection Trip 4
49
Phase Over
Current Trip
Trip was caused by

Earth / Ground
Overcurrent
Protection
Trip was caused by
Sensitive Earth /
Ground Fault
Protection
Sequence advance
occurred.
Trip was caused by

Phase Overcurrent
Protection
50
51
52
Earth / Ground N
Over Current
Trip
SEF/SGF
Over Current
Trip
Reserved
Trip was caused by

Earth / Ground
Overcurrent
Protection
Trip was caused by
Sensitive Earth /
Ground Fault
Protection

and Currents
protocol control
command
Time
Accuracy
10ms
Any Operator Close

action
10ms
controller software
reset (data is
volatile)
10ms
Start of a new
sequence
10ms

and Currents
protocol control
command
10ms
Any Operator Close

action
10ms
controller software
reset (data is
volatile)
10ms
Comment
and
Cleared = 0
Set = 1
Class
Phase Over
Current Trip
W Series
45
Name
DNP3 ID
Start of a new
sequence
Always 0
Accumulated Protection Trip Operation Flags

Multiple Flags can be set in this section because they accumulate all the trips in the sequence
53
54
Phase Over
Current Trip
Earth / Ground N
Over Current
Trip
N00-324.doc R39
One or more trips

were caused by
Phase Overcurrent
Protection
One or more trips

were caused by
Earth / Ground
Overcurrent
Protection

and Currents
protocol control
command
Any Operator Close

action
.
10ms
10ms
Page 49
Sequence
Advance
One or more trips

were caused by
Sensitive Earth /
Ground Fault
Protection
One or more
sequence advances
occurred.
Time
Accuracy
Comment
and
Cleared = 0
SEF/SGF
Over Current
Trip
Set = 1
Class
56
W Series
55
Name
DNP3 ID
controller software
reset (data is
volatile)
10ms
Start of a new
sequence
10ms
End of Protection Flags

Close Isolate Switch
OFF/ISOLATE(i.e.
Close is disabled)
Trip Isolate Switch
OFF (i.e. Trip is
disabled)
ACR Locked Open

ON/ENABLE (i.e. Close
is enabled)
Trip Isolate Switch
ON(i.e. Trip is enabled)
Shows the state of the Trip &

Close isolate switches on the
control panel
10ms
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
Shows that the controller has
retrieved the data from the ACR
memory. When invalid the
switchgear attributes and the
gas pressure are zeroed,
500ms
500ms
57
Close Isolate
58
Trip Isolate
59
Locked
60
ACR Memory
Data Invalid
ACR Memory Data

not valid
ACR Memory Data Valid
61
Auxiliary
Supply
Fail
Switchgear
Connection
Auxiliary supply has

failed
Auxiliary supply is
normal
Switch disconnected
from control cubicle.
Switch connected from

control cubicle.
63
SF6 Gas
Pressure Low
or Invalid
64
Battery Supply Y
62
N00-324.doc R39
Shows the connection state of

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
Gas pressure Low or Gas Pressure Normal, or Only set when switchgear is
Invalid
Not Known, or Not a
connected and ACR memory
switchgear which has
data is valid and switchgear
SF6.
type has SF6.
500ms
500ms
Battery supply not
Battery supply normal
normal.
This includes :Battery Off
Battery Overvolt
Battery Low Volts
Page 50
Capacitor Charge OK
Mechanism Failure
Mechanism OK
Y
N
N
Y
1
1
1
1
Phase is live
Phase is dead
Source
Y
Voltage Status
Load Voltage
Y
Status
66
67
Reserved
Capacitor
Charge
Failure
N
Y
2
2
68
Mechanism
Failure
69
70
71
72
Phase Ai Live
Phase Bi Live
Phase Ci Live
Phase Ax Live
73
Phase Bx Live
Name
DNP3 ID
Contacts Life
Low
Time
Accuracy
Capacitor Charge
Failed
65
Comment
and
Cleared = 0
When all vacuum
interrupters have contact
life >= 20%
Class
When any vacuum

interrupter contact life
is less than 20%.
W Series
Set = 1
500ms
The Trip/Close Capacitors have

failed to charge
500ms
The switchgear has failed to
Trip or Close electrically
500ms
Shows if the phase bushings
are above or below the live line
threshold.
Note 3
Note 3
74
Phase Cx Live
10ms
Note 3
75
76
Note 3
77
78
79
80
81
82
83
84
85
86
Load Current
On
Loop Auto On
Loop Auto
Restore On
Loop Auto
Tie Restore
On
Loop Auto
Type Feeder
Loop Auto
Type Midpoint
Loop Auto
Type Tie
Reserved
Reserved
Loop Auto
Trip Request
N00-324.doc R39
Y
Y
2
2
2
N
N
Y
Shows that any of the

three phases of the
designated Source
side or Load side are
live.
All of the source side are

Terminals dead
Current of 2.5A or
more is flowing in at
least one phase
Loop Automation is
On
Loop Auto Restore is
On
The Tie recloser is
configured to restore
supply in both
directions
Current of less than 2.5A

is flowing in all three
phases
Loop Automation is Off
All of the load side are

Terminal dead
Note that these points are

different to the Load/Source
Live/Dead events in the
controller event record
10ms
10ms
Note 1
500ms
Loop Auto Restore is Off
Note 1
Note 1, 2
Recloser type is set

to Feeder
The Tie Recloser will

only restore supply to its
Load side or the
Recloser type is not set
to Tie
to Feeder

to Midpoint

to Midpoint
Note 1

to Tie

to Tie
Note 1
Reserved
Reserved
Reserved
Set
when
Loop
Automation issues a
Trip Request.
Reserved
Normal state, cleared on Note 1
next internal scan after
set
500ms
500ms
Note 1
500ms
500ms
500ms
10ms
Page 51
Time
Accuracy
Comment
and
Cleared = 0
Set = 1
Class
W Series
Name
DNP3 ID
87
Loop Auto
Y
Close Request
88
Dummy Circuit Y
Breaker
Closed
89
Automatic
Protection
Group
Selection
Supply
Outage
Measurement
Door Open
APGS is ON
Normal state, cleared on Note 1

10ms
next internal scan after
set
The dummy circuit breaker is
DCB Not Closed
an internal point useful for
SCADA system testing. The
value of the DCB is non-volatile.
500ms
500ms
APGS is OFF
Supply Outage
Measurement ON
Supply Outage
Measurement OFF
Cubicle Door Open
Cubicle Door Closed
92
Phase Current
HI Alarm
Phase Current Alarm

ON
Phase Current Alarm

OFF
93
Phase Current
LOW Alarm
Phase Current Alarm

ON
Phase Current Alarm

OFF
500ms
94
Phase Voltage Y
HI Alarm
Phase Voltage Alarm

ON
Phase Voltage Alarm

OFF
500ms
95
Phase Voltage Y
LOW Alarm
Phase Voltage Alarm

ON
Phase Voltage Alarm

OFF
500ms
96
Earth Current
HI Alarm
Earth Current HI
Alarm ON
Earth Current HI Alarm

OFF
500ms
97
Earth Current
LOW Alarm
Earth Current LOW

Alarm ON
Earth Current LOW

Alarm OFF
500ms
98
System Power Y
HI Alarm
System Power HI
Alarm ON
System Power HI Alarm

OFF
500ms
99
System Power Y
LOW Alarm
System Power LOW

Alarm ON
System Power LOW

Alarm OFF
500ms
100
Auxiliary
Supply Fail
(Delayed)
Most Recent
Trip Phase A
Overcurrent
Auxiliary Supply has

failed for more than
120 seconds
Set if the most recent
trip was caused by a
A Phase Overcurrent
Protection Trip

been restored for more
than 20 seconds
and Currents
protocol control
command
Any Operator Close
action
500ms
90
91
101
102
Most Recent
Trip Phase B
Overcurrent
N00-324.doc R39
Set
when
Loop
Automation issues a
Close Request.
DCB Closed

B Phase Overcurrent
Protection Trip
500ms
This point only valid if hardware

option installed.
10ms
500ms
10ms
10ms
Page 52
Instantaneous
Most Recent
Trip
105
Under
Frequency
Over
Frequency
Normal
Frequency
Close
Source Dead
Protection
Source Dead
Lockout
Work Tag Trip
106
107
108
109
110
Time
Accuracy
104

C Phase Overcurrent
Protection Trip
The peak current for
the most recent trip
was greater than the
instantaneous setting
Under frequency
protection ON
Over frequency
protection ON
Enable Normal
Frequency Close
protection ON
Source Dead
Protection ON
Set if a lockout
caused by the Dead
Lockout feature
occurred.
Comment
and
Cleared = 0
Set = 1
Class
Most Recent
Trip Phase C
Overcurrent
Name
103
DNP3 ID
W Series
Protection turned
ON
10ms
At the time of next

trip - the flags are
refreshed
10ms
Under frequency
protection OFF
Over frequency
protection OFF
Enable Normal
Frequency Close
protection OFF
Source Dead Protection
OFF
Cleared by:
protocol command
any operator close
or operator trip. This
includes remote
control commands.
Start of a new
sequence.
Work Tag Protection All fault flags are cleared
was active at the time by one of the following
actions :of the trip.
Reset Fault Flags
and Currents
protocol control
command
Any Operator Close
action
controller software
reset (data is
volatile)
Start of a new
sequence
Input state for IOEX
Input asserted
input 1
Note 4.
500ms
Note 4.
500ms
Note 4.
500ms
Note 5
500ms
Note 5
10ms

a work tag trip forces lockout.
Event time is the time of the
pickup.
10ms
111
IOEX Input 1
112
IOEX Input 2

input 2
Input asserted
Input not asserted
113
IOEX Input 3

input 3
Input asserted
Input not asserted
114
IOEX Input 4

input 4
Input asserted
Input not asserted
115
IOEX Input 5

input 5
Input asserted
Input not asserted
N00-324.doc R39
Input not asserted
Page 53
IOEX Input 7
118
IOEX Input 8
119
IOEX Input 9
120
IOEX Input 10
121
Time
Accuracy
117
Comment
and
Cleared = 0
Set = 1
Class
IOEX Input 6
Name
116
DNP3 ID
W Series

input 6
input 7
input 8
Input asserted
Input not asserted
Input asserted
Input not asserted
Input asserted
Input not asserted

input 9
Input asserted
Input not asserted

input 10
Input asserted
Input not asserted
IOEX Input 11

input 11
Input asserted
Input not asserted
122
IOEX Input 12
Input asserted
Input not asserted
123
Most recent
trip Under
Frequency

input 12
trip was caused by
an Under Frequency
condition

there is no auto reclose after a
frequency trip.
10ms
124
Most recent
trip Over
Frequency

trip was caused by
an Over Frequency
condition
Cleared by one of the

following:
protocol command
any operator close
or operator trip. This
includes remote
control commands.
Start of a new
sequence.
Cleared by:

close caused by local !
or remote panel close
request.
Set if the most recent !
close caused by an
IOEX close input.
!
close caused by a
protocol close
request.
close caused by a
Distributed
Automation close
request (ie Loop
Automation or Auto
Changeover).
close caused by
Normal Frequency
close request
125
Operator
Close
126
IOEX Close
127
Protocol Close
128
Automation
Close
129
Normal
Frequency
Close
N00-324.doc R39
10ms
'Reset Flags and

Currents' protocol
command
Controller Software
Reset
(data
is
volatile)
At the time of the
next Close
10ms
10ms
10ms
10ms
Page 54
131
ACO
Autorestore
132
Auto
Changeover
Enable
133
Auto
Changeover
Mode
134
ACO Rank
135
Live Load
Blocking
136-160 Reserved
Time
Accuracy
Class
Comment
and
W Series
External Close
Cleared = 0
Name
130
Set = 1
DNP3 ID
10ms
Set if any of the

following caused the
most recent close
CCEM external
button on NSeries
Mechanical
action. The
switchgear
detected as
closed without a
close request
Electrical action
(only available
on the Advanced
controller)
ACO Autorestore ON
ACO Autorestore OFF
Auto-changeover is
enabled
Auto-changeover is
disabled
Break before Make.
Make before Break.
Whether to automatically
change back to master supply if
it returns live.
500ms
Turn ACO on/off
500ms
500ms
N
Y
2
1
ACO Master
Live Load Blocking
Active
ACO Slave
Live Load Blocking
Inactive
500ms
10ms
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.
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.doc R39
Page 55
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.
DNP3 Implementation
Static: Configurable Object 30 Variation 1, 2, 3, or 4 (refer to section 5.3)
Event: Configurable Object 32 Variation 1, 2, 3, or 4 (refer to section 5.3)
Deadband: Configurable Object 34 Variation 1, 2 (refer to section 5.3)
Units
Default
Dead Band
16000
16000
16000
16000
1.9GVA
1.9GVAR
65535
1A
1A
1A
1A
1 kVA
1 kVAR
1
Operation
10 A.
10 A.
10 A.
5 A.
250 kVA.
250 kVAR.
1
Operation
Class
Max
Min
W Series
Name
DNP3 ID
ACR Analogue Input Points (Small)
Line Currents and System Power

0
1
2
3
4
5
6
A Current
B Current
C Current
Note 2
System kVA
System kVAR Note 2
Operations Counter
Y
N
N
N
Y
Y
Y
0
0
0
0
0
0
0
1
1
1
1
1
1
2
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:-
7
8
9
Reset Fault Flags and Currents protocol control command
Any Operator Close action
controller reset (data is volatile)
Start of a new sequence

A Fault Current Written on Y
an A-Max event.
B Fault Current Written on N
a B-Max event.
C Fault Current Written
N
on a C-Max event.
N00-324.doc R39
16000
1A
1A
16000
1A
1A
16000
1A
1A
Page 56
Class
Default
Dead Band
Units
Max
Min
W Series
Name
DNP3 ID
ACR Analogue Input Points (Small)
N
0
16000
1A
1A
1
Earth / Ground Fault
Current - Written on a GMax event. This includes
SEF/SGF Fault currents.
During a protection
Y
1
4
1
1
1
11
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.
10
13
Ai Phase-(Earth / Ground)
Voltage
Bi Phase-(Earth / Ground)
14
Voltage
15
Ci Phase-(Earth / Ground)
Voltage
Ax Phase-(Earth / Ground)
16
Note 3
Volts
17
Bx Phase-(Earth / Ground)
Note 3
Volts
Cx Phase-(Earth / Ground)
18
Note 3
Volts
19 to 69 Reserved
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
Note
1. The deadband for all analogue points can be configured, refer section 5.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.doc R39
Page 57
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
Min
Max
Units
Default
Dead Band
Class
A-Phase Current
16000
1A
10 A.
B-Phase Current
16000
1A
10 A.
C-Phase Current
16000
1A
10 A.
3
4
5
(Earth / Ground) Current

Note 2
System kVA
System kVAR Note 2
N
Y
Y
0
0
0
16000
1.9GVA
1.9GVAR
1A
1 kVA
1 kVAR
1
1
1
Operations Counter
65535
1
Operation
5 A.
250 kVA.
250
kVAR.
1
Operation
Name
DNP3 ID
W Series
ACR Analogue Input Points (Full)
System Line Currents and Power
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

A Fault Current Written
on an A-Max event.
16000
1A
1A
16000
1A
1A
Note 10
B Fault Current Written

on a B-Max event.
Note 10
N00-324.doc R39
Page 58
16000
1A
1A
16000
1A
1A
Class
Units
Dead Band
Max
Default
Min

on a C-Max event.
W Series
Name
DNP3 ID
Note 10
10
11
12

During a protection
sequence the value
increments indicating the
current trip or sequence
advance.
After a protection sequence
the final trip or sequence
advance that occurred.
Protection Group that was
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
All voltages have a common deadband which can be configured (refer section 5.3.5).
13
14
15
16
Voltage
Voltage
Voltage
Volts
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
38000
1V
100 V.
38000
1V
100 V.
38000
1V
100 V.
38000
1V
100 V.
Note 10
17
Volts
Note 10
18
Volts
Note 10
19
A-Bi Phase-Phase Voltage

Note 2
20
B-Ci Phase-Phase Voltage

Note 2
21
C-Ai Phase-Phase Voltage

Note 2
22
A-Bx Phase-Phase Volts

Note 2, 10
N00-324.doc R39
Page 59
Min
Max
Units
Default
Dead Band
Class
B-Cx Phase-Phase Volts
W Series
23
Name
DNP3 ID
38000
1V
100 V.
38000
1V
100 V.
-1.9GW
1.9GW
1 kW
250kW.
0.0
1.0
0.1
0.1
-100
300
1 kPaG
5kPaG
-14
44
1 psi
1psi
99,999,999
99,999
Y
Y
0
0
2147483647
2147483647
1
1
1
1
0
2
0.0
100.0
0.1 %
0.1 %
0.0
100.0
0.1 %
0.1 %
0.0
100.0
0.1 %
0.1 %
Y
Y
Y
0
0
0
32768
32768
999
1
1
1
1
1
1
0
0
0
999
Note 2, 10
24
C-Ax Phase-Phase Volts

Note 2, 10
System Status
25
System Power (kW)

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

Note 6
27
Gas Pressure, kPag.

Note 3, 9
28
Gas Pressure, psi

Note 3, 9
29
Code Version
Note 2, 4
30
Configuration Number
Note 2, 5
31
32
CAPM Serial Number

ACR Serial Number
Note 2
33
I Contact Life
Note 7
34
II Contact Life
Note 7
35
III Contact Life

Note 7
36
37
38
39
40
Protection setting selection

0 = Group A
1 = Group B
9 = Group J
Transmitted frame count
Received frame count
Received message length
error
Received message CRC
error
N00-324.doc R39
Page 60
Class
Dead Band
Default
Units
Max
Min
W Series
Name
DNP3 ID
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
41
42
43
44

on an A-Max event.
on a B-Max event.
on a C-Max event.
16000
1A
1A
16000
1A
1A
16000
1A
1A
16000
1A
1A
Protection Trip 2
45

on an A-Max event.
16000
1A
1A
46

on a B-Max event.
16000
1A
1A
47

on a C-Max event.
16000
1A
1A
48

16000
1A
1A
Protection Trip 3
49

on an A-Max event.
16000
1A
1A
50

on a B-Max event.
16000
1A
1A
51

on a C-Max event.
16000
1A
1A
52

16000
1A
1A
N00-324.doc R39
Page 61
Units
16000
1A
1A
54

on a B-Max event.
16000
1A
1A
55

on a C-Max event.
16000
1A
1A
56

16000
1A
1A
1800
1 second
10 second
16000
1A
10A
45
65
1Hz
0.1Hz
15
Name
Class
Max

on an A-Max event.
Default
Min
53
DNP3 ID
W Series
Dead Band
Protection Trip 4
Miscellaneous
57
Loop automation time

remaining prior to a trip or
close action occurring. For
no action pending value is
zero.
Note 8
58
59
Maximum Average Current

of all phases for the
previous day ending at
24:00
Frequency
Note 11
60
Auto-Changeover Status
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
61 to Reserved
69
Note
N00-324.doc R39
Page 62

3. If ACR 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.
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 controllers.
N00-324.doc R39
Page 63
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
Load Outages Note 2, 3

Load Outage Duration
Units
3
4
Max
KWH Cumulative Note 1

Source Outages Note 2, 3
Source Outage Duration
Min
0
1
2
W Series
Name
DNP3 ID
ACR Counter Points
Y
Y
Y
0
0
0
2147483647
2147483647
2147483647
KWH
Counts
Seconds
Y
Y
0
0
2147483647
2147483647
Counts
Seconds
Note 2, 3
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.
3. The power flow direction (source/load designation) is determined by the user. Refer to Power Flow
Direction Binary Input for status and Binary Output for control.
N00-324.doc R39
Page 64
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 does not
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
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. 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.
The count, on-time, off-time, queue, and clear parameters are ignored.
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

protection
Enable Earth / Ground

Protection
Rejected if:
earth/ground fault
OFF is not allowed.
SEF/SGF protection
SEF/SGF protection
ON and
Earth / Ground
Protection ON
N00-324.doc R39
Control Type
Cleared = 0
Set = 1
W Series
Name
DNP3 ID
ACR Binary Output Points
Earth / Ground
Protection OFF and
SEF/SGF Protection
OFF
Rejected if:
earth/ground fault
OFF is not allowed.
Disable SEF/SGF
protection
L, P
L, P
Page 65
Y
Y
Work Tag
Cold Load Idle/Max
Loss of Phase Protection

N
Rejected if:
LOP and Loop Auto
linked.
Single Phase switchgear.
Sequence Control
Y
Live Load Blocking
N00-324.doc R39
Enable Sequence
Control
Live Load blocking ON
Control Type
Auto Reclose
ACR Control
Rejected if:
SEF/SGF is not
available
Auto Reclose ON
Close
Rejected if:
Close coil is
isolated
controller is in
LOCAL control
mode
SF6 gas pressure
is low (if applicable)
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
Applies Work Tag.
Rejected if:
controller is in
LOCAL Mode
Set cold load time to its
maximum value. This
means that the cold
load threshold current
will be set to its
maximum value
Rejected if:
Cold load support
is OFF
Enable High Current
Lockout
Enable Loss of Phase
Protection
Cleared = 0
2
3
Set = 1
W Series
Name
DNP3 ID
Auto Reclose OFF

Trip
Rejected if:
Trip coil is isolated
SF6 gas pressure
AND low gas
lockout is ON
Switchgear data
invalid
L, P
TC,
L, P
Removes Work Tag.

Rejected if:
controller is in
LOCAL Mode.
Set cold load time to
zero. This means that
the threshold multiplier
will not be affected by
the cold load function.
Rejected if:
Cold load support
is OFF
L, P
L, P
Disable High Current

Lockout
Disable Loss of Phase
Protection
L, P
Disable Sequence
Control
L, P
L, P
L, P
Page 66
10 `
Reset Fault
Flags and Currents
Note 1
11
Protection Control
12
13
14
15
16
17
18
19
20
21
22
23
Power Flow Direction Note 4

Protection Group A Note 1, 3
Protection Group B Note 1, 3
Protection Group C Note 1, 3
Protection Group D Note 1, 3
Protection Group E Note 1, 3
Protection Group F Note 1, 3
Protection Group G Note 1, 3
Protection Group H Note 1, 3
Protection Group I Note 1, 3
Protection Group J Note 1, 3
Loop Automation Control
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Note 2
24
Dummy Circuit Breaker
N00-324.doc R39
Resets all Object 30

Fault Currents to zero
and clears all Object 01
protection trip flags
Enable Protection
Source X, Load I
Group A ON Note 5
Group B ON Note 5
Group C ON Note 5
Group D ON Note 5
Group E ON Note 5
Group F ON Note 5
Group G ON Note 5
Group H ON Note 5
Group I ON Note 5
Group J ON Note 5
Loop Automation ON
Rejected if:
Loop automation
capability not
available
Work tag applied
Trip coil isolated
Close coil isolated
Mechanism fail
Switchgear data
invalid
Battery not normal
SF6 Gas Pressure
AND Low Gas
Lockout is ON
Tripped AND
(Midpoint OR
Feeder)
U Series AND no
external CVTs
AND (TIE OR Auto
Restore ON)
DCB Close
No Action
Turn ALL Protection

OFF
Rejected if:
protection OFF is
not allowed
Source I, Load X
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
Loop Automation OFF
Rejected if:
Loop automation
capability not
available
DCB Trip
Control Type
Cleared = 0
Set = 1
W Series
Name
DNP3 ID
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
TC,
L, P
Page 67
26
Supply Outage Measurement

Control
Reset
28
Under Frequency Protection
29
Over Frequency Protection
30
Normal Frequency Close

Protection
31
32
33
34
35
36
37
38
39
40
Source Dead Protection

Protocol IOEX control 1
ACO Auto Restore
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
41
ACO Enable
42
ACO Mode
27
N00-324.doc R39
Control Type
Automatic Protection Group

Selection
Cleared = 0
25
APGS OFF
L, P
Set = 1
W Series
Name
DNP3 ID
APGS ON
Rejected if:
APGS ON is Not
Allowed
Loop Automation
ON
Supply Outage
Measurement ON
Resets all Supply
Outage counters
values.
Enable under frequency
protection
Rejected if:
CAPM4
Enable over frequency
protection
Rejected if:
CAPM4
Enable normal
frequency close
protection
Rejected if:
CAPM4
Enable
Sets IOEX output that is
mapped to this point.
For RTU emulation.
Supply Outage
Measurement OFF
L, P
No Action
L, P
Disable under
frequency protection
Rejected if:
CAPM4
Disable over frequency
protection
Rejected if:
CAPM4
Disable normal
frequency close
protection
Rejected if:
CAPM4
Disable
Clears the IOEX output
that is mapped to this
point. For RTU
emulation.
L, P
L, P
L, P
L, P
TC,
L, P
ACO Auto Restore ON.

Rejected if:
Switch is LBS
ACO feature is not
available
ACO ON. Rejected if:
Switch is LBS
ACO feature is not
available
ACO Auto Restore

OFF. Rejected if:
Switch is LBS
ACO feature is not
available
ACO OFF. Rejected if:
Switch is LBS
ACO feature is not
available
L, P
ACO Mode = Make

before Break. Rejected
if:
Switch is LBS
ACO feature is not
available
ACO Mode = Break

before Make. Rejected
if:
Switch is LBS
ACO feature is not
available
L, P
L, P
Page 68
Note:
1. The response for binary output status for these points will always be 0.
2. This point is only valid when the Loop Automation option is enabled for the current 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 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.doc R39
Page 69
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
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
Analogue Output Status
Static Object:
Object 40 Variation 02 16 Bit Analogue Status
Analogue Output Block
Control Object:
Object 41 Variation 02 16 Bit Analogue Output Block
W Series
Min
0
Units
Protection Group Selection

0 = Group A
1 = Group B
9 = Group J
Max
Name
DNP3 ID
ACR Analogue Output Point
N/A
Note 1
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.doc R39
Page 70
DNP V3.00 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 5.3
For any of the following

conditions: Trip or Close
Isolated,
LBS Mechanically
locked open (if
applicable)
Work Tag Applied
None of the specified

conditions are true
LBS Tripped (open)
LBS Tripped
LBS not Tripped
LBS Closed
LBS Closed
LBS not Closed
Controller Mode
LOCAL control Disabled

Remote control
Enabled
LOCAL Control
Enabled
Remote Control
Disabled
Maintenance
Required
For any of the following

conditions: Battery NOT normal
Capacitor charge
failure
Low power mode
Low SF6 gas
pressure LBS data
not valid (includes
connection to an
No maintenance
required
N00-324.doc R39
Resolution
Time
Abnormal Operator
conditions
and
Comment
Cleared = 0
Class
Set = 1
Name
DNP3 ID
LBS Binary Input Points (Status)

operator has the LBS in
an abnormal state such
as work tag applied.
This means that it will
operate differently to its
normal mode of
operation.
500ms
These are repeats of the
mechanism travel
switches. When the LBS
is disconnected from the
control cubicle they are
both cleared.
10ms
The controller is either in
LOCAL or Remote
Controller Mode. This
affects the closing
command the
permission to
set/remove work tag.
500ms
The controller has
detected one or more
conditions which require
maintenance.
This point cannot
become Set until at least
five minutes after
controller start.
500ms
Page 71
invalid switch type)

Any contact life is
less than 20%
Mechanical failure
Work Tag Applied
Work Tag Removed
Detection Group A is
active
Detection Group B is
active
Detection Group A is not

active
Detection Group B is not
active
Work Tag
Detection A Active
Detection B Active
Detection C Active
Detection Group C is
active
Detection Group C is not

active
Detection D Active
10
Detection E Active
11
Detection F Active
12
Detection G Active
13
Detection H Active
14
Detection I Active
15
Detection J Active
Detection Group D is
active
Detection Group E is
active
Detection Group F is
active
Detection Group G is
active
Detection Group H is
active
Detection Group I is
active
Detection Group J is
active
Detection Group D is not

active
Detection Group E is not
active
Detection Group F is not
active
Detection Group G is not
active
Detection Group H is not
active
Detection Group I is not
active
Detection Group J is not
active
16
Power Flow
Direction
Source X, Load I
Source I, Load X
17
Close Isolate
18
Trip Isolate

OFF/ISOLATE(i.e. Close
is disabled)
Trip Isolate Switch OFF
(i.e. Trip is disabled)

ON/ENABLE (i.e. Close
is enabled)
Trip Isolate Switch
ON(i.e. Trip is enabled)
N00-324.doc R39
Resolution
Time
and
Comment
Cleared = 0
Set = 1
Class
Name
DNP3 ID
The controller can have

a work tag. This affects
the closing command
500ms
These flags indicate
the active protection
group. If neither A nor
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
Only one detection
group is active at any
one time.
500ms
The power flow direction

(source/load
designation) is
determined by the user.
Refer to the Power Flow
Direction binary output
for more information
500ms
Shows the state of the
Trip & Close isolate
switches on the control
panel
10ms
Page 72
19
Locked
LBS Locked Open
LBS not locked open
20
LBS Memory Data

Invalid
LBS Memory Data not

valid
LBS Memory Data Valid
21
Auxiliary Supply
Fail
Switchgear
Connection
Auxiliary supply has

failed
Auxiliary supply is
normal
Switchgear
disconnected from
control cubicle.
Switchgear is connected
to control cubicle.
23
SF6 Gas Pressure

Low or Invalid
Gas pressure Low or

Invalid
Gas Pressure Normal,

or Not Known, or Not a
switchgear which has
SF6.
24
Battery Supply
Battery supply normal
25
Switchgear Family
Battery supply not

normal.
This includes : Battery Off
Battery Overvolt
Battery Low Volts
Set for Load Break
Switch
22
When all contacts have

contact life >= 20%
Capacitor Charge OK
Mechanism Failure
Mechanism OK
Contacts Life Low
27
Capacitor Charge
Failure
28
Mechanism Failure
N00-324.doc R39
Resolution
Time
and
Shows that the LBS is

mechanically and
electrically locked in the
open position..
10ms
Shows that the controller
has retrieved the data
from the LBS memory.
When invalid the
switchgear attributes and
the gas pressure are
zeroed,
500ms
500ms
Shows the connection
state of the cable
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
Only set when
switchgear is connected
and LBS memory data is
valid and switchgear
type has SF6.
500ms
500ms
Clear For Recloser
When any contact life is

less than 20%.
Capacitor Charge Failed
26
Comment
Cleared = 0
Set = 1
Class
Name
DNP3 ID
500ms
500ms
The Trip/Close
Capacitors have failed to
charge. (where relevant)
500ms
The switchgear has
failed to Trip or Close
electrically
500ms
Page 73
Phase Bi Live
Phase Ci Live
Phase Ax Live
Phase Bx Live
Phase Cx Live
Source Voltage
Status
1
1
1
1
1
1
36
Load Voltage
Status
37
Load Current On
Resolution
30
31
32
33
34
35
Phase is dead
Time
Phase is live
and
Comment
Phase Ai Live
Cleared = 0
Set = 1
29
Name
Class
DNP3 ID
Shows if the phase

bushings are above or
below the live line
threshold.
10ms
Shows that any of the

three phases of the
designated Source side
or Load side are live.
All of the source side are

Terminals dead
All of the load side are
Terminal dead
Current of 2.5A or more

is flowing in at least one
phase
Dummy LBS Closed
Current of less than 2.5A

is flowing in all three
phases
Dummy LBS not closed.
Note that these points

are different to the
Load/Source Live/Dead
events in the controller
event record
10ms
10ms
38
Dummy LBS
Closed
39
Supply Outage
Measurement
Supply Outage
Measurement ON
Supply Outage
Measurement OFF
40
41
Reserved 1
Phase Current HI
Alarm
2
2
Reserved
Phase Current Alarm
ON
Reserved
Phase Current Alarm
OFF
42
Phase Current
LOW Alarm
Phase Current Alarm

ON
Phase Current Alarm

OFF
500ms
43
Phase Voltage HI
Alarm
Phase Voltage Alarm

ON
Phase Voltage Alarm

OFF
500ms
44
Phase Voltage
LOW Alarm
Phase Voltage Alarm

ON
Phase Voltage Alarm

OFF
500ms
45
Earth Current HI
Alarm

ON

OFF
500ms
46
Earth Current LOW

Alarm
Earth Current LOW

Alarm ON
Earth Current LOW

Alarm OFF
500ms
47
System Power HI
Alarm

ON

OFF
500ms
48
System Power
LOW Alarm
System Power LOW

Alarm ON
System Power LOW

Alarm OFF
500ms
49
Auxiliary Supply
Fail (Delayed)

failed for more than 120
seconds

been restored for more
than 20 seconds
500ms
N00-324.doc R39
This point represents an

internal dummy LBS.
This is an internal point
useful for SCADA
system testing. The
value of the dummy LBS
is non-volatile.
500ms
500ms
500ms
Page 74
Resolution
Time
and
Comment
Cleared = 0
Set = 1
Class
Name
DNP3 ID
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.
2
Phase Detection ON
Phase Detection OFF
500ms
Sectionaliser Auto ON
54
Cold Load Auto
Cold Load auto-mode is

armed.
This means the Cold
Load function is enabled
and may, or may not, be
affecting the threshold
multiplier.
Cold Load is Idle or is
turned off.
This means that the
threshold multiplier is not
being affected by the
cold load function.
Live Load Blocking ON
Earth/Ground Detection
OFF
SEF/SGF Detection
OFF
Sectionaliser OFF (Load
Break Switch)
Cold Load pickup is
OFF.
This means that the cold
load function is
completely disabled.
500ms
Earth/Ground Detection
ON
SEF/SGF Detection ON
53
Phase Detection
Enabled
Earth/Ground
Detection Enabled
SEF/SGF
Detection Enabled
Sectionaliser Auto
50
51
52
55
Cold Load Idle
56
Live Load Blocking
57
Automatic
Detection Group
Selection
(Code Version 02501 and later)
Automatic Detection
Group Selection is ON
500ms
500ms
500ms
See Cold Load Idle
(below)
Cold load is NOT Idle.

This means that the
being raised by the cold
load pickup function.
500ms
Live Load Blocking OFF
500ms
Automatic Detection
Group Selection is OFF
500ms
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
Progress
N00-324.doc R39
Start of sequence That

is a detection trip or
sequence advance has
occurred.
End of sequence.
This shows that a

Detection sequence has
started and not yet
completed.
Note that operator trip
does not cause a
sequence in progress
10ms
Page 75
59
Cleared by
Operator trip
Any close
Reset Flags
Protocol Command
Resolution
Time
and
Comment
Cleared = 0
Set = 1
Class
Name
DNP3 ID
These flags show which

elements were picked up
since last clear action
10ms
64
A Phase
Overcurrent Fault
B Phase
Overcurrent Fault
C Phase
Overcurrent Fault
Earth/Ground
Overcurrent Fault
SEF/SGF
Overcurrent Fault
Supply Interrupt
A Phase Overcurrent
Fault
B Phase Overcurrent
Fault
C Phase Overcurrent
Fault
Earth/Ground
Overcurrent Fault
SEF/SGF Overcurrent
Fault
Supply Interrupt
65
Sectionaliser Trip
Sectionaliser Trip

input 1
Input asserted
Set if a supply interrupt

occurred after the most
recent fault.
10ms
Set if switch trips to
sectionalise
Input not asserted

input 2
input 3
input 4
Input asserted
Input not asserted
Input asserted
Input not asserted
Input asserted
Input not asserted

input 5
Input asserted
Input not asserted

input 6
Input asserted
Input not asserted

input 7
input 8
input 9
Input asserted
Input not asserted
Input asserted
Input not asserted
Input asserted
Input not asserted

input 10
Input asserted
Input not asserted

input 11
Input asserted
Input not asserted

input 12
Input asserted
Input not asserted
60
61
62
63
66
67
68
69
70
71
72
73
74
75
76
77
IOEX Input 1
IOEX Input 2
IOEX Input 3
IOEX Input 4
IOEX Input 5
IOEX Input 6
IOEX Input 7
IOEX Input 8
IOEX Input 9
IOEX Input 10
IOEX Input 11
IOEX Input 12
N00-324.doc R39
2
2
2
2
1
1
1
1
Page 76
78
1
Operator Close
79
1
IOEX Close
80
1
Protocol Close
81
External Close
82
83
93
Live Load Blocking
Resolution
Time
and
Comment
Cleared = 0
Set = 1
Class
Name
DNP3 ID

close caused by local or
remote panel close
request.
Cleared by:
!
'Reset Flags and

Currents' protocol
command

close caused by an
IOEX close input.
close caused by a
protocol close request.
Controller
Software
Reset
(data is volatile)
10ms
At the time of the

next Close
10ms
Set if any of the following

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)
Cleared by:
close was blocked due
! 'Reset Flags and
to a Live Load condition
Currents' protocol
command
10ms
Controller Software
Reset
(data
is
volatile)
At the time of the

next Close
10ms
10ms
Reserved
Note:
1. Only available on CAPM-5 controller
Appendix K LBS - Analogue Input Points (Status - Small Set)

This is the reduced set of analogue status points available from the controller.
N00-324.doc R39
Page 77

All analogues in the small analogue data set can fit in a signed 16-bit DNP3 data object
except where noted.
DNP3 Implementation
System kVAR
Operations Counter
Class
0
0
0
0
0
Default
Dead Band
A Current
B Current
C Current
Note 2
System kVA
Units
0
1
2
3
4
Max
Min
Name
DNP3 ID
LBS Analogue Input Points (Small)
16000
16000
16000
16000
1.9
GVA
1.9
GVAR
65535
1A
1A
1A
1A
1 kVA
10 A.
10 A.
10 A.
5 A.
250 kVA.
1
1
1
1
1
1 kVAR
250 kVAR.
1
Operation
1 Operation
Line Currents and System Power
Note 2
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
7
8
9
10
11
12
Voltage
Voltage
Voltage
Voltage
Voltage
Voltage
N00-324.doc R39
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
30000
1V
100 V.
Page 78
Class
Default
Dead Band
Units
Max
Min
Name
DNP3 ID
LBS Analogue Input Points (Small)
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 : Reset Fault Current remote control command defined below
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.
13
14
15
16
17
18
Active Detection Group

The number of the Detection
Group active during the
sequence.
Supply Interrupt Count
The number of Supply
Interrupts Counted.
Most Recent A-Phase Fault
Written on a Max Current event
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 EMax event. This includes
19
29
10
16000
Amps
1A
16000
Amps
1A
16000
Amps
1A
16000
Amps
1A
Reserved
Note
2. These points may exceed the 16 bit limit and can be obtained using 32 bit analogue input
objects.
N00-324.doc R39
Page 79
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
System kVA
Note 2
System kVAR
Note 2
Operations Counter
Class
0
0
0
0
Default
Dead Band
A-Phase Current
B-Phase Current
C-Phase Current
(Earth / Ground) Current
Units
0
1
2
3
Max
Min
Name
DNP3-ID
LBS Analogue Input Points (Status Full Set)
16000
16000
16000
16000
1.9
GVA
1.9
GVAR
1A
1A
1A
1A
10 A.
10 A.
10 A.
5 A.
1
1
1
1
1 kVA
250 kVA.
1 kVAR
250 kVAR.
1
Operation
1 Operation
System Line Currents and Power
65535
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 5.3.5).
7
8
9
10
11
Ai Phase-(Earth/ Ground)
Voltage
Voltage
Voltage
Voltage
Voltage
N00-324.doc R39
30000
1V
100 V
30000
1V
100 V
30000
1V
100 V
30000
1V
100 V
30000
1V
100 V
Page 80
Max
Units
Default
Dead Band
Class
Voltage
Min
12
Name
DNP3-ID
30000
1V
100 V
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 : Reset Fault Current remote control command defined below
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
14
15
16
17
18
Active Detection Group

The number of the Detection
Group which was active during
the sequence.
Supply Interrupt Count
The number of Supply
Interrupts Counted.
Most Recent A-Phase Fault
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-Max event. This includes
10
16000
Amps
1A
16000
Amps
1A
16000
Amps
1A
16000
Amps
1A
38000
1V
100 V
38000
1V
100 V
38000
1V
100 V
38000
1V
100 V
38000
1V
100 V
Voltage Measurements (Phase/Phase)

19
A-Bi Phase-Phase Voltage

Note 2
20
B-Ci Phase-Phase Voltage

Note 2
21
C-Ai Phase-Phase Voltage

Note 2
22
A-Bx Phase-Phase Voltage

Note 2
23
B-Cx Phase-Phase Voltage

Note 2
N00-324.doc R39
Page 81
Max
Units
Default
Dead Band
Class
C-Ax Phase-Phase Voltage
Min
24
Name
DNP3-ID
38000
1V
100 V
1.9
GW
1.9GW
1 kW
250kW.
0.0
1.0
0.1
0.1
100
300
1 kPaG
5kPaG
-14
0
0
0
0
0.0
0.0
0.0
0
0
0
0
44
99,999,999
99,999
2147483647
2147483647
100.0
100.0
100.0
32768
32768
999
999
1 psi
1
1
1
1
0.1 %
0.1 %
0.1 %
1
1
1
1
1psi
1
1
1
1
0.1 %
0.1 %
0.1 %
1
1
1
1
2
0
0
0
2
2
2
2
0
0
0
0
480
1 Min
1 Min
16000
1A
10A
Note 2
System Status
25
System Power (kW)

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

Note 6
27
28
29
30
31
32
33
34
35
36
37
38
39
Gas Pressure, kPag.

Note 3
Note 3
Gas Pressure, psi
Note 2, 4
Code Version
Configuration Number Note 2, 5
CAPM Serial Number
LBS Serial Number Note 2
Note 7
I/U Contact Life
II/V Contact Life Note 7
III/W Contact Life Note 7
Transmitted frame count
Received frame count
Received message length error
Received message CRC error
Detection State
40
41
Cold Load
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.
Detection Group currently
selected
0 = Detection Group A
1 = Detection Group B
n = Other Detection Group
Miscellaneous
42
Maximum Average Current of

all phases for the previous day
ending at 24:00
N00-324.doc R39
Page 82
43
53
Class
Default
Dead Band
Units
Max
Min
Name
DNP3-ID
Reserved
Note
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.
and is otherwise always reported as zero.
N00-324.doc R39
Page 83
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
3
4
Load Outages Note 2, 3

Load Outage Duration
Units
KWH Cumulative Note 1

Source Outages Note 2, 3
Source Outage Duration
Max
0
1
2
Min
Name
DNP3 ID
LBS Counter Points
0
0
0
2147483647
2147483647
2147483647
KWH
Counts
Seconds
0
0
2147483647
2147483647
Counts
Seconds
Note 2, 3
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.
3. The power flow direction (source/load designation) is determined by the user. Refer to Power Flow
Direction Binary Input for status and Binary Output for control.
N00-324.doc R39
Page 84
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 does not
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.
DNP3 Implementation
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. 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.
The count, on-time, off-time, queue, and clear parameters are ignored.
Response Codes: Refer to Appendix C for a table of reported status values
N00-324.doc R39
Set = 1
Close
Rejected if:
Close coil is
isolated
controller is in
LOCAL control
mode
SF6 gas pressure
is low (if
applicable) AND
low gas lockout is
Control Type
LBS Control
Cleared = 0
Name
DNP3 ID
LBS Binary Output Points
Trip
Rejected if:
Trip coil is isolated
SF6 gas pressure is
low (if applicable)
Switchgear data
invalid
Mechanically
interlocked
TC,
L, P
Page 85
Control Type
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
Applies Work Tag.
Rejected if:
controller is in
LOCAL Mode
Cleared = 0
Set = 1
Name
DNP3 ID
Removed the Work

Tag.
Rejected if:
controller is in
LOCAL Mode.
Set cold load time to
zero. This means that
the threshold multiplier
will not be affected by
the cold load function.
Rejected if:
Cold load support is
OFF
L, P

No Action
L, P
L, P
Source I, Load X
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
No Action
DCB Trip
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
L, P
TC,
L, P
L, P
Work Tag
Cold Load Idle/Max
3
4
Live Load Blocking

Reset Fault
Flags and Currents
Note 1
5
6
7
8
9
10
11
12
13
14
15
16
Power Flow Direction Note 4

Detection Group A Note 1, 3
Detection Group B Note 1, 3
Detection Group C Note 1, 3
Detection Group D Note 1, 3
Detection Group E Note 1, 3
Detection Group F Note 1, 3
Detection Group G Note 1, 3
Detection Group H Note 1, 3
Detection Group I Note 1, 3
Detection Group J Note 1, 3
Dummy Circuit Breaker
17
Automatic Detection Group

Selection
N00-324.doc R39
Set cold load time to its

maximum value. This
means that the cold
load threshold current
will be set to its
maximum value
Rejected if:
Cold load support
is OFF
Live Load blocking ON
Resets all Object 30
Fault Currents to zero
and clears all Object 01
Detection trip flags
Source X, Load I
Group A ON Note 5
Group B ON Note 5
Group C ON Note 5
Group D ON Note 5
Group E ON Note 5
Group F ON Note 5
Group G ON Note 5
Group H ON Note 5
Group I ON Note 5
Group J ON Note 5
DCB Close
APGS ON
Rejected if APGS ON
is Not Allowed
APGS OFF
L, P
Page 86
18
19

Control
Reset
20
Sectionaliser Auto
21
22
23
24
25
26
27
28
29
30
ACO Autorestore
Autochangeover Enable
31
Auto Changeover
Mode
Control Type
Cleared = 0
Set = 1
Name
DNP3 ID
Supply Outage
Measurement ON
Supply Outage
Measurement OFF
L, P
Resets all Supply

Outage counters
values.
Turn Sectionalising ON
No Action
L, P
Turn Sectionalising
OFF.
L, P
Sets IOEX output that

is mapped to this point.
For RTU emulation.
Clears the IOEX output

that is mapped to this
point. For RTU
emulation.
TC,
L, P
ACO Autorestore ON
Auto-changeover is
operating
Make before break.
ACO Autorestore OFF

Auto-changeover is
disabled
Break before make.
L, P
L, P
L, P
Note:
1. The response for binary output status for these points will always be 0.
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:
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.doc R39
Page 87
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
status to verify the success of an action.
DNP3 Implementation
Analogue Output Status
Static Object:
Object 40 Variation 02 16 Bit Analogue Status
Analogue Output Block
Control Object:
Object 41 Variation 02 16 Bit Analogue Output Block
Max
Units
Detection Group Selected

0 = Group A
1 = Group B
9 = Group J
Min
Name
DNP3 ID
LBS Analogue Output Point
N/A
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.doc R39
Page 88
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 RTU 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 RTU 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 RTU, transmits a broadcast message.
From the RTUs 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 RTU address to the master.
5. The master station sends data requests and a POLL
6. The CAPM replies with the requested data.
N00-324.doc R39
Page 89

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:
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.
2.
3.
4.
DTR is asserted.
The master station establishes the X.25 connection.
The CAPM strips off the leading NUA and COM characters.
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 RTU 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 RTU, transmits a broadcast message.
From the RTUs 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).
N00-324.doc R39
Page 90

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 RTU, it sends an
INITIALISE with a Broadcast address.
6. The CAPM transmits the INITIALISE reply with its RTU 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.
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.doc R39
Page 91

N00 324rev39

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

N00 324rev39

Încărcat de

Drepturi de autor:

Formate disponibile

NU-LEC INDUSTRIES PTY LTD

A Schneider Electric Company

COPYRIGHT NU-LEC INDUSTRIES PTY LTD 2001

DNP V3.00 Protocol Technical Manual

Nu-Lec Industries Pty Ltd.

DNP V3.00 Protocol Technical Manual

Changed the defaults for DL Cf Reqd and DL Max Retries

Changed the Apl Cf TO maximum value

Added OFF field to port selection

Added in functionality for FORCED Unsolicited Behaviour

Added new binary and counter object support to Device Profile

Reworded protection data operation + loop auto trip/close pending

Corrected/improved numerous point descriptions in appendices

Changed ownership to Nulec Industries

Updated the DNP device profile and implementation table

Added new Aux Fail Alarm to Binary Inputs in App D

Clarified DNP3 technical bulletin support list

DNP V3.00 Protocol Technical Manual

Added LBS Appendices and amended associated wording

Added IIN1-4 to device profile

Extended support include CAPM5 controllers.

Added comment note for analog phase-phase voltage range

Added Paknet interface to P8 RS-232 port

Corrections to Appendix P Paknet Call Procedures

Additions for Close flags, ACO and Live Load blocking.

Toggled meaning of ACO Mode Binary Status.

DNP V3.00 Protocol Technical Manual

DNP V3.00 Protocol Technical Manual

DNP V3.00 Protocol Technical Manual

Mounting room for a radio or modem in the control cubicle.

2.1 Status Points

Open or Close Status

DNP V3.00 Protocol Technical Manual

2.3 Data Configuration

Selection of three sets of analogue points full, small and none.

Default data object type with/with out flag/time; analogue size

Point class assignment.

2.4 Password Protectio n

2.5 LBS vs ACR Point Mapping.

2.6 Year 2000 Complia nce Statement

DNP V3.00 Protocol Technical Manual

3 SCADA System Design

DNP V3.00 Protocol Technical Manual

4.2 DNP3 Protocol

Basic Four Documentation Set :

4.3 Switchgear Type

N-Series ACR, all models with CAPM-4/5 controllers.

DNP V3.00 Protocol Technical Manual

Transmission Services Configuration (refer Section 5.1)

5.1 Transmission Serv ices Configuration

Data link layer confirmation

Data link time out

Application layer confirmation time out

Control select / operate time out period

Time Synchronisation request operation

5.1.2 Transmission Serv ices Parameters

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

---- DNP Transmission Services 2

DNP V3.00 Protocol Technical Manual

Data Link Confirm Timeout

Data Link Maximum Retries

Application Layer Confirm Timeout

DNP V3.00 Protocol Technical Manual