ECO tuning files for the actual operating profile.
Calibration focused on driveability and efficient use, without a fixed fuel-saving promise.
On this page4 topics ⌄
01
Define the operating profile
Mileage, payload, route and driving style affect fuel consumption. Provide the original file, ECU identification and a description of actual use. Passenger cars, vans, commercial vehicles and agricultural applications need individual assessment.
02
Measure the result
Compare sufficiently similar routes and operating conditions before and after a change. A single trip-computer value is not proof of savings. ECO tuning does not imply a fixed percentage or guaranteed payback period.
03
Assess economics transparently
A hypothetical calculation: 40,000 km per year at 7 l/100 km, an assumed €1.75 per litre and hypothetical savings of 10% would equal €490 per year before costs. This is not evidence that the saving is achievable.
ECO tuning starts at €90.00 / 0.9 Credits, net plus statutory VAT. Confirm additional options in the portal, upload the original file and configuration, then write the developed calibration using the correct protocol and check diagnosis and relevant measurements.
Identify the operating problem before selecting ECO software
An ECO enquiry should describe how the vehicle is used and what the operator wants to improve. A delivery van, a passenger car and a machine working under sustained load present different questions. Explain the normal workload and the behaviour the customer would like the workshop to review.
It is useful to distinguish an efficiency objective from a request for a different pedal response or torque delivery. Those aims can overlap in the customer's description, but they are not the same measurement. A clear brief helps development discuss the calibration request without turning an expectation of better driveability into an unsupported saving claim.
02
Build a meaningful before-and-after record
Choose a recording method that suits the operation and keep its basis consistent. Record distance or working time, fuel quantities and the circumstances of use. Note changes in payload, route, equipment, weather or operating practice where they affect the comparison. Retaining the underlying records is more useful than an isolated display photograph.
Agree how the workshop will interpret the record before drawing a conclusion. If the vehicle performs a different task after the software change, the comparison may answer a different question from the one originally planned. Explain those limitations in the customer discussion instead of attributing every observed difference to the calibration.
03
Check maintenance and configuration alongside the request
Document relevant diagnostic findings and known mechanical concerns before asking for ECO calibration. Software development should not conceal an unresolved operating issue. Supply the original data, ECU identification and the actual hardware specification so that the request is assessed against the current vehicle rather than a generic model description.
Include the transmission and any operating modes that matter to the brief. If the customer changes fuel or working practice during the project, update the order. A different configuration can alter the basis on which the previous observations and requested software work were discussed.
Use reference power figures for context, not fuel evidence
The vehicle database lists recorded stock and Stage 1 power and torque figures. Those values help identify an engine variant and frame a separate performance enquiry. They do not measure an ECO result or establish the fuel consumption of a customer's vehicle under its actual workload.
Keep the requested service clear when placing the order. If the project combines an operating-profile objective with another software function, describe both and ask for the scope to be confirmed. The central price list provides the current ECO base service and additional option information, without implying a fixed financial return.
Review the commercial result using the customer's own inputs
For a workshop business case, use the actual file charge and the labour needed for assessment, reading, writing and follow-up. For the operator, use a documented consumption comparison and the costs relevant to that use. Keep any hypothetical assumptions separate from measured results when discussing whether a project meets expectations.
If further development is needed, attach the operating records and identify the written software version in the existing portal order. Explain which condition or behaviour needs attention. This gives a revision request a practical focus while keeping the customer's commercial expectations linked to evidence rather than a headline percentage.
