W639 EIS - Damaged MCU

[DeLuXe]

Hi,

I have a W639 EIS with damaged odometer MCU. Tried to read it with several programmers with no success. Mask 3K85K

I have new MCUs. I want to replace both. Is it somehow possible to write a dump made from the keys dump (other MCU) ?
Or what is the process here? To write other dump files to both MCU, renew ELV and code new key ?

Thanks for the help and tips..

Best regards,
DeLuXe

[bersch8688]

How do you read MCU?
Which Programmer have you for this Job?

[DeLuXe]

ETL, VVDI Prog, Orange 5, Xprog..

Thanks for help

Best regards,
DeLuXe

[bersch8688]

Try again with vvdi prog

[DeLuXe]

I have the MCU desoldered and have tried a lot of times.
No echo from mcu with other programmers, heating sometimes let it read but not anymore, so i think its done with that mcu to be honest.

Best regards,
DeLuXe

EDIT: Sorry, I have the original IMMO MCU, EEPROM, would that be enough if to let say having same number on EIS donor? :) If I give up the mcu exchange process :)

[bersch8688]

Which country you are coming?

Send me mcu and i read out eeprom and flash for you

[DeLuXe]

If to use new MCU's and replace them, will I need to write something to odometer mcu ?

Thanks for all the answers.

Best regards,
DeLuXe

[DeLuXe]

Hi,

I have got a donor with same matching numbers, renewed ecu, wanted to connect with Star or VVDI MB Tool but there is no OBD communications.
But with Launch I could diagnose whole car.

Anyone experienced that ?

I get error in MB star "CAL error number 5012".

No communication to EZS, Engine and so on.. Tried 2 different MB Star softwares, latest and old wich came with my MB Star diagnosis.

Best regards,
DeLuXe