ABB RED615 ANSI, Руководство по эксплуатации

Страница: 85 / 116

Section 7 Troubleshooting
7.1 Fault tracing
7.1.1 Identifying hardware errors
Most hardware errors are caused by external events which physically damage the
IED's hardware. Probable causes are, for example, overvoltage, spikes and short
circuits which damage one or several of the IED's physical inputs or outputs. Human
errors can also cause damage during installation or operation. As a consequence, one
or several physical cards, inputs or outputs may stop operating due to the damage.
1. Check the module with an error.
Check the IED supervision events in
Main Menu/Monitoring/IED status/Self-
supervision for a faulty hardware module.
2. Inspect the IED visually
•
Inspect the IED visually to find the physical error causes.
• If you can find some obvious physical damage, contact ABB for repair or
replacement actions.
3. Check whether the error is external or internal.
•
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.
7.1.2 Identifying runtime errors
Runtime errors may be caused by component failures or software problems. Some
errors are cleared automatically but sometimes, for example in case of a component
failure, proper corrective actions are needed.
1. Check the error origin from the IED's supervision events Main Menu/
Monitoring/IED status/Self-supervision .
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.
1MRS756499 A
Section 7
Troubleshooting
RED615 77
Operation Manual