Humanoid robot battery life: A2 Ultra vs A3 on a shift
A runtime figure on a spec sheet reads like a single number to compare, and on the floor it behaves like a scheduling constraint that has to be designed around rather than simply looked up.
- The A2 Ultra walks for 1.5 hours or more, and stands for about 3, before it needs a swap or a fast charge; the A3 runs up to 10 hours on its own battery, with a 10-second hot-swap available on top of that.
- Read as a shift-length problem rather than a spec comparison, the gap changes what a floor plan needs to include. A machine that walks for an hour and a half between charges needs a charging or swap station within reach of every route it walks, built into the layout from the start. A machine rated for most of a shift on one charge needs that station too, just less urgently, and the difference is entirely about how often the walk to it happens, not whether it happens at all.
- A hot-swap is what lets a platform outlast its battery on an 8-hour shift, if it has one.
- Ten seconds is short enough that a swap barely interrupts a routine, and the A3's dual 1,152 Wh packs are built specifically to make that swap possible without powering the machine down. A platform without a fast swap option is not disqualified for longer shifts, but it does need the charging point placed somewhere the route already passes, rather than somewhere convenient to install.
A hand releases a battery module from the A3's back and puts it in again, with no tools: this is the 10-second hot-swap the platform's dual battery packs are built for.
- None of this is decided by the runtime number alone; it is decided by where the swap or charge point sits relative to the route.
- A platform that walks for an hour and a half, with its swap station at the far end of a long floor, loses more shift time to walking there and back than a well-placed one loses to the swap itself. The question worth asking before a layout is drawn is not how long a platform runs, it is how far the route sits from wherever it recharges, because that second number is the one that actually decides how much of a shift the platform is doing useful work.
Runtime is a starting constraint, not a finished answer. The floor plan is where the answer actually gets decided.
