Information to include
- ECU/TCU identification and original file
- Tool and reading method
- Service objective and hardware configuration
- Information relevant to any custom requirement
BlagTuning / Software
From the original file to technical follow-up
One request should contain the software history that matters. The portal connects the original file, the calibration objective, delivery and technical follow-up.
Prepare the original software and identification
Start with the ECU or TCU identification and the file obtained with the appropriate reading method. Record the tool used and identify any known previous modification. Include the vehicle or machine details needed to understand the application.
For supported virtual-reading workflows, the file origin and reference still matter. The purpose is not to collect information for its own sake: it is to establish which software is being discussed and what configuration the returned revision is intended to support.
Describe the requested software work
Select the relevant service and explain the objective in practical terms. State whether the hardware is standard or modified and provide the component details that affect the request. For a combined ECU/TCU project, keep the two configurations connected.
If the requirement is unusual, ask about feasibility and scope before committing to a customer. A complete initial request can reduce unnecessary clarification and helps distinguish a standard calibration from separately scoped development work.
Keep the delivered revision identifiable
The returned file belongs to a particular request and configuration. Keep the original and delivered revision distinguishable, and follow the appropriate writing procedure for the vehicle and equipment. The workshop should know exactly which version has been installed.
The file portal also provides a place for the technical conversation around that delivery. Use the same request for questions about the file, rather than starting a disconnected enquiry that loses the original software context.
Provide useful feedback for the next step
Describe the behaviour observed, the current configuration and the exact software version. Include relevant information that helps explain the issue or the further improvement requested. Clear feedback makes it easier to discuss the software rather than speculate about which file or setup is in use.
If hardware, fuel or the project objective has changed, make that explicit. A follow-up can then be assessed as a revision within the existing scope or as additional work. This preserves an orderly software history and a more effective relationship between the workshop and technical support.
Your software request
Service scope
- A single place for the software request
- Identifiable originals and returned revisions
- Follow-up linked to the same technical history
Questions about the service
Where do I upload a technical file?
Use the dealer portal, not the public enquiry form. Keep the file associated with the appropriate request.
Can I add information after submitting?
Continue in the same portal conversation so the additional detail remains linked to the software request.
What should I send when requesting a revision?
The installed version, current configuration and a precise description of the result or behaviour you want reviewed.