Section 3 Dnp3 Protocol Implementation; Dnp3 Device Profile - ABB Relion 620 Series Manual

1MRS757660 A
Section 3
3.1
Table 177: Device profile document
DNP3 device profile document
Vendor name:
Device name:
Highest DNP level supported:
For requests:
For responses:
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):
Transmitted:
Received:
Maximum data link re-tries:
○ None
○ Fixed
● 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
RET620
Point List Manual
DNP3 protocol implementation

DNP3 device profile

The following table provides a device profile document in the standard format
defined in the DNP3 Subset Definitions Document. In the DNP3 Subset
Definitions Document it is referred to as a document, although 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.
Level 2+
Level 2+
292
292
DNP3 protocol implementation
ABB Oy
RET620
Device function:
○ Master
● Slave
Maximum application fragment size (octets):
Transmitted: Configurable (256...2048)
Received: 2048
Maximum application layer re-tries:
● None
○ Configurable
Section 3
71