Hacker News new | ask | show | jobs
by esmi 4465 days ago
There are 100s of ways to game this cycle spec too. For example, for all we know there is a 100WHr pack inside the box and they only make 50WHr of it available to the user. This way you can make a 50WHr battery that effectively never "degrades". The BatteryOS just manages the "reserve". Then the only thing they are really measuring is the speed at which their algorithm looses calibration. The software for many BMUs (battery management units) actually does this today.
2 comments

That's not a terrible idea, actually.

When you purchase any NAND flash device like a USB stick or an SSD, essentially the same thing is happening. The raw storage is much higher, but due to a high raw bit error rate (see NAND displacement errors), the need for wear leveling, and the need for reserve blocks to swap into service as the device ages, the claimed capacities are reduced to accommodate MTBF and observed bit error specs.

In cases such as this I think it'd be disingenuous not to drop your claimed specs to reflect the actual usefulness of the device.

Except they explicitly state that they don't do this. They refer to the 50% charge scheme being used in the Chevy Volt and claim they don't do that.