How to Troubleshoot and Repair ABB VFD Faults: A Practical Step-by-Step Guide

When You Need This Guide (And When You Don't)

Look, if you're just starting to collect fault codes and hoping they'll go away on their own—this guide is for you. I've been on both sides: the guy who ignored a persistent F2310 on an ACS355 and the guy who paid for it later. Not my finest moment.

This is for situations where:

• You've got an ABB VFD showing a fault code you don't recognize
• You're trying to decide between calling a service tech and doing it yourself
• You need to get a production line running again—fast

It's not for: deep component-level repair (we don't do that here) or situations where the drive is still under warranty (let ABB handle it).

There are six steps. Follow them in order. Skip one, and you're troubleshooting blind.

Step 1: Capture the Fault Code (Don't Clear It Yet)

First thing: note the exact fault code. Not just the number, but the context. When did it happen? What was the drive doing? Was it at startup, during steady running, or under load?

I still kick myself for not logging these details earlier. I'd see code F2310 on an ACS550, clear it, and cross my fingers. Rinse and repeat. The same fault reappearing? That's a pattern, not bad luck.

Here's what you need to record (I keep a spreadsheet—nerdy, I know):

• Fault code and description (e.g., F2310 = IGBT temperature)
• Drive model and firmware version
• Motor parameters (power, current, speed)
• Time of day and production load
• Ambient temperature (I check this with a cheap IR thermometer)

Note to self: I really should automate this logging. For now, a notebook works.

Step 2: Check the Obvious (Power, Cooling, Wiring)

Worse than expected: a fault code that disappears after a power cycle. It's tempting to call it fixed. Don't.

Run through this checklist before touching any parameters:

1. Input power: Is voltage stable? A multi-meter (not a multimeter—one tool) is fine. I've seen a loose connection at the breaker cause intermittent F2310 faults on an ACS355.
2. Cooling: Clean the heatsink. Seriously. A clogged fan is the #1 cause of overtemperature faults in dirty environments (like, say, a cement plant).
3. Motor wiring: Check for shorts, ground faults, and loose terminals. A frayed wire can mimic a sensor failure.

After the third late delivery from the same vendor, I was ready to give up on them entirely. What finally helped was building in buffer time rather than trusting their estimates. Same logic here: check the basics before assuming complex failure.

Step 3: Understand the Fault's Root Cause (Not Just the Symptom)

The most frustrating part of fault codes: they tell you what failed, not why. F2310 is an IGBT temperature fault. But why is the IGBT hot?

Possible root causes:

• Overload (motor drawing too much current)
• Poor cooling (fan failure, dirty heatsink)
• High ambient temperature (above 40°C for most ABB drives)
• Low carrier frequency (creates higher switching losses)
• Short circuit or ground fault in the motor

I talked to a guy who spent two months chasing a F2310 on an ACS880. Turned out to be a misconfigured carrier frequency. Two months. The parameter was set to 4 kHz instead of 3 kHz. That's a 25% difference in switching losses. Point is: don't assume the drive is faulty. Assume the settings or environment are.

Step 4: Use ABB's Built-In Diagnostics (Before Calling Support)

ABB's drives have pretty solid diagnostic tools. But most people don't use them. (I didn't for the first year).

Here's what to check:

1. Fault history: Every ABB drive stores the last 2-5 faults. Use the keypad or DriveStudio software to pull them. I like the ACS355's history function—simple and clear.
2. Actual signals: Monitor motor current, DC bus voltage, and heatsink temperature in real-time. Compare to normal values.
3. Parameter check: Verify settings against the motor nameplate. A mismatched motor nominal current is a common mistake.

Quick tip: if you have a DriveStudio cable, use it. The software logs are way more detailed. (Mental note: I need to upgrade my DriveStudio to the latest version. The one I have is from 2022.)

Step 5: Apply the Fix (And Test Under Load)

Once you've identified the root cause, apply the fix. Some examples:

• Overload: Reduce load, increase acceleration time, or check for mechanical binding.
• Cooling issue: Clean the fan, increase the heatsink's surface area (add an external fan if needed).
• Parameter error: Re-set the motor parameters from the nameplate. Use the autotune function if the drive supports it.

Then: test under full load. Not just a no-motor run. Put the motor under its normal load for 15-20 minutes. Watch the temperature. If the fault returns, you missed something.

I've come to believe that a 15-minute test under load is worth more than a week of theoretical analysis. At least, that's been my experience with production environments where 'try and see' is the practical option.

Step 6: Document Everything (Your Future Self Will Thank You)

This is the step most people skip. Don't. After troubleshooting the same fault three times on the same drive model, you'll wish you'd written it down.

Document:

• The fault code, drive model, and serial number
• The root cause and fix applied
• The date and time
• Any parameter changes made
• Parts replaced (if any) and their order numbers

I use a shared Google Sheet for our plant. It's not fancy, but it's searchable. Do this for a year, and you'll have a fault history that makes troubleshooting the next one 50% faster.

Common Mistakes (Learn From Mine)

I mentioned a few already, but here are the big ones:

• Clearing the fault without logging it. You lose the context. Program your DriveStudio to auto-save logs.
• Assuming the drive is faulty. It's usually a configuration or application issue. I've replaced a perfectly good IGBT module because I didn't check the heatsink first.
• Skipping the motor check. A bad motor can sink a good drive. Check the motor insulation resistance (megger test) before blaming the VFD.
• Using a 'universal' parameter set. The ACS355 and ACS880 have different default parameters. Don't assume one set works for all.

Note: pricing data for DriveStudio software and spare parts was accessed on April 7, 2025. Verify current pricing with your ABB distributor as rates may have changed.