IoT firmware development for LoRaWAN join, payloads, and OTA — you run the network server.
Embedded firmware for Commercial IoT: LoRaWAN join, Class A/C, ADR, payloads, provisioning, and OTA — written next to the circuit it boots. You run the network server. We do not host it.
Bare-metal and RTOS firmware for commercial IoT: boot, sensors, radio, power states, and field diagnostics. Written next to the schematic, not after it.
Join credentials, key handling, and factory provisioning so devices arrive ready for your network — not a pile of identical blanks.
Payloads, MQTT or HTTP hooks, and the glue that lands device data in the stack you operate. We do not run your network server.
Companion apps for install, pairing, and field checks when the product needs a phone in the loop.
Over-the-air update paths designed with battery and radio constraints, so field devices can stay current without a truck roll.
AI-assisted test coverage and validation planning before pilot — so bring-up scripts match what the hardware can actually do.
The drawing, then the floor that proves it.
04 · Firmware
Bare-metal or RTOS, join and payload, OTA planned against the battery. The dashboard or BMS you run gets a documented uplink map — we do not host your network.
You leave with: Source, payload notes, test suite
Continue this threadTest coverage
AI-assisted test coverage plus fixtures written for that product. Radio, sleep current, and OTA are measured against the architecture.
You leave with: Test suite and scripts
You host it
Payload maps, APIs, and optional companion UI. Starting views you brand — ParticlIO does not operate the LNS.
You own the source at every milestone. We write the code that runs on your device and the systems that keep it current in the field — engineered alongside the hardware, not after it.
You own every design file — at every milestone, not just at the end.
Anonymous project notes — problem, what we did, what the partner kept. No customer names.
Problem. The same end-node family had to join EU868, US915, and AS923 networks with one payload map.
What we did. Firmware variants on a shared radio stage: join, ADR, and documented uplink fields. Current draw measured against the battery budget.
What they kept. Band SKUs the partner flashes and points at their own network server. Payload notes stay with them.
Problem. A life-safety reseller needed their name on a battery LoRaWAN smoke/CO device, with CE and EN 14604 scoped for the market — not a generic box.
What we did. Started from the fire-alarm product line. Brand, CMF, pack-out, and alarm payload mapped to their monitoring stack. Marks planned per SKU, not as a company stamp.
What they kept. Pilot units under their brand, plus a certification plan they can take to the next market.
Problem. A building team had wireless CO₂ / VOC sensors that joined a network but arrived as undocumented bytes.
What we did. IAQ platform firmware with a published uplink map (CO₂, VOC, temperature, humidity, status) and configurable intervals. Ceiling housing and CMF for commercial interiors.
What they kept. Devices the partner points at their LNS and BMS. They own the application layer; we own getting the hardware and payload right.
Sensor node, fire, IAQ, gateway, and an IoT software layer. Start here when you do not want a blank schematic.
Hardware platform
A proven end-node platform — MCU, LoRaWAN radio, power path, and enclosure options — so partners add sensors, branding, and payloads instead of starting from a blank schematic.
Fire safety
Smoke, CO, heat, and related alarm hardware as a product line partners customize — housing, marks, and panel integration — while we handle LoRaWAN and manufacturing.
Software platform
Device models, APIs, and application building blocks partners brand and run — ParticLIO does not operate customer networks or host your production stack.
Services, Process, and Why ParticlIO — then Contact Us so an engineer can read your brief.
IoT hardware design and manufacturing — PCB, firmware, enclosure, and assembly in one flow.
See servicesOne team for OEM/ODM LoRaWAN — design-house depth with manufacturing follow-through.
Why ParticlIO