CAN FD Protocol Explained: Why Your Next Scanner Needs It

If you have tried to scan a 2022 Ford Bronco, a 2023 Chevy Silverado, or a 2024 Toyota Tundra with an older diagnostic scanner and gotten nothing but communication errors, you have already run into the CAN FD problem. Your scanner is not broken. It is speaking a language the vehicle does not understand anymore.

CAN FD — Controller Area Network with Flexible Data-rate — is the most significant change to vehicle communication protocols in over 30 years. It is not coming in the future. It is here now, and it is making scanners purchased even two or three years ago partially or fully obsolete on the newest vehicles. Here is what every technician, shop owner, and serious DIYer needs to understand.

A Quick History: How We Got Here

The original CAN bus protocol was developed by Bosch in 1986 and became the standard vehicle communication network throughout the 1990s and 2000s. When OBD2 was mandated in 1996, CAN was one of several allowed protocols (alongside J1850, ISO 9141, and KWP2000). By 2008, CAN became the sole required OBD2 protocol for all new US vehicles.

Classic CAN works well. It is reliable, deterministic, and well-understood. But it has fundamental limitations:

Maximum data rate: 1 Mbps (megabit per second)
Maximum payload: 8 bytes per frame
Bandwidth: Adequate for traditional vehicles with 30-40 ECUs, insufficient for modern vehicles with 60-100+ ECUs

As vehicles added more electronic content — advanced driver assistance systems, infotainment with over-the-air updates, electrified powertrains, camera systems, radar modules — the classic CAN bus became a bottleneck. There was simply too much data for the available bandwidth. Manufacturers needed a faster pipe.

What Is CAN FD?

CAN FD was developed by Bosch and standardized as ISO 11898-1:2015. The "FD" stands for "Flexible Data-rate," and the name describes its key innovation: the data rate can increase during the data phase of each frame while maintaining compatibility with classic CAN for the arbitration phase.

Here are the technical improvements over classic CAN:

Faster Data Rates

Classic CAN tops out at 1 Mbps. CAN FD supports data rates up to 8 Mbps during the data phase of a frame — an 8x improvement. The arbitration phase (where modules compete for bus access) still runs at 1 Mbps for backward compatibility, but once a module wins arbitration, data transfers at the higher speed.

Larger Payloads

Classic CAN frames carry a maximum of 8 bytes of data. CAN FD frames can carry up to 64 bytes — an 8x increase. This means more data per frame, fewer frames needed, and less bus overhead. A single CAN FD frame can carry what previously required 8 classic CAN frames.

Improved Error Detection

CAN FD uses a longer CRC (Cyclic Redundancy Check) field — 17 or 21 bits compared to classic CAN's 15 bits. This provides stronger error detection capability, which is important given the higher data rates where bit errors are more likely.

The Combined Effect

When you multiply the faster data rate by the larger payload, the effective throughput improvement is dramatic. CAN FD can transfer data roughly 8 to 30 times faster than classic CAN, depending on the specific implementation. For diagnostic scanning, this means faster module communication, faster live data streaming, and faster ECU reprogramming.

How CAN FD Differs from Classic CAN: The Technical Details

For technicians who want to understand what is happening at the protocol level, here are the key differences:

Frame Format

CAN FD frames are similar to classic CAN frames but with critical modifications:

FDF bit (FD Format) — This bit (formerly the reserved bit in classic CAN) indicates whether the frame is classic CAN or CAN FD. A recessive bit means CAN FD; a dominant bit means classic CAN.
BRS bit (Bit Rate Switch) — Unique to CAN FD. When set, the bit rate switches from the arbitration rate to the higher data rate after the BRS bit. This is the "flexible data-rate" in action.
DLC field — The Data Length Code has been extended. Classic CAN DLC values 0-8 map directly to byte counts. CAN FD adds DLC values 9-15 mapping to 12, 16, 20, 24, 32, 48, and 64 bytes respectively.
ESI bit (Error State Indicator) — Indicates whether the transmitting node is in error-active or error-passive state.

Physical Layer Compatibility

CAN FD uses the same physical layer (wiring, connectors, transceivers) as classic CAN. This is important: the wiring harness does not change. The difference is in the controller chip that interprets the signals. A classic CAN controller chip physically cannot process CAN FD frames because it does not understand the FDF and BRS bits and will interpret them as errors.

