Page 2 of 4
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Sun Aug 02, 2026 7:34 pm
by jhansen
New to this, so forgive me if this is obvious -
DC-DC conversion losses across all the individual actuator drivers add up across a whole robot - it's a less glamorous efficiency question than battery chemistry, but power electronics efficiency meaningfully affects real-world runtime too.
Totally unrelated but has anyone else noticed how fast component costs are dropping this year.
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Tue Aug 04, 2026 4:39 am
by mohammed64
Speaking from personal experience here,
Hot-swappable battery packs solve the runtime bottleneck for continuous operations (like a 24/7 warehouse shift) without needing a much bigger, heavier pack, but they add mechanical complexity, a failure-prone connector interface, and logistics overhead for managing spare packs.
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Wed Aug 05, 2026 9:42 pm
by choi98
I can speak to this a bit.
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. 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: How do you even measure real-world runtime fairly across different robots?
Posted: Sun Aug 09, 2026 4:55 pm
by ronald.clark
Genuine beginner question -
Battery placement (torso-centered vs backpack vs distributed through the limbs) is a real tradeoff between center-of-mass/balance considerations and thermal/cooling access - a torso-centered pack helps balance but is harder to cool than a more exposed backpack placement.
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Tue Aug 11, 2026 2:55 pm
by pierregreen
@ronald.clark I'd take that specific number with a grain of salt, honestly.
There's no widely standardized safety certification specific to humanoid battery packs yet in most jurisdictions - deployments generally lean on adapted versions of existing standards for industrial battery systems and electrical safety rather than a purpose-built humanoid standard.
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Sun Aug 16, 2026 8:53 am
by greta78
@pierregreen Genuinely curious -
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: How do you even measure real-world runtime fairly across different robots?
Posted: Tue Aug 25, 2026 4:10 am
by amara.brown
Can I ask a dumb follow-up -
There's no widely standardized safety certification specific to humanoid battery packs yet in most jurisdictions - deployments generally lean on adapted versions of existing standards for industrial battery systems and electrical safety rather than a purpose-built humanoid standard. Solid-state battery claims from platforms like XPeng's IRON, GAC's GoMate, and EngineAI's T800 are genuinely promising on paper for energy density and safety margins, but independent, large-scale field validation of those runtime claims is still fairly limited as of 2026 - it's real progress, not yet fully proven at scale.
Reminds me a bit of the early drone hobbyist scene, honestly.
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Sat Aug 29, 2026 2:12 am
by young58
Not to derail, but this reminds me of something adjacent:
Hot-swappable battery packs solve the runtime bottleneck for continuous operations (like a 24/7 warehouse shift) without needing a much bigger, heavier pack, but they add mechanical complexity, a failure-prone connector interface, and logistics overhead for managing spare packs.
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Sun Aug 30, 2026 11:59 am
by omar.farouk
Minor factual note:
Battery placement (torso-centered vs backpack vs distributed through the limbs) is a real tradeoff between center-of-mass/balance considerations and thermal/cooling access - a torso-centered pack helps balance but is harder to cool than a more exposed backpack placement. 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.
Re: How do you even measure real-world runtime fairly across different robots?
Posted: Sun Aug 30, 2026 11:59 am
by garcia51
@omar.farouk Here's what I know on this:
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. 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.
Totally unrelated but has anyone else noticed how fast component costs are dropping this year.