ABB VFD 2310 Fault: What It Means, How to Diagnose It, and When to Repair vs. Replace

When I first started managing variable frequency drive purchases for our facility, I assumed any fault code meant one thing: call a technician, and probably budget for a new drive. That assumption was mostly wrong. After five years of handling ABB VFD issues across our production lines, I've learned that the same fault code leads to very different outcomes depending on your situation.

Take the ABB VFD 2310 fault, the overcurrent trip. I used to see "overcurrent" and immediately expect the worst. But here's the thing: the 2310 fault is the drive doing its job. It detected current above its threshold and shut down to protect itself and the motor. What you do next depends on why it tripped, not just that it tripped. That's why I'm going to walk through the three most common scenarios I've seen, with concrete steps for each.

If you're in procurement like me, this guide will help you ask better questions before approving a repair or a replacement.

There Is No Single Fix for a 2310 Fault

Here's what the fault code means in plain terms: the drive measured current above its trip threshold and shut down. That's the whole message. The diagnostic code tells you what happened, but it doesn't tell you why it happened.

The 2310 fault is the drive doing exactly what it was designed to do. Your job is to find out what triggered it.

From what I've seen, the cause usually falls into one of these categories:

• Wiring issues — loose terminals, damaged cables, or an incorrect phase connection between the drive and the motor.
• Mechanical overload — something is physically preventing the motor from turning freely, so current spikes.
• Parameter problems — acceleration ramp times that are too aggressive, or motor data that doesn't match the nameplate.
• Component failure — the drive itself, or, more commonly, the cooling system that keeps the drive within its rated temperature range.

Which one is causing your problem? That depends on when the fault appears, what the drive is doing at the time, and what your multimeter tells you. Let's take each scenario in turn.

Scenario 1: The Drive Powers Up Normally, But Trips When the Motor Draws Current

This is the most common variation we've dealt with. The drive energizes, the panel shows no faults at idle, and then the 2310 fault appears as soon as the motor starts pulling real current. Here's the sequence I use.

Check the mechanics first

Disconnect the motor from the load if you can, and turn the driven shaft by hand. I wasted an entire afternoon once diagnosing a "faulty drive" that was actually being overloaded by a seized bearing in the gearbox. The motor couldn't accelerate normally, so current spiked and the drive shut down. The drive wasn't the problem. The mechanics were.

Measure the actual current draw

Next, check what the drive is really putting out. If you've never used a clamp meter for this, you're not alone — but it's worth learning. Here's how to set amp gain with multimeter for a basic drive check:

• Set the dial to AC current (usually labeled "A~" or with a "~A" symbol). Make sure you're on the current scale, not voltage.
• Zero the meter if it has that function, and clamp it around one phase conductor on the output side of the drive.
• Read the value under load and compare it to what the drive keypad reports.

The point isn't to perform a precision calibration. It's to see if the keypad reading and the actual current are in the same neighborhood. If the keypad says 25 amps and your meter reads 25, the drive's current sensing is probably fine and the overcurrent is real. If there's a large mismatch, you may have a current-sensing problem, and that's a job for an ABB-authorized tech.

Inspect wiring and parameters

Loose terminals cause voltage drops, and voltage drops cause current spikes. Check all three output phases and the ground connection. And check your acceleration time. I can't tell you how many times a 2310 fault turned out to be a drive configured with a ramp time of one second when the application realistically needed five. The drive was doing its best; the configuration was wrong.

