OBD is dead.
That's where
bench starts.
When the scanner can't connect, the diagnostic path doesn't end — it moves to the bench. Failed flash, water damage, power surge, bricked write — each has a different recovery path. We work out which one before we quote.
$ obd --scan --all-protocols
[ERR] No response — CAN / K-Line / DoIP
OBD path terminated.
$ bench --power --rail-check
[OK] 12V supply stable — 11.97V
[OK] Ground continuity — all pins
$ bench --can-transceiver --check
[WARN] CAN Hi/Lo — no response
Transceiver: suspected fault
$ jtag --connect
[OK] JTAG detected — Bosch ME17.9
$ jtag --read-flash --output=dump.bin
[>>] Reading 4MB flash...
[OK] Read complete — checksum verified
[OK] Calibration region intact
$ jtag --reflash --input=correct.bin
[OK] Flash written and verified
$ bench --comms --test
[OK] ECU responding on CAN — 0x7E8
[OK] Module ID confirmed
[OK] Ready for reinstall"Dead ECU" is not
one thing
The recovery path depends entirely on the cause. Four common scenarios — each handled differently.
Failed flash / bricked
Programming interrupted, wrong file, bad connection mid-write. ECU won't boot — no comms, no response. Best recovery candidate.
- JTAG / bench mode access bypasses boot failure
- Original or correct calibration reflashed
- High success rate on supported platforms
No comms — transceiver fault
ECU powers up but the CAN transceiver is failed or damaged. Module is missing from network scan — not necessarily dead internally.
- Bench comms check isolates the transceiver
- Flash intact — data recoverable via JTAG
- Component-level repair or reflash depending on damage
Water / corrosion damage
Ingress causes short circuits, corrosion on traces, or component failure. Outcome depends on what corroded and whether data survived.
- Full inspection under magnification
- Board cleaned, damaged traces assessed
- EEPROM read attempted if MCU is intact
Power surge / reverse polarity
Jump-start connected wrong way, voltage spike from alternator failure. Often destroys the MCU or protection diodes — worst prognosis.
- Hardware damage assessed on bench
- Data recovery via EEPROM direct read if chip survived
- May be data-only — no module restoration possible
What bench work
actually involves
Not plugging in a different scanner. The ECU is removed from the vehicle, powered on a controlled bench supply, and accessed directly.
$ jtag --connect
[ERR] No JTAG response — MCU dead
$ eeprom --identify --chip=direct
[OK] 93C86 detected (1KB Microwire)
$ eeprom --read --output=eeprom.bin
[>>] Reading via CH341A...
[OK] Read complete — 1024 bytes
[OK] Checksum intact
$ decode --vin --immo --odometer
[OK] VIN: WVWZZZ3CZJE######
[OK] IMMO data: extracted
[OK] Odometer: 187 432 km
[OK] Coding: extracted
[INFO] Module hardware: unrecoverable
[INFO] Data: available for donor setup
Replacement ECU can be cloned
from this extracted dataset.Two paths forward —
we tell you which applies
After bench diagnosis, one of two outcomes. We communicate this before you commit to repair cost.
Full recovery
The module hardware is intact. The fault is in flash corruption, a transceiver, or boot failure — all accessible via bench. ECU is returned working and ready to reinstall.
- Bricked by failed flash — reflash via JTAG
- Correct calibration sourced or read from backup
- VIN, IMMO, coding preserved from original data
- Comms verified on bench before return
- Backup of final state stored on file
Data recovery only
The module hardware is too damaged to restore. But the EEPROM chip may have survived — and the data inside it is what a replacement ECU needs to be set up correctly.
- Original ECU: unrecoverable hardware
- EEPROM read directly via CH341A
- VIN, IMMO codes, odometer, coding extracted
- Replacement / donor ECU can be cloned from this data
- Sourcing donor ECU is a separate process
Bench access by platform
Bench recovery requires physical access to ECU internals. Tool support varies by platform and ECU family. Send part number for confirmation before shipping.
| Platform | Common ECUs | Bench access method | Year range | Recovery type |
|---|---|---|---|---|
VAG VW · Audi · Skoda · Seat |
Bosch ME7.x · ME17 Siemens PPD · Simos Delphi DCM |
Ktag · PCM Tuner bench JTAG (select platforms) EEPROM direct (CH341A) |
Pre-2022 | Full recovery + data recovery |
BMW E · F series |
Bosch DME MSS/MSV Siemens MSD80/81/85 |
Ktag bench harness EEPROM direct |
Pre-2020 | Full recovery (case-dep.) + data recovery |
Mercedes-Benz W204 · W212 · W221 era |
Bosch EDC16/17 Siemens SIM |
Ktag bench EEPROM direct |
Pre-2019 | Data recovery primary — full recovery case-dep. |
Toyota Corolla · Hilux · RAV4 |
Denso — petrol & diesel | PCM Tuner bench EEPROM direct (CH341A) |
Pre-2022 | Full recovery + data recovery |
Ford Focus · Ranger · Transit |
Bosch · Siemens EEC-V / EEC-VI era |
PCM Tuner / Ktag bench EEPROM direct |
Pre-2019 | Data recovery primary |
Mail-in ECU recovery
Courier the module from anywhere in South Africa. WhatsApp us before removing anything.
✓ ECU part number: from module label
(not just make/model)
✓ VIN: 17-digit chassis number
✓ Vehicle: Make / Model / Year
✓ Fault: What happened — failed flash,
no comms, water, surge, etc.
✓ Previous work: Any programming attempted,
who did it, what tool
✓ Photo: ECU label clearly visible
We confirm coverage, then quote.
Do not ship before we confirm.Send the part number before you ship anything.
We confirm the platform is supported and quote the diagnosis step first. You don't pay for a recovery attempt that doesn't apply to your hardware.