ESP32 LiPo/Reading the battery/13. When it will not run on battery
Reading the battery · 13 of 13

When it will not run on battery

Four ways this kit fails on battery — dead, resetting when Wi-Fi starts, a cell that never charges, and heat in the first few seconds — and the order to check each in. The first check is usually the answer, and a meter settles the rest.

Four symptoms

Four ways it fails on battery, and where to look
Dead on battery, fine on USB
  1. Shield switch at ON
  2. Cable from TO ESP32 to the board, red to +
  3. Cell in LIPO BTT, red to the + mark
  4. Plug USB in for a minute to wake a cell whose protection has tripped
What it does
Dead on battery, fine on USB. The commonest cause is the switch, then the cable to the board. A protected cell that was run flat shuts itself off and looks dead until a charger wakes it.

Each list starts with the check that finds the fault most often and costs least. Two faults sit behind most of them: the switch and cable between the shield and the board, and a cell that is lower than it looks.

Two readings settle it

With a meter on DC volts:

  1. The cell, at the back of the LIPO BTT socket. 3.0–4.2 V is a cell with something in it. Under 3.0 V, charge it. 0 V means its protection circuit has switched it off, and a charger usually wakes it.
  2. 3V to GND on the shield, switch ON, USB out. 3.3 V means the board is running from the cell. 0 V with a good cell means the path between them is open: the switch, the TO ESP32 cable, or the cell in the wrong socket.

A reading somewhere in between — 2.8 V on the 3V pin, say — is a cell too low to hold the rail, and from the cell to 3.3 V is why.

When to give up on a cell

Put a cell aside for good if it has swollen, if it got hot while charging, or if it will not hold above 3.0 V a day after a full charge. Take it to battery recycling rather than the bin: a lithium cell with any charge left can still start a fire when crushed.

When it does not work

The cell reads 0 V at its plug

Its protection circuit has switched it off, usually after it was run flat. Connect it and plug in USB: the charger normally wakes it within a few minutes. If it still reads 0 V after an hour on the charger, the cell is finished.

The shield's fuse keeps cutting out

Something on the wiring draws too much or is shorted. The PPTC resets by itself once it cools, usually within a minute of the fault being removed. Unplug everything from the shield's terminals and add it back one wire at a time.

It runs on battery for a minute, then stops

The cell is nearly empty and sags under load until the board resets. Charge it for an hour and read it with the read-the-cell sketch before trusting it again.

Where this goes next

The chip this board is built around, asleep: how a battery project lasts for months.

Deep sleep and wake sources

Edit this page — content/books/esplipo/when-it-will-not-run-on-battery.mdx

Community

Questions about this product

See what other owners have asked, and read their solutions.

Ask a question ↗

ESP32 LiPo Dev Kit: 3 Boards with LiPo Charger + 3 Shields

Loading discussions…

Discuss this article

Ask about this page. The answer stays here, on the page it belongs to, for whoever hits the same wall next.

Browse Modules and blocks on the forum