6-part series · 1 live
Series
Building a Steer-by-Wire System
Steer-by-wire removes the mechanical column between the wheel and the road. The driver's intent becomes a signal, and a safety-critical actuator turns that signal back into feel. Validating that loop (proving it behaves, fails safe, and earns its ASIL-D rating) is one of the hardest jobs in chassis engineering.
This series follows a single program from the first data off the bench to the signed safety case, through the engineer who owns its validation. Each chapter is a stage of that program, and each one foregrounds the same quiet adversary: the data tax. The uncounted work of finding, cleaning, aligning, correlating, and trusting engineering data before any real analysis can begin.
The engineer validates the system. The data and analysis layer (MOVEcenter) carries the tax. Figures throughout are illustrative, built to mirror real campaigns; the shape of the problems is real.

Chapters
06
- 01Chapter 1Prep & Cleanup
The first data off the rig
Mixed formats from the steering robot, torque/angle sensors, and redundant ECUs (days lost before any analysis can start).
June 22, 2026 · 6 min readRead - 02Chapter 2ScaleComing soon
The fault-injection campaign
ISO 26262 fault and regression runs explode in volume (more results than any engineer can review by hand).
- 03Chapter 3CorrelateComing soon
Rig versus road
HIL versus vehicle, steering model versus test, road-feel and torque, reconciled by hand one channel at a time.
- 04Chapter 4DiagnoseComing soon
The intermittent fault
A failure that only shows up hot and late, with the root cause hidden across separate data sources.
- 05Chapter 5Report + ComplyComing soon
The safety case
The sign-off report and ISO 26262 ASIL-D traceability, assembled by hand from a dozen scattered artefacts.
- 06CloserRetainComing soon
What the program leaves behind
The method stays with the team, not in one engineer's scripts on a drive nobody else can find.