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

[NamGrandPaa]

Hopefully someone more knowledgeable would chip in

[NamGrandPaa]

I’m having the same issues hoping this thread would help

[NamGrandPaa]

How long have you been having this issues ?

[ValVal456]

If anyone is interested in changing the coolant gauge buffer, it start at 0xF4.
there isnt much of a buffer on the S54 EEPROM compared to the non m.

M54 Cluster Water Temp Gauge




S54 Cluster Water Temp Gauge

I tried changing the gauge calibration string on a friend 3.0l Z3. For some reason it doesn't work, as soon as I program my custom string in the 93S56 EEPROM the cluster shows EEP_2 error and none of the gauge works. I tried both UPA USB and Xprog, programming process ends succesfully with each one. I verified every flash by reading the eeprom afterward, no difference between programmed file and read file. Of course, if I program the stock EEPROM file back everything works fine again.

Here is the stock gauge string : 0F 21 32 4E 4B A7 73 A7 78 2A 7D 53 which is 15 50 75 115 120 125°C.
Here is the modified string : 0F 21 3C 4E 55 A7 69 A7 6E 2A 73 53 which is 15 60 85 105 110 115°C.

Seems to me that there is a checksum in the file because that's the only explaination that come up to me for the program to throw an EEP_2 error. I would like to understand because it's a useful mod on the E46.

[sda2]

Does anyone know where the speedometer end value is stored in the cluster dump? I found 0xB4 and 0xB5 to be LoHi HEX*10 = rpm

Coding index looks to be stored at 0x89

[JBanzhaf]

I tried all the 93S56 algorithms PASoft provided and none were anything close to the actual EEPROM read.

Yes. PASoft hasn’t been setup to work with Z3 CAN bus clusters. The algorithm it uses doesn’t correctly read or write to the EEPROM. Interestingly enough, the dump it provides combines both the internal EEPROM and the coding plug with a large section of FF’s between them. It is unable to correctly write to the EEPROM. This is also in part because some sectors of the EEPROM are read only over TXD bus. So far, the only way I’ve found to code these clusters is by manually writing to the EEPROM chip itself using a chip burner.

[armenh7]

From my first attempt at reading the EEPROM with PASoft, it struggles to get an accurate read. Lots of FF's and missing information. That was only with a single algorithm though. I'll need to try the rest and see what happens.

I tried all the 93S56 algorithms PASoft provided and none were anything close to the actual EEPROM read.

[armenh7]

Yeah I wonder. Or maybe PASoft?

From my first attempt at reading the EEPROM with PASoft, it struggles to get an accurate read. Lots of FF's and missing information. That was only with a single algorithm though. I'll need to try the rest and see what happens.

[et89]

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.

Nice! keeping it inconspicuous with the black faceplate and no M-logo.

[ZiMMie]

Did you receive these things yet?
I am doing the same thing.

Waiting for my venoxy faceplate before continuing to build, but I am not sure yet how to wire in the Gauge.S into the cluster.

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.

[et89]

Just to give an update and a few tips.

I got the eeprom flashed.

ended-up removing it as i didn't have a clip.

X-prog is not able to flash the 93CS56.
It doesn't have the option to clear the "Protections Bit" that enables to writing the entire eeprom.

You can use X-porg for the external coding chip C46.

Ended up using UPA programmer to flash the CS56 Chip.
Tips...
Read Protect Register
Record the protection bit *DA*.
Clear Protect Regiser
Write the Eerpom
Write Protect Register


I have ordered the Gague S. and a custom M S54-Z3 gauges from Venoxy.

Its keeps the s54 m z3 tachometer scale but has the oil temp cutout for gauge s.

Did you receive these things yet?
I am doing the same thing.

Waiting for my venoxy faceplate before continuing to build, but I am not sure yet how to wire in the Gauge.S into the cluster.

[ZiMMie]

If anyone is interested in changing the coolant gauge buffer, it start at 0xF4.
there isnt much of a buffer on the S54 EEPROM compared to the non m.

M54 Cluster Water Temp Gauge




S54 Cluster Water Temp Gauge

[ZiMMie]

Just to give an update and a few tips.

I got the eeprom flashed.

ended-up removing it as i didn't have a clip.

X-prog is not able to flash the 93CS56.
It doesn't have the option to clear the "Protections Bit" that enables to writing the entire eeprom.

You can use X-porg for the external coding chip C46.

Ended up using UPA programmer to flash the CS56 Chip.
Tips...
Read Protect Register
Record the protection bit *DA*.
Clear Protect Regiser
Write the Eerpom
Write Protect Register


I have ordered the Gague S. and a custom M S54-Z3 gauges from Venoxy.

Its keeps the s54 m z3 tachometer scale but has the oil temp cutout for gauge s.

[terra]

JBanzhaf thanks. i just ordered one to play with. could you please upload the EEPROM.
Do you know what byte to change to change it from Miles to KM?


I'm going to integrate Gague s in mine.



This will give me Oil temp, Level, Logging, coolant etc.

This will be a much cleaner solution. Not to mention the convenience of not turning your head to look at other gauges.


terra are these CAN Messages applicable to MSS54HP (CSL 0401/0301) as well?

Yeah those should be generally accurate for the mss5x

[JBanzhaf]

ZiMMie, I’ll send you a dump from one of those clusters tomorrow evening. Interesting that you say the changes don’t stick, as that is the method I used to code the two KM clusters I have. Are you using the correct profile in NCS to perform coding changes? I use revtor’s expert mode profile.


It’s interesting that gauge.s requires you to manually define the CAN id’s. It was my understanding that it used one of the diagnostic lines going to the cluster to get its data. I thought it was also plug and play with native MSS54 support. I don’t know very much about the gauge.s, so I’m probably just misunderstanding something.