Live Nov 18 · Cohort 3Nov 18, 19:00 MSK — free hands-on AI agents live workshop · Live Cohort 3 starts Nov 23Join Nov 18 Live →Cohort 3 (Nov 23)
ReleaseInsight · On RadarHabr AI→ original

Boston Dynamics Put Atlas on Scooter Wheels to Push Its Actuators to the Limit

Boston Dynamics attached ordinary scooter wheels to the "ankles" of its Atlas humanoid. The idea is simple: on wheels, every acceleration, turn and stop drives the motors across their full range of torque and speed, under real load. The robot is controlled by a neural network trained with RL, and it learned smooth rolling on its own. The entire modification came down to a single adapter.

AI-processed from Habr AI; edited by Hamidun News
Boston Dynamics Put Atlas on Scooter Wheels to Push Its Actuators to the Limit
Source: Habr AI. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceHabr AI ↗
Editor-in-Chief
Key metric #1The only new part is an adapter for a scooter wheel
Key metric #2The whole-body control algorithm was trained with RL in simulation
Key metric #3The findings are already being carried over to the standard Atlas configuration

When you see a humanoid robot on scooter wheels, your first thought is that the engineers decided to play a joke. In reality, Boston Dynamics pulled off a perfectly serious engineering trick. The wheels aren't there for speed or looks, but to torture the hardware: to check how Atlas's actuators handle the most demanding operating modes.

Why a Robot Needs Wheels

Every humanoid has a bottleneck: the pairing of a trained neural-network controller with real motors. In simulation, motors are ideal; in hardware they heat up, hit torque limits and don't always keep up with commands. To see exactly where problems begin, you need a scenario in which the motors constantly work at the edge of their specifications.

Walking is a poor fit for this: it has plenty of pauses, stance phases and calm stretches. On wheels, everything is different. Every start, turn and stop forces the motors to deliver high torque at high speed, all with a real load on the body. Atlas on wheels is a research platform, not a new product.

How It Was Done

The hardware side turned out to be almost trivial. A standard scooter wheel was attached to the stock "ankle" assembly through a single custom-made adapter. It is the only new part in the entire design. According to the company, Atlas was designed from the start for mass production and easy maintenance, so the modification turned out to be no harder than changing a bicycle wheel.

The software side didn't involve drama either. In simulation, each wheel was described as an "ankle" capable of rotating continuously. The controller was trained under conditions as close to real as possible, so that quality would not degrade when transferred to hardware.

For reinforcement learning, existing approaches were adapted with three targeted changes:

  • the structure of the reward function;
  • the range of commands the algorithm is trained on;
  • the methods for maintaining posture.

That was enough for the robot to learn smooth rolling on its own while staying stable, leaving it simple to control.

What It Looked Like in Practice

Some of the movements were taken from a human motion-capture library, in which the feet slide actively. Where a human would slide a foot, the algorithm learned to turn the wheels and cover the stretch by rolling. In effect, the neural network translated a human idea of movement into a different "kinematics."

A telling example is a jump with a 360-degree turn. Here the algorithm works as trajectory tracking: it repeats a recorded human motion. According to the company, it worked on the first try. Traction with the surface is used differently than in the legged Atlas: before the jump, the lower body quickly rolls into the right position and prepares for the upward thrust.

The project's first results are already being integrated into the robot's standard configuration. The company also recently showed a new hand for Atlas: four fingers, 13 degrees of freedom, direct drive and a design optimized for accurate modeling.

Takeaways

First: if you build a robot or any hardware with a trained controller, look for a scenario that squeezes the maximum out of the actuators. Here the wheels work as a cheap load test. One adapter instead of reworking the whole platform lets you see what calm walking won't reveal.

Second: designing for maintenance pays off. A one-part modification is possible only because the robot was designed from the start to be replaceable and repairable. For robotics startups, it's a good argument for modularity.

Third: sim-to-real doesn't always require a new algorithm. Here, careful retuning of the reward, command range and posture maintenance, plus a correct model of the new assembly in simulation, was enough. Motion-capture data can be reused if the controller itself finds a substitute for sliding.

Limitations

The publication contains no numbers: no peak torques, temperatures or actuator lifetimes. This is a demonstration of an approach, not a benchmark, and it's not yet possible to say how much such a test improved real-world performance. The wheeled Atlas will not become a production model: it is a tool that makes the "legged" Atlas more reliable. But as an example of how a simple idea helps verify a complex system, the story is a good one.

Story

Key Questions Answered

Why a Robot Needs Wheels?

Every humanoid has a bottleneck: the pairing of a trained neural-network controller with real motors. In simulation, motors are ideal; in hardware they heat up, hit torque limits and don't always keep up with commands. To see exactly where problems begin, you need a scenario in which the motors constantly work at the edge of their specifications. Walking is a poor fit for this: it has plenty of pauses, stance phases and calm stretches. On wheels, everything is different.

How It Was Done?

The hardware side turned out to be almost trivial. A standard scooter wheel was attached to the stock "ankle" assembly through a single custom-made adapter. It is the only new part in the entire design. According to the company, Atlas was designed from the start for mass production and easy maintenance, so the modification turned out to be no harder than changing a bicycle wheel. The software side didn't involve drama either. In simulation, each wheel was described as an "ankle" capable of rotating continuously.

What It Looked Like in Practice?

Some of the movements were taken from a human motion-capture library, in which the feet slide actively. Where a human would slide a foot, the algorithm learned to turn the wheels and cover the stretch by rolling. In effect, the neural network translated a human idea of movement into a different "kinematics." A telling example is a jump with a 360-degree turn. Here the algorithm works as trajectory tracking: it repeats a recorded human motion. According to the company, it worked on the first try.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…