Other Parts Discussed in Thread: BQ34110,
Battery chemistry: NiMH.
I have the BQ23713 working as Buck/Boost converter for loads and battery charger/controller. A BQ34110 is used as well. Charging/discharging is controlled by firmware using mainly data from the 34110.
For safety reasons, I want to add some hardware mechanism to avoid battery overtemperature to avoid the scenario where the firmware does not terminate fast charging due to some bug. Before somebody asks, I am using the watchdog of BQ25713, but I want to avoid that some condition where the firmware does not detect charging termination and keeps writing to ChargeCurrent() register, causing the charge overload.
I connected one of the ALERT outputs of 34110 to CELL_BATPRESZ pin. I expected that whenever the ALERT output pulled this pin to zero, the ChargeCurrent() register would be forced to zero. However, I noticed that, if I write to ChargeCurrent(), it sets the charging current to a non zero value and it is only zeroed if there is a negative transition on the CELL_BATPRESZ pin.again. So a misbehaved software could inadvertently force the overload. I would like to make the charging system as bullet proof as possible.
So, is there an alternative way to zero the charging current that could be more bullet proof?
Thank you in advance.