- 20+
- Sensor & Actuator Classes
- 8+
- Radio & Network Paths
- 12+
- Protocol Integration Options
- Legacy + LAB 4.0
- Factory Data Gateway Fit
Modular by Contract, Not by Convention
Most microcontroller firmware becomes device-specific and difficult to scale. Sensor wiring, protocol handling, and control logic get tightly coupled, making integration expensive for growing teams.
o-OS enforces one Hardware Abstraction Layer for every module. Ownership tokens prevent peripheral conflicts, and the EventBus connects modules without hard coupling. The result is a portable IoT foundation for sensor ingestion, local control, and integration with legacy systems and LAB 4.0 workflows.
- One HAL contract — move from one MCU board profile to another with minimal application changes
- Gateway-ready architecture — ingest sensor data, trigger actions, and expose operations to external systems
- SMB-friendly implementation — lower integration cost for logistics, production, and industrial monitoring
One Platform, Any Industry
o-OS follows the same ten-vertical architecture model and is currently active for Forge, Care, Serve, and Move — with gateway-first patterns for industrial monitoring and control.
o-Forge
Machine, line, and quality telemetry on one industrial IoT layer
o-Care
Clinical devices and ward operations connected for safer care
o-Serve
Cold-chain, kitchen, and delivery signals synchronized in real time
o-Move
Fleet, warehouse, and shipment data integrated edge-to-cloud
One Contract, Four Responsibilities
o-Core
The kernel and orchestration layer: deterministic tick, static EventBus, ownership-token allocation, and system lifecycle control for reliable monitoring and automation workloads.
o-Control
Control and routing: event-driven input handling, command dispatch, application workflow orchestration, and policy hooks for industrial control scenarios.
o-Sense
Sensor intelligence: plug in environmental, motion, location, and process sensors through a common contract to normalize data for monitoring, alerts, and reporting.
o-Device
Device and connectivity layer: display/audio drivers plus extensible interfaces for WiFi, BLE, LoRa, wired buses, and field peripherals for real-world IoT deployments.
How o-OS Works
-
Deploy
Start from the Cardputer ADV reference build, then deploy the same architecture to your target microcontroller profile with minimal board-specific changes.
-
Boot
o-Core initialises the HAL contract, allocates ownership tokens to all modules, and brings up the EventBus before any user code runs.
-
Capture
o-Sense and o-Control capture sensor and operator inputs, normalize event streams, and route them into local logic or upstream monitoring pipelines.
-
Integrate
o-Device bridges radio, fieldbus, and serial channels so legacy equipment and modern services can exchange telemetry, status, and control signals.
-
Operate
Run monitoring and control loops continuously, then expose key data to dashboards and workflows, including logistics and production flows in LAB 4.0.
Six Engines. One Architecture.
EventBus
Deterministic publish-subscribe backbone for telemetry, alerts, and control events, designed for robust operation on constrained MCU targets.
HAL Ownership Tokens
Conflict-free peripheral governance across sensors, radios, and actuators. Compile-time ownership checks keep field deployments predictable and safe.
Edge UI & Diagnostics
Lightweight local interface and diagnostics pipeline for on-device status, commissioning, and troubleshooting at the machine edge.
Multi-Protocol Connectivity
Unified connectivity abstractions for WiFi, BLE, LoRa, serial, and field buses to support diverse integration requirements across industries.
Portable Deployment Model
Reference implementation runs on Cardputer ADV today, with board-profile portability for broader MCU fleets and staged rollouts.
Legacy & LAB 4.0 Bridge
Map machine signals into standardized events that can feed legacy operations software and LAB 4.0 dashboards for better end-to-end visibility.
What Is Inside
| Reference Hardware (Current Build) | |
|---|---|
| Device | M5Stack Cardputer ADV |
| SoC | ESP32-S3 |
| Display | ST7789, 240×135 px |
| Keyboard | TCA8418 |
| IMU | BMI270 |
| Storage | 4 MB internal flash + microSD (SPI) |
| Audio | ES8311 / I2S |
| Radio | WiFi + BLE on-chip; LoRa/NRF/GPS via expansion |
| Portability | Board-profile approach for migration to additional MCU targets |
| Runtime | |
|---|---|
| Language | C++ (Arduino framework) |
| Partitions | TEST (launcher) + ota_0 (user app) |
| Frame rate | 30 FPS (~18 ms/frame) |
| EventBus | 8 subscribers/type (static) |
| AppRegistry | 12 fixed slots + SD scan |
| Industrial integration | Gateway pattern for legacy systems and LAB 4.0 ingestion |
| Build tool | VS Code + Arduino IDE |
Roadmap
-
Foundation Release
Core kernel, EventBus (8 subs/type), HAL ownership tokens, lightweight runtime, and reference deployment on Cardputer ADV.
-
Protocol & Gateway Expansion
Expanded sensor adapters, stronger protocol coverage, and hardened gateway flows for production monitoring and control.
-
Cross-Board Scale-Out
Port to additional MCU families, extend protocol adapters, and deepen integration into logistics and production workflows in LAB 4.0.
Build on o-OS
Build on o-OS
Fork the repo, deploy on your target microcontroller, and build a modular IoT gateway for monitoring and control in production and logistics.