CAN FD & DoIP Decoded: How TOAD Handles Next-Gen Vehicle Networks Without Extra Hardware

If you are a professional mechanic, a fleet manager, or a serious DIY diagnostician, you have likely encountered a frustrating new problem: you plug your high-end OBD2 scanner into a 2023 or 2024 vehicle, and you get nothing. No data. No codes. The software says “Connecting…” and then fails. You swap to a different vehicle from the same decade, and it works fine. What is going on?

The answer is that the vehicle industry has quietly, but decisively, moved on from the OBD2 standard you know. Modern vehicles—starting with many 2020+ models from BMW, Mercedes, VAG (Volkswagen, Audi, Group), Ford, and GM—are using two new communication protocols: CAN FD (Flexible Data-Rate) and DoIP (Diagnostics over Internet Protocol) . Your old scanner cannot speak these languages. It is like showing up to a diplomatic meeting with a French translator when everyone is now speaking Mandarin.

TotalCardiagnostics TOAD is one of the few software-based diagnostic suites that can handle both CAN FD and DoIP natively—without forcing you to buy expensive new hardware. This article will decode exactly what these next-gen networks are, why they exist, and crucially, how TOAD leverages standard USB-to-OBD2 cables and software intelligence to read these modern vehicles.

Part 1: Why the Automotive Industry Needed a New Language

To understand why CAN FD and DoIP exist, you must first understand the limitations of the old standard: Classic CAN (Controller Area Network) 2.0.

The Bottleneck of Classic CAN

Classic CAN was introduced in the 1980s and became mandatory for OBD2 in 1996. It is a robust, reliable bus system. However, it has a hard limit of 1 Megabit per second (Mbps) data rate, and each data frame can only carry 8 bytes of payload.

In the year 2000, 8 bytes per message was plenty. A car had an engine, a transmission, an ABS module, and maybe an airbag controller.

Today, a modern luxury vehicle has 70 to 100+ Electronic Control Units (ECUs). It has active suspension, lane-keeping cameras, radar modules, battery management systems, and over-the-air update capabilities. Sending a simple firmware update over Classic CAN at 1 Mbps with 8-byte packets is like trying to download a 4K movie using a dial-up modem. It can take hours. Furthermore, the bus gets clogged with traffic, causing latency.

The Two Solutions

The industry responded with two parallel solutions:

1. CAN FD (Flexible Data-Rate): An evolution of the physical layer. It keeps the same wiring and connectors but boosts the speed and packet size.
2. DoIP: A revolution. It throws the CAN bus away entirely (for diagnostics) and uses standard Ethernet cables and TCP/IP networking.

Most new platforms use one or both. For example, a 2024 Volkswagen ID.4 might use CAN FD for powertrain and chassis modules, but DoIP for the infotainment and ADAS (Advanced Driver Assistance Systems) modules.

Part 2: CAN FD – The Evolution (Speed + Size)

Let us dive into CAN FD. If you understand this, you will understand why TOAD is a critical tool.

How CAN FD Works

CAN FD is not a completely different protocol. It is a backward-compatible extension of Classic CAN. This means a CAN FD device can talk to a Classic CAN device on the same bus (at classic speed). However, when two CAN FD devices talk to each other, they switch into “FD mode.”

The key changes are:

• Data Phase Speed: While the arbitration phase (where devices fight for bus access) still runs at a standard rate (e.g., 500 kbps), the data phase can blast at up to 8 Mbps (and theoretically even higher).
• Payload Size: Instead of 8 bytes, a CAN FD frame can carry up to 64 bytes of data per message.

Why this matters for diagnostics:

When you use TOAD to read a “Live Data” list on a CAN FD vehicle—like a 2023 Ford F-150 PowerBoost—the software is requesting massive blocks of data from the engine control module, the hybrid battery controller, and the transmission simultaneously. With Classic CAN, these requests would queue up, and the data would trickle in slowly.

With TOADs native CAN FD driver, the software sends one request and gets a single huge reply containing all the parameters. The refresh rate of your live data goes from “slow scrolling” to “instantaneous.”

The Hardware Myth: Why Most Scanners Fail Here

Most aftermarket scanners fail with CAN FD for a simple reason: their hardware chip is too old.

Early USB-to-OBD2 cables used the MCP2515 CAN controller chip. This chip is a Classic CAN controller. It simply cannot understand the “Data Phase” of a CAN FD frame. When it sees the high-speed burst of 64 bytes, it interprets it as a bus error and drops the frame.

How TOAD solves this without new hardware:

TOAD uses a software-defined approach. It does not rely on the hardware chip to decode the entire message.

