Why it exists
Software defines more and more of the vehicle. OTA updates fix bugs and security issues without a workshop visit — in 2026 several large recalls were remedied mostly over the air — and enable new features after sale.
What R156 requires
- A Software Update Management System (SUMS) at the manufacturer, assessed by an approval authority.
- Traceable software identification (RXSWIN) for type-approval-relevant software.
- For OTA: the vehicle must be in a safe state, have enough energy, inform the user, and be able to recover from failed updates.
How an update works
The backend builds a signed campaign for the vehicles that need it → the TCU downloads it → the update master on the HPC verifies and distributes it → each ECU installs (often into an inactive A/B bank) → activation at a safe moment → verification and reporting; rollback on failure.
This simplified sequence shows the update path from the backend to ECU activation and recovery.
Best practices
- Use A/B partitions or equivalent recovery for every updatable ECU.
- Verify compatibility of the complete software set, not single ECUs.
- Stage roll-outs and monitor before expanding.
Common pitfalls
- ECUs that cannot be updated remotely, forcing workshop visits for the whole fleet.