3.4.15
Accessing of non-protocol-mapped data
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 using the Application Configuration or Signal Matrix 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. This way, the client cannot accidentally write a change to a physical
output.
It is possible to connect general-purpose outputs to physical outputs using the
Application Configuration tool. The general-purpose output can also be controlled
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.
Any non-protocol-mapped internal signal can be freely connected to a general-
purpose input object via the Application Configuration tool. 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 PCM600/Communication Management 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.
General-purpose input object and OR function block may cause
delays to time stamps.
Section 3
1MRS757645 B
Vendor-specific implementation
64
620 series
Communication Protocol Manual
