-
When Alarm 2010 Hits, You Have Minutes—Not Hours
-
Step 1: Lock Out, Tag Out, and Verify Zero Energy
-
Step 2: Read the Fault History (Don't Just Reset)
-
Step 3: Check the Motor and Cables (This Is the Step Most People Skip)
-
Step 4: Verify Key Parameters (99.01, 99.05, 99.06, 20.01)
-
Step 5: Test the Mechanical Load (Turn the Motor by Hand)
-
Step 6: Check Drive Output with a Meter (Three-Phase Balance)
-
Step 7: Reset and Monitor Under Load (Don't Walk Away)
-
Common Mistakes (and Three Unrelated Fixes That Could Bite You)
When Alarm 2010 Hits, You Have Minutes—Not Hours
I'm a senior field service engineer at an authorized ABB VFD distributor. I've handled 200+ rush VFD repairs in the last 8 years, including same-day turnarounds for manufacturing clients. When a production line goes down because of alarm 2010, the clock starts ticking. I've seen a $50,000 penalty clause triggered by a 4-hour delay. So here's the 7-step checklist I actually use. It's not fancy—it's what works when you're under pressure.
This checklist is for maintenance techs, plant engineers, and anyone who needs to get an ABB drive back online fast. Total steps: 7. Average time if you follow it: 45–90 minutes, depending on the fault.
Step 1: Lock Out, Tag Out, and Verify Zero Energy
Before you touch anything, lock the disconnect and verify no voltage at the VFD terminals. I know it's basic, but I've seen a tech skip this because 'the drive was already off.' The DC bus capacitors can hold a lethal charge for up to 5 minutes after power removal. Wait for the charge LED to go out, then measure DC bus voltage with a meter rated for 1000V DC.
If you're also replacing an electrical outlet on the same circuit—say, the one feeding the VFD's control panel—treat it with the same respect. Kill the breaker, test for voltage, and use a GFCI outlet if it's in a wet location. That 5-minute check beats a 5-day hospital stay.
Step 2: Read the Fault History (Don't Just Reset)
Everyone wants to hit reset and move on. Don't. Alarm 2010 on ABB drives (ACS355, ACS880, ACH580) usually means overcurrent, but the exact cause matters. Go to the fault history in parameter group 04 (or the control panel's fault log). Write down the timestamp, the current at fault, and any other active faults.
Why? Because a single reset might clear the alarm, but if the underlying issue is a dying motor bearing or a loose cable, it'll come back at 2 a.m. I learned this the hard way: in February 2023, we reset a drive without checking the history. It tripped again 6 hours later during a critical run. Cost us a $12,000 emergency call-out and a very unhappy customer. Now I always pull the fault log first.
Step 3: Check the Motor and Cables (This Is the Step Most People Skip)
Here's what the manual doesn't emphasize enough: alarm 2010 is often not the drive's fault. Disconnect the motor cables from the VFD and megger the motor windings. You want at least 1 MΩ to ground (consult your motor's manual for exact values). Then check the cable insulation—look for nicks, crushed spots, or moisture ingress.
Everything I'd read said overcurrent alarms are usually ground faults. In practice, I've found that parameter mismatch causes them just as often. One time, a client had replaced a motor but forgot to change the motor nameplate data in the drive. The drive was pushing 20% more current than the motor wanted. Alarm 2010 every time. So step 3b: verify the motor data in parameters 99.05 and 99.06 matches the nameplate.
Step 4: Verify Key Parameters (99.01, 99.05, 99.06, 20.01)
This is the most overlooked step. After a firmware update or a parameter restore, it's easy to miss a critical setting. Use the ABB drive's control panel or Drive Composer to check:
- 99.01 – Language (irrelevant, but a common gotcha if you can't read the display)
- 99.05 – Motor nominal voltage (should match nameplate)
- 99.06 – Motor nominal current (this one trips people up—set it too low, and the drive thinks there's an overcurrent)
- 20.01 – Maximum current limit (factory default is usually fine, but check it)
I've also seen parameter 21.09 (overcurrent trip level) set too aggressively. If it's below the motor's actual starting current, you'll get nuisance trips. According to the ABB ACS880 firmware manual, alarm 2010 triggers when the drive's internal current limit is exceeded for a set time. So if your limit is 10% lower than the motor's FLA, you're asking for trouble.
Step 5: Test the Mechanical Load (Turn the Motor by Hand)
Lock out the drive again, then try to rotate the motor shaft. It should move freely (or with normal bearing resistance). If it's locked or hard to turn, you've got a mechanical problem—not an electrical one. Common culprits: a seized pump, a jammed conveyor, or a bound-up gearbox. Fix the mechanical issue first, then reset the drive.
Why does this matter? Because a jammed load draws way more current than a free one. I once spent two hours chasing an alarm 2010 on a pump, only to find a rag stuck in the impeller. The drive was fine.
Step 6: Check Drive Output with a Meter (Three-Phase Balance)
With the motor disconnected and the drive powered, use a true-RMS meter to measure output voltage from U, V, W to ground (not phase-to-phase if you're not rated for it). The three phases should be balanced within 3–5%. If one phase is significantly lower, you may have a failing IGBT or a bad output module. That's a drive repair, not a field fix.
If I remember correctly, the last time I saw an unbalanced output, it was on an ACS800 that had been running 24/7 for 7 years. The capacitors were shot. I want to say the repair cost was around $2,500, but don't quote me on that—it varies by drive size.
Step 7: Reset and Monitor Under Load (Don't Walk Away)
After you've fixed the root cause, reset the drive and start it with no load if possible. If it runs clean, slowly apply load and watch the current draw on the control panel. It should stabilize below the motor's FLA. Stay for at least 15 minutes to catch any intermittent trips.
This is the step that prevents the 'it came back' call. If you reset and immediately leave, you're gambling. And the odds are not in your favor.
Common Mistakes (and Three Unrelated Fixes That Could Bite You)
Mistake #1: Using a VFD for a solar panel battery charger. I've seen this attempt twice. A VFD is designed for motor control, not battery charging. The output waveform and voltage regulation are completely wrong. You'll damage the drive or the battery. Use a proper MPPT charge controller.
Mistake #2: Trying to control a whirlpool washer's control panel with a VFD. Washing machine panels are not simple motors—they have sensors, logic boards, and specific voltage requirements. Modifying one with a VFD is a fire hazard and voids the warranty.
Mistake #3: Replacing an electrical outlet without considering VFD harmonics. If you're adding a convenience outlet near a VFD, avoid sharing the same circuit. VFDs inject high-frequency noise that can damage sensitive electronics (like your phone charger). Use a separate circuit and a surge suppressor.
Mistake #4 (the one that gets people): Forgetting to document the final parameter set. Take a screenshot or write it down. Next time the drive acts up, you'll know what 'normal' looks like.
Look, I'm not saying following this checklist will eliminate every alarm 2010. But it will catch the 80% of cases that are caused by loose cables, wrong parameters, or a stuck load. And that's a lot cheaper than a downtime emergency. The 5 minutes you spend verifying motor data beats the 5 hours you'll spend explaining why the line is down.