Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Remapping
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

A remap is a changed calibration written back to the ECU that was read. The trade has several other names for that job, and several products that stop halfway through it. This page is those names and products. The read, the edit and the write are described in how an ECU is remapped. What the tables themselves do is ECU remapping.

Chipping means a chip was fitted

Chipping was the method. A one-time-programmable PROM cannot be rewritten, so a different calibration was a different device fitted in its place. An ultraviolet EPROM can be erased through the window in the package and written again in a programmer, which still means the device comes off the board. MOTOR described the PROM as the carrier of the lookup tables, the calibration and the operating strategies, and described flash as the later part that can be erased and rewritten through the diagnostic connector without being removed. MOTOR, August 1998; MOTOR, November 1999. The device class is illustrated by the ST M27C512, sold both as a windowed UV EPROM and as a one-time-programmable part. STMicroelectronics, M27C512.

The word outlived the method. A current flash write, with every component left soldered where it was, is still sold as chip tuning. The word is not evidence that a socket was opened, and it is not evidence that a table was inspected. It is evidence that the advertisement is using the name of the 1980s and 1990s service.

A bench tune is a better remap than an OBD tune

OBD and bench are cables. The calibration is the numbers in the file after the read. A smoke limit, a torque limit or an ignition table does not become a different object because the ECU was powered on a bench instead of through the diagnostic socket.

Tool makers use the words as connection modes. Alientech defines OBD as a read and write from the diagnostic port, including a virtual read; bench as a connection on the ECU plug without opening the case; and boot as access with the case open. Asked which is better, their FAQ says it depends on the vehicle and the operation. The differences they actually name are speed, whether the unit stays in the car, whether the port can do the job, stability of the supply, completeness of the image, and cloning. Alientech, connection methods; Alientech FAQ.

Completeness is a real difference, and it is not a grade of tune. A virtual OBD read can omit regions a bench or boot read contains. The missing region makes a worse backup. It does not make the tables you did receive a lesser calibration, and possessing the extra region does not make the tables you edit a better one. Two files of different length can carry the same edited limit. The engine follows the limit that was written, not the connector that was used. Where one mode cannot write the region that was edited, the write has not happened. That is a failed transfer.

"Bench" also means an engine test bench or a chassis dynamometer. Those measure a running engine. They do not extract a file. A programming bench does not measure the engine. A dyno does not edit a map. The measurement and the file meet only when a person changes the calibration because of what the engine did. A price list that says "bench tune" has not said which of these three things the customer is buying.

Boot mode is the real calibration

Boot mode puts an opened unit into a programming state so the memory can be read or recovered when the diagnostic path will not do it. Alientech describes that access, including recovery of a damaged unit, and also describes it as working "like a true tuner". The second phrase is a sales line. Opening the case reaches the memory. The calibration is still whatever is, or is not, changed in the file afterwards. A careful fuel table written over the diagnostic socket, and a careless one written in boot mode, are exactly as careful as the work that was done on each file.

Boot mode is the right tool when the other paths are unavailable or the unit no longer answers. Needing it says something about access and about risk. It says nothing about the maps.

A tuning box is a remap

A tuning box leaves the calibration where it is and changes a signal on the way into the ECU. On a common-rail diesel that signal is usually rail pressure. On a turbo petrol it is usually manifold pressure. A pedal box only rescales the accelerator, so the existing request arrives earlier in the pedal travel. The mechanisms, and the protections that then operate on a measurement that is not true, are in tuning boxes and pedal boxes.

Unplugging the box restores the wire. It does not restore a calibration, because the calibration was never the thing that changed. A remap is the opposite arrangement: the sensors stay honest, and the tables change.

The ordinary product is now a ready-made file

The tools sold for everyday remapping are built so that the person at the car need not edit a map.

Alientech's Slave product is the explicit version. The workshop reads the ECU, sends the file to a Master, and writes the file that comes back. The company's FAQ calls this starting "without handling map modification". The product page calls the returned file encrypted and ready to use. A Master, in the same description, is the configuration that does modify files, and that can run a network of Slaves as a way of supplying those files. Alientech, KESS3; Alientech FAQ. This is one manufacturer's product, not a census of every workshop. It is evidence of what the programming-tool trade now sells as the normal way to offer the service: a read, a file from somewhere else, and a write.

Automated-solutions software is the same arrangement without a second person. The editor directory groups programs that apply their publisher's solution to a file the workshop has already read. They do not program the ECU. A one-click module, a mail-order file chosen by software number, and a Slave file ready to write are the same kind of product at the car. The calibration decisions were made earlier, by a person building a catalogue, or by a rule in the tool. The workshop's remaining job is to put the result in.

That is the sense in which off-the-shelf tunes now occupy the ordinary end of the trade. How large the share is will vary by workshop, and this page has no count of businesses. What is visible, because the tool makers publish it, is that the product on offer is a ready file, and that the person fitting it is not expected to handle the maps.

"Custom" on the invoice does not reverse that. A custom job can mean this car's own read was the input. The input is the original file. The output is custom only when the changes were chosen for this hardware and this software. A catalogue file, or a script, keyed by the software number and applied to every car that presents it, uses the car's file as a carrier. The carrier is unique. The edit is not.

An automated tool is useful, and it is not a check

Automation is how a repetitive edit gets done without a person retyping every cell. Map search, a definition, a script that reapplies a known change, and a module that prepares a starting file all save that labour. EVC documents WinOLS scripts and imported map packs as ways to reuse earlier work, and tells the user to verify addresses, axes, scaling and values on the destination software, because revisions differ. Search results are candidates until that check. EVC, map search; EVC, reusing projects. WinOLS.

