Mercedes W204 2008 - Dash swap

[jaxone]

I have a W204 2008 where the dash will turn off after it gets hot.

Instead of trying to repair want to just change cluster with another used one.
If I buy used cluster there will be warranty on it and can't open.
Can I read 24C128 eeprom on the table trough the cluster connector or not possible ?

Clsuter part number : A2045404548

I have Carprog , FVDI , DP3.

Thanks in advance.

P.S. Alternatively , if this is a common problem for this clusters, is there any repair guide ? Some capacitor broken or transistor maybe ?

[Cllau]

Mate, to read that Eeprom you need to open the dash....:captain:

[autodiagdoctor]

Yes, you can connect the cluster on bench and read the eeprom by diagnostics. Then just write the eeprom dump in your donor cluster and all should be fine.

[pepi]

You cant just write eeprom data to other dashboard . All you need is to write SSID of original dashboard to the spare dash and of course km stand.
Upload two dumps and we can prepare your new dump.

[jaxone]

Thanks.
As far as I understand I can not power up / read dash on bench without a can emulator ?

Pepi: If not possible to read eeproms by obd or bench , then I will have to open up dash. So why not just swap over the 24C128 ?

[jaxone]

Mate, to read that Eeprom you need to open the dash....:captain:


I can see FVDI has option to read dash eeprom by obd. Safe ?

[rafalgt]

Hi.
FVDI read eeprom but not all, can not read first 7line.
There is mileage and SSID.
SSID is in fifth line...
Open dash, read 24LC128 eeprom, edit SSID (fifth line) and if new dash has bigger mileage correct it. If lower than EZS don't need correct mileage.

[pepi]

Thanks.
As far as I understand I can not power up / read dash on bench without a can emulator ?

Pepi: If not possible to read eeproms by obd or bench , then I will have to open up dash. So why not just swap over the 24C128 ?

You can write ONLY if your label is 100% same with spare dash. Even then you dont know if was updated dash or no , so better dont do it.

[jaxone]

You can write ONLY if your label is 100% same with spare dash. Even then you dont know if was updated dash or no , so better dont do it.


OK, understand.
I will just open up and read eeproms from both. Will post dumps as soon as I get donor dash home. Thanks for headsup !

[jaxone]

Attached Redout from ORI Cluster.

[jaxone]

Finally "NEW" Cluster arrived.
It has same part number but I have not connected it to the car to read ID and info.

Attached Defective Cluster 24C128 ORI and New Cluster 24C128 ORI.
Can someone please move KM and SSID from "DEFECTIVE" to "NEW" ?

Thanks in advance.

[jaxone]

I tried to transfer SSID and KM , can someone please check if correct ?
Thanks.

[jaxone]

Well, I wrote my edit on the new cluster eeprom and installed in the car.
After 2 seconds 999.999km appeared :)

I could start the car.
Then I corrected the mileage in EZS and Dash DP3 and everything seems ok.

Looking at service assist data on the OLD eeprom, this car has actually drove 477.xxx km .... but hey , he did not come to me to adjust mileage just swap the dash.

Thanks everyone for the input, I have learned something new today.

[jaxone]

Hi.
FVDI read eeprom but not all, can not read first 7line.
There is mileage and SSID.
SSID is in fifth line...
Open dash, read 24LC128 eeprom, edit SSID (fifth line) and if new dash has bigger mileage correct it. If lower than EZS don't need correct mileage.

Thanks for the picture, saved me some time.

[omglol]

Reviving old thread ...

I have the same problem. I need to put used instrument cluster in Mercedes W204 2007. Original one is dead. Unfortunately, I don't have OBD tools for this job. Can I:

1) read ORIGINAL instrument clusters' EEPROM (24LC128) to extract SSID and mileage
2A) read USED instrument clusters' EEPROM (24LC128) and put original SSID and original mileage
2B) read USED instrument clusters' EEPROM (24LC128) and put original SSID and 0 km

Which procedure is correct, 2A or 2B? How can I avoid mileage getting 999.999km? I don't have tools for EZS. Thanks in advance!

[pepi]

Upload booth dumps.

[peko]

hi friends

i have same problem, but guy swap dash and original dash go to destroy it

so i reset SSID & mileage
can you confirm my reset is ok please ?

and second question, how i can extract SSID from w204 car ? i test with learning key tool but not show SSID

thanks

[brend]

hi friends

i have same problem, but guy swap dash and original dash go to destroy it

so i reset SSID & mileage
can you confirm my reset is ok please ?

and second question, how i can extract SSID from w204 car ? i test with learning key tool but not show SSID

thanks


If fbs3 , right tool away you can get this from key .
Tool like : cgmb , vvdi bga and other similar tool .

If fbs 4 , you can't get this from car or key .
And for this only virgin and atorization option .

[peko]

is year 2010 so can't read SSID from eis

from ECU is not possible ?

[brend]

is year 2010 so can't read SSID from eis

from ECU is not possible ?



What about key ?


Or start first ..........
Which tool you have for work with mersedes ?

Because with right tool easy get from.........
# key
# ezs
# elv

[peko]

What about key ?


Or start first ..........
Which tool you have for work with mersedes ?

Because with right tool easy get from.........
# key
# ezs
# elv

about keys i use autel but i test it via obd , can add keys but not show ssid

maybe on bench ezs ? i not test it

i mean about ECU engine because i have lot of tools according with this job

enigma not read this EZS

[brend]

about keys i use autel but i test it via obd , can add keys but not show ssid

maybe on bench ezs ? i not test it

i mean about ECU engine because i have lot of tools according with this job

enigma not read this EZS


About ecu.......

In here only hash and other info but not ssid .

[brend]

about keys i use autel but i test it via obd , can add keys but not show ssid

maybe on bench ezs ? i not test it

i mean about ECU engine because i have lot of tools according with this job

enigma not read this EZS


About ecu.......

In here only hash and other info but not ssid .


For safe time...........
Find person who have better tool for mersedes .
Just put key in read tool coil 1-2 sec and done .

[peko]

hi friend

i just test and found ssid
but when i write SSID in eeprom, dash continu showing ------- mileage

if i remove key, passed little time dash show 0 km so mileage is ok

but SSID not seem insert fine

can you check my mod file please ?

thanks

[brend]

hi friend

i just test and found ssid
but when i write SSID in eeprom, dash continu showing ------- mileage

if i remove key, passed little time dash show 0 km so mileage is ok

but SSID not seem insert fine

can you check my mod file please ?

thanks


Strange .
For trust autel tool need check ssid .

Can you calculate key data ,this autel tool away ?
If yes .........
load one key data in here .
I can check key dump away from ezs.

[peko]

here key data
thanks for your help

[brend]

here key data
thanks for your help

I mean key dump

[jaymbz]

Can the 24LC128 be R/W by connecting without desoldering?

Can one just do a straight copy over from the old cluster to the new one or does the SSID from the new cluster match it's h/w only and has to stay with the current cluster rather than be overwritten with the original cluster SSID? Thanks.

Edited: Okay it wasn't possible, tried in-circuit and it must have been reading something different - but copied old ROM over to new cluster - most functions work fine but lost speed sensor input and trip computer functions. Looks like the clusters are slightly different units (both have same part but must be a different variant - one 2007, one 2010) so there must be some software change.

2nd try - just copied miles and essid into original IC code - now it works again and speed sensor is working, trip computer returns, but fuel display is broken - there seemed to be a few differences between the old and new ROMs. I will go in search in case nobody responds here.

If anyone knows what IDs you need to copy for fuel readout that would be great. Seems to be a few serial numbers recorded in the EEPROM.

Clearly the fuel sender is still sending data as the old cluster code had a fuel display but no speedo, the new cluster code has a speedo but no fuel display. so either the source ID of the rear SAM/fuel sender has to be copied over to the new IC to marry it OR the destination ID for the fuel data is not the ESSID. Does hex at 0200, 0240, 0280 need migration directly so the rear SAM doesn't need changes to restore fuel without breaking speedo or new IC..