Stage 1 remap and tuning files
Stage 1 is the calibration for a car that is otherwise standard. No hardware changes, no compromises asked of the owner — just the factory software rewritten to use the headroom the manufacturer left in it, and returned as a checksum-corrected file you flash with your own tool.
- For a vehicle with no hardware modifications
- Applied to your own ECU read, not a generic file
- Checksum-corrected and flash-ready
- About a minute, from €49.95
What a Stage 1 remap changes
A remap — also called chip tuning, a tuning file or a calibration — is a modified copy of the software the control unit runs. Boost pressure targets, injection quantity and timing, torque limiters and the throttle map are all stored as tables inside that software, and a Stage 1 file rewrites them within what the standard hardware can support.
The headroom exists because a factory calibration is not written for maximum output. It has to work on the worst fuel the car might be given, in the hottest and coldest markets it is sold in, with maintenance that may or may not happen, for a warranty period, across every variant sharing the engine. A tune written for one car in known condition does not carry all of those constraints.
Which is also the honest limit of it. Stage 1 does not change what the hardware can flow. It gets more out of what is there, and how much more depends entirely on how much the factory left on the table for that particular engine.
Stage 1, Stage 2 or Stage 3
The distinction is about the car, not about how aggressive the file is. If nothing has been changed on the engine, Stage 1 is the correct file — ordering something higher does not produce more power on standard hardware, it produces a calibration written for parts the car does not have.
- Stage 1 — a calibration for an otherwise standard vehicle
- Stage 2 — for cars with supporting hardware such as an exhaust or intake
- Stage 3 — for heavily modified builds, matched to the parts fitted
- Individual options — deletes, limiter changes and drivability tweaks
How it works at StageGen
You read the car with your own tool and upload the file. We decode it, identify the control unit and match it against the project database, then apply the calibration to your file — the one from your car, not a template for the model.
The result is checksum-corrected before it reaches you. That matters more than it sounds: an ECU verifies its own memory, and a file whose checksum no longer matches its data is refused or throws a fault regardless of how good the calibration is.
- Upload the original read from your control unit
- Pick Stage 1, plus any other options for the same file
- Download the checksum-corrected result and flash it with your own tool
What it does not require
There is no dyno booking, no appointment and no leaving the car anywhere. Processing is automatic and runs around the clock, so a file uploaded at midnight comes back at midnight rather than on Monday.
It does require that you can read and write the control unit yourself, with a tool you already own. This is a file service — we never touch the vehicle.
Options that go with it
Anything else you need can go into the same file rather than into a second flash cycle.
- Pops and bangs crackle map, on petrol cars
- Off-road emissions-equipment changes where the build calls for them
Which control units are covered
The platform covers the control units that make up the bulk of the European parc, petrol and diesel. If your read comes from one of these families there is a high chance we already hold matching projects for it.
- Bosch ME7, MED9, MED17, MEVD17
- Bosch EDC15, EDC16, EDC17 (including C74 and C76)
- Bosch MG1 and MD1 (MG1CS001, MG1CS003, MG1CS011, MG1CS111 and related)
- Siemens/Continental SID, SIMOS, MSD and PCR families
- Delphi DCM, Marelli MJD and IAW, Denso, Temic/ZF transmission units
Reading the file in the first place
Master reads open directly — .bin, .ori, .mpc and the other common formats. A read from a slave tool is encrypted and has to be unlocked first, through the crypt/decrypt service or by linking your device to our master.
- Alientech KESS3 — decode a protected slave read first
- Autotuner — decrypt a slave read first
- MMS Flex — .mmf containers handled the same way
Turnaround, pricing and what happens if it is wrong
€49.95, typically back in under a minute. If your read cannot be matched automatically the job does not simply fail — you can request manual processing and it is handled by hand.
If the file does not work on the car, open a support ticket and we correct it. Where we cannot make it work, the cost goes back to your balance.
Frequently asked questions
Related
- Stage 2 tuning The right file once a downpipe, decat or intake is fitted.
- Pops and bangs Crackle on overrun — commonly ordered in the same file on petrol cars.
- Power Gains What has actually been recorded for specific engines and variants.
- File services Every service on the platform, with what each one changes.