Other Parts Discussed in Thread: BQSTUDIO, EV2400
I was wondering if anyone else here has seen this scenario on battery packs using the BQ2060 - after an event like a battery pack going overtemp - subsequent queries for voltages and temperatures appear to be stale; after a time (I'm assuming this is a time-out that's possibly in the config EEPROM) - the charger will come back on and readings resume.
I've tried using a tool like the EV2400 to look at the registers (EEPROM) on the BQ2060 PCBA via the SMB bus - but that's not entirely successful since that's not supported by bqStudio - but I suppose I will find a way to do that.
From the datasheet:
Over-Temperature: An over-temperature condition exists when Temperature() is greater than or equal to the
Max T value programmed in EE 0x45 (most significant nibble). On detecting an over-temperature condition,
the bq2060 sets the ChargingCurrent() to zero and sets the OVER_TEMP_ALARM and
TERMINATE_CHARGE_ ALARM bit in BatteryStatus() and the CVOV bit in Pack Status. The
over-temperature condition is cleared when Temperature() is equal to or below (Max T– 5°C).
I'll see if I can check that value - does the charging current being set to zero somehow cause data reads to be stale?