You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, indicated 0% SoC does not always correlate with real 0% SoC due to these reasons:
fixed battery capacity value in the configuration
real capacity is changing due to temperature / load / aging etc.
indicated SoC drift due to shunt inaccuracies and inaccurate charge efficiency setting (I mostly limit the SoC to 80%, I noticed a significant drift if I'm not charging to 100% at least once a month)
My proposal would be to calibrate the indicated SoC to 0% as soon as the lowest cell falls below a configurable value (e.g. 3V) for some time.
Also, the calculated Ah between calibrated 100% and 0% in a full cycle can be automatically set as new capacity for future SoC estimations.
Future improvements could also be factors that consider the cell temperature and load in the SoC calculation. (e.g. 5% capacity loss for each 10K below 20°C, configurable. Similar factors for the C-rate could be used aswell)
The text was updated successfully, but these errors were encountered:
Currently, indicated 0% SoC does not always correlate with real 0% SoC due to these reasons:
My proposal would be to calibrate the indicated SoC to 0% as soon as the lowest cell falls below a configurable value (e.g. 3V) for some time.
Also, the calculated Ah between calibrated 100% and 0% in a full cycle can be automatically set as new capacity for future SoC estimations.
Future improvements could also be factors that consider the cell temperature and load in the SoC calculation. (e.g. 5% capacity loss for each 10K below 20°C, configurable. Similar factors for the C-rate could be used aswell)
The text was updated successfully, but these errors were encountered: