Troubleshooting; Fault Tracing; Identifying Hardware Errors; Identifying Runtime Errors - ABB Relion 670 series Operation Manual
Hide thumbs
Also See for Relion 670 series:
- Technical manual (1432 pages) ,
- Technical reference manual (1232 pages) ,
- Applications manual (944 pages)
Table of Contents
Advertisement
1MRK 500 127-UEN D
Section 9
9.1
Fault tracing
9.1.1
Identifying hardware errors
1.
Check the module with an error.
•
•
2.
Inspect the IED visually.
•
•
3.
Check whether the error is external or internal.
•
•
•
9.1.2
Identifying runtime errors
1.
Check the error origin from IED's internal event list Main menu/Diagnostics/IED status/
General.
2.
Reboot the IED and recheck the supervision events to see if the fault has cleared.
3.
In case of persistent faults, contact ABB for corrective actions.
9.1.3
Identifying blocked functions
1.
Check the list of blocked functions from the LHMI under Main menu/Diagnostics/IED
status/Function overview.
2.
Check the settings for the 9-2LE receiver and associated cabling.
3.
In case of persistent faults, contact ABB for corrective actions.
9.1.4
Identifying communication errors
Communication errors are normally communication interruptions or synchronization message
errors due to communication link breakdown.
•
Check the IEC61850 and DNP3 communication status in internal event list in Main menu/
Diagnostics/IED Status/General.
•
In case of persistent faults originating from IED's internal faults such as component
breakdown, contact ABB for repair or replacement actions.
670 series
Operation manual
Troubleshooting
Check the general IED status in Main menu/Diagnostics/IED status/General for a
faulty hardware module.
Check the history of changes in internal event list in Main menu/Diagnostics/
Internal events.
Inspect the IED visually to find any physical error causes.
If you can find some obvious physical damage, contact ABB for repair or
replacement actions.
Check that the error is not caused by external origins.
Remove the wiring from the IED and test the input and output operation with an
external test device.
If the problem remains, contact ABB for repair or replacement actions.
Section 9
Troubleshooting
GUID-0F0FF99B-E3EF-4D44-ABB4-19041BA9FBF1 v7
GUID-105A9FFE-75F3-4E65-BFF7-F31268CD7DCE v7
GUID-012B4B88-F260-4B20-885F-998AD384D586 v2
GUID-4C589FC4-B122-4F12-8E3D-1B05B4FC5FCE v8
77
Advertisement
Table of Contents
