1. Start with a known device
Pick a preset that behaves like the node you are designing. The first estimate should be simple and visible.
Build an IoT power budget from sleep current, short active bursts, radio time, battery derating, and target lifetime.
A power budget turns tiny sleep currents and short radio bursts into one daily energy number. Change the design, watch the duty cycle move through a compressed day, and decide which part deserves engineering effort first.
Pick a preset that behaves like the node you are designing. The first estimate should be simple and visible.
The timeline is time-compressed so short wake, sense, process, and transmit stages can be seen clearly.
The bars show mAh per day. The largest bar is usually your first optimization target.
Efficiency, temperature derating, reserve, and self-discharge can change a good load estimate into a poor field estimate.
Most of the calendar time is spent here.
--Clock startup and sensor power-up.
--Measurement hardware is active.
--MCU formats and validates the reading.
--Transmit, receive, join, or retry cost.
--Use Play or Step to follow one reporting cycle. Bar lengths below the timeline are based on daily energy, not visual stage width.
Each bar is calculated from current multiplied by total seconds per day.
Convert each current burst into daily charge.
mAh/day = current_mA x seconds_per_day / 3600
Average current is daily charge spread over 24 hours.
I_avg = total_mAh_per_day / 24
Efficiency matters when converting load energy to battery energy.
Wh/day = load_mAh_day x rail_V / 1000 / efficiency
Usable battery energy is nameplate capacity after derating and reserve.
days = usable_battery_Wh / battery_Wh_per_day
mAh is charge at a voltage. This animation calculates load mAh/day, converts it to load Wh/day at the selected rail voltage, then divides by regulator efficiency to estimate battery Wh/day.
Nameplate capacity depends on chemistry, temperature, discharge rate, cutoff voltage, aging, and pulse load. The derating and reserve controls are first-order correction factors, not substitutes for a datasheet and lab test.
A device can have a low average current but still fail if the battery or regulator cannot supply radio peaks without voltage droop. Check peak current separately from lifetime.
Go deeper into battery drain curves, self-discharge, target life, and charge per wake cycle.
Compare idle, light sleep, deep sleep, and hibernate against wake latency and duty cycle.
Inspect measured current profiles and find which phase consumes the most energy.