Setting Guidelines - ABB REL670 2.2 IEC Applications Manual

1MRK 506 369-UEN B
18.6.3
Line distance protection REL670 2.2 IEC
Application manual
Every disturbance report recording is saved in the IED. The same applies to all
events, which are continuously saved in a ring-buffer. Local HMI can be used to
get information about the recordings, and the disturbance report files may be
uploaded in the PCM600 using the Disturbance handling tool, for report reading or
further analysis (using WaveWin, that can be found on the PCM600 installation
CD). The user can also upload disturbance report files using FTP or MMS (over
61850–8–1) clients.
If the IED is connected to a station bus (IEC 61850-8-1), the disturbance recorder
(record made and fault number) and the fault locator information are available. The
same information is obtainable if IEC 60870-5-103 is used.

Setting guidelines

The setting parameters for the Disturbance report function DRPRDRE are set via
the local HMI or PCM600.
It is possible to handle up to 40 analog and 352 binary signals, either internal
signals or signals coming from external inputs. The binary signals are identical in
all functions that is, Disturbance recorder (DR), Event recorder (ER), Indication
(IND), Trip value recorder (TVR) and Event list (EL) function.
User-defined names of binary and analog input signals are set using PCM600. The
analog and binary signals appear with their user-defined names. The name is used
in all related functions (Disturbance recorder (DR), Event recorder (ER), Indication
(IND), Trip value recorder (TVR) and Event list (EL)).
Figure 394 shows the relations between Disturbance report, included functions and
function blocks. Event list (EL), Event recorder (ER) and Indication (IND) uses
information from the binary input function blocks (BxRBDR). Trip value recorder
(TVR) uses analog information from the analog input function blocks (AxRADR),
which is used by Fault locator (FL) after estimation by Trip Value Recorder (TVR).
Disturbance report function acquires information from both AxRADR and
BxRBDR.
Section 18
Monitoring
IP14874-1 v1
M12179-64 v9
785