A consolidated reference for the ABB ACS580 fault codes you are most likely to trip, with the common remote-checkable cause for each and the parameter to verify before you consider a replacement drive.
The ACS580 shows a fault code on the control panel (or through the drive's monitoring data in ABB commissioning tools) together with a stored fault history. That history — the code, the event timestamp and the parameter values around the trip — is what a remote specialist reads to tell whether the trip was an application issue, a wiring issue or a genuine hardware fault.
| Fault source | Where you see it | What it tells you |
|---|---|---|
| Fault code | Control panel display / ABB tools | The numeric code that classes the trip |
| Fault history | Drive menu (Fault history) | Recent codes with timestamps and a sequence |
| Live values | Monitoring menu | Bus voltage, output current, motor temp at the moment |
The table lists the most common ACS580 codes, their meaning, and the first remote check. Likelihood reflects field frequency.
| Code | Meaning | Likelihood | First Remote Check |
|---|---|---|---|
| 3210 | DC link overvoltage — bus exceeded its limit | High | Check bus voltage and look for motor regeneration or wrong parameter 30.xx |
| 2310 | Output overcurrent — current above drive rating | Med–High | Note the output current trend; check for a jam, winding fault or acceleration ramp |
| 2910 | Motor ground fault — current leaking to ground | Med | Isolate the motor cable and confirm with insulation checks |
| 3220 | DC link undervoltage — bus too low | Med | Check AC line voltage and input fuses/contactor at the moment of trip |
| 4210 | Parameter error — invalid or incompatible setting | Low–Med | Review recently changed parameters and restore defaults for that group |
| 5010 | Internal error — drive firmware or board issue | Low | Log the full code and fault history; cycle and re-read before deciding hardware |
Many ACS580 codes share the same root cause family (overvoltage, overcurrent, ground fault). Reading the bus voltage, output current and the recent-change log together is what identifies the actual trigger.
Work through these in order. Each step is something you can perform and report back on without opening the drive or removing parts.
Open the fault history on the panel and note the code(s), the sequence and the timestamps. The order of multiple codes is diagnostic gold.
Note bus voltage, output current and motor temp around the trip. Overvoltage vs overcurrent is told apart by these numbers, not the code label alone.
Was there a parameter change, a motor swap, a wiring edit, or a mains event right before? Recent changes usually reveal the trigger.
Confirm the motor nameplate data was entered correctly and the acceleration/deceleration ramps suit the load. Parameter errors are a common single-trip cause.
After aligning parameters and confirming the load path, reset and verify the drive holds without a repeated trip for a sustained run.
An ACS580 trip is an overvoltage, overcurrent or ground-fault path more often than a board failure. Cross-reference the specific conditions: Overvoltage fault · Ground fault · All motor/drive symptoms · VFD technology.
Fault 3210 is a DC link overvoltage. It usually means the DC bus exceeded its limit, typically from motor regeneration, mains overvoltage, or wrong parameter settings. It is remotely diagnosable from the fault history and live bus voltage.
Fault 2310 is an output overcurrent. Common remote-checkable causes include a motor winding fault, wrong motor parameters, or a mechanical jam. It is often recoverable without swapping the drive.
Yes. Share the fault history, live values and what changed; a specialist interprets the code and guides recovery. We never take control of your drive.
Send the fault history, live bus voltage/current and what changed. We interpret the code and guide recovery remotely — no drive replacement unless it is genuinely required.
Submit Your Case Connect With SpecialistsWe do not perform hardware repair, we do not replace parts, and we cannot promise a 100% resolution. Our role is limited to remote diagnostic and step-by-step guidance based on the information, photos and logs you share.
The most common DC-link trip in detail.
When current leaks to earth and trips the drive.
A related drive fault with a different vendor path.
Full VFD and motor troubleshooting collection.