Commercial IoT electronics, designed to be built. We take LoRaWAN and related wireless products from block diagram to tested prototype: radio and battery first, schematic capture, PCB layout with antenna keep-out, and design-for-manufacturing checks on every revision.
Deliverables: Schematics (PDF and source), PCB layout files and library parts, Gerbers, drill files, assembly drawings
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.
Deliverables: Documented source, Build system, Test suite
Enclosures for wall, ceiling, DIN, pole, and outdoor IoT nodes. Antenna window, gasket, and battery holder are designed as one assembly with the radio — not a pretty box that kills range. Print and CNC before anyone cuts steel.
Deliverables: 3D models, 2D drawings, CMF spec
SMT, assembly, and functional test for the same LoRaWAN and IoT products we design — fixtures written for that radio and payload, not a generic ICT recipe. When a node fails join or a gateway drifts, the person who laid out the board is in the conversation.
Deliverables: Assembled boards and finished goods as scoped, Test fixtures and scripts, Yield and failure notes
One file set, four disciplines
Schematic, PCB, and 3D-print tiles are public examples (Wikimedia Commons). Workshop photos show the floor — no generated box diagrams.
A LoRaWAN node or gateway first. Schematic, firmware, housing, and the line in service of that product.
End node
MCU, radio, battery, and enclosure on one base. Partners add the measurement set, payload, and brand. Sleep current and regional band (EU868 / US915 / AS923) are planned before the first schematic — not patched after a quote.
You leave with: Node architecture, radio plan, battery budget
Continue this thread04 · 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 thread
Buildings
CO₂, VOC, temperature, humidity in a published uplink. Ceiling or wall housing, configurable intervals, and CMF that looks like a commercial product — not a lab box with a sticker.
You leave with: Payload map and housing starting points
Continue this thread08 · SMT, assemble, test
The file set the engineer signed is the file set the line runs. When a board fails, the person who laid it out is in the same conversation — not on a purchase order.
You leave with: Pilot units, fixtures, yield notes
Continue this thread
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.
Building sensing
Indoor air quality and environmental sensing — CO₂, VOC, temperature, humidity — with LoRaWAN payloads partners adapt for BMS and building automation.
Network edge
Gateway hardware as a customizable platform — regional band, backhaul, enclosure, and antenna — so partners ship network edge devices under their brand.
Software platform
Device models, APIs, and application building blocks partners brand and run — ParticLIO does not operate customer networks or host your production stack.
Anonymous project notes — problem, what we did, what the partner kept. No customer names.
Problem. An outdoor environmental node needed IP-rated housing. The first ID concept boxed the antenna and killed range.
What we did. Electronics and industrial design sat in one review: antenna keep-out, gasket, and wall thickness. 3D print for feel, CNC for RF and fit, then mold-ready CAD.
What they kept. A housing that still meets the radio budget. The partner owns the CAD, keep-out drawing, and DFM notes.
Problem. A facility node needed extra I/O and a different battery than the reference. The team did not want to buy a steel tool on an unproven layout.
What we did. Schematic and layout with RF and battery isolation on pass one. Automated DFM, then a small SMT run and bring-up report.
What they kept. Working prototypes and a file set (Gerbers, BOM, pick-and-place) ready for pilot — without a second vendor re-learning the board.
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.
Problem. A campus rollout needed Ethernet indoor units and a pole-mount outdoor unit on the same band plan.
What we did. Shared concentrator and backhaul options; two enclosures and antenna kits. Onboarding notes for the LNS they already run.
What they kept. One radio family, two install SKUs, documentation they keep. We do not operate the network.
When we design your hardware, we're already planning the firmware that boots it, the enclosure that protects it, and the line that builds it. That's the difference between four vendors and one team — and it shows up as fewer respins, faster milestones, and one number to call.
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