[Terraphantm]

Looks like it's on the back. And while I can't find a close up of the CPU, it looks pretty similar:



Even if you don't have convenient vias to solder to, you could solder straight to the CPU (though you'd have to be careful since all the points are next to each other)

[Mik325tds]

Originally Posted by Sensible_

EEPROM dump from E9X KOMBI (DCT) and MPH dials.

https://drive.google.com/open?id=0B0...0RzaHRHbnJRa2c

Thank you good sir!
It is very strange though. Even with this known good Eeprom content, the cluster always stays with one DTC:
9317 EEPROM: Fehler Codierdaten BMW
unplausibles Signal oder Wert
Testbedingungen erfüllt
Fehler momentan vorhanden und bereits gespeichert
Fehler würde kein Aufleuchten einer Warnlampe verursachen
Error code: 93 17 68

I can write my VIN to it and the tamper dot goes away. But when I try to read (or write) coding data with NCSexpert, I get always this error message:
[10:17:26.214] [2017-01-10] [SERIE] 2062 PABD/CABD A_PL2KMB.IPS Cod 391
[10:17:26.214] [2017-01-10] [SERIE] Fehler beim Codierdaten lesen KOMB87, C_C_LESEN: ERROR_ECU_UPLOAD_NOT_ACCEPTED
[10:17:26.319] [2017-01-10] [SERIE] 2062 Error COAPI2.CPP coapiRunCabd 6
[10:17:26.319] [2017-01-10] [SERIE] Fehler beim Codierdaten lesen CODIERDATEN_LESEN

A nettodat coding goes through without problems, but as soon as I code it either with Nettodat or empty FSW_PSW.MAN, I get this message on the CIC:
"Speedometer display malfunction".
Yet the speedometer works fine, in Ediabas and while driving. The rpm gauge stays at 0 (except shortly after reset with engine running). All gauges work flawlessly with Ediabas steuern_xxx.

Any ideas?

[Terraphantm]

What kind of car are you trying to install this cluster in?

[Dtype]

Originally Posted by Mik325tds

Thank you good sir!
It is very strange though. Even with this known good Eeprom content, the cluster always stays with one DTC:
9317 EEPROM: Fehler Codierdaten BMW
unplausibles Signal oder Wert
Testbedingungen erfüllt
Fehler momentan vorhanden und bereits gespeichert
Fehler würde kein Aufleuchten einer Warnlampe verursachen
Error code: 93 17 68

I can write my VIN to it and the tamper dot goes away. But when I try to read (or write) coding data with NCSexpert, I get always this error message:
[10:17:26.214] [2017-01-10] [SERIE] 2062 PABD/CABD A_PL2KMB.IPS Cod 391
[10:17:26.214] [2017-01-10] [SERIE] Fehler beim Codierdaten lesen KOMB87, C_C_LESEN: ERROR_ECU_UPLOAD_NOT_ACCEPTED
[10:17:26.319] [2017-01-10] [SERIE] 2062 Error COAPI2.CPP coapiRunCabd 6
[10:17:26.319] [2017-01-10] [SERIE] Fehler beim Codierdaten lesen CODIERDATEN_LESEN

A nettodat coding goes through without problems, but as soon as I code it either with Nettodat or empty FSW_PSW.MAN, I get this message on the CIC:
"Speedometer display malfunction".
Yet the speedometer works fine, in Ediabas and while driving. The rpm gauge stays at 0 (except shortly after reset with engine running). All gauges work flawlessly with Ediabas steuern_xxx.

Any ideas?

What datens are you use?

[Sensible_]

Try another Daten set. Maybe a bug with these datens.

Also could be hardware problem. Have you removed and resoldered the eeprom chip?

[Mik325tds]

Originally Posted by Sensible_

Try another Daten set. Maybe a bug with these datens.

Also could be hardware problem. Have you removed and resoldered the eeprom chip?

