ECU files contain the software data of an engine control unit. Our file service works from your original data and a defined job, matching the requested calibration to the ECU and vehicle configuration.
On this page4 topics ⌄Original data and vehicle configuration define the calibration brief.
01
Original file, tuning file and backup
An original file is the unchanged starting software. A tuning file contains the requested changes. A full backup may cover additional memory areas. Consult the tool documentation to establish what the read contains and what recovery requires; a virtual read is not automatically a complete backup.
02
Order the file for the actual vehicle
Create a portal account, confirm the Master or Slave connection and upload the unchanged original data. Add ECU identification, tool, hardware changes, fuel and intended use. A matching model badge or power rating does not establish compatibility.
The current Stage 1 base price is €100.00 / 1 Credit, including VMax Off. Modified hardware, TCU work and additional options have separate prices. Euro prices are net plus statutory VAT; the confirmed portal order applies.
Save the original data separately and record the version written. Follow tool instructions, then check diagnosis and suitable measurements at the vehicle. Include the version and useful logs in a revision request.
Select the binary by identification, not by resemblance
Two files can have the same extension or a similar filename and still belong to different software versions. Start with the ECU identification recorded by your tool and keep it connected to the uploaded file. If the vehicle model, engine description or software history is uncertain, explain that uncertainty rather than choosing a file that merely looks familiar.
The original data gives development a reference for the requested changes. It also helps distinguish a new calibration enquiry from a vehicle that has already been modified elsewhere. State which situation applies and retain the original read unchanged. That information is more useful than renaming an unknown file as stock software.
An openly readable binary and a protected Slave container are different handovers. The development route must support the format your device produces and the way the resulting file will be written back. Confirm the tool model and connection before treating a file from another workshop or another device as interchangeable with your own read.
File extensions are useful labels, but they do not establish memory coverage or recovery capability. If the tool exports several files, describe their names and origin and ask which one is required for the editing order. Keep full recovery data separately rather than replacing it with the smaller file prepared for calibration work.
A finished tuning file is intended for the agreed software-writing process. A DAMOS, A2L or MapPack request concerns definition or project information used during development. Finding the controller in a definitions catalogue does not mean that a ready-to-write calibration has been selected. Make the purpose of the enquiry explicit so it reaches the correct service.
For a definition request, send the original BIN or ORI together with the controller and software identification. For a tuning-file request, describe the required calibration and vehicle configuration. The original data is relevant to both, but the deliverable and the work required are different.
After delivery, keep a clear record of the assigned version and the actual vehicle it was written to. If the controller is later replaced, updated or read with another tool, do not assume that the previous tuning file remains the right choice. Report the changed identification and discuss the next order. A clean file history helps prevent an old download from being mistaken for a compatible file simply because the customer or model is familiar.
