A remap is a changed calibration written back to the ECU it was read from. Several trade terms, products and results are commonly taken to say more about that calibration than they do. This page corrects those readings. The read, edit, checksum and write steps themselves are described in how an ECU is remapped, and what the tables control is in ECU remapping.
| Common belief | What the evidence supports |
|---|---|
| "Chipping" means a chip was changed | Historically true; today the word is used for flash rewrites with nothing removed. |
| A bench tune is better than an OBD tune | Bench and OBD are connection modes. They can differ in read completeness, not in calibration quality. |
| Boot mode gives the "real" calibration | Boot mode reaches memory the other paths cannot. The calibration is whatever is then edited. |
| A tuning box is a remap | A box alters a sensor signal and leaves the calibration untouched. |
| A file matched by software number is custom | Only if the edits were chosen and checked for this car's hardware. |
| An automated tool checked the file | The tool applied a rule; a person still has to compare the result with the original. |
| Stage numbers are a specification | They are seller labels with no common definition. |
| A dyno figure, a passing checksum or a cleared code proves the job | Each proves something narrower than the calibration being correct. |
"Chipping" no longer means a chip
Early engine controllers held their lookup tables, calibration and operating strategy in a one-time-programmable PROM or an ultraviolet-erasable EPROM, so a new calibration meant a new or reprogrammed device fitted to the board (MOTOR, 1998). From the early 1990s, flash and EEPROM controllers could be rewritten through the diagnostic connector without removing anything (MOTOR, 1999). The term "chip tuning" survived the change. It is now applied to flash rewrites in which every component stays soldered in place, so the word says nothing about whether a device was replaced or whether any table was examined. The device history is illustrated in how an ECU is remapped.
"Bench" and "OBD" name the cable, not the calibration
Programming-tool makers use OBD, bench and boot as connection modes. Alientech's answer to which is better is that it depends on the vehicle and the operation; the differences it names are speed, whether the unit stays in the car, whether the diagnostic port supports the job, supply stability, completeness of the image and cloning (Alientech FAQ). None of these is a property of the edited tables.
Completeness is a genuine difference, and it matters for backups, not for tune quality. A virtual OBD read can omit regions that a bench or boot read contains, so it is a weaker restore point. The tables that were received and edited are the same tables in either file. Where a mode cannot write the region that was edited, the result is a failed write, not a lower grade of tune.
"Bench" is also ambiguous. It can mean a programming bench, which reads and writes memory and measures nothing, or an engine test bench or chassis dynamometer, which measures a running engine and edits nothing. A price list offering a "bench tune" has not said which of these is being sold.
Boot mode reaches memory, not a better map
Boot mode puts an opened unit into a programming state so memory can be read or recovered when the diagnostic path will not do it. Alientech's connection-methods page also describes it as working "like a true tuner", which is a sales line: opening the case gives access, and the calibration is still only as careful as the work done on the file afterwards. Needing boot mode says something about access and risk to the unit. It says nothing about the maps.
A tuning box is not a remap
A tuning box leaves the calibration as it was and alters a signal on its way into the ECU: usually rail pressure on a common-rail diesel and manifold pressure on a turbocharged petrol engine. A pedal box only rescales accelerator travel. The ECU's protections then operate on a measurement that is no longer true. Unplugging the box restores the wiring; there was never a calibration change to undo. The mechanisms are on tuning boxes and pedal boxes.
Ready-made and "custom" files
Much of the everyday remapping trade supplies a ready-made file rather than a calibration built at the car. Alientech's Slave configuration is the explicit example: the workshop reads the ECU, sends the file to a Master, and writes the encrypted, ready-to-use file that comes back, which the FAQ describes as starting "without handling map modification". Automated-solution software, listed in the editor directory, applies a publisher's solution to a file the workshop has read. In both cases the calibration decisions were made earlier, by whoever built the catalogue or the rule. That is one manufacturer's product line and a category of software, not a count of workshops; no figure for the share of the trade has been published.
"Custom" on an invoice often means only that this car's read was the input. The output is custom when the changes were chosen for this hardware and software. A catalogue edit keyed to a software number uses the car's file as a carrier: the carrier is unique, the edit is not.
A ready-made file can still be correct. The conditions are that it was built for this exact software identifier, the car's hardware is the hardware the file assumes, someone compared it with an original of that software including the limits under the request, a matching car was logged, and the fitting workshop confirms the identifier and holds a restorable backup. Where the workshop cannot open the maps (as with a Slave tool), its share of the check is the part that needs no editor: confirming identifiers on the returned file, confirming the backup, and logging request against delivered boost, fuel, lambda, timing and temperature on the car.
An automated tool is not a check
Map search, definitions, scripts and modules save labour. EVC's own guidance is that map-search results are candidates, and that transferred scripts and map packs must be verified for address, axes, scaling and values on the destination software, because revisions differ (EVC map search; EVC reusing projects). A fixed percentage applied to every recognised object moves objects that should have stayed still, and leaves unrecognised objects at their original values; the unrecognised one may be the limit that actually caps output (the limit that wins). A run that completes without an error means the rule ran. The check is a comparison of the modified file with the original, followed by a log on the vehicle.
Some automated modules are sold to alter emissions equipment or fault reporting, which can be unlawful on a public road. This wiki does not describe those procedures.
The same software number is not always the same car
The software identifier is the right key for selecting a definition or a file, but not the whole key. Neighbouring revisions can share map names and not addresses; see choosing ECU definition files. Under one identifier the car can still differ in ways the number does not record: a later dealer update, a different turbocharger or injectors fitted by a previous owner, a gearbox the torque limit was not set for, or market-specific emissions hardware. Hardware changes have to be reflected in the calibration explicitly; the usual list is in ECU remapping.
Stage numbers are not a specification
Stage 1, 2 and 3 have no definition in the manufacturer or tool documentation this wiki draws on. They are seller labels: one seller's stage 1 is a small change to the driver request, another's is a percentage across every table found. The label does not say which limits moved, what hardware is assumed or whether the file was logged. How the labels are commonly used, and what to ask, is on tuning stages explained.
What a power figure, checksum or code reader proves
- A dyno or road-pull figure records what the car did on that run, in that gear and those temperatures. It does not show which tables changed, whether knock correction was already spending the margin, whether a smoke limit will intervene in thinner air, or whether the clutch will hold. Without a log of request, delivery and protections, the figure has no cause attached.
- Knock control retards timing after knock has begun. It does not restore a boost or torque ceiling the file removed, or correct a table advanced beyond the fuel in the tank (engine knock). A diesel smoke limit is the equivalent protection, and removing it is how smoke is produced (diesel smoke limits).
- A passing checksum means the integrity values for the ranges the tool knows were recalculated. It passes equally for a careful file and a destructive one (EVC checksums).
- A code reader reads and clears stored faults. Reading a fault is not reading a calibration, and clearing one after a write confirms only that the code was cleared.
- Restoring the original file undoes the calibration write if the backup was a real image of the unit. It does not undo adaptations learned on the modified calibration or any mechanical consequence of running it (adaptations and calibration drift). A virtual read that never held the whole memory is not that original.
Sources
- MOTOR, Trouble Shooter, August 1998. PROM replacement as the way to change a calibration; flash rewritten through the diagnostic connector. Trade magazine. Accessed 2026-11-12.
- MOTOR, To Flash or Not to Flash, November 1999. Reprogramming through the diagnostic connector without removing the memory device. Trade magazine. Accessed 2026-11-12.
- STMicroelectronics, M27C512 datasheet. Distributor PDF mirror. UV-window and one-time-programmable versions of one EPROM. Manufacturer datasheet. Accessed 2026-11-12.
- Alientech, KESS3, connection methods and FAQ. OBD, bench and boot as connection modes; virtual read; Master and Slave configurations. Tool-vendor documentation. Accessed 2026-11-12.
- EVC, automatic map search, checksums and reusing projects and scripts. Tool-vendor documentation. Accessed 2026-11-12.
- How an ECU is remapped, ECU remapping, tuning boxes and pedal boxes, tuning software directory. This wiki.