6.2.1
Disturbance recording triggering
GUID-5569488B-F930-4762-99CE-2863BEFB1947 v8
Disturbance recordings are normally triggered by IED applications when they detect fault
events. Disturbance recordings can also be triggered manually or periodically. The manual
trigger generates an instant disturbance report. Use this function to get a snapshot of the
monitored signals.
6.2.2
Disturbance record analysis
GUID-52E4493E-5F8F-44F8-94DE-23A2EBD36AC1 v5
The IED collects disturbance records of fault events which are set to trigger the disturbance
recorder. Disturbance data is collected and stored for later viewing and analysis. The
disturbance recorder data can be read and analyzed with PCM600.
For more information, see PCM600 documentation.
6.2.3
Disturbance reports
GUID-4191AAA0-EA7E-4C74-9B8E-EC44FC390919 v3
PCM600 can be used for creating reports of disturbance recorder data.
For more information, see PCM600 documentation.
6.2.4
IED self-supervision
GUID-FFF9F2C4-B04B-40BD-A636-8D430DBA69CF v10
The IED self-supervision handles internal run-time fault situations. The main indication of an
internal fault is a flashing green Ready LED.
Internal faults can be divided to hardware errors, run-time errors in the application or
operating system and communication errors. Further actions always depend on the cause of
the error.
Only authorized and skilled personnel should analyze the errors and decide on
further actions.
The IED records IED status data and events.
Document all the recorded data from the IED before resetting the tripping and
IED lockout functions.
6.2.5
Non-operative functions
GUID-752CDABC-4F21-4A02-AF77-F8AD0165F1DD v2
Protection and control functions can be non-operative if:
•
function is not turned on, that is,
Operation = Off.
•
function is connected to bad or lost input data from MU.
•
function is set to a non-operative state by IEC 61850.
Section 6
1MRK 500 127-UEN D
IED operation
48
670 series
Operation manual
