ABB ACS560 Firmware Manual page 428

428 Fault tracing
Fault / Aux. code
Code
code visible only on
(hex)
assistant control panel
and drive composer)
5690 PU communication
internal
5691 Measurement circuit
ADC
5692 PU board powerfail
5693 Measurement circuit
DFF
5695 Reduced run
5697 Charging feedback
5698 Unknown PU fault
50A0 Fan
6181 FPGA version
incompatible
6306 FBA A mapping file
6481 Task overload
6487 Stack overflow
64A3 Application loading
(aux
Cause
Internal communication error.
Measurement circuit fault.
Power unit power supply
failure.
Measurement circuit fault.
Configured power units not
found.
Charging feedback signal
missing.
The power unit logic generated
a fault which is not known by
software.
Cooling fan stuck or
disconnected.
Firmware and FPGA versions
are incompatible.
Fieldbus adapter A mapping
file read error.
Internal fault.
Internal fault.
Application file incompatible or
corrupted.
8006 Not enough memory for the
application.
8007 The application contains the
wrong system library version.
8008 The application is empty.
8009 The application contains
invalid tasks.
What to do
Contact your local ABB representative.
Contact your local ABB representative.
Contact your local ABB representative.
Contact your local ABB representative.
Configure the power units.
Check the feedback signal coming from
the charging system
Check the logic and software
compatibility.
Check fan operation and connection.
Replace fan if faulty.
Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative
Contact your local ABB representative.
Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative
Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative.
Check the auxiliary code. See actions for
each code below.
Reduce the size of the application.
Reduce the number of parameter
mappings.
See the drive-specific log generated by
Automation Builder.
Update the system library or reinstall
Automation Builder.
See the drive-specific log generated by
Automation Builder.
In Automation Builder, give a "Clean"
command and reload the application.
In Automation Builder, check application
task configuration, give a "Clean all"
command, and reload the application.