Interpretation Of The Counter Values; Accessing Of Non-Protocol-Mapped Data - ABB RELION 620 Series Communication Protocol Manual

1MRS757647 C
3.3.6.2
3.3.7
620 series
Communication Protocol Manual
in parallel can be connected to a binary output and wired to other units, a
broadcast freeze can be achieved.

Interpretation of the counter values

The ASDU 205 counters are derived from the corresponding IEC 61850 counter
objects. Due to range differences, the scaling of the IEC 61850 counter objects are not
similar to the expected ASDU 205 scaling. With the default settings the difference is
approximately:
ASDU 205 value = 0.2684 × IEC 61850 counter value
Information about how interpret the IEC 61850 counter values in turn are found
elsewhere in the IED documentation.
The scale factor is the quotient between the maximum range values of the different
counter types.
ASDU 205 counter range is 0...268435455 (0...0×0FFFFFF)
IEC 61850 counter range is 0...999999999 (0...0×3B9AC9FF)
For calculation purposes, the IEC 60870-5-103 protocol needs to know the source
counter roll-over value. The roll-over values can be defined through the
Communication Management tool Scale value. Default setting is 1000000000
(999999999+1).

Accessing of non-protocol-mapped data

The protection relay 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 protection
relay 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.
Vendor-specific implementation
Section 3
23