ESP32 E-Paper Power Consumption: Measure Battery Life
E-paper can retain a static image without refreshing, but the ESP32 board, driver circuit, regulator and radio can still consume power. Estimate battery life from the complete system rather than a panel standby figure or an ESP32 chip-only deep-sleep value.
Measure at the battery input
Use one measurement boundary for the current readings and the battery capacity. Record startup, Wi-Fi connection, data transfer, display update and sleep. Check that the instrument can capture both sleep current and brief active peaks without causing excessive voltage drop. Disconnect external USB power if it bypasses the battery path.
A transparent current-budget example
The following numbers are illustrative assumptions, not measurements of an ESP32S product. Assume the measured current at the battery input is 60mA for 8 seconds and 0.05mA for the remaining 3,592 seconds of an hourly cycle.
Average current = (60 mA × 8 s + 0.05 mA × 3592 s) / 3600 s
= 0.1832 mA
Illustrative usable capacity = 800 mAh
Idealized runtime = 800 mAh / 0.1832 mA
≈ 4366 hours ≈ 182 days
This simplified estimate excludes further aging, self-discharge, temperature and changing operating conditions. If the measurements are taken on a regulated rail instead of the battery input, include voltage conversion and efficiency using an energy budget; do not divide battery mAh by an unrelated rail current.
What to investigate when sleep current is high
| System part | Useful check |
|---|---|
| Development board | Regulator quiescent current, power LEDs and USB bridge |
| Display adapter | Whether the documented sleep/power-down sequence actually completes |
| ESP32 | Actual sleep state, enabled wake sources and application behavior |
| Signal connections | Possible back-power paths when one rail is disabled |
| Radio | Reconnect time, retries and transfer duration at the intended installation |
Choose signal states and power switching from the complete schematic. A generic “set every SPI pin to pull-down” rule is not appropriate for every controller. A raw panel still needs drive circuitry; bypassing that circuitry to connect the panel directly to a battery is not a low-power solution.
Reduce active energy as well as sleep current
Cache unchanged data, avoid unnecessary network retries and update the display only as the application requires. Evaluate partial updates only where the panel supports them, using the manufacturer/library sequence. Faster refresh and lower average energy are not automatically the same result. Check the supply during current peaks as well as over a complete cycle.
Keep a reproducible test record
Record the board and panel revisions, battery type, measurement boundary, firmware, wake interval, network conditions, active duration and sleep current. Re-measure after changing a regulator, driver board or library. A one-year target is a design requirement to verify, not an automatic property of an e-paper screen.
Continue with the ESP32 e-paper overview, the refresh guide and 2.9-inch E-Paper: GDEY029T94 / ESP32 or 4.2-inch E-Paper: GDEY042T81 / ESP32 for panel-specific setup.
