Turbo petrol
A standard or near-standard setup can be reviewed from the exact ECU software, fuel grade and original read.
Vehicle-specific performance calibration
Stage 1 Tuning File Service for Workshops
A professional Stage 1 file service starts with the exact vehicle, controller software and original ECU read rather than a generic one-file-fits-all calibration.
Credit price
10 credits
Delivery estimate
Confirmed after vehicle, ECU and original-file review
File delivery
Secure portal
Workflow
Tracked status
Stage 1 request fit
Is this a Stage 1 file-service request?
Stage 1 is a vehicle- and software-specific review for standard or near-standard hardware. The original ECU read and exact controller identity matter more than the model badge alone.
Turbo diesel
Engine, gearbox, read method and current diagnostic condition must stay attached to the request.
Naturally aspirated
A file can be checked, but realistic gains are usually more limited than on a supported turbo application.
Modified hardware
Turbo, exhaust, fuel-system or other supporting changes should be declared and may require Stage 2 or custom review.
Stage 1 vehicle brand guidesOpen the brand route before submitting when model, engine or controller context is unclear.ViewClose
Stage 1 ECU platform guidesUse the controller guide to check the identity and read-method details needed with the original file.ViewClose
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
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
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
What this service is for
Stage 1 is generally intended for a standard or near-standard engine setup. The review considers the vehicle condition, engine and ECU identity, source-file history, fuel, gearbox context and any existing hardware changes before suitability is confirmed.
Petrol and diesel engines use different control strategies, operating limits and diagnostic evidence. For that reason, the requested response and torque delivery are considered within the submitted platform instead of being described with universal power figures.
MG AutoTech keeps the complete workflow in the customer portal: submit the untouched original ECU file, record the read method and technical notes, follow customer-visible status, download delivered versions and request a revision when testing or logging provides useful evidence.
Vehicle- and ECU-specific review for standard or near-standard hardware
Torque delivery, response and drivetrain context considered together
Petrol, diesel, fuel-quality and transmission constraints kept visible
Private request history, delivered versions and evidence-led revision support
Professional file workflow
01
Vehicle and ECU details
Brand, model, generation, engine, read method and HW/SW information are collected before file work starts.
02
Original file upload
The customer uploads the original ECU file through the secure portal so the request stays connected to the correct account.
03
File preparation
The source-file context, ECU identity, vehicle condition, fuel and drivetrain constraints are reviewed before suitability is confirmed.
04
Delivery and revision
The completed modified file is delivered in the order detail view. If needed, the customer can request a revision.
Supported vehicle focus
BMW
Mercedes-Benz
Audi
Volkswagen
Porsche
Opel
Renault
Peugeot
Information needed
Original ECU file
Vehicle make, model, engine, model year and transmission
ECU supplier, type and HW/SW identifiers where available
Read method such as OBD, bench, boot or virtual read
Fuel type or octane and every existing hardware modification
Current fault codes, workshop observations and logs when available
Ready to submit?
Create an account, buy credits and submit the original file with vehicle details. The request can then be tracked from the customer dashboard.
Start Secure RequestFAQ
Common questions
What is a Stage 1 tuning file service?
It is an online workshop workflow for preparing a vehicle-specific ECU calibration from the submitted original read, exact controller identity, fuel, drivetrain and vehicle context. It is not a universal file selected only by model name.
What file do I need for a Stage 1 request?
Submit the untouched original ECU read and identify whether it was read by OBD, bench, boot or a supported virtual-read method. Include ECU HW/SW data where available so file coverage can be reviewed.
Is Stage 1 suitable for every vehicle?
No. Suitability depends on ECU type, file quality, vehicle condition and hardware setup. A file check may be needed for unclear requests.
What is the difference between Stage 1 and Stage 2?
Stage 1 is generally reviewed for standard or near-standard hardware. Stage 2 depends on documented supporting modifications and may require additional logs or drivetrain context.
Can both petrol and diesel vehicles use this request route?
Supported petrol and diesel applications can be reviewed, but they do not share one generic calibration strategy. Exact ECU software, fuel, engine and vehicle condition remain decisive.
Why do transmission torque limits matter?
Engine torque delivery and gearbox protection strategies can interact. Include the gearbox type and any TCU work so the request is reviewed with the correct drivetrain context.
Can a file read by AutoTuner, KESS, Flex or another tool be submitted?
Use the secure request flow and state the tool and OBD, bench, boot or virtual-read method. Tool name alone does not prove read coverage or originality, so the file context is still reviewed.
Is a Stage 1 tuning file generic?
No. Vehicle model, ECU family, HW/SW identifiers, original-file history, fuel, gearbox and installed hardware can change the correct review context. Similar vehicle descriptions do not make files interchangeable.
Do I need logs for a Stage 1 file request?
Not every standard request needs a log before review, but current fault codes and useful workshop observations should be supplied. Logs are important when measured behaviour or a revision needs evidence.
Live status
Checking availability