Pacis MPP-DNP3 en

ESO-PACiS MPP DNP3
Gateway and C264
ESO-PACIS MPP-DNP3 EN / E41
PACiS V6.3
Master Protocol Profile

DNP3
www.schneider-electric.com
Legal Information
The Schneider Electric brand and any registered trademarks of
Schneider Electric Industries SAS referred to in this guide are
the sole property of Schneider Electric SA and its subsidiaries.
They may not be used for any purpose without the owner's
permission, given in writing. This guide and its content are
protected, within the meaning of the French intellectual property
code (Code de la propriété intellectuelle français, referred to
hereafter as "the Code"), under the laws of copyright covering
texts, drawings and models, as well as by trademark law. You
agree not to reproduce, other than for your own personal,
noncommercial use as defined in the Code, all or part of this
guide on any medium whatsoever without Schneider Electric's
permission, given in writing. You also agree not to establish any
hypertext links to this guide or its content. Schneider Electric
does not grant any right or license for the personal and
noncommercial use of the guide or its content, except for a
non-exclusive license to consult it on an "as is" basis, at your
own risk. All other rights are reserved.
Electrical equipment should be installed, operated, serviced

and maintained only by qualified personnel. No responsibility is
assumed by Schneider Electric for any consequences arising
out of the use of this material.
A qualified person is one who has skills and knowledge related

to the construction, installation, and operation of electrical
equipment and has received safety training to recognize and
avoid the hazards involved.
As standards, specifications and designs change from time to

time, please ask for confirmation of the information given in this
publication.
Issue A
Safety Information
Read these instructions carefully and look at the equipment to become

familiar with the device before trying to install, operate, service, or maintain
it. The following special messages may appear throughout this manual or
on the equipment to warn of potential hazards or to call attention to
information that clarifies or simplifies a procedure.
The addition of either symbol to a “Danger” or

“Warning” safety label indicates that an electrical
hazard exists which will result in personal injury if the
instructions are not followed.
This is the safety alert symbol. It is used to alert you to

potential personal injury hazards. Obey all safety
messages that follow this symbol to avoid possible
injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in
death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in
death or serious injury.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in
minor or moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury. The safety
alert symbol shall not be used with this signal word.
ESO-PACIS MPP-DNP3 EN / E41 - Issue A Master Protocol Profile Documentation
Page 4/28 ESO-PACiS MPP - DNP3
CONTENTS
1. INTRODUCTION 5
1.1 Scope of the document 5
1.2 Glossary 5
2. DNP3 MASTER SPECIFICITY 6

2.1 Chapter Finality 6
All rights reserved. Schneider Electric. Passing on and copying of this document, use and communication of its contents are not permitted without prior written authorization.
2.2 Generic Behaviors 6
2.3 Legacy IP line redundancy management 7
2.3.1 Alternate connection tries 8
2.3.2 Alternate and Double operation 8
2.4 Data received from IEDs 9
2.4.1 Data points GI and cyclical acquisition 9
2.4.2 Management of DPS (Double Point Status) 10
2.4.3 Management of SPS, DPS, MV and Counter Quality 11
2.4.3.1 SPS 11
2.4.3.2 DPS 12
2.4.3.3 MV 13
2.4.3.4 Counter 14
2.5 Data sent to IEDs 15
3. LIMITS AND PERFORMANCES 17

4. CONFIGURATION 18
5. MASTER DNP3 PROFILE 20
5.1 Device Properties 20
5.2 DNP.3 Level 3 Implementation Table (DNP3-L3) 22
Master Protocol Profile Documentation ESO-PACIS MPP-DNP3 EN / E41 - Issue A
ESO-PACiS MPP - DNP3 Page 5/28
1. INTRODUCTION
1.1 Scope of the document
This document is a chapter of PACiS GATEWAY documentation binders. It addresses
protocol profile and specificity of the DNP3 Master Station communication protocol
implemented on PACiS GATEWAY.
This document deals with DNP3 communication with IEDs (Intelligent Electronic Devices) on
legacy bus.
In this document, unless explicitly stated, the name Master will be used to designate the
"PACiS GATEWAY" Master DNP3 protocol.

