Editing ECU Maps in the Browser: What the AI File Editor Does, and What It Refuses to Do

Most portals stop at “upload, wait, download”. The AI File Editor is the part where the tuner actually works: the maps are read out of the binary, laid out as editable grids, and every change becomes a revision the customer can be handed.

What it reads before you touch anything

Drop a read into a job and the analyser goes at the bytes, not the filename. It reports the ECU manufacturer and family, the Bosch part number, the software and hardware numbers, the VIN if the read carries one, and the byte order. The last of those sounds like trivia and is not: get endianness wrong and every value in every map is nonsense, so the editor states what it detected rather than guessing silently.

Filenames lie constantly. A file called golf_stage1_final_v3.bin tells you what somebody hoped, not what the ECU is. Reading identity from the bytes is the difference between “probably an EDC17” and “EDC17C64, SW 03L906012AB, little-endian”.

The maps, as grids

Identified maps are grouped by what they do — Boost & Airflow, injection, torque limiters, DTC handling — and each opens as a normal two-axis grid with its axes labelled in real units. You select cells the way you would in a spreadsheet: click, drag, shift-click a block.

Then you change them, two ways:

• Add or subtract a value on every selected cell — an absolute offset.
• Add a percentage — type 10 for +10% across the selection.

The panel shows the arithmetic mean of the selection and the average change you have applied, so you can see the shape of what you did without reading every cell back.

Auto-sync similar maps

Real calibrations rarely hold one copy of anything. A boost limiter often exists three or four times over for different conditions, and a change to one that misses its siblings produces a car that behaves differently depending on which table the ECU happens to consult.

Auto-sync finds the maps that match the one you are editing and offers to apply the same change across them. It is the difference between a tune that works on the dyno and a tune that works on the road in fourth gear at 1,300 rpm.

When the detection is wrong

Sometimes an axis is misread or a map is typed incorrectly. You can override the interpretation and re-read the map with your correction, and the override is saved per map — so the next file with the same signature reads correctly the first time. The editor gets better at your ECUs as you use it, without anybody shipping an update.

Apply → Revision

This is the button that makes the editor part of a business rather than a toy. When you are done, Apply → Revision writes the modified binary as a new revision on the job.

That means:

1. The original read is never overwritten. It stays as revision zero, forever.
2. The customer gets a download that is versioned — v1, v2, v3 — not “final_final.bin” over email.
3. If a revision is wrong, the previous one is still there and still deliverable.
4. The whole chain is on the job, so six months later you can see what was changed and when.

If the file arrived vendor-locked, the delivery is re-encrypted on the way out. Plain bench and boot reads go in plain and come back plain, with no vendor call in the middle.

The assistant, and what it is for

The AI Tuning Assistant sits beside the grids and answers questions about the file in front of it — what a map controls, what a sensible range looks like, what a given change is likely to affect. It has the analysis as context, so “what is this map” is answerable rather than generic.

It does not press the button. It does not apply changes, and it is not a substitute for knowing what you are doing to somebody’s engine. It is there to shorten the reading, not to replace the tuner.

A worked example

A dealer sends an EDC17C64 read and asks for Stage 1 plus a DPF delete.

1. The analyser returns EDC17C64, the Bosch part number, SW and HW, byte order confirmed.
2. The file matches work already done on the network, so the previous modification list is on screen before any editing starts.
3. The tuner opens the boost limiter, selects the mid-load region, applies +8%, and the panel reports the average change across the selection.
4. Auto-sync flags three sibling limiters. All four move together.
5. Injection quantity gets an absolute offset in the same way.
6. DTC handling is adjusted for the delete.
7. Apply → Revision writes v1. The customer’s download appears, re-encrypted if the read was locked.

The original read is untouched. Every value that moved is recorded. If the dealer comes back in a fortnight asking for a little more, the starting point is exactly where it was left.

Frequently asked

Do I need WinOLS to use this?

No. The editor reads the maps out of the binary and lays them out in the browser. Plenty of shops still keep a desktop tool for deep work, and the two are not exclusive — but a Stage 1 with a delete does not need one.

What happens to the original file?

It stays as the base revision and is never overwritten. Every edit produces a new revision alongside it.

Can it identify any ECU?

It identifies what it can prove from the bytes and says so plainly when it cannot. A clear “no confident match” is worth more than a confident wrong answer — the tuner then fills in what the file could not tell it.

Does the AI change my file?

No. It answers questions about the maps you are looking at. Every change is one you make and apply yourself.

What if a map is read incorrectly?

Override the interpretation and re-read it. The override is stored per map, so the correction sticks for future files with the same signature.