Dnp3 Device Profile - GE P24DM Technical Manual

Motor protection ied
Table of Contents

Advertisement

Chapter 16 - Communications
If the clock is being synchronized using the IRIG-B input then it will not be possible to set the device time using the
Courier interface. An attempt to set the time using the interface will cause the device to create an event with the
current date and time taken from the IRIG-B synchronized internal clock.
6.3.8

DNP3 DEVICE PROFILE

This section describes the specific implementation of DNP version 3.0 within General Electric MiCOM P40 Agile IEDs
for both compact and modular ranges.
The devices use the DNP 3.0 Slave Source Code Library version 3 from Triangle MicroWorks Inc.
This document, in conjunction with the DNP 3.0 Basic 4 Document Set, and the DNP Subset Definitions Document,
provides complete information on how to communicate with the devices using the DNP 3.0 protocol.
This implementation of DNP 3.0 is fully compliant with DNP 3.0 Subset Definition Level 2. It also contains many
Subset Level 3 and above features.
6.3.8.1
DNP3 DEVICE PROFILE TABLE
The following table provides the device profile in a similar format to that 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 just one component of a
total interoperability guide. This table, in combination with the subsequent Implementation and Points List tables
should provide a complete interoperability/configuration guide for the device.
The following table provides the device profile in a similar format to that 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 just one component of a
total interoperability guide. This table, in combination with the subsequent Implementation and Points List tables
should provide a complete interoperability/configuration guide for the device.
Vendor Name:
Device Name:
Models Covered:
Highest DNP Level Supported*:
*This is the highest DNP level FULLY supported. Parts of level 3 are
also supported
Device Function:
Notable objects, functions, and/or qualifiers supported in addition to the highest DNP levels supported (the complete list is described in the
DNP 3.0 Implementation Table):
For static (non-change event) object requests, request qualifier codes 00 and 01 (start-stop), 07 and 08 (limited quantity), and 17 and 28 (index)
are supported in addition to the request qualifier code 06 (no range (all points))
Static object requests sent with qualifiers 00, 01, 06, 07, or 08 will be responded with qualifiers 00 or 01
Static object requests sent with qualifiers 17 or 28 will be responded with qualifiers 17 or 28
For change-event object requests, qualifiers 17 or 28 are always responded
16-bit and 32-bit analogue change events with time may be requested
The read function code for Object 50 (time and date) variation 1 is supported
Analogue Input Deadbands, Object 34, variations 1 through 3, are supported
Floating Point Analogue Output Status and Output Block Objects 40 and 41 are supported
Sequential file transfer, Object 70, variations 2 through 7, are supported
Device Attribute Object 0 is supported
Maximum Data Link Frame Size (octets):
Maximum Application Fragment Size (octets)
328
DNP 3.0
Device Profile Document
General Electric
MiCOM P40Agile Protection Relays – compact and modular range
All models
For Requests: Level 2
For Responses: Level 2
Slave
Transmitted: 292
Received: 292
Transmitted: Configurable (100 to 2048). Default 2048
Received: 249
P24xM
P24xM-TM-EN-2.1

Advertisement

Table of Contents
loading

This manual is also suitable for:

Micom p40 agileP24nm

Table of Contents