
When playing around main processor, I warmed too much the PCB with the heat gun.

Then I set key to position 2, and mileage+SIA was taken by IKE from LCM. Remove FA infos from cluster with tool32 (c_fa_loeschen).Īnd then update ZCS with EWS infos with NCS and recode IKE (SG_CODIEREN with blank. I recoded my VIN with no issue with NCS (FGNR_SCHREIBEN). Mileage was reset to -00004 km on cluster display. I will try tomorrow morning with IKE on the car if resetting km to zero is enough to allow VIN programming. However, the M35080 programmer software allows to read, save the content of the eeprom but not to load or edit (or I didn't understood how) it so that I was unable to reset the VIN. Kilometers was properly reset to zero then. I removed the needles and I unsoldered the eeprom. In this case, M35080 programmer 5V was down to 1.2V. I didn't manage to program M35080 with eeprom soldered and not powering IKE. Is it needed to have the IKE powered or not? You can clear the ZCS with tool32 (function is ZCS LOESCHEN) It can't write mileage though (or at least it can't lower it). Thanks in advance!I just read the EEPROM out with PASoft.

Yes it seems each of the 16 16-bit values is increased at a time in a loop mode so that we only need to add the 16 16-bits values to have the proper mileage. Since you can erase easily LCM with pa soft, did you try to add a ZCS on top of FA and vice versa? I don't know if a module can have both ZCS and FA stored? I also have a CI37 ALSZ to store FA (no FA store since I bought it brand new). I think that I will have to reset also the FA from new cluster since my car is ZCS encoded (12/2000) and the new cluster is FA based. I'm currently waiting m35080 eeprom programmer to change VIN on the new cluster and update the mileage to the one of my factory cluster. I've bought a CI07 IKE to replace my CI04 one in order to retrofit dynamic brake lights. What tool do you use to read the whole eeprom? 2154D in decimal is 136525, which is exactly what was reported by the cluster.Yes it seems each of the 16 16-bit values is increased at a time in a loop mode so that we only need to add the 16 16-bits values to have the proper mileage.

So in this case, we have 3 sets of "2154". Then decrement that number by 1 for every "value - 1" groups you have. Take the value of the first group (0x2155 in the first example) and multiply it by 0x10.

There are 16 16-bit values in the beginning of the file. The VIN of the car in this case is PN60542.Įdit: Okay, I figured out how the mileage works too In the example above, what you have there is: VIN is stored in 5 bytes starting at 0x7A