(Should mention: if you've got a Mac control panel or a computer running ABB's Drive Composer software, you can check fault history and parameters without standing at the drive. We rarely use ours for day-to-day troubleshooting, but it's invaluable for comparing settings across multiple drives.)

Scenario 2: Overheating and the ABB VFD Cooling Fan

The second-most-common root cause we've found is heat — specifically, the drive's internal cooling fan not doing its job.

ABB VFDs rely on internal fans to keep the IGBT modules and DC bus capacitors cool. When the fan slows down or fails, the drive runs hotter, components age faster, and eventually you'll start seeing faults. Sometimes the drive displays a thermal fault; sometimes it appears as a 2310 under load because the elevated temperature changes the electrical characteristics of the power stage.

Here's what I've learned about the abb vfd cooling fan:

• Fans fail gradually. The motor still spins, but at a lower speed. The drive doesn't detect it because the fan is still spinning — just not moving enough air.
• Noise matters. If you hear a grinding noise or a high-pitched bearing whine, don't wait for a fault. Replace the fan on schedule.
• Dust is the enemy. A fan that's clogged with dust moves almost no air, regardless of what the tachometer says.

Replacing the cooling fan is one of the few repairs I'm comfortable doing in-house, and honestly, it's closer to preventive maintenance than a repair. We now replace fans every five years on our ACS355 units. Some maintenance managers I know think that's too aggressive. I've seen enough failed fans to disagree. (The cost-benefit math is pretty clear: a fan is a hundred-something-dollar part. A drive failure with production downtime costs us thousands.)

One thing that genuinely surprised me: air quality makes a real difference. We started running Winix air purifiers in the electrical rooms a couple of years ago, and staying on top of winix air filter replacement has visibly reduced the dust that accumulates inside our VFD enclosures. I didn't expect that when I originally ordered the purifiers for the office. The maintenance team liked the idea for the control room, so we added them there. Now we keep spare filters in the regular procurement cycle.

If your drive is in a dusty environment, add "inspect and clean the cooling fan" to your quarterly maintenance checklist. It's the cheapest insurance you'll ever buy.

Scenario 3: Repeated Faults, End-of-Life, and the Repair vs. Replace Decision

At some point, you have to stop asking what's causing the fault and start asking is this drive worth keeping.

That decision is uncomfortable because nobody wants to replace equipment that's supposed to last 15 to 20 years. I'm not saying you should replace at the first sign of trouble. But after the third or fourth trip to the same well, you need to be honest about what's happening.

Here's the decision rule we use:

• Same fault code appears three times in one year, and...
• Wiring, mechanics, parameters, and cooling fan have all been ruled out, and...
• The drive is more than 10 years old or approaching its obsolescence window...

...then the drive itself is the problem — and the next repair probably won't be the last repair.

When that happens, do the math in terms of total cost, not just the repair invoice. A repair might cost $1,200. A replacement might cost $2,000. But each failure also costs you:

• Production downtime, which is almost always the biggest line item
• Emergency shipping and after-hours labor
• The maintenance manager's time spent troubleshooting instead of doing planned work
• Confidence that the repair will actually hold

So while the repair quote looks cheaper on paper, the real cost of keeping an unreliable drive running is usually far higher. For our critical ABB ACS355 and ACS880 units, we've started keeping a configured spare drive on the shelf. That one decision — a few thousand dollars in inventory — has saved us multiple unplanned shutdowns. Better than any extended warranty we've never used.

I have mixed feelings about extended warranties on drives, honestly. On one hand, they transfer risk to someone else. On the other hand, we've never had a warranty pay off — the failures we've experienced happened outside the coverage window, or the premium simply didn't justify the benefit. What actually protects us now is the spare drive and the diagnostic checklist.

How to Tell Which Scenario You're In

Here's the decision path I use when the 2310 fault appears. It's not a replacement for a qualified technician's judgment, but it'll help you narrow things down and communicate better with whoever you bring in.

1. Does the drive power up and display normally at idle?
   No → This isn't a 2310 problem yet. Check supply voltage, fuses, and input wiring.
2. Does the 2310 fault appear immediately on start, or only when the motor is under load?
   Immediately → Suspect wiring or a physically seized load. Stop and inspect before running again.
3. Can the driven equipment turn by hand with the motor disconnected?
   No → The mechanical load is the problem, not the drive. Fix the mechanics first.
4. Does the measured amp draw match the keypad's display?
   No → Possible current-sensing issue. This is where I'd call in a tech with proper instrumentation.
   Yes → Look at acceleration times and motor parameters. Then check the cooling fan.
5. Is the cooling fan spinning smoothly, quietly, and at full speed?
   No → Replace the ABB VFD cooling fan before spending money on anything else.
6. Has this fault repeated multiple times in the past year?
   Yes → Start the repair-versus-replace analysis. Get quotes, check lead times, and consider a spare drive.

Working With Your ABB VFD Distributor

If the diagnostic path points to something you can't handle in-house, the way you approach an ABB VFD distributor makes a big difference in how quickly you get back up. Here's what I've learned from the procurement side:

• Have the model and serial number from the nameplate ready. Don't make tech support ask for it. It saves everyone time.
• Take a clear photo of the fault code display. Not a blurry screenshot from a control room monitor or a shaky 45-second video. One clear photo is worth a thousand words.
• Know the fault history. "2310 appeared four times in the last eight weeks" is the kind of detail that helps a distributor recommend the right fix — or the right replacement.
• Send the drive's parameter list. If you're working with a qualified tech, they can pull this with Drive Composer. If you're buying a replacement drive, your distributor needs to know how the existing unit is configured so they can supply a like-for-like match.

At the end of the day, the ABB VFD 2310 fault isn't usually a death sentence. It's the drive telling you that something is wrong — and your job is to find out what. The drive is doing exactly what you bought it to do.

I built a simple six-step diagnostic checklist after our third confusing 2310 incident, and it's saved us an estimated $8,000 in potential rework and unnecessary repairs. Not because it's clever, but because it forces us to verify before we replace. Five minutes of checking beats five days of correcting — and that's a lesson I only had to learn a few times.