1.2 Glossary
DE Direct Execute
DPC Double Point Control
DPS Double Point Status
GI General Interrogation
GPS Generic Product Specification
IED Intelligent Electronic Device
Master Used to designate either the "MiCOM C264" computer or the "PACiS
GATEWAY" personal computer
MV Measurement Value
SBO Select Before Execute
SPC Single Point Control
SPS Single Point Status
SP Setpoint
UTC Universal Time Coordinated
2. DNP3 MASTER SPECIFICITY

2.1 Chapter Finality
The purpose of this chapter is not to describe the DNP3 protocol but to focus on both
specificity of DNP3 functions and specificity of the implementation of DNP3 on the master
equipment (PACiS GATEWAY).
PACiS GATEWAY communication protocols default behaviors are described in the PACiS
communication GPS. Only parts which need precisions or present deviations are described
here. Please, notice that there are some differences between Pacis MiCOM C264 and
PACiS GATEWAY DNP3 Master management.
NOTE: The reader is expected to have knowledge on the DNP3 protocol.
2.2 Generic Behaviors
Physical layer (protocol communicate link):
GTW Description
S Serial link
S TCP over IP
S UDP over IP
In the above table: S is standing for supported, N is standing for not supported.
Initialization frame:
− To connect an IED, a “Reset CU” (function 0) frame is sent to the IED.
− When the response is OK, the Master DNP3 send a message to the application to tell
that connection step is passed.
− The polling period is defined using the “Downgraded cycle” parameter.

Synchronization process:
− The DNP3 object used to synchronize IEDs is “Write Date and Time Request (Object
50, Variation 1).
− The calculation of the transmission delay compensation is not performed.
− Synchronization is sent at connection of an IED and cyclically in broadcast. The

Period of synchronization is configurable with “synchronization cycle” configuration
parameter.
Dating specificity:
− The "master" handles the synchronization status of each IED. The synchronization
status of a DNP3 IED is given by the IIN1.4 [NEED_TIME] bit of DNP3 application
message headers. The IED is considered synchronized when the “need time” bit is in
reset state.
− Non-dated events sent by IED are time tagged, on reception, by the master.
− Synchronization status of dated events is given as follows:
 When the master is not synchronized, time tagged received events are tagged
non-synchronized
 When the master is synchronized, synchronization tag is given by the

synchronization status of the IED (coming from IIN1.4 [NEED_TIME] bit).
General Interrogation:
− GI is done using the class 0 (static data) read request (group “60” variation “1”). This
allows the master to update his database with static data from the IEDs.
− GI is requested at IED connection. GI can be requested cyclically by the master. The

GI polling period is configurable using the “class 0 polling period” configuration
parameter. When this parameter is set to 0 second, there is no cyclic GI.
− On GTW: On IED connection, a warm restart is sent to the IED to clear event queues.
The request is sent before the first GI request.
Event management:
− The “master” implementation does not support unsolicited response.
− Events will only be transmitted on polling request (I.E. slave devices have to wait for
being polled by the master to transmit an event).
− Polling of events is done cyclically on IEDs by using a class 1 to 3 read request

(Group 60, variation 2, 3, 4).
Polling sequencing:
− IEDs of the network are polled cyclically in sequence. The sequence may be
momentarily interrupted to transmit a synchronization message or a command.
2.3 Legacy IP line redundancy management

DNP3 IP Master Protocol offers the facility to manage line redundancy in DOUBLE or ALTERNATE
configuration.
2.3.2
2.3.1
Page 8/28
Alternate connection tries
Alternate and Double operation

ESO-PACIS MPP-DNP3 EN / E41 - Issue A
ESO-PACiS MPP - DNP3

Master Protocol Profile Documentation
2.4 Data received from IEDs

2.4.1 Data points GI and cyclical acquisition
Data from IED’s are cyclically polled using object group 60 for GI and event polling.
Object Variation Data GI Event Function

group (optional Polling
polling)
60 01 Class 0  [1] READ

60 02, 03, 04 Class 1,2,3  [1] READ
Class 0 objects (polled for GI) shall be:
Type of data Object group Data
SPS (Single Point Status) and 01 Static Binary Input

DPS (Double Point Status) (1)
Counter Value 20 Static Counter
MV (Measurement Value) 30 Static Analogue Input

Class 1 to 3 objects (polled for events acquisition) shall be:
Type of data Object group Data
SPS (Single Point Status) and 02 Binary Input Event

