TECHNICAL WIKI
Getting started with engine remapping
Do you want to offer engine remapping in your garage? Before choosing a tool, you need to understand what you will actually do on the vehicle, which operations you can outsource, and which checks remain your responsibility. Here is how a job works, the equipment you need, and the points to master to get started on the right footing.
01
Offering remapping without developing the files yourself
A garage can offer remapping services without modifying the maps itself. It must, however, master the workshop side: vehicle diagnostics, ECU identification, choice of the read and write procedure, power supply during programming and checks after the job.
Modifying the file is a separate activity. It requires understanding how engine management strategies work and how the different maps interact: torque request and limitation, injection, ignition on petrol engines, boost, temperatures and protections. Changing values without mastering these interactions can cause malfunctions or damage the engine.
Developing and validating your own maps usually takes years of training, practice and development work. It is work that calls on the skills of an engine development engineer. Buying WinOLS, a Master tool or a map definition pack does not give you this expertise.
With a File Service, the garage handles the vehicle and the read and write operations. Developing or adapting the file is entrusted to the provider. This setup lets you offer services without claiming to master map development yourself.
Who does what?
| Operation | Garage using a File Service | Workshop developing its files in-house |
|---|---|---|
| Diagnostics and checking the vehicle’s condition | Garage | Garage |
| ECU/TCU identification, read and write | Garage | Garage |
| Modifying the maps | File Service | In-house team with the necessary skills |
| Checks and tests on the vehicle | Garage | Garage |
| Analysing and correcting a possible file-related problem | Exchange between garage and File Service | In-house team, with the vehicle’s logs |
02
Master and Slave: what the tool really changes
With a Slave tool, files intended for modification are generally protected and must be processed by the Master the tool is associated with. With a Master tool, the professional generally has directly usable files and can choose their File Service more freely, depending on the supported formats.
In both cases, working on the vehicle requires a sound command of ECU identification, diagnostics, reading, writing and post-programming checks. Moving from Slave to Master does not, on its own, turn the professional into a map developer.
Developing files yourself is a separate activity. See the section above and the Master vs Slave guide: the tool does not replace engine calibration expertise.
03
The equipment you actually need
A read and write tool
A tool such as AutoTuner, KESS3, or Flex can identify, read, and write ECUs or TCUs depending on its coverage and licences. None of these tools supports every vehicle and every operation. Before buying, check the manufacturer's compatibility list for the brands, years, ECUs, and access methods you encounter most often.
Master or Slave mainly depends on how you obtain and process files. A Slave can suit a workshop working with an associated Master. A Master gives more freedom choosing a File Service. In-house development remains a separate activity. See our “Master vs Slave” guide.
A power supply suited to programming
During an on-vehicle write, voltage must stay stable for the entire operation. A simple maintenance charger is not necessarily designed to deliver the current required during programming. Use a stabilised power supply (voltage support) designed for programming, with the characteristics recommended by the tool and vehicle manufacturer.
A diagnostic tool
Before working, record fault codes and useful parameters. After writing, check starting, any faults, and vehicle operation. Depending on the service, logging engine parameters under load may be necessary. A flash tool alone is not a complete diagnostic solution.
A computer and file organisation
Use a computer compatible with manufacturer software, reliable connections, and clear folder structure. Keep the read file, modified file, ECU identification, and job information. Never overwrite your only copy of the initial read.
04
How does a job work?
- 01
Identify the vehicle
Record the model, engine, year, gearbox, ECU or TCU references, and any mechanical modifications. Two vehicles advertised with the same power may use different ECUs or software.
- 02
Check its condition
Query the ECUs, record present faults, and look for issues that could affect the service. Boost pressure loss, an injection problem, or a gearbox fault must be investigated before any modification.
- 03
Read or identify the ECU
Select the protocol indicated by the tool manufacturer. Depending on the ECU, this may be a real, partial or virtual read. A Virtual Read provides a reference file tied to software identification, not a backup of the current content — details in the Read and write guide.
- 04
Prepare the request
Send the file accepted by your supplier, with vehicle references, mechanical modifications, useful fault codes, and the requested service. State if the vehicle has already been remapped.
- 05
Write the adapted file
Use the write method intended by the tool for this ECU. The write method is not necessarily the same as the read method. Follow the software instructions, maintain power, and do not interrupt the procedure.
- 06
Verify the result
Confirm start-up and operation, re-read faults and analyse any anomaly. Carry out a road test and, when relevant, logs or dyno measurements. Results must be assessed on the vehicle, not only from file delivery.
05
Practical case: a vehicle has already been remapped
A workshop receives a vehicle whose owner wants a new calibration but does not know its history. The tool identifies the ECU and offers a Virtual Read. That reference file alone cannot reveal modifications already in the ECU. Do not present it as a backup of the installed map (see the Read and write guide).
Before ordering, it records hardware and software references, reports the uncertain history to the File Service, and checks whether a real read is necessary or possible. It then follows the procedure compatible with the tool and ECU. This example shows why knowing how to start a read is not enough: you need to understand what the file obtained actually represents.
06
Mistakes to avoid when starting
Buying a tool without checking real coverage.
Compatibility depends on the ECU, software, access method, and sometimes the licence.
Confusing identification and backup.
A file obtained by Virtual Read may not represent the ECU's current content.
Neglecting power supply.
An interruption during programming can prevent the ECU from restarting.
Sending a file without context.
A vehicle already modified or fitted with non-standard parts must be reported.
Skipping checks.
A write completed without error is not enough to confirm correct vehicle operation.
07
And what next?
To start, focus on diagnosis and read/write operations on the vehicles you take on. Master vs Slave mainly affects how you use files and work with a provider. Map development remains a separate trade.
Remapping must respect rules applicable to the vehicle and its use. Removing or disabling an emissions device (DPF, EGR, AdBlue, catalyst, etc.) can make the vehicle non-compliant with its type approval for road use, depending on country and usage. The installer informs the customer and remains responsible for the local framework. This is not personalised legal advice.
Already have a read tool? Discover how the ECUTuneFiles portal works and the services available.
Access the portal