Custom ECU Tuning Files

What ECU tuning files do we provide?

An ECU tuning file on this portal is a modified engine binary produced from the original read you upload. It is an ECU remap file for that vehicle request — not a shared download for “any Bosch EDC17”.

You choose ECU as the file kind, identify the vehicle in the catalog, select the calibration options offered for that request, and attach the original .bin. When the request is Ready, the processed file is on the same job.

There is no public map pack. Without an original read, there is nothing to remap.

Stage 1, Stage 2 and custom calibrations

Stage 1 ECU tuning files are stock-hardware calibrations. That intent has its own page so it does not compete with this remap overview.

Stage 2 ECU tuning files are for vehicles with supporting hardware such as intake, exhaust, or intercooler. Order Stage 2 only when the hardware matches.

Custom calibrations are the other options shown on the request. Labels such as DPF, EGR, or AdBlue appear only if they exist in the catalog for that file. They are not separate landing pages.

Supported ECU manufacturers and families

Coverage is the live catalog on the request: vehicle type, brand, model, generation, engine, and ECU. Type and brand are required. Later fields can be marked unknown if they are not listed.

Names such as Bosch, Continental, Delphi, or Denso appear only as catalog ECU rows when those rows exist. This page does not publish a fake manufacturer matrix. The full catalog rule is on Supported ECU types & families.

Compatible ECU reading and flashing tools

You read the original file and write the modified file with your own tool. If that tool saves a .bin — including tools people often use such as KESS3, FLEX, or Autotuner — that file can be uploaded.

ECUFilePortal does not run those tools, sell them, or certify slave protocols. Tool-level notes live on Supported ECU tuning tools.

How the ECU file service works

For this remap intent the loop is: original ECU BIN → vehicle and calibration on the request → TuningPoints at submit → processed BIN on File History when Ready.

Account creation, statuses, and gearbox jobs are documented on How our ECU file service works. This page stays on the ECU file itself.

File checking and quality process

Who does the work: TMY Tuned. The portal is not an instant generator and does not apply a remap in the browser. A tuner pulls the original BIN from your request, prepares the modified file offline, and uploads a processed version. Status becomes Ready when that file is attached. The uploader on processed files is the admin/tuner account — not an automated pipeline in the app.

What is checked in the portal: the original file is stored on the request with the vehicle fields and selected options, so the job is not an anonymous email attachment. Every processed delivery is kept as its own version on that same request. You download with a time-limited link for files that belong to your account.

What this page does not claim: WinOLS, a slave solution database, automatic checksum patching, or dyno testing are not product features of ECUFilePortal. If the tuner uses those methods, they sit in the calibration workflow — not as a self-serve checkbox here. We will not invent them for ranking.

Pricing and TuningPoints

The public rate is 1 TuningPoint = €10. The cost of a custom ECU file is the sum of the options you select, shown before upload. There is no static “remap pack” price on this page because those numbers live on the catalog options.

Credits are checked when you submit the BIN. Buy TuningPoints in the Shop. Full credit rules: ECU tuning file pricing.

File revisions and technical support

If a later processed file is uploaded, it is stored as the next version on the same request. You keep the earlier deliveries; the list is not overwritten.

Technical questions about a job belong on that request’s chat in File History, or email [email protected] with the request in context.

Frequently asked questions

Is a custom ECU tuning file a generic download?

No. It is a remap of the original ECU BIN you upload for that vehicle request.

Who prepares the modified file?

TMY Tuned. A tuner downloads the original from the request and uploads the processed file. The website does not auto-generate maps.

Do you use WinOLS or checksum automation?

Those are not documented features of this portal. The product records original and processed files, versions, and status. Calibration tools used offline are not a checkbox in ECUFilePortal.

How do I order Stage 1 or Stage 2?

Same ECU upload flow, then select that option if it is listed. Stage 1 and Stage 2 also have their own pages for those searches.

What if my ECU family is not listed?

Select type and brand, then mark later fields unknown. Do not invent a catalog row.