Solutions · IoT Gateway
Ship an industrial IoT gateway.
A connected-gateway OS for stationary industrial-IoT deployments. Ships Modbus RTU/TCP, MQTT bridge, OPC-UA-ready transport, signed boot, A/B OTA, and the CRA-ready compliance pack. Engineering writes the gateway application — not the OS or device-management layer.
How MOS4 fits
Three capabilities for a field gateway.
Modbus RTU + TCP from one micro service
The Modbus stack ships client and server in one process. RTU (RS-485) and TCP/MBAP confirmed in production. ASCII mode is experimental. Hot-reload of baud rate and TCP address via the config service — no firmware rebuild for field reconfiguration.
Embedded MQTT broker
An MQTT broker runs in-process — no external broker process. Translates inbound MQTT topics to MOS4 service calls; bridges to cloud via the MD21 uplink. Integrators with existing MQTT back-ends connect — no format negotiation layer.
Production container isolation
CPU and memory limits are declared per container and enforced as a hard contract — not best-effort. Relevant on a constrained device running third-party algorithms. Container budget: under 5% CPU/RAM and ~10 MB resident memory. MOS4 supplies the platform security mark; the container workload mark is the customer's responsibility.
Protocol coverage
Modbus transport variants.
service mos-modbus ships one binary for both client and server roles.
The same Modbus core is shared with the
service obdstacks-v2 vehicle protocol stack for polling scheduling
and cloud publish — no reimplementation across micro services.
| Variant | Framing | Status |
|---|---|---|
| Modbus RTU | RS-485 serial | Confirmed in production |
| Modbus TCP/MBAP | Ethernet / IP | Confirmed in production |
| Modbus ASCII | RS-232 / RS-485 | Experimental |
| Modbus RTU-over-TCP | TCP gateway mode | Not confirmed in production |
Platform metrics
Key numbers.
Reference architecture
An industrial gateway on MOS4.
MQTT streaming-RPC
MessageGate — MQTT to event bus bridge.
The MessageGate micro service bridges inbound MQTT topics to internal service calls
using the same typed contract as REST and RPC — no format negotiation layer required. Outbound service
events publish back to MQTT topics on a configurable prefix, making MOS4 field gateways a drop-in
data source for existing MQTT back-ends — no proxy or adapter process.
See the EventBus and streaming-RPC model in the architecture overview →
FAQ
Frequently asked questions
-
Which Modbus variants ship in production?
RTU (RS-485) and TCP/MBAP are confirmed in production. ASCII mode is experimental. RTU-over-TCP gateway mode is present in the codebase but not confirmed in deployed gateways.
-
Do I need an external MQTT broker?
No. The MQTT broker runs in-process. Inbound MQTT topics map to MOS4 service calls. Cloud bridging uses the same MD21 uplink that every micro service shares.
-
How are container resource limits enforced?
CPU and memory limits are declared per container at start time and enforced as a hard contract — not best-effort. Docker Compose v3 file parsing is supported for container configuration.
-
How fast can I update a deployed gateway?
Delta updates with signed packages and automatic rollback. A failed over-the-air (OTA) update reverts without operator intervention. Hot-swap from end-of-compile to first successful service call takes around 10 seconds on a real device.
-
What 1-Wire devices are supported?
DS18B20/DS18S20 temperature probes, DS2438 hygrometer, DS2401 iButton credentials, and DS1992 EEPROM — all via one service. Plug/unplug events stream without polling.
-
Is there a formal ten-year LTS commitment?
No formal LTS. Support windows are agreed per programme — <a href="/contact?vertical=iot-gateway">contact engineering</a> for a programme-specific support proposal.
-
Does MOS4 support eSIM in sealed enclosures?
Yes. Embedded SIM (eUICC) profile management compliant with GSMA SGP.22 v2.2 (Consumer) and GSMA SGP.02 (M2M) ships in the modem stack. Remote SIM profile swap is available without physical hardware access.
Bring the gateway architecture.
Protocol mix, sensor types, lifecycle duration, container workloads. Bring what is locked; engineering will sketch the MOS4 fit.