SOPS Recovery I&M

be corrupted or erased. This can happen when SDP3 writes SOPS in ECU and communication stops or interferes between client system and SDP3.
Using special tool 99 738 and connect to engine stand alone, helps to avoid this kind of failure. If customer panel have the possibility to stop diagnostics, it can help.
Follow the instrucion to write SOPS back in ECU.
The recovered SOPS would be the one saved in the last SDP3 connection. You should re-start the jobb you did after that.
Exemple: Connect to SDP3 2018,01,25-14:12:08. Change 3 parameters in adjustments. SDP3 try to write SOPS and it gets corrupt due comunication brake down. You choose the file ”xxxxxxx 2018-01-25 141208”. After you are done with SOPS Recovery you may Change parameters again.

26 February 2018

Info class internal Department / Name / Subject

SOPS Recovery I&M

"eng nr" OperationalData folder. Choose the file created just before SOPS disappeared.

Info class internal Department / Name / Subject

26 February 2018

and add ”.txt” to create a ”light” demo file.

file in Demo mode. You can use ”Check and adjustments” or ”Conversion”

file

ECU and choose Converion jobb tipe.