DPS (Double Point Status) (1)
Counter Value 22 Counter Event
MV (Measurement Value) 32 Analogue Input Event
(1) “Double-bit Binary Input” (object group “3”) is not available in the actual version of
DNP3 level 3 implementation. On PACiS GTW, DPS (Double Points Status) can be
configured through configuration of the associated Open and Close Dnp3 binary
Inputs.
2.4.2 Management of DPS (Double Point Status)
The DPS is associated to two binary inputs.
Constraint: The address of the “binary input” representing the Contact Close (CC) must be the
one of the Contact Open (CO) + 1 (“address CC” = “address CO” + 1).
The transient states [CO, CC] = [0, 0] and [CO, CC] = [1, 1] are filtered provided both binary
inputs are received in the same Dnp3 response.
Others states changes are immediately signalled.
2.4.3 Management of SPS, DPS, MV and Counter Quality

2.4.3.1 SPS
In the below table we assume :
• When the “Comm.lost” bit is set, the SPS quality is set to UNKNOWN.
• Else, When one of the “Forced” bit is set, the SPS quality is set to SUBSTITUTED.
• Else, When the “Restart” bit is set, then the SPS quality is set to UNKNOWN.
• Else, When “on-line” is reset, the SPS quality is set to SELFCHECKFAULT
• The “Reserved” bit is not taken into account.
Hence, when a “Forced” bit is set, others quality bits are not considered except the
“Comm.lost” bit.
Legend:
• X : mean « 0 » or « 1 ».
• (S): received state is used :
• “State BS1[7]”=0 => RESET
• “State BS1[7]”=1 => SET
• (Fo): “Remote Forced BS1[3]” = 1 OR “Local Forced BS1[4]” =1.
2.4.3.2 DPS
STATES:
QUALITY:
In the table below:
• “SPS 1” can be the Contact OPEN or the Contact CLOSE SPS of the DPS.
• T mean value is True, F or Empty cell mean value is false, x mean value can be
True or False.
2.4.3.3 MV
• When the “Comm.lost” bit is set, the SPS quality is set to UNKNOWN.
• Else, When one of the “Forced” bit is set, the MV quality is set to SUBSTITUTED.
• Else, When the “Restart” bit is set, then the MV quality is set to UNKNOWN.
• Else, When “on-line” is reset, the MV quality is set to SELFCHECKFAULT
• The “Reserved” bit is not taken into account.
Legend:
• X : mean « 0 » or « 1 ».
• V : The MV value received.
2.4.3.4 Counter
• When the “Comm.lost” bit is set, the CT quality is set to UNKNOWN.
• Else, When one of the “Forced” bit is set, the CT quality is set to SUBSTITUTED.
• Else, When the “Restart” bit is set, then the CT quality is set to UNKNOWN.
• Else, When “on-line” is reset, the CT quality is set to SELFCHECKFAULT
• The “Reserved” , “Roll-Over” and “Discontinuity” bits are not taken into account.
Legend:
• X : mean « 0 » or « 1 ».
• V : The MV value received.
2.5 Data sent to IEDs
− Digital controls (Set, Reset, Trip, Close): DNP3 object 12 is used with Variation 01.
− Set time control: DNP3 object 50 is used with Variation 01.
− Analog Control DNP3 object 41 is used with Variation 02.

Table of used control objects and associated control functions:
Object Variation Data Function

12 01 Binary Command - 3 (select)
Control Relay Output

4 (operate)
Block (CROB)
5 (direct op)
41 02 Analog output (16bits) 5 (direct op)
50 01 Time and Date – 2 (write)
Absolute time
The DNP3 Master manages both direct controls sequence and Select Before Operate (SBO)
control sequence for digital controls, and only Direct Operate (DO) for Analog Controls.
As CROB parameters are not accessible on DNP3 Master for GTW, following behavior must
be considered:
SCE (configurator) SPC/DPC parameters:

DPC
• Activation mode: [Transient, Permanent, Permanent until feedback]
• Close duration (ms): [0, 15000] step 10
• Open duration (ms): [0, 15000] step 10
SPC
• Activation mode: [Transient, Permanent, Permanent until feedback]
• Order on duration (ms): [0, 15000] step 10
For TAP changer associated to DPC, Open means Raise, Close means Lower.
Reminder: Control relay output block (CROB) Pictorial:

