CAN FD & DoIP Explained: Next-Gen Vehicle Diagnostics

If you have plugged an OBD2 scanner into a 2020-or-newer vehicle and received gibberish or incomplete data, you may have run headlong into one of two protocols that are rapidly replacing the classic CAN bus: CAN FD (Controller Area Network with Flexible Data-rate) and DoIP (Diagnostics over Internet Protocol). Both were designed because modern vehicles generate far more data than the original CAN specification can handle — and both demand different hardware from your scan tool.

The Original CAN Bus — and Why It Hit a Wall

Classic CAN 2.0, the backbone of vehicle communication since the mid-1990s, transmits data frames of up to 8 bytes at a maximum speed of 500 kbit/s. For most powertrain and chassis modules, that was plenty. But as automakers added ADAS cameras, LiDAR preprocessors, high-resolution instrument clusters, and over-the-air update managers, the 8-byte payload became a bottleneck. Diagnostic sessions that once took a few seconds began stretching into minutes, and module flash programming over classic CAN could take half an hour or more.

Two solutions emerged. CAN FD extends the payload to 64 bytes and cranks the data-phase bit rate to 2, 5, or even 8 Mbit/s while staying backward-compatible with classic CAN physical layers. DoIP goes further — it routes diagnostic traffic over standard Ethernet at 100 Mbit/s or faster, which is especially useful for flashing large calibration files and running high-bandwidth test routines like camera calibrations.

CAN FD: What Changed Under the Hood

CAN FD keeps the arbitration phase identical to classic CAN — same 11-bit or 29-bit identifiers, same priority scheme, same physical transceivers. The difference kicks in during the data phase. Once a node wins arbitration, it can switch to a faster bit rate and transmit up to 64 bytes instead of 8. The FD frame includes a new bit called BRS (Bit Rate Switch) that tells receivers "speed up now," and an ESI (Error State Indicator) bit that flags whether the transmitting node is in an error-active or error-passive state.

For diagnostics, the 64-byte payload means a single frame can carry what used to require eight classic CAN frames. Multi-frame ISO-TP segmentation still exists for very long transfers, but far fewer segments are needed. That translates to faster DTC reads, quicker freeze-frame downloads, and dramatically shorter module programming times.

Which Vehicles Use CAN FD?

CAN FD adoption accelerated around 2019–2020. Early adopters include many European manufacturers who needed bandwidth for ADAS processing. By the mid-2020s, most new vehicles sold globally use CAN FD on at least some bus segments — often the powertrain and chassis backbones — while keeping classic CAN for lower-bandwidth body modules like seat heaters and window controllers.

DoIP: Diagnostics Go Ethernet

DoIP takes a fundamentally different approach. Instead of riding on the CAN bus, diagnostic traffic is encapsulated in TCP/IP packets and sent over automotive Ethernet — the same physical medium that connects cameras, radar modules, and infotainment ECUs inside the vehicle. A DoIP-capable scan tool connects to the vehicle through a standard OBD2 connector (pins 3 and 11 are allocated for Ethernet), but the communication is pure IP networking under the surface.

The speed advantage is enormous. A 100 Mbit/s Ethernet link can transfer a 500 MB calibration file in under a minute, compared to half an hour or more over classic CAN. Camera ADAS calibration routines, which may need to exchange image data with a target board, become practical in a shop environment rather than requiring dealership-only equipment.

How DoIP Discovery Works

When a scan tool connects, it broadcasts a Vehicle Identification Request on UDP port 13400. Every DoIP-capable gateway in the vehicle responds with its VIN, logical address, and supported diagnostic protocols. The tool then establishes a TCP connection to the gateway, which routes diagnostic requests (still using UDS service IDs) to individual ECUs behind it. From the technician's perspective, it looks like a normal scan session — the Ethernet plumbing is invisible.

What This Means for Your Scan Tool

The practical impact is simple but expensive: your scan tool either supports these protocols or it does not, and there is no software update that can add CAN FD or DoIP support to hardware that lacks the right transceiver chips.

Checking Your Scanner's Compatibility

Look for these indicators in your tool's specifications. A CAN FD-ready tool will list support for ISO 11898-1:2015 or explicitly mention "CAN FD." A DoIP-ready tool will reference ISO 13400 or "Diagnostic over IP." Some professional-grade tools support both. Budget adapters — including many popular Bluetooth ELM327-based dongles — support neither. They work fine on older vehicles and on the classic CAN segments of newer ones, but they cannot access CAN FD-only modules or DoIP gateways.

Classic CAN Isn't Dead

Despite the headlines, classic CAN 2.0 remains deeply embedded in the vehicle landscape. Most body-control modules, HVAC controllers, and many powertrain ECUs on vehicles built before 2020 still speak classic CAN exclusively. Even on brand-new vehicles, lower-priority subsystems may use classic CAN or LIN (Local Interconnect Network) to save cost. A good diagnostic strategy is layered: keep your reliable classic CAN tool for the bulk of your work, and add a CAN FD/DoIP-capable tool for newer vehicles that require it.

Future Trends: CAN XL and Beyond

The industry is already developing CAN XL, which promises payloads up to 2,048 bytes and data rates matching Ethernet while retaining CAN's deterministic arbitration. Automotive Ethernet itself is evolving from 100BASE-T1 to Multi-Gig speeds. For technicians and DIYers, the takeaway is that scan tool hardware will continue to evolve — buying tools with firmware-updatable protocol stacks and modular interfaces protects your investment longer than locked-down budget hardware.