[X-treme]

Hello everybody, can someone reset working hours in my dump?  Thanks

[volavka]

Car , model................. ?

[Clusters]

From the VIN in the dump....

D700301

Prod. Date 2013-10-14
Type 320I (EUR)
Series F34 (3 Series)
Body Type SAT
Steering LHD
Engine N20
Displacement 2.00
Power 135kw / 184hp

[X-treme]

OKay maybe some more info, car came from chiptuner. he did virtual read with magpro, made tune on it, wrote tune back and car didn"t start anymore. The he tried recovery, car still doesnt start. After that he did VR with new genius, and wrote VR from genius (not tune). After that car started but has mil on and error 1f2108 (variantcoding).
So i checked, variant is in FEM 0C (UL). In dme coding it is 00. Off course i cannot code it sinds working hours to high.
What i tried: Cafd tool it gives you the hex string of the coding. Found this hexstring twice in the eeprom. But as soon as i write eeprom with modded coding data string there is an extra error saying dme not coded. After that i cannot code it with esys. only after flashing again i can code, but then variantcoding is back to 0 again.

[pweber84]

Start ISTA-D or P and program it again, should be fine.

[X-treme]

Obviously i tried that first, whole car is updated.

[CEBEP]

OKay maybe some more info, car came from chiptuner. he did virtual read with magpro, made tune on it, wrote tune back and car didn"t start anymore. The he tried recovery, car still doesnt start. After that he did VR with new genius, and wrote VR from genius (not tune). After that car started but has mil on and error 1f2108 (variantcoding).
So i checked, variant is in FEM 0C (UL). In dme coding it is 00. Off course i cannot code it sinds working hours to high.
What i tried: Cafd tool it gives you the hex string of the coding. Found this hexstring twice in the eeprom. But as soon as i write eeprom with modded coding data string there is an extra error saying dme not coded. After that i cannot code it with esys. only after flashing again i can code, but then variantcoding is back to 0 again.

program DME with esys, then read coding and check class power
it should match class power in FEM and class power calculated in FA_FP

[Gabrola]

OKay maybe some more info, car came from chiptuner. he did virtual read with magpro, made tune on it, wrote tune back and car didn"t start anymore. The he tried recovery, car still doesnt start. After that he did VR with new genius, and wrote VR from genius (not tune). After that car started but has mil on and error 1f2108 (variantcoding).
So i checked, variant is in FEM 0C (UL). In dme coding it is 00. Off course i cannot code it sinds working hours to high.
What i tried: Cafd tool it gives you the hex string of the coding. Found this hexstring twice in the eeprom. But as soon as i write eeprom with modded coding data string there is an extra error saying dme not coded. After that i cannot code it with esys. only after flashing again i can code, but then variantcoding is back to 0 again.

Changing the CAFD directly in the EEPROM is not working because after you change CAFD data the CAFD signature does not match and that's why you get a DME not coded error. Send me your CAFD with the fixed variant coding and I will fix the signature for you.

[X-treme]

OKay maybe some more info, car came from chiptuner. he did virtual read with magpro, made tune on it, wrote tune back and car didn"t start anymore. The he tried recovery, car still doesnt start. After that he did VR with new genius, and wrote VR from genius (not tune). After that car started but has mil on and error 1f2108 (variantcoding).
So i checked, variant is in FEM 0C (UL). In dme coding it is 00. Off course i cannot code it sinds working hours to high.
What i tried: Cafd tool it gives you the hex string of the coding. Found this hexstring twice in the eeprom. But as soon as i write eeprom with modded coding data string there is an extra error saying dme not coded. After that i cannot code it with esys. only after flashing again i can code, but then variantcoding is back to 0 again.

Changing the CAFD directly in the EEPROM is not working because after you change CAFD data the CAFD signature does not match and that's why you get a DME not coded error. Send me your CAFD with the fixed variant coding and I will fix the signature for you.

Yes i think it has to do with signature, but i don't know how to fix signature? Here are 2 cafds, one with variant 0c and one with variant 01, both are Untere Leistungsklasse.
Thanks   EDIT: POSTED WRONG CAFDS, HAVE TO MAKE NEW 

---

Okay, i added 2 cafds, one modified to powerclass 0C and one to 01. 

[Gabrola]

OKay maybe some more info, car came from chiptuner. he did virtual read with magpro, made tune on it, wrote tune back and car didn"t start anymore. The he tried recovery, car still doesnt start. After that he did VR with new genius, and wrote VR from genius (not tune). After that car started but has mil on and error 1f2108 (variantcoding).
So i checked, variant is in FEM 0C (UL). In dme coding it is 00. Off course i cannot code it sinds working hours to high.
What i tried: Cafd tool it gives you the hex string of the coding. Found this hexstring twice in the eeprom. But as soon as i write eeprom with modded coding data string there is an extra error saying dme not coded. After that i cannot code it with esys. only after flashing again i can code, but then variantcoding is back to 0 again.

Changing the CAFD directly in the EEPROM is not working because after you change CAFD data the CAFD signature does not match and that's why you get a DME not coded error. Send me your CAFD with the fixed variant coding and I will fix the signature for you.

Yes i think it has to do with signature, but i don't know how to fix signature? Here are 2 cafds, one with variant 0c and one with variant 01, both are Untere Leistungsklasse.
Thanks   EDIT: POSTED WRONG CAFDS, HAVE TO MAKE NEW 

---

Okay, i added 2 cafds, one modified to powerclass 0C and one to 01. 

Only 0C is UL not 01. You had more problems in your CAFD but I've fixed them all according to your VIN. Here is your CAFD with all values fixed and signature correctly set.

Also, don't read the hex string from Ncd Tool because it has a bug where the last byte in each NCD section is missing. Read it directly from the ncd in a text editor.  NCD files are in SREC (https://en.wikipedia.org/wiki/SREC_(file_format)) format and it is easy to read manually.

---

EDIT: I took a look at your EEPROM file and it seems that there are 2 occurrences of the coding values and 4 occurrences of the signature which is broken up into two pieces. I've went ahead and made the edits for you. I've added the edited EEPROM file for you.