What to expect from Stage 1 on a car: turbo petrol, diesel and naturally aspirated engines
What to expect from a Stage 1 calibration on a car: where the difference comes from on turbo petrol, diesel and naturally aspirated engines, why working with your own file matters, and the EcuPrime workflow. No promised figures; with notes on the read, the backup and the checksum.
The most common question about Stage 1 is "how much will it gain?". The honest answer depends on the type of engine and cannot be given as one figure. This article describes in general terms what can be expected from Stage 1 on turbo petrol, diesel and naturally aspirated engines, explains why working with your own file matters, and shows how the job runs in EcuPrime. EcuPrime is ECU modification and chiptuning software: you upload the file you read yourself, the software identifies the ECU from the file and opens only the operations that can be applied to that file. The overview for this vehicle type is on the car ECU tuning page.
What Stage 1 is and is not
Stage 1 is a software calibration with no hardware changes: the engine's power and torque maps are reworked within the limits of the existing parts. Calibrations that require a different exhaust, intercooler or turbocharger fall outside this heading. Factory software is written with margin for different fuel qualities, climates and several power ratings of the same engine; Stage 1 uses part of that margin. The scope is described on the Stage 1 page. For engine types that have a match in the catalogue, typical ranges are shown on the vehicle type page; they are typical values, not a commitment.
Turbo petrol engines
On a turbo petrol engine the software manages boost pressure, ignition advance, fuelling and torque limiters. Because the amount of air can be changed in software, the difference is usually clear and is felt most in the mid-range, during in-gear acceleration. The result depends on fuel quality and on the condition of the engine: worn spark plugs, leaking hoses or a tired fuel pump reduce what the calibration can deliver and can even cause trouble. The car has to be healthy before it is tuned.
Diesel engines
On a diesel the software sets injection quantity and timing, rail pressure, boost pressure and torque limits. The expectation is usually low and mid-range torque: the car pulls more easily when loaded, on hills and when overtaking. The limit here is often set by the driveline rather than the engine; the torque the clutch and gearbox can carry must not be exceeded. The effect on consumption depends on driving style.
Operations on emission systems are also asked about on diesel cars. The software offers them as separate operations: DPF Off and EGR Off. The pre-analysis shows which of them open for your file.
Operations on emission systems are offered only for use permitted by local law (e.g. off-road / motorsport / export); responsibility lies with the user.
Naturally aspirated engines
A naturally aspirated engine has no turbocharger; the amount of air entering the engine cannot be raised in software. The room the software has to work with is narrow: ignition, mixture, throttle response, rev limit. So the change is limited and is usually felt in throttle response rather than in power. Expecting a turbo-style difference from a naturally aspirated engine leads to disappointment; set your expectations accordingly.
Why working with your own file matters
The same make, model and engine can leave the factory with different software versions, and dealer updates change the version later on. A change prepared for one software version may not sit at the same addresses in another. That is why the software works with the file read from your car: it identifies the ECU and the software version from the file, matches the solution to that file and applies the change to your file. The parts of the file that are not changed stay as they are in your car.
The workflow
Read: you read the ECU with your own tool and save the file; the software does not connect to the car and does not write to it. Which file to upload is explained on the ECU file page.
Upload: you upload the file in the browser and the ECU is identified from the file itself. You can check beforehand whether the family is in the catalogue on the ECU list.
Pre-analysis: you see, free of charge, which operations can be applied to your file.
Choose and collect the output: the solution is applied at byte level, with the match against your file checked. If one of the operations you chose cannot be applied, no file is delivered and the credit is refunded.
What to watch for
The file you upload should be the original, unmodified file read from the ECU; on a car that was tuned before, the software may not find a correct match. Keep a copy of the original file somewhere separate: it is the way back to stock. The checksum is not corrected automatically in the delivered file; open the Checksum tab in the software before you write. On some modern, signed ECU families the software does not perform the correction and you need your own tool or an external one; the software shows a warning for the families it recognises. Details are on the checksum correction page. You write the file to the car with your own tool.