Is it safe to keep resetting a VFD that trips?

An occasional trip may be harmless, but repeatedly resetting a drive without finding the cause usually leads to a larger failure. The trip is protecting the motor. Resetting without diagnosis just removes the protection while the underlying problem continues.

What is the difference between an overload trip and an overcurrent trip?

An overcurrent trip is a fast reaction to a sudden current spike, often from a short circuit or ground fault. An overload trip is slower: the drive uses a thermal model to track heat building in the motor over time and trips when sustained current would damage the windings. They have different causes and different fixes.

Why does a VFD trip if the motor is sized correctly?

Most trips on correctly sized systems are not caused by sizing. They come from configuration errors, mechanical resistance in the driven load, power quality problems, or environmental conditions the drive is detecting. The fault code reports the symptom the drive noticed, not the root cause upstream of it.

Troubleshooting guide

Why Your VFD Keeps Tripping (and How to Actually Diagnose It)

A tripping drive isn't the problem. It's the drive telling you it noticed one. The trick is reading what it noticed and working backward to the cause — in the right order, so you're not throwing parts at a symptom.

Last updated: August 2026 · written and reviewed by a working maintenance professional

If you're here, you've probably got a variable frequency drive that keeps faulting out — on overload, on overcurrent, maybe seemingly at random — and someone's already suggested replacing it. Before you spend that money, understand one thing that separates techs who fix drives from techs who swap them: the fault code names the symptom, not the cause.

An overcurrent fault can come from a jammed conveyor, a ramp that's too fast, a nicked motor cable, or a genuinely failing drive. Same code on the display. Four completely different fixes. If you react to the code instead of the cause, you'll be right about a quarter of the time and broke the rest.

And there's a second pressure most guides ignore: the machine is usually down while you're diagnosing it. Every minute of troubleshooting is a minute of lost production, and someone is asking when it'll be back. That changes how you prioritize. You don't just work cheapest-first — you work cheapest and fastest first. When you've got several things worth checking, start with the one you can rule in or out in thirty seconds, not the one that needs the panel open and ten minutes of setup. Get the machine running again as fast as you safely can, then chase the deeper root cause.

Here's the diagnostic sequence that actually works.

Step 1: Read the fault log, not just the current fault

The drive remembers. Almost every VFD keeps a fault history with timestamps, and that history is the single most useful thing on the panel. Pull it up before you touch anything.

What you're looking for is pattern. Does it trip at startup, or minutes into a run? Always at the same point in the cycle, or randomly? Clustered at a certain time of day? A trip that always happens two seconds after start is a completely different animal from one that happens once a shift under peak load. The log turns "it keeps tripping" into "it trips on overload, 90 seconds into the cut, only on the heavy parts" — and that sentence nearly diagnoses itself.

Step 2: Separate overload from overcurrent

These get used interchangeably in the break room, but they mean different things and point in different directions.

An overcurrent fault is the drive reacting fast to a sudden current spike — the kind you get from a short circuit, a ground fault, or a mechanical slam. It's an instantaneous protective trip.

An overload fault is slower and smarter. The drive runs a thermal model of the motor: it watches how much current is flowing, for how long, and calculates the heat building in the windings. When that modeled heat crosses the danger line, it trips — even if no single instant looked alarming. Overload is about sustained effort, not a sudden spike.

Knowing which one you have tells you where to look next. Overcurrent points you toward the electrical side — cables, connections, insulation. Overload points you toward the mechanical load and the drive's configuration.

Step 3: Rule out the cheap, fast stuff before the expensive, slow stuff

This is the part most guides skip, and it's the part that gets the machine running soonest. Work from cheapest and fastest to most expensive and slowest — because the line is down and every option you try has a time cost, not just a parts cost. If two checks are equally likely, do the quicker one first:

Check the motor parameters in the drive. If the motor's full-load amp rating was entered too low during commissioning, the drive thinks the motor is overloaded when it's running perfectly normally. This is a five-minute check that fixes a surprising number of nuisance trips. Compare the nameplate to what's actually programmed.
Turn the driven load by hand (safely, locked out). A conveyor that's hard to turn, a pump that won't spin freely, a bearing that grinds — that mechanical resistance shows up as extra current the drive has to push, and eventually as an overload trip. The fault is real; it's just not electrical.
Look at the ramp and torque settings. A ramp that accelerates too fast on a high-inertia load forces a big current surge every startup. Torque boost set too high does the same. These are configuration, not hardware.
Measure your three input phases under load. If one phase sags when the load comes on, you've got a high-resistance connection somewhere — a loose lug, a pitted contactor contact — and the drive is correctly complaining about the imbalance it sees.

Step 4: Only now consider the drive itself

Field data backs this up: the large majority of first-year drive faults trace back to installation, commissioning, and application decisions — not defective hardware. The drive is usually the messenger. So a genuinely failed drive is the last box you tick, not the first, after you've cleared configuration, the mechanical load, and power quality.

If you've confirmed the parameters match the nameplate, the load turns freely, the ramp is sane, and all three phases hold voltage under load — and it still trips — now you've earned the right to suspect the drive.

Reading about this is one thing. Doing it is another.

faultline101 drops you into VFD nuisance-trip scenarios where the readings respond to your choices — chase the wrong theory and you'll watch it cost you, exactly like a real callout. You practice the sequence above until it's instinct, on a drive you can't actually break.

Module 1 is free, no card required — see how it works.

Works with no signal. Install it on your phone and the whole course — 35 modules, 210 faults — comes with you into the plant.

Try the trainer free

The one habit that matters

If you take a single thing from this: work from symptom, to fault code, to measurement, to root cause — in that order — and when you have several things to try, do the quickest one first. A machine that's down doesn't just cost you a part; it costs production for every minute it's stopped. Resist the urge to fix the first thing that looks wrong, but also resist the urge to pull the whole panel apart when a thirty-second check might get you moving again. The displayed fault is the end of the story the drive is telling you, not the beginning. Your job is to read it backward to where the trouble actually started — as fast as you safely can.

Do that consistently and you'll fix drives that other people replace, and get the line back sooner than the tech who starts by swapping parts — which is exactly the reputation worth having.