When the Fault Is Real, But the Module Isn't in Charge

Why the next generation of vehicle diagnostics is shifting from "what failed" to "who owns this function"

For years, most diagnostic work has followed a familiar path: DTC to module, module to circuit, circuit to component. In a lot of cases, that path still gets you there.

But the vehicles coming through the workshop are starting to change the map. As the industry moves toward domain controllers, zonal architecture and central compute, the old one-to-one relationship between a fault code and a physical cause is breaking down.

One controller may now own several functions at once. A function may depend on the software state of another module entirely. A replacement part may need backend authorization before it's allowed to work. A physical output can be blocked by a controller that has nothing to do with the circuit you're testing. And the DTC itself may only tell you where the problem was detected — not where it actually started.

That changes the job in a subtle but important way. You can have power. You can have ground. The wiring can test perfectly. The component itself can be known good. And the function still won't work.

So the question stops being simply "what failed?" It becomes: "who owns this function, and what has to happen before it's allowed to operate?" That's a genuinely different way of thinking about a fault — and it's not speculation about where the industry might be headed. It's already showing up in how manufacturers are building and documenting these systems.

What the evidence actually shows

Mercedes-Benz engineers have published technical work questioning whether fixed DTC structures are flexible enough for software running on high-performance vehicle computers. A 2024 SAE technical paper co-authored by Mercedes-Benz AG engineers (SAE 2024-01-2981, "Towards Future Vehicle Diagnostics in Software-Defined Vehicles") states plainly that existing DTC-based diagnostic approaches "are not designed for such complex systems and lack of flexibility" — because DTCs are locked in during vehicle development, and adapting them later takes substantial rework.

Volkswagen's own systems already show the same pressure in practice. Gateway installation lists, coding levels and feature-enablement data all have to stay in sync across multiple modules — get that alignment wrong, and the result isn't a working function, it's a fault code.

GM and Ford are already running VIN-specific, server-connected programming, where the calibration a vehicle receives is tied to its identity and pulled from the manufacturer's own systems rather than sitting locally on a disc or a tool.

And the industry has introduced SOVD — ISO 17978 — to sit alongside traditional UDS, purpose-built to support diagnostics on software-defined, high-compute vehicles where the old service-oriented model doesn't fully translate.

What this doesn't mean

The scan tool isn't becoming obsolete. It's becoming one piece of a bigger diagnostic picture. The fundamentals — voltage, ground, current, waveforms, mechanical condition, proof — still matter as much as they ever did. Nothing about function ownership or software state replaces the need to verify a physical effect.

What's changing is what sits alongside those fundamentals. Increasingly, that means understanding function ownership, software state, authorization, network dependencies and system state — not as a replacement for hands-on diagnostic skill, but as an extension of it.

This isn't a move away from technician skill. It's technicians having to see more of the vehicle than ever before.

Are you starting to see this shift in your own workshop yet?

Evs are charging ahead—but the game’s getting complex

One of the biggest shifts in the car world right now is the rapid rise of electric vehicles (EVs)—but it’s not just about swapping petrol for lithium. The whole landscape is evolving:

• Battery tech is surging: Solid-state batteries are on the horizon, promising longer life cycles and faster charging
• Peak ICE is approaching: Internal combustion engines are expected to be overtaken by EVs globally by 2036.
• Cybersecurity is now critical: With cars becoming rolling computers, protecting vehicle networks from hacks is a growing priority.
• Autonomous tech is scaling: Robo-taxis and shared autonomous shuttles are inching closer to mainstream deployment.
• Australia’s market is shifting: After record sales in 2024, prices are expected to drop in 2025 as supply stabilizes and cost-of-living pressures bite.