Environment-monitor battery budget

Environment-monitor battery budget

animation
capstone
power
Try Change sample interval and press Calculate.
Observe Watch Battery Life and Status against the 7-day target.
Explain Explain why the 7-day target requires measuring the full active trace.

Technical boundaries. This optimistic screening case omits wake-up, sensor conversion, Wi-Fi association, DHCP, DNS, TCP/TLS/MQTT setup, display use, retries, regulator loss, and battery voltage sag. Its target ratio is not engineering margin.

Meeting the 7-day battery life target requires careful power budgeting. The calculation below is an intentionally optimistic screening case: it assigns 160mA to Wi-Fi transmit, 0.8mA to light sleep, 20mA to sensors, and only 200 ms to the whole active window every 5 minutes. A real budget must measure and include wake-up, sensor conversion, Wi-Fi association, DHCP, DNS, TCP/TLS/MQTT setup, display use, retries, regulator loss, and battery voltage sag.

Duty cycle calculation: Dactive=0.2s300s=0.000667 (0.067% of time)D_{active} = \frac{0.2s}{300s} = 0.000667 \text{ (0.067\% of time)}

Average current: Iavg=160mA×0.000667+0.8mA×0.999+20mA×0.000667I_{avg} = 160mA \times 0.000667 + 0.8mA \times 0.999 + 20mA \times 0.000667 Iavg=0.107+0.799+0.013=0.92mAI_{avg} = 0.107 + 0.799 + 0.013 = 0.92 \text{mA}

Battery life (2x AA = 3000mAh): Hours=3000mAh0.92mA=3261 hours=136 days\text{Hours} = \frac{3000mAh}{0.92mA} = 3261 \text{ hours} = 136 \text{ days}

With those best-case inputs, the arithmetic produces 136 days, or 19 times the target, but that ratio is not engineering margin for retries or display use because those costs were omitted from the active window. Measure the full active trace and substitute its charge before making a pass/fail claim. If the same unverified 200 ms assumption is reused for one-minute sampling, the screening result becomes 89 days; it remains a sensitivity example, not a battery-life prediction.

Back to the chapter