ECU identification: matching a file to the right control unit
Vehicle model and power output are not enough to identify a file. Record the identity of the control unit actually fitted to the vehicle.
From the vehicle to the control unit actually fitted
“Diesel Golf, model year known” describes a vehicle, but does not yet provide an unambiguous basis for editing a file. First record which control unit you have actually identified. Include the displayed ECU family and the available hardware, software and calibration identifiers. Manufacturers use different labels, so retain the complete output instead of deciding which individual numbers to omit.
Diagnostic systems can provide identification data from the connected control unit. The fields available depend on the system. A photograph of the label complements this information but does not replace current electronic identification. For your job, it is important to distinguish information printed on the housing from information read electronically.
An identification record that answers follow-up questions
Create a short record for each readout. The following fields are a practical documentation aid, not a claim that every ECU supplies all these values:
- Job number and an unambiguous link to the vehicle.
- ECU manufacturer, family and displayed part numbers.
- Hardware identifier, software identifier and calibration version where available.
- Date, tool used, its software version and the selected protocol.
- Reading method, associated file name and exported operation log.
Save the complete identification report with the file. A screenshot can also help if an identifier appears differently in the export. Explicitly mark values that are illegible or not provided. A blank labelled “not displayed” is more useful than a number copied from a similar job.
Workshop example: two similar vehicles
Suppose two vans have the same engine and the same stated stock power output. You read vehicle A on Monday and vehicle B on Wednesday. A shared folder called “Stock van” makes confusion easy. Two separate job folders with their own identification reports provide a traceable match, even when the file size and ECU family look identical.
Compare the identifiers before assigning an existing modified file to a new job. Matching visible headline details does not replace checking the specific combination. If you find a discrepancy, record it and clarify the correct starting point. Renaming an identifier in the file name does not resolve that discrepancy.
Information that helps with the handover
For a technical enquiry, the unchanged identification report, the exact reading method and the file concerned are particularly useful together. Also explain whether any work or software measures have been carried out on the vehicle since the readout. Nobody then has to infer the current condition from a file name.
Software and hardware versions explains the identifiers in more detail. Once the match is established, preparing your original file covers the next steps for handing it over to the file service.
Technical sources & further reading
Your file. Your setup.
Upload your file, select the required modifications and pay directly. No account and no credits.