Brushless (BLDC) motor
Brushless (BLDC) motor – definition
A brushless DC motor, usually abbreviated as BLDC motor, is an electric motor that uses electronic commutation instead of mechanical brushes and a commutator. In mobile robotics, the term usually refers to a permanent magnet synchronous machine driven by a dedicated electronic speed controller (ESC) that switches phase currents according to rotor position. The practical result is a compact actuator with high efficiency, high torque-to-weight ratio, good speed control, and low maintenance.
In a UGV, a BLDC motor is not a standalone part. It is one element of a drivetrain that also includes an ESC, gearbox or belt reduction if needed, wheel encoder feedback, a power distribution stage, and a higher-level motion controller. On platforms such as Leo Rover or Raph Rover, the engineering question is not only whether a motor is brushless, but how its electrical constants, torque curve, thermal behavior, supply voltage, and feedback interfaces fit the vehicle mass, wheel diameter, terrain profile, and ROS 2 control architecture.
BLDC motors are common in mobile robots because they provide better durability than brushed DC motors under long duty cycles. They also scale well from small educational rovers to larger payload-oriented UGVs. For outdoor work, where dust, vibration, and variable load are typical, removing brushes reduces wear and electrical noise from mechanical commutation.
How a BLDC motor works in a mobile robot
A BLDC motor has a stator with multiple windings and a rotor with permanent magnets. Torque is produced when the ESC energizes stator phases in a sequence synchronized with rotor position. Rotor position can be estimated or measured in several ways. Common methods include Hall sensors, rotary encoders mounted on the motor shaft, and sensorless back-EMF estimation. In robotics, sensored operation is often preferred at low speed because start-up torque and velocity estimation are more reliable.
For UGV motion, the control stack is typically layered. The low-level ESC regulates phase current, torque, or motor velocity. A motor controller board may then regulate wheel speed using encoder feedback. At the robot level, a differential drive controller converts commanded body velocity into left and right wheel targets. In ROS 2, this usually means consuming geometry_msgs/msg/Twist on /cmd_vel and publishing wheel or odometry state through sensor_msgs/msg/JointState and nav_msgs/msg/Odometry. Frame naming and coordinate conventions should follow REP 103 and REP 105.
The core electromechanical relationships are simple and useful during sizing:
Mechanical power: P = tau * omega
Back-EMF: E = Ke * omega
Torque: tau = Kt * I
Where tau is torque in N m, omega is angular velocity in rad/s, Ke is the back-EMF constant, Kt is the torque constant, and I is current. For SI-consistent motor models, Kt and Ke are numerically related. In practice, vendor datasheets may express motor constants in rpm/V, A, mN m/A, or oz-in, so unit conversion matters.
Key parameters and metrics
When a BLDC motor is selected for a rover, the decision should be based on measurable drivetrain requirements rather than only nominal wattage. Wheel-ground interaction, gradeability, payload, and thermal limits often dominate performance.
| Parameter | Why it matters in UGVs | Typical source |
|---|---|---|
| Rated voltage | Must match battery bus and ESC input range | Motor and ESC datasheet |
| Continuous current | Defines thermal operating envelope | Motor datasheet |
| Peak current | Important for starts, obstacles, and slope transitions | Motor and ESC datasheet |
| Torque constant Kt | Relates current to motor torque and wheel torque through gear ratio | Motor datasheet |
| KV rating | Approximates no-load speed per volt | Motor datasheet |
| Encoder resolution | Affects odometry quality and low-speed control | Encoder specification |
| Ingress and thermal limits | Critical in outdoor robots exposed to dust and splash | System specification |
| Gear ratio | Sets trade-off between speed and tractive effort | Gearbox specification |
For differential-drive robots, a practical sizing check is wheel torque. If the wheel radius is r and the required longitudinal force per wheel is F, then the required wheel torque is:
tau_wheel = F * r
The motor must provide that torque after gearbox efficiency losses and with thermal margin. If the robot operates on deformable terrain, the required torque can be much higher than on indoor flat floors.
BLDC motors in ROS 2 and control integration
ROS 2 does not directly drive a motor phase bridge. It interfaces with a lower-level controller through drivers and hardware abstractions. In modern mobile robots, the common pattern is to expose wheel joints to ros2_control, then run a differential drive controller over them. The motor controller firmware handles current loops, commutation, and encoder counting. ROS 2 handles velocity commands, odometry, diagnostics, and higher-level autonomy.
For a BLDC-based drivetrain, the useful interfaces are usually:
geometry_msgs/msg/Twistfor body velocity command on/cmd_velsensor_msgs/msg/JointStatefor wheel position and velocitynav_msgs/msg/Odometryfor fused motion estimatediagnostic_msgs/msg/DiagnosticArrayfor temperature, current, voltage, and controller faults
A minimal ROS 2 controller configuration may look like this:
controller_manager:
ros__parameters:
update_rate: 50
joint_state_broadcaster:
type: joint_state_broadcaster/JointStateBroadcaster
diff_drive_controller:
type: diff_drive_controller/DiffDriveController
diff_drive_controller:
ros__parameters:
left_wheel_names: ["left_front_wheel_joint", "left_rear_wheel_joint"]
right_wheel_names: ["right_front_wheel_joint", "right_rear_wheel_joint"]
wheel_separation: 0.34
wheel_radius: 0.0625
publish_rate: 50.0
base_frame_id: base_link
use_stamped_vel: false
The exact values depend on the rover geometry. Coordinate and frame semantics should remain consistent with REP 103 and REP 105 so that odometry, localization, and Nav2 components work correctly.
Use cases with Leo Rover and Raph Rover
On Leo Rover, a BLDC-based drivetrain is relevant when a project needs higher efficiency, lower wear, or custom wheel modules compared with simpler educational drivetrains. Leo Rover supports ROS 2 and uses a differential-drive kinematic model. That means the motor selection should prioritize stable low-speed control, repeatable odometry, and compatibility with onboard compute resources based on Raspberry Pi. Since Leo Rover is not an autonomous outdoor navigation system out of the box, BLDC integration is usually part of a larger stack that also includes wheel calibration, localization, and safety supervision.
On Raph Rover, the same BLDC principles apply, but the constraints change. The platform is larger and intended for heavier payloads, so continuous torque, thermal headroom, and regenerative braking behavior become more important. Larger wheels and higher mass increase reflected inertia and startup current demand. In field inspection or agricultural trials, engineers often prefer sensored BLDC drives with robust current limiting and telemetry because low-speed operation on uneven terrain is common.
In both platforms, BLDC motors are especially useful when the rover carries perception payloads such as LiDAR, depth cameras, or RTK GNSS. Higher drivetrain efficiency can extend mission time. Cleaner low-speed control can also improve sensor data quality by reducing jerky motion during mapping and inspection runs.
Limitations and trade-offs
BLDC motors are not automatically better in every rover. They require a more complex electronic drive than brushed DC motors. Sensorless ESCs designed for hobby propulsion may perform poorly at very low speed, which is exactly where UGVs often operate during docking, precise inspection, or autonomous navigation in cluttered environments.
The main trade-offs are:
- Higher integration complexity – ESC tuning, feedback wiring, and fault handling
- Potentially worse low-speed behavior with sensorless commutation
- Need for thermal monitoring under sustained stall-like load
- Greater importance of EMC and power integrity when sensitive sensors share the same power bus
For research robots, the best drivetrain is often the one that exposes enough telemetry to be observable in software. Current, voltage, controller state, and temperature should be available to ROS 2 diagnostics and logs. That matters more than nominal motor power alone.
Normative references and standards
In ROS-based mobile robotics, BLDC integration should be interpreted through the software and frame conventions used by the rest of the robot. The key references are REP 103 for standard units and coordinate conventions, and REP 105 for coordinate frames in mobile platforms. Message interfaces are defined in the ROS 2 documentation for geometry_msgs, sensor_msgs, nav_msgs, and diagnostic_msgs. Hardware-specific electrical limits must always come from the motor, encoder, and ESC manufacturer datasheets.
For Leo Rover-specific implementation details, the relevant source is the official platform documentation at docs.fictionlab.pl/leo-rover. For accessories and compatible integration components, the practical catalog reference is fictionlab.pl/shop/.