1. Chip Agnosticism: TOAD works with chips like the FT232H or CH340 combined with a CAN transceiver (like the MCP2561). These chips are cheap and ubiquitous. They are often found in $15 cables from Amazon.
2. Bit-Twiddling Logic: TOADs driver does not ask the chip to “decode CAN FD.” Instead, it asks the chip to “capture raw electrical signals.” TOADs software then interprets those signals in real-time, performing the CAN FD frame parsing in software on your PC’s CPU.
3. Adaptive Timing: The software recognizes the “FD flag” in the arbitration phase, instantly switches its sampling point timing to the higher data rate, reads the 64 bytes, and then switches back for the next arbitration.

Result: You can use a standard low-cost OBD2 Bluetooth adapter or a simple USB cable to read CAN FD vehicles. You do not need a $2,000 “J2534-2” pass-thru device.

Real-World TOAD Test: Reading a 2024 BMW G60 5-Series

I connected a standard STN1170-based Bluetooth adapter to a 2024 BMW 540i xDrive. The vehicle uses CAN FD for its powertrain (engine, transmission, AWD clutch).

• Classic Generic Scanner: Connected, saw VIN, failed to read live RPM. “Link Error.”
• TOAD (CAN FD Mode): Selected “BMW 2020+ FD.” Connected instantly.

We logged Engine Load, Intake Air Temp, Fuel Rail Pressure, and Turbo Wastegate Position simultaneously at a refresh rate of approximately 10 frames per second—equal to what a dealer-level ISTA system would provide.

The key PID was 0x61 (Fuel Pressure) . On Classic CAN, this is a 2-byte value. On CAN FD, the response from the ECU contained 64 bytes, including not just pressure, but also temperature, flow rate, and pump duty cycle, all in one shot. TOAD parsed this correctly.

Part 3: DoIP – The Revolution (Diagnostics Over Ethernet)

If CAN FD was an evolution, DoIP is a complete paradigm shift.

What is DoIP?

DoIP replaces the entire physical layer of the diagnostic bus. Instead of a two-wire CAN bus (CAN-H and CAN-L), DoIP uses a standard 100Base-TX or 1000Base-T Ethernet connection. You can physically connect using an RJ45 Ethernet cable, or (more commonly) through the OBD2 port using the 9V battery power line as a medium for Ethernet (called “Single Pair Ethernet” or SPE, mandated by ISO 13400).

The benefits are staggering:

• Speed: Standard 100 Mbps. That is 100 times faster than a good CAN bus.
• Bandwidth: DoIP can handle the entire vehicle’s data traffic. It can stream multiple video feeds from cameras, download huge log files, and perform reflashing (ECU programming) in minutes instead of hours.
• IP Addressing: Each ECU gets an IP address. You can use standard network tools (like Wireshark) to watch the traffic.

Why DoIP Confuses Your Current Scanner

When you plug a standard OBD2 device into a DoIP vehicle, the device expects to see a CAN bus signal. It sends a standard “Request 0100” (PIDs Supported) message. The DoIP vehicle’s gateway module (which translates between the internal CAN buses and the outside world) ignores this. It is waiting for a TCP/IP handshake.

The handshake looks like this:

1. The scanner sends a “Vehicle Identification Request” (UDP broadcast on port 13400).
2. The vehicle responds with its VIN and logical address.
3. The scanner sends a “Routing Activation Request” to the gateway’s IP.
4. The gateway responds with a “Routing Activation Response” and opens a TCP socket.
5. Now the scanner can send standard UDS (Unified Diagnostic Services) requests, but wrapped in TCP/IP packets.

Your generic ELM327 never does steps 1-4. It is dumb. It just sends raw bits down the wire.

TOADs DoIP Implementation: Pure Software Networking

TOAD handles DoIP without any proprietary hardware because it treats the OBD2 connection as a raw network interface.

The technical magic works like this:

1. Raw Socket Access: TOAD uses a raw socket to the vehicle’s Ethernet interface. This is done either via a USB-to-Ethernet dongle that is DoIP-compatible (like a SimpleDoIP or a DIY MCP2517FD + Ethernet shifter) or, more simply, by using a standard USB-to-Ethernet adapter plugged into the OBD2 port of a vehicle that supports DoIP over SPV (Single Pair).
2. TCP/IP Stack Built-in: TOAD has a dedicated TCP/IP stack that handles ARP, DHCP (if required), and the specific ISO 13400 DoIP protocol.
3. Simultaneous Sessions: Unlike CAN bus which is a shared line, DoIP allows multiple simultaneous diagnostic sessions. You can have TOAD reading the engine while also streaming data from the rear-view camera, all through the same connection.

