Check: Trace and lifetime evidence

Knowledge check · self-test
Check: Trace and lifetime evidence
Review firmware markers, profiling order, cycle charge, lifetime limits, and measurement errors.
Review firmware markers, profiling order, cycle charge, lifetime limits, and measurement errors.
Checkpoint: Trace Interpretation {.depth-l0}
You now know:
- A useful trace includes sleep baseline, wake, sensor stabilization, data acquisition, processing, radio activity, shutdown, and return to sleep.
- Multiple cycles plus GPIO markers reveal retries, maintenance tasks, timers, and code phases that one clean cycle can hide.
:::
::: {.callout-tip}
##
Checkpoint: Lifetime Evidence {.depth-l0}
You now know:
- Charge per useful cycle is the evidence that connects a current trace to a battery-life estimate.
- In the 10-minute example, the radio event contributes 46.7 uAh out of about 52 uAh, so it dominates the average.
- The rough 256-day estimate still needs battery derating, temperature effects, self-discharge, and reserve margin.
:::
Back to Energy Measurement and Profiling: Validate across operating conditions