Section 7 Troubleshooting; Fault Tracing; Identifying Hardware Errors; Identifying Runtime Errors - ABB REX610 Operation Manual

Hide thumbs Also See for REX610:
Table of Contents

Advertisement

2NGA000823 A
Section 7
7.1
7.1.1
7.1.2
7.1.3
7.1.3.1
REX610
Operation Manual
Troubleshooting

Fault tracing

Identifying hardware errors

1.
Check the module with an error.
Check the relay supervision events in Main menu/Monitoring/IED status/
Self-supervision for a faulty hardware module.
2.
Inspect the protection relay visually.
Inspect the protection relay visually to find any 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 protection relay and test the input and
output operation with an external test device.
If the problem remains, contact ABB for repair or replacement actions.

Identifying runtime errors

1.
Check the error origin from the protection relay's supervision events Main
menu/Monitoring/IED status/Self-supervision.
2.
Reboot the protection relay and recheck the supervision events to see if the
fault has cleared.
3.
In case of persistent faults, contact ABB for corrective actions.

Identifying communication errors

Communication errors are normally communication interruptions or
synchronization message errors due to communication link breakdown.
In case of persistent faults originating from protection relay's internal faults
such as component breakdown, contact ABB for repair or replacement actions.

Checking front communication link operation

To verify front communication, check that both LEDs above the RJ-45
communication port are lit.
Section 7
Troubleshooting
57

Advertisement

Table of Contents
loading

Table of Contents