MG AUTOTECH
Request

Performance request route

Stage 2 ECU file requests built around the actual hardware setup.

Stage 2 should not be treated as a generic step above Stage 1. The request needs a clear hardware inventory, exact ECU identity, original-file context and a realistic technical target before compatibility can be reviewed.

Create file requestCompare all services

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

When this route fits

Start with evidence, not assumptions.

The vehicle has documented hardware changes that are relevant to calibration.
The workshop can provide an untouched original ECU read and the explicit read method.
Fuel, engine setup, installed parts and intended use can be described before review.
Transmission torque context is available when ECU and TCU behavior must be coordinated.

Required request context

What the workshop should prepare.

  1. 1Vehicle brand, model, generation, engine and model year
  2. 2ECU supplier, family and HW/SW identifiers when available
  3. 3Untouched original ECU file and explicit OBD, bench, boot or virtual-read context
  4. 4Complete hardware-change list, including relevant intake, exhaust and turbo changes
  5. 5Fuel type, available logs, current fault codes and workshop observations
  6. 6Requested result and any gearbox or torque-limit constraints

Technical review gates

Three checks keep the request precise.

01

Identity before calibration

Vehicle, ECU, software and read coverage must agree before the request can move forward.

02

Hardware-to-file fit

The submitted hardware description is reviewed against the requested service scope instead of assuming a universal Stage 2 setup.

03

Drivetrain context

Gearbox type and known torque constraints stay attached to the request when they affect the target.

Secure workflow

From workshop brief to tracked request.

  1. Step 1

    Document the setup

    Prepare the vehicle, ECU, hardware, fuel, read method and target as one technical brief.

  2. Step 2

    Submit the original

    Open the request inside the secure portal and attach the untouched source file.

  3. Step 3

    Compatibility review

    MG AutoTech reviews identity, file context and the requested scope before work continues.

  4. Step 4

    Track the request

    Questions, status, delivered versions and revisions remain connected to the private order.

Questions before submission

Service-specific answers.

Is Stage 2 automatically available for every vehicle?

No. Availability depends on the exact ECU, software, original-file quality, installed hardware, read method and technical target. The route remains review-first.

Why is a hardware list required?

Stage 2 context depends on what is physically installed. A clear hardware list prevents a request from being reviewed as a generic Stage 1 job.

Should I include logs and fault codes?

Include them when available. Logs, active faults and workshop observations can reveal missing context before a file is prepared or written.

Can ECU and TCU requests be coordinated?

Yes, but the ECU and TCU should keep separate original files and controller identities. Mention the gearbox and torque context in the request.

Published by MG AutoTech

Related workshop routes

Updated . Public guidance only; secure handling remains account-based.

About MG AutoTech
Stage 1 ECU file serviceStage 3 custom calibrationTCU tuning file serviceRequest brief builderECU read-method advisorComplete service catalog