01
Exact TCU identity
Controller and software identity are reviewed independently from the vehicle badge or gearbox marketing name.
Transmission request route
TCU tuning requests with gearbox identity kept separate and clear.
A gearbox name alone is not enough to identify a TCU file. The controller family, software, original read, vehicle torque context and current transmission behavior should travel together through the request.
When this route fits
Start with evidence, not assumptions.
The workshop has a separate original TCU read or exact controller identification.
The gearbox family, vehicle application and read method can be stated explicitly.
Current shift behavior, hardware changes and known faults can be described clearly.
Engine torque context is available when ECU and TCU requests need coordination.
Required request context
What the workshop should prepare.
- 1Vehicle, engine, gearbox type and model year
- 2TCU supplier, controller family, gearbox code and HW/SW identifiers when available
- 3Original TCU file with explicit OBD, bench, boot or virtual-read context
- 4Current ECU setup and intended engine torque context
- 5Existing shift complaints, clutch or gearbox hardware changes and diagnostic codes
- 6Requested transmission behavior described without mixing it into the ECU file
Technical review gates
Three checks keep the request precise.
02
Separate source files
ECU and TCU reads remain separate artifacts so controller history and delivered versions stay traceable.
03
Torque coordination
Engine and transmission targets are reviewed together when torque monitoring or limit interaction matters.
Secure workflow
From workshop brief to tracked request.
- Step 1
Identify the gearbox
Record the TCU family, gearbox code, software, vehicle and read method.
- Step 2
Submit the TCU source
Create the secure request and attach the correct original transmission-controller file.
- Step 3
Technical review
MG AutoTech reviews the controller, request scope, faults and ECU torque context.
- Step 4
Receive tracked versions
Customer-visible messages, delivery and revisions stay inside the protected order page.
Questions before submission
Service-specific answers.
Can a TCU request be identified from the gearbox name alone?
No. Controller family, software identifiers, gearbox code, vehicle context and the original read may all be needed for reliable review.
Should the ECU file be included in a TCU request?
If coordinated ECU and TCU work is required, mention it and submit each controller through the correct file context. Do not combine two controller reads into one file.
Are DSG, ZF, VGS, DCT and PDK requests all handled the same way?
No. They describe different controller and gearbox families. Each request is checked against its own hardware, software and read-method context.
Does this public page upload or inspect a TCU file?
No. It prepares the request. File submission and private technical handling start only inside the authenticated customer portal.
Published by MG AutoTech
Related workshop routes
Updated 2026-07-31. Public guidance only; secure handling remains account-based.