Accessing Non-Protocol Mapped Data - ABB Relion 615 Series Protocol Manual

1MRS756709 D
3.3.3
615 series
Communication Protocol Manual

Accessing non-protocol mapped data

Since the 615 series version 4.0.0, the IED application includes a number of
general purpose I/O data. By default, these data are mapped to this protocol. See
the point list manual for the exact mappings.
The general purpose objects can be connected to any internal object in the IED
configuration application by ACT or SMT tool. This gives additional opportunities
for the protocols.
Example 1
Due to security reasons, protocols do not contain mappings for the direct control of
physical outputs. In this manner the master cannot accidentally write a change to a
physical output.
It is possible to connect general-purpose outputs to physical outputs using the ACT
tool. The general purpose output can, of course, be controlled also from the protocol.
Example 2
The legacy protocol default mappings are a selection of the most important signals
produced by the IEC 61850 based IED applications. The manufacturer's selection
of important signals may not always serve every customer.
Via the ACT tool the user can freely connect any non-protocol mapped internal
signal to a general purpose input object. This object can then be accessed by the
legacy protocol as regular protocol application data.
Example 3
The basic IEC 61850 application model of the IED produces a great amount of
information. In some cases, this is more than what is feasible to transport through a
legacy protocol. Via the PCM/CMT tools unnecessary data objects can be excluded
from the legacy protocol.
However, in some cases a better solution is to OR together several internal signals
into one general signal. This OR output can be connected to a general purpose
input and accessed by the legacy protocol as regular protocol application data.
Vendor-specific implementation
Section 3
17