Page 1 of 2

How much does firmware-level power management actually extend real runtime?

Posted: Tue Oct 22, 2024 6:37 pm
by sharonschmidt
Trying to organize my own thinking on this, so bear with me. 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. 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. Happy to be told I'm wrong on any of this.

Re: How much does firmware-level power management actually extend real runtime?

Posted: Tue Oct 22, 2024 9:21 pm
by kwilliams
@sharonschmidt Same conclusion I've come to. Also worth noting: 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 much does firmware-level power management actually extend real runtime?

Posted: Tue Oct 22, 2024 11:52 pm
by scott21
Slightly off-topic, but related: Fast charging accelerates capacity fade over repeated cycles, so fleet operators generally have to choose between minimizing downtime (fast charging) and maximizing pack lifespan (slower charging or swap-based approaches) rather than getting both for free.

Re: How much does firmware-level power management actually extend real runtime?

Posted: Wed Oct 23, 2024 1:56 am
by camila.jackson0
Thanks for laying this out, genuinely useful. 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. 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.

Re: How much does firmware-level power management actually extend real runtime?

Posted: Wed Oct 23, 2024 6:58 am
by dubois35
@camila.jackson0 Counterpoint: 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. 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. Reminds me a bit of the early drone hobbyist scene, honestly.

Re: How much does firmware-level power management actually extend real runtime?

Posted: Thu Oct 24, 2024 4:59 pm
by scott21
Follow-up question though - 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 much does firmware-level power management actually extend real runtime?

Posted: Sun Oct 27, 2024 3:02 pm
by williams84
@scott21 That's the official framing, at least - reality tends to lag a bit. A BMS (battery management system) has to guard against transient current spikes from sudden gait changes or lifting motions, not just steady-state draw - peak current headroom and fast-acting protection logic matter as much as total capacity for real-world duty cycles.

Re: How much does firmware-level power management actually extend real runtime?

Posted: Mon Oct 28, 2024 3:26 am
by kwilliams
Same conclusion I've come to. Also worth noting: 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: How much does firmware-level power management actually extend real runtime?

Posted: Tue Oct 29, 2024 12:08 am
by scott21
@kwilliams Speaking from personal experience here, Best-in-class lithium-ion cells used in humanoids are currently landing around 280-300 Wh/kg, which is respectable but still leaves battery mass as one of the largest single contributors to total robot weight. 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 much does firmware-level power management actually extend real runtime?

Posted: Tue Oct 29, 2024 6:40 pm
by emilyperez
@scott21 Minor factual note: 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. Totally unrelated but has anyone else noticed how fast component costs are dropping this year.