Finding
Driverless operation requires redundant steering, braking, power and compute, and that hardware, not the AI model, sets much of the cost floor of a robotaxi
A Level 2 system can hand control back to the driver or stop. A Level 3 or Level 4 system must keep control long enough to reach a minimal-risk condition, so every link - perception, compute, low-voltage power and actuation - needs an independent backup. Mercedes-Benz Drive Pilot (UN R157 Level 3) carries redundant steering, braking and power; Waymo's sixth-generation driver and Zoox's purpose-built robotaxi duplicate compute and actuation throughout.
The building blocks are well established: dual SoCs or an SoC plus an external safety MCU (Infineon AURIX, Renesas RH850, NXP S32, TI TMS570); lockstep CPU cores and ECC memory; independent 12 V or 48 V rails with dual DC-DC paths; overlapping camera and radar coverage; and steer-by-wire and brake-by-wire with dual motors or dual pressure sources. Steer-by-wire is in production on the Tesla Cybertruck, NIO ET9 and Lexus RZ; brake-by-wire units include Bosch iBooster with ESP, ZF Integrated Brake Control and Continental MK C2 (now Aumovio).
Functional safety (ISO 26262) and cybersecurity (ISO/SAE 21434, UN R155) are separate disciplines. ISO 21448 (SOTIF) covers hazards from sensor and algorithm limits when nothing has failed; UL 4600 sets the safety case for vehicles with no human driver.
Design modes
Fail-safe versus fail-operational
| Mode | Behavior on fault | Typical fit | Hardware implication |
|---|---|---|---|
| Fail-safe | Transitions to a safe state, usually a controlled stop or handover | Level 2 driver assistance | Supervision and safe-stop; limited redundancy |
| Fail-degraded | Continues with reduced function for a bounded time | Level 3 conditional automation | Redundant power and actuation; supervised compute |
| Fail-operational | Keeps driving safely to a minimal-risk condition | Level 4 robotaxis and trucks | Independent compute, power, sensing and actuation paths |
Elements
Safety hardware elements
| Element | Protects | Where it sits | Example suppliers |
|---|---|---|---|
| Redundant compute | Perception and planning correctness | Central ADAS/AV compute | NVIDIA, Mobileye, Qualcomm, Horizon Robotics, Huawei |
| Functional safety MCU | Command integrity, safe-state logic | ADAS DCU, gateway, central compute | Infineon, Renesas, NXP, TI, ST; SemiDrive |
| Redundant LV power | Compute, steering and braking availability | LV distribution, dual DC-DC | Infineon, TI, Vicor; eFuse makers |
| Sensor redundancy | Perception coverage under faults | Camera, radar and lidar suite | Sony, onsemi, OmniVision; Bosch, Continental radar; Hesai, RoboSense lidar |
| Steer-by-wire | Lateral control authority | Steering rack actuators | Bosch, ZF, Nexteer, JTEKT; Bethel (China) |
| Brake-by-wire | Longitudinal control authority | Brake actuators | Bosch, ZF, Aumovio, Brembo; Bethel, Tongyu (China) |
| Monitoring and isolation ICs | Fault containment between domains | Compute modules, power rails | TI, ADI, Infineon, NXP; Novosense |
Standards
Standards that set the requirements
| Standard | Scope |
|---|---|
| ISO 26262 | Functional safety of E/E systems; integrity levels ASIL A to D |
| ISO 21448 (SOTIF) | Hazards from intended function and sensor limits |
| UL 4600 | Safety case for autonomous products without a human driver |
| UN R157 | Automated lane keeping (Level 3) type approval |
| ISO/SAE 21434, UN R155 | Cybersecurity engineering and management systems |
Sources
Sources and scope
- Scope
- EV Safety and Redundancy Hardware
- Sources
- ISO 26262, ISO 21448, UL 4600, UNECE R157; Mercedes-Benz, Waymo and supplier disclosures
- Updated
- October 2026