Column-, Pinion- and Rack-Assist Layouts

EPS systems differ mainly in where the assist motor couples into the steering mechanism. Column-assist EPS (C-EPS) mounts the motor and ECU close to the steering column, near the driver. This keeps the module compact and reduces required motor torque, which in turn eases power-stage current and thermal design for smaller vehicles.

Pinion-assist and rack-assist EPS (P-EPS and R-EPS) place the motor near the steering gear or rack, closer to the front axle. These layouts can deliver higher assist levels for heavier vehicles, but the motor currents and peak torque are significantly higher. The ECU usually sees harsher vibration, temperature and splash environments, so gate drivers, power devices and current-sense components must be chosen with greater thermal and mechanical margin.

Motor Types for EPS: Brushed, BLDC and PMSM

Early EPS designs often used brushed DC motors with relatively simple H-bridge drivers. While easy to control, brushes introduce wear, acoustic noise and commutation sparks that stress the EMI and reliability budget. Modern systems increasingly adopt brushless solutions to improve efficiency, lifetime and noise behaviour.

Brushless DC (BLDC) and permanent-magnet synchronous motors (PMSM) both rely on electronic commutation and precise current control. They require three-phase gate drivers, rotor position feedback and microcontrollers capable of handling PWM generation, current loops and diagnostics. Compared with brushed motors, they push stricter requirements onto the current-sense path, gate drivers, power devices and signal-conditioning ICs.

12 V vs 48 V EPS and Impact on Electronics

Most existing EPS modules run from the 12 V vehicle supply, sharing wiring and protection concepts with other body and chassis loads. High-assist designs push large currents through the power stage and wiring harness, making shunt selection, copper area and thermal design critical. Over-current and over-temperature protection must react quickly enough to protect both power devices and steering hardware.

Newer platforms adopt 48 V EPS to reduce current for the same assist power and to integrate with mild hybrid systems. The higher voltage introduces tougher requirements for creepage and clearance, isolation barriers, surge protection and gate-driver ratings. Designers often need isolated current and voltage sensing, isolated DC-DC supplies and digital isolators, and must coordinate these choices with the central 48 V power architecture described on the separate mild-hybrid system page.

Inputs & Sensors

Torque sensors measure torsion in the steering shaft, typically with dual channels to support safety goals. Steering-angle sensors provide absolute or incremental position and are often implemented as redundant encoders. Additional inputs such as vehicle speed and yaw rate arrive from other ECUs over CAN or Ethernet, allowing the EPS controller to adapt boost and steering feel to driving conditions.

Control, Safety & Memory

The main MCU or SoC runs torque and angle processing, assist algorithms, diagnostics and communication stacks. A redundant MCU or lockstep core monitors safety-critical paths, compares key results and supervises watchdog and self-test mechanisms. Internal RAM/Flash and external NOR or EEPROM store calibration data, fault logs and configuration with ECC, CRC and periodic integrity checks.

Power Stage & Sensing

High-current gate drivers control a three-phase bridge or H-bridge that connects the vehicle supply to the EPS assist motor. Current-sense elements and DC-bus voltage feedback feed both control and protection functions, supporting fast over-current detection, torque control loops and thermal management. Power modules often integrate shunts, temperature sense and protections into a single package.

Power Supply & In-Vehicle Networking

The ECU accepts 12 V or 48 V supply, adding filtering, reverse-battery and surge protection before generating regulated rails for MCUs, AFEs, gate drivers and sensors. CAN FD, FlexRay and Ethernet PHYs provide connectivity to body, chassis, ADAS and gateway ECUs, with wake-up and diagnostic support so the EPS module can report faults and receive steering and safety commands.

Power Stage Architectures for EPS

Most EPS systems use either a three-phase bridge for BLDC or PMSM assist motors, or an H-bridge for lower-power column-assist designs. The three-phase bridge supports smoother torque and advanced control strategies, but it requires more gate-drive channels and tighter current measurement. H-bridges simplify the hardware and control, at the cost of lower peak assist capability in larger vehicles.

System-Level Requirements for Gate Drivers

Gate drivers in EPS must deliver enough peak current to switch large MOSFETs or IGBTs quickly while respecting device voltage limits and electromagnetic constraints. They integrate protections such as short-circuit and desaturation detection, undervoltage lockout and thermal feedback, and report faults back to the MCU so that steering torque can be limited or disabled safely.

At the system level, diagnostics for open and shorted loads, phase-to-phase or phase-to-ground faults, and over-temperature conditions are essential. The EPS safety concept defines how the MCU reacts to each fault, for example entering a limp-home mode where assist is limited but mechanical steering remains possible. Detailed gate resistor sizing and switching-waveform shaping are handled in the dedicated gate-driver design domain.

Torque Sensing Chain in EPS

The torque sensor measures torsion in the steering shaft and is typically implemented as a dual-channel device. Magnetic, inductive, Hall-based or strain solutions are used to convert mechanical twist into electrical signals. Each channel feeds its own analog front-end with excitation, differential amplification and filtering before conversion by an ADC or sigma-delta modulator.

Redundancy is achieved by using two independent torque paths, often with different polarity or sensitivity, routed into separate MCU or safety inputs. The EPS safety software constantly compares both channels for range, offset and dynamic behaviour so that latent faults or drift in one path can be detected before they lead to incorrect steering assist.

