BQ27Z561-R2: low temperature optimization issue

Part Number: BQ27Z561-R2
Other Parts Discussed in Thread: BQ27Z561, GPCRB

Tool/software:

1round_verify.csv

round1_low_optimize_20250807-report.zipround2_low_optimize.zip

Hi,

Currently we have some issue with gauge BQ27z561 low temp optimization.

In the first round, after flashing the optimized gauge firmware to our product, the SoC always jumped from 7% to 0, and then working for a long time with SoC=0%. After check the data in DOD_newRb_ratio.txt, a lot of the value is constant.

In the second round, the constant value in the DOD_newRb_ratio.txt is less, but it report " Qmax, mAh : 206", in fact, the real design capacity is 2000mAh.

Could you give some support about how to improve the low temp optimization?

Thanks in advance!

Jerry Lv

  • Hello,

    This question has been assigned and will be reviewed by someone on the team when possible. In the meantime feel free to attach any associated .log/.gg/test files from this project.

    Thank you,
    Alan

  • GPCRb uses the current and time information in the log files together with the ChemID to determine Qmax. If Qmax is that off then something went very wrong. Please check the total passed charge in your log file (integrate the current over time) and make sure that it is reasonable (e.g. the room temperature data should be >= 90% of Qmax, depending on load current and the cold temperature data should be >= 70% of Qmax, also depending on load current and temperature.

    If the total passed charge is in the vicinity of 200mAh for a rated design capacity of 2000mAh then you must make sure that the measurements and time in the log files are correct.