Last Tuesday evening, a WhatsApp voice note came in from Miguel, who runs a five-bay independent workshop in Valencia and has never sold a used EV in his life. His message ran to forty seconds and it was not a request for a price. “I have a 2023 BYD Atto 3 on the ramp that will not charge and my dongle shows me nothing. Not a code, nothing. My supplier in Shenzhen says send me photographs of the DC socket. Photographs.” The car had been on the ramp for a day and a half.
Miguel’s problem was not that he bought a bad tool. It was that most diagnostic tools still sold for EV work were built for a car that no longer exists. A reader that speaks only the older OBD protocol will interrogate a 2023 Atto 3 the way a 1998 diagnostic cable interrogates a tractor: it connects, it asks, and nothing answers.
So this guide is about capability rather than brand. Which protocol layers a workshop actually needs in order to read a fault on the cars now arriving from China, what each missing layer costs in bench time, and how to buy a kit that will still be useful in five years rather than a drawer full of dongles. Every tool named here is a real line in our catalogue, and for each one I have written down what it does not do, because that is the part that decides your afternoon.
One caveat before we start. Diagnostic capability in 2026 is not a single product you buy once; it is a stack, and the stack is only as good as its lowest layer. A tablet that reads beautifully over DoIP will still leave you guessing when the fault is a cooling circuit or a door lock actuator, because those are module-specific behaviours that live outside the fault-memory tree.
The Protocol Stack Decides What Your Workshop Can See
Modern vehicles talk over a layered set of protocols, and almost every unhappy workshop I speak to has bought a tool that stops one or two layers short of the car in front of it. Here is the stack in the order it matters when a fault is live.
| Protocol layer | What it actually is | Where you meet it |
|---|---|---|
| OBD-II and KWP2000 | The 1990s diagnostic standard, still alive on older Japanese and Korean hybrids | Mostly pre-2018 cars, and the reason cheap dongles feel familiar |
| CAN, classic | A 500 kbit/s two-wire bus, the backbone of vehicle electronics since roughly 2010 | Body control, BMS, chargers and inverters on most 2018+ EVs |
| CAN FD | The same bus at up to 5 Mbit/s, able to move far larger diagnostic payloads | Newer Chinese platforms and the Volkswagen ID family, 2022 onward |
| DoIP | Diagnostics tunnelled over the car’s own ethernet port instead of a USB cable | Volkswagen Group and most premium European marques |
| UDS, ISO 14229 | The message set that rides on top of CAN FD and DoIP | Everything modern, and the reason a reader without it returns silence |
| Brand fault trees | The manufacturer’s own service data: known fault paths, coding, guided tests | Only from the vendor’s own software, which is why a generic reader has a ceiling |
The practical consequence is that “it is an OBD scanner” is no longer a meaningful description of a diagnostic tool, in the same way that “it has a battery” is no longer a meaningful description of a phone. A tool that clears codes is cheap and broadly useless. A tool that reads the fault, knows the fault tree, and can act on the module is the one that decides whether the vehicle leaves the bay this afternoon.
There is a second distinction worth drawing early, because tool vendors blur it on purpose: reading versus writing. Reading a code and clearing it is one permission level. Writing — coding a module, pairing a new high-voltage component, setting a seat-to-module calibration, running a guided active test — is a different one, and it is the level that turns a tool from a code reader into something you can bill diagnostic time against.
Three Tools That Cover Most of a Real Bay
Miguel’s bay is typical: a mix of Volkswagen Group cars, a couple of Chinese imports, and enough older hybrid Toyota to pay the rent. Three tool classes cover that mix, and each one has a real product behind it in our catalogue.
The DoIP-capable tablet
For the Volkswagen side and most of the newer Chinese platforms, the single most useful purchase is a tablet that speaks DoIP and CAN FD rather than classic CAN alone. The unit we list most often for this is the VAS 6154A CAN FD and DoIP diagnostic tablet, which covers CAN FD and DoIP in one box and is the reason a 2022 ID.4 or a recent Chinese platform reads at all instead of returning an empty response.
Two things to check before you buy any tablet of this type. First, ask for the DoIP support to be demonstrated on a vehicle you can reach, not shown in a brochure, because DoIP requires a wired ethernet path to the car and a lot of cheap units quietly implement only the USB variant. Second, ask what the update path is. A tablet that needs a USB stick and a dealer visit to update is a tablet that will be silently wrong within eighteen months.
The brand-original diagnostic head
A DoIP tablet still does not know how a Mercedes thinks. For brand-specific fault trees, guided active tests and secure variant coding you need the manufacturer’s own head, and the Mercedes-Benz Xentry diagnostic head is the Mercedes-Benz Xentry diagnostic head we supply. The honest way to describe these is as an insurance policy on a small number of vehicles: you will not use it every day, but the day you have one, the alternative is a day of guesswork.
If your volume justifies it, the same logic applies across brands. A workshop taking two or three vehicles a week from one marque will usually come out ahead with that marque’s own head; a workshop taking one a month will not, and should buy capability rather than brand depth.
The restraint and airbag reset tool
This is the cheapest item on the list and the one most workshops discover they need only after they have already had the car apart. After any front-end collision work, the airbag and seatbelt pretensioner circuits have to be read, cleared and reset correctly, and without that step the vehicle may pass a workshop test while the restraint system still refuses to arm. A dedicated unit such as an airbag replacer and resistance tester handles the resistance measurement and the reset in one place, and it is the difference between a completed repair and a vehicle that goes back to the customer with a warning light.
Reading the Fault Is the Easy Half
Most of the bench time I am asked about is not lost reading codes. It is lost after the code is read, when the fault turns out to be a behaviour rather than a memory entry, and the workshop realises it needs a part, a procedure, or a tool it does not have.
1. The module that refuses to pair
High-voltage modules and comfort modules on Chinese EVs frequently arrive with no fault code at all. They simply do not work until they are paired or coded to the vehicle. A replacement on-board charger for the Li Auto L7, such as an on-board charger for the Li Auto L7, is mechanically and electronically correct the moment it arrives, and will still sit dead on the bench until the pairing step is done with the right software. Same story with an entry and start permit control unit for the Audi Q5 e-tron — an entry and start permit control unit for the Audi Q5 e-tron will install cleanly and do nothing until the coding is run.
The practical test: if a module swap has produced no change and no new code, suspect pairing before you suspect the part. This single habit saves more bench days than any upgrade on this page.
2. Radar and camera calibration after body work
Any body panel replacement on a modern car is also a sensor alignment job. Replace a bumper or a door and the radar behind it may be physically fine and geometrically wrong. An AGRU reversing radar for the Audi Q7, an AGRU reversing radar for the Audi Q7, and a radar sensor for the Audi Q5 e-tron, a radar sensor for the Audi Q5 e-tron, both read correctly and both still need a calibration pass with the correct target board afterwards.
This is where parts and diagnostics meet, and it is worth quoting the panel work properly. An AVATR 11 full body panel set, an AVATR 11 full body panel set, or a Li Auto L8 set, a Li Auto L8 full body panel set, is a sensor-relevant job, not a cosmetic one. Quote the calibration with the panels and you will not be the one explaining the fault later.
3. Coolant circuit drift
Thermal faults on electric vehicles are frequently reported as a battery or charger fault when they are actually a cooling circuit problem, and the difference can be a hose. A coolant hose for the Volkswagen ID.7, a coolant hose for the Volkswagen ID.7, is the sort of part that looks trivial in the catalogue and decides whether you are chasing an electronics ghost for a week. On any EV that reports a temperature plausibility fault, the cooling circuit is worth checking before the module is condemned.
4. Door lock actuators and body electronics
The most common single-part fault on modern vehicles is now a small electromechanical actuator rather than a large electronic module. A front left door lock actuator for Xiaomi vehicles, a front left door lock actuator for Xiaomi vehicles, is a good illustration: the vehicle reports a body controller fault, the controller is fine, and the actuator is what has failed. Reading the fault takes a minute; diagnosing it properly requires understanding that the code is a symptom.
5. Rolling radius and tyre specification
Finally, and this one catches everyone once: a wheel-speed or traction fault on a car that has been fitted with the wrong tyre specification is not a tyre fault, it is a diagnostic one. A 225/58R19 99W tire for the BYD Song PLUS, a 225/58R19 99W tire for the BYD Song PLUS, is a specific diameter, width and load index, and a close-but-wrong fitment changes the rolling radius enough for the vehicle to argue with its own stability system.
What an Importing Workshop Needs That a Dealer Workshop Does Not
If your customer base includes cars imported from China, there is one diagnostic environment a dealer workshop never has to deal with, and it is the charging interface. The car speaks one standard, the cable in your bay speaks another, and the vehicle will report a fault that is genuinely a handshake failure.
The fix is unglamorous and cheap. A GBT to CCS2 DC charging adapter, a GBT to CCS2 DC charging adapter, an EU to China EV charging adapter, an EU to China EV charging adapter, and a European to GB electric vehicle charging adapter, a European to GB electric vehicle charging adapter, cover the three combinations that come up constantly, and having them on the shelf turns an hour of argument with a customer into a five-minute test.
The charging pile on the ramp
Once you are testing the charging side, you need a known-good supply to test against, and that is where a pile becomes a diagnostic instrument rather than a product. A 7 kW to 30 kW AC charging pile, a 7 kW to 30 kW AC charging pile, lets you prove the vehicle’s onboard charger, the cable and the vehicle’s request all in one sequence. For a workshop that sees charging faults regularly, it pays for itself faster than any software subscription.
Seven Questions to Ask Before You Buy Any Diagnostic Tool
Every one of these has come up in a conversation with a customer who had already bought the tool. Ask them before you buy, not after.
1. Does it speak DoIP, or only CAN? If the seller cannot show you DoIP working on a physical vehicle, treat the claim as absent. This single question separates the tools that will read your 2024 cars from the tools that will read last decade’s.
2. Is CAN FD genuine, or CAN 2.0 with a sticker? Ask for the bus speed, and ask them to show it reading a module that only transmits on CAN FD. If the answer is vague, assume classic CAN.
3. Which marques does the software cover, and is the list published? An honest vendor publishes a coverage list including the model years. A vendor who says “all Chinese EVs” is describing a marketing position, not a tested one.
4. What happens to the licence when the vendor updates? Diagnostic software is a subscription you did not know you were taking on. Some tools require an annual code, some need a USB update at a dealer, and a few silently stop supporting vehicles that are more than three years old.
5. Can it be installed on the machine already in the bay? Check the processor, the free disk space and the operating system version before it arrives, because setting up a Windows laptop for diagnostics on a Friday afternoon is not a good use of Friday afternoon.
6. Does it read only, or does it code and pair? This is the question that decides whether the tool is a code reader or a diagnostic system. Ask specifically whether you can run a module pairing and a guided active test.
7. What is the return path when it fails mid-diagnosis? Diagnostic tools fail, and they fail at the worst moment. Ask what the RMA path is and how long a replacement takes, in writing, before you pay.
Three Kit Levels, and Where Each One Breaks
The market offers three broadly distinct kits, and most buying mistakes come from paying for level three when level two would do, or level one and hoping.
| Kit | What it covers | Where it stops |
|---|---|---|
| Single-brand reader | Read and clear codes on one marque, usually over classic CAN | The first Chinese import that speaks a different protocol family |
| Multi-brand read and clear | CAN plus CAN FD across several marques, often with DoIP | Brand-specific coding, guided fault trees and module pairing |
| Brand-original head plus tablet | Coding, parameterisation, pairing and guided diagnosis on the marques the head covers | Only the marques it covers — and it needs updating when the vendor revises it |
For a workshop like Miguel’s, the honest answer is usually level two plus a restraint tool, with a brand head bought later and only if the volume justifies it. The common mistake is the opposite one: a single-brand reader on a shelf that sees four different marques every week, which is a tool that reads the car in front of it exactly half the time.
The Bench-Day Math
Miguel’s Atto 3 took a day and a half, and the tool that would have shortened it was not expensive. It was a matter of reading the fault at all. A workshop charging a day rate for a fault it cannot read is charging a day rate for a guess, and the customer’s second question is always the same: what happens next?
Put it the other way round. If your average diagnostic job is worth, say, a few hundred euros of bay time, then the tool that turns one lost day per month into one saved hour per month has paid for itself inside a year — and that calculation does not even count the goodwill, because the workshop that answers on the first call gets the next three jobs as well.
The counter-argument is worth making honestly. If your volume is one EV a fortnight and your customer base is a single marque, a better brand head may beat a broader multi-brand tablet. Coverage should follow the cars you actually see, not the cars the vendor’s brochure shows.
What We Tell Customers Who Ask Us First
We send a lot of workshops through this decision, and the pattern in what they end up buying is consistent enough to be worth writing down.
Buy capability before you buy brand. A multi-brand tablet with CAN FD and DoIP will keep working across marques for years. A single-brand tool that is right for today’s mix will be wrong within eighteen months, because the mix changes faster than the tool does.
Check the protocol coverage against the cars on your ramp this month. Not the cars in the brochure. If a marque you work on every week is not on the published list, that tool is not for you.
Treat pairing and coding capability as the deciding feature. Reading is a commodity now. Being able to make the part you just fitted actually work is not.
Keep the restraint tool. It is cheap, it is small, and it is the only item on this page that prevents you having to send a vehicle back to the customer with an unresolved warning.
Do not skip the charging interface stock. If you touch imported Chinese EVs, three adapters and a known-good pile will pay for themselves faster than any software licence.
And if you are still unsure, send us the last three jobs that ran long on your bench, with the marque, the year and what you found. We will tell you straight whether the missing capability was diagnostic or whether you were chasing the wrong part — and we have told several customers exactly that, including one who was about to order a tool he did not need.
Because the cheapest diagnostic tool in the world is not the one with the lowest price. It is the one that tells you what is actually wrong, while the customer is still in the building.
— Wang (JLL Auto Parts founder) · 13 years sourcing EV parts from Shanghai · jllautoparts.com

