shop.foreman
2024-05-02T20:02:17Z
Attempting to change the ISN of a MEVD17.2.2 that was installed in an originally MEVD17.2.7 vehicle.
The ISN manager in Autohex fails to load.
Given the difference in modules, I do not believe the Hexprog II will clone this module either with their differences.

Is there a way to make this MEVD17.2.2 DME work in a MEVD17.2.7 vehicle?
Sponsor

Start ECU Repairing, ECU Cloning, and Chip Tuning today, all from an incredible price of just USD 385.00.

No annual fees, no extra charges: You pay only when you have a job.

Visit Hexprog II page

sixcode
2024-05-03T06:14:43Z
short answer is no so you can stop and get the same ecu as the original one to get this to work
cloning can be an option, but there are still HW differences so probably you also need to update the software
shop.foreman
2024-05-03T20:50:55Z
Was able to perform this task by cloning the internal EEPROM using the file from the 17.2.7 loaded onto the 17.2.2
Vehicle started right up but had a coding fault. Performed coding of the DME and vehicle now functions normally.