Read this first: the code on the drive display isn’t always the root cause — an earlier fault can
trigger the one you see. Export the drive’s full event/fault history and work the earliest relevant
entry first (see “How to pull the full fault history” below).
No matches.
Try the code alone, an aux value, or a keyword like “overtemp”, “earth”, “cable”.
Try the code alone, an aux value, or a keyword like “overtemp”, “earth”, “cable”.
How to pull the full fault history (why the visible code can mislead)
A drive often trips on a secondary fault after a first event knocked it offline. The screen shows the last code, not always the trigger.
- On the assistant control panel: Menu → Diagnostics → Fault & event log for the ordered, timestamped event list.
- Or connect Drive Composer and export the Support package — full event history plus parameters.
- Work the earliest relevant fault/warning first, then re-check whether later codes clear on their own.
Sourced from the ABB ACS580 standard control program and ACS880 primary control program firmware manuals. Aux codes pinpoint the specific cause (phase, source, channel); where the manual lists them separately they appear under each code.
Reference tool for qualified personnel. Only qualified electricians may service a drive; follow the drive’s safety instructions.
Stuck on a code?
Contact our ABB-certified drives team and we’ll help work the history, not just the last code on the screen.
