Hello,
I am experiencing issues with TPS3831L30 (voltage supervisor), which I use on a battery powered device I designed to disable three voltage regulators when battery voltage drops below 2.63V (factory trimmed), see attachment for circuit schematic.
Full_scenario.png is oscilloscope view of battery voltage (yellow) and RESET signal coming from TPS3831L30 (blue).
Note that battery range is supposed to be 4.2V to 2.5V.
Explanation of picture:
Simulating the battery with a power supply, when the battery is fully charged at 4.2V, the RESET pin of the voltage
supervisor is HIGH as it should be, because 4.2V > 2.67V, which is the fixed threshold of the voltage supervisor.
As I discharge the battery, the RESET pin goes low when Vbatt < 2.67V, all good here.
Now the problem: as I recharge the battery, I would expect the RESET pit to ho HIGH again when Vbat > 2.67V, but infact it does so at around 3.8V.
While recharging, if I hold 2.67 < Vbat < 3.8 (glitch.png) I see some glitches where the RESET signal tries to go high, but it does so just for a moment.
For some reason the range 2.67V to 3.8V has some quirks, which I first noted when I discharged and recharged the battery, as shown above.
Later I discovered that this happens also "on the way down", meaning that, starting from a charged battery, if I discharge it to somewhere 2.67 < Vbat < 3.8 and I turn off the power supply
to simulate turning off the device, when I turn it back on the same behaviour is observed: RESET pin low with glicthes unless charged back to above 3.8V.
All of this happens only when the RESET pin has a "load", meaning it is attached to the three EN pins of the voltage regulators.
If the RESET pin is left floating, its signal is what I would expect.
I initially thought that the RESET pin cannot source enough current to drive the three EN pins, but the datasheet says 8mA max on RESET pin, and trying to drive the EN
pins with a power supply it draws less than 1mA, so clearly this is not the issue.
Any idea why this is happening?
I condensed all this info in diagrams.png.
I was troubleshooting something else before this issue, and in doing so I reflowed the area at least a dozen times at 250 °C.
Is it possible that to much heating/cooling cycles have cooked the component such that it results in this behaviour? Everything else on the board is working absolutely fine.
Thanks