When the thing you need does not exist yet
Off-the-shelf covers most problems. For the rest we design the board, the enclosure and the power budget, and write the firmware that runs on it — then field-test it somewhere cold.
Where we work
Node and gateway hardware
Schematic through bring-up: radio front end, MCU, sensors, antenna matching and the enclosure it all has to live in.
- Radio and antenna design
- Sensor integration
- Enclosure and ingress rating
Power budgets
Sized for the worst week of the year rather than an average. Solar, primary cell or harvested, with the margin written down.
- Duty-cycle modelling
- Solar and battery sizing
- Cold-weather chemistry
Embedded firmware
The code on the device: radio stack integration, sleep behaviour, over-the-air update and the diagnostics you need when it is on a roof.
- MeshCore and LoRaWAN stacks
- OTA update paths
- Field diagnostics
Backend to match
The other end of the link, from the same people — ingest, decoding, storage and an API, so the device and the service are designed together.
- Ingest and decoding
- APIs and dashboards
- Fleet management
Designed together, because the radio and the console are one system
A firmware decision about sleep intervals is a backend decision about gaps in the data, and a backend decision about retries is a battery decision. Splitting them across two suppliers is how both get made badly.
Bring us the constraint
The distance, the power available, the temperature range, the thing that has to be measured. Constraints make better briefs than specifications.