This is exactly why a scanner without CAN FD hardware support cannot communicate with CAN FD modules. It is not a software limitation — the transceiver chip on the scanner's VCI (Vehicle Communication Interface) hardware must support CAN FD at the silicon level.

Which Vehicles Use CAN FD?

CAN FD adoption has accelerated rapidly since 2020. Here is a detailed breakdown by manufacturer:

Ford

Ford was the first major US manufacturer to widely adopt CAN FD. Their transition has been aggressive:

2020+: Mustang Mach-E (full CAN FD architecture)
2021+: F-150 (14th generation), Bronco, Bronco Sport, Maverick
2022+: F-150 Lightning, E-Transit
2023+: Most remaining models transitioning to CAN FD
2025+: Entire lineup on CAN FD

If you work on Ford vehicles, CAN FD capability is not optional. It has been mandatory since approximately 2021 model year.

General Motors

GM's CAN FD rollout has been tied to their new platform architectures:

2020+: Corvette C8 (first GM CAN FD vehicle)
2022+: Hummer EV, Cadillac Lyriq
2023+: Silverado/Sierra (new platform), Colorado/Canyon, Blazer EV, Equinox EV
2024+: Majority of new GM models

Stellantis (Chrysler, Dodge, Jeep, Ram)

2022+: Grand Wagoneer, Wagoneer
2023+: Ram 1500 (DT platform), new Jeep models
2024+: Expanding across the lineup

Toyota / Lexus

2022+: Tundra (new TNGA-F platform), Lexus LX
2023+: Sequoia, Tacoma (new generation), Grand Highlander
2024+: Land Cruiser, additional new-generation models

BMW

2021+: iX, i4 (new platforms)
2023+: 5 Series (G60), 7 Series (G70), X1 (U11)
2024+: Most new-generation models

Hyundai / Kia / Genesis

2022+: Ioniq 5, EV6, GV60 (E-GMP platform)
2024+: Ioniq 6, EV9, expanding to more models

Other Manufacturers

Volkswagen Group (VW, Audi, Porsche): 2021+ on new platforms, widespread by 2024
Mercedes-Benz: 2021+ EQS and new platforms, expanding through 2024
Honda / Acura: 2023+ on newer platforms
Nissan / Infiniti: 2024+ on next-generation platforms
Rivian, Lucid, other EVs: CAN FD from launch (all-new architectures)

Why Older Scanners Cannot Read CAN FD

This is the critical point that many technicians misunderstand: CAN FD incompatibility is a hardware problem, not a software problem.

When a scanner's VCI (the OBD2 dongle) connects to a vehicle, it communicates through a CAN transceiver chip. Classic CAN transceiver chips (like the common NXP TJA1040 or TJA1050) cannot process CAN FD frames. When they encounter a CAN FD frame on the bus, they interpret the FDF bit as an error and reject the frame. No amount of firmware updates can change this because the limitation is in the silicon.

To support CAN FD, a scanner's VCI must use CAN FD-capable transceiver chips (like the NXP TJA1443 or TJA1463). These chips are backward-compatible with classic CAN, but classic CAN chips are not forward-compatible with CAN FD.

Here is what happens in practice when you connect an old scanner to a CAN FD vehicle:

Best case: The scanner reads some modules that still use classic CAN (some vehicles run mixed networks) but cannot access CAN FD modules. You get partial data with missing systems.
Common case: Communication error on connection. The scanner cannot establish a diagnostic session with any module on the CAN FD bus.
Worst case: The scanner connects but displays incorrect or garbled data because it is misinterpreting CAN FD frames as corrupted classic CAN frames.

This is not hypothetical. Shops across the country are experiencing this right now with scanners purchased as recently as 2020-2021. A two-year-old professional scanner that cost thousands of dollars may not be able to scan the newest Ford F-150 in your bay.

DoIP: The Next Protocol Layer

While CAN FD is the immediate priority, there is another protocol gaining traction: DoIP (Diagnostics over Internet Protocol), standardized as ISO 13400.

DoIP uses Ethernet-based communication rather than CAN. It is dramatically faster — up to 100 Mbps compared to CAN FD's 8 Mbps. DoIP is primarily used for:

