ABB +N5600 Firmware Instructions page 594

594 Fault tracing
Code
Fault
(hex)
6181 FPGA version
incompatible
6200 Checksum mismatch
Programmable fault:
Checksum action
6306 FBA A mapping file
6307 FBA B mapping file
6481 Task overload
6487 Stack overflow
64A1 Internal file load
64A2 Internal record load
64A3 Application loading
64A5 Licensing fault
Cause
Firmware and FPGA file
version in the power unit are
incompatible.
Update of power unit logic
failed.
The calculated parameter
checksum does not match any
96.54
enabled reference checksum.
Fieldbus adapter A mapping
file read error.
Fieldbus adapter B mapping
file read error.
Internal fault.
Internal fault.
File read error.
Internal record load error.
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.
800A The application contains an
unknown target (system)
library function.
Running the control program is
prevented either because a
restrictive license exists, or
because a required license is
missing.
What to do
Reboot the control unit (using parameter
96.08 Control board boot) or by cycling
power. If the problem persists, contact
your local ABB representative.
Retry.
See A686 Checksum mismatch
574).
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.
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.
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.
Update the system library or reinstall
Automation Builder.
See the drive-specific log generated by
Automation Builder.
Record the auxiliary codes of all active
licensing faults and contact your product
vendor for further instructions.
(page