How to Read a VFD Fault Log to Find a Root Cause

Back to Blog

Read the Fault Sequence, Not Just the Last Fault

The last fault displayed is often not the cause. A drive can post a cascade where one real fault triggers several downstream ones, and the one left on the screen is frequently a consequence rather than the origin. Open the fault log and read the sequence in time order, because the first fault in a burst is usually the root and the rest are what followed. Treating the final code as the answer sends you chasing a symptom while the real cause hides earlier in the list.

Note the timestamps and spacing between faults. Faults microseconds apart are a single cascade from one event; faults spread across hours or days are separate incidents that may or may not share a cause. A cluster of related codes at one instant tells a different story from the same code recurring on a schedule. The timing turns a flat list of codes into a narrative of what happened and in what order, which is where the diagnosis actually lives.

Map each fault to its meaning and its likely direction. An overcurrent, an overvoltage, an undervoltage, a ground fault, and an overtemperature each point to different territory, and knowing which one came first narrows the search immediately. An overvoltage first points at deceleration or the supply, as in the guide on setting VFD accel and decel times, while an overcurrent first points at the start or the load, as in the guide on diagnosing VFD overcurrent at start. The first fault chooses which trail to follow.

Interpret the Values Captured at the Trip

Many drives snapshot their state at the moment of a trip, and that snapshot is the closest thing to a witness. Read the latched output current, DC bus voltage, output frequency, and commanded speed captured at the fault, because they show what the drive was actually doing when it tripped. A trip at a high current tells a different story from one at a normal current with a low bus voltage, and the captured values separate those cases without you having to reproduce the event.

Cross-read the values against each other for consistency. An overcurrent latched with the current at the drive's limit confirms a genuine current event; an overvoltage latched with a high DC bus during deceleration confirms regeneration; an undervoltage with a low bus points at the supply, which you can pursue through the guide on diagnosing a VFD undervoltage fault. When the latched values agree with the fault name, you have confidence; when they do not, that mismatch is itself a clue that something unexpected happened.

Use the captured frequency and speed to place the fault in the operating cycle. A fault latched at a low frequency during acceleration is a start-region problem; one latched at a specific mid-range frequency hints at a resonance or a speed-dependent load issue; one at full speed under load points at an overload or supply limit. Knowing where in the speed range the drive was when it tripped often narrows the cause faster than the fault code alone, because many faults have a characteristic speed at which they appear.

Find the Pattern Across Repeated Faults

A single fault is an anecdote; the pattern across many is the diagnosis. Look at how the faults distribute: do they all happen at start, at a certain speed, after a run of a certain length, or at a particular time of day. Faults that cluster at start point at the start sequence or the load breaking away; faults at one speed point at a resonance or a speed-dependent problem; faults at a time of day point at a supply that dips when other equipment runs. The distribution usually names the cause more reliably than any one code.

Correlate the fault pattern with what else was happening. A drive that faults whenever a large motor elsewhere starts is telling you about the supply, not itself; a drive that faults only on hot afternoons points at temperature; a drive that faults after long runs points at heat building up. Reading the fault log alongside knowledge of the plant's schedule and environment turns a list of drive codes into a diagnosis of a system, which is where intermittent faults are finally caught.

Preserve the pattern with continuous monitoring rather than relying only on the drive's finite log. A drive's onboard log holds a limited number of faults and rolls the oldest off, so a slow-building intermittent problem can lose its early history. Because the drive's faults, current, bus voltage, and running state are values a monitoring system can trend continuously, the full pattern is retained beyond what the drive itself keeps, letting a fault that happens once a week be seen against months of context and its root cause found before it becomes a failure.

Frequently Asked Questions