When you need an original ECU file, the safest match is not “same car, same engine.” It is the correct ECU family plus matching software and hardware identifiers.
Two cars with the same engine code can leave the factory with different ECU hardware, different software revisions and different emissions or transmission calibrations.
Start with the ECU identification
Read the identification with the flashing or diagnostic tool before removing or opening the ECU. Save the result. Typical useful fields include ECU family, Bosch number, software number, hardware number, calibration identifier and sometimes additional OEM identifiers.
SW number: the software identity
The software number identifies the program/calibration version running in the ECU. It is one of the strongest identifiers when searching for an original replacement file.
If the requested original has a different SW number, do not assume it is safe merely because file size and ECU family match.
HW number: the hardware identity
The hardware number identifies the ECU hardware revision. Different hardware revisions may use different processors, memory layouts or internal configurations even within the same family.
When possible, match both SW and HW.
Bosch part numbers and OEM part numbers
Some jobs expose a Bosch number such as 0 281 … plus an OEM manufacturer number. Both can help narrow the search, but neither replaces a proper software identification from the ECU.
A practical matching order
- Confirm ECU family.
- Match the software number.
- Match the hardware number.
- Compare Bosch/OEM part numbers.
- Confirm file size and memory type.
- Check the flashing protocol and checksum handling.
- Keep the ECU’s original read before writing anything.
Why “same engine” is not enough
Manufacturers update software during production. A 2.0 TDI, 2.0d or 1.5 dCi label describes the engine, not the exact ECU software. Transmission type, emissions package, model year and regional configuration can change the calibration.
What if you only have a dead ECU?
Use the label and any previous diagnostic or flashing logs. If communication is still possible on bench or boot, read identification there before writing. For Bosch EDC17 families, see the EDC17 bench and boot setup guide.
Original file does not always restore immobilizer data
A stock flash can restore program and calibration data but may not restore EEPROM, ISN, PIN, coding or immobilizer pairing. Recovery and cloning are separate tasks from finding the correct calibration.
Before you write the replacement
- Keep the old file even if it is corrupted.
- Save identification and tool logs.
- Confirm stable power.
- Verify checksum behaviour for the protocol.
- Do not overwrite unique EEPROM data unless the job specifically requires it.
For more detail on checksum handling, read ECU Checksum Explained.
Bottom line
Match by ECU family + SW + HW first. Treat model, engine and file size as supporting information, not proof of compatibility.
search original ECU files by SW/HW or browse the ECU software-number index.