We're configuring a bq78PL114S12-based BMS for use with a 4S, 2.3Ah pack for a client to evaluate and we're having a lot problems getting the RSOC values to behave when we discharge at high current levels. The discharge current profile alternates between approximately 5A-10A, for most of the discharge, with 50A bursts for up to 30 seconds.
As you can see in the attached plot, RSOC behaved pretty well during the first 50A burst. During the second burst, RSOC was adjusted (that's OK) but then it suddenly dropped to zero and stayed there until we started discharging again. At the end of the discharge, RSOC had only dropped to 23% or so.
Checking the Learned tab, Qmax was around 196mAh and Qrem was around 59mAh (we're using a 1mOhm sense resistor so 0.1x for everything). This certainly doesn't seem to indicate that the pack has reached CUV at just above 2.5V/cell at a fairly low discharge rate, approx. 5A. After clearing the CUV alarm, a 5A discharge ended in seconds with a CUV alarm so the pack was empty. The RSOC value had only dropped to 20%.
How can we prevent this sudden RSOC drop? It wouldn't be too much of a problem if RSOC recovered after resting a bit but previous tests didn't show RSOC being reset even after the pack was idle for an hour (OCV Idle Qualifier = 45 min).
The AUX file for this pack was created at a 5A charge/discharge rate to get as close as we could to the typical 5A-10A continuous and 50A long-burst discharge rates the pack would experience. We can't go much higher than that as AuxGui says it couldn't generate certain Ra values at above an 8A rate during the AUX file creation. There's just not enough capacity available to run the discharge long enough.
The Capacity Algorithm is set to 3 (Average).
How can we stop RSOC diving to zero? Is it better to use as high a rate as we can during the creation of the AUX file? Or is it better to use a C/2 rate to give AuxGui lots of time to create the AUX file data? Are there any bqWizard settings can we adjust to help prevent this RSOC dive-to-zero? The client's accuracy spec for the SOC reading is +/-10% so even if a changed setting affects overall accuracy, that's OK. We just need to keep RSOC from dropping to zero.
Thanks!