Individual ECU calibration based on the original software, vehicle condition and stock configuration.
On this page4 topics ⌄
ECU / PERFORMANCEPower. Torque. A smooth profile.
SCHEMATIC
PowerRelative profile
Engine speed→
TorqueRelative profile
Engine speed→
StockCalibrated
Schematic illustration without measured data. Actual power and torque depend on the vehicle, hardware and calibration.
01
What Stage 1 means
Stage 1 usually refers to software calibration for stock hardware. It is not a uniform technical standard. ECU version, fuel and vehicle condition define the suitable scope. Fixed power gains or durability guarantees cannot be derived from the stage name.
02
The order process
Register in the portal, obtain the required credits and upload the original file with ECU identification, tool and vehicle configuration. Confirm any Slave-to-Master binding first. Download the developed file, write it using the correct protocol and check diagnosis and relevant measurements.
03
Options and pricing
The Stage 1 base price is €100.00 / 1 Credit, including VMax Off. Additional options are charged separately. Prices are net plus statutory VAT; the portal order confirmation applies.
Development measurements do not prove the result at every customer vehicle. Save the original data and document the written version. The existing service includes free revisions; supply a clear description and relevant logs. Returning to stock does not guarantee undetectable modifications or manufacturer warranty.
On this page5 topics ⌄
01
Choose the exact engine before discussing reference figures
The vehicle database provides a way to compare recorded stock and Stage 1 power and torque for the listed engine variants. Select the correct model generation and engine rather than using a result for a similar badge. The comparison is a starting point for a file enquiry, with the software match still to be established.
Use those reference figures in a customer discussion together with the condition of the vehicle and its intended use. They are not an individual dyno measurement or a guaranteed result. The workshop's supplied identification, original software and assessment determine how the actual request can be reviewed.
Confirm whether the vehicle still has its original component configuration or whether anything relevant has been changed. Customers do not always describe an intake, exhaust, cooling or other component change as a modification. Record the actual setup so the stage label does not hide a different technical requirement.
Include the fuel specification and known software history. A vehicle can have standard hardware while already carrying an altered calibration. If that is the case, retain the current readout and describe what is known before requesting the next file. Do not treat an unfamiliar existing calibration as an identified factory starting point.
03
Prepare the file in the format your tool supports
State the tool model, read method and whether the device uses a Master or Slave workflow. Send the file intended for editing in its supported form and clarify any uncertain container format. A normal read, virtual read and recovery backup are different attachments and should be labelled accordingly.
The method used to obtain the software does not define the development scope. An OBD request can still require detailed vehicle information, and another supported reading method does not automatically make every option available. Check the connection and software details before buying credits for the first job.
Separate the engine file from requested extra functions
Stage 1 concerns the agreed engine calibration. Review any additional function individually and check the current list of included options and separate charges. If transmission work is required, provide the TCU identification and clarify the associated order instead of assuming that it is part of the engine file.
Mapswitch and Pops & Bangs also need a defined request and software-specific feasibility check. Describe the intended operation and discuss the relevant service before adding it to a customer promise. A model listed for Stage 1 reference figures does not establish that all additional functions are supported.
Assess the result against the customer's actual brief
After the supported writing procedure, complete the diagnosis and functional checks appropriate to the job. Record the installed version and any observations about the requested operating behaviour. Where measurements are needed, agree the channels and conditions so the data can answer a useful technical question.
Use the existing portal order for a revision and state which delivered version is installed. Include fuel, hardware and any changes made during the job. This keeps the discussion tied to the same configuration and gives development a clear explanation of what the workshop wants reviewed.