In the below table, “Permanent until feedback” and “Permanent” are regrouped in
“Permanent”. This to say that “Permanent until feedback” is managed as “Permanent” for
DNP3 Master protocol.
Control code
Activation
mode TCC CR QU OP Type On-Time DESCRIPTION
Hex
7 6 5 4 3 2 1 0
0x03 0 0 0 0 0 0 1 1 0 NUL / LATCH ON

SPC Permanent
0x04 0 0 0 0 0 1 0 0 0 NUL / LATCH OFF
0x20 0 0 1 0 0 0 0 0 0 NUL / CANCEL
0x01 0 0 0 0 0 0 0 1 On Duration NUL / PULSE ON

SPC Transient
0x00 0 0 0 0 0 0 0 0 0 NUL/NUL
0x20 0 0 1 0 0 0 0 0 0 NUL / CANCEL
0x43 0 1 0 0 0 0 1 1 0 CLOSE / LATCH ON

DPC Permanent 0x83 1 0 0 0 0 0 1 1 0 TRIP / LATCH ON
0x20 0 0 1 0 0 0 0 0 0 NUL / CANCEL
0x41 0 1 0 0 0 0 0 1 Close Duration CLOSE / PULSE ON

DPC Transient 0x81 1 0 0 0 0 0 0 1 Open Duration TRIP/ PULSE ON
0x20 0 0 1 0 0 0 0 0 0 NUL / CANCEL
Other fields:
− Count Field: Always set to “1”
− Off-Time field: Always set to “0”
− “RES/Status Code” = “0”

3. LIMITS AND PERFORMANCES

Disturbance management is not treated in DNP3 Protocol.
Tunneling management is not treated in DNP3 Protocol.
There is No Application Layer Re-tries.
Maximum Data Link Frame Size (octets):
− Transmitted: 292
− Received: (must be 292)

Maximum Application Fragment Size (octets):
− Transmitted (configurable: 15 to 2048 octets)
− Received 2048
4. CONFIGURATION
The following parameters shall be available from configuration tool.
General attributes of DNP3 Master:
Parameter Value Comments

Master address 0 to 65535 DNP3 Master link address
Acknowledgement 1 to 300 [x100 ms] Time out for data link.
time-out (AT) (*)
Default = 300
Number of retries 1 to 10 Maximum number of retries in case of non
(NT) (*) response of an IED before declaring it
disconnected.
Default = 2
Class 0 polling 0 to 3600 [seconds] No polling when set to “0”
period
Default = 0
Synchronization 1 to 65535 [x10 seconds] If set to “65535” synchronization is not sent
cycle cyclically.
Application time-out 0 to 255 [seconds] Time-out for multifragments.
0: use auto calculated value, by the
software. Better to impose a known value.
Default = 0
Downgraded cycle 10 to 100 [x100 ms] Deadline between two polling of a
(DC) (*) disconnected IED.
Default = 50
(*) Constraint to be respected:

If "N" is the number of IEDs on the DNP3 network, then DC > N * AT * NT
General attributes for DNP3 outstations (IEDs):
Parameter Value Comments

IED address 0 to 65535 Link Address of the device
Outstation Data point addressing:
Data point Parameter

SPS address 0 to 65535 index over protocol
DPS address 0 to 65535 Open index over protocol
And
Close index over protocol
SPC Address 0 to 65535 index over protocol
Order type SBO, DE Select Execute from the SCADA or
Direct Execute (protocol view)
DPC Address 0 to 65535 index over protocol

Order type SBO, DE Select Execute from the SCADA or
Direct Execute (protocol view)
SP Address 0 to 65535 index over protocol
Order type DE Direct Execute (protocol view)
MV address 0 to 65535 index over protocol
Counter address 0 to 65535 index over protocol
5. MASTER DNP3 PROFILE

5.1 Device Properties
DNP V3.00 Device Profile

Vendor Name: SCHNEIDER ELECTRIC ENERGY SA
Device Name: PACiS GATEWAY
Highest DNP Level Supported: Device Function:
For Requests Level 3 ◼ Master  Slave
For Responses Level 3
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels supported:
________________________________________________________
________________________________________________________
Maximum Application Fragment Size (octets):

Maximum Data Link Frame Size (octets):
Transmitted: 2048
Transmitted: 292
Received: (must be 292)
Received: 4096
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
 None ◼ None
 Fixed at _______________________  Configurable, range ____ to _______
