For workshops & professional tuners

Professional ECU file service for custom tuning files.

Built for workshops and professional tuners: submit the original ECU or TCU file with exact vehicle, controller, fuel and hardware context. MG AutoTech reviews Stage 1, Stage 2, Stage 3 and supported software requests through one secure, vehicle-specific workflow.

Vehicle-specific by design
This public hub does not read or inspect customer files.
File submission starts only inside the authenticated customer request flow.
Private order details remain inside the customer dashboard.
Unclear or complex requests stay review-first before delivery.

Calibration route comparison

Stage 1 vs Stage 2 vs Stage 3 ECU tuning files.

The stage name is only a starting point. Vehicle condition, ECU software, fuel, gearbox limits and installed hardware determine what can be reviewed for the submitted file. No stage promises a universal result.

Stage 1

Stage 1 ECU File Service

Vehicle-specific calibration for a standard or near-standard vehicle after ECU identity, source-file context and operating condition are reviewed.

Typical hardware
Standard or near-standard engine hardware
Calibration scope
Calibrated torque, load and response within the reviewed standard-hardware context
Supporting modifications
Normally not required; every vehicle and existing change must still be declared
Logging
Useful when available and may be requested when condition or behavior needs confirmation
Intended customer
Road and workshop customers seeking a measured first performance step
Review
Vehicle, engine, ECU, fuel, gearbox and original-file review
Ordering
Submit the original ECU file through the secure request portal
Explore Stage 1
Stage 2

Stage 2 ECU File Service

Hardware-aware calibration for a modified vehicle. The exact installed parts, ECU identity and drivetrain context must be documented before review.

Typical hardware
Documented supporting hardware changes
Calibration scope
Custom review aligned with the declared intake, exhaust, cooling, turbo or fuel setup
Supporting modifications
Application-specific; there is no universal Stage 2 parts list
Logging
Commonly useful and may be required to validate the setup or guide revisions
Intended customer
Workshops and owners with a clearly documented modified setup
Review
Exact hardware inventory, ECU/SW identity, fuel and drivetrain constraints
Ordering
Submit the original file and a complete hardware brief for compatibility review
Explore Stage 2
Stage 3

Stage 3 Custom Calibration

Engineering-led calibration request for extensively modified combinations where turbo, fuel, engine and transmission specifications define the work.

Typical hardware
Extensively modified, fully documented powertrain
Calibration scope
Custom calibration plan built around the exact mechanical and control-system combination
Supporting modifications
Turbo, injectors, fuel system, cooling, engine or gearbox changes may be relevant
Logging
Expected as part of technical validation; revisions may be necessary
Intended customer
Professional workshops and advanced projects with complete technical evidence
Review
Mandatory technical review; availability is never assumed from the model name alone
Ordering
Open a request with the full specification for feasibility and scope review
Explore Stage 3
Workflow

From file-service search to dashboard delivery.

The public hub explains the path. The authenticated portal handles the actual request, account ownership, credit verification and delivery status.

01

Prepare the request

Confirm vehicle, engine, ECU or TCU context, read method and the requested service before opening the portal flow.

02

Submit through the portal

Customers create the request from their own account so access, credits, status and delivery stay attached to the order.

03

Technical review

MG AutoTech can review the selected service, notes and file context before the request moves forward.

04

Track and download

Customer-visible messages, status changes and completed file delivery stay inside the private dashboard.

Request requirements

Information that makes an ECU file request usable.

  • Vehicle make, model, generation, engine and model year
  • Transmission and TCU context when torque coordination matters
  • ECU supplier, family, hardware and software identifiers when available
  • Untouched original ECU or TCU file and the explicit read method
  • Fuel type or octane, installed hardware and intended operating context
  • Requested services, exact fault codes, workshop observations and available logs

Quality and traceability

Checks stay attached to the vehicle-specific workflow.

  • Source-file and controller identity are reviewed together instead of trusting a filename alone.
  • Compatibility is considered against the exact ECU software, read method and vehicle setup.
  • Requested calibration scope stays tied to declared hardware, fuel and drivetrain constraints.
  • Delivered versions, customer-visible messages and revision context remain attached to the private order.

Supported-brand guidance

Start with the vehicle, then confirm the exact ECU.

Brand guides provide request context only. Controller and software identification remain necessary for support confirmation.

Browse all brand guides
FAQ

ECU and TCU file service questions.

What is an ECU file service?

An ECU file service is a structured workflow where the customer provides the vehicle context, selected service and original controller file through a secure request process. MG AutoTech keeps the request status and delivery inside the customer portal.

What is a TCU file service?

A TCU file service focuses on transmission-controller requests. The request should include gearbox or controller context, vehicle information, selected service and clear technical notes for review.

What is the difference between Stage 1, Stage 2 and Stage 3?

Stage 1 is generally reviewed for standard or near-standard hardware. Stage 2 is tied to documented supporting modifications. Stage 3 is an advanced custom project requiring a complete build specification, technical review and a credible logging or revision path.

Are ECU tuning files vehicle-specific?

Yes. The request is reviewed against the submitted vehicle, engine, ECU software, original-file context, fuel, gearbox and hardware setup. A stage name alone is not enough.

Can I submit a file read by AutoTuner, KESS, Flex or another tool?

State the tool and the OBD, bench, boot or virtual-read method when submitting. Tool name alone does not prove file coverage or originality, so the controller identity and source context are still reviewed.

What information is needed for a tuning file?

Provide vehicle and engine data, transmission, ECU HW/SW where available, original file, read method, fuel, installed hardware, requested services and relevant fault or log context.

How do I receive and download the tuned ECU file?

Delivered versions appear inside the authenticated order page. The customer can track status, read customer-visible messages and download the completed file from the private portal.

Can a file be revised after testing or data logging?

Where a revision is appropriate, the request and supporting observations or logs remain attached to the same order so the delivered-version history stays traceable.

What happens if the uploaded file is not original?

Do not hide uncertain file history. Mention previous work and use the ECU file-check route when originality, identity or read coverage needs verification before another service is considered.

Do you support petrol and diesel engines?

Supported petrol and diesel applications can be reviewed, but controller families, operating strategies and evidence requirements differ. Exact support is confirmed from the submitted identity and file context.

Do you offer TCU tuning files?

Selected TCU and gearbox-controller requests are supported. Submit a separate original TCU file, exact controller identity and engine torque context where ECU and TCU behavior must be coordinated.

Can workshops and professional tuners use the service?

Yes. The workflow is designed to keep repeat file requests, technical notes, status, customer-visible communication, delivered versions and revisions connected to the correct account and order.

Is this an ECU file-management software product?

MG AutoTech provides a secure customer portal for file submission, order status, request history, messages, revisions and downloads. It is a service workflow, not a standalone ECU editing application.

Does this public page upload, inspect or modify files?

No. The public page explains the service. File submission and private technical handling begin only inside the authenticated customer request flow.

Ready to create a file-service request?

Use the secure customer portal when the vehicle context and service details are ready.

Create account & start request
Checking availability