01
Identity before calibration
Vehicle, ECU, software and read coverage must agree before the request can move forward.
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.
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.
- 1Vehicle brand, model, generation, engine and model year
- 2ECU supplier, family and HW/SW identifiers when available
- 3Untouched original ECU file and explicit OBD, bench, boot or virtual-read context
- 4Complete hardware-change list, including relevant intake, exhaust and turbo changes
- 5Fuel type, available logs, current fault codes and workshop observations
- 6Requested result and any gearbox or torque-limit constraints
Technical review gates
Three checks keep the request precise.
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.
- Step 1
Document the setup
Prepare the vehicle, ECU, hardware, fuel, read method and target as one technical brief.
- Step 2
Submit the original
Open the request inside the secure portal and attach the untouched source file.
- Step 3
Compatibility review
MG AutoTech reviews identity, file context and the requested scope before work continues.
- 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 2026-07-31. Public guidance only; secure handling remains account-based.