A Stage 1 file is a calibration for a mechanically standard or clearly declared vehicle. It is not a universal percentage and it is not permission to ignore the condition of the engine, turbo, fuel system, cooling, clutch or transmission.
What defines the Stage 1 brief
BLAG starts with the original ECU software and exact HW/SW identification. The workshop supplies vehicle, engine, fuel, transmission, read method, current DTCs, known hardware and the result required. Torque delivery should suit the application: a loaded van, a tractor and a performance car do not need the same strategy.
The supplied read is checked as the technical starting point for that job.
Existing faults, fuel quality, maintenance and hardware must be known before development.
Driver request, torque model, air, fuel, pressure, limits and monitoring are considered as related systems.
The workshop confirms diagnostics, behaviour, logs and safe operation after writing.
Information the workshop must send
- Make, model, year, engine and original output.
- ECU type, HW, SW and original file.
- OBD, bench, boot or virtual read method and tool.
- Fuel grade, transmission and any hardware changes.
- Existing DTCs and mechanical/diagnostic status.
- Application and realistic objective.
What Stage 1 does not guarantee
Database figures are indicative, not a promise for every software version, vehicle, fuel, dyno or environment. A Stage 1 file cannot repair a boost leak, failing injector, inaccurate sensor, worn clutch or cooling problem. Final figures exist only when measured using an identified method.
Cars, vans and working machinery
The same service name can cover very different operating needs. For agricultural machinery see agricultural ECU tuning; for commercial operation see truck and fleet calibration. Use the configurator to qualify a reference before submitting the original.
A controlled validation sequence
After writing, begin with a complete scan and low-load checks. Confirm that requested and actual values behave plausibly before increasing load. Record the gear, RPM, fuel, temperature and conditions used for every log. If knock, smoke, pressure deviation, excessive temperature, clutch slip or a new fault appears, stop the test and diagnose it instead of repeating full-load runs. The delivered scope is validated against the agreed objective, not against an unrelated internet claim or a file from another software version.
Prepare and validate the job
Submit the exact original file
Open one portal job with ECU identification, HW/SW, read method, hardware, diagnostic context and the required result.