04-10-2019 update:
Trying to clone Mercedes sl500 ME2.8 ecu and everything goes fine until the end when writing eeprom it gives error..
04-10-2019, 19:21 PM update:
One friend suggested: Swap eeproms. Or do it with eeprom programmer like UPA. So just clone flash with ktag. Clone ktag have this issue with that ecu. Ori works perfectly.
Another friend agreed: Absolutely right… I have done the very same car with upa and didn’t do the flash but hw and sw numbers of ecu were the same.
05-10-2019 update:
After cloning was complete I examined files before and after clone with HxD editor and mpc file was identical also was maps, then examined eeprom file and vin was written in almost the complete file was
the same except for a few scattered digits maybe 10 or so in the whole file, so wondering if this is just a
false error, haven’t been able to try ecu in car yet after clone, will report how car reacts to clone ecu….
One friend shared his experience on 08-10-2019:
Ktag 6.070 under Trasdata working like a charm on this ECU. R/W e2p/mpc/ext with no problems.
6.070, 7.020 under Ksuite never work.
Kess v2 5.017 under Ksuite 2.47 and 2.23 write good.
Car was w203 C32 AMG.
08-10-2019, I have some good news:
I have some good news, installed ecu last evening and car starts fine so this must be a false error..As I wrote in my 4th post after looking at the eeprom files all blocks that contain vin#
and immo data was written only a few hex digits at end of file were different and after more research I think those are dates and other non important information from factory writing..I’m using K-tag fw 7.020 sw2.25 version..
Question: Need desolder eeprom and read/write off the board using Ktag?
Answer:
No. I did read/write via boot mode according to pinout and ktag instructions..
