Three doors, not three brands
OBD, Bench and Boot are not tools: they are access paths. The same Kess or the same Autotuner does all three. What changes is where you connect, what the ECU agrees to give you, and what you risk if it goes wrong.
The general rule: the deeper you go, the more protected areas you reach — and the more committing the job becomes.
OBD: simple, fast, often partial
You plug into the diagnostic port, the vehicle stays assembled, and you talk to the ECU through the vehicle network. It is the fastest mode and the least risky.
Its limit is structural: you go through the protocol the manufacturer chose to leave open. On many recent ECUs that only reaches the calibration area — the maps — and nothing else. For a Stage 1 on a common EDC17, that is enough. For an Immo Off that needs the EEPROM, usually not.
- For: nothing to remove, a few minutes, no mechanical risk.
- Against: frequently partial reads, depends on network stability and voltage.
- When: a standard remap on a well-supported controller.
Bench: the right balance
The ECU is removed and powered on the bench through a dedicated harness. You no longer go through the vehicle network but talk to the controller directly, while staying in its normal communication mode.
This is the mode that removes most of OBD's limits without Boot's drawbacks: generally complete reads, perfectly controlled voltage since you supply it yourself, and no component to touch.
- For: complete reads on most families, stable supply by design, case stays closed.
- Against: the ECU has to come out, and you need the right harness.
- When: as soon as OBD hands back a partial file, and always for anything involving the immobiliser.
Boot: total access, real risk
The case is opened and the microcontroller's boot pin is forced so the memory can be reached before the program runs. It is the only mode that reaches everything, including on an ECU that no longer starts.
It is also the only one that requires soldering or placing contacts on a board. One torn track, one badly placed ground, and the ECU goes from “recoverable” to “lost”.
- For: complete access, works on a bricked ECU, the only option on some locked families.
- Against: opening the case, physical work, irreversible risk.
- When: recovering a dead controller, or a family that offers no other way in.
How to choose in thirty seconds
| What you need | The mode | Why |
|---|---|---|
| Stage 1 / Stage 2 on a common ECU | OBD | The calibration area is enough, and it is the fastest. |
| OBD hands back a file that is too small | Bench | A complete read almost always goes through on the bench. |
| Immo Off, pairing, EEPROM | Bench | Those areas are almost never reachable over OBD. |
| The ECU stopped answering entirely | Boot | The only mode that works without valid software in memory. |
| Locked family, no other access | Boot | There is no alternative. |
And a shortcut that almost always holds: start with OBD, and go up one level only if the file you get is not enough. Nobody has ever bricked an ECU by reading it through the diagnostic port.
🔍 Got your read but not the file?
72,000 files indexed by ECU reference — Stage 1·2·3, Original, DSG, E85.
The mistakes that cost an ECU
- Going to Boot without trying Bench. In most cases that means opening a case for nothing.
- Trusting “read successful”. Always compare the size of the file you got against the expected size for that memory.
- Reading over OBD with the engine running or a weak battery. The worst moment for a write is also a bad moment for a read.
- Not saving the original read before modifying anything. It is the one thing that turns an accident into a simple rewrite.
In short
OBD is the front door: fast, safe, often partial. Bench is the serious working mode: complete reads, controlled voltage, case closed. Boot is the last resort: it reaches everything, including a dead controller, but it is paid for in physical risk.
Go up one level only when the previous one is not enough — and save the original whichever mode you pick.