Automation Fundamentals
One Drive or Many Drives?
Compare centralized motion and distributed actuators.
A real system shows a symptom related to “One Drive or Many Drives?”, and you need to find the cause before replacing parts or changing settings.
Compare a central drive, several coordinated actuators and mixed driven/passive support by tracing load sharing, stiffness, feedback, wiring, synchronization, fault behavior and maintenance across the complete machine.
- Select or check first
- Distributed actuators do not automatically provide redundancy. If one actuator stops while others continue, a shared structure can twist, bind or overload. Redundancy requires an explicit failure analysis, remaining capacity, fault detection, communication behavior and a safe coordinated response.
- Controlling assumption
- Sensors, controller logic, actuator limits, timing, fault response and environmental conditions are defined together.
- Top risk
- Never commission coupled axes as independent machines. Before energizing, verify mechanical freedom, direction, feedback polarity, travel margin and low-force/current limits for each axis. Then test coordinated motion at reduced speed and load while monitoring skew.
- Proof
- Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test.
Start with the basics Optional foundation before “One Drive or Many Drives?”
Automation-and-control basics
An automatic system measures a condition, decides what it means and commands an actuator while checking whether the expected result actually happened.
- Sensor
- A sensor converts a physical condition into a signal. Its range, uncertainty, response time, environment and failure behaviour matter as much as its nominal output.
- Controller
- A controller reads inputs, applies logic or a control law and issues outputs. Software cannot correct missing measurements, inadequate hardware authority or unsafe architecture.
- Actuator
- An actuator turns a command into physical action, such as motor torque, valve position or switching. Its real limits depend on load, supply, drive and duty.
- Feedback
- Feedback compares measured behaviour with the desired state so error can be corrected. Open-loop command assumes the action occurred; closed-loop control checks it.
- Fault and safe state
- A fault is an abnormal condition that may invalidate control. The safe response must be defined from the hazard and may require independent hardware, not only software.
How to use this article: Trace one complete chain—physical condition, sensor, signal conditioning, controller, drive, actuator and feedback—then ask how each link can fail.
On this page
A wide moving structure can be driven from one point, from several points, or from a mixture of driven and passive supports. The number of motors is only the visible difference. The real architecture includes shafts or linkages, bearings, frames, drives, power distribution, communication, feedback, stopping devices and service access. The best arrangement keeps deformation and coordination within verified limits through normal motion, disturbance and faults.
Three arrangements move loads through different paths
Diagram description
The illustration is qualitative. It does not establish actuator quantity, structural capacity, synchronization performance, redundancy, cost or suitability for a particular tracker.
| Question | Central drive | Distributed drives | Mixed driven/passive |
|---|---|---|---|
| Mechanical load path | Torque/force travels through a common structure or transmission | Loads enter near several support points | Driven points move a structure carried by passive guides/supports |
| Coordination | Mostly mechanical, though torsion and backlash remain | Electronic and mechanical synchronization are both required | Driven points must not fight support friction or compliance |
| Power wiring | Concentrated drive with longer mechanical transmission or motor cables | Power and communication distributed across the machine | Intermediate complexity |
| Feedback | One sensor may not reveal distant twist | Per-axis feedback can reveal skew if the load coordinate is measured | Feedback placement must cover driven and passive behavior |
| Single fault | Can stop the whole machine | A failed axis may rack the structure unless coordinated response is designed | A jammed passive support can overload driven points |
| Service | Fewer drive units but potentially large central components | More replaceable units, addresses and connectors | Both actuator and guide maintenance are needed |
Start with the structure and load-sharing tolerance
Illustrative position skew
Δx = x_1 − x_2
The allowable magnitude of skew must come from structural analysis, bearing/guide tolerance and load requirements. Equal motor commands do not guarantee equal x values: friction, backlash, compliance, sensor error and unequal loads can separate them. For a flexible beam, local deflection between sensors may also matter, so this two-point quantity is not a complete structural model.
- Δx
- relative travel or angular-coordinate difference
- x_1
- position measured at driven/support point 1
- x_2
- position measured at driven/support point 2
| Question | Why it changes the architecture |
|---|---|
| How stiff is the structure in torsion and bending? | Determines how far one drive can be from the controlled load and how skew propagates |
| Can guides tolerate misalignment? | Parallel actuators may bind before sensors report a large error |
| Does gravity or wind load supports unequally? | Nominal equal sharing may disappear across orientation and weather |
| Can the transmission back-drive? | A powered-off axis may move, hold or resist the others differently |
| Where are hard stops? | Unsynchronized arrival can concentrate load at one point |
| What happens after a broken coupling or jam? | Determines sensors, independent limits and stop strategy |
Distribute hardware only with a defined coordination contract
Siemens documents both centralized and distributed motion-control architectures and supports synchronized operation across controllers over an industrial network. That proves such architectures are technically available; it does not make network timing irrelevant. A production design declares update periods, synchronization method, maximum data age, allowed position disagreement, clock behavior, communication-loss response and which controller owns the coordinated stop.
| Layer | Design decision | Evidence |
|---|---|---|
| Trajectory | Common position profile or individual commands | Bounded velocity, acceleration and jerk for every axis |
| Time | Synchronized clocks/cycle or tolerated asynchrony | Measured command and feedback timing under network load |
| Feedback | Motor, actuator or load position | Calibrated agreement with the structural coordinate |
| Cross-coupling | How skew modifies each axis command | Stable response across stiffness, load and backlash range |
| Fault | Stop all, controlled recovery or limited degraded mode | Injected sensor, drive and network faults |
| Safety | Independent risk-reduction functions | Required performance and validation—not ordinary synchronization alone |
Cable savings can move complexity into field devices
A distributed converter near a motor can shorten individual motor cables and move heat or cabinet space into the field. It also adds environmental exposure, connectors, address/configuration management and service locations. Manufacturer claims such as a particular percentage of cable savings apply to stated product comparisons, not to every machine. Compare a real bill of materials and cable schedule, including mains distribution, network, feedback, safety circuits, grounding, isolation and spare strategy.
| Record | Central question |
|---|---|
| Load cases | Which support carries what force/torque in every orientation and fault? |
| Component count | How many motors, drives, brakes, sensors, cables and connectors? |
| Commissioning | How are axis identity, direction, zero and skew verified? |
| Diagnostics | Can maintenance distinguish drive, sensor, network and mechanical jam? |
| Replacement | Can one unit be replaced without unsafe movement or hidden parameter mismatch? |
| Recovery | How is position re-established after a partial power or communication loss? |
| Spares and access | Are field devices safely reachable and compatible through product life? |
Frame the useful motion requirement first in Where Automatic Positioning Is Useful, then decide what each loop really measures in Open-Loop Commands Versus Real Feedback. Mechanical life and load verification are treated in Lifetime and Safety Checks for a Motion Axis.
Selection boundary and evidence to keep with the decision
Treat “One Drive or Many Drives?” as a selection problem, not only a definition. Record the required result, alternatives considered, the controlling assumption and the condition that would change the choice.
Keep evidence proportional to consequence: Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test. Revisit the decision when the load, environment, duty, interface, regulation or maintenance plan changes.
One-minute questions
Questions to answer before you apply this lesson
What should I select or check first for One Drive or Many Drives?
Distributed actuators do not automatically provide redundancy. If one actuator stops while others continue, a shared structure can twist, bind or overload. Redundancy requires an explicit failure analysis, remaining capacity, fault detection, communication behavior and a safe coordinated response.
Which assumption can change the conclusion?
Sensors, controller logic, actuator limits, timing, fault response and environmental conditions are defined together.
What can go wrong if I copy the example directly?
Never commission coupled axes as independent machines. Before energizing, verify mechanical freedom, direction, feedback polarity, travel margin and low-force/current limits for each axis. Then test coordinated motion at reduced speed and load while monitoring skew.
How do I verify the result in the real system?
Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test.
Sources and further reading
- Motion Control Architectures with SIMOTION and SINAMICSSiemens · 2026-10-13Manufacturer catalogue reviewed for centralized, decentralized and distributed synchronous motion-control architectures over PROFINET.
- Distributed Frequency ConvertersSiemens · 2026-10-13Manufacturer product guidance reviewed for near-motor converter placement, cable, environmental and application context; promotional savings were not generalized.