Transmission request preparation

TCU File Service: What a Workshop Should Prepare

A practical request-preparation guide for TCU and gearbox file service, including controller identity, transmission context, separate original reads and secure delivery.

A TCU request needs the transmission controller's own identity and original read. The gearbox marketing name or vehicle model is not a reliable substitute for the installed TCU hardware, software and read context.

ECU and TCU work can belong to the same vehicle request, but their files and controller details should remain clearly separated. This prevents the engine and transmission records from being confused during review or delivery.

TCU request essentials

  • Vehicle, engine, gearbox type and production year
  • Transmission controller family or label details
  • TCU hardware and software identifiers when known
  • Original TCU read and the exact read method used
  • Existing shift concerns, hardware changes and intended request context

Keep ECU and TCU context separate

  • Identify each file as ECU or TCU before submission
  • Do not rename files in a way that hides the controller source
  • State whether the request concerns engine, gearbox or both
  • Attach controller-specific notes to the correct file request
  • Keep every delivered version associated with its controller role

Review checkpoints

  • Controller identity matches the submitted transmission read
  • Read coverage is appropriate for the requested review
  • Vehicle torque and hardware context are stated where relevant
  • Previous software work or controller replacement is disclosed
  • The programming method is confirmed by the workshop before writing

Frequently asked questions

Can a TCU request be prepared without a TCU file?

Controller support may be discussed from identification data, but a file-service request normally requires the correct original TCU read for review.

Should an ECU file be uploaded as a TCU file?

No. ECU and TCU files have different roles and must remain clearly identified. Upload each controller file through the appropriate request context.

Does MG AutoTech confirm the workshop write method?

The request can include read and controller context, but the workshop remains responsible for using a suitable tool, stable power supply and a verified programming procedure.