🛠️ VFD Fault Codes: Common Variable Frequency Drive Faults and Fixes

Why VFD Faults Need a Different Approach Than a Tripped Breaker

A circuit breaker gives you one signal: tripped or not. A VFD gives you a fault code, and that code is telling you which of the drive's internal protection functions detected a problem — which is far more specific, but only useful if you understand what each fault category actually means. Every VFD manufacturer uses its own numbering scheme and exact fault names, but the underlying fault categories are remarkably consistent across brands, because they're all protecting against the same physical failure modes: too much current, too much or too little voltage, a path to ground, too much heat, or a lost feedback signal. Learn the categories, and you can diagnose an unfamiliar drive's fault code without the manual in hand, just from context.

Overcurrent Faults

An overcurrent fault trips when output current exceeds the drive's rated or configured limit, and it's one of the most common VFD faults because several unrelated conditions all produce the same symptom. Common causes: a mechanical overload on the driven equipment (the same real overload that would trip a motor's thermal overload on an across-the-line starter); acceleration or deceleration ramps set too aggressively for the load's inertia, causing the drive to demand more current than it can supply while trying to follow the commanded ramp rate; a short circuit or ground fault in the motor or motor cable (some drives report this as a distinct fault, others fold it into overcurrent); and, on drives sized close to the motor's rating, simple undersizing for the actual application.

Diagnosis: check whether the fault occurs during acceleration, at steady speed, or during deceleration — the timing narrows the cause significantly. A fault only during acceleration points toward ramp time or load inertia; a fault only during deceleration often points toward regenerative energy the drive can't dissipate fast enough (see overvoltage, below); a fault at steady-state speed under load points toward a genuine mechanical overload or an undersized drive.

Overvoltage and Undervoltage (DC Bus) Faults

VFDs rectify incoming AC to DC on an internal bus, then invert it back to variable-frequency AC for the motor. Both overvoltage and undervoltage faults are almost always about that internal DC bus, not the motor.

Overvoltage most commonly happens during deceleration — a motor and its load carry mechanical energy, and when the drive commands the motor to slow down faster than the load naturally would, that energy has to go somewhere. Without adequate dynamic braking (a braking resistor and chopper circuit) or regenerative capability, that energy pumps back into the DC bus and raises its voltage until the drive trips to protect itself. The fix is extending the deceleration ramp time, adding a braking resistor sized for the application, or enabling any built-in "flying start" or overvoltage-limiting ramp features the drive offers. Overvoltage faults can also stem from genuinely high incoming line voltage or voltage transients/spikes on the supply.

Undervoltage typically points to a genuine problem with the incoming supply — a sagging utility feed, a loose or high-resistance connection somewhere upstream (including at the drive's own input terminals), an undersized supply transformer or feeder for the load, or a momentary power interruption. Because the drive's control electronics and gate-drive circuits need adequate DC bus voltage to operate correctly, undervoltage faults are treated as a hard protective trip rather than something to push through.

Ground Fault

A drive-detected ground fault means current is finding a path to ground somewhere between the drive's output terminals and the motor — in the motor cable, motor terminal box, or the motor windings themselves. This is distinct from a ground fault detected by upstream protection on the input side. Common causes: motor cable insulation damage (heat, abrasion, or moisture in conduit runs), a failed motor winding-to-frame insulation (common in older or moisture-exposed motors), or a miswired or damaged motor terminal connection.

Diagnosis: disconnect the motor cable at the drive output and megger the motor and cable separately — insulation resistance from each phase to ground, measured with the motor and cable isolated from the drive. A low reading isolates whether the fault is in the cable or the motor itself. This is one of the few VFD faults that genuinely requires physical testing rather than parameter review, because it originates outside the drive's own electronics.

Overtemperature Faults

Modern VFDs monitor heatsink and/or IGBT junction temperature directly and will fault before physical damage occurs. Common causes: inadequate ventilation or cooling airflow around the drive (blocked vents, a failed cooling fan, or a drive mounted in an enclosure without adequate heat dissipation for its ambient conditions), an ambient temperature at the drive location that exceeds its rating, dust or debris buildup on heatsink fins restricting airflow, and the drive running at a continuous output current near its thermal limit for the installed conditions (which can happen if the drive is undersized relative to a genuinely continuous, high-duty-cycle load).

Diagnosis: check the drive's own displayed temperature reading against its rated maximum before assuming a fan or ventilation problem — many drives will show the actual measured temperature on the keypad or fault log. Physically inspect and clean heatsink fins and check that the cooling fan (if equipped) spins freely and reaches full speed.

Encoder / Feedback Faults

On drives running in closed-loop vector control with an encoder or resolver for speed/position feedback, a feedback fault indicates the drive isn't receiving a valid signal from the feedback device — a lost, noisy, or out-of-range signal. Common causes: a damaged or disconnected encoder cable (a very common cause, especially where the cable runs alongside power cabling and picks up electrical noise, or where cable strain over time causes an intermittent connection), a failed encoder itself, or incorrect feedback scaling/configuration parameters in the drive that don't match the actual encoder installed.

Diagnosis: verify the encoder cable is intact and, critically, routed separately from motor power cables (parallel runs of unshielded feedback cable next to VFD output cable is a classic source of noise-induced feedback faults, because VFD output waveforms are electrically noisy). Check encoder supply voltage at the drive terminals, and confirm the drive's encoder pulses-per-revolution and signal type parameters match the actual encoder nameplate.

Input Line vs. Motor/Cable vs. Drive-Internal — Sorting Faults by Location

A useful mental model when facing an unfamiliar fault code: ask whether the fault category points to the input side (undervoltage, some overvoltage causes, input phase loss), the motor/cable side (ground fault, some overcurrent causes, encoder faults), or the drive's own internals (overtemperature from a failed internal fan, IGBT-related faults, control board faults). This location-based thinking transfers across manufacturers even when the exact fault code number and wording doesn't, because the physical failure modes a drive protects against are the same regardless of brand.

For a broader look at when a VFD is the right choice of motor controller in the first place versus a soft starter, see VFD vs. Soft Starter: Which Motor Control Device Should You Use?

Why Firmware-Aware Diagnosis Matters

Unlike a thermal-magnetic breaker, whose trip behavior is fixed by its physical mechanism, a VFD's fault thresholds, ramp behavior, and even which conditions generate which fault code are configurable in firmware and parameter settings. Two identical drive models with different parameter configurations can behave differently under the same fault condition. Before assuming a hardware failure, always check the drive's parameter settings against the application (acceleration/deceleration times vs. load inertia, current limit vs. motor and load rating, and any application-specific settings a previous technician may have changed) — a large fraction of "drive failures" are actually parameter mismatches, not failed components.