Scope: professional workshop preparation and validation. Always follow the vehicle and tool manufacturer’s instructions and the law that applies to the vehicle.
01
Start with the vehicle and the control unit
Record the make, model, generation, model year, engine, gearbox and market. Add the VIN only through the private portal, never in a public comment. Identify the ECU or TCU manufacturer, family, part number, hardware number and software number exactly as reported by the tool or label. Similar vehicles can use different control units and software branches, so a commercial vehicle description alone is not enough.
02
Preserve a trustworthy original
Submit the untouched original read whenever the tool supports it. Do not rename a modified file as original. Note the tool, protocol and mode used, whether the read was OBD, bench or boot, and whether the file is a full read, virtual read or calibration area. Keep your own local backup before writing anything. If the vehicle has already been modified, say so clearly and provide the best known stock reference.
03
Diagnose before requesting power
Scan every relevant module and resolve active faults that can invalidate the result. Check fuel pressure, boost control, air metering, temperatures, ignition quality, exhaust condition, battery voltage and communication stability as appropriate to the vehicle. A calibration cannot repair a failing sensor, leaking charge system, weak clutch or damaged turbocharger. Include current fault codes and the work already completed.
04
Describe hardware and intended use
List non-standard intake, exhaust, turbocharger, injectors, fuel system, intercooler, gearbox or engine components. Explain whether the vehicle is a daily road car, towing vehicle, competition application, agricultural machine or another lawful use. State fuel grade, altitude or climate constraints where they matter. A precise use case supports a more appropriate request than asking only for the highest possible number.
05
Validate and report with evidence
After writing, clear only the codes that were legitimately addressed, perform the correct adaptation procedure and test the vehicle under controlled conditions. Report logs, measured values, symptoms and exact operating conditions rather than “it does not work”. Keep the portal ticket for every revision so the relationship between original, modified file and feedback remains auditable.