We have been using the STC3115AIQT in a released product, but have run into a number of rare issues relating to the SOC value. We have the STC3115AIQT connected to an STM32 STM32F091, on an I2C bus. The I2C bus is shared with several other devices (no address clashes), and we are using an in house STC3115AIQT driver. We read the fuel gauge data every 3s.
We have found some devices that have been returned from customers that are reading an SOC value of 0, despite having a fully charged battery. The voltage value was also incorrect. After testing the device was plugged into the charger, and the fuel gauge recovered.
We have implemented application level measures to reset the fuel gauge when this occurs, but the root cause is still unknown. Currently the failure rate is in the range of 1-5 per 1000 devices.
Is anyone able to provide any insight into why this might be happening or any changes we can make to reduce the risk of this occurring?
