Académique Documents
Professionnel Documents
Culture Documents
Quebec City
Revision History
Version
Date
Author
Comments
2007-02-27
Johanne Lavalle
2007-01-15
Jonathan Fortier
2006-07-11
Frdric Vallires
2006-01-20
Rmi Dutil
Contents
Tables ............................................................................................................................................. iii
1.
Introduction ............................................................................................................................. 1
2.
Features.................................................................................................................................... 2
2.1 Communication ..................................................................................................................... 2
2.2 Interoperability...................................................................................................................... 2
2.2.1
DNP3 Device Profile................................................................................................. 3
2.2.2
Implementation Table.............................................................................................. 6
2.3 Device Data Retrieval........................................................................................................... 10
2.4 Device Control..................................................................................................................... 10
2.4.1
Analog output control operations ............................................................................ 10
2.4.2
Binary output control operations ............................................................................. 10
2.4.2.1
OPEN/CLOSE operations using two PULSE points ..................................... 11
3.
4.
5.
Troubleshooting ..................................................................................................................... 36
Tables
Table 2-1
Table 2-2
Table 2-3
Table 2-4
Table 2-5
Table 3-1
Table 3-2
Table 3-3
Table 3-4
Table 3-5
Table 3-6
Table 3-7
Table 3-8
Table 3-9
Table 3-10
Table 3-11
Table 3-12
Table 3-13
Table 3-14
Table 3-15
Table 3-16
Table 3-17
Table 3-18
Table 4-1
Table 5-1
Troubleshooting .............................................................................................. 36
III
1.
Introduction
This manual provides the information required to install and set up a DNP3 master protocol
component on a Cybectec SMP gateway.
The DNP3 master protocol component is used to retrieve data from any device compatible with
the DNP3 protocol definition. It can also be used to control such a device.
You need to be familiar with the SMP gateway environment, master protocol concepts, and the
DNP3 protocol specification before proceeding with this document. You can obtain this
information by reading the following documents:
Transporting DNP V3.00 over Local and Wide Area Networks, DNP Users Group, 1998.
2.
Features
This chapter outlines the features provided by the DNP3 master protocol component.
2.1
Communication
The following communication features are available when connecting devices to the SMP
hardware:
Feature
Comment
Serial Ports
The DNP3 protocol component supports RS-232, RS-422 and RS485 interfaces at bit rates up to 115200 bps.
Multidrop
Passthru
Connections
Listen Mode
TCP/IP
Modem
Link Redundancy
Hot Standby
2.2
Communication Features
Interoperability
This section, in conjunction with chapter 3, the DNP 3.0 Basic 4 Document Set, and the DNP
Subset Definitions Document, provides complete information on how to communicate with the
DNP3 master component via the DNP3 protocol.
The implementation of the DNP3 master is fully compliant with DNP V3.00 Subset Definition Level
2, contains many Subset Level 3 features, and contains some functionality even beyond Subset
Level 3.
2.2.1
Together, these three components make up a complete interoperability and configuration guide
for the DNP3 master protocol component.
DNP V3.00
DEVICE PROFILE DOCUMENT
(See also the Implementation Table, in section 2.2.2)
Vendor Name: Cybectec Inc.
Device Name:
Level 2
Device Function:
Master
Slave
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported (the
complete list is described in the attached table):
For static (non-change-event) object requests, request qualifier codes 00 and 01 (start-stop) are
supported, in addition to request qualifier code 06 (no range or all points).
16-bit and 32-bit Analog Change Events with Time may be requested.
The read function code for Object 50 (Time and Date), variation 1, is supported.
Maximum Data Link Frame Size (bytes):
Transmitted:
292
Transmitted:
2048
Received:
292
Received:
2048
Never (default);
Always;
None
Fixed at ____
Variable
Configurable from 0 to 31
days, in ms (default value
set to 3000 ms)
None
Fixed at ____
Variable
Configurable
Application Confirm
None
Fixed at ____
Variable
Configurable
None
Fixed at ____
Variable
Configurable, from 0 to 31
days, in ms (default value
set to 3000 ms)
Never
Always
Sometimes
Configurable
SELECT/OPERATE
Never
Always
Sometimes
DIRECT OPERATE
Never
Always
Sometimes
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
Device Profile
2.2.2
Implementation Table
The following table identifies the variations, function codes and qualifiers supported by the DNP3
master component in both request and response messages.
Text shaded as Subset Level 3 indicates Subset Level 3 functionality (beyond Subset Level 2),
and text shaded as beyond Subset Level 3 indicates functionality beyond Subset Level 3.
OBJECT
Object
Number
1
Variation
Number
0
10
10
12
20
20
20
20
20
Description
REQUEST
RESPONSE
(Component may send)
(Component will parse)
Function
Qualifier
Function Codes
Qualifier Codes
Codes (dec)
Codes (hex)
(dec)
(hex)
1
(read) 00, 01 (start-stop)
06 (no range, or all)
1
(read) 00, 01 (start-stop) 129 (response)
00, 01 (start-stop)
06 (no range, or all)
17, 28
(index)
27
(index)
1
(read) 00, 01 (start-stop) 129 (response)
00, 01 (start-stop)
06 (no range, or all)
17, 28
(index)
27
(index)
1
(read) 06 (no range, or all)
07, 08 (limited qty)
17, 28
1
(read) 06 (no range, or all) 129 (response)
(index)
07, 08 (limited qty) 130 (unsol. resp)
27
(index)
17, 28
1
(read) 06 (no range, or all) 129 (response)
(index)
07, 08 (limited qty) 130 (unsol. resp)
27
(index)
1
(read)
(read)
(read)
3
(select)
4
(operate)
5
(direct op)
6 (dir. op, noack)
1
(read)
7
(freeze)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read)
7
(freeze)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read)
7
(freeze)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read)
7
(freeze)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read)
7
(freeze)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
(response)
(unsol. resp)
(response)
129
(response)
(response)
(index)
17, 28
27
(index)
(index)
00, 01
17, 28
27
(start-stop)
00, 01
17, 28
27
(start-stop)
00, 01
17, 28
27
(start-stop)
00, 01
17, 28
27
(start-stop)
00, 01
17, 28
27
(start-stop)
(index)
(index)
echo of request
00, 01 (start-stop)
06 (no range, or all)
(response)
(response)
(response)
(index)
(index)
(index)
(index)
(index)
(index)
(index)
(index)
OBJECT
Object
Number
20
Variation
Number
5
20
20
20
21
21
21
21
21
10
22
22
22
30
30
Description
REQUEST
(Component may send)
Function
Qualifier
Codes (dec)
Codes (hex)
1
(read) 00, 01 (start-stop)
7
(freeze) 06 (no range, or all)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read) 00, 01 (start-stop)
7
(freeze) 06 (no range, or all)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read) 00, 01 (start-stop)
7
(freeze) 06 (no range, or all)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read) 00, 01 (start-stop)
7
(freeze) 06 (no range, or all)
8 (freeze noack)
9 (freeze clear)
10(frz. cl. noack)
1
(read) 00, 01 (start-stop)
06 (no range, or all)
1
(read) 00, 01 (start-stop)
06 (no range, or all)
1
(read)
(read)
(read)
(read)
(read)
(read)
(read)
(read)
RESPONSE
(Component will parse)
Function Codes
Qualifier Codes
(dec)
(hex)
129 (response)
00, 01 (start-stop)
17, 28
(index)
27
(index)
129
129
129
129
129
130
129
130
129
(response)
(response)
(response)
(response)
(response)
(response)
(response)
(response)
(unsol. resp)
(response)
(unsol. resp)
(response)
30
(read)
(response)
30
(read)
(response)
30
(read)
(response)
30
(read)
00, 01 (start-stop)
06 (no range, or all)
32
(read)
32
(read)
32
(read)
129
129
130
129
130
(response)
(response)
(unsol. resp)
(response)
(unsol. resp)
00, 01
17, 28
27
(start-stop)
00, 01
17, 28
27
(start-stop)
00, 01
17, 28
27
(start-stop)
00, 01
17, 28
27
00, 01
17, 28
27
00, 01
17, 28
27
00, 01
17, 28
27
(start-stop)
17, 28
27
17, 28
27
00, 01
17, 28
27
(index)
(index)
(index)
(index)
(index)
(index)
(index)
(index)
(start-stop)
(index)
(index)
(start-stop)
(index)
(index)
(start-stop)
(index)
(index)
(index)
(index)
(index)
(index)
(start-stop)
(index)
(index)
00, 01 (start-stop)
17, 28
(index)
27
(index)
00, 01 (start-stop)
17, 28
(index)
27
(index)
00, 01 (start-stop)
17, 28
(index)
27
(index)
00, 01 (start-stop)
17, 28
(index)
27
(index)
17, 28
27
17, 28
27
(index)
(index)
(index)
(index)
OBJECT
REQUEST
(Component may send)
Function
Qualifier
Codes (dec)
Codes (hex)
1
(read) 06 (no range, or all)
07, 08 (limited qty)
1
(read) 06 (no range, or all)
07, 08 (limited qty)
1
(read) 06 (no range, or all)
07, 08 (limited qty)
1
(read) 06 (no range, or all)
07, 08 (limited qty)
1
(read) 00, 01 (start-stop)
06 (no range, or all)
1
(read) 00, 01 (start-stop)
06 (no range, or all)
RESPONSE
(Component will parse)
Function Codes
Qualifier Codes
(dec)
(hex)
129 (response)
17, 28
(index)
130 (unsol. resp)
27
(index)
129 (response)
17, 28
(index)
130 (unsol. resp)
27
(index)
129 (response)
17, 28
(index)
130 (unsol. resp)
27
(index)
129 (response)
17, 28
(index)
130 (unsol. resp)
27
(index)
Object
Number
32
Variation
Number
3
32
32
32
40
40
40
(read)
40
(read)
00, 01(start-stop)
06 (no range, or all)
129
(response)
41
17, 28
129
(response)
41
41
50
3
(select)
4
(operate)
5
(direct op)
6 (dir. op, noack)
3
(select)
4
(operate)
5
(direct op)
6 (dir. op, noack)
3
(select)
4
(operate)
5
(direct op)
6 (dir. op, noack)
1
(read)
(response)
50
1
2
(response)
(response)
07
Description
17, 28
(index)
(index)
129
129
(response)
(response)
00, 01 (start-stop)
17, 28
(index)
27
(index)
00, 01 (start-stop)
17, 28
(index)
27
(index)
00, 01 (start-stop)
17, 28
(index)
27
(index)
echo of request
echo of request
(response)
echo of request
(response)
00, 01 (start-stop)
07 (limited qty=1)
17, 28
(index)
27
(index)
00, 01 (start-stop)
07 (limited qty=1)
17, 28
(index )
27
(index)
51
51
129
(response)
07
52
129
(response)
07
52
129
(response)
07
60
129
(response)
1b
60
60
60
60
70
80
1
2
1
1
Class 0 Data
Class 1 Data
Class 2 Data
Class 3 Data
File Identifier
Internal Indications
No Object (function code only).
No Object (function code only).
(read)
(write)
17, 28
(index)
129
1
20
21
1
1
20
21
1
20
21
1
20
21
2
2
(read)
(limited qty)
(qty = 1)
(limited qty)
(qty = 1)
(limited qty)
(qty = 1)
(limited qty)
(qty = 1)
(enbl. unsol.)
(dsbl. unsol.)
(read)
(read)
(enbl. unsol.)
(dsbl. unsol.)
(read)
(enbl. unsol.)
(dsbl. unsol.)
(read)
(enbl. unsol.)
(dsbl. unsol.)
(write)
(write)
1b
00
(free-format)
(free-format)
(start-stop)
(index must =7)
13 (cold restart)
14(warm restart)
OBJECT
Object
Number
Variation
Description
Number
No Object (function code only).
REQUEST
(Component may send)
Function
Qualifier
Codes (dec)
Codes (hex)
23 (delay meas.)
Table 2-3
RESPONSE
(Component will parse)
Function Codes
Qualifier Codes
(dec)
(hex)
Implementation Table
2.3
2.4
Device Control
Analog and binary output points may be configured to allow device control. The DNP Select (FC
3), Operate (FC 4) and Direct Operate (FC 5) application layer requests are used to send control
requests to devices. Usage of Select/Operate and/or Direct Operate control requests is on a
point-by-point basis, and is dictated by the Select Required setting (see sections 3.7 and 3.8).
When an Operate or a Direct Operate request is successfully confirmed by the remote device, the
DNP3 master component sends an operate feedback poll request, to obtain the state of all points
that may potentially have changed during the output control operation. The operate feedback
poll request is actually a Read request for data class 1/2/3.
2.4.1
Object 41 Variation
32-Bit Value
16-Bit Value
Float Value
2.4.2
Function
Not supported
Latch ON/OFF
Trip/Close
Pulse
10
Control Type
Function
OPEN/CLOSE requests are not supported.
Pulse, Open
Pulse, Close
2.4.2.1
11
3.
Configuration Settings
This chapter enumerates the configuration settings to be specified for each DNP3 master protocol
instance. Cybectecs SMP Config software is generally used to define these settings.
Only the settings specific to the DNP3 protocol are described here. The settings common to all
master protocol components are described in the Cybectec document entitled Master Protocol
Common Concepts.
3.1
General Settings
Every instance of a master protocol component contains general settings, which set the general
behavior of the component. The following table shows the general settings that are specific to
the DNP3 master protocol.
Setting
Description
Link Address
The DNP data link address of this DNP3 master protocol instance.
This address must be unique for each instance that uses a particular
multidrop link.
Range:
0 to 65,534
Default value:
The DNP data link address of the remote device with which this
DNP3 master instance is communicating.
Range:
0 to 65,535
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 0, Class 1, Class 2 and Class 3 data (static
I/O point value and change event).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
3,600,000 ms (1 hr)
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 0 data (static I/O point value).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 1 data (report by exception/change event).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 2 data (report by exception/change event).
If you set this value to 0, the request will not be sent cyclically.
12
Setting
Description
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 3 data (report by exception/change event).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 1, Class 2 and Class 3 data (report by
exception/change event).
If you set this value to 0, the request will not be sent cyclically.
Clock Sync
Range:
0 to 2,147,483,647 ms
Default value:
5,000 ms
Cyclically, based on the value of the Clock Sync Cycle setting (if
not 0).
Range:
checkmark / no checkmark
Default value:
checkmark
Time interval, in milliseconds, after which the DNP3 master will send
a clock synchronization request to the slave device, if allowed (see
Clock Sync).
If you set this value to 0, the request will not be sent cyclically.
Unsolicited Report
Link Sync
Range:
0 to 2,147,483,647 ms
Default value:
30 secs
checkmark / no checkmark
Default value:
no checkmark
checkmark / no checkmark
Default value:
no checkmark
13
Setting
Description
Link Confirmation
Mode
Never
No confirmation for any frame.
Sometimes
Confirmation requested for multi-frame
fragments only.
Always
Confirmation requested for all frames.
Default value:
Link Confirmation
Timeout
Never
Applic Response
Timeout
Range:
0 to 2,147,483,647 ms
Default value:
3,000 ms
0 to 255
Default value:
0 to 255
Default value:
Tx During SBO
checkmark / no checkmark
Default value:
no checkmark
Table 3-1
14
100 to 300,000 ms
3,000 ms
General Settings
3.2
Redundancy Settings
Each instance of this master protocol component contains redundancy settings, which set the
general behavior of the redundancy component. The following table shows the redundancy
settings that are specific to the DNP3 protocol component.
Setting
Description
Link Address
Range:
0 to 300,000 ms
Default value:
3,000 ms
0 to 300,000 ms
Default value:
3,000 ms
The DNP data link address of this DNP3 master protocol instance.
This address must be unique for each instance that uses a particular
multidrop link.
Range:
0 to 65,534
Default value:
The DNP data link address of the remote device with which this
DNP3 master instance is communicating.
Range:
0 to 65,535
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 0, Class 1, Class 2 and Class 3 data (static
I/O point value and change event).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
3,600,000 ms (1 hr)
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 0 data (static I/O point value).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 1 data (report by exception/change event).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
15
Setting
Description
a read request for Class 2 data (report by exception/change event).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 3 data (report by exception/change event).
If you set this value to 0, the request will not be sent cyclically.
Range:
0 to 2,147,483,647 ms
Default value:
Time interval, in milliseconds, after which the DNP3 master will send
a read request for Class 1, Class 2 and Class 3 data (report by
exception/change event).
If you set this value to 0, the request will not be sent cyclically.
Clock Sync
Range:
0 to 2,147,483,647 ms
Default value:
5,000 ms
Cyclically, based on the value of the Clock Sync Cycle setting (if
not 0).
Range:
checkmark / no checkmark
Default value:
checkmark
Time interval, in milliseconds, after which the DNP3 master will send
a clock synchronization request to the slave device, if allowed (see
Clock Sync).
If you set this value to 0, the request will not be sent cyclically.
Unsolicited Report
Link Sync
16
Range:
0 to 2,147,483,647 ms
Default value:
30 secs
checkmark / no checkmark
Default value:
no checkmark
Setting
Link Confirmation
Mode
Description
Range:
checkmark / no checkmark
Default value:
no checkmark
Never
No confirmation for any frame.
Sometimes
Confirmation requested for multi-frame
fragments only.
Always
Confirmation requested for all frames.
Default value:
Link Confirmation
Timeout
Never
Applic Response
Timeout
Range:
0 to 2,147,483,647 ms
Default value:
3,000 ms
0 to 255
Default value:
0 to 255
Default value:
100 to 300,000 ms
3,000 ms
Redundancy Settings
17
3.3
Description
Index
0 to 65,535
Default value:
Table 3-3
3.4
Description
Type
Normal
Usual binary input point type.
Time sync status
Binary input point used to qualify the
timestamp of reported transitions.
When set to 0, the reported timestamps
have a synchronized status.
When set to 1, the reported timestamps
have a non-synchronized status.
Default value:
Index
0 to 65,535
Default value:
Table 3-4
3.5
Normal
Description
Index
0 to 65,535
Default value:
Table 3-5
18
3.6
Description
Index
0 to 65,535
Default value:
Table 3-6
3.7
Description
Index
Select Required
Output Control
Range:
0 to 65,535
Default value:
checkmark / no checkmark
Default value:
checkmark
The data type used for the output control object that is sent to the
slave device when a control output operation occurs.
Range:
16-bit value
32-bit value
Floating-point value
Default value:
32-bit value
Table 3-7
3.8
Description
Index
19
Setting
Select Required
Control Type
Description
Range:
0 to 65,535
Default value:
checkmark / no checkmark
Default value:
checkmark
Pulse, Open and Pulse, Close support pulse operations, and allow
Open/Close Pair
Range:
Not Supported
Latch ON/OFF
Trip/Close
Pulse
Pulse, Open
Pulse, Close
Force Pulse
Default value:
Not Supported
0
1 to 65,535
Default value:
Table 3-8
20
not assigned
pair number
3.9
3.9.1
Defines the general settings for each instance of the DNP3 master protocol.
Type:
Setting
Description
Line Identifier
Must be MDGP.
Master Name
Device Prefix
Listen Mode
Link Address
Scan Priority
Control Enabled
Clock Sync
Unsolicited Report
Link Confirmation
Mode
Link Confirmation
Allowed values:
0:
1:
2:
Never
Sometimes
Always
21
Setting
Description
Timeout
Link Max Retries
Applic Response
Timeout
Selection Timeout
Tx During SBO
Delay Between Tx
Link Sync
Hot-Standby
Support
checkmark / no checkmark
Default value:
no checkmark
Table 3-9
3.9.2
22
Defines the redundancy settings for each instance of the DNP3 master
protocol.
Type:
Setting
Description
Line Identifier
Must be MDRD.
Master Name
Enabled
Link 1 Preferred
Setting
Description
Link Address
Scan Priority
Clock Sync
Unsolicited Report
Link Confirmation
Mode
Link Confirmation
Timeout
Applic Response
Timeout
Selection Timeout
Delay Between Tx
Link Sync
Allowed values:
Table 3-10
3.9.3
0:
1:
2:
Never
Sometimes
Always
Defines the switched connection settings for each instance of the DNP3
master protocol.
Type:
23
Setting
Description
Line Identifier
Must be MDSW.
Master Name
Enabled
Accept Incoming
Connections
Force Init
Max Retries
Retry Delay
Urgent Connections
Timeout
Inactivity Timeout
Control Inactivity
Timeout
3.9.4
Defines the switched connection schedule settings for each instance of the
DNP3 master protocol.
Type:
Setting
Description
Line Identifier
Must be MDSC.
Master Name
Start Time
Stop Time
Comm Cycle
24
3.9.5
Type:
One line of data per analog input point, up to a maximum of 65,535 lines per
instance of the DNP3 protocol.
Setting
Description
Line Identifier
Must be MDAI.
Master Name
Name
Description
Type
Index
Scale
Offset
SMP Deadband
Units
Disabled
Persistent
Monitor Activity
Comm Deadband
3.9.6
Type:
One line of data per binary input point, up to a maximum of 65,535 lines per
instance of the DNP3 protocol.
Setting
Description
Line Identifier
Must be MDBI.
Master Name
25
Setting
Description
Description
Type
DNP3 BI Type
26
Index
Inverted Polarity
Disabled
Persistent
Monitor Activity
3.9.7
0:
1:
2:
Type:
One line of data per counter input point, up to a maximum of 65,535 lines
per instance of the DNP3 protocol.
Setting
Description
Line Identifier
Must be MDCI.
Master Name
Name
Description
Index
Scale
Offset
Setting
Description
Concepts document.
SMP Deadband
Units
Disabled
Persistent
Monitor Activity
Comm Deadband
3.9.8
Type:
One line of data per frozen counter input point, up to a maximum of 65,535
lines per instance of the DNP3 protocol.
Setting
Description
Line Identifier
Must be MDFCI.
Master Name
Name
Description
Index
Scale
Offset
SMP Deadband
Units
Disabled
Persistent
27
Setting
Description
Monitor Activity
Comm Deadband
28
3.9.9
Type:
One line of data per analog output point, up to a maximum of 65,535 lines
per instance of the DNP3 protocol.
Setting
Description
Line Identifier
Must be MDAO.
Master Name
Name
Description
Type
Always 0.
Index
Scale
Offset
SMP Deadband
Units
Select Required
Output Control
0:
1:
2:
16-bit value
32-bit value
Floating-point value
Disabled
Monitor Activity
Comm Deadband
29
3.9.10
Type:
One line of data per binary output point, up to a maximum of 65,535 lines
per instance of the DNP3 protocol.
Setting
Description
Line Identifier
Must be MDBO.
Master Name
Name
Description
Type
Index
Select Required
Master Duration
Allowed
Activation Time
Control Type
Not Supported
Latch ON/OFF
Trip/Close
Pulse
Pulse, Open
Pulse, Close
Force Pulse
Open/Close Pair
Disabled
Monitor Activity
30
0:
1:
2:
3:
4:
5
6:
4.
Implementation Details
4.1
Startup Sequence
The protocol component goes through the following steps on startup:
Creates all I/O points and marks them as invalid (communications failure).
4.2
Scan Process
The protocol component manages the device polling cycle using the following principles:
The remote device may send an unsolicited response at any time if this feature is supported
and the device is configured to do so.
DNP3 response processing complies with the DNP technical specifications. Since this topic goes
beyond the scope of this document, it will not be described here. Refer to the DNP
documentation for additional information on the topic.
The DNP3 response processing rules are as follows:
In addition to the DNP rules, an application layer response is valid only if it arrives within the
configured application response timeout delay.
All objects and their variations are supported (see section 2.2.2 "Implementation Table" for
the complete listing of all supported objects and variations).
The same request is re-issued if the reception status is incorrect, up to the number of
configured retry counts. For output control requests, only Select requests may be re-issued.
Whatever the reason, the link is reset from scratch if too many consecutive bad receptions
are received, too many being the number of configured retry counts.
The communications link is being reset due to too many consecutive errors of any type.
The communications link is being reset due to a control request on a logical binary output
point.
31
Once the link has been initialized, and as long as it remains active, a regular scanning
process is used on a continuous basis. Note that the link is not considered active until a valid
response to a data class 1/2/3/0 read request is received from the device.
4.2.1
If the last sent request failed and must be retried, send it again.
If the previous application layer response contains IINs that require a special operation,
perform the operation (see section 4.2.1).
If an event requiring a special operation occurs, perform the operation (see section 4.2.2).
If a scheduled operation is ready to be performed, carry out the operation (see section
4.2.3).
The scanning process may be interrupted at any time, if there are output control requests.
If the normal scanning process is abandoned to cause a link reset, all I/O points are tagged
as being defective due to a communications failure. Analog, binary and counter input points
become valid again on an individual basis only when valid I/O data is received from the
device. Analog and binary output points become valid again as soon as the link is considered
active.
Related Operation
N/A
N/A
32
Related Operation
request, depending on the unsolicited response
configuration.
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Table 4-1
All internals indication bits are available as statistics for diagnostic purposes. These statistical
fields are updated each time remote device IINs are reported. See section 5 - Troubleshooting.
4.2.2
Related operation
Reception of an unsolicited
response from the remote
device
Clock synchronization
Response timeout
33
4.2.3
Scheduled operations
Scheduled operations are performed cyclically. The cycle for each operation is set through
configuration. The operations that can be scheduled are described in the following table.
Operation
Description
Integrity poll
Clock synchronization
Scheduled Operations
It is important to note that the normal scanning sequence may be interrupted by output control
operations, depending of the Tx During SBO general setting value. When this parameter is set to
0, the scanning process is momentarily suspended after a successful Select request, until an
associated Operate request is sent, or until the selection timer expires. This feature is required to
interact with special devices that automatically recall any selected point when a request, other
than an appropriate Operate request, follows the Select request.
4.3
Listen Mode
The DNP3 master component can be configured to operate as a spy on a serial link, i.e., in listen
mode. The following restrictions apply:
Communication link failures are detected using the inactivity timeout mechanism of the data
link layer. Thus, if no valid data link layer frames are received during the inactivity timeout
period, the communications link is reset, with all the consequences that this implies.
Cycle of
the fastest
configured
request
(ms)
Application
layer
configured
retry number
Application
layer
configured
timeout (ms)
34
Remember that the basic idea in using a master protocol component in listen mode is to spy on
another link that already controls the acquisition cycle with the RTU. Thus, the instance used in
listen mode should have a configuration that is compatible with the information that is exchanged
on the primary link, so that a request timeout on one side will reflect as an inactivity timeout on
the other side, at approximately the same time.
35
5.
Troubleshooting
The following table enumerates solutions to common problems experienced with the DNP3
master protocol component.
Problem
Solution
All requests in the scanning cycle are disabled (the cycle is set
to 0). At least one request must be enabled (cycle greater than
0) in your general settings.
36
Troubleshooting