Estimate battery life from sleep and wake currents
Enter your battery, your sleep current and how often the device wakes. The calculator shows the average current, where it goes and how long the battery should last.
Key characteristics
- Inputs
- Capacity, sleep current, wake-ups, radio events, self-discharge
- Outputs
- Average current, share per state, life in hours, days and years
- Default example
- Fictional LW-1 soil probe on two AA lithium cells
- Runs
- In your browser with nothing sent
Calculator: Estimate battery life from sleep and wake currents
Battery life comes down to a handful of numbers: how much current the device draws asleep, how often it wakes, how long each wake-up lasts and what it draws while awake. This calculator combines them into one average current and divides your usable capacity by it. It also shows which state uses the most charge, which tells you where an hour of firmware work will pay off.
How to use it
- Enter the battery’s rated capacity and the share of it you can count on.
- Enter the sleep current you measured, not the datasheet’s best case.
- Describe the two kinds of activity: sensor wake-ups and radio events.
- Add the battery’s self-discharge, then read the results.
Change one input at a time and watch the shares. If the radio takes 60% of the average, halving the sleep current barely moves the result.
What each input means
| Input | What it means | Where to get a real number |
|---|---|---|
| Battery capacity | Charge the cell delivers at your load, in mAh | The cell maker’s datasheet, at a current close to yours. Two cells in series give twice the voltage, not twice the mAh |
| Usable share | How much of that capacity you can rely on | Your circuit’s cutoff voltage, the coldest temperature you must support and the spread between cells |
| Sleep current | Draw with everything in its lowest state | A measurement on a real board over several minutes, radio idle, sensors off, debug probe disconnected |
| Sensor wake-ups, time awake, current while awake | One measurement cycle: wake, power the sensor, read, store, sleep | A current trace of one cycle; the average current is the area under the trace divided by its length |
| Radio events, time per event, current | Advertising or connection events with a phone or gateway | The same kind of trace over a few events; the count per hour follows from your advertising or connection interval |
| Self-discharge | Charge the cell loses on its own each year | The cell maker’s datasheet for your chemistry and storage temperature |
Reading the default example
Example (fictional). Loamwick’s LW-1 soil probe runs on two AA lithium cells, entered as 3,000 mAh with 85% usable. It sleeps at 4 µA. It wakes 12 times an hour (one reading every 5 minutes) for 150 ms at 3.2 mA, and has 3,600 radio events an hour of 2.5 ms at 6 mA. Self-discharge is 1% a year. The calculator gives an average current of 24.0 µA: the radio is 62.5% of it, sleep 16.6%, self-discharge 14.3% and sensor wake-ups 6.7%. Estimated battery life is 106,194 hours, which is 4,425 days or 12.1 years.
Two things stand out. First, the radio dominates. If Loamwick wants more margin, the place to look is how often the probe talks to its gateway, not the sensor code. Second, 12.1 years is far beyond the 3-year target in Loamwick’s firmware requirements worksheet. That does not mean a probe will last 12 years. At a current this low, the real limits are the ones the calculator does not model: winter on the plains, the cell’s shelf life and the voltage at which the circuit stops working. Read it as room in the budget, not a number to print on the box.
How it calculates
The calculator works in one-hour slices. Each active state contributes its current multiplied by the share of the hour it is on. Twelve wake-ups of 150 ms are 1.8 seconds, or 0.05% of the hour, at 3.2 mA: 1.6 µA on average. The radio is on for 3,600 × 2.5 ms, which is 9 seconds or 0.25% of the hour, at 6 mA: 15 µA. The sleep current applies to the rest of the hour: 3.988 µA. Self-discharge is spread evenly over the year: 1% of 3,000 mAh is 30 mAh a year, about 3.4 µA. The four add up to the average current, and battery life is the usable capacity (2,550 mAh here) divided by that average.
Limits
- Pulses are averaged away. A radio event that averages 6 mA may peak much higher. Some cells deliver less capacity at high pulse currents, and an ageing cell can dip below your brownout voltage during a pulse even when the average looks fine.
- Temperature is not modeled. Capacity and self-discharge both change with temperature. Use the usable share to cover your coldest and hottest cases.
- Rare events are missing. Firmware updates, retries when the gateway is out of reach and long error states can each cost more than a normal day. Average them over a month and add them as radio events.
- It trusts your inputs. A sleep current copied from a datasheet, or measured with a debug probe attached, can be far from what a production unit draws.
What to do next
Measure before you commit. A current trace of one full cycle on a real board replaces most of the guesses above. If firmware updates will travel over Bluetooth LE, the BLE update time calculator shows how long the radio stays on for each one. Our low-power design service covers power profiling, sleep states and battery budgets on your hardware, and the connectivity and power section of Field Update covers radio duty cycles in more depth. Or request a firmware review to have your power budget read alongside your schematics and code.
Send us your board and your plan.
A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.
Or email sales@fumbar.com, or call (720) 675-4202.