DIY: Z3 Non-M gauge cluster to Z3M S54 Conversion

[burhan]

Burhan, I just sent you an EEPROM dump from a US spec E36 M3 cluster. It should match the odometer mileage on your coding plug. So it should not have a tamper dot illuminated. Hopefully this works for you.

Thanks,
Joel

i tried with the dump but it is showing code eep2. also the guage is not working at all. what to do now. appreciate your help.

[burhan]

Burhan, I just sent you an EEPROM dump from a US spec E36 M3 cluster. It should match the odometer mileage on your coding plug. So it should not have a tamper dot illuminated. Hopefully this works for you.

Thanks,
Joel

Thank you so much, i will write it and update you soon

[JBanzhaf]

Burhan, I just sent you an EEPROM dump from a US spec E36 M3 cluster. It should match the odometer mileage on your coding plug. So it should not have a tamper dot illuminated. Hopefully this works for you.

Thanks,
Joel

[burhan]

thank you for response, please if you can try to send me us spec m3 cluster epprom dumps. atleast my half job will be done.

[JBanzhaf]

sorry for late response, yes you are right the main eeprom data has been lost with wrong reading. i am using dsp3+ programmer and the cluster for e36 m3. so i need your help to send me dump for both eeprom so i can flash it.

It looks like that’s a late model E36 non-M euro cluster. Unfortunately I don’t have any EEPROM dumps from any of those. I’m not sure if it’ll work, but I can get you an EEPROM dump from a US spec M3 cluster. Then maybe you can code it back to euro spec non-M using NCS Expert.

[burhan]

Sorry I'm only replying to you now. I didn't see the post until now. I just sent you a PM asking you some additional details. I should be able to help you get it fixed. I just need to know exactly what you have, and what you're trying to do. The one dump you attached looks like a good dump of the coding plug M93S46 EEPROM, with a good and non-corrupt mileage. I'm not sure what the other dump is, as it does not match the format of the CAN bus Z3 cluster's ST93CS56 dumps, and the non-CAN bus E36 clusters don't use ST93CS56 EEPROMs. It would also be helpful if you attached photos of the chips and the IC that you're trying to flash, to help identify what you're working with. I think you may be possibly trying to flash your internal EEPROM with the wrong settings.

Thanks,
Joel

sorry for late response, yes you are right the main eeprom data has been lost with wrong reading. i am using dsp3+ programmer and the cluster for e36 m3. so i need your help to send me dump for both eeprom so i can flash it.

[deyayi]

Hey Joel. I needed some help with a few things are you able to pm me? I guess my accounts too new to message you first
thanks

[JBanzhaf]

can anyone send me dump for coding unit and main eeprom fo bmw e36. my both dump is got corrupted and now getting error in display. please help

Sorry I'm only replying to you now. I didn't see the post until now. I just sent you a PM asking you some additional details. I should be able to help you get it fixed. I just need to know exactly what you have, and what you're trying to do. The one dump you attached looks like a good dump of the coding plug M93S46 EEPROM, with a good and non-corrupt mileage. I'm not sure what the other dump is, as it does not match the format of the CAN bus Z3 cluster's ST93CS56 dumps, and the non-CAN bus E36 clusters don't use ST93CS56 EEPROMs. It would also be helpful if you attached photos of the chips and the IC that you're trying to flash, to help identify what you're working with. I think you may be possibly trying to flash your internal EEPROM with the wrong settings.

Thanks,
Joel

[burhan]

can anyone send me dump for coding unit and main eeprom fo bmw e36. my both dump is got corrupted and now getting error in display. please help

[burhan]

hey mate,
I am trying to change the mileage for the cluster , as my older cluster is damage and i got another cluster, now i would like to write the orig km, which i am unable to do so, rear 93c46 code plug and main eeprom (unknown chip), seems the main eeprom is corrupted now as now the cluster diplayed eep-2, before when i was trying to rear and write code plug eeprom the km was showing same.
i have attached both the file for cluster, can you help me to reflash and send me , or if you have new file to be reflashed please help me to send.

