Choosing a motor for a robot is a system decision. The actuator must deliver the required torque and speed through a transmission, fit the available package, reject disturbances, survive impacts and stalls, and remain controllable from the available power source. “DC motor” alone does not answer those questions.
Brushed DC and brushless DC motors are both useful in robotics. The better choice depends on the joint or mechanism, duty cycle, feedback, motion quality, maintenance target, safety behavior and cost of the complete drive.
Define the motion before choosing the motor
Start with the load at the output, then work backward through the mechanism and transmission. Useful inputs include:
- continuous, intermittent and peak output torque;
- maximum speed and required acceleration;
- reflected inertia, friction, gravity load and external disturbances;
- gear ratio, efficiency, compliance, backlash and backdrivability;
- position, speed and torque accuracy;
- duty cycle, ambient temperature and cooling path;
- bus voltage, battery impedance and regenerative energy;
- allowable mass, diameter, length and cable routing;
- stall, collision, emergency-stop and power-loss behavior.
A motor that looks adequate at nominal torque can fail the application because of acceleration current, gearbox loss, thermal accumulation, bus droop or an unfavorable torque-speed operating point.
Brushed DC, BLDC and servo are different categories
A brushed DC motor uses brushes and a commutator to switch armature current. A brushless DC motor uses electronic commutation and generally a three-phase inverter. Either can be used in a servo system. Servo describes a closed-loop function—usually controlling torque, speed or position—not a single motor construction.
| Architecture | Useful characteristics | Engineering constraints |
|---|---|---|
| Brushed DC + H-bridge | Simple torque direction and voltage control; straightforward current loop; economical for modest mechanisms | Brush wear, commutator behavior, debris, arcing and maintenance |
| BLDC + six-step | Electronic commutation with moderate computation; good fit for many speed-controlled axes and auxiliary mechanisms | Commutation ripple, rotor sector feedback or sensorless startup, three-phase inverter |
| BLDC/PMSM + FOC | Smooth torque, precise current control and a strong foundation for velocity/position loops | Accurate current/angle feedback, deterministic firmware, commissioning and motor parameters |
Microchip’s BLDC architecture overview separates motor construction from commutation and feedback choices. That distinction is especially important in robotics, where the same motor can behave very differently under six-step and field-oriented control.
Convert output requirements to motor requirements
Torque and speed through the transmission
For a first-order estimate, output torque is motor torque multiplied by gear ratio and transmission efficiency. Output speed is motor speed divided by gear ratio. The simple equations are useful, but gearbox efficiency varies with load, direction, speed, lubrication and temperature. Breakaway friction and back-driving can differ from steady operation.
Reflected inertia changes approximately with the square of gear ratio. Increasing ratio can reduce motor torque demand while making the load appear dynamically different to the controller. High ratio may also add backlash, compliance and friction that limit position bandwidth or force sensitivity.
Peak current is part of the motion profile
Motor torque is related to current over the useful operating region. Acceleration, gravity compensation, contact forces and shock recovery can therefore create current peaks well above the continuous value. The motor winding, connector, cable, current sensor, MOSFETs, shunt, gate driver, DC link and source must tolerate the same transient.
Peak current ratings must include time and thermal conditions. A one-second acceleration, repeated every few seconds, can be more demanding than an isolated peak even when each event stays below a data-sheet limit.
Back EMF limits high-speed torque
As speed rises, the motor generates back EMF that opposes the applied voltage. Winding resistance, inverter drop, bus sag and modulation margin reduce the voltage available to force current. The drive should be evaluated on a torque-speed envelope at minimum bus voltage and worst-case temperature, not only at the motor’s no-load speed.
Feedback should match what the robot must know
Hall sensors can provide commutation sectors and coarse speed information. Incremental encoders can support velocity and relative position after an index or homing operation. Absolute encoders can provide position immediately at power-up. Resolvers may suit harsh environments. Current sensing supports torque estimation and protection but does not replace output-side sensing when gearbox compliance, backlash or slip matters.
Mounting the sensor at the motor shaft simplifies packaging and gives high apparent resolution after gearing. Mounting at the output measures the joint more directly. Some robots use both to observe transmission deflection or improve force control. The choice affects homing, calibration, safety diagnostics and cable design.
Control structure for a robotic axis
A high-performance axis often uses nested loops:
- a fast current loop regulates motor torque-producing current;
- a velocity loop commands current or torque;
- a position loop commands velocity or torque;
- a trajectory generator limits position, velocity, acceleration and sometimes jerk.
The loop rates and bandwidths should be separated enough to avoid interaction. Mechanical resonance, flexible links, gearbox compliance and sensor filtering limit achievable bandwidth. Controller tuning on a free motor does not validate the assembled robot.
FOC can provide smooth current-vector control for a permanent-magnet motor. Six-step can be sufficient where motion and acoustic requirements are less demanding. The separate guide to FOC versus six-step BLDC control explains the architecture tradeoffs.
Power, braking and regeneration
A robot can drive energy back into the DC bus while decelerating, lowering a gravity load or being pushed externally. A battery may absorb some energy within charging limits. A bench supply may not. A shared DC bus can transfer energy between axes, but the controller still needs an overvoltage strategy.
Possible system measures include a braking resistor and chopper, controlled deceleration limits, battery-management coordination, bus capacitance and a supply designed for bidirectional power. The correct choice depends on the energy and repetition rate. Treat regeneration as an operating mode, not an exceptional fault.
Safety and fault behavior
Robotic actuators can store electrical, kinetic, elastic and gravitational energy. The motor drive should have defined behavior for:
- blocked rotor and sustained stall;
- unexpected contact or collision;
- encoder disagreement, implausible velocity and lost feedback;
- open phase, phase short and current-sensor fault;
- overcurrent, overtemperature, bus under/overvoltage and watchdog reset;
- loss of communication or supervisory command;
- emergency stop, brake engagement and power removal.
Software current limits are useful for normal operation. Fast hardware protection is still needed when a switching or short-circuit event can damage the inverter before the control loop responds.
Thermal design is a duty-cycle calculation
Motor copper loss grows with the square of RMS current. Winding resistance rises with temperature. Inverter conduction loss, switching loss, gear loss and nearby heat sources add to the assembly. A compact joint can have an efficient motor and still overheat because the enclosure provides a poor thermal path.
Build a duty-cycle profile, estimate losses at each segment and validate temperatures at the winding, power semiconductors, PCB, connector and enclosure. Include repeated acceleration and holding torque, not only continuous rotation.
Bench validation for a robotic actuator
- measure torque and speed through the real transmission;
- run representative trajectories with payload and inertia extremes;
- verify current, bus voltage and regeneration during acceleration and braking;
- measure tracking error, settling, overshoot, backlash and resonance;
- test startup, homing and recovery from interrupted motion;
- record motor, inverter and enclosure temperature over the full duty cycle;
- test stall, collision and feedback faults with safe fixtures;
- evaluate emissions and immunity with production cables and grounding.
A better motor-selection question
The right question is not whether DC motors are “great for robotics.” It is which motor, transmission, feedback, power stage and control architecture meets the robot’s defined motion and safety behavior. Brushed DC can be ideal for a simple intermittent mechanism. BLDC with FOC may be justified for a quiet, precise joint. Six-step may fit an auxiliary axis. Each is a defensible choice when the complete system is engineered and verified.
Outer Reef develops custom motor controls and multidisciplinary robotics engineering systems around the load, mechanics, electronics, firmware and verification plan.
