Where software-defined vehicles are heading
The opportunity map of SDV: what changes economically with OTA and features as software, which technical directions are compounding, and why now is an unusually good entry point for software engineers.
7 posts
The opportunity map of SDV: what changes economically with OTA and features as software, which technical directions are compounding, and why now is an unusually good entry point for software engineers.
The software-defined vehicle from first principles: how E/E architecture is consolidating, why hardware and software are decoupling, what vehicle APIs like COVESA VSS change, and how to try it today with digital.auto.
The two moves that define modern vehicle software work: shift left (validate earlier, against virtual targets) and shift north (develop at higher abstraction, against vehicle APIs instead of bus signals).
What ACC actually is per ISO 15622 — sensing, the two-loop controller, time-gap policy, the state machine — and how we test a real ACC controller as an FMU in a virtual car.
From zero to a tested virtual ECU with RemotiveLabs, file by file: signal databases, a Python behavioral model, topology build, and a pytest that proves it works.
A one-page, hand-verified reference for the RemotiveLabs toolchain: CLI command map, broker verbs, record & replay in 3 steps, offsets, versions, and every gotcha we hit.
Build a virtual vehicle from containerized ECUs with RemotiveLabs: signal databases, CAN/LIN/SOME-IP buses, behavioral models — the mental model, a worked topology, and the gotchas.