The new controllers on the other hand happily commit suicide at over-discharge voltages where cells are still easily and safely recoverable with little to no capacity loss. The old controllers tried to fix over-discharged cells and they succeeded in the majority of cases because you rarely have a true 0V scenario unless you have a shorted cell or something. Clarification: True 0V discharge kills Li-ion cells and you shouldn't attempt to recover them. Some people will say 'Well that's by design, a single overdischarge turns Li-Ion cells into potential fire-bombs!' If that was true there would've been a lot more cases of batteries setting houses on fire back in the early 2000s as '0V deep discharge recovery' used to be a feature in some laptop battery pack controllers back then.It's not nearly as bad as some urban legends would have you believe. Querying the controller reveals it's had 43 charge/discharge cycles so the cells are practically new! And yet the controller was in permanent lockout mode due to a single overdischarge condition getting logged.Trying to charge the battery in the laptop resulted in a rapidly flashing charge LED indicating charge failure. (Aside from a few outtakes from chinese developer forums) So why would you want to mess with a smart battery controller anyway? Consider the case of one ThinkPad X100e I purchased a few months ago.īattery dead. Looking around there's very little software available out there for working with battery controllers in general and most of them cost hundreds or even thousands of dollars.0/SLUU225 datasheet, cross reference, circuit and application notes in pdf format.Usually the chips' datasheets aren't even publicly available. Having gone deep down the rabbit hole of researching smart laptop battery controllers I've ended up reverse engineering a couple of them used in ThinkPad batteries.

Sanyo tool reset bq8030 datasheet pdf