CAN FD and DoIP: why an older scanner can't even connect to a new car

Sometimes a scanner doesn't fail to diagnose a fault - it fails before that, unable to establish a connection at all. On a growing number of 2020+ vehicles from GM, VW, Volvo, Land Rover and BMW, that's not a broken tool. It's a protocol the tool simply doesn't speak.

What actually changed

Older scan tools talk to the car over classic CAN bus - a wiring standard that's been the backbone of vehicle diagnostics for two decades. Newer vehicles increasingly use CAN FD (Flexible Data-rate), which moves data faster and in larger chunks, and DoIP (Diagnostics over Internet Protocol), which routes diagnostic traffic over the car's internal Ethernet network instead of the old CAN wiring entirely. A tool built before these protocols existed can't just "try harder" - it's speaking a different language the car's gateway won't even acknowledge.

How this shows up in a workshop

  • The tool identifies the vehicle but then times out trying to reach specific modules
  • Some systems (engine, transmission) connect fine; others (gateway-protected modules on newer platforms) don't respond at all
  • A car that diagnosed perfectly two model years ago suddenly won't connect on the newer version

What to check before you buy

If your customer base is trending newer, CAN FD and DoIP support stop being a spec-sheet detail and start being the reason a job stays in your bay instead of going to the dealer. Our workshop-tier tools - including the Autel MaxiCOM MK900TS, MaxiPRO MP900 and Launch X431 PROS V5.0 - all support current CAN FD and DoIP protocols. Entry-level four-system scanners generally don't need them, since private owners rarely hit gateway-protected modules.

Not sure if this affects you?

Tell us the makes and roughly how new the vehicles you see are, and we'll tell you honestly whether this matters for your work or not. Get in touch - advice is free.

Back to blog