IoT and remote telemetry
Devices that go out once and are expected to work for a decade without anyone visiting them.
Evidence
What we can substantiate
Everything below is work we have actually done, described at a level that respects the client’s confidentiality. If you need detail, ask under NDA.
- Energy budgets that survive contact Measured whole-board sleep current, not the datasheet figure — the gap between them is where deployments fail
- Link budgets before enclosures Antenna placement and detuning modelled while the mechanics can still change
- Update paths designed in Signed images, rollback protection and a recovery partition, decided at schematic stage
- Duty-cycle compliance Sub-GHz airtime planned against regional limits rather than discovered afterwards
Common questions
Straight answers
Why do IoT devices miss their battery targets so badly?
Because the calculation is done on datasheet sleep currents and the board does something else. A regulator with high quiescent current, a floating input, a sensor that never enters standby, or a converter that is 50% efficient at microamps will each cost more than the radio. We measure the assembled board rather than trusting the arithmetic, and the first prototype almost always reveals something. Our battery estimator models all four of those effects.
Does the Cyber Resilience Act apply to a simple sensor?
Almost certainly, if it connects to anything and is sold in the EU. The scope is "products with digital elements", and indirect connections count — a wired sensor reporting to a gateway is in scope. The expensive requirement is the secure update path, because it is fixed by hardware decisions made in the first schematic. Our CRA scoper walks the classification in eight questions.
Got a board to design — or one that won’t boot?
You talk to the engineer who would do the work. Reply within one business day, and we’ll sign your NDA before you go into detail.