ABB RELION Series, Руководство по протоколу связи

Страница: 22 / 40

The available DNP3 data objects are taken (mapped) entirely from the native IEC
61850 application data available in the protection relay. Mainly the IEC 61850 data
that resides in IEC 61850 default dataset is included in the DNP3 object mapping.
Objects within IEC 61850 datasets produce time tagged events. IEC 61850 events and
time stamps are propagated into DNP3 class events.
Some IEC 61850 objects, which do not reside in any IEC 61850 dataset, have also
been mapped to DNP3. Since these objects do not create any events upon change, it is
not possible to assign them into any event class (1...3) in DNP3. The Communication
Management tool prevents this kind of assignment. These objects are in the point list
referred to as “Static-only” objects. The controlling station can read them on demand
directly from the object group in question, or they can be assigned to DNP3 Class 0.
The protection relay includes a predefined set of available function blocks, which in
turn includes data objects that are visible for the DNP3 protocol. However, only a part
of these function blocks can be used by the protection relay's application
configuration. The Communication Management tool shows only the DNP3 objects
that are active in the configuration. Not all the available function blocks are included
in the default application configuration.
It is impossible to make the DNP3 point configuration before the protection relay's
application configuration has been created.
• If a function block is removed from the configuration, the DNP3 objects
belonging to this function block are automatically removed from the DNP3 point
list. If points are mapped to a DNP3 object address, a “hole” in the mapping
occurs. In such case, the remaining map can be modified with the Communication
Management tool.
• If a function block is added, the DNP3 points from this function block appear as
unmapped in the Communication Management tool.
3.4.2 Class events
DNP3 objects that are not of “Static-only” type can be assigned by the
Communication Management tool in PCM600 into DNP3 event classes 1...3. Event
buffering is defined per DNP3 object type and not by DNP3 event class.
The DNP3 standard does not define or suggest any specific usage of the different
classes. In polled mode, the controlling station could prioritize the polling of a specific
class. However, this is not used very often, since the chronology of events is
considered more important than the prioritization of certain objects.
Different DNP3 object types are often assigned to different DNP3 event classes. This
has no meaning if the client performs class polling simultaneously to all the three
classes. Outstation still responds to the events in chronological order. However, there
are some advantages.
Section 3
1MRS758757 A
Vendor-specific implementation
16 REC615 and RER615
Communication Protocol Manual