What DoIP Protocol Means for Modern Vehicle Scanning

DoIP, short for Diagnostics over Internet Protocol, is the communication standard that replaced older serial-based vehicle diagnostic protocols in most post-2020 vehicles. It runs over Ethernet rather than CAN bus, which changes the hardware and software requirements for any scan tool trying to talk to those systems. Understanding what DoIP actually does, and why it exists, is the first step toward knowing whether your current diagnostic equipment can still handle modern vehicles.

Why DoIP Exists and What Problem It Solves

Traditional vehicle diagnostics ran over CAN bus, a protocol designed in the 1980s for real-time control signals between ECUs. CAN bus tops out at 1 Mbit/s in its standard form, which was adequate when vehicles had a handful of modules and diagnostic sessions involved pulling a few fault codes. Modern vehicles are a different situation. A current-generation luxury or electric vehicle can have over 100 electronic control units, each generating data simultaneously, plus features like over-the-air software updates, camera systems, and ADAS modules that transfer large datasets during calibration. CAN bus cannot move that volume of data fast enough for efficient programming sessions or full-system diagnostics. DoIP solves this by routing diagnostic traffic over automotive Ethernet, which operates at 100 Mbit/s or higher. A firmware reflash that would take 20 minutes over CAN can complete in under two minutes over DoIP. The protocol is standardized under ISO 13400, which defines how diagnostic requests and responses are packaged as UDP and TCP payloads and routed through the vehicle’s Ethernet backbone to the target ECU. The underlying diagnostic application layer, UDS (ISO 14229), stays the same, which is why DoIP is more accurately described as a transport layer change than a wholesale protocol replacement.

How DoIP Changes the Physical Connection

The OBD2 port itself did not change. Pins 1, 3, 11, and 12 of the standard 16-pin OBD2 connector are designated for Ethernet use under SAE J1962, and automakers began populating those pins in production vehicles as DoIP adoption increased. The scan tool connects to the same port it always has, but instead of communicating via CAN signals on pins 6 and 14, the DoIP session runs over the Ethernet pins. The critical difference is inside the scan tool itself. A DoIP-capable tool needs an Ethernet-capable interface chip, firmware that can establish a TCP/IP session, and software that understands how to address specific ECUs through the vehicle’s gateway module. Budget scan tools built around legacy CAN transceivers cannot establish a DoIP session regardless of software updates, because the hardware limitation is fundamental. Some manufacturers, notably BMW since around 2017 and Mercedes-Benz on newer platforms, also use DoIP for module programming in conjunction with their dealer tools. On vehicles like the Volkswagen Group’s MQB Evo and PPE platforms, DoIP is the primary diagnostic transport for ADAS calibrations and module coding. The 9 best OBD2 scanners with DoIP support covers which aftermarket tools actually implement the full ISO 13400 stack rather than just advertising the feature on the box (see the scanners verified for DoIP compatibility for a tested breakdown of what passes and what falls short).

DoIP and CAN FD: Two Parallel Protocol Shifts

DoIP is often discussed alongside CAN FD, but they operate at different levels of the vehicle network and solve different problems. CAN FD (Controller Area Network Flexible Data-rate) increases the CAN bus payload from 8 bytes to 64 bytes per frame and raises the data phase bitrate to 5 or 8 Mbit/s. It handles real-time control signals between ECUs on the internal vehicle network, while DoIP handles the connection between an external diagnostic tool and the vehicle’s gateway. A technician working on a 2022 Ford F-150 or a 2023 BMW 5 Series needs a scan tool that can handle both: CAN FD for reading live data from modules that communicate internally over the faster bus, and DoIP for initiating the diagnostic session itself through the Ethernet-based gateway. These are not redundant requirements, they address separate layers of the same diagnostic path. A scan tool that supports DoIP but not CAN FD will establish the session but may fail to read module data that is transmitted in CAN FD frames. Conversely, a CAN FD-capable tool without DoIP support cannot open a diagnostic session on vehicles where Ethernet is the gateway protocol. Manufacturers began mandating DoIP support in dealer scan tools around 2019 to 2021 depending on the platform, which is roughly when aftermarket tool makers started adding genuine DoIP hardware, the CAN FD scanner compatibility breakdown maps out which models cover both protocols in the same unit.

What DoIP Means for Scan Tool Buying Decisions

If your vehicle was manufactured before 2019, DoIP is largely irrelevant to your diagnostic work. CAN-based tools will read every system correctly because those vehicles use CAN as the primary transport. If you work on newer vehicles or plan to in the next few years, DoIP support is a concrete hardware requirement, not a marketing checkbox. Verify that the tool includes an Ethernet-capable adapter, explicitly lists ISO 13400 compliance, and has been tested against actual DoIP vehicle platforms rather than just claiming compatibility. Tools from Autel, Launch, and Topdon in the $500 to $1,200 range generally include genuine DoIP hardware in their current product lines. Below that price point, the feature is rarely implemented correctly. Professional shops that handle vehicles from multiple brands should also consider whether their existing pass-through interface supports DoIP, since many J2534 interfaces purchased before 2020 predate the standard. Replacing a pass-through interface is significantly cheaper than replacing a full scan tablet, so auditing what you have before a DoIP-only vehicle arrives on the lift is worth the ten minutes it takes. For independent shops evaluating their current equipment stack, diagnostic tools reviewed for professional shop use addresses this gap directly.

DoIP is not a feature trend, it is a protocol transition already underway in production vehicles on the road today. Vehicles built on Volkswagen’s MEB platform, BMW’s current 5 and 7 Series, and most post-2022 Mercedes-Benz models require DoIP for full diagnostic access. A scan tool without genuine ISO 13400 support will either fail to connect entirely or only access basic OBD functions through a legacy CAN fallback path. Knowing exactly where your equipment stands relative to this shift prevents the kind of diagnostic dead end that costs a shop real labor time on the lift.