What to check on the car before you order a remap file

The fastest way to blame a file is to skip the bay checks. Extra torque on a dual-mass that already rattled will rattle louder. That is not a map fault. That is a part finishing a conversation it started last winter. Write the mileage. If the clutch smells, say so before the customer drives away grinning and comes back angry.

Boost leaks hide under Stage 1 complaints. A pipe that whistles at 1.2 bar will scream when the map asks for more. Soap, a gauge, five minutes. Same with a tired MAF story and an intake hose that looks original because nobody looked. We can write a careful file. We cannot invent a pipe.

On diesels, look at the filter the ECU still thinks is there. A DPF already on the edge of regeneration hell does not get kinder with more soot. If the car is a track or off-road build and the can is coming out, that is a different ticket — DPF-off as a motorsport option, not a street trick, and not something you hide inside a Stage 1 note.

Battery and stable power belong in the same paragraph as the flash, but they start before you read. A weak battery gives you a short dump, a tool timeout, or a write that dies at 94 percent. Then everyone argues about checksums. Charge it. Use a booster that stays up. Then read.

Scan first. Live data if you have it. Codes that already live on the dash are not the remap will clear those. An EGR flow code on a valve that sticks is a workshop job, not a sentence in the file notes. If you still want the file, put the scan on the ticket. We would rather see P0401 before we write than after the customer is in reception.

Petrol turbo: knock under load on 95 pump is a fuel and heat conversation, not a dare. Say 98 if that is what will be in the tank. Gearbox: a DSG that already flares in second will not grow a spine because the engine map is braver. Attach the TCU read if you want both. Circuit and motorsport only.