Solutions · Machinery
Ship an off-highway machine programme.
A connected-machine OS for off-highway, ISOBUS, and agriculture programmes — chosen for fifteen-year lifecycle expectations. Ships J1939, ISOBUS, Modbus, geofencing, 1-Wire sensors, camera capture, and A/B OTA out of the box. The engineering team writes the machine application — not the OS or protocol infrastructure.
The programme constraint
The machine outlives the OS.
Off-highway and agriculture machines ship for fifteen years. The OS choice carries procurement filters, support windows, and Cyber Resilience Act (CRA) compliance for that horizon. MOS4 ships the software bill of materials (SBOM), security scan pipeline, and compliance artefacts that procurement expects.
How MOS4 fits
Three capabilities for a machinery programme.
J1939, ISOBUS, and Modbus from one runtime
MOS4 runs J1939, ISOBUS, Modbus, CANopen, and CAN-FD concurrently on one device. ISOBUS (ISO 11783) support covers signal acquisition — read-only. Stack definitions are data files; adding a new parameter group (PGN) or signal (SPN) requires no firmware change.
On-device geofencing — 1,000+ zones
The geofencing micro service evaluates zone membership at the edge — no cloud round-trip per position fix. Entry, exit, and dwell events fire locally; zone maps survive reboots and are updated at runtime without reflashing.
Operator vision without CPU overhead
Five camera inputs (MIPI-CSI, GMSL2, USB UVC, RTSP/ONVIF, WebRTC). Camera, GPU, and NPU share memory directly — frames move to AI inference and recording without the CPU copying pixel data.
Protocol coverage
Bus protocols shipped in obdstacks-v2.
All protocols share one service obdstacks-v2 runtime. J1939 and ISOBUS
run concurrently on the same device without separate hardware.
22 production stacks ship validated on every CI push.
| Protocol | Bus | Use on machine |
|---|---|---|
| J1939 | CAN | Powertrain PGN/SPN, fault codes |
| ISOBUS | CAN | Implement signal acquisition (read-only) |
| Modbus RTU | RS-485 serial | Third-party attachments, PLCs |
| Modbus TCP/MBAP | Ethernet | Fixed-installation subsystems |
| CANopen | CAN | Hydraulic / electro-actuator nodes |
| CAN-FD | CAN | High-bandwidth sensor buses |
| ISO-TP | CAN | UDS diagnostic sessions |
ISOBUS support covers signal acquisition only — read-only. VT display authoring is not part of the micro service.
Platform metrics
Key numbers.
Reference architecture
A machinery programme on MOS4.
Anonymous proof point
Agricultural-machinery manufacturer · regional rollout.
An agricultural-machinery manufacturer ships MOS4 across a regional fleet, decoding ISOBUS (ISO 11783) and J1939 simultaneously. Geofencing boundary detection and 1-Wire temperature acquisition run on the same device. Compliance documentation and software bills of materials (SBOM) ship out of the box.
Reference under NDA · request an engineering-mediated reference call
ROS2 integration
ROS2 nodes hosted without rewriting.
The ROS2 bridge micro service connects any unmodified ROS2 node to the MOS4 event bus without code changes. Existing ROS2 nodes run in isolated containers alongside CAN, GNSS, geofencing, and remote care. The bridge translates ROS2 (DDS) messages to and from the MOS4 typed event bus bidirectionally.
See the ROS2 sidecar gateway in the micro services catalog →
FAQ
Frequently asked questions
-
Can J1939 and ISOBUS run simultaneously?
Yes. MOS4 runs multiple protocol stacks concurrently on the same physical interfaces from one device — J1939 and ISOBUS share the same runtime without separate hardware.
-
What does ISOBUS support cover?
Signal acquisition (ISO 11783) — read-only. Virtual Terminal (VT) display authoring is not part of the micro service.
-
How does precision agriculture positioning work?
The GNSS service supports real-time kinematic (RTK) positioning when paired with an RTK-grade receiver. Inertial sensor fusion (ESF) feeds CAN wheel-speed pulses for dead reckoning through signal outages at field edges. For hardware details and SKUs, see munic.io.
-
How are geofencing zones updated in the field?
Zone definitions are updated via a service call at runtime — no firmware reflash required. Zone maps are persisted across reboots. 1,000+ zones are evaluated efficiently with no cloud round-trip per position fix.
-
What 1-Wire devices are supported?
DS18B20/DS18S20 temperature probes, DS2438 hygrometer, DS2401 iButton operator credentials, DS1992 EEPROM — all via one service. Other services consume events from these devices without accessing hardware directly.
-
How does over-the-air updating work in a remote field deployment?
Delta updates with signed packages and automatic rollback. A failed update reverts automatically without requiring a field technician. Download over HTTP, HTTPS, or SFTP.
-
Is there formal long-term support?
No formal LTS. Support windows are agreed per programme.
Bring the machine architecture.
Protocol mix, sensor types, lifetime expectations, silicon tier. Engineering will sketch the MOS4 fit on the call.