Page 3 of 3

Re: Battery placement (torso vs backpack vs distributed) - tradeoffs for balance and cooling?

Posted: Sun Aug 30, 2026 11:59 am
by green28
Not sure I fully agree here. Thermal margin in a densely packed humanoid chassis is often the real limiting factor on sustained performance, not raw motor power - actuators get thermally throttled well before they'd hit their absolute torque limits, especially during repeated high-load cycles like continuous lifting. Distributed power architectures (multiple smaller packs or local capacitor buffering near high-draw actuators) can reduce peak current demands on the main bus and improve fault isolation, at the cost of added complexity versus a single central pack.

Re: Battery placement (torso vs backpack vs distributed) - tradeoffs for balance and cooling?

Posted: Sun Aug 30, 2026 11:59 am
by williams84
Pretty much this. One thing to add: Regenerative braking on humanoid joints can recover some energy during deceleration phases of walking, but the actual energy recovered is modest compared to a vehicle, since humanoid joints don't sustain the same continuous high-speed rotation that makes regen worthwhile in EVs. Tesla's Optimus Gen 2 reportedly carries roughly a 2.3 kWh pack and manages about two hours of dynamic work, while Unitree's H1 runs a smaller 0.864 kWh pack good for under four hours of largely static operation - a useful illustration of how battery size and workload type both drive runtime.

Re: Battery placement (torso vs backpack vs distributed) - tradeoffs for balance and cooling?

Posted: Sun Aug 30, 2026 11:59 am
by olga_lind
I'd take that specific number with a grain of salt, honestly. Idle/standing power draw is often surprisingly close to a meaningful fraction of active walking power draw once you account for onboard compute, sensors, and balance-holding torque - 'doing nothing' still costs real energy on a humanoid. The average humanoid in 2026 carries under 2.5 kWh of battery capacity, with real-world runtimes clustering between two and four hours depending on how dynamic the workload is - static, low-motion tasks stretch runtime much further than continuous walking or lifting.

Re: Battery placement (torso vs backpack vs distributed) - tradeoffs for balance and cooling?

Posted: Sun Aug 30, 2026 11:59 am
by james15
Ran into exactly this myself. Higher-voltage power architectures reduce resistive losses and current draw through the wiring harness for a given power level, which is part of why some newer platforms are moving away from lower-voltage packs as total system power demand climbs. Distributed power architectures (multiple smaller packs or local capacitor buffering near high-draw actuators) can reduce peak current demands on the main bus and improve fault isolation, at the cost of added complexity versus a single central pack.

Re: Battery placement (torso vs backpack vs distributed) - tradeoffs for balance and cooling?

Posted: Sun Aug 30, 2026 11:59 am
by samuel.adams
@james15 Here's the relevant bit as far as I understand it: Tesla's Optimus Gen 2 reportedly carries roughly a 2.3 kWh pack and manages about two hours of dynamic work, while Unitree's H1 runs a smaller 0.864 kWh pack good for under four hours of largely static operation - a useful illustration of how battery size and workload type both drive runtime.

Re: Battery placement (torso vs backpack vs distributed) - tradeoffs for balance and cooling?

Posted: Sun Aug 30, 2026 11:59 am
by carol38
This matches what I've seen too. Regenerative braking on humanoid joints can recover some energy during deceleration phases of walking, but the actual energy recovered is modest compared to a vehicle, since humanoid joints don't sustain the same continuous high-speed rotation that makes regen worthwhile in EVs. Tesla's Optimus Gen 2 reportedly carries roughly a 2.3 kWh pack and manages about two hours of dynamic work, while Unitree's H1 runs a smaller 0.864 kWh pack good for under four hours of largely static operation - a useful illustration of how battery size and workload type both drive runtime.