10 min · 2026-09-02 · ChiptuningLab desk
Autotuner, Kess or Magic: pick one tool and send that dump
The desk writes on the file you read. Mixing protocols is how a quiet dash becomes a recovery Monday. Same tool out as in.
Reviewed by the lab desk before it went live. We write files; we do not rubber-stamp brochure numbers.
Workshops ask which tool we prefer. We prefer the one that already talks to that ECU in your bay. Autotuner, Kess, K-TAG, Magic, PCMFlash, a bench pinout — the file is the dump, not the logo on the case. What we cannot use is a 200 kb snippet, a screenshot of a checksum, or a folder of 4.000 bins from a Facebook group.
Read with one tool. Flash with the same tool. A map written on an Autotuner read does not owe a Kess protocol a favour. If the tool spat out two files on the way in, you already told us which one you wrote last. Write the matching one back. Mixing those two is how a quiet dash becomes a week with the ECU on a bench.
OBD is fine when the family allows it. Bench or boot is fine when the family needs it. Do not fight a locked ECU on the ramp at 16:40 and then send us half a read. If you cannot get a full file, say so on the ticket before we start the clock. A restricted Drive link is not a full file either.
Name the dump like a person. Tool name in the ticket helps when two files look identical and only one is the virtual read. BMW_320d_2018_EDC17_Autotuner.bin beats dump2.bin. Keep the virgin copy next to it. Reception will ask for factory software the week the car goes to a dealer.
We do not remote-desktop the laptop in the yard. Checksum is your habit. Stable power, a charged booster, ignition where the instructions say ignition. A dying battery in the middle of a write is not a map problem and it is not a reason to try the other tool ‘just to see’.
Credits leave when you open the request. Circuit and motorsport only. The tool does not homologate the car. Brief the driver. Then put the laptop down.