+1-866-7SMARTD (1-866-776-2783)
SmartD News
One VFD for multiple motors: Simplicity Has a Price
Why Run Multiple Motors on One VFD?
At first, the idea looks obvious.
Several motors must run at the same speed. So why install several variable frequency drives when you can run multiple motors on one VFD?
One drive means fewer components, less wiring, less panel space, less heat, and a simpler speed-control strategy. There is one run command, one speed reference, and one system to commission.
Technically, it can be an efficient and elegant architecture. But the real engineering question is not whether one VFD can run several motors.
The real question is this:
What happens to the process when that one VFD is no longer available?
The simplicity that creates dependency
When one VFD feeds several motors, the drive becomes more than a speed controller.
It becomes the single point on which the entire motor group depends. A fault trip stops every motor.
- A hardware failure stops every motor.
- A loss of control power stops every motor.
- A blown upstream fuse stops every motor.
- A communication loss between the PLC and the drive may also stop every motor, depending on the configured communication-loss behavior.
The architecture therefore has an all-or-nothing characteristic:
One drive trip means one complete group stoppage.
This is the trade-off.
You gain simplicity and reduce installed cost, but you also remove fault isolation.
With one VFD per motor, the loss of one drive normally removes only one motor from service. The process may continue at reduced capacity. With one VFD for the complete group, the same type of failure can create a total outage.
The difference is not simply electrical. It is operational.
Availability belongs to the complete drive chain
The availability of the system is only as good as the availability of the shared drive chain:
Line power → upstream protection → VFD → output switching devices → motors
Every motor depends on that same path. This changes how downtime must be considered.
The mean time to repair of the VFD does not apply to one motor. It applies to the whole group.
If replacing or repairing the drive takes four hours, then the complete group may be unavailable for four hours.
This is why a shared-drive architecture cannot be justified only by comparing purchase prices.
The engineering decision must also consider:
the cost of a full-group shutdown;
the time required to diagnose the failure;
the availability of a replacement drive;
the time required to load the correct parameters;
the ability of the process to stop and restart safely;
and the consequences if recovery takes longer than expected.
The important question is not, “How often will the drive fail?”
It is: “What will happen when it does?”
Switching motors is not an ordinary contactor operation
A second technical issue appears when motors are added to or removed from a group while connected to the output of a VFD.
A VFD output is not the same as utility power.
It is an actively controlled power-electronic output.
Opening or closing motor contactors while the drive is producing voltage can create current transients, DC-bus disturbances, nuisance trips, and stress on the output power stage.
The safe sequence is therefore deliberate:
Stop → Disable → Connect or disconnect → Restart
First, command the drive to stop.
Then wait until the motor group is confirmed stopped and the drive is no longer producing output.
Next, apply the Motor Disable function—or another approved safe-to-switch output condition—before operating the motor contactors.
Only after the output is disabled should a motor be connected to or disconnected from the group.
Then the drive can be re-enabled and the complete group restarted.
This sequence prevents contactor switching under drive power.
The result is fewer nuisance trips, lower stress on the output stage, and a repeatable method that can be documented and approved.
Why restart strategy matters
When several motors are connected to one drive, they may not all be at exactly the same mechanical state when the group restarts.
One shaft may still be rotating.
Another may have stopped.
A fan may be windmilling because of airflow.
A pump may be turning because of process flow.
A conventional flying-start or speed-search function may attempt to detect the speed of the connected load. But with several motors turning at different speeds—or in different conditions—the drive does not see one clean rotating machine.
It sees a combined electrical response.
This can lead to a false catch, unstable detection, high current, or DC-bus overvoltage.
For large parallel-motor groups, a controlled pre-magnetization or constant-time start is often more predictable.
Instead of trying to identify one existing shaft speed across several different motors, the drive establishes the motor flux and applies a known acceleration profile to the complete group.
The result is a smoother current ramp, fewer overcurrent or overvoltage trips, and cleaner synchronization of the motors.
Predictability matters more than cleverness.
A restart method that behaves the same way every time is easier to commission, troubleshoot, and approve.
When One VFD for Multiple Motors Is Reasonable
A single VFD for several motors can be a reasonable choice when the process can safely tolerate a complete stop.
This may be the case for non-critical ventilation, non-continuous pumping, or another application where a short interruption does not create a safety hazard, product loss, equipment damage, or environmental risk.
It can also be justified when cost, available panel space, and system simplicity clearly outweigh the consequence of a temporary full-group outage.
The architecture becomes even more logical when all motors:
operate with the same speed profile;
start and stop as one functional group;
do not require independent speed control;
and do not need to remain operational individually when another motor is unavailable.
In these conditions, one VFD is not necessarily an unacceptable compromise.
It is a conscious system-level decision.
But it should only be made when the operator can tolerate the outage and when a fast recovery plan exists.
When one drive is not enough
Some processes cannot accept the all-or-nothing behavior of a shared VFD.
Life-safety and mission-critical services are the clearest examples.
Smoke-control fans, essential cooling systems, critical wastewater lift stations without sufficient storage, and continuous production processes may need to remain operational even when one component fails.
In these applications, a single shared drive may create too large a failure consequence.
The same applies when motors require independent control or protection.
Although several motors may be connected to one VFD, each motor still requires its own overload protection. The VFD sees the total group current. It does not automatically know whether one individual motor is overloaded, mechanically blocked, or operating abnormally.
If individual operating decisions are required, individual drives—or another form of redundancy—may be the more responsible architecture.
How to Reduce the Single-Point-of-Failure Risk
There is not always a binary choice between one drive and one drive per motor.
The group can be divided.
For example, instead of one VFD supplying six motors, two VFDs can each supply three motors.
This increases cost compared with a single-drive architecture, but it limits the failure consequence. One trip removes half the capacity instead of the complete process.
In reliability engineering, this is sometimes described as limiting the blast radius.
The objective is not to eliminate every possible failure.
The objective is to prevent one failure from becoming a complete system failure.
Recovery must be designed before the failure
If one VFD is still the preferred architecture, the recovery strategy should not be improvised after the trip.
It should be designed, documented, and tested in advance.
A pre-programmed spare VFD can significantly reduce downtime. But keeping a spare drive on a shelf is not enough.
The spare should be compatible with the installed unit. A current parameter file should be available. The required cables, connectors, tools, and quick-disconnect hardware should be identified. The person responsible for the swap should know the procedure.
A replacement-time objective should also be defined.
For example: “In the event of a VFD failure, the complete drive shall be replaced and returned to service in less than 60 minutes.”
This statement turns a vague recovery intention into an operational requirement.
A fixed-speed bypass may also be considered when variable-speed operation is temporarily non-essential. An across-the-line bypass can provide a fallback path, but it changes the motor starting conditions, available protection, process control, and energy consumption.
The bypass is not simply a second way to energize the motor.
It is another operating mode that must be engineered.
The documentation should state when bypass operation is permitted, what process performance is lost, and which protections remain active.
Buffered or uninterruptible control power may also protect the VFD electronics and PLC I/O from brief power disturbances. This does not solve every power failure, but it may prevent avoidable shutdowns caused by short control-power interruptions.
Condition monitoring can reduce surprise failures as well.
Drive temperature, cooling-fan condition, DC-bus behavior, overload trends, and other diagnostic indicators can reveal degradation before it becomes a trip.
The purpose of these alarms is not to generate more information. It is to create enough warning to act before the entire group stops.
What the Clean Power VFD changes
The reliability trade-off of one shared drive still exists when using the Clean Power VFD.
It does not remove the single point of failure. But it changes several other technical aspects of the installation.
The Clean Power VFD supplies a sine-wave output to the motors without requiring an external sine-wave or dV/dt filter.
In a conventional VFD installation, parallel motor cables and multiple cable drops can increase cable-charging current, reflected-wave effects, common-mode stress, and electromagnetic interference.
External output filters are often added to manage these effects. But filters bring their own consequences:
additrional power losses;
additional heat;
more panel space;
added wiring;
more components to maintain;
and another element that can fail.
With the Clean Power VFD, the sine-wave output removes the need for these external filters in the intended application. The result is a simpler bill of materials, lower panel heat, and fewer components between the drive and the motors.
Better conditions for motors and cables
Parallel motor installations can be demanding for motor insulation, bearings, and cables.
Fast voltage transitions increase turn-to-turn insulation stress. Common-mode voltage contributes to bearing-current activity. Long cable runs and multiple branches increase capacitive effects.
A clean sine-wave output reduces these stresses at their source.
Low dV/dt reduces insulation stress.
Lower common-mode voltage reduces the electrical conditions that contribute to bearing distress.
A cleaner waveform also reduces cable-charging concerns, which is particularly useful when the installation includes several cable drops or long distances between the drive and the motors.
The practical result is not simply a better-looking waveform.
It is a more motor-friendly and cable-friendly electrical environment.
That can mean longer motor life, fewer bearing-related surprises, and fewer unexplained problems appearing months after commissioning.
Cleaner power around the system
The Clean Power VFD also addresses the input side of the installation.
Its ultra-low input harmonics reduce distortion injected into the upstream electrical system.
At the output, the sine-wave voltage reduces the high-frequency electrical noise normally associated with conventional PWM drive outputs.
For a parallel-motor installation, this is particularly useful because several outgoing cables can otherwise behave like several paths for high-frequency common-mode current and interference.
A cleaner electrical environment can reduce EMI and RFI problems around controls, sensors, communication networks, and grounding systems.
It can also reduce the conditions that contribute to nuisance operation of residual-current or ground-fault protection devices, provided that the complete protection scheme is correctly engineered.
The result is a quieter electrical system—not acoustically, but electrically.
And electrically quiet systems are generally easier to commission and easier to troubleshoot.
The economic reason remains valid
Using one drive for several common-speed motors can significantly reduce installed cost.
There are fewer drives, fewer upstream protective devices, fewer control interfaces, and less heat to remove from the enclosure.
The panel can be smaller.
Commissioning can be faster.
Spare-part management can be simpler.
One analog speed reference and one run/stop path can control the complete array.
This reduces coordination errors when motors are staged into or out of the group.
But the economic benefit is valid only when the reliability consequence is acknowledged.
A lower initial cost is not a saving if the first full-group outage creates a larger operational loss than the equipment cost that was avoided.
The architecture must therefore be evaluated over the complete system lifecycle—not only at purchase.
Safety behavior must be auditable
A good motor-switching sequence should not depend on operator intuition.
It should be possible to describe it, test it, and verify it.
The Motor Disable function provides a positive no-output condition before switching the output contactors.
This creates a sequence that can be included in the control narrative, functional test, commissioning procedure, and operating instructions.
The owner, engineer, and authority having jurisdiction should be able to confirm:
what initiates the stop;
how stopped status is verified;
how output disable is confirmed;
when contactor operation is permitted;
what prevents switching under power;
and what conditions are required before restart.
Safety is not created because a sequence appears logical. Safety is created when the sequence is explicit, controlled, and repeatable.
What should be documented
The design documentation should state the dependency clearly:
“One VFD controls Motors M1 through M4. Any outage of the VFD or its common supply path stops all four motors.”
This single sentence prevents the system architecture from being misunderstood later.
The recovery plan should identify:
whether a spare drive is stored on site;
where the current parameter backup is maintained;
who is authorized to replace the drive;
the target swap time;
the required tools and parts;
and how correct operation is verified after replacement.
The documentation should also define the operating limits of any bypass mode, including the performance and protection functions that are lost.
Finally, change control should include periodic functional tests, parameter backups, drive firmware versions, spare-drive verification, and records of any modification to the motor group.
A recovery plan that has never been tested is only an assumption.
The decision
One VFD running several motors can be a technically sound architecture.
It can provide lower installed cost, a smaller footprint, simpler controls, clean common-speed operation, and—when combined with the Clean Power VFD—a filter-less sine-wave output that is friendly to motors, bearings, and cables.
But these benefits do not remove the central fact:
The complete motor group depends on one drive.
That is not automatically a design flaw. It is a risk decision.
When the process can tolerate a full-group stop, when the motors share the same operating profile, when switching is performed through a controlled Stop → Disable → Connect → Restart sequence, and when a practiced recovery plan exists, the architecture may be fully justified.
When the process cannot tolerate that outage, the answer is not to hide the dependency behind optimistic reliability assumptions.
The answer is to change the architecture.
Use more than one VFD.
Split the motor group.
Add a properly engineered bypass.
Or introduce redundancy.
Because good engineering is not only about making the system work efficiently when everything is normal.
It is also about deciding, in advance, how the system must behave when something is not.
Ready to run multiple motors on one VFD?
The architecture may be simple, but its implementation must be deliberate.
Application Note AN009 — Running Several Motors in Parallel on One VFD explains how to size and protect the motors, switch motors safely, manage starting and restarting, and implement the correct Stop → Disable → Connect → Restart sequence with the Clean Power VFD.
Use it to turn the design principles described above into a controlled, documented, and repeatable installation.
Cette publication est également disponible en :
