[Martin1234]

can someone check this file please,
 we are having problems after reading from original and writing to a doner eis , 

all works but  it has lost 2 ecus on the can link, but put the old original back on the car and the ecus are present when reading with das,

maybe the eis unit is at fault i believe its another  part of the can link,

  the original key randomly didnt turn ( 4j74y chip faulty r2)
the whole reason for doing the job, thanks

[rs@chip]

can someone check this file please,
 we are having problems after reading from original and writing to a doner eis , 

all works but  it has lost 2 ecus on the can link, but put the old original back on the car and the ecus are present when reading with das,

maybe the eis unit is at fault i believe its another  part of the can link,

  the original key randomly didnt turn ( 4j74y chip faulty r2)
the whole reason for doing the job, thanks

Did you try reprogram eis unit obd after you made clone?eep looks ok not sure for one hash error 2 key

[Martin1234]

reprogram ? sorry ? the car all works , drives , locks unlocks on th efob, but roof ecu and a couple of others not seen when diagnostic with das ,,

[Ecutech]

I think you have only cloned the eeprom. The config is stored on another chip. Need to configure now with xentry.

[Martin1234]

I think you have only cloned the eeprom. The config is stored on another chip. Need to configure now with xentry.

no i did pull out of both chips the eeproms and the flash files ,

---

i can just pull both files out again and reload both used eis chips again its not a problem

[Ecutech]

Eis cloning is relatively straightforward. If you have done it correctly and have ecus offline afterwards then suspect hardware problem. Id the hw numbers the same?

[Martin1234]

hi ecutech it shows a hahs error, also i am doing it all again tomorrow, ill pull both files out of both chips R1 and R2 then rewrite them to the used one again, if not i may have to just change over the (R2) on from board to board