DNP Profile - RTU To Master Rev1
DNP Profile - RTU To Master Rev1
SCOUT
DNP PROFILE DOCUMENT
__________________________________________
Revision/Update Information
www.survalent.com
Information furnished by Survalent Technology Corporation has been checked carefully and is believed to be accurate and reliable.
However, Survalent Technology Corporation does not assume any responsibility for inaccuracies. Survalent Technology Corporation
reserves the right to make changes without notice to improve reliability, function or design.
Table of Contents
1 DNP Slave Implementation........................................................................2
1.1 General parameters.........................................................................................2
1.2 Implementation Table.......................................................................................5
1.2.1 Binary Input (status and alarms) Objects........................................................6
1.2.2 Binary Output (control) Objects......................................................................6
1.2.1 Counter Input Objects....................................................................................7
1.2.2 Analog Input Objects.....................................................................................9
1.2.3 Analog Output Objects.................................................................................11
1.2.4 Time Objects...............................................................................................11
1.2.5 Class Objects..............................................................................................12
1.2.6 Miscellaneous Objects.................................................................................12
1.3 Notes...............................................................................................................13
1.3.1 Change with Time.......................................................................................13
1.3.2 Binary Events with Time..............................................................................13
1.3.3 Quality Flags...............................................................................................13
1.3.4 Class Data..................................................................................................13
1.3.5 File Transfer................................................................................................13
1.3.6 Configuration...............................................................................................13
1.3.7 Retries and Timeouts...................................................................................14
1.3.8 Unsolicited Reporting..................................................................................14
1.3.9 Source and Destination Addresses..............................................................14
i
1 DNP Slave Implementation
This section describes the DNP implementation on the Scout as a slave. The tables are
configured as recommended by the DNP User’s Group. Any notes can be found in the
section after the tables.
DNP V3.00
DEVICE PROFILE DOCUMENT
Refer to Implementation Table
For Responses 2
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):
Received 292
Received _2048__
-2-
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
None None
Fixed at _______________________ Configurable, range __0_ to ____255___
Configurable, range ____ to _______
Applies to unsolicited mode only
Never
Always
Sometimes If 'Sometimes', when?
______________________________________________
Never
Always (not recommended)
When reporting Event Data (Slave devices only)
When sending multi-fragment responses (Slave devices only)
Others
__________________________________________________________________________
Attach explanation if 'Variable' or 'Configurable' was checked for any timeout. See Notes
-3-
Sends/Executes Control Operations:
Reports Binary Input Change Events when no Reports time-tagged Binary Input Change Events
specific variation requested: when no specific variation requested:
Never Never
Only time-tagged Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
Configurable to send both, one or the Configurable (attach explanation)
other (see Notes)
Never Never
Configurable (see Notes) When Device Restarts
Only certain objects When Status Flags Change
Sometimes (attach explanation)
No other options are permitted.
ENABLE/DISABLE UNSOLICITED
Function codes supported
-4-
1.2 Implementation Table
This table contains information on how data is handled for a specific application. Some data has
been deleted from the full level 2 implementation for clarity. It is recommended that the master
(host) implements the full level 2 for future changes to this application. Bold lettering indicates
most common messages
*** a indicates variation returned for an “any variation” (var 0) request with DI/AI flag parameter
set to “without flag” or “dynamic” if all flags are normal
*** b indicates variation returned for an “any variation” (var 0) request with DI/AI flag parameter
set to “with flag” or “dynamic” if any flag is abnormal
*** c indicates variation returned for an “any variation” (var 0) request if time has not been set
in Scout (time invalid)
*** d indicates variation returned for an “any variation” (var 0) request if time has been set in
Scout (time valid)
*** e indicates variation returned for an “any variation” (var 0) when the analog data base point
is declared a 16 bit value
*** f indicates variation returned for an “any variation” (var 0) when the analog data base point
is declared a 32 bit value
-5-
1.2.1 Binary Input (status and alarms) Objects
2 2 Binary Input Change with Abs. Time *** d 1 06,07,08 129,130 17,28
12 3 Pattern Mask
-6-
1.2.1 Counter Input Objects
-7-
Counter Input Objects continued
-8-
1.2.2 Analog Input Objects
30 1 32-Bit Analog Input with Flag *** b,f 1 06,00,01 129 00, 01
30 2 16-Bit Analog Input with Flag *** b,e 1 06,00,01 129 00, 01
30 3 32-Bit Analog Input without Flag *** a,f 1 06,00,01 129 00, 01
30 4 16-Bit Analog Input without Flag *** a,e 1 06,00,01 129 00, 01
-9-
Analog Input Objects continued
Reply has
34 1 16-Bit Analog Input Deadband Set 2 17,28 129 no object
Reply has
34 2 32-Bit Analog Input Deadband Set 2 17,28 129 no object
- 10 -
1.2.3 Analog Output Objects
129 07
50 1 Time and Date ***
- 11 -
1.2.5 Class Objects
60 0
20,
Reply has
60 2 Class 1 Enable/Disable Unsol., Assign Obj, 21, 06 129 no object
22
20,
Reply has
60 3 Class 2 Enable/Disable Unsol., Assign Obj, 21, 06 129 no object
22
20,
Reply has
60 4 Class 3 Enable/Disable Unsol., Assign Obj, 21, 06 129 no object
22
- 12 -
1.3 Notes
The Scout will support DNP Level 2 as a slave with the following comments and exceptions.
Based on DNP-L2 described in DNP v3.00 Subset Definitions (document number P009-0IG.SUB,
version 1.00), chapter 2.
1.3.6 Configuration
Configurations mentioned in this document can be performed via the Maintenance console or the
Web Server connected to the RTU.
- 13 -
1.3.7 Retries and Timeouts
Retries of transmissions are only supported when in unsolicited reporting mode. Retries are
carried out when application confirms are not received within the configurable timeout (Default 4
seconds). The primary number of retries and time between can be configured (Default: 5 times
and 10 seconds). After all primary retries, secondary retries will occur (Default: 5 minutes)
indefinitely or until confirmation is received.
Application confirm must also be received within the Application Timeout period for it to be acted
on even in polling mode.
- 14 -