how to use ecusafe

CU-Safe V2
ECU safe is a remapping tool which enables you to edit flash files of different ECU to change its performance and its functions according to your needs, it supports a huge cars ECU list, also it's easy to use, read below how to use ECU safe.
1. Start application

After starting of application your screen should look like this:

Information about licensed modules and databases for DPF / FAP and speed limiters is presented. 
2. Choose type of file - open combo box.

Standard selection is “Any car (for speed limiter only)” as seeking for speed limiter , does not need file type to be selected. In other cases (DPF / FAP removal and/or anti OBD protection) exact car and ECU (ECM) group should be chosen. In this example we choose VAG Siemens PPD.


3. Select options - checkboxes on the right side. 
 Protection - select to scan for locking OBD read of file.
 Remove DPF - select to scan for DPF / FAP structures and switch them off.
 Find speed limit - select to scan for speed limit structures and change them.
 Use 2nd pass - use additional heuristic pass trough data if first pass was unsuccessful. 
4. Select binary to be processed - Open binary button
After opening binary (“Open binary”)ECUsafe starts to process it. This may take quite a long time, especially when “Use 2nd pass” checkbox is checked. Progress will be visible on progress gauge. 
In case of troubles you can switch off (by clicking appropriate button) some types of patches, that may be applied by ECUsafe to your binary. When button is red, that patch type wont be applied. Usually there is no need to do this. In case of strange behavior (no power at all) try switching off “Torque limiters”. In case of too high NOx levels, switch off “Postinjection” removal. In case of diagnosis problems, switch off “DTC Error Tables”. Strategy Maps should be switched on anyway.
After finishing processing of file, “Save binary” button will be enabled. Pressing it will open dialog, where file can be named and saved. “Cancel scan” can stop scanning at any time.
By pressing “Online Help” button, this manual will be invoked in your browser. If file is unsuccessfully scanned and you want it to be manually processed by us, and it’s structures to be added to ECUsafe database, press “Upload file”. This invokes web form, where user should give his e-mail and description.  “Check for updates” button invokes updater for databases. It tries to get newer databases (if available). If it finds new databases, it shows popup window with information about newer databases. Otherwise it closes without any popup.
While processing file comments will be visible:
- ECU software number (if found)
- structures, that are found (here in this example: PPD1.1 L1 structure in DTC table (responsible for Particle Filter pressure sensor)
- after finishing of scan - information about success or failure of scan will be shown.
Progress bar may go with various speed. When square indicator on the right of progress bar is gray checked - empty or unimportant area is found and scan goes faster. If it is pale yellow - data is found and scan goes slower. After finishing scanning it is green checked if file is patched successfully. Otherwise it is red.
5. Opening EEPROM files
ECUsafe can automatically process EEPROM files (read in programmer or extracted with BDM tool).
In cases, when even after removing FAP/DPF there is blinking lamp at dashboard, this means, that level of FAP at moment of removal was over critical point (vary from car manufacturer to car manufacturer). Usually it is over 200%. This value is stored in EEPROM and must be cleared (set below threshold). EEPROM editor is added to ECUsafe. Read EEPROM and open binary file in ECUsafe. Remember to choose proper brand of car and ECU type. Point of FAP level storage will be detected automatically. Set it to any low value (or zero). Export file and program EEPROM with it. EEPROM checksum is calculated automatically. Blinking lamp will disappear. Below you can see example of ECUsafe reaction to opening EEPROM file (notice that proper file type must be done.) This example is with Audi 3.0 TDI EDC16 EEPROM:
Usually you should set value to zero. Checksum in EEPROM is updated automatically.