DSG files and TCU tuning matched to your engine setup.
We develop transmission software for supported DSG and automatic software versions. Each order is based on the gearbox, TCU identification and engine configuration, with shift behaviour and torque management considered together.
On this page5 topics ⌄
ECUEngine control
TCUTransmission control
Schematic illustration
01
Identify the TCU before choosing a file
Send the gearbox type and full TCU identification. A family name such as DQ250, DQ381 or DQ500 alone is not enough to approve a file. Other automatic transmissions also require the exact identification and software version. We check the specific software before accepting the work.
02
Agree on the transmission changes
Describe the shift behaviour you want and the installed engine software. Relevant torque limits and shift strategies can be adjusted where the software supports the requested work. The agreed scope follows the vehicle configuration. TCU software is not a repair for mechanical wear or existing transmission faults.
03
Order a DSG file
The current TCU Tuning base price is €80.00 net / 0.8 Credits. Launch Control is listed as a separate option. Include any additional requests in the order. Read using the appropriate TCU protocol and upload the file with the gearbox and vehicle details.
Specify the installed engine software and hardware changes. For a Stage 2 project, reference the related engine and transmission orders. This allows the requested TCU work to be assessed alongside the torque model.
Keep the original data and identification. Follow the tool and vehicle instructions for writing and any subsequent procedures. For questions, record the version, observed shift behaviour and relevant measurement data.
Engine and transmission software are separate services. If both are required, include the relevant identifications and files in the order.
Are all DQ250, DQ381 and DQ500 versions supported?+
The gearbox family alone does not confirm support. TCU hardware, software version and tool protocol are checked for the specific order.
On this page3 topics ⌄
01
Use the full TCU identification in the brief
A request headed DQ250, DQ381 or DQ500 identifies a transmission family, but it does not establish every detail needed for the file order. Include the tool identification, software information and the original TCU data available through the supported protocol. State whether the transmission is standard or whether relevant mechanical work has been carried out. Development can then discuss the actual version rather than a family name in isolation.
Keep the engine configuration in the same technical brief. If the ECU file is being changed as part of the project, identify its current or planned version. If the engine calibration came from elsewhere, declare that history so the transmission request is not assessed against an assumed stock configuration.
Describe the shift behaviour the customer is asking for
Explain the operating condition that matters to the customer: for example, a particular shift pattern or the relationship between engine response and transmission behaviour. Avoid making the stage name the entire specification. The requested behaviour, controller software and vehicle condition together define the technical discussion.
Do not interpret a changed software threshold as an increase in the mechanical capacity of the gearbox. The workshop still needs to assess condition and any relevant hardware limitations. If an existing concern is present before tuning, record it clearly and distinguish that diagnostic issue from the requested calibration work.
Record which ECU and TCU versions are installed when collecting feedback. If one file changes while the other remains the same, state that in the order so the next discussion refers to the correct combination. Follow the tool procedure and the relevant workshop checks for the actual controller; do not borrow a procedure simply because another gearbox has a similar family name.
For a revision, describe the reproducible condition and supply the agreed raw data. A general statement that the gearbox feels different does not identify the shift, load condition or mode being discussed. A defined record gives development a practical question to assess and keeps subsequent changes traceable.
