A file download belongs to a specific portal order. Upload original data and a documented configuration, resolve technical questions, then download the version assigned to that job.
On this page3 topics ⌄
01Original file
02Job details
03Development
04Tuning file
Schematic illustration
01
Prepare the upload
Include ECU or TCU identification, tool, protocol, file format, hardware changes and intended use. Confirm any Slave binding first. Keep unchanged original data separately.
Select the required base service and additional options. Processing time depends on the data, scope and workload. Review the confirmed price in the portal rather than assuming that every request uses the same number of credits.
Associate the delivered version with the correct vehicle and order. Follow the tool instructions for writing and subsequent checks. For a revision, include the version, observed behaviour and relevant measurements.
Make the downloaded file traceable at the workshop
Treat a tuning-files download as the release of a particular version for a particular job. Before the writing appointment, establish which portal order it belongs to and which original data was supplied. If a workshop has several similar vehicles booked in, a model name or customer surname is not enough to distinguish the correct file. Use a clear internal job reference alongside the portal reference.
If you rename files for your workshop system, retain the relationship to the delivered filename. That relationship becomes important when a colleague handles the write or when the development team later asks which version is installed. Keep the downloaded original package unchanged where practical, and distinguish it from copies prepared for the flash tool.
Resolve open questions before moving the file to the tool
Read any technical notes attached to the order rather than treating the presence of a download as the whole handover. Check that the requested service and any agreed options are understood. If the vehicle configuration has changed since upload, tell development before writing a file prepared for the earlier brief. The same applies if you discover previous tuning or a different software identification.
Confirm that the delivered format follows the agreed Master or Slave route. Do not convert an unfamiliar container or substitute another vehicle's file simply to make the upload screen accept it. When the format or procedure is unclear, ask using the existing order reference and the exact tool information.
A revision should remain identifiable as a different delivered version. Avoid overwriting the original download with a renamed replacement that hides which data was previously written. Record the change in the workshop job, including the version removed and the version fitted. This helps development and the workshop discuss a result without confusing measurements taken before and after the change.
If the tool creates communication or writing logs, keep those as tool records. Vehicle measurement logs are a different type of evidence. Upload the relevant material with an explanation of what it shows, instead of assuming that every file labelled log contains the data needed to assess driving behaviour.
A vehicle may return after a dealer software update, controller replacement or a change of hardware. The old download remains part of its history, but that does not establish compatibility with its new state. Obtain the current identification and discuss the required file route again. Keep the previous original and tuned versions separate from the new read so there is a clear sequence of events.
The portal provides an organised place for file exchange, but your workshop still needs its own retention and job-identification routine. Decide who is responsible for storing the source data and recording what was written. This is particularly useful when another technician handles a later appointment or the customer refers to work carried out some time earlier.
Choose the relevant service, check its current credit requirements and upload the unmodified source file with the necessary identification. For a broad overview of the different deliverables, use the tuning-files guide; for a question about the file already in your order, keep the discussion attached to that order.
