Contents

Power distribution, eFuses and power modes

How electrical energy reaches every ECU and load — from 12/24/48 V supply and terminal states like KL30 and KL15 to smart electronic fuses in zone controllers.

Why it matters

Every function depends on power. As vehicles stay connected while parked, and as safety-critical functions rely on electronics, the power net becomes an engineering discipline of its own — not just cables and fuses.

What the building blocks are

  • Supply voltages: 12 V in most passenger cars, 24 V in trucks and buses, increasingly 48 V for high loads; high-voltage traction batteries feed the low-voltage net through DC/DC converters.
  • Terminal states: the traditional German terminal names are still used worldwide — KL30 (permanent battery), KL15 (ignition on), KL31 (ground). Modern vehicles replace the key with power modes managed by software.
  • Protection: melting fuses and relays are being replaced by eFuses and smart high-side switches that can switch loads, measure current and trip without being replaced.
  • Redundancy: critical consumers get two independent supply paths.

How it works in a zonal vehicle

The battery feeds zone controllers through a few thick cables. Each zone distributes power locally via eFuses, switching loads on demand from software. When the vehicle sleeps, zones keep only permanent consumers (e.g. access, telematics) powered and switch everything else off to save quiescent current.

Local power distribution through a zone
Battery
Zone controllerReceives power through a supply cable
eFuseSwitches and protects a local supply
Local load

Example supply path through one zone, with eFuses located inside the zone controller.

Best practices

  • Budget quiescent current per ECU and per power mode; verify it on the vehicle, not only on the bench.
  • Define behaviour for under-voltage, cranking and load dumps for every ECU.
  • Make eFuse trips diagnosable and recoverable, with clear rules for automatic retries.
  • Model power modes and network management together.

Common pitfalls

  • A single ECU that never sleeps drains the battery over a weekend.
  • Safety-critical loads sharing a protection element with comfort loads.

What it means for your discipline

  • Hardware & silicon Core

    Designs supply paths, protection, eFuse sizing, voltage ranges, thermal behaviour and quiescent current.

  • E/E architecture Core

    Defines power domains, redundancy for safety-critical loads and the split between battery-fed and ignition-fed consumers.

  • Functional safety Core

    Steering, braking and other critical functions need redundant, monitored power paths; loss of power must lead to a safe state.

  • Networks & communication Partial

    Power modes and wake-up are tightly linked to network management: which ECUs are powered decides who can communicate.

  • Base software Partial

    ECU state management, eFuse control, under-voltage handling and wake-up sources are configured in base software.

  • Diagnostics & lifecycle Partial

    eFuses report over-current and open-load events; zones must turn them into usable diagnostics.

  • Software update & OTA Partial

    Defines the power and battery conditions required for installation and keeps target ECUs and communication paths powered through flashing and restart. Handles under-voltage and interrupted power without leaving ECUs unrecoverable.

No direct stake: Cybersecurity · HPC & application software

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • AUTOSAR Adaptive — Coordinates application lifecycle and machine states with vehicle power modes and shutdown requests.
  • BSP · drivers — Provides platform drivers for power-state transitions, wake-up sources and supply monitoring.
MCU-based ECU · AUTOSAR Classic
  • ECU abstraction — Exposes smart power switches and current measurements through hardware-independent interfaces.
  • Microcontroller abstraction (MCAL) — Drives switch-control interfaces and samples voltage and current monitoring inputs.
  • Communication — Coordinates network sleep and wake-up with the availability of powered ECUs.
  • Diagnostics — Records eFuse trips, open loads and supply-voltage faults for diagnosis and recovery.