Firmware for industrial sensors and gateways
Industrial devices are fitted to machines that run for decades and owned by people who plan downtime months ahead. The firmware has to fit both.
Key characteristics
- Service life
- Often longer than any one RTOS release
- Typical links
- LTE-M, NB-IoT, LoRaWAN or the plant network
- Updates
- Scheduled into the site's maintenance windows
- EU market
- CRA reporting duties apply since September 11 2026
Industrial IoT covers vibration sensors on pumps, temperature and current monitors on motors, tank-level sensors, and the gateways that collect their readings. Many are retrofits: battery-powered devices clamped onto machines that were never designed to be connected, sold to plants that will not let a startup touch their control systems. They are expected to run for many years, and the people who own them care much more about the machine than about the sensor.
That shapes the firmware. It has to last, survive radio conditions inside steel buildings, and accept updates only when the site says so.
Long service lives
An industrial sensor can outlive the RTOS release it shipped on, the cellular module’s firmware, and sometimes the startup’s first cloud architecture. Plan for that from the first release:
- Choose a software base with long support and write down when you will move to the next one. Our RTOS selection worksheet scores long-term support and security fixes as a criterion, and sustaining releases covers the migrations.
- Version everything. Hardware revisions change over a long production life. A version scheme that includes the board revision stops the wrong image reaching the wrong unit; draft one with the version scheme builder.
- Plan for key changes. Over ten years you may need to replace a signing key. Decide now how a device will learn to trust a new key through a signed update, and who holds the old one meanwhile. See firmware security.
- Keep data formats migratable. Settings and calibration stored on the device need a version number, so a new release can read and convert what an old one wrote.
Choosing the link: LTE-M, NB-IoT or LoRaWAN
LTE-M (3GPP eMTC) and NB-IoT are low-power cellular technologies from 3GPP Release 13. LoRaWAN is a low-power wide-area network that runs through gateways you install or a network operator provides. Wired gateways sit on the plant network. Each changes how updates work.
| Link | What it means for updates |
|---|---|
| LTE-M or NB-IoT | Every byte is billed by a carrier, so full images to a large fleet cost real money; check carrier coverage and module support at each site before you commit |
| LoRaWAN | Small payloads and limited airtime make full-image updates slow; plan for small images, delivery in chunks, or an update route through a gateway or a local link |
| Plant network through a gateway | Bandwidth is rarely the problem; the site’s network and security policies are |
Signal inside metal enclosures and buildings varies a lot, so measure at real sites before fixing the design. Our connectivity work includes measured throughput and current, and the over-the-air data cost calculator puts a price on each rollout.
Update windows
Industrial customers schedule maintenance windows and expect suppliers to respect them. The update path should let the device download a new image in the background while it keeps measuring, then apply it only inside an agreed window, with a clear record of what changed. Gateways in particular should never reboot mid-shift without approval.
We write the rules down before the first release with the update policy worksheet: who can approve a release, which sites and devices get it first, which windows apply, what signals stop a rollout, and how a device rolls back. Rollouts then go out site by site, starting with your own test units, so a problem stops at one plant instead of all of them.
The EU Cyber Resilience Act
If you sell in the EU, the Cyber Resilience Act (Regulation (EU) 2024/2847) applies to products with digital elements, including industrial ones. As checked on November 22, 2026:
- Reporting duties have applied since September 11, 2026. Actively exploited vulnerabilities and severe incidents get an early warning within 24 hours and a notification within 72 hours, through the CRA Single Reporting Platform set up by ENISA.
- The main obligations apply from December 11, 2027. They include a support period of at least five years unless the product is expected to be in use for less, security updates provided free of charge unless otherwise agreed for a tailor-made product with a business user, and an SBOM covering at least top-level dependencies.
In the US, the FCC’s voluntary Cyber Trust Mark excludes products primarily used for manufacturing, industrial control or enterprise applications, so it is unlikely to be your label. This is not legal advice; confirm how each rule applies with a qualified adviser.
We do not declare products compliant. We produce the evidence a manufacturer needs: an SBOM per release, a vulnerability intake and triage process, a written support-period statement, a signed update path with tested rollback, and a runbook for the 24-hour and 72-hour reporting clocks.
Where to start
Request a firmware review. We read your schematics, code, flash layout and update plan, look at the link and the sites you are targeting, and send a written plan with the risks and the order of work. The connectivity and power section of Field Update goes deeper on links and batteries.
Send us your board and your plan.
A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.
Or email sales@fumbar.com, or call (720) 675-4202.