Loading
Preparing Engineering Confidence
We're loading the requested content. This should only take a moment.
Loading
Preparing Engineering Confidence
We're loading the requested content. This should only take a moment.
Why bench instrumentation and network emulation must be combined before you can decide whether a device should infer locally or send raw data.
A cellular module with a sleep floor of 3.2 µA can sit on a carrier board that draws 39 mA doing nothing. Both figures come from the vendor. Both are correct. The ratio between them is roughly 12,000 to 1, and which of them governs battery life depends on what the rest of the board does while the module sleeps.
That gap is one of four reasons datasheet figures cannot settle a question most connected-device teams answer from datasheets anyway: should a battery-powered device run inference locally and transmit a result, or transmit raw data and infer elsewhere?
TB-2026-001 sets out what a measurement environment has to provide before that question can be answered from measurement rather than assumption. It reports no results. Those follow through the Engineering Readiness Series.
Module datasheets publish current per operating mode. Those figures are accurate, and they are not the numbers the decision needs.
Transmit current assumes a link condition that is never stated, because uplink power is set by the network through closed-loop power control. NB-IoT and Cat-M1 extend coverage by repeating transmissions, so the energy cost of a message is a property of the message and the link condition together, not of the message alone. For small payloads, connection establishment and the release tail can cost more than the payload itself. And sleep floors, which dominate the budget for a device reporting once an hour, span five orders of magnitude against transmit bursts.
A three-month field study of thirty NB-IoT nodes across more than twelve hundred locations found energy consumption imbalanced by up to 75 to 1 between nodes running identical workloads. The variable was coverage, not code.
Cellular energy metrology measures module current against a base station emulator. The network is controlled; there is no compute workload.
Edge inference metrology measures per-inference energy using shunt isolation and GPIO triggers. The compute is rigorous; there is no network.
Live-network measurement captures both, but the measuring party controls neither the propagation environment nor the operator's power-saving timers. A result from Tuesday afternoon cannot be reproduced on Wednesday morning, or by anyone else anywhere else.
The brief states its own limits in a dedicated section. No real propagation. No operator-specific network behaviour. No cross-vendor generalisation from a single module. No substitute for field trials.
A method described without its limits is marketing.
Related Publications
Radianode provides independent validation for connected, wireless and embedded systems. If you are making an architecture decision that rests on a battery life claim, talk to an engineer.