BQ27441-G1: SOC reports wrong value when stopping and restarting discharge some times later

Part Number: BQ27441-G1

I've been struggling for several weeks to solve the following problem: I'm using the bq27441G1 chip to control the charging of a 3.7V 3000mAh Li-ion battery. Once the battery is fully charged, if I discharge it with a constant current (between C/30 and C/8) down to 0%, the gauge readings are correct. However, if the discharge cycle is discontinuous, for example, a discharge at C/10 for 3 hours followed by a one-hour pause (discharge current < 1mA), the battery's state of charge (SOC) instantly drops by several percent when I restart the discharge at C/10. If I continue the discharge with one or two more discharge + pause cycles, the gauge's SOC reaches 0% even though there are still several tens of percent of charge remaining in the battery. I performed several full charge and discharges to have the device computing the QMAX and Ra tables without much success. After updates of the Ra table, the filtered SOC tends to be more accurate but only when SOC is roughly 60%, after that the filtered SOC is falling too fast to reach 0% at about the same time that the unfilterd SOC. I Join a capture of the SOC step event done with the eval board. I see that 'debugX' values have big value changes at the time of the event but I do not have any clue of what those debug values meanstep_capture.xlsx  ... If someone may help .... 

  • Hello,

    This question has been assigned within the team and will be reviewed and followed up with a application engineer when possible. In the meantime please attach any associated .log/.gg files associated with the projects

    Thank you,
    Alan 

  • If you stop a discharge and let the cell relax, then the gauge will use a voltage reading to adjust cell state (depth of discharge). When you restart the discharge, the gauge will update its estimate based on this DOD change. A minor adjustment is not unusual (because there's always an error between cell model and actual cell) - this is one reason why there's a filtered version.

    A large adjustment means that the DOD update was incorrect due to either an error in voltage measurement, a premature voltage measurement or an error in the ChemID. With this gauge with a built-in ChemID, it's most likely an incompatibility between cell and ChemID. Debug 3 is DOD0 (the DOD update based on an OCV measurement).

  • If I understand you correctly, this means my battery is incompatible with the chemID programmed into the gauge? Is there a way, by modifying the gauge's parameters, to mitigate the correction in the SOC value when discharging resumes? Would sending a SOFT-RESET command shortly after discharging resumes recalculate an SOC value closer to reality?

    Thank you,

    Pierre

  • This gauge has a fixed ChemID. You can check the DOD error by calculating DOD = DOD0 + 16384 * Passed Charge / Qmax.

    DOD0 = Debug 3 [no unit]
    Passed Charge = Debug 6 [mAh]
    Qmax = Debug 1 [mAh]

    If I do this, then I can see that DOD has a discontinuity at the TrueSOC jump (due to the DOD0 update). This indicates that either Qmax is completely wrong (configuration mistake) or that the chemistry isn't compatible.

    As the ChemID is fixed in this gauge there isn't much that you can do (if Qmax is correct).

  • SOFT_RESET won't fix this either. All that does is force a DOD0 update (with potentially questionable OCV quality). It doesn't fix the chemistry incompatibility problem.