Professional Documents
Culture Documents
Distributed Network Protocol (DNP) V3.00 For Visionr
Distributed Network Protocol (DNP) V3.00 For Visionr
00 FOR VISIONR
OVERVIEW
The VISIONr Recloser Control supports Distributed Network Protocol (DNP) V3.00 L2 Slave
protocol. This includes access to metering data, protection elements, contact I/O, sequential events
recorder, relay summary event reports and time synchronisation. The VISIONr supports DNP point re-
mapping as well.
DNP Operation
To configure the RS485 port for DNP, set the “Serial Protocol” setting in “Serial Settings” page to
“DNP 3.0”. The following settings configure a port for DNP operation:
Setting Description Default
RS485 Baud Rate 9600,19200 or 38400bps 9600
Drive Number DNP Address (1-65534) 1
Binary Event Data Class for binary event data (CLASS 0–3) CLASS 2
Analogue Event Data Class for analogue event data (CLASS 0–3) CLASS 2
Counter Event Data Class for counter event data (CLASS 0–3) CLASS 2
Time Set m-Interval Time-set request interval (0–32767 min.) 0
Sel./Exe. Timeout Select/execute time-out (0.1–30.0 sec.) 1.0
Data Link Retries Times of data link retries (0–15) 3
Data Link Timeout Data link time-out (0–5 sec.) 1
Transmit Delay Minimum time from Rx to Tx (0–100 ms) 0
I-Analogue Deadband Current reporting dead band, counts (1–32767 counts) 100
V-Analogue Deadband Voltage reporting dead band, counts (1–32767 counts) 100
P-Analogue Deadband Power/Energy reporting dead band, counts (1–32767 counts) 100
F-Analogue Deadband Frequency reporting dead band, counts (1–32767 counts) 100
O-Analogue Deadband Miscellaneous Data Reporting dead band, counts (1–32767) 100
Unsolicited Report Enable Unsolicited reporting (Disabled, Enabled) Disabled
Unsol Report @pow-up Enable Unsolicited reporting at power-up (Disabled, Enabled) Disabled
Unsol Dest. Address DNP Address to report to (0–65534) 0
Start Transmit on Number of events to transmit on (1–200) 10
Age of Oldest Event Age of oldest event to transmit on (0.0–60.0 sec.) 2.0
Unsol Confm Timeout Unsolicited confirmation time out (0–50 sec.) 2
DATA-LINK OPERATION
It is necessary to make two important decisions about the data-link layer operation. One is how to
handle data-link confirmation, the other is how to handle data-link access. If a highly reliable
communications link exists, the data-link access can be disabled altogether, which significantly reduces
communications overhead. Otherwise, it is necessary to enable confirmation and determine how many
retries to allow and what the data-link time-out should be. The noisier the communications channel, the
more likely a message will be corrupted. Thus, the number of retries should be set higher on noisy
1
channels. Set the data-link time-out long enough to allow for the worst-case response of the master
plus transmission time.
Data Retrieval
Relevant DNP Settings
Method Description
Polled Static The master polls for static Set “Binary Event Data” to “CLASS 0”
(Class 0) data only. Set “Analogue Event Data” to “CLASS 0”
Set “Counter Event Data” to “CLASS 0”
Set “Unsolicited Report” to “Disabled”
Polled Report- The master polls Set “Binary Event Data” to “CLASS 1/2/3”
by-Exception frequently for event data Set “Analogue Event Data” to “CLASS 1/2/3”
and occasionally for static Set “Counter Event Data” to “CLASS 1/2/3”
data. Set “Unsolicited Report” to “Disabled”
Unsolicited The slave devices send Set “Binary Event Data” to “CLASS 1/2/3”
Report-by- unsolicited event data to Set “Analogue Event Data” to “CLASS 1/2/3”
Exception the master and the master Set “Counter Event Data” to “CLASS 1/2/3”
occasionally sends Set “Unsolicited Report” to “Enabled”
integrity polls for static
Set “Start Transmit on” and “Age of Oldest Event”
data.
according to how often messages are desired to be
sent.
Quiescent The master never polls Set “Binary Event Data” to “CLASS 1/2/3”
and relies on unsolicited Set “Analogue Event Data” to “CLASS 1/2/3”
reports only. Set “Counter Event Data” to “CLASS 1/2/3”
Set “Unsolicited Report” to “Enabled”
Set “Start Transmit on” and “Age of Oldest Event”
according to how often messages are desired to be
sent.
DEVICE PROFILE
The following is the device profile as specified in the DNP V3.00 Subset Definitions document:
2
DNP V3.00
DEVICE PROFILE DOCUMENT
This document must be accompanied by a table having the following headings:
Object Group Request Function Codes Response Function Codes
Object Variation Request Qualifiers Response Qualifiers
Object Name (optional)
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported
(the complete list is described in the attached table):
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted 2048 (if >2048, must
Transmitted 292
be configurable)
Received (must be 292) Received 2048 (must be >249)
3
Timeouts while waiting for:
Data Link Confirm None Fixed at Variable Configurable
Complete Appl. Fragment None Fixed at Variable Configurable
Application Confirm None Fixed at Variable Configurable
Complete Appl. Response None Fixed at Variable Configurable
Others
Attach explanation if 'Variable' or 'Configurable' was checked for any timeout.
Reports Binary Input Change Events when no Reports time-tagged Binary Input Change
specific variation requested: Events when no specific variation requested:
Never Never
Only time-tagged Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative
Configurable to send both, one or the Time
other (attach explanation) Configurable (attach explanation)
4
Default Counter Object/Variation: Counters Roll Over at:
No Counters Reported No Counters Reported
Configurable (attach explanation) Configurable (attach explanation)
Default object 20 16 Bits
Default variation 6 32 Bits
Point-by-point list attached Other Value
Point-by-point list attached
In all cases within the device profile that an item is configurable, it is controlled by VISIONr settings.
OBJECT TABLE
The supported object, function and qualifier code combinations are given by the following table.
Request Response
Object (supported) (may generate)
Func Qual Func Qual
*default
Codes Codes Codes Codes
Obj Var Description (dec) (hex) (dec) (hex)
5
Request Response
Object (supported) (may generate)
Func Qual Func Qual
*default
Codes Codes Codes Codes
Obj Var Description (dec) (hex) (dec) (hex)
6
Request Response
Object (supported) (may generate)
Func Qual Func Qual
*default
Codes Codes Codes Codes
Obj Var Description (dec) (hex) (dec) (hex)
7
Request Response
Object (supported) (may generate)
Func Qual Func Qual
*default
Codes Codes Codes Codes
Obj Var Description (dec) (hex) (dec) (hex)
DATA MAP
The following is the default object map supported by the VISIONr relay.
8
DNP Object Type Index Description
10,12 02 Control “Protection Enabled” bit
10,12 03 Control “E/F Enabled” bit
10,12 04 Status of “Remote Enabled” bit(Read only)
10,12 05 Control “AUX2 Enabled” bit
10,12 06 Control “Liveline Enabled” bit
10,12 07 Control “Recloser Enabled” bit
10,12 08 Control “AUX1 Enabled” bit
10,12 09 Control “AUX3 Enabled” bit
10,12 10 Serial reset faults
10,12 11 Reset energies.
10,12 12 Reset demands/demand peaks.
10,12 13 Read next relay event.
30,32 00 I1 magnitude.
30,32 01 I2 magnitude.
30,32 02 I3 magnitude.
30,32 03 I0 magnitude.
30,32 04 Reserved
30,32 05 Pre-trip I1.
30,32 06 Pre-trip I2.
30,32 07 Pre-trip I3.
30,32 08 Pre-trip I0.
30,32 09 Reserved.
30,32 10 Pre-alarm I1
30,32 11 Pre-alarm I2
30,32 12 Pre-alarm I3
30,32 13 Pre-alarm I0
30,32 14 Reserved
30,32 15 V1 magnitude
30,32 16 V2 magnitude
30,32 17 V3 magnitude
9
DNP Object Type Index Description
30,32 18 V12 magnitude
30,32 19 V23 magnitude
30,32 20 V31 magnitude
30,32 21 Pre-trip V1.
30,32 22 Pre-trip V2
30,32 23 Pre-trip V3.
30,32 24 Pre-alarm V1.
30,32 25 Pre-alarm V2.
30,32 26 Pre-alarm V3.
30,32 27 A-phase power (P1).
30,32 28 B-phase power (P2).
30,32 29 C-phase power (P3).
30,32 30 3-phase power (P1+P2+P3).
30,32 31 Reserved
30,32 32 A-Phase power peak demand.
30,32 33 B-Phase power peak demand.
30,32 34 C-Phase power peak demand.
30,32 35 A-Phase apparent power.
30,32 36 B-Phase apparent power.
30,32 37 C-Phase apparent power.
30,32 38 A-Phase reactive power.
30,32 39 B-Phase reactive power.
30,32 40 C-Phase reactive power.
30,32 41 A-Phase accumulated power (energy).
30,32 42 B-Phase accumulated power (energy).
30,32 43 C-Phase accumulated power (energy).
30,32 44 3-Phase accumulated power (energy).
30,32 45 A-Phase accumulated apparent power (energy).
30,32 46 B-Phase accumulated apparent power (energy).
30,32 47 C-Phase accumulated apparent power (energy).
30,32 48 Pre-trip A-phase power.
30,32 49 Pre-trip B-phase power.
30,32 50 Pre-trip C-phase power.
30,32 51 Pre-alarm A-phase power.
30,32 52 Pre-alarm B-phase power.
10
DNP Object Type Index Description
30,32 53 Pre-alarm C-phase power.
30,32 54 Frequency
30,32 55 Pre-trip frequency.
30,32 56 Pre-alarm frequency.
30,32 57 A-phase power factor.
30,32 58 B-phase power factor.
30,32 59 C-phase power factor.
30,32 60 Feeder load rate.
30,32 61 Phase current scale.
30,32 62 E/F current scale.
30,32 63 Last trip number.
30,32 64 Last alarm number.
30,32 65,66,67 SER event time in DNP format (high, middle, and low 16
bits).
30,32 68 SER event ID and Asserted/De-asserted status (see
table for definition).
Binary inputs (objects 1 and 2) are supported as defined by the previous table. Binary inputs 0–120
(excluding point 8) are scanned approximately once per second to generate events. When time is
reported with these event objects, it is the time at which the scanner observed the bit change. This may
be significantly delayed from when the original source change and should not be used for sequence-of-
events determination.
Binary Inputs 128–148 are derived from the Sequential Events Recorder (SER) and carry the time
stamp of actual occurrence with 10ms resolution. Static reads from these inputs will show the same
data as a read from the corresponding index in the 0–120 group. Only points that are actually in the
SER list will generate events in the 120–148 group.
Analogue Inputs (objects 30 and 32) are supported as defined by the preceding table. The values are
reported in primary units. Analogue inputs 0–2, 5–7 and 10–12 are further scaled according to the
reading value of analogue input 61 (scale range 1,10,100). Similarly, Analogue inputs 3, 8 and 13 are
further scaled according to the reading value of analogue input 62 (scale range 1,10,100).
Analogue inputs 27-53 are power or energy related, whose formats and units are determined by the
setting of “Comms Power Scale” in the “Serial Settings” page. If above setting is set to “Fixed”, then
the unit of these analogue inputs is 100kW, 100kW·Hrs, 100kVA or 100kVA·Hrs, and the value is as it
appears and it needs no further conversion. If above setting is set to “Auto”, then the unit of these
11
analogue inputs is 0.1kW, 0.1kW·Hrs, 0.1kVA or 0.1kVA·Hrs, and it needs further conversion to get
the right reading value as described bellow.
The reading is 16 bits format and is defined as:
bit 15 = Sign (0 = positive, 1 = negative);
bit 14,13 and 12=3 bits Exponent ( exponent = 4 * bit14 + 2 * bit13 + bit12 );
bit 11,10,9,...,1,0=12 bits mantissa ( mantissa = (2048 * bit11 + 1024 * bit10 + 512 * bit9 + ... + 2 *
bit1 + bit0);
So the total power or energy = sign * mantissa * (10**exponent) * (unit stated above).
The scale for analogue points 54-56 (frequency) is fixed to 10 and the remaining analogues are not
scaled.
Event-class messages are generated whenever an input changes beyond the value given by the
corresponding dead band settings. The dead-band check is done after any scaling is applied.
Generally speaking, analogue inputs except points 65–68 are scanned at approximately a 1-second rate,.
During a scan, all events generated will use the time the scan was initiated. Analogues 65–68 are
derived from the history queue data for the most recently read fault. Analogue 68 is a 16-bit composite
value and it is defined as follows,
The lower byte (bit 7 to bit 0) = SER event ID (i.e. the corresponding binary input point which initiates
the SER event). bit 8 = the status of SER event (i.e. bit 8 = 1: Asserted, bit 8 = 0: De-asserted).
Control Relay Output Blocks (object 12, variation 1) are supported. The control relays correspond to
the remote bits and other functions, as shown above. The control field is interpreted as follows:
Index Close (0x4X) Trip (0x8X) Latch On (3) Latch Off (4) Pulse On (1) Pulse Off (2)
0 Do nothing Do nothing Pulse CC Do nothing Do nothing Do nothing
1 Do nothing Do nothing Pulse OC Do nothing Do nothing Do nothing
2-9 Do nothing Do nothing Set Clear Do nothing Do nothing
10-12 Do nothing Do nothing Pulse Do nothing Do nothing Do nothing
13 Do nothing Do nothing Read Oldest Do nothing Do nothing Do nothing
The Status field is used exactly as defined. All other fields are ignored. A pulse operation asserts a
point for a single processing interval. Caution should be exercised with multiple remote bit pulses in a
single message (i.e., point count > 1), as this may result in some of the pulse commands being ignored
and returning an already active status.
The Relay Event Summary data are available on a first in, first out (FIFO) basis. To read the SER
summary data, the master should monitor binary input point 8, which will be on when there is an
unread relay event summary. To read the oldest relay event summary, the master should Pulse-On
binary output point 13. This will load the relay event summary analogues (points 65-68) with
information from the oldest relay event summary, discarding the values from the previous load. After
reading the analogues, the master should again check binary input point 8, which will be on if there is
another unread relay event summary. The master should continue this process until binary input point
12
8 is off. If the master attempts to load values using output point 13 when binary input point 8 is off, the
relay event type analogue (point 65-67) will be loaded with zero, and analogue point 68 will be loaded
with 65535. With the FIFO method the relay event summaries will always be collected in
chronological order.
In order for this to work successfully, binary output 8 must be pulsed no faster than once every twenty
milliseconds. If binary output 8 is pulsed faster, some data may not be recognised and processed by the
DNP event scanner.
POINT REMAPPING
The analogue and binary input points (objects 1, 2, 30, and 32) may be remapped via the P&B
commands (using “P&B Std” protocol, i.e. change the “Serial Protocol” to “P&B Std”). A Microsoft
VB based application program provides the remapping function as well as the function of adding the
binary input points into the SER event list, which is of easy use (using windows interface). The order
they occur in the remapped list determines the index that the corresponding value is reported as to the
DNP master. If a value is not in the list, it is not available to the DNP master. All 121 binaries and 69
analogues may be included in the list, but may occur only once. The maps are stored in non-volatile
memory.
Index Definition
0 Power Up
1 Trip
2 Alarm
3 Inhibit
4 Seq. Lockout
5 Supply Missing
6 Reserved 1
7 Reserved 2
9 Protection Enabled
10 E/F Enabled
11 Remote Enabled
13
12 AUX 2 Enabled
13 Liveline Enabled
14 Reclose Enabled
15 Aux 1 Enabled
16 Aux 3 Enabled
20 Digital input 4
21 Digital input 5
22 Digital input 6
23 Digital input 7
24 Digital input 8
25 Digital input 9
26 Digital input 10
27 Digital input 11
28 Digital input 12
31 Relay Output 3
32 Relay Output 4
33 Relay Output 5
34 Relay Output 6
35 Relay Output 7
36 Relay Output 8
37 Undervoltage Trip
38 Overvoltage Trip
14
43 Load Increased Trip
44 Overcurrent 1 Trip
45 Overcurrent 2 Trip
47 HS Overcurrent Trip
63 Overcurrent 3 Trip
64 Overcurrent 4 Trip
65 HS Overcurrent 1 Trip
66 HS Overcurrent 2 Trip
67 HS Overcurrent 3 Trip
68 HS Overcurrent 4 Trip
15
73 Single Shot O/C Trip
79 Undervoltage Pickup
80 Overvoltage Pickup
86 Overcurrent 1 Pickup
87 Overcurrent 2 Pickup
89 HS Overcurrent Pickup
16
104 Earth Fault 4 Pickup
The binary input points 128-148 are encoded the same as inputs 000–120 with 128 added only.
17