ECU coverage

Last updated 12 October 2026

A listed ECU family is not the same thing as your exact software. A solution is applied only when it matches that file. If it does not match, the desk says so and the job is not counted.

What supported means

The coverage list names families and modules, such as a Bosch EDC17 variant. Inside one family there are many software numbers, hardware revisions, and earlier modifications. The desk looks at the file you upload. It does not assume the badge on the car is enough. Not every vehicle, ECU, TCU, hardware revision, or software number can be done. Not every function is available on every unit.

A limit can come from the tool maker, the condition of the vehicle, the software already on the unit, how you read it, or an upstream server. OBD, bench, and boot are not interchangeable. A family that is listed can still refuse the file you send.

When a solution is missing

The usual reason is that this software number is not matched yet. The family can still be listed. Nothing is written from a neighbouring version onto your file. That refusal is intentional. On a paid job the credits for that selection come back, because the solution cannot be created. The payment in euros stays. On the free file, and on the weekly file included with a plan, that attempt is not used. Use the coverage pages and the free file to check a vehicle before you pay.

Figures

Power and torque numbers on a coverage page come from tested examples. The same stage on another engine, gearbox, fuel, or software version can land somewhere else. Those numbers are not a promise of power, fuel use, emissions, or durability.

Checksums

Where the file can take a corrected checksum, the result includes it. On units that need a manufacturer signature, the checksum may be absent. Your own flash tool has to finish that correction before the file is written. Writing a file that still needs that step can leave the ECU unable to start.

What you keep

Upload a complete original that was read correctly. The result is only as good as that file. Keep the untouched original of every ECU you work on. Read and write with a method that suits that ECU. A bad read, a bad write, or a fault already in the vehicle is not a defect in the processing. You remain responsible for whether the modification is lawful where the vehicle is used.