ECU Coverage Policy

Last Updated: 16 August 2026

This page explains, without marketing language, what “supported” means in Softechpro, why a service can show as unavailable for your particular file, and exactly what we do about it. It is written for professionals: you deserve to know where the limits are before you buy, not after.

In one paragraph

An ECU family being covered is not the same as your exact software version being covered. We only apply a solution when it matches your file exactly, byte for byte, at the correct addresses. If your version is not matched, the service shows unavailable and the software tells you so — we do not force a solution from a similar version onto your ECU. That refusal is the product protecting your customer’s vehicle, and it is why we also give you a free trial and a 7-day money-back guarantee: check your own vehicles first, and if it does not fit, you get your money back.

A. What “supported ECU” means

Our supported list names ECU families and modules (for example Bosch EDC17C50, MED17.5, Delphi DCM3.7). Within one family there are hundreds of software versions, hardware revisions and calibration structures, and they differ from each other far more than the family name suggests.

Whether a specific service can run on your file depends on the software number, the hardware revision, the internal file structure, the checksum structure, and any previous modification of that file. Every file is evaluated individually, at the moment you load it. Nothing is assumed from the badge on the car.

B. Why a service can show as unavailable for your file

The most common reason is simple and honest: we do not yet hold your exact software version. The family is covered, your version is not matched. In that case the software says so instead of pretending, and no credit is charged.

What we do next:

  • Your version is logged as a priority to add.
  • If you can supply an original + already-tuned pair of that same version from any source, we add it — usually the same day — and you receive credits for the contribution.
  • Otherwise it goes into the queue and we notify you when it is ready.

C. Incremental activation — safety before schedule

ECU variants and sub-functions are activated incrementally, after internal testing and technical validation. Vehicle safety and ECU stability take precedence over release dates. A family appearing on the supported list does not mean every sub-function is active for every variant on day one, and we will not activate something that has not been validated in order to hit a date.

D. What the software tells you, and what it will not do

  • Available — a solution exists that matches your file exactly. It applies, and you see how many bytes changed.
  • Unavailable / on request — the family is covered but your version is not matched yet. It is not a statement that your ECU is impossible; it is a statement about our database. Request it and we add it.
  • We never cross-apply. A solution built for a different software version is never written onto your file, even when the difference looks small. Applying a power map from a neighbouring version is how engines end up not starting, and we have taken that possibility out of the product.
  • We do not claim your file is modified unless we can name what was modified. Two factory reads from two different cars already differ by hundreds of bytes (VIN, immobiliser data, learned adaptations), so a difference alone proves nothing.

E. Checksums and manufacturer-signed ECUs

On most ECUs the checksum is corrected automatically and the file is ready to write. On manufacturer security-signed units (MD1, MG1, MDG1 and signed MEDC17 families) the checksum and signature cannot be recalculated on our side. We still apply your tune and deliver the file, and the software states clearly that the checksum is not applied.

On those ECUs you must run checksum + signature correction with your own bench/boot tool (KESS3, AutoTuner, Flex, PCMflash, WinOLS) before writing the file. Writing it without that correction will not start the engine and can damage the ECU. The notice is shown to you at delivery, on every file it applies to.

F. Digital product, free trial and refunds

Softechpro is a digital product: nothing is shipped, and access is granted immediately. Because you cannot inspect digital goods the way you inspect a tool, we do two things instead:

  • A free trial before payment — load your own ECU files and see what is available for your actual vehicles.
  • A 7-day money-back guarantee — if it does not fit your workshop, you get your money back. Full detail in our Refund Policy.

Coverage limits described on this page are therefore not a trap: if your vehicles turn out not to be covered the way you needed, that is exactly what the guarantee is for.

G. Your responsibilities as the professional

  • Always keep the original untouched read of every ECU you work on. It is your safety net and ours.
  • Read and write with a tool and method appropriate to the ECU (bench/boot where required).
  • You remain responsible for the legality of any modification in your jurisdiction, including emissions-related changes and road legality. See our Compliance page and Terms.

H. Versions and updates

The software is provided as the version available at the time of purchase. Coverage grows continuously — new solutions are added as files are validated — but we make no commitment to fixed update intervals, and we do not promise a specific ECU by a specific date unless we have already validated it.

Questions about a specific ECU? Write to support@softechpro-solutions.com with the brand, ECU type and software number, or simply load the file — the answer takes seconds and costs nothing.