I tried reflashing it multiple times.
The cluster is from a 2007 E92 328xi with the ZB number 9168354. I’m trying to retrofit it into a 2011 E90 335d. My cluster’s ZB number is 9242376. Both point to the same program file 9316169A.opa in HKOML2, except that my ZB number updates to the newest ZB nr 9316157 and the E92 updates to the ZB nr 9316151. I also tried force feeding the ZB 9242370 of a 2011 E92 (file 9242396A.0pa) via WinKFP expert mode. All flashes went without problems but the EEprom corruption DTC persists.
I did physically replace the original EEprom but I’m sure the connections are all good since I can write to the gauge sections with Ediabas just fine.
Any other suggestions? Your help is greatly appreciated.

[Sensible_]

Are you able to test the cluster in another vehicle?

Also, if you read eeprom back and compare to original is it the same?

[Mik325tds]

Originally Posted by Sensible_

Are you able to test the cluster in another vehicle?

Also, if you read eeprom back and compare to original is it the same?

Interesting question - do you think that the coding error dtc is because it is now placed in an E90 instead of an E92? I can try in a 2011 E92 but I'm beginning to think that this has to do with it being from a 2007 model year.

Reading back EEprom confirms that content is exactly the same as the file written to it. I always do that in addition to the automatic verify the xprog.

[808AWD325xi]

Originally Posted by Mik325tds

Interesting question - do you think that the coding error dtc is because it is now placed in an E90 instead of an E92? I can try in a 2011 E92 but I'm beginning to think that this has to do with it being from a 2007 model year.

Reading back EEprom confirms that content is exactly the same as the file written to it. I always do that in addition to the automatic verify the xprog.

Your original cluster and the donor cluster share the same physical hardware number, 6966737. You can verify this with PHYSIKALISCHE_HW_NR_LESEN.

Have you tried flashing the donor cluster with ZB number 9242376?

The reason I ask is because unlike the petrol kombi high firmware releases which are qualified across multiple chassis types, ZB number 9242376 was exclusively qualified for the US 335d 09/08-11/11.

[Alex_WLY]

Originally Posted by Mik325tds

I tried reflashing it multiple times.
The cluster is from a 2007 E92 328xi with the ZB number 9168354. I’m trying to retrofit it into a 2011 E90 335d.

I think here is the problem.
you want petrol cluster to fit on diesel car?!?!?!?

[N54Twin]

Originally Posted by Mik325tds

Interesting question - do you think that the coding error dtc is because it is now placed in an E90 instead of an E92? I can try in a 2011 E92 but I'm beginning to think that this has to do with it being from a 2007 model year.

Reading back EEprom confirms that content is exactly the same as the file written to it. I always do that in addition to the automatic verify the xprog.

U never put a pre-lci cluster on a lci.

[Sensible_]

Originally Posted by N54Twin

U never put a pre-lci cluster on a lci.

I think this is more likely the problem.

Have you tried coding the KOMBI with a fake date in FA?

Change FA to date of retrofitted cluster but DO not FA_WRITE. Then go back and code KOMBI to default with expert mode and SG_CODIEREN.

[Dtype]

My cluster is from a E92 335d LCI and my car is a E91 320d non-lci and I got no errors. Could not be that.
Are you sure your "new" cluster is from a 328? Rpm gauge is marked at 8000rpm?

[Mik325tds]

Originally Posted by 808AWD325xi

Your original cluster and the donor cluster share the same physical hardware number, 6966737. You can verify this with PHYSIKALISCHE_HW_NR_LESEN.

Have you tried flashing the donor cluster with ZB number 9242376?

The reason I ask is because unlike the petrol kombi high firmware releases which are qualified across multiple chassis types, ZB number 9242376 was exclusively qualified for the US 335d 09/08-11/11.

You guys never cease to amaze me. How did you know this? It works perfectly now.
I find that very strange though. In the history file all ZB numbers 9242376 (your suggested), 9242396 (my current) and 9168354 (the donor cluster original) all point to the same newest update file 9316169A.opa. Why wouldn't the donor work with that?
Also, you are right that they both share the same physical hardware number, 6966737. But when I opened up mine to pull the EEprom data, I noticed that the EEprom was turned 90 degrees in comparison to the donor cluster. How can the be the same HW number? Usually, if a supplier does a change like that, the HW number changes as well.

Anyway, thousand thanks to you 808AWD325xi and Sensible_ for your help!

