Troubleshooting; Identifying Hardware Errors; Identifying Runtime Errors; Identifying Communication Errors - ABB ABILITY SSC600 Operation Manual

1MRS758850
5

Troubleshooting

5.1

Identifying hardware errors

1.
2.
3.
5.2

Identifying runtime errors

1.
2.
3.
5.3

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 IED's internal faults such as component
breakdown, contact ABB for repair or replacement actions.
5.3.1

Internal faults

An indication about the fault is shown in the event list of the WHMI. The text Internal Fault
with an additional text message, a code, date and time, is shown to indicate the fault
type.
Different actions are taken depending on the severity of the fault. The IED tries to
eliminate the fault by restarting. After the fault is found to be permanent, the IED stays in
the internal fault mode. All other output contacts are released and locked for the internal
fault. The IED continues to perform internal tests during the fault situation.
SSC600
Operation Manual
Check the module with an error.
Check the IED supervision events in Main menu > Monitoring > IED status > Self-
supervision for a faulty hardware module.
Inspect the IED visually.
• 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 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.
Check the error origin from the IED's supervision events Main menu > Monitoring >
IED status > Self-supervision.
Reboot the IED and recheck the supervision events to see if the fault has cleared.
In case of persistent faults, contact ABB for corrective actions.
Troubleshooting
53