Second-Hand ECU:
Why It Won't Just Work.

A customer buys a second-hand ECU from a scrap yard. The part number matches. The physical connector fits. They plug it in, start the car — and it doesn't run, or it runs with the immobiliser warning lit, or it refuses to communicate entirely. The assumption is that the second-hand unit is faulty. Usually, it isn't.

The problem is not the hardware. The problem is that a vehicle control module is not a generic component. It's a configured node in a network that was specifically set up for another vehicle. Before it will work in yours, several things need to happen — and none of them happen automatically.

What the ECU carries from its previous vehicle

A used ECU carries several layers of data from the vehicle it came from. Depending on the platform, this includes:

• VIN coding — On VAG, BMW, and Mercedes platforms, the ECU stores the VIN of the vehicle it was last coded to. On first communication, the gateway compares this against the chassis VIN. A mismatch is logged and in many cases prevents normal operation.
• Immobiliser pairing data — The ECU's EEPROM contains a shared secret with the immobiliser control unit (CAS on BMW, EWS on older BMW, EIS/EZS on Mercedes, IMMO on VAG). Without the matching data, the engine will not start regardless of how perfectly everything else is configured.
• Variant coding — Engine management parameters, gearbox type, options fitted, regional fuel requirements. A unit from a left-hand-drive European vehicle may not be configured for ZA market fuel quality or emissions standards.
• Adaptations — Throttle body learned values, fuel trim corrections, transmission clutch pack adaptations. These are not critical for basic operation, but will affect drivability until reset and relearned.

Platform-by-platform: what's needed

VAG (VW, Audi, Skoda, Seat)

On a VAG platform, a replacement ECU requires component protection removal (on newer MQB/MLB platforms), VIN adaptation, and IMMO login. The IMMO system on VAG links the ECU, the key transponder, and the instrument cluster — all three must be synchronised. On EEPROM-accessible platforms (MED9, MED17, EDC17 variants), the ISN (IMMO synchronisation number) can be extracted from the old ECU's EEPROM and written to the replacement. On locked platforms, the dealer PIN or a calculable online response is required.

BMW (E, F, G series)

BMW uses a CAS (Car Access System) on E-series and a FEM/BDC (Front Electronic Module / Body Domain Controller) on F-series. The CAS or FEM holds the ISN — a unique identifier that the DME (engine ECU) must match to release the starter. A second-hand DME with a different ISN will communicate, pass all diagnostics, and still refuse to start the engine. The ISN must be read from the old DME via EEPROM and written to the replacement, or the ISN must be calculated and written via tool. On F-series, FA (Vehicle Order) coding is also required.

ISTA+ connects to FEM/BDC
✓  FEM communication OK
✓  DME communication OK
✓  DME part number matches

Start attempt
✗  Engine will not start
!  DTC 480C — ISN mismatch (DME vs CAS/FEM)
The module communicates. The IMMO data is wrong.

Fix: read ISN from original DME EEPROM
     write ISN to replacement DME
     recode FA and adaptations

Mercedes-Benz (W204, W212, W221 era)

Mercedes uses the EIS (Electronic Ignition Switch) as the immobiliser hub. The EIS holds the Mercedes-Benz password (MB password) for each key, and the ECU (ME SFI) holds its own matching data. A replacement ECU requires EIS adaptation — either via the dealer online system (SCN coding) or via EEPROM-level work if the EIS is accessible. The ME SFI on W204/W212 platforms stores the EIS learned data in EEPROM; without matching this to the current EIS, the engine will crank but not fire.

What bench work looks like for a second-hand ECU

When a replacement ECU comes to DAC for preparation, the process is:

1. Read the original ECU EEPROM — extract ISN, IMMO data, VIN, and adaptations before it leaves the vehicle.
2. Verify the replacement unit — confirm hardware revision, software version, and that it's not locked or component-protected.
3. Write IMMO/ISN data — transfer the ISN or IMMO synchronisation data from the original to the replacement.
4. VIN adapt and variant code — set the replacement's VIN to match the chassis, configure all variant options for the specific vehicle.
5. Reset adaptations — clear learned values so the engine management can re-adapt to the current engine condition.

This is bench work — it happens before the module goes into the vehicle. You don't fit it and hope. You prepare it, fit it, and it works.

Send the details before you buy

A five-minute WhatsApp conversation before purchasing a second-hand ECU can save you weeks of frustration and the cost of a unit you can't use. Send the VIN, the part numbers of both the original and the replacement, and the platform. DAC will confirm whether it's viable, what the preparation involves, and what it will cost.

The work is nationwide. The module comes to the bench, gets prepared correctly, and goes back ready to fit.