Section 3
DNP3 protocol implementation
3.1
DNP3 device profile
The following table provides a device profile document in the standard format
defined in the DNP3 Subset Definitions Document. While it is referred to in the
DNP3 Subset Definitions as a document, it is in fact a table, and only a component
of a total interoperability guide. The table, in combination with the Implementation
table and the point list tables provides a complete configuration/interoperability
guide for communicating with a device.
Table 5:
Device profile document
DNP3 device profile document
Vendor name:
ABB Oy
Device name:
RED615
Highest DNP level supported:
Device function:
For requests:
Level 2+
○
Master
For responses:
Level 2+
●
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 07 and 08 (limited quantity), and 17 and 28 (index) are supported.
Static object requests sent with qualifiers 07, or 08, will be responded with qualifiers 00 or 01.
16-bit and 32-bit Analog Change Events with Time may be requested.
Maximum data link frame size (octets):
Maximum application fragment size (octets):
Transmitted:
292
Transmitted:
Configurable (256...2048)
Received:
292
Received:
2048
Maximum data link re-tries:
Maximum application layer re-tries:
○
None
●
None
○
Fixed
○
Configurable
●
Configurable (0...65535)
Requires data link layer confirmation:
○
Never
○
Always
○
Sometimes
●
Configurable as: "Never", "Only for multi-frame messages", or "Always"
Requires application layer confirmation:
○
Never
○
Always
○
When reporting event data (slave devices only)
○
When sending multi-fragment responses (slave devices only)
Table continues on next page
1MRS756879 A
Section 3
DNP3 protocol implementation
RED615
19
Point List Manual
