Charge and discharge termination criterias
Just ordered our second unit, we love your device! Our main problem with the software is the following:
We would like a checkbox next to each criteria for discharge and charge functions.
This is very useful for battery calibration, where SOC level is not matching RSOC. We could just disable SOC criteria and have termination based on cell voltages.
Also, currently minimum discharge cell voltage is set to 3000mv, please make it possible to discharge to 2800mv.
Actually, the termination based on cell voltage is limited/not working.
Could you please come with some examples ? SOC is actually RSOC, it is the parameter reported by Windows.
By SOC i mean SOC parameter registered by the controller IC. RSOC as state of charged based on cell voltages.
Ok, so we have a lot of batteries that are stored for 1-2 years by clients.
Many of these batteries have wrong SOC level registered in the chip. Seems like mostly replacement batteries with chinise IC, when they go to sleep / long time storage, SOC will not update as the cells slowly discharge. For example I have about 10-15 units where SOC is 100%, but cell voltages are sitting at 3600mV each pair. With your device and the current software, charge terminates because of 100% SOC.
With my other devices, I can set it up so It will continute charging until a certain cell voltage level or I can set cut-off current / or cut-off pack voltage.
This is a safety protection mechanism. When a battery reports SOC=100% then it should not accept any charging current (charging FET disabled) and sets a fully charging alarm. If the battery does not disable the charging FET when SOC = 100% then something is bad inside the data flash (it could be the calibration). An option would be to Force charging as long as charging FET are not disabled even the SOC=100%, but in this case you trust that FET charging enabling/disabling mechanism works fine. Same for SOC=0%. I can do this but it is too dangerous in case there is a failure inside the chip.
@nex Yeah this is a calibration issue. I find these a lot with replacement Apple batteries. Also im sure these are not TI controllers, If you want I can take apart the next one I find with this problem and take a photo of the IC. We are a battery wholesale, I test a lof of batteries daily (returns or old used batteries that come in for service).
So far your machine has the best connectivity, our old machines does not read newer controllers. Even if they do, newer batteries have charge issue with our old gear, I think they start with CV and new batteries refuse that. So your way of raising voltage and current at the same time for starting is awesome. If works with everything the old machines couldnt do.
If you could add a force charge and force discharge option, I wouldnt need to use any other machine for my daily work.
We would also gladly buy a multi channel machine of this, if you ever make one!
Apple batteries use in principle TI chips. I have’t found any other chip inside Apple batteries.
To charge a laptop battery is quite complex since the charging algorithms are different from brand to brand or even family to family for the same brand. Most of them do not respect the standard. After I managed to charge most of the batteries to about 90-95% I spent about 3 years for improving the NLBA charging. Now it is charging most batteries to 99-100%.
Is your secondary equipment able to charge batteries to 99-100% ?
If you need more devices I can make you a good offer and allocate time to implement stop condition based on cell voltage. I am currently working in Reseting the chips. With this feature the batteries can be repaired.
OK, so here is an example for this: I have an Apple A1322 battery, that has bad calibration. Did auto calibrate with your software, multiple cycles of it, very small improvement on FCC.
During discharge, I get termination because 0% state reached, but all cells still have 3600mv. I need an update where I can set your software to ignore SOC, and discharge to the set cell voltage limit.
If you could make it a checkbox on each termination criteria before charge / discharge. This way I could select more of them If I want, or just one.
If you can implement this, we would buy 5 more devices right away, and some more later.
So now how I solve this currently, I connect to my DC load and my old tester at the same time, to track voltages. I could do it all with your device, with that update we talked about.
Please focus on this feature, because i dont like to say this but the NLBA is so far useless for calibrating chips. Most of the times after a chip reset the State Of Charge is reported wrong. So u need to discharge at least to 3.0v and then charge to 100% to calibrate the chip.