A VFD, variable frequency drive, is an electronic controller that varies the speed of an AC motor by changing the frequency and voltage of the power feeding it. It rectifies incoming AC to DC, then rebuilds a new AC waveform at whatever frequency the process needs. Slow the motor, and on pumps and fans the energy savings are dramatic.
If a PLC is the brain that decides when a motor should run, the VFD is the muscle that decides how fast. It sits between the electrical panel and the motor, and it is quietly one of the highest-return pieces of hardware on a plant floor, both because it cuts the power bill and because the drive is measuring the motor the whole time it runs.
What does a VFD actually do?
It breaks the fixed relationship between line frequency and motor speed. An AC induction motor's speed is set by the frequency of its supply: on a 60 Hz grid, a four-pole motor turns near 1,800 RPM whether you need that speed or not. Without a drive, the only ways to slow the output are mechanical, throttling valves, dampers, gearboxes, all of which waste energy by fighting a motor still running flat out. A VFD changes the supply frequency itself, so the motor turns exactly as fast as the job requires and draws only the power that speed demands.
Three stages do the work. The rectifier a bank of diodes, turns the incoming fixed-frequency AC into DC, which only flows one direction. The DC bus uses a capacitor bank to smooth that DC into a stable reservoir of voltage. The inverter does the clever part: fast electronic switches, usually insulated-gate bipolar transistors (IGBTs), chop the DC into precisely timed pulses using pulse-width modulation (PWM) switching thousands of times per second. The motor's windings average those pulses into a clean-enough sine wave at whatever frequency and voltage the drive commands.
How does a VFD save energy?
On pumps and fans, through physics, the affinity laws. For centrifugal loads, flow scales with speed, pressure scales with speed squared, and the power the motor draws scales with the cube of speed. That cube is the whole story. Slow a fan to 80% of full speed and it draws roughly half the power. Slow it to 50% and it draws about an eighth. Compare that with the old approach, running the motor at full speed and throttling a damper, which is like driving with your foot flat on the gas and controlling speed with the brake.
Not every load behaves this way. Conveyors, mixers, and positive-displacement pumps are constant-torque loads, where power scales roughly linearly with speed, real savings, but not cubic. VFDs still earn their keep there through soft starting (no inrush current slamming the motor and gearbox), precise process control, and gentler mechanical wear. The drive keeps a constant volts-per-hertz ratio as it lowers frequency so the motor holds its rated torque instead of stalling.
Where are VFDs used on a plant floor?
Almost anywhere a motor does not need to run at one fixed speed. The classic wins are on centrifugal equipment: supply and exhaust fans, cooling-tower fans, boiler-feedwater pumps, circulation pumps, and HVAC air handlers, where the affinity-law cube turns a modest speed cut into a large power cut. But the reach is wider than energy. Conveyors use drives to ramp product gently and to synchronize line speed. Mixers and agitators use them to dial in shear. Centrifuges, extruders, spindles, and winders use them for precise, repeatable speed control that a fixed-speed motor simply cannot deliver.
There is also a process-quality argument that has nothing to do with the power bill. A drive lets a filling line creep to a stop and ramp back cleanly instead of slamming on and off, which reduces spillage, product damage, and mechanical shock through the whole drivetrain. Softer starts mean less wear on belts, chains, couplings, and gearboxes, the drive protects everything downstream of the motor, not just the motor. On many lines that reduction in mechanical stress justifies the drive before a single kilowatt-hour is counted.
What are the most common VFD faults?
Drives fail in a small number of recognizable ways, and the drive usually tells you which one. The most frequent trip codes:
| Fault | What it means | Usual cause |
|---|---|---|
| Overcurrent (OC) | Output current exceeded the trip limit | Jam, seized bearing, short, accel ramp too fast |
| Overvoltage (OV) | DC bus voltage climbed too high | Decel too fast, regenerating load, no brake resistor |
| Undervoltage (UV) | DC bus voltage sagged too low | Line dip, loose input connection, brownout |
| Overtemperature (OT) | Heatsink or IGBT too hot | Clogged filter, dead cooling fan, dusty cabinet |
| Ground fault (GF) | Current leaking to ground | Motor winding breakdown, damaged cable insulation |
| Overload (OL) | Sustained current above motor rating | Oversized load, mechanical binding, wrong sizing |
Two failure patterns dominate the physical hardware: DC bus capacitors dry out and lose capacitance over years of heat cycling, and cooling fans clog or seize, which is why overtemperature trips are so common in dusty plants. Neither is mysterious. Both are predictable if someone is watching the numbers the drive already publishes.
The pattern most worth internalizing is that a trip is rarely the drive's fault, it is usually the drive protecting itself and the motor from something happening in the mechanical system around it. An overcurrent trip on a conveyor is often a jam; a ground fault is often a motor winding finally breaking down after months of insulation stress; repeated overtemperature is often a filter nobody has cleaned. Reading the fault code tells you what tripped; reading the trend of current and temperature in the hours before the trip usually tells you why, and gives you the chance to fix it on your schedule instead of at 2 a.m. when the line is down.
Why is drive data worth capturing?
Because a VFD is already a high-resolution sensor bolted to your motor. To do its job it continuously measures output current, output frequency, DC bus voltage, motor load percentage, heatsink temperature, run hours, and every fault it has ever thrown. That is a rich, free signal for predictive maintenance a slow creep in running current at the same load points to a fouling impeller or a tightening bearing long before it trips, and it is the same physics that motor current signature analysis uses to find broken rotor bars and misalignment.
The problem is that on most floors this data lives and dies inside the drive's keypad. Reading it out, through the drive's communication port into a monitoring layer, turns a reactive component into a leading indicator. It is the same move behind any good IIoT retrofit: the sensor is already installed and already measuring, so the cheapest win is simply to read what it knows. That is where a layer like Harmony starts, pulling drive, PLC, and sensor signals the plant already owns into one real-time picture, computing true machine health above the control layer without touching how the drive runs the motor. No rip-and-replace (connected systems module).
How do you scope a VFD retrofit?
A drive is only a good investment when the load and the duty cycle justify it. Work through it in order:
- Confirm the load type. Centrifugal pump or fan (variable torque) is the home run because of the affinity-law cube. Conveyors and positive-displacement pumps (constant torque) still benefit, but justify them on control and soft-start, not cubic energy savings.
- Measure the real duty cycle. A motor already running at full speed 100% of the time saves nothing. The prize is in loads that spend hours throttled, dampered fans, valved pumps, oversized systems that were specified for a peak that rarely happens.
- Size the drive to the motor, not the nameplate horsepower alone. Match voltage, full-load amps, and service factor. Undersizing causes nuisance overcurrent trips; oversizing wastes money and can weaken motor protection.
- Plan for the electrical side effects. PWM output can stress motor insulation and bearings (shaft currents), and drives inject harmonics back onto the line. Inverter-duty motors, output reactors or dV/dt filters, shaft grounding rings, and line reactors exist for exactly these reasons.
- Wire in the data from day one. Commission the communication port and log current, DC bus, temperature, and faults from the start. Retrofitting monitoring later costs more than doing it at install, and the baseline you capture on day one is what makes every later trend readable.
Numbers worth knowing
A few figures anchor the VFD business case, each from a primary source.
- ~70% of industrial electricity is consumed by electric motor systems, which is why motor efficiency dominates industrial energy strategy (U.S. Department of Energy).
- Power scales with the cube of speed on centrifugal loads (the affinity laws): a 20% speed reduction cuts power draw by roughly 49%.
- Up to ~50% energy savings are achievable on variable-torque applications like pumps and fans with variable-speed control (U.S. Department of Energy).
- ~2-3% internal loss in the drive itself, the small overhead you pay for the ability to vary speed.
- Constant volts-per-hertz is the control law that lets the motor keep rated torque as frequency drops, so it slows without stalling.
A VFD is one of the rare upgrades that pays back twice: once on the utility bill, and again as a stream of machine-health data you were not collecting before. For where that data belongs, see machine monitoring and the wider smart factory stack; to keep the motor itself healthy underneath the drive, start with electric motor maintenance. And if the drive is throwing faults you cannot explain, the panel next to it is usually the HMI showing why.