Begin with the actual transmission
A vehicle model or a broad gearbox family name is a useful starting description, but it does not identify the complete job. Include the transmission designation and the hardware and software information reported by the tool. If you have only an engine read, make clear that a TCU read has not yet been obtained.
Alientech identifies ECU and transmission programming as distinct tool applications, with available operations determined by the selected protocol. Check the current tool coverage and instructions for the transmission being worked on. Brand-level compatibility is not a substitute for that application check.
Explain the engine configuration alongside the gearbox request
Tell us whether the engine software is original or modified, and reference an existing engine submission where relevant. Include the hardware configuration and the planned engine work if the two jobs form one workshop appointment. Keeping the requests connected avoids treating the gearbox as though the rest of the vehicle were unchanged.
Describe what the customer experiences and what they want to change. A request for different shift behaviour should say when it matters: ordinary driving, a particular operating mode or another clearly defined condition. Do not reduce the brief to a broad request for everything to be more aggressive.
Separate observations from requested changes
A gearbox that behaves unexpectedly needs a documented starting condition. Record diagnostic observations, relevant service history and the conditions in which the concern appears. Distinguish an existing issue from a preference about how a healthy vehicle should feel after the work.
File preparation does not establish the mechanical condition of a transmission at a distance. If the workshop has not yet diagnosed an existing fault, say so. That keeps the conversation focused on whether the proposed calibration work is appropriate and what information is still needed.
- Transmission type and the TCU identification report.
- Original transmission read, tool model and supported method.
- Engine software state and a related submission reference if available.
- Requested behaviour, existing concerns and relevant service information.
Price and deliver the correct service
Use the current service catalogue to identify the applicable gearbox service. Do not apply the engine Stage 1 or Stage 2 price to a TCU job without checking its selection. If your requirement does not match a listed service, contact us with the specification before spending credits.
Once the submitted file is completed, the dashboard contains the download and completion notes. Keep engine and transmission deliveries clearly labelled in the workshop record. If feedback is needed, identify which control unit and file version the observation concerns, and refer to both submissions when the behaviour involves the combined setup.
Questions before you upload
Is a TCU file the same as an ECU tuning file?
A TCU file concerns the transmission controller; an engine ECU file concerns the engine controller. They require their own identification and appropriate service selection, even when both are part of one vehicle project.
Can you supply files for every DSG or ZF gearbox?
Support must be confirmed for the exact transmission, control-unit software, tool and requested work. A gearbox family name alone does not establish compatibility.
Can I send an engine file for a gearbox request?
An engine read does not replace the required transmission information or read. Explain which files you have and confirm the input needed for the intended TCU work before ordering.
Keep exploring
Related workshop reading
Published by Fileservice Chiptuning / Xtra-Facilities BV. Reviewed .
Vehicle names identify customer applications. We are an independent file service; vehicle and tool manufacturers do not sponsor or endorse these pages.
Manufacturer reference material
