VFD Overcurrent Fault (OC): Causes, Diagnosis, and How to Stop Repeat Trips

Key Takeaways: An overcurrent (OC) fault means the variable frequency drive measured output current above its protective threshold and shut down to protect its transistors. When the trip happens tells you where to look: at power-up points to the drive or wiring, during acceleration points to settings or an undersized drive, and at steady speed points to the motor or the mechanical load. Overcurrent is a symptom; the fix that lasts is finding what is drawing the current.

Read the trip by its timing

• Immediately at start: a shorted motor cable, a failed motor winding, a damaged output transistor, or a motor far too large for the drive. Test before restarting repeatedly: repeated starts into a short destroy drives.
• During acceleration: the acceleration ramp is too short for the inertia, the V/Hz or vector settings do not match the motor, or the mechanical load binds as it comes up to speed.
• At steady speed: a mechanical overload (failing bearing, jammed product, tightened belt), voltage imbalance, or a motor developing an insulation fault under heat.
• During deceleration: regenerative energy from a high-inertia load; the drive needs a longer ramp or braking capability.

Diagnosis: isolate drive, motor, load

• 1. Read the fault history. Most drives store current, frequency, and DC bus voltage at the moment of trip. Record them before resetting.
• 2. Lock out and inspect the obvious. Burnt smell, discolored terminals, damaged cable, water in the conduit.
• 3. Test the motor and cable disconnected from the drive. Megohm windings to ground and check phase-to-phase resistance balance. A megohm test finds most start-trip causes.
• 4. Run the drive uncoupled or unloaded if possible. If the drive runs a bare motor cleanly, the problem is in the machine, not the electronics.
• 5. Turn the load by hand. A bearing or gearbox that has started to fail shows up as resistance you can feel long before it seizes.
• 6. Verify parameters. Motor nameplate data in the drive, sensible acceleration and deceleration times, correct control mode for the application.

Stopping repeat trips

A drive that trips OC every few weeks is telling you something is degrading. Log every trip with its stored values in your CMMS so the trend is visible instead of anecdotal, and put the mechanical suspects (bearings, belts, lubrication) on the preventive maintenance schedule. Current monitoring through condition monitoring catches a rising load weeks before the protective trip. On the production side, Fabrico's computer-vision-verified OEE captures every one of these stops with true duration and context, and the closed-loop CMMS connects the trip to its work order, which is what makes downtime analysis point at the real offender.

FAQ

Can I just increase the overcurrent limit or auto-restart count?
Treat that as a last resort, not a fix. The limit protects the drive's transistors; raising it to silence a mechanical problem converts a cheap repair into a drive replacement.

The drive trips OC but the motor tests fine. Now what?
Suspect the load and the settings: run uncoupled, check the ramp times, verify nameplate parameters, and watch the stored trip values for a pattern.

Is an OC fault the same as an overload (OL) fault?
No. Overload is a thermal calculation over time; overcurrent is an instantaneous protective trip. OL says "working too hard for too long", OC says "current spiked past the safe limit".

Do all VFD brands behave the same?
Codes differ (OC, OCF, F0001, E-01 and so on) but the physics and the diagnostic order are identical across brands: timing of the trip, then isolate drive, motor, and load.

To see how verified downtime capture and closed-loop maintenance turn drive faults into trends you can act on, book a demo.