You wouldn't know by any chance what the coding would be to display coolant temp on the oiltemp/KVA gauge?

[N54Twin]

Originally Posted by Dtype

My cluster is from a E92 335d LCI and my car is a E91 320d non-lci and I got no errors. Could not be that.
Are you sure your "new" cluster is from a 328? Rpm gauge is marked at 8000rpm?

U can put a LCI on a pre lci without a problem.

The problem is Pre lci to lci.

In 5 Series case, cruise control error if u put a Pre lci on a lci.

[808AWD325xi]

Originally Posted by Mik325tds

You guys never cease to amaze me. How did you know this? It works perfectly now.
I find that very strange though. In the history file all ZB numbers 9242376 (your suggested), 9242396 (my current) and 9168354 (the donor cluster original) all point to the same newest update file 9316169A.opa. Why wouldn't the donor work with that?
Also, you are right that they both share the same physical hardware number, 6966737. But when I opened up mine to pull the EEprom data, I noticed that the EEprom was turned 90 degrees in comparison to the donor cluster. How can the be the same HW number? Usually, if a supplier does a change like that, the HW number changes as well.

Anyway, thousand thanks to you 808AWD325xi and Sensible_ for your help!

You wouldn't know by any chance what the coding would be to display coolant temp on the oiltemp/KVA gauge?

You're welcome!! I'm glad that you were able to get things sorted.

With regards to the program data sets (.0pa), each of the ZB numbers in this case actually reference a different .0pa file:

2007 E92 328xi donor ZB number 9168354 --> 9168320A.0pa
2011 E90 335d original ZB number 9242376 --> 9242396A.0pa

If you have the SP daten that includes a given ZB number, view the .DAT file to determine the corresponding program data set.

For example, HKOML2.DAT:

;ZB-NR  TYP-NR  HW-NR  IX SW-NR     AM          PIN S CS
[...]
9242376,0000000,9242396,A,0000000DA,0FFFFFFFFFD,000,1 4
[...]

9316169A.0pa is used by the latest firmware for the US 335d, ZB number 9316157:

;ZB-NR  TYP-NR  HW-NR  IX SW-NR     AM          PIN S CS
[...]
9316157,0000000,9316169,A,0000000DA,0FFFFFFFFFD,000,1 R
[...]

Neither the donor cluster nor your original cluster are compatible with that program data set because it's intended for the latest kombi high hardware (part numbers 62-10-9-283-845 and 62-10-9-316-157):
http://www.realoem.com/bmw/enUS/part...2-10-9-316-157

I believe that physical hardware numbers only change when there is a material change which impacts firmware compatibility.

[berne]

Originally Posted by N54Twin

U can put a LCI on a pre lci without a problem.

The problem is Pre lci to lci.

In 5 Series case, cruise control error if u put a Pre lci on a lci.

PM and mail

[19E92]

Has anyone successfully done this with a MiniPro TL866CS (there is also a TL866A) programmer and SOP 8 clip?

I have the TL866CS and it's giving me an over current error...

[Alex_WLY]

I know someone who put nLCI cluster on LCI car with zero problem.

[kylet101]

Originally Posted by 19E92

Has anyone successfully done this with a MiniPro TL866CS (there is also a TL866A) programmer and SOP 8 clip?

I have the TL866CS and it's giving me an over current error...

Did you try this:
http://www.bimmerfest.com/forums/sho...46&postcount=9

[jimmy1022]

bumping this one if anyone can help,

have 07 m3 cluster to retro fit to 06 335i, miles and vin are correct but when I try to code i get these 2 errors:

2060 PABD/CABD A_PL2KMB.IPS COD 371
coding erroneous (general) KOMB87, C_C_AUFTRAG: ERROR_ECU_UPLOAD_NOT_ACCEPTED.

and

2060 Error COAPI2.CPP coapiruncabd 6
coding erroneous (general) sg_coderian

with i drive error "speedometer display faulty"

can anyone help?

[ahmedsesco]

can i take off old eeprom from old cluster and put it on the new cluster this will fix the problem and my vin will be ok and milage even if they are deffrant kinds of eeprom pls hlp