The drive tripped on overcurrent. You pressed reset, pressed start, and it tripped again. The production supervisor is walking over. Someone has already floated the idea of calling the manufacturer to report a defective drive.
Before you make that call, understand what an overcurrent fault actually means. The drive detected output current exceeding its instantaneous trip threshold, and that threshold exists for exactly one reason: to protect the drive’s IGBTs from destruction. The drive is not broken. It is doing its job.
The real question is why the current spiked in the first place. More than 80% of the time, the answer is not a hardware defect in the drive. It is something upstream, downstream, or in the parameter settings, and once you know where to look, the fix is usually fast.
Overcurrent vs. Overload: They Are Not the Same Fault
The first thing to clarify, because a lot of technicians run these together, is that overcurrent and overload are different faults with different causes. They both involve current, and they both trip the drive, but everything else about them is different.
Overcurrent is an instantaneous trip. The current exceeded a hard threshold in a very short time window, typically within one PWM cycle. The drive is protecting its own power electronics from a current spike that would damage the IGBTs almost immediately.
Overload is a thermal accumulation trip. The current exceeded the motor’s rated current for long enough to create a thermal risk to the motor windings. The drive is protecting the motor. This is often reported as I-squared-t or OL1 depending on the manufacturer.
The causes and the investigations are different. Overcurrent points you toward mechanical problems, ramp issues, control mode mistakes, and cable faults. Overload points you toward load characteristics, motor data entry, and drive sizing. This article covers overcurrent. If your drive is throwing an overload fault instead, the diagnostic path is related but distinct, and it is covered in our VFD Troubleshooting Guide.
Acceleration Ramp Too Fast
This is the most common cause of overcurrent on startup, especially on fans, flywheels, centrifuges, and any load with significant rotational inertia. The drive is trying to accelerate the motor and its load faster than the available current allows. The inrush current during acceleration exceeds the drive’s instantaneous limit, and the drive trips to protect itself.
Factory default ramp times are typically 5 to 15 seconds, and for many applications those defaults are far too aggressive. Large fans need 60 seconds minimum, often 90 to 120 seconds. Pumps often need 30 to 60 seconds. The goal is to spread the acceleration energy demand over a longer window so the peak current during acceleration stays below the drive’s overcurrent threshold.
The fix is straightforward. Increase the acceleration time. Start by doubling it. If the fault clears, fine-tune from there by reducing in 25% increments until you find the balance between process response and current headroom. If the fault persists even with a very long ramp (say, 120 seconds on a fan), the ramp time is not the problem and you need to investigate further. Do not try to fix this by increasing the overcurrent trip level or by cranking up torque boost. Both approaches mask the symptom while stressing the motor and driven equipment.
Mechanical Binding or Seized Load
If the motor cannot turn because something is mechanically stuck, the drive will pour current into a stalled rotor. Stall current on a standard induction motor is typically 5 to 7 times the rated full-load current, which means the drive’s overcurrent protection will trip almost instantly. The drive is not the issue. Something in the mechanical system is.
Common culprits include a seized bearing in the motor or driven equipment, a jammed conveyor, debris in a pump impeller, a frozen coupling, or a gearbox that has lost lubrication. On outdoor installations in cold climates, ice formation inside a fan housing or condensate freezing in a pump can cause a no-spin condition on the first start of the day.
Before you open the drive cover, go to the motor. Lock out and tag out the drive. Then try to rotate the motor shaft by hand. If the shaft will not turn, or if it takes unusual force to turn it, the problem is mechanical. Fix the mechanical problem before you touch the drive. This takes two minutes and eliminates or confirms the most common physical cause of an overcurrent fault.
Wrong Control Mode: Variable Torque on a Constant Torque Load
A drive configured for variable torque (VT) mode is expecting a centrifugal load where torque demand is very low at low speeds and rises with the square of speed. Fans and centrifugal pumps behave this way. Conveyors, mixers, positive displacement pumps, and extruders do not.
If the actual load is constant torque (CT) and the drive is set for VT, the drive limits low-speed current too aggressively and cannot deliver the torque the load requires to break away. The result is a classic first-week fault: the conveyor will not start, the mixer stalls on the initial command, and the drive trips on overcurrent before the shaft moves. You have not damaged anything. You have simply told the drive to behave in a way that does not match what the load actually needs.
The fix is to change the load type parameter to constant torque and verify the drive was sized for its CT rating (not its VT rating) in the first place. Most drives have dual horsepower ratings on the nameplate, one for CT and one for VT, with the VT rating being higher. If the original specifier used the VT rating for a CT load, you have a sizing problem on top of the parameter problem. For details on CT vs. VT sizing, see our VFD Sizing Guide.
Starting Into a Spinning Load
This scenario shows up most often on fans. The fan is still rotating when the drive receives a start command, usually because air pressure from another running fan has backdriven it (windmilling), because the fan is coasting after a recent stop, or because wind loading is turning an outdoor exhaust wheel. The drive starts its output at 0 Hz, but the motor shaft is already turning at some speed, possibly in the reverse direction.
The frequency mismatch between the drive’s output and the motor’s actual rotation creates a massive inrush of current as the drive tries to force synchronization. The drive trips on overcurrent before the first stable half-cycle of output.
The fix depends on the application. Flying start (also called catch-on-the-fly or spinning start) is a feature available on most modern drives that senses back-EMF from the spinning motor, matches its current speed and direction, and then ramps to the commanded setpoint. Enabling flying start solves most windmilling overcurrent faults on fans. For applications where multiple fans are adjacent, coordinating the start sequence or installing dampers to prevent cross-draft is another path. DC braking at start, which brings the motor to a full stop before ramping, is a third option for stubborn cases.
Motor Cable Problems
A short between output phases, a phase-to-ground fault in the cable, or a damaged connection can cause overcurrent. The telltale sign is timing: if the fault occurs the instant the drive begins output, before the motor even has a chance to turn, suspect the cable.
Disconnect the motor cable at the drive and perform an insulation resistance test (megger test) on each phase to ground and phase to phase. Anything below 1 megohm at 500 VDC is suspect. Anything below 100 kilohms is a definite problem. The test takes five minutes and either eliminates the cable as the cause or confirms it definitively. For details on proper cable installation that prevents these problems in the first place, see our VFD Installation Guide.
Physical damage to the cable jacket, moisture intrusion at junction boxes or conduit bodies, and rodent damage in outdoor or underground runs are all common causes. Do not assume a cable that tested fine during original commissioning is still fine six months or six years later.
Undersized Drive
If the drive is simply too small for the load, overcurrent faults will be persistent and repeatable regardless of what you do to the parameters. Check the drive’s rated output current against the motor’s full-load amps and against the application’s actual current demand at the operating point.
A drive running continuously above 90% of its rated current is undersized for the application, even if the nameplate math looked right on paper. Real-world conditions, elevation, ambient temperature, duty cycle, and acceleration inertia all eat into the drive’s usable capacity. For the full sizing methodology that prevents this problem at specification time, see our VFD Sizing Guide.
A Simple Investigation Sequence
When you get an overcurrent fault, work through these questions in order. This sequence moves from the most common and easiest-to-check causes to the less common ones, and most overcurrent faults are resolved in the first three steps.
- Can the motor shaft rotate freely by hand with the drive locked out?
- Is the acceleration ramp time reasonable for the load’s inertia?
- Is the control mode (VT vs. CT) correct for the actual application?
- Is the motor spinning when the start command is given?
- Is the motor cable in good condition (verify with a megger test)?
- Is the drive sized correctly for the actual load conditions?
If you work this sequence and the fault is still present, the problem is outside the common causes and you are into the territory that Chapter 18 of Before the First Fault covers in more detail: faulty DCCT sensing circuits, torque boost misconfiguration, and the hardware-level diagnostics that come next.
Closing
The overcurrent fault is a message. The drive detected a condition that would damage its power electronics if it continued, and it did what it was designed to do. The correct response is to investigate, not to reset and hope.
For the complete diagnostic framework covering every first-week fault category (overcurrent, overload, overvoltage, undervoltage, ground fault, and communication faults), see our VFD Troubleshooting Guide. For the full treatment of fault diagnosis, root cause investigation, and the installation decisions that prevent faults in the first place, see Before the First Fault: A Field Guide to VFD Installation and Reliability. For hands-on training that takes practitioners through these diagnostic sequences live on real drives, see our VFD intermediate certificate course. If the training has to be justified to somebody holding the budget, the ROI of VFD training works through the replacement cost and the failure math.
Author: Dr. Carl Lee Tolbert, PhD, CMRP, Wayward Leaders LLC, waywardleaders.com
Frequently Asked Questions
What does an overcurrent fault mean on a VFD?
An overcurrent fault means the drive detected output current exceeding its instantaneous trip threshold, usually within one PWM cycle. The drive trips to protect its IGBTs from damage. It is a protective action, not a sign of drive failure, and it almost always points to something in the load, the cables, or the parameters rather than a defect in the drive itself.
What is the difference between overcurrent and overload on a VFD?
Overcurrent is an instantaneous trip caused by a current spike, protecting the drive's power electronics. Overload is a thermal accumulation trip (I-squared-t) caused by sustained current above the motor's rated value, protecting the motor from overheating. They show up with different fault codes and point to different root causes, so read the fault code carefully before starting diagnosis.
Why does my VFD trip on overcurrent at startup?
The most common causes of startup overcurrent are acceleration ramp time too short for the load's inertia, mechanical binding in the driven equipment, wrong control mode (variable torque configured on a constant torque load), starting into a spinning or windmilling load, and motor cable faults. Work through these in order and most cases resolve quickly.
Can a bad motor cable cause a VFD overcurrent fault?
Yes. A short between output phases, a phase-to-ground fault, or a damaged connection in the motor cable can trigger an overcurrent fault the instant the drive begins output. Disconnect the cable at the drive and run an insulation resistance test (megger test) on each phase to ground and phase to phase. The test takes five minutes and will confirm or eliminate the cable as the cause.
How do I fix a VFD overcurrent fault?
Start with the easiest checks first. Verify the motor shaft turns freely by hand (lock out the drive first). Increase the acceleration ramp time if the fault occurs during startup. Verify the control mode matches the load type. Check for a spinning load and enable flying start if needed. Megger-test the motor cable. Finally, verify the drive is sized correctly for the actual load. Resetting and retrying without investigating is not troubleshooting. It is denial, and it often leads to equipment damage.
What is flying start on a VFD?
Flying start (also called catch-on-the-fly or spinning start) is a drive feature that detects the rotational speed and direction of a spinning motor before applying output. The drive matches its output frequency to the motor's current speed, then ramps to the commanded setpoint. This prevents the massive inrush current that occurs when a drive starts at 0 Hz into a motor that is already turning. It is essential for fans with long coastdown times and for any application where the motor may be windmilling at start command.