Steering-Angle Sensing Chain in EPS

Steering-angle sensors provide absolute or incremental position information for zero-point calibration, steering feel shaping and alignment with ADAS features. Implementations range from encoder wheels and magnetic rings to integrated angle sensor ICs. Their outputs are typically digital, using interfaces such as SPI, SENT, PSI5 or resolver-style excitation and demodulation.

Redundant angle sensing can be realised with dual tracks or separate ICs, each feeding its own interface channel. The EPS controller uses these channels both to control assist and to check consistency between torque, angle and vehicle dynamics signals when deciding whether to keep full assist or enter a degraded mode.

System Metrics & Failure Modes

Key metrics for torque and angle chains include resolution, bandwidth, linearity and temperature behaviour, all referenced to the assist torque and steering feel targets. The measurement bandwidth must comfortably cover driver inputs and control loop dynamics, while linearity and drift determine how stable the boost curve and on-centre feel remain over vehicle lifetime.

Typical failure modes include sensor distortion, supply loss on one or both channels, connector or wiring faults and calibration drift. EPS safety concepts map these into plausibility checks between torque, angle and vehicle dynamics, and define how the system transitions from full assist to warning, limited-assist or purely mechanical steering when faults are detected.

Safety Goals and EPS Control Path

EPS safety concepts focus on preventing incorrect steering torque in magnitude or direction and on maintaining a controllable state if faults occur. The safety path runs from torque and angle sensors through the control MCUs and the power stage to the motor and rack. Each element needs measures for fault detection, containment and safe reactions consistent with an ASIL-D allocation.

MCU Redundancy Patterns for EPS

One approach uses a single automotive MCU with lockstep CPU cores and an on-chip safety island. The lockstep cores execute the same control code and a comparator flags mismatches, while the safety island hosts watchdogs, diagnostics and self tests. This offers high integration but still relies on a single device package.

An alternative is a dual-MCU architecture, with a main controller running full EPS algorithms and networking and a safety MCU monitoring key inputs and torque commands. The two devices communicate over a safety-qualified link and cross-check results, allowing more diverse implementations and a clearer separation between complex application software and a simpler supervision path.

Safety Mechanisms and Monitors

EPS controllers combine hardware and software mechanisms to detect faults. Windowed watchdogs supervise program flow, supply and clock monitors track voltage and oscillator margins, and memory protection checks ensure that Flash, RAM and EEPROM contents remain valid over lifetime. Periodic self tests help reveal latent faults before they impact steering.

On the communication side, end-to-end protection for CAN or Ethernet messages adds sequence counters and CRCs, allowing torque commands and feedback exchanged with ADAS or gateway controllers to be checked for corruption. The safety MCU or safety manager collects these indications and turns them into diagnostic trouble codes and safety reactions.

Degradation Strategies and Safe States

Safety software cross-checks torque commands from the main path against the safety calculation, correlates torque and angle readings with vehicle dynamics, and compares commanded and measured motor currents. When discrepancies exceed defined thresholds, the EPS transitions into warning or degraded modes instead of silently maintaining full assist.

Typical strategies include fail-silent behaviour, where assist is quickly disabled and mechanical steering remains, and fail-operational behaviour, where assist is limited in magnitude or vehicle speed until the driver can stop safely. Mechanical fallback through the steering column ensures that even with electrical failures the driver retains a direct connection to the road wheels.

In-Vehicle Networking for EPS

Most EPS controllers are connected to the vehicle via CAN FD, exchanging torque requests, mode commands and diagnostic information with body, chassis or safety domains. On higher-end or centralized platforms, FlexRay or automotive Ethernet may be added so EPS can participate in redundant safety networks or higher-bandwidth links to ADAS domain controllers and zone gateways.

From the EPS perspective, the chosen network topology directly impacts the number and type of PHYs, MCU interface resources and bandwidth budgeting. It also defines where end-to-end protection and security features must be implemented so torque commands and feedback cannot be corrupted or delayed without detection.

Diagnostics & DTCs on the EPS Node

EPS ECUs typically implement UDS over CAN and, on Ethernet-equipped platforms, UDS over TCP/IP for calibration, routine control and fault reading. Diagnostic trouble codes cover torque and angle sensor failures, power-stage over-current or thermal events, supply anomalies, and mismatches between redundant control channels or internal self-test results.

For system designers this means planning a clear mapping from internal safety mechanisms to externally visible DTCs. The OEM’s fault tree and service strategy decide which conditions raise a warning, which trigger limited assist and which require immediate shutdown of electric assist while preserving mechanical steering capability.

Cybersecurity Hooks in the EPS Controller

Because EPS can generate steering torque directly, its firmware must be protected against tampering. Secure boot uses a hardware root of trust to verify that the EPS image is authentic before any torque-related code executes. Secure flash update ensures that field or workshop reprogramming is authenticated, integrity checked and able to recover from interruptions without leaving the ECU in an undefined state.

Hardware security modules or secure MCUs store keys and perform cryptographic operations so that torque requests and other critical messages from gateways or ADAS controllers can be authenticated and protected. Detailed protocols and security policies are defined at the gateway or ADAS level, but from the EPS viewpoint the MCU must provide secure boot, secure update and HSM capabilities that fit into the vehicle-wide cybersecurity concept.