◼ Configurable, range 1 to 10 ( Fixed is not permitted )
Requires Data Link Layer Confirmation:
 Never
 Always
◼ Sometimes If ’Sometimes’, when? For serial communication only
 Configurable If ’Configurable’, how?

User option to set Data Link Confirmation to:
• Always – device will always request Data Link Confirmations.
• Multi-packet only – the device will request Data Link Confirmations when
sending multi-packet responses.
• Never – the device will never request Data Link Confirmations.
Requires Application Layer Confirmation:
◼ Never
 Always (not recommended)
 When reporting Event Data (Slave devices only)
 When sending multi-fragment responses (Slave devices only)
 Sometimes If 'Sometimes', when? ______________________________________________
 Configurable If 'Configurable', how? ______________________________________________
Timeouts while waiting for:
Data Link Confirm  None  Fixed at 3s  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
Data Link Confirm : aknowledgement time-out (x100 ms) [1,300]
Complete Appl. Fragment : application time-out (s) [0,255] (0 : calculated by the application)
See $4 Configuration
Attach explanation if 'Variable' or 'Configurable' was checked for any timeout
DNP V3.00 Device Profile

Sends/Executes Control Operations:
WRITE Binary Outputs  Never  Always  Sometimes ◼ Configurable

SELECT/OPERATE  Never  Always  Sometimes ◼ Configurable
DIRECT OPERATE  Never  Always  Sometimes ◼ Configurable
DIRECT OPERATE - NO ACK ◼ Never  Always  Sometimes  Configurable
Count > 1 ◼ Never  Always  Sometimes  Configurable

Pulse On  Never  Always  Sometimes ◼ Configurable
Pulse Off  Never  Always  Sometimes ◼ Configurable
Latch On  Never  Always  Sometimes ◼ Configurable
Latch Off  Never  Always  Sometimes ◼ Configurable
Queue ◼ Never  Always  Sometimes  Configurable

Clear Queue ◼ Never  Always  Sometimes  Configurable
• Select timeout: configurable

5.2 DNP.3 Level 3 Implementation Table (DNP3-L3)

Strikethrough information in grey is not processed by the master (but must still be parsed)
Functionality supported beyond the subset level are Highlighted
OBJECT REQUEST RESPONSE

(Master can issue) (master parses)
Grp. Var. Description Func. Qualifier Function Qualifier