ECU reprogramming (where large data transfers make Ethernet's speed advantage most apparent)
Centralized computing architectures where a single powerful ECU manages multiple vehicle domains
Vehicles with advanced infotainment and autonomous driving systems that generate massive data volumes

Currently, DoIP is found primarily on European luxury vehicles (BMW, Mercedes, VW Group) and some high-end EVs. It will become more widespread as vehicle architectures consolidate from dozens of separate ECUs to a few powerful central computers. When shopping for a scanner, DoIP support is a forward-looking bonus rather than an immediate necessity for most shops, but it is worth noting which scanners include it.

ThinkCar CAN FD Capable Models

ThinkCar has built CAN FD support into the hardware of their current professional scanner lineup. Here are the models with confirmed CAN FD capability:

ThinkCar Master 2 — Full CAN FD and DoIP support. Flagship professional scanner with the latest VCI hardware. Handles everything from classic CAN vehicles to the newest CAN FD platforms. [LINK: professional-scanners]
ThinkCar Platinum S10 — CAN FD support in a mid-range professional package. The best value option for shops that need CAN FD capability without flagship pricing. [LINK: platinum-s10]
ThinkCar Reader 8 — CAN FD support in a compact form factor. Excellent for mobile technicians and advanced DIYers who need future-proof hardware at an accessible price point. [LINK: reader-8]

All of these models include lifetime free software updates, which means as new CAN FD vehicle coverage is added, you receive it automatically without any additional cost. [LINK: scanner-buying-guide]

Future-Proofing Your Diagnostic Setup

Here is the practical advice for shops and technicians evaluating their diagnostic tool strategy:

If You Are Buying a New Scanner

CAN FD support is mandatory. Do not buy any scanner in 2026 that lacks CAN FD hardware capability, regardless of how good the price looks. Within two years, the majority of new vehicles entering your shop will require CAN FD communication. A non-CAN FD scanner purchased today will have a useful life measured in months, not years.

If Your Current Scanner Lacks CAN FD

You have two options:

Supplement: Keep your existing scanner for the older vehicles that make up the bulk of your current workflow, and add a CAN FD-capable scanner for newer vehicles. This is the most cost-effective approach if your current tool still has years of useful life on older vehicles.
Replace: If your current scanner is aging and you are already experiencing coverage gaps, replace it with a CAN FD-capable unit. The ThinkCar Platinum S10 offers professional CAN FD diagnostics at a price point that makes the transition painless. [LINK: thinkcar-vs-snapon-autel]

What to Verify Before Buying

Do not take marketing claims at face value. Verify CAN FD support with these questions:

Is CAN FD support in the VCI hardware, or is it a planned software update? If the answer is software update, the VCI hardware likely does not support it. Walk away.
Which CAN FD transceiver chip does the VCI use? A legitimate manufacturer can answer this question. Common CAN FD chips include the NXP TJA1443, TJA1462, TJA1463, and Microchip ATA6561.
Can you demonstrate CAN FD communication on a specific vehicle? Ask the vendor to show the scanner communicating with a known CAN FD vehicle like a 2023+ F-150 or Silverado. If they cannot demonstrate it, the claim is unverified.
Does the scanner also support DoIP? This is not critical today but indicates the manufacturer is thinking ahead.

The Timeline: How Fast Is CAN FD Taking Over?

Based on current manufacturer adoption rates and announced platform plans:

2024: Approximately 35-45% of new vehicles sold in the US use CAN FD on at least some bus segments
2025: Approximately 55-65% of new vehicles use CAN FD
2026: Approximately 70-80% of new vehicles use CAN FD
2028: Expected to reach 90%+ adoption on new vehicles

Remember that shops do not only work on new vehicles. The average age of vehicles on US roads is 12.6 years, so classic CAN vehicles will be in shops for another decade or more. But the trend is clear and irreversible. Every year, a larger percentage of the vehicles rolling into your bay will require CAN FD capability.

The Bottom Line

CAN FD is not a feature to consider. It is a requirement. The protocol transition is already well underway, and any scanner purchased today without CAN FD hardware support has a limited remaining useful life. The good news is that CAN FD-capable scanners do not carry a significant price premium — the ThinkCar lineup offers CAN FD support across multiple price points with lifetime free updates to ensure your coverage stays current as new CAN FD vehicles hit the market.

Do not wait until you cannot scan the truck in bay three to make this decision. Check your current scanner's CAN FD capability today, and if it falls short, explore ThinkCar's CAN FD-ready lineup. [LINK: all-products]