Case study · Industrial IoT · 2025 - The plant in one data model: Modbus and MQTT
PLCs, sensors, and gateways speak different protocols. We folded them into one monitoring and control stack.
- Modbus and MQTT, one data model
2 protocols
Modbus and MQTT, one data model
- buffering on an unstable network
Reconnect
buffering on an unstable network
- faster onboarding of the next device
Fewer connectors
faster onboarding of the next device
- Industry
- Industrial IoT
- Year
- Service
- IoT integration
Challenge
On industrial sites, PLCs, sensors, and gateways speak different protocols. Each new device meant another one-off connector.
Solution
In 2025 we delivered a layer joining Modbus (TCP/RTU) with MQTT: a shared data model, reconnect, buffer, API, and dashboards. We didn’t rewrite the existing automation.
What we shipped
- Mapping Modbus registers and MQTT topics
- Reconnect and buffering when the network drops
- APIs and dashboards for operators
Results
New devices come online faster. Modbus stays on the floor, MQTT carries events to cloud and edge — scalable IoT without resetting the plant.
We don’t publish the client name — scope and stack on request.
Tech stack
- Modbus TCP/RTU
- MQTT
- Node.js
- NestJS
- React
- PostgreSQL
