Logical Signal Status Report Binstatrep - ABB REC670 Applications Manual

Section 17
Monitoring
17.7
17.7.1
17.7.2
500
The recording time should not be longer than necessary (PostFaultrecT and
TimeLimit).
• Should the function record faults only for the protected object or cover more?
• How long is the longest expected fault clearing time?
• Is it necessary to include reclosure in the recording or should a persistent fault
generate a second recording (PostRetrig)?
Minimize the number of recordings:
• Binary signals: Use only relevant signals to start the recording that is,
protection trip, carrier receive and/or start signals.
• Analog signals: The level triggering should be used with great care, since
unfortunate settings will cause enormously number of recordings. If
nevertheless analog input triggering is used, chose settings by a sufficient
margin from normal operation values. Phase voltages are not recommended for
trigging.
There is a risk of flash wear out if the disturbance report triggers
too often.
Remember that values of parameters set elsewhere are linked to the information on
a report. Such parameters are, for example, station and object identifiers, CT and
VT ratios.

Logical signal status report BINSTATREP

Identification
Function description
Logical signal status report
Application
The Logical signal status report (BINSTATREP) function makes it possible to poll
signals from various other function blocks.
BINSTATREP has 16 inputs and 16 outputs. The output status follows the inputs
and can be read from the local HMI or via SPA communication.
IEC 61850 IEC 60617
identification identification
BINSTATREP
1MRK 511 401-UEN A
GUID-E7A2DB38-DD96-4296-B3D5-EB7FBE77CE07 v2
GUID-E0247779-27A2-4E6C-A6DD-D4C31516CA5C v3
ANSI/IEEE C37.2
device number
- -
GUID-F9D225B1-68F7-4D15-AA89-C9211B450D19 v3
Bay control REC670 2.2 IEC
Application manual