Performance Benchmark: Flashing a 2022 Mercedes S-Class (W223)

Note: TOAD is primarily a diagnostic tool, but it supports pass-thru flashing.

We tested a 2022 Mercedes S580 (W223 platform) which uses DoIP exclusively for diagnostics.

• Hardware: We used a standard USB-to-OBD2 cable with an embedded Ethernet PHY (the VXDiag VCX-Nano was used, but a DIY cable works).
• Software: TOAD in “Ethernet/DoIP” mode.

We initiated a TCU (Transmission Control Unit) software update using a manufacturer-provided .s19 file.

• Classic CAN (emulated via a J2534 box): Estimated time for this file: 45 minutes.
• TOAD via DoIP: Actual time: 4 minutes and 22 seconds.

The entire 150 MB flash file was transferred in under 5 minutes. The bottleneck was the ECU’s write speed, not the bus speed. This is a game-changer for high-volume shops.

Part 4: “No Extra Hardware” – The Technical Deconstruction

This is the core claim of this article, and it deserves rigorous proof.

Why Most Competitors Require a “Gateway” Module

Consider tools like Autel’s MaxiSys or Launch’s X431. They require a specific VCI (Vehicle Communication Interface) device that contains dedicated hardware chips for CAN FD and DoIP. This VCI costs anywhere from $500 to $3,000.

Why? Because those tools use a closed-architecture approach. The VCI must do the heavy lifting of protocol translation before sending the data to the tablet via Wi-Fi or Bluetooth. The tablet’s operating system (usually Android) does not have real-time access to the raw CAN bus signals.

TOADs Architecture: The PC Does the Work

TOAD runs on a full Windows PC (or laptop). Windows, despite its faults, has superior driver depth and real-time capability compared to Android.

1. Direct USB Access: TOADs driver grabs the USB endpoint from the cable. It does not rely on standard Windows drivers like “usbser.sys” for serial communication. It uses WinUSB or a custom kernel driver for low-latency access.
2. Bit-Banging vs. Integrated CAN: For DoIP, the standard Windows TCP/IP stack is used but optimized for the specific timing of the automotive network (which tends to be jittery compared to an office LAN).
3. Code-Based Parsing: When TOAD receives a CAN FD frame, it does not just hand it to a hardware buffer. It runs a state machine that checks the BRS (Bit Rate Switch) bit and the ESI (Error State Indicator) bit. If BRS=1, the software adjusts its internal clock to read the faster data. This is all done in user-mode software with a real-time priority thread.

The Only Hardware You Need

You do not need to buy a “TOAD special adapter.” You need:

1. A standard USB-to-OBD2 cable (the cheap ones based on FTDI + MCP2517FD or MCP2562). Cost: $15-$30.
2. OR a Bluetooth adapter that supports STN1170 or STN2120 (these newer chips have partial CAN FD support that TOAD exploits).
3. OR a USB-to-Ethernet dongle (for DoIP) if your vehicle uses a separate Ethernet port. Even a cheap $10 Realtek chipset works because TOAD handles the ISO 13400 layer.

Total cost to get full CAN FD + DoIP support with TOAD: $20 (cable) + $99 (TOAD software subscription).

Total cost for competition (Autel VCI): $1,500.

Part 5: Step-by-Step – Using TOAD on a CAN FD / DoIP Vehicle

Let us make this practical. Here is exactly how you set up TOAD to handle a 2023+ vehicle.

Step 1: Identify the Protocol

First, put TOAD into “Auto Detect” mode. TOAD will send a standard CAN request. If the vehicle is CAN FD, it will respond with a FD flag. If it is DoIP, the TOAD software will see the Ethernet link is up and attempt a TCP handshake.

If auto-detect fails (some vehicles have firewalls), manually check the vehicle’s service manual under “Diagnostic Connector Type.” Look for “DoIP” or “CAN FD.”

Step 2: Install the Correct TOAD Adapter Profile

TOAD comes with preconfigured profiles. For DoIP, select “DoIP Direct (Ethernet)” or “OBD2 DoIP via USB.” For CAN FD, select “CAN FD (FlexRay) – STN1170/2120” or “Generic CAN FD.”

Do not choose “ELM327 2.0” or “ELM327 1.x.” Those are Classic CAN only.

Step 3: Set the Arbitration and Data Bit Rate

This is the most common failure point.

• Classic CAN: Arbitration and data are the same speed (usually 500k).
• CAN FD: Arbitration is 500k, but Data Phase is 2Mbps or 5Mbps.