The tool does what it was built to do. It does not know that this turbo is not the turbo the rule assumes, that the clutch behind a stock car will not hold the torque the module asks for, or that the object it labelled as a fuel map is an axis, a limit or a sensor scaling. A fixed percentage on every recognised object moves the objects the tool recognised, by the amount the rule says, including objects that should have stayed still. An object the tool did not recognise stays at the original value, and that object may be the limit that actually caps the engine. The limit that wins is why a raised request can leave the output unchanged, and why an unexamined limit can be the entire result.

A finished run with no error message means the tool completed its rule and, where a checksum module ran, that the integrity values it knows about were updated. EVC's checksum modules correct supported ranges. A matching checksum does not mean the calibration is appropriate. EVC, checksums. The check is a person comparing the modified file with the original: which objects moved, by how much, and whether anything outside that list moved with them. Then a log on this vehicle, not a screenshot of the button.

Some of the automated modules in that directory are sold to change emissions equipment or fault reporting. That can be unlawful on a public road. This page does not describe those procedures. A module of that kind is also a bad example of the wider point, because the thing to check is not only whether the edit is lawful. It is whether the edit is the edit the file appears to contain.

The workshop that cannot open the file

On a Slave tool the workshop may never see a map. Alientech's design is that the Slave writes the Master's file and does not itself handle the modification. The check then has two halves, and they happen in different places.

The Master's half is the comparison above, done on the original that was sent, for the software identifier that was sent, with the hardware of that vehicle in mind. A stored file selected only by software number skips that comparison for this car. It can still be the right file when this car is the stock vehicle the file was built for, and when the identifier really matches. The match is the Master's responsibility to make, not a property of the portal.

The workshop's half is the half that does not require an editor. Confirm the hardware and software numbers against the file that came back. Confirm the read was a backup complete enough to restore the unit. Write only that file, then log the request against the delivered boost, fuel, lambda, timing and temperatures on this car. Logging a drivability complaint. A workshop that cannot open the maps can still refuse a file that identifies as a different software, and can still feel a car that smokes, knocks or pulls timing while the invoice says the calibration was checked. Those observations are the check that remains at the car. They are not a substitute for the comparison the Master was supposed to do before the file was returned.

Same software number, same file

The software identifier is the right key. It is not the whole key. A definition has to match the exact software, the file layout, the units and the byte order, which is the reference set in ME7 getting started. EVC's warning on reused maps is the same fact from the editor's side: a similar file is not proof that addresses and meanings match.

Inside one identifier the car can still differ in ways the number does not record. A later dealer update, a different turbo or injector that a previous owner fitted, a gearbox the torque limit was never meant to cover, and a market version with different emissions hardware can all sit under a label that looks close enough for a catalogue. The original read is what resolves it. The original read resolved nothing if nobody compared it with the file that is about to be written.

Hardware changes belong in the calibration explicitly. ECU remapping lists the usual ones: a different compressor, a different injector, a camshaft, a change in compression or displacement. An off-the-shelf file for the stock car, written onto that hardware, is the stock description applied to an engine that no longer matches it.

Stage numbers are a specification

Stage 1, stage 2 and stage 3 have no definition in the calibration material this page draws on. They are sellers' labels. One seller's stage 1 is a small change to the driver request on an otherwise stock car. Another's is a percentage across every table the tool found. The label does not say which limits moved, which hardware it assumes, or whether the file was ever logged. A stage number is a way of ordering a price list. The file behind it still has to be read as a file.

A power figure, a checksum or a code reader closes the job

A dynamometer or a road pull measures what that car did on that pull, in those temperatures, in that gear. It does not list the tables that changed. It does not show a knock correction that was already spending the margin, a smoke limit that will step in when the air is thinner, or a clutch that will slip at the torque the pull happened to reach. The useful record beside a power figure is the log of request, delivery and protection. Without it, the figure is a result with no cause attached.

Knock control is one of those protections, not a safety net that makes any file acceptable. It retards after knock has started. It does not put back a boost or torque ceiling the file removed, and it does not rewrite a table that was advanced past the fuel in the tank. Engine knock is the mechanism. The same shape applies to a diesel smoke limit: the limit is what keeps fuel inside the air that is there, and deleting the look of the limit in a file is how smoke is made. Diesel smoke limits.

A checksum that passes is an integrity result for the ranges the tool recalculated. It will pass for a careful file and for a destructive one, provided the sums match. It is necessary for the ECU to accept the image. It is not the calibration.

A code reader closes a different job. Stored faults are a diagnostic readout. Programming the flash is a download, which MOTOR describes as its own equipment and its own session through the diagnostic connector. A tool that can display a fault code has not, by doing that, read or written a calibration. Clearing a fault afterwards does not confirm the new file. It confirms that the code was cleared.

Putting the original file back undoes the calibration write, when the backup is a real image of what was there. It does not unwind adaptations that learnt on the modified car, and it does not undo a mechanical result of running the modified file. Adaptations and calibration drift. A virtual read that never held the whole memory is not that original, even if it was enough to send for a catalogue file.

What remains true of a catalogue file

A file prepared in advance can be the right calibration. The conditions are ordinary, and they are conditions, not a slogan. It was built for this software identifier. The hardware on the car is the hardware it assumes. Someone compared it with an original of that software, including the limits that sit under the request. Someone logged a car that matches, or logged this car, and looked at request against delivery, temperature and protection. The workshop that fits it still confirms the identifier and still has a backup that can restore the unit.

An automated tool can be part of producing that file. It can find candidates, apply a repeatable change and correct a supported checksum. The file becomes an off-the-shelf mistake at the moment those outputs are written without the comparison. The tool was not wrong to run. The unchecked result was treated as a calibration.

Sources