ElectronsX > Supply Chains > Compute & Control > EV Controller Units


EV Controller Units


This article consolidates the most common EV controller and compute terms and clarifies what each controller does, its voltage domain, and how these controllers relate to modern E/E (Electrical/Electronic) architectures such as domain controllers, zonal controllers, and centralized compute. This is a cross-cutting topic that spans both HV/LV (High-Voltage / Low-Voltage) electrical systems and the ADAS/AV (Advanced Driver-Assistance Systems / Autonomous Vehicle) stack because most “control units” and all compute platforms operate in the low-voltage domain while commanding and supervising high-voltage systems indirectly.

Controllers and compute operate primarily on low-voltage power, but they command and supervise high-voltage devices via messaging and safety interlocks.

This table consolidates common EV controller-unit terms and clarifies scope, voltage domain, architectural role, and how they relate to zonal architectures and ADAS compute:

Controller type What it is SDV trend
MCU (Microcontroller Unit) Embedded real-time compute chip inside ECUs Still essential; moves down the stack
ECU (Electronic Control Unit) Generic embedded vehicle controller Being eliminated or absorbed
VCU (Vehicle Control Unit) Vehicle-level supervisory controller Becoming software services on central compute
PCU (Powertrain Control Unit) Powertrain-focused control unit Often merged into VCU or central compute
DCU (Domain Control Unit) Functional-domain controller Transitional architecture
ZCU (Zonal Control Unit) Physical-location-based (zonal) controller Core building block of modern SDVs
Central Compute (ADAS / SDV Computer) High-performance SoC-based platform Increasingly dominant compute node

Controller Responsibilities and Notes

  • MCU: A safety-reliable embedded compute chip used inside many ECUs, often real-time. Handles deterministic control logic, sensor/actuator I/O, diagnostics and network messaging. Not a "unit" by itself; it is the silicon inside ECUs, ZCUs, gateways and many VCUs, and it moves "down the stack" as features consolidate upward.
  • ECU: Generic term for any embedded vehicle controller, handling a single function or small set of functions (examples: window lift, seat motor, HVAC flap, airbag module). Parent term: VCU, PCU, DCU and ZCU are all ECUs.
  • VCU: Vehicle-level supervisory controller (motion/vehicle state): driver input interpretation, torque arbitration, drive modes, vehicle state supervision, and coordination with BMS and powertrain controllers. Does not switch HV power directly; issues commands over CAN/Ethernet (and other legacy buses where used).
  • PCU: Sometimes merged with the VCU. Covers motor torque control logic, regen coordination, transmission control (if present) and powertrain thermal coordination. Naming varies by OEM; function is more stable than the label.
  • DCU: Domain aggregation for body, chassis, infotainment, or ADAS; ECU consolidation; local decision-making within a domain. Grouped by function (domain), not by physical location; a transitional architecture toward fewer, larger computers.
  • ZCU: Aggregates local sensors/actuators, provides smart I/O, bridges LIN/CAN to Ethernet, and reduces harness length and ECU count. Some OEMs use "zonal gateway" or "zonal controller" interchangeably.
  • Central Compute: High-performance compute platform (often SoC-based) with safety supervision. Runs sensor fusion, perception (AI inference), planning, cross-domain coordination and OTA-enabled software services. May include SoC(s) + safety MCU/safety islands + Ethernet switch fabric; ADAS is software running here.

Related Coverage