This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BQ27510-G3: Strange Capacity Readings Continued

Part Number: BQ27510-G3

I had a thread opened about some accuracy issues with the BQ27510-G3 and worked through the details to obtain a very accuracy golden image with the help of TI support.  However, I just had a unit that has a very large capacity discrepancy.  You can see the filteredFCC is very different.  I recall this happening last time as well and it seems to possibly coincide with us plugging and unplugging the battery.   This particular unit ran accurately a week ago when I tested it.  It ran for 14hrs+ which is what I calculated and the gauge was accurate.  Now it is predicting <10hrs.  This is using a golden image that I cycled 10 times to verify accuracy before deploying it to test units.

Here was the sequence of events.  The unit was at ~40% SOC and then I unplugged the battery to make some other unrelated hardware changes.  I plugged the battery back in and it was suddenly at 4% despite the cell still being at > 3.6V.  I plugged it in to charge and surprisingly it was starting to taper the charge current at 40% SOC already.  I let it continue to charge and noticed the state of charge jumped from ~70% to 100% because the fuel gauge was so far off when it reached charge termination.  So somewhere in here the gauge thinks we lost 1900mAh

We are going to production here in a few weeks and so this is becoming very concerning.

  • Thinking more about this.  Is it possible if the unit was previously running, then powered off, battery removed and the battery was reinserted after removal that the first OCV reading would be off because the battery had not relaxed enough?

  • Hello Andrew,

    When the battery is removed then reinserted the complete system has to be powered up. On power up the gauge runs an initialization sequence to determine the state of the battery. The previous info about the battery prior to removal is no longer used/valid since the gauge doesn't know what was done to the battery after removal and prior to reinsertion. Therefore during the initialization the gauge tries to take an OCV reading to establish state of charge (SOC). What I suspect happened because the system was  being powered up there was a high inrush current during the time the OCV was being taken, which resulted in the error in SOC. Allowing the cell to relax and take another OCV would correct it and as you observed charging to full with valid charge termination correct the error as well.

    You may want to increase "Max IR Correct" to 1000mV to see if it help resolve the issue then decrease it to a level that works for your application.

  • Damian,

    Thanks.  So for Max IR Correct, how do we know what to tweak it to?  Also, is there a way to force it to take another OCV reading after letting the system rest?  I let it sit for a couple hours and never saw it update the capacity.

  • Hello Andrew,

    I gave you a recommendation above. I would decrease it based on trial and error. We don't know your application to give you a specific value. Sending reset command should force an OCV measurement.