The master file can be freely modified, it is not encrypted. It contains all the data constituting the engine mapping.
The slave file cannot be freely modified. It can only be processed by the master to which the slave tool is linked.
The slave file is a file in .zip format that contains the same information as the backup file but also the data constituting the engine mapping.
The information it contains is encrypted and intended to be modified by a master.
The backup file contains all the memories of the MCU.
The extension used is .bak and corresponds to a .zip file. It can be decompressed with any decompression software that supports .zip format.
This file is automatically saved during boot read in the "Autotuner ECU backups" folder. This folder can be accessed by opening the Windows File Explorer and pasting the following address:
%userprofile%\documents\Autotuner ECU backups\
( The Windows File Explorer can be opened by using the keyboard shortcut "Windows Key + E" )
Maps are usually found in eflash0 or eflash1. These are variable data that occupy only a part of the memory, the rest is code to make the computer working.
As part of a boot tricore reading we find:
(eflash) if the MCU has an external flash memory
In the context of an OBD reading, no backup file is saved.
The backup file has two functions:
- Return a vehicle to its original state
To do this, the user has the option to directly write the backup file within the ECU.
The slave user has the option to write the backup file on his own initiative without intervention from his master.
- Edit data that does not relate to engine mapping
Any modification made to a file contained in the backup file causes the modification of its checksum.
Therefore, if the data has been modified, the user must systematically correct the checksum before writing one of the files from the backup.