← Back to the chapter · Previous detail · Next detail →
Technical detail · Power Consumption Analysis
Quantify scope and sampling errors
A boundary error can be larger than the optimization being reviewed. Suppose the isolated MCU rail measures 8 uA in sleep, but the product rail also includes a 25 uA regulator, a 12 uA standby sensor, and 6 uA of pull-up leakage. The deployed sleep baseline is 51 uA, not 8 uA. Over a 30-day bench interval, that missing 43 uA x 720 h = 30.96 mAh is already more than many design-review margins.
Sampling resolution is another boundary. A meter that averages over one-second windows can hide a 120 mA, 200 ms transmit burst inside a calm-looking trace. For state budgets, reviewers need enough bandwidth to capture peaks and enough interval logging to prove the quiet states stay quiet.