— Solutions / Automotive

Connected-vehicle platform for the small and mid-volume segment.

MOS4 ships the vehicle protocol stack, OTA infrastructure, and compliance artefacts on day one. Your team builds the vehicle application and cloud policy — not the OS.

What you get on day one.

12 vehicle protocols from one runtime. DTC reading and clearing. J2534-2 passthrough for existing dealer tooling. A/B OTA with automatic rollback. GNSS with LTEE fast fix and ESF dead reckoning. And a CI-ready ECU simulator so diagnostic regression runs without bench hardware.

What your team writes.

The vehicle application and cloud policy. Protocol stacks, OTA pipeline, modem control, and GNSS multiplexing are already shipped. PID and SPN changes are data-file edits — no firmware rebuild.

Connected sedan side-profile with six sensor halos: GPS, cellular, OBD-II, CAN, accelerometer, ambient-light — amber on cellular

Capabilities most relevant

What ships out of the box.

— 01

12 vehicle protocols from one runtime

CAN, CAN-FD, ISO-TP, DoIP, J1939, J1587/J1708, J1850 VPW/PWM, TP 2.0, GMLAN, CANopen, Modbus, and K-Line share one unified protocol API via obdstacks-v2. 22 production stacks ship validated on every CI push.

— 02

DTC reading + clearing, J2534-2 passthrough

DTC reading and clearing across the supported stack — OBD-II service 03, UDS ReadDTCInformation, J1939 SPN fault codes. J2534-2 passthrough lets existing dealer tools reach the vehicle bus through the same gateway handling continuous telematics.

— 03

A/B OTA with automatic rollback

Delta updates with signed packages and automatic rollback. A/B rootfs slots; if the new slot fails to boot, the bootloader falls back automatically. Cohort and canary OTA management via the Munic cloud companion. No operator action on failure.

Protocol coverage

12 protocols from one runtime.

All protocols share one service obdstacks-v2 runtime and one service VehicleInterfaceManager . Stack definitions are JSON DSL data files — protocol changes require no firmware rebuild. The service SubscribeCanFrames streaming service lets any container or cloud subscriber receive raw CAN frames alongside J2534 passthrough on the same interface.

obdstacks-v2 protocol coverage
Protocol Transport Notes
CAN Classical / CAN-FD ISO 11898 SubscribeCanFrames streaming service
ISO-TP / DoIP CAN / Ethernet UDS diagnostic sessions
J1939 CAN PGN/SPN addressing, FMS
J1587 / J1708 SAE J1708 serial Legacy heavy-duty
J1850 VPW / PWM SAE J1850 Legacy OBD-II
TP 2.0 / GMLAN CAN VAG / GM variants
CANopen CAN Industrial node profiles
Modbus RS-485 / TCP Auxiliary subsystems
K-Line ISO 9141-2 Legacy OBD-II

Platform metrics

Key numbers.

12 vehicle protocols via obdstacks-v2, one runtime
22 production stacks validated on every CI push
129/180 platform features across all scenarios
1.6 s boot time modem-class reference profile, first-app-ready

Cloud egress

Vehicle data to cloud via MD21.

Telemetry, DTC events, and OTA status travel to the fleet cloud over the MD21 uplink — the same channel used by all micro services. No per-micro service cloud connector; the cloud policy is a data-file configuration, not application code.

Canary and cohort OTA management sits in the Munic cloud companion. The vehicle reports boot-slot health and service readiness automatically; no operator polling required.

Edge device with cloud connectivity — MOS4 telemetry path to fleet cloud

Reference architecture

A vehicle programme on MOS4.

Anchor proof

Production deployments.

Performance vehicles

A leading performance-vehicle OEM ships its fleet on MOS4.

Multi-platform deployment. Telemetry into MD21; remote diagnostics into the engineering pipeline.

scope fleet-wide since 2022
Specialty platforms

An EV maker ships specialty platforms on MOS4.

Sub-platform variants from the same image. Per-product silicon class; shared OTA; single fleet console.

scope multi-platform since 2023

FAQ

Frequently asked questions

  • What vehicle protocols does obdstacks-v2 cover?

    12 protocols — CAN, CAN-FD, ISO-TP, DoIP, K-Line, J1939, J1587/J1708, J1850 VPW/PWM, TP 2.0, GMLAN, CANopen, and Modbus — share one unified protocol API. Stack definitions are JSON data files; adding or changing a PID requires no firmware rebuild.

  • How does DTC reading work?

    DTC reading and clearing is available across the supported stack: OBD-II service 03, UDS ReadDTCInformation, and J1939 SPN fault codes. This is the same interface used by vehicle-tier products.

  • What is J2534-2 passthrough?

    obdstacks-v2 implements J2534 passthrough via JSON/Protobuf. Existing OEM diagnostic applications — scan tools, ECU flashers — reach the vehicle bus through the same gateway handling continuous telematics, without a dedicated J2534 dongle.

  • How does the OTA rollback work?

    A/B rootfs slots with automatic rollback. If the new slot fails to boot, the bootloader falls back automatically. Retry and reboot limits are persisted across power cycles.

  • Is MOS4 ASIL-certified?

    Not ASIL-certified today. MOS4 is aligned to ISO 26262 process where the customer programme requires it.

  • How do I run diagnostic regression without bench hardware?

    A bundled ECU simulator covers UDS/OBD-II/ISO-TP/DoIP/J1939 over virtual CAN. 20+ real-vehicle fixture profiles and YAML declarative test scenarios run in CI without a bench ECU or per-seat tool licence.

  • What silicon tiers are available?

    MOS4 runs on modem-class through AI-class silicon. See munic.io for hardware SKUs and datasheets.

Bring your vehicle programme.

A discovery call with engineering — bring the vehicle architecture sketch and the constraints already locked in.

Talk to engineering Why MOS4 →