i would like to know while writing the main eeprom the error pops up in programmer (DSP3+) code error while writing which means chip is not rewriting the data, even now i am trying to rewrite orig dump also it is same. so cna you tell me which eeprom it is so i can use new eeprom and reflash with new dump.

thank you

[JBanzhaf]

Hello

I am doing an S54 swap into an 01/99 Z3 that originally came with an M52TU/MS42, but that I had previously put an M54/MS43 into. Now I finally own an S54/MSS54 and am collecting all of the little things to make it work well. I have a CAN 02 cluster that works well with the MS43 DME (but I see that you have had better luck with CAN 03 clusters so I can pick one up if necessary). I would really appreciate if you could send me the EEPROM dump from the S54 Z cluster so I could reflash mine. The chassis and engine both have around 150K miles on them, so if it's possible to just use my CAN 02 cluster I wouldn't have to touch the milage.

Thanks,
Nathan

Just sent you a DM with the EEPROM dump. Let me know if you have any questions or issues. This dumps works fine on all CAN clusters, so it will work fine on your CAN 02.

[nesterkyn]

Hello

I am doing an S54 swap into an 01/99 Z3 that originally came with an M52TU/MS42, but that I had previously put an M54/MS43 into. Now I finally own an S54/MSS54 and am collecting all of the little things to make it work well. I have a CAN 02 cluster that works well with the MS43 DME (but I see that you have had better luck with CAN 03 clusters so I can pick one up if necessary). I would really appreciate if you could send me the EEPROM dump from the S54 Z cluster so I could reflash mine. The chassis and engine both have around 150K miles on them, so if it's possible to just use my CAN 02 cluster I wouldn't have to touch the milage.

Thanks,
Nathan

[bmxcm]

Yes. although i haven't had time to continue. I'd like to reuse unused pins on the Cluster PCB and install external wifi antenna.
Hopefully i find some time within this month to finish it up. Although I'm not really in a rush.
Here is how it sits currently.

Any updates on this ZiMMie ?

I love the Gauge S integration, I may have to steal that idea from you. Is the custom gauge face setup from Venoxy fairly straightforward?

[bmxcm]

So much great info in this thread, I've been looking for a solution for my impending swap and this may check all the boxes. So grateful for this community.

[todor]

Todor,

I sent you another PM with some more information, as well as an updated coding plug dump for converting to KM. All E36 cluster coding plugs store their odometer mileage in a dimensionless hex value. When you code it to KM, it keeps the same value and switches the display to KM. The hex value for the coding plug is only accurate to plus or minus one mile, as part of the algorithm equation divides the value by 2. This is why it's displaying 130001. Also, the internal EEPROM file I sent you was coded using NCS Expert for regular E36 brake fluid level sensors, as they are different to Z3's. As 99% of these clusters have gone into S54 swapped E36's, I forgot about that difference. So I sent you a file that needed one coding change made. Glad you got that figured out.

Thanks,
Joel

Thanks very much Joel! I've been away from home for the holidays and that's why I haven't replied. Also, apparently I can't reply to PMs (I guess my account here is too new). Pls send me a PM with your email and I'll send you my original files - I certainly don't mind sharing those to help out the community.

Coding is not an issue for me - I can just redo it with NCS Expert at any point in time, but it seems like it does require the VIN to match. There's also the issue of the FA and other ZCS data... which in my case happened to be 100% the same as the data on the dump you sent me. And since the default coding is determined based on the ZCS data, I could also just code thw cluster using its own ZCS data even if the VIN didn't match (and that worked). But yeah, looks like switching the VIN in the dump and then recoding with NCS Expert works too.

Btw I also recorded other dumps at various steps in my process, so you can see which bytes get changed for which operations. I'll send you all of those by email.

-Todor