Brushed vs Brushless DC Motors for Mobile Robots: Torque, Efficiency and Control
Tom Cosgrove,
TL;DR: The brushed vs brushless DC motor choice for a robot comes down to four practical variables: control complexity, continuous torque per unit mass, efficiency under partial load, and maintenance interval. Brushed motors commute mechanically through carbon brushes and a commutator, so they run from a simple H-bridge and two power wires. Brushless (BLDC/PMSM) motors commute electronically, which requires a three-phase inverter and either rotor position feedback or sensorless position estimation, but removes the main wear item and typically delivers higher efficiency and better thermal behavior. For small indoor or educational UGVs with modest duty cycles, a brushed gearmotor is often the pragmatic answer. For long-duration field robotics, heavy payloads, or precise low-speed motion, brushless with field-oriented control (FOC) often wins. This article explains the mechanisms, the tradeoffs, and how each choice propagates into runtime and terrain behavior.
Why does the brushed vs brushless DC motor decision matter for a robot drivetrain?
Motor selection is one of the few hardware decisions that is difficult to change mid-project. It determines your power electronics, your wiring harness, your encoder strategy, your thermal budget, and the shape of your ROS 2 control stack. Changing from brushed to brushless after the chassis is built means replacing motor controllers, re-tuning the velocity loop, and often redesigning the drive module mounting.
The brushed vs brushless DC motor question is frequently framed as “which is better.” That framing is not useful. In the permanent-magnet motor types commonly used in mobile robots, both follow the same fundamental relationships: torque is proportional to current, back-EMF is proportional to speed, and the mechanical power you extract equals electrical power minus copper, iron, friction, and other losses. What differs is how commutation happens – and commutation method cascades into everything else.
In a brushed motor, the stator holds permanent magnets and the rotor carries the windings. Current reaches the rotating windings through carbon brushes sliding on a segmented commutator. The commutator mechanically switches current direction as the rotor turns, keeping torque roughly unidirectional. No electronics are required for commutation itself.
In a brushless motor, the arrangement inverts: permanent magnets sit on the rotor, windings sit on the stator, and an external controller energizes the three phases in sequence. The controller must know or estimate rotor angle to decide which phases to drive. That information can come from Hall sensors, an encoder, a magnetic angle sensor, or sensorless back-EMF estimation.
What this means physically
Because brushed rotors carry windings, they often have higher rotor inertia and the windings are thermally isolated in the middle of the machine, surrounded by air and magnets. Heat generated in the copper has a poor path to the housing. Brushless motors put the copper on the stator, bonded close to the outer case, which is typically the robot’s heat sink. That geometric difference often explains much of the continuous-torque advantage of BLDC machines at comparable size.
How do torque, efficiency and lifetime compare in practice?
The table below summarizes the engineering tradeoffs. Treat the numeric ranges as typical values for small mobile robot drive motors in roughly the 10 W to 500 W class, drawn from general manufacturer datasheet ranges rather than a single measured sample. Actual figures vary enormously by winding, magnet grade, controller, and gearbox.
| Criterion | Brushed DC | Brushless DC (BLDC / PMSM) |
|---|---|---|
| Peak torque | High for short bursts; limited by allowable current, commutation, and thermal or demagnetization limits | High; limited mainly by inverter current rating, winding temperature, and magnet temperature |
| Continuous torque per mass | Lower – rotor copper is hard to cool | Typically higher – stator copper conducts heat to the housing |
| Peak efficiency | Approximately 70-90% for quality units at a favorable operating point | Approximately 80-95% at a favorable operating point, depending on the motor and controller |
| Efficiency at partial load | Often degrades noticeably; brush friction and contact drop are significant losses | Often degrades more gracefully; no brush friction or brush-contact loss |
| Wear items | Brushes and commutator; brushes are consumable | Bearings are the principal motor wear item |
| Typical lifetime driver | Brush wear, often rated in hundreds to a few thousand hours depending on duty | Bearing L10 life and magnet thermal aging, typically much longer |
| Control hardware | H-bridge, 2 power wires, PWM duty cycle | Three-phase inverter (ESC), 3 power wires and optional sensor wiring |
| Control algorithm | Open-loop PWM or simple PID on encoder feedback | Six-step trapezoidal or FOC with current loops |
| Position feedback | Optional; only needed for closed-loop velocity or position control | Required for sensored commutation; sensorless control estimates rotor position from electrical measurements |
| Low-speed smoothness | Cogging plus commutator ripple; usable but notchy | Very smooth with FOC; six-step shows torque ripple at low RPM |
| Electrical noise | Significant brush arcing EMI; needs capacitors and shielding | Switching noise from the inverter; manageable with layout and filtering |
| Relative cost (motor + driver) | Lower; drivers are commodity parts | Higher; FOC-capable controllers carry most of the premium |
| Field serviceability | Brushes replaceable on some models; motors are cheap to swap | No brushes to replace, but controller tuning knowledge may be required |
Where the efficiency difference actually shows up
A mobile robot almost never operates at its motor’s rated point. It spends most of its time at partial load, cruising at a fraction of peak torque, with intermittent bursts when climbing or overcoming obstacles. This is often where the brushed vs brushless DC motor gap widens.
Brush friction and the brush contact voltage drop (often on the order of 1-2 V total for carbon brushes, depending on the motor and current) are significant losses that do not scale directly with torque. At low torque demand, those losses consume a growing fraction of input power. A brushless motor has no equivalent brush-contact loss, so its efficiency curve can remain flatter across the operating band.
The practical consequence is runtime. Two robots with the same battery, same mass, and same gear ratio can differ meaningfully in mission duration purely from drivetrain efficiency. The exact figure depends on the duty cycle, so the only honest approach is to measure it on your own platform with your own terrain profile rather than trusting a catalog number.
What does BLDC control actually require?
This is the part that surprises teams migrating from brushed hardware. A brushless motor is not a drop-in replacement; it is a motor plus a control problem.
The control chain, step by step
A field-oriented control loop for a brushless drive motor commonly follows this sequence at a current-control rate often in the 10-30 kHz range:
- Measure or estimate rotor angle. Hall sensors give 60-degree electrical resolution, enough for six-step commutation. A magnetic or incremental encoder, resolver, or sufficiently accurate sensorless estimator can provide the electrical angle needed for FOC.
- Measure phase currents. Usually two of the three phases via shunt resistors or Hall-effect current sensors; the third is inferred from Kirchhoff’s current law.
- Clarke transform. Convert three-phase currents (Ia, Ib, Ic) into a two-axis stationary frame (Iα, Iβ).
- Park transform. Rotate that frame into the rotor reference frame using the measured or estimated angle, producing Id (flux-producing) and Iq (torque-producing) currents.
- Run two PI current loops. Drive Id toward zero (for surface-mount magnet rotors below base speed) and Iq toward the torque command from the outer velocity loop.
- Inverse Park and space vector modulation. Convert the PI outputs back into three-phase duty cycles for the inverter.
- Drive the gates. Six MOSFETs, or in some higher-power systems IGBTs, apply the computed voltages to the motor windings.
Above this sits the outer velocity PID loop, typically running at 100-1000 Hz, which is what your ROS 2 diff_drive_controller or equivalent hardware interface ultimately commands. The velocity command arrives from /cmd_vel, gets split into per-wheel targets by the kinematics, and the motor controller closes the loop locally.
Six-step trapezoidal control skips the transforms entirely: read Hall state, look up which two phases to energize, apply PWM. It is far simpler and runs fine on an 8-bit microcontroller. The cost is torque ripple at the commutation boundaries, which is audible and can be noticeable at low RPM. For a robot that must creep smoothly during a manipulation task or a precision docking maneuver, FOC is worth the complexity.
The brushed control chain by comparison
For brushed motors, the entire chain is: PWM duty cycle into an H-bridge, optional encoder feedback into a single velocity PID. That is it. The commutation is handled by physics inside the motor. This simplicity is a genuine engineering advantage, not a compromise – it means fewer failure modes, easier debugging, and a controller you can build or source for a few dollars.
How does motor choice change runtime and terrain behavior?
Datasheet comparisons are abstract. The brushed vs brushless DC motor decision becomes concrete when you look at how each behaves on real ground.
Stall and obstacle climbing
When a wheel hits a rock or a step edge, the motor approaches stall. Current rises toward the stall value, torque peaks, and nearly all input power becomes heat in the copper.
A brushed motor at stall concentrates that heat in the rotor windings, which have a poor thermal path. Hold stall for tens of seconds and winding insulation can degrade. Worse, high current through a stationary commutator segment pair can concentrate heating and commutation damage in one spot.
A brushless motor under FOC can be current-limited precisely at the controller level, holding a known torque for a thermally permissible duration while heat flows into the stator and out through the case. You can set a hard Iq limit that corresponds approximately to a specific Newton-meter value and monitor temperature or thermal limits. That predictability matters for autonomous operation where no human is watching the ammeter.
Regenerative braking and slope descent
A three-phase inverter can support bidirectional power flow when its controller, battery, and protection circuitry are designed to accept regeneration. Descending a slope, a BLDC drive can then push current back into the battery rather than dissipating it as heat. The recovered energy is modest for a small UGV, but the thermal and brake-wear benefit can be real. Brushed H-bridges can also regenerate, though many low-cost drivers lack proper handling for the resulting bus voltage rise.
Encoders and odometry quality
Odometry quality depends on encoder resolution relative to wheel circumference, not on the commutation method. Brushless drives may include Hall sensors or high-resolution magnetic encoders for control, but Hall sensors alone are often too coarse for accurate odometry. On a brushed drive you must specify and mount the encoder deliberately, which is an extra integration step but also an extra degree of design freedom.
On skid-steer platforms like the Leo Rover, wheel slip dominates odometry error regardless of encoder quality, so pairing wheel encoders with an IMU and fusing them in robot_localization matters far more than counts per revolution.
When should you pick each type?
The honest framing is situational fit, not superiority. Consider the following signals when weighing brushed vs brushless DC motor options for your robot:
- Lean brushed when: duty cycle is intermittent, the platform is lightweight, budget is constrained, the team lacks motor control expertise, or the robot is a teaching and prototyping tool where simplicity accelerates iteration.
- Lean brushless when: the robot runs multi-hour missions, carries significant payload, must operate unattended in the field, needs smooth low-speed motion, or operates in dusty and humid environments where brush dust and arcing are liabilities.
- Either works when: the platform is a mid-size research UGV with moderate duty and you already have a validated controller for one type. In that case, integration maturity beats theoretical efficiency.
One nuance worth stating plainly: a well-matched brushed gearmotor with a good gearbox will outperform a poorly tuned brushless drive with a bad controller. The gearbox ratio, wheel diameter, and thermal design frequently matter more than the commutation method. Fictionlab’s team sees this regularly during platform integration work – teams chase motor technology when the actual bottleneck is gear ratio selection or an undersized battery.
Gearboxes change the equation
Brushless motors are often designed for higher speeds, which can mean a higher reduction ratio to reach the same wheel RPM. However, required reduction depends on the specific motor winding, supply voltage, wheel speed target, and gearbox design. Higher reduction adds gear losses, backlash, and cost. Factor the complete drive module efficiency, not just the motor, when comparing.
For platforms where the drive module must be specified around a particular payload, terrain, or endurance target, the motor choice sits inside a broader mechanical tradeoff. That is the kind of work handled under custom robotics development, where the chassis, battery, and controller are co-designed rather than assembled from independent choices.
Frequently asked questions
Can you swap a brushed motor for a brushless one in an existing robot?
Not directly. You need a three-phase inverter in place of the H-bridge, additional wiring for Hall sensors or an encoder if using sensored control, and a re-tuned velocity loop. Mechanical mounting and shaft dimensions also rarely match. Plan it as a drive module redesign, not a component swap.
Do brushless motors always last longer?
They remove the dominant wear item, but bearings still fail and magnets can demagnetize if overheated. A brushless motor run consistently above its thermal limit will not outlive a conservatively specified brushed motor. Lifetime depends on how you operate the machine, not only on its construction.
Is FOC always better than six-step commutation?
No. FOC gives smoother torque, quieter operation, and can improve efficiency at low speed, but it demands more processing power, current sensing on at least two phases, and a sufficiently accurate rotor-angle measurement or estimate. If your robot does not require smooth low-speed operation and acoustic noise is not a concern, six-step is simpler and adequate.
What encoder resolution do you need for ROS 2 odometry?
There is no universal number. Work backward from your requirement: decide the smallest wheel rotation you need to resolve, calculate the required counts per wheel revolution, then divide by the gear ratio if the encoder is mounted on the motor shaft. On skid-steer platforms, slip typically dominates error, so very high resolution often yields diminishing returns.
How much does brush EMI affect robot electronics?
Brush arcing generates broadband interference that can disturb nearby analog sensors, I2C buses, and radio links. Standard mitigation includes ceramic capacitors across the motor terminals and, where appropriate, from terminals to the motor case, twisted or shielded motor leads, and physical separation from signal wiring. These are routine measures rather than difficult ones.
Does a brushless drive always improve battery runtime?
No. It can improve drivetrain efficiency, which helps, but runtime also depends on compute load, sensors, and payload power. On a robot where the onboard computer and sensor suite draw more than the motors during low-speed operation, the drivetrain gain may be a small fraction of total consumption. Measure your full power budget before assuming a large gain.
Which motor type suits outdoor field robotics better?
Brushless generally fits better because it eliminates brush dust and brush arcing, can offer better thermal handling on sustained climbs, and allows precise current limiting during stall events. Environmental sealing, however, depends on the specific motor and drive-module design rather than on commutation type alone. Properly sealed brushed gearmotors are used successfully on many outdoor platforms where duty cycles are intermittent.
Where to go from here
The brushed vs brushless DC motor comparison resolves differently for every platform because it depends on duty cycle, payload, thermal environment, and the control expertise available on the team. The useful next step is to define your continuous torque requirement, your worst-case stall duration, and your target mission length, then evaluate drive modules against those three numbers rather than against general claims.
If you are specifying a drivetrain for a platform that has to meet a defined payload, terrain, or endurance target, Fictionlab’s engineering team works on exactly this class of problem. Explore custom robotics development to discuss drive module design, controller selection, and ROS 2 integration for your application.