Remote updates with A/B partitions
Firmware is updated without collecting devices from the field, and a failed update rolls back to the previous image. Across a fleet of hundreds, this is the detail that makes the project possible at all.
← All products
IoT Hardware
In the fieldWe design the device too
ESP32 + LTE Cat M1 + GNSS, door and state sensors, remote firmware updates. The device is designed to speak the platform's language, so there is no integration project in between.
- ~15 months
- on one charge at 2 events a day (93µA sleep)
- FOTA
- A/B partitions, remote updates with rollback
- Lossless
- persistent queue while out of coverage
What it does
In the field there is rarely a device that fits the need exactly: the sensor you want is missing, the battery life does not match the duty cycle, or the data format does not fit your system at all. We build the device starting from the scenario — hardware selection, firmware, data path and dashboard come from one place. The result is meaningful data on the dashboard the day the first packet arrives.
Inside the device
Let us open the case.
What is inside the box that goes out to the field? Pull the slider and the layers separate.
How it works
- 01
From scenario to hardware
Which event must be caught, which sensor does it need, how many months must the device run on one charge? Hardware is selected or designed from those three answers.
- 02
Firmware on a shared core
The core, the hardware abstraction layer and the modem driver are shared, so a new device is not written from scratch. A new model is a configuration, not a new product project.
- 03
The device type is declared to the platform
A manifest and schema define fields, the IO map and wake reasons, each mapping to something the platform understands. It shows up on the dashboard the day the first packet lands.
- 04
Rollout and maintenance
Remote firmware updates, remote configuration and device health monitoring. Nobody has to drive out to the device twice.
Highlights
No data lost when the link drops
Out of coverage the device queues events to persistent storage and drains the backlog in order once the link returns.
Event-driven sleep, long battery life
The device sleeps when nothing happens and wakes on triggers such as a door opening, or on a periodic check. Roughly two months on one charge in a typical trailer scenario.
Tested without real hardware
A simulation environment and host-side unit tests exercise the whole chain before anything ships. Hardware lead times stop blocking software.