C3F
The software foundation that runs on every SPIDEX device. C3F abstracts what is underneath and gives every device — gateway, sensor, bridge or tracker — the same model for communication, control, telemetry and lifecycle.
C3F turns devices into software-defined platforms.
What the framework provides.
Hardware abstraction
One interface model across device platforms. Application code stops caring which board it is running on.
Communication
MQTT, BLE, UART, SPI, I²C, RS485, Ethernet and further protocols handled through a common transport layer.
Device control
Commands, parameters and configuration delivered and acknowledged through a single control path.
Telemetry
Readings are normalised at the device, so the same measurement means the same thing across a mixed fleet.
Diagnostics
Structured logs, health status and remote diagnostics built in rather than bolted on before shipping.
Security
Device identity, credential handling and encrypted transport as a framework service, not a per-product task.
Firmware lifecycle
Versioning, staged rollout, verification and rollback handled the same way on every device family.
Extensibility
Capabilities ship as reusable modules. What one product needs becomes available to the next one.
Cloud integration
Designed to pair with SPIEngine, and to speak to external platforms over standard protocols.
How C3F is layered.
Each layer depends only on the one below it, which is what makes a device portable between boards and a module portable between products.
Application services
Product behaviour, expressed against a stable device model.
Device services
Telemetry, control, configuration, diagnostics, firmware, identity.
Protocol layer
MQTT, BLE, Modbus, RS485, Ethernet, UART, SPI, I²C.
Hardware abstraction
One interface model across boards, radios and peripherals.
Platform / OS
Embedded Linux or RTOS, depending on the device class.
The same task, with and without a framework.
| Task | Without a shared framework | With C3F |
|---|---|---|
| Add a new sensor type | New driver, new parsing, new telemetry shape | Sensor profile added as a C3F module |
| Ship a firmware fix | Per-product build, manual distribution | Staged rollout through the shared update path |
| Support a second board | Port application code to new hardware | Hardware abstraction handles the difference |
| Add device security | Re-implemented per product, reviewed per product | Framework service, reviewed once |
| Diagnose a field failure | Ad hoc logs, site visit | Structured diagnostics and remote session |
| Onboard a new product line | Rebuild the stack, then start the product | Start at the product |
Open where it matters.
C3F speaks standard protocols and integrates with external systems, PKI and cloud platforms. SPIDEX does not currently publish C3F as an open-source project — where that changes, it will be stated here plainly rather than implied.
Put a working device foundation under your next product.
Bring us the device you are planning. We will map which C3F capabilities apply directly and where work would still be needed.