Que sont les technologies CAN FD et DoIP, et votre prochain outil de diagnostic en a-t-il besoin ?

You plug a scanner that has always worked into a late-model car, and it hangs on the identification screen, reports a communication error, or only opens the generic engine menu. The vehicle may be fine. Often the car is simply talking over a newer diagnostic network than the tool was built to use.
Two of those networks show up again and again on tool listings: CAN FD and DoIP. This guide explains what they are, what fails when a scanner does not support them, and how to decide whether your next Scanner OBD2 needs a CAN FD DoIP scanner-level interface.
Classic CAN, in Plain English
For many years, most vehicles have used Controller Area Network, or CAN, to move diagnostic data between modules and a scan tool. If you have used a typical OBD2 tool on a 2008 sedan or a 2014 pickup, you have almost certainly been talking over classic CAN. It is still enough for a huge share of everyday work. It is not obsolete. Automakers added faster networks as vehicles gained more modules, driver-assistance systems, and gateways. For background, see Comprendre l'OBD2 du point de vue de l'application.
What CAN FD Is
CAN FD stands for Controller Area Network Flexible Data-rate. It belongs to the same family as classic CAN, but it can move more data in a single frame and run parts of the message at a higher speed.
A late-model car or truck may have dozens of control units sharing a network. When those modules exchange larger messages, classic CAN becomes a bottleneck, so manufacturers adopted CAN FD on many newer platforms.
The practical point is simple: if a module or gateway lives on a CAN FD network, a tool that only speaks classic CAN may never reach it. You might still get generic powertrain codes, or you might get nothing useful at all.
What DoIP Is
DoIP stands for Diagnostics over Internet Protocol. Instead of riding only on the older CAN wires, diagnostic traffic can travel over an Ethernet-style connection between the vehicle and the scan tool. That is especially useful for module programming or other data-heavy jobs on some late-model vehicles.
Because the physical interface is different, the tool and its vehicle communication interface (the VCI that plugs into the OBD2 port) must officially support DoIP. A software update alone usually cannot add that hardware capability. DoIP and CAN FD are not the same thing, and a vehicle may use one, both, or neither. Treat them as two separate boxes to check.
What You Will See If the Tool Cannot Talk
Those symptoms are easy to misread as a vehicle fault. Common ones include:
- The scanner cannot identify the vehicle, or it identifies the VIN and then fails to enter the diagnostic menu.
- You can open generic OBD2 functions, but manufacturer-specific modules never appear.
- Functions that worked on an older model in the same nameplate disappear on the newer one.
- Communication drops as soon as you try to read a body, gateway, or driver-assistance module.
A basic code reader can still be useful for check-engine work on many cars, even when it cannot reach those newer networks. If you are deciding between a simple reader and a tablet, start with Lecteur de codes vs. Scanner multisystème vs. Tablette de diagnostic.
Do You Actually Need CAN FD and DoIP?
Not every buyer needs both protocols tomorrow. The honest answer depends on the vehicles you work on.
You may be fine without them if you mostly service older daily drivers, earlier light trucks, and vehicles whose coverage charts do not list CAN FD or DoIP.
You should look for both if you regularly see late-model U.S., Asian, and European vehicles, or if you run a shop that cannot predict what will come in tomorrow. Turning a job away because the tablet cannot communicate is expensive.
Hardware support is not the same as coverage. A tablet can have a CAN FD and DoIP VCI and still lack software for a particular system or year. Always check coverage for the exact vehicle and year before you buy, and again before you promise a specific function.
Scan Tools That Officially List These Protocols
On Autel 900-series service tablets, official materials list DoIP and CAN FD on the MaxiCOM MK900-BT et le MaxiCheck MX900. If you also want ECU coding on that 8-inch generation, look at the MaxiDAS DS900BT and confirm the functions you need.
Further up the Autel line, DoIP and CAN FD are official features on the MaxiSYS MS906 Pro et le MaxiSYS MS909. Notre Guide de la gamme MaxiSYS explains how those tablets compare.
On the TOPDON side, the TOPDON Phoenix Lite 3 officially lists CAN-FD support. If you need a VCI that official materials describe as supporting both DoIP and CAN-FD, review the TOPDON Phoenix Smart and confirm the interface included in the kit. You can also browse the broader catégorie outils de diagnostic and filter by the protocols listed on each product page.
How to Check Before You Buy
- Look for CAN FD et DoIP as separate, official claims on the product listing, not as a vague “latest protocols” phrase.
- Confirm the VCI in the box is the interface that actually supports those protocols.
- Check vehicle coverage for your make, model, and year, including the specific modules you care about.
- Ask whether the support is already in the current software or requires a future update you cannot rely on today.
FAQ
Can I add CAN FD or DoIP to an older scanner with a software update? Usually not. These are hardware capabilities in the vehicle interface. Confirm with the manufacturer before you assume an upgrade path exists.
Will a CAN FD DoIP scanner still work on older cars? In general, yes, subject to the same coverage limits as any other scan tool. A security gateway is a separate access-control issue, not a protocol issue.
En résumé
CAN FD and DoIP are the reason a previously reliable scanner can go silent on a newer vehicle. If your bay is starting to see late-model cars and trucks, choose a tool that officially supports the protocols you need, then verify coverage for each vehicle instead of assuming the hardware alone will do the job.





