How It Works

Start with the actual vehicle specification and the work the customer wants. Identify the controller using your supported flash tool and retain the identification from that session. Record hardware changes, fuel and known previous software. If the vehicle has an existing diagnostic concern, describe it separately so the requested calibration is not confused with an unresolved workshop investigation.

Choose the service that matches that brief. Stage 1, hardware-based development, transmission software and additional functions have different scopes. A broad tuning-files enquiry is useful at the planning stage; the portal order should be specific enough for development to understand what file and configuration it is being asked to assess.

Send the unmodified source file through the agreed workflow and explain how it was obtained. A normal read, virtual read and backup are not interchangeable descriptions. If the device produces a protected Slave container, confirm the Master connection before assuming it can be processed. Include the tool and protocol information needed to connect the upload with the actual vehicle.

When several files are available, retain their original relationship and ask which export belongs in the editing order. Do not discard recovery data because the smaller file uploads successfully. Keep the source and backup material separately from later tuned versions, using a workshop reference that can be found during a future appointment.

Use the portal order as the reference for technical clarification. If a component changes, another software version is discovered or the customer asks for an additional function, explain that change under the same job. Development can then assess the updated brief rather than continuing from information that no longer describes the vehicle.

Check the current credit service and the confirmed scope before treating an option as included. Mapswitch and DAMOS or MapPack work require their own enquiry context. In particular, a definition used in software development is a different deliverable from a finished calibration intended for writing to the ECU.

Identify the assigned version before moving it to the flash tool. Retain the delivered filename or a clear reference to it, and record which version is actually written. Follow the tool procedure for the selected controller and complete the relevant checks at the vehicle. A file downloaded for an earlier software identification should not be substituted simply because the model name looks familiar.

If another technician performs the write, give them the order reference, file identification and agreed brief. The handover should make the intended work clear without requiring them to reconstruct the previous conversation.

Where feedback is needed, describe the operating condition and the observed behaviour. Provide the installed version and the agreed raw measurements rather than an isolated screenshot with no context. Keep the discussion in the existing order and record the next assigned revision separately. This creates a traceable sequence from the original source through development, writing and any subsequent review.