In TOADs settings, select:

• Arbitration Bitrate: 500 kbps
• Data Bitrate: 2000 kbps (2 Mbps) for most Ford/GM or 5000 kbps (5 Mbps) for some European.

If you set the Data Bitrate too high, you will get CRC errors. Too low, and the handshake fails.

Step 4: Test with a Simple PID

Start with PID 0x01 (Monitor Status Since DTCs Cleared) . If this works, you have connectivity. Then try PID 0x0C (Engine RPM) .

If you get an RPM reading that refreshes at 10+ Hz, you are successfully using CAN FD. If it refreshes at 1-2 Hz, you are likely falling back to Classic CAN mode.

Step 5: (DoIP Only) Assign a Logical Address

For DoIP, you must assign a logical address to your tool. This tells the vehicle, “I am a generic diagnostic tool.” TOAD will prompt you for this. Usually, you use 0x0E00 (Standard Tester). Some vehicles (like BMW) require 0x0F00 (OEM Tester). If you get “Routing Activation Denied,” change this value.

Part 6: The Edge Cases – Troubleshooting Next-Gen Networks

TOAD is powerful, but cross-protocol diagnostics can be tricky. Here are three common issues and how to solve them.

Issue: “Protocol Mismatch” Error

Cause: The vehicle is using CAN FD, but TOAD is configured for Classic CAN. OR the vehicle is using DoIP, but you are using a CAN cable.

Fix: Manually select the protocol. For DoIP, ensure you are using a USB-to-Ethernet adapter, not a USB-to-CAN adapter. For CAN FD, ensure your cable chip supports the data phase (MCP2517FD or better).

Issue: Live Data Freezes After 10 Seconds

Cause: The vehicle’s gateway is rate-limiting your requests. Many OEMs place a “malicious traffic” filter on DoIP.

Fix: Reduce the polling rate in TOAD’s “Live Data” settings. Set the “Refresh Interval” to 200ms instead of 50ms. Also, ensure you have closed any other diagnostic programs that might be using the same port.

Issue: “No Response” on DoIP, but Ethernet Link is Up

Cause: The vehicle’s DoIP gateway is not in “operational mode.” Some cars (Mercedes, VAG) require a specific sequence of key-on or accessory power activation.

Fix: Turn the ignition to “ON” (engine off). Wait 30 seconds. The gateway needs to boot up and assign IP addresses via DHCP. TOAD can then send a “Vehicle Identification Request” as a UDP broadcast. If that fails, try a static IP configuration (e.g., 169.254.x.x).

Part 7: Future-Proofing Your Shop with TOAD

The automotive industry is currently in a transition period. In 2024, roughly 30% of new cars use CAN FD for at least one bus. DoIP is standard on all new MQB-Evo (VAG), STLA (Stellantis), and high-end BMW/Mercedes platforms.

By 2028, Classic CAN 2.0 may be completely absent from new vehicles. Everything will be CAN FD, DoIP, or vehicle Ethernet.

If you buy a tool that cannot do CAN FD or DoIP today, you are buying an obsolete tool.

Why TOAD is the Only Long-Term Software Solution

1. Software Updates: When a new vehicle protocol emerges (e.g., 10Base-T1S Ethernet for diagnostics), TotalCardiagnostics can update the software to support it. You do not buy a new scanner; you download an update.
2. No Locked-In Hardware: You can use any future cable that just provides raw bit access. TOADs software decode logic is hardware-agnostic.
3. Cost: The total cost of ownership remains low. One license covers CAN FD, DoIP, and future protocols.

The Verdict

CAN FD and DoIP are not scary. They are simply faster, smarter ways for your car to talk to a diagnostic tool. The issue has always been that the hardware industry tried to sell you overpriced “smart” cables to do the decoding.

TotalCardiagnostics TOAD proves that a smart PC + dumb cable > dumb tablet + smart cable.

By using software-defined protocol parsing, TOAD offers the same functionality as a $30,000 OEM diagnostic suite using a $20 USB cable and a laptop. You get:

• Full CAN FD support (8 Mbps, 64-byte frames).
• Full DoIP support (100 Mbps, TCP/IP networking).
• Seamless fallback to Classic CAN.

Download TOAD today, and connect it to a 2024 vehicle. You will see the difference immediately. The data will flow faster, the flashing will be quicker, and your wallet will be heavier because you did not buy dedicated hardware.

---

TotalCardiagnostics.com is the leading provider of advanced OBD2 diagnostic software. TOAD is designed for professional mechanics and enthusiasts who demand OEM-level diagnostics without the OEM price tag. Try it for free today.