Page 1 of 3

Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sat Aug 29, 2026 9:34 pm
by brian.campbell
This has been on my mind since a conversation I had last week. 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. 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. 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. Curious to hear how others see this.

Re: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 2:29 am
by ethan17
One nitpick - 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.

Re: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 7:56 am
by elarsen
@ethan17 Slight correction, though the overall point stands: 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.

Re: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 11:59 am
by jwang
From hands-on experience, 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: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 11:59 am
by betty.king
Worth being a little skeptical of the marketing angle here. 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.

Re: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 11:59 am
by greta78
@betty.king Yeah, this tracks with what I've read as well. 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. 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: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 11:59 am
by harmonicjen60
@greta78 Follow-up question though - 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. Kind of makes me think about how different this all looked even three years ago.

Re: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 11:59 am
by nancy_lewi
@harmonicjen60 Worth being a little skeptical of the marketing angle here. 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: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 11:59 am
by amandawhite
Pretty much this. One thing to add: 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. 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: Anyone building their own cell-level monitoring instead of trusting a BMS chip?

Posted: Sun Aug 30, 2026 11:59 am
by brenda52
Tangent, but worth mentioning: 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. 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.