Codes Codes Codes Codes
(dec) (hex) (hex)
1 (read) 00, 01 (start-stop)
1 0 Binary Input – Any Variation
22 (assign class) 06 (no range, or all)
00, 01 (start-stop)
1 1 Binary Input − Packed format 1 (read) 129 (response) 00, 01 (start-stop)
06 (no range, or all)
00, 01 (start-stop)
1 2 Binary Input − with flags 1 (read) 129 (response) 00, 01 (start-stop)
2 0 Binary Input Event − Any Variation 1 (read)
07, 08 (limited qty)
06 (no range, or all) 129 (response)
2 1 Binary Input Event − without Time 1 (read) 17, 28 (index)
07, 08 (limited qty) 130 (unsol. Resp)
2 2 Binary Input Event − with AbsoluteTime 1 (read) 17, 28 (index)
Binary Input Event − with Relative 06 (no range, or all) 129 (response)
2 3 1 (read) 17, 28 (index)
Time 07, 08 (limited qty) 130 (unsol. Resp)
00, 01 (start-stop)
10 0 Binary Output - Any Variation 1 (read)
Binary Output – Output status with 00, 01 (start-stop)
10 2 1 (read) 129 (response) 00, 01 (start-stop)
flags 06 (no range, or all)
3 (select)
Binary Command - Control Relay Output 4 (operate)
12 1 Block (CROB) (1) 17,28 (index) 129 (response) Request echo
5 (direct op)
6 (dir. op, no ack)
1 (read)
7 (freeze)
00, 01 (start-stop)
20 0 Counter - Any Variation 8 (freeze noack)
9 (freeze clear)
10 (frz. cl. noack)
00, 01 (start-stop)
20 1 Counter - 32-Bit with flag 1 (read)
129 (response 00, 01 (start-stop)
00, 01 (start-stop)
20 2 Counter - 16-Bit with flag 1 (read)
00, 01 (start-stop)
20 5 Counter - 32-Bit without Flag 1 (read)
00, 01 (start-stop)
20 6 Counter - 16-Bit without Flag 1 (read)
1 (read) 00, 01 (start-stop)

21 0 Frozen Counter –Any Variation
22 (assign class) 06 (no range, or all)
00, 01 (start-stop)
21 1 Frozen Counter –32-Bit with flag 1 (read) 129 (response) 00, 01 (start-stop)
00, 01 (start-stop)
21 2 Frozen Counter –16- Bit with flag 1 (read) 129 (response) 00, 01 (start-stop)
Frozen Counter –32-Bit without 00, 01 (start-stop)
Flag 06 (no range, or all)
Frozen Counter –16-Bit without 00, 01 (start-stop)
Flag 06 (no range, or all)
22 0 Counter Event - Any Variations 1 (read)
22 1 Counter Event - 32-Bit with flag 1 (read)
07, 08 (limited qty) 130
17, 28 (index)
(unsol. Resp)
22 2 Counter Event - 16-Bit with flag 1 (read)
17, 28 (index)
(unsol. Resp)


(dec) (hex) (hex)

22 5 Counter Event - 32-Bit with time 1 (read)
17, 28 (index)
(unsol. Resp)
22 6 Counter Event - 16-Bit with time 1 (read)
17, 28 (index)
(unsol. Resp)
Frozen Counter Event - Any 06 (no range, or all)

23 0 1 (read)
Variation 07, 08 (limited qty)
Frozen Counter Event - 32-Bit with 06 (no range, or all) 129 (response)
23 1 1 (read) 17, 28 (index)
flag 07, 08 (limited qty) 130 (unsol. Resp)
Frozen Counter Event - 16-Bit with 06 (no range, or all) 129 (response)
23 2 1 (read) 17, 28 (index)
flag 07, 08 (limited qty) 130 (unsol. Resp)
1 (read) 06 (no range, or all)
30 0 Analogue Input - AnyVariation
22 (assign class) 07, 08 (limited qty)
30 1 Analogue Input - 32-Bit with flag 1 (read)
129 (response) 00, 01 (start-stop)

30 2 Analogue Input - 16-Bit with flag 1 (read)

30 3 Analogue Input - 32-Bit without Flag 1 (read)

30 4 Analogue Input - 16-Bit without Flag 1 (read)

32 0 Analogue Input Event - Any Variation 1 (read)
32 1 Analogue Input Event - 32-Bit without Time 1 (read)
17, 28 (index)
(unsol. Resp)
32 2 Analogue Input Event - 16-Bit without Time 1 (read)
17, 28 (index)
(unsol. Resp)
32 3 Analogue Input Event – 32-Bit with Time 1 (read) 17, 28 (index)
32 4 Analogue Input Event - 16-Bit with Time 1 (read)
17, 28 (index)
(unsol. Resp)
Analogue Output Status – Any 00, 01 (start-stop)
40 0 1 (read)
Variation 06 (no range, or all)
Analogue Output Status – 32 with 00, 01 (start-stop)
flag 06 (no range, or all)
Analogue Output Status – 16- with 00, 01 (start-stop)
flag 06 (no range, or all)
3 (select)
4 (operate)
41 1 Analogue Output – 32-Bit 17,28 (index) 129 (response) Request echo
5 (direct op)
6 (dir. op, no ack)
3 (select)
4 (operate)
41 2 Analogue Output – 16-Bit 17,28 (index) 129 (response) Request echo
5 (direct op)
6 (dir. op, no ack)
07 (limited qty)
1 (read) 07 (limited qty=1) 129 (response)
50 1 Time and Date – Absolute time (qty = 1)
2 (write) 07 (limited qty=1)
Time and Date CTO – Absolute time 129 (response) 07 (limited qty)
51 1
synchronized 130 (unsol. Resp) (qty = 1)
Time and Date CTO – Absolute time 129 (response) 07 (limited qty)
51 2
unsynchronized 130 (unsol. Resp) (qty = 1)
07 (limited qty)
52 1 Time Delay – Coarse 129 (response)
(qty = 1)
07 (limited qty)
52 2 Time Delay – Fine 129 (response)
(qty = 1)


(dec) (hex) (hex)
60 1 Class Objects––– Class 0 Data 1 (read) 06 (no range, or all)

1 (read)
60 2 Class Objects––– Class 1 Data 20 (enbl. unsol.)
21 (dab. unsol.) 06 (no range, or all)
22 (assign class)
1 (read)
22 (assign class)
1 (read)
22 (assign class)
00 (start - stop)
Internal Indications – Packed 2 (write)
(index=7 )
80 1
format
1 (read) 00,01 (start - stop) 129 (response) 00, 01 (start-stop)
No Object (function code only) 13 (cold restart)
No Object (function code only) 23 (delay meas)
Remarks: Object 12 Commands must be selected / executed on one data point

Customer Care Centre
http://www.schneider-electric.com/CCC
 2019 Schneider Electric. All rights reserved.
Schneider Electric
35 rue Joseph Monier
92506 Rueil-Malmaison
FRANCE
www.schneider-electric.com Publishing: Schneider Electric
Publication: ESO-PACIS MPP-DNP3 EN / E41 10/2019

Pacis MPP-DNP3 en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pacis MPP-DNP3 en

Uploaded by

Copyright:

Available Formats

ESO-PACiS MPP DNP3

Gateway and C264

ESO-PACIS MPP-DNP3 EN / E41

Master Protocol Profile

Electrical equipment should be installed, operated, serviced

A qualified person is one who has skills and knowledge related

As standards, specifications and designs change from time to

Read these instructions carefully and look at the equipment to become

The addition of either symbol to a “Danger” or

This is the safety alert symbol. It is used to alert you to

Page 4/28 ESO-PACiS MPP - DNP3

2. DNP3 MASTER SPECIFICITY 6

3. LIMITS AND PERFORMANCES 17

ESO-PACiS MPP - DNP3 Page 5/28

"PACiS GATEWAY" Master DNP3 protocol.

Page 6/28 ESO-PACiS MPP - DNP3

2. DNP3 MASTER SPECIFICITY

− To connect an IED, a “Reset CU” (function 0) frame is sent to the IED.

− The polling period is defined using the “Downgraded cycle” parameter.

− The calculation of the transmission delay compensation is not performed.

− Synchronization is sent at connection of an IED and cyclically in broadcast. The

− Synchronization status of dated events is given as follows:

 When the master is synchronized, synchronization tag is given by the

ESO-PACiS MPP - DNP3 Page 7/28

− GI is requested at IED connection. GI can be requested cyclically by the master. The

− The “master” implementation does not support unsolicited response.

− Polling of events is done cyclically on IEDs by using a class 1 to 3 read request

2.3 Legacy IP line redundancy management

Alternate connection tries

Alternate and Double operation

ESO-PACiS MPP - DNP3

ESO-PACiS MPP - DNP3 Page 9/28

2.4 Data received from IEDs

Object Variation Data GI Event Function

60 01 Class 0  [1] READ

60 02, 03, 04 Class 1,2,3  [1] READ

Class 0 objects (polled for GI) shall be:

Type of data Object group Data

SPS (Single Point Status) and 01 Static Binary Input

Counter Value 20 Static Counter

MV (Measurement Value) 30 Static Analogue Input

Page 10/28 ESO-PACiS MPP - DNP3

Class 1 to 3 objects (polled for events acquisition) shall be:

Type of data Object group Data

SPS (Single Point Status) and 02 Binary Input Event

Counter Value 22 Counter Event

MV (Measurement Value) 32 Analogue Input Event

ESO-PACiS MPP - DNP3 Page 11/28

2.4.3 Management of SPS, DPS, MV and Counter Quality

Page 12/28 ESO-PACiS MPP - DNP3

ESO-PACiS MPP - DNP3 Page 13/28

Page 14/28 ESO-PACiS MPP - DNP3

ESO-PACiS MPP - DNP3 Page 15/28

2.5 Data sent to IEDs

− Set time control: DNP3 object 50 is used with Variation 01.

− Analog Control DNP3 object 41 is used with Variation 02.

Object Variation Data Function

Control Relay Output

SCE (configurator) SPC/DPC parameters:

Reminder: Control relay output block (CROB) Pictorial:

Page 16/28 ESO-PACiS MPP - DNP3

0x03 0 0 0 0 0 0 1 1 0 NUL / LATCH ON

0x20 0 0 1 0 0 0 0 0 0 NUL / CANCEL