Siemens 7SR23 DAD, Manual

Page: 109 / 226

Chapter 4) 7SR23 DAD Data Communications
©2013 Siemens Protection Devices Limited Chapter 4 Page 31 of 54
Section 5: DNP3.0 Definitions
5.1 Device Profile
The following table provides a “Device Profile Document” in the standard format defined in the DNP 3.0 Subset
Definitions Document. While it is referred to in the DNP 3.0 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 provided in Section 5.2 (beginning on page 34), and the Point List Tables provided in Section 5.3
(beginning on page 39), should provide a complete configuration/interoperability guide for communicating with a
device implementing the Triangle MicroWorks, Inc. DNP 3.0 Slave Source Code Library.
DNP V3.0
DEVICE PROFILE DOCUMENT
(Also see the DNP 3.0 Implementation Table in Section 5.2, beginning on page 34.)
Vendor Name:
Siemens Protection Devices Ltd.
Device Name: 7SR23 DAD, using the Triangle MicroWorks, Inc. DNP3 Slave Source Code Library,
Version 3.
Highest DNP Level Supported:
For Requests: Level 3
For Responses: Level 3
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 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.
Output Event Object 11 is supported.
Maximum Data Link Frame Size (octets):
Transmitted: 256
Received 256
Maximum Application Fragment Size (octets):
Transmitted: 2048
Received 2048
Maximum Data Link Re-tries:
None
Fixed (3)
Configurable from 0 to 65535
Maximum Application Layer Re-tries:
None
Configurable
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)
Sometimes
Configurable as: “Only when reporting event data”, or “When reporting event data or multi-
fragment messages.”