Coding the W204 Instrument Cluster with Vediamo

[B0bby92]

A day ago I swapped the ECU, EIS and ESZ on my W204 with ones from another car. Now my car starts and drives. I configured the ESP module by loading the correct VIN into it using Xentry. Now I have problems with the instrument cluster, the total mileage is shown as (- - - - -). I have Vediamo and Xentry downloaded from this forum. I need help repairing the IC. I am using Openport 2.0 Tactrix HQ copy as hardware. Can anyone tell me how to fix/sync my mileage? Also I know I need to copy the SSID from the EIS but I don't know how to find it and do that.
Any help would be greatly appreciated.

 

[mattehardware]

I think it is impossible to do this job with OP. You will need a programmer for the EEPROM chip, extract the file (unsolder and resolder or clip) and set the EEPROM file to 0.00 (KM), after that you need to add the SSID from the EIS to the correct section and reflash the IC. This procedure can be bypassed by using a CAN filter after IC and writing the mileage directly to IC with a suitable tool.

 

[B0bby92]

Wow, that sounds too complicated for me. Anyway, I wonder how MBTools allows these mileage adjustments via Openport.

 

[mattehardware]

I think the method involving the communication error between EZS and IC works like this: the trick is to set 1.6 million kilometers (I don't remember the exact value) on the EZS. This creates a communication error with the IC, and after that you can use Vediamo to set another mileage on the IC. However, in my opinion, this is a wrong solution. It's just a trick, and you will always have a permanent error in the EZS when using Xentry or other diagnostics. The real solution is to work with the EEPROM or CAN filter on this car.

 

[w204fan]

I am also interested in upgrading my 2009 W204 instrument cluster to the facelift.

So far I understand:
1. Choose the correct cluster. Petrol and diesel clusters are different.
2. Cluster EEPROM has 8 contacts, so programmers are cheap and readily available.
3. Read both EEPROMs with a programmer, you may not need to desolder. I have had success resetting various EEPROMs without desoldering, although I guess it depends on the circuit.
4. You need to get the SSID from the old EEPROM. The SSID is the first four bytes of address 0x040.
5. Set the value to 0 km and replace the SSID in the new EEPROM.
6. Flash EEPROM on the new cluster.

It's not clear yet:

1. Where in EEPROM are km/miles stored?
2. After changing and reflashing these values, do I need to perform any additional actions with Vediamo or Xentry?

 

[vlad0]

Post EEPROM dump from original cluster and EEPROM from donor cluster, I can change SSID for you and set 0 for mileage on dashboard, kilometers are synced with EZS on first ignition on.

 

[B0bby92]

I'll check how to do it. I'm afraid I'm not that advanced. Do I need special technology or will my Openport 2 work?

 

[mattehardware]

You can't read EEPROM with OpenPort. (With OP you can write kilometers to IC, but you can't read EEPROM)... To read and write EEPROM you need a programmer (search on Internet and you will find it), after all you have our user who can create file to write for you... so work on it.

 

[B0bby92]

Will Scanmatik 2.0 clone work?

 

[mattehardware]

No, this operation will be done only when working with EEPROM. So you don't need another VCI, but an EEPROM reader. For working with Vediamo you can use OP, Scanmatik or something else.