Title: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 24, 2014, 09:25:48 AM Hi.
I've taken one extra ecu to play with so I was wondering if it is possible to do the following: 1. Read my ECU flash 2. Read my ECU eeprom (immo) 3. Write all this on the new ecu. Basically I want to do a clone of my car ecu. Thanks! Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on September 25, 2014, 05:54:30 AM There are different hardware versiones of the ME7.3.1. The most obvious is that the 4-cyl ECUs don't have outputs for a 6-cyl engine, but there might be other differences as well. I did try to put the FLASH and EEPROM from a GTA on a 4-cyl ME7.3.1. Car did start, but naturally only ran on four cylinders.
A straight clone might work. You can also try to make the ECU virgin. I've just written a small paper on how to "virginize" the ME7.3.1. Seems to work alright when I test it on the bench, and did work with the GTA/4-cyl test as mentioned, but it would be interesting if more people did test it. I attach the PDF with the guide. Please report back your results, and also report if anything is wrong in the guide. Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 25, 2014, 07:42:37 AM The spare ECU came from 2.0ts engine. My car is 1.6ts. So everything should be the same except for one additional driver that 2.0 ecu should have to control the variable length intake.
I'll go trough the guide and try to make a virgin ecu. Will let you know the results. Tnx! Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 25, 2014, 12:46:09 PM I've had a look at the guide. It is pretty clear, however I have one question. How do you know the memory type of the eeprom?
When I was downloading the eeprom I selected 95040 and got a successful read. It worked on both ECUs. But when I compare the hex with the one in the manual it looks different. I've attached one bin so you can have a look. Title: Re: Cloning ECUs ME7.3.1 Post by: ddillenger on September 25, 2014, 12:47:59 PM I've had a look at the guide. It is pretty clear, however I have one question. How do you know the memory type of the eeprom? When I was downloading the eeprom I selected 95040 and got a successful read. It worked on both ECUs. But when I compare the hex with the one in the manual it looks different. I've attached one bin so you can have a look. Open the ecu. Read the numbers on the eeprom. Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on September 25, 2014, 01:16:07 PM I've had a look at the guide. It is pretty clear, however I have one question. How do you know the memory type of the eeprom? When I was downloading the eeprom I selected 95040 and got a successful read. It worked on both ECUs. But when I compare the hex with the one in the manual it looks different. I've attached one bin so you can have a look. I used trial and error. Read as 95080 and you will find that there's more information in the EEPROM past address 0200h. Reading and writing as 95080 seems to do the job fine. ME7.3.1 is a hybrid ECU. I tried identifying the bare dye chips on the ECU hybrid under a microscope, but I couldn't find any readable markings. The protective silicon coating blurs the picture, and the microscope I have access to is limited in magnification. If anyone has better equipment and can identify the bare dye chips, any help is most welcome! Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 25, 2014, 02:21:07 PM I used trial and error. Read as 95080 and you will find that there's more information in the EEPROM past address 0200h. Reading and writing as 95080 seems to do the job fine. ME7.3.1 is a hybrid ECU. I tried identifying the bare dye chips on the ECU hybrid under a microscope, but I couldn't find any readable markings. The protective silicon coating blurs the picture, and the microscope I have access to is limited in magnification. If anyone has better equipment and can identify the bare dye chips, any help is most welcome! I tried reading all formats. I agree, there are more data after 0200h. When you read as 95P08, all the data after 0200h are filled with FF. When you read as 95080 you get some data after 0200h. When you read as 95160 you get exactly double of 95080. So I'd say looks like 95080 :) I've compared it to the file in the manual. The virgin line in this immo looks like only for address 0068h. And the checksum calculation works for this line. The line with 0058h doesn't compute. I've attached the bin so you can have a look. Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on September 26, 2014, 02:07:25 AM I tried reading all formats. I agree, there are more data after 0200h. When you read as 95P08, all the data after 0200h are filled with FF. When you read as 95080 you get some data after 0200h. When you read as 95160 you get exactly double of 95080. So I'd say looks like 95080 :) I've compared it to the file in the manual. The virgin line in this immo looks like only for address 0068h. And the checksum calculation works for this line. The line with 0058h doesn't compute. I've attached the bin so you can have a look. That's strange! All the EEPROMs I have read from ME7.3.1 have had the two duplicated identical lines. Was it the same result on both your ECUs? Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 26, 2014, 02:15:09 AM I didn't check the second ECU yet. I've just read the spare one. I can check the original one today when I get home. I'll let you know.
Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 26, 2014, 09:32:22 AM Same with the other ECU...
Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on September 26, 2014, 11:07:04 AM Same with the other ECU... Really strange. ??? I'll put together all the ME7.3.1 eeprom dumps I have as a reference and post them. Don't have the time until after the weekend though. Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on September 29, 2014, 01:20:12 AM Here's all of the eeprom dumps I have at the moment. They all have the duplicated lines, and two of the dumps wasn't read me, but from two different Alfisti.
Neno-ri, did you use the exactly same command line as in my guide? Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 29, 2014, 01:31:30 AM Here's all of the eeprom dumps I have at the moment. They all have the duplicated lines, and two of the dumps wasn't read me, but from two different Alfisti. Neno-ri, did you use the exactly same command line as in my guide? I've used exactly the same command line. I have no idea we have this difference. Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on September 29, 2014, 01:39:08 AM I've used exactly the same command line. I have no idea we have this difference. It might be a difference in the ECUs . Your two ECUs have different P/N from the ones I have, so we can't compare them. It will be interesting to here if you succeed with the cloning. Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 29, 2014, 01:41:10 AM It might be a difference in the ECUs . Your two ECUs have different P/N from the ones I have, so we can't compare them. It will be interesting to here if you succeed with the cloning. Yesterday I finalized the cloning. Today or tomorrow I will try the ECU on the car. Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 29, 2014, 12:42:28 PM I tried the clone today. Works like a charm :)
No immo errors, nothing. Re-calibrated the throttle and started the car without and problems or errors. Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on September 29, 2014, 12:52:09 PM I tried the clone today. Works like a charm :) No immo errors, nothing. Re-calibrated the throttle and started the car without and problems or errors. Great news! Did you just clone the eeprom, or did you try the virgin mod? ECU/SW numbers was: 0261206707-1277356512 and 0261206715-1277356511, right? Title: Re: Cloning ECUs ME7.3.1 Post by: Neno-ri on September 29, 2014, 01:03:51 PM Great news! Did you just clone the eeprom, or did you try the virgin mod? ECU/SW numbers was: 0261206707-1277356512 and 0261206715-1277356511, right? I just cloned them. Virgin mod will be next :). Correct. Those are the numbers. Title: Re: Cloning ECUs ME7.3.1 Post by: certik on January 22, 2015, 04:21:44 PM That's strange! All the EEPROMs I have read from ME7.3.1 have had the two duplicated identical lines. Was it the same result on both your ECUs? Hi redtop, I have ME7.3.1 too, and in my dump aren't duplicated lines too. It looks like Neno-ri's dumps. I attach it for you. If I can have one question: I tryed download ROM image from my unit via Galletto in bootmode. It was downloaded successfully, but it looks totally different when I compare it with dumps from other types ECU with this kind of processor. Missing the interrupt vector table on start of file for example. But in some places I can see readable texts, so it can't look as garbage. It is anything wrong on my side, or it is normal in this unit? Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on January 23, 2015, 02:20:31 AM A bit off topic! ;)
I take it it's from a Lancia Thesis 3.2 (0261208118-1037368765) ? I don't know anything about the structure of the software, but there are some good info about the Alfa 147 3.2 here: http://www.ecuconnections.com/forum/viewtopic.php?f=25&t=11594 Maybe it's useful for you? I attach a couple of other dumps from Alfa 3.2 with the ME7.3.1 so you can compare. (BTW are you Alfachip in other forums?) Title: Re: Cloning ECUs ME7.3.1 Post by: certik on January 23, 2015, 10:00:17 AM Yes, you are right, its as you say. Lancia Thesis 3.2.
I am sorry, if it's offtopic. It's the same ECU, so I sended it for info, because it haven't duplicated lines and have the same structure as Neno-ri dumps. Thanks for yours dumps. Looks like my dump. (The AR166 zip file is broken). I am not Alfachip. All my nicks on every forums ended with "ertik" (czertik, e-certik, ecertik...). Title: Re: Cloning ECUs ME7.3.1 Post by: certik on January 23, 2015, 10:08:43 AM And for info, the reinit of virgin ECU work fine. I tried it on Thesis, I changed the ECU for another (i have two spare cars) and car normally started.
Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on January 23, 2015, 01:19:47 PM And for info, the reinit of virgin ECU work fine. I tried it on Thesis, I changed the ECU for another (i have two spare cars) and car normally started. OK, someone was asking for an immo-off file for this ECU in other forums. I thought it might be you. You just cloned the eeprom, and that did the trick? (The 166 file works fine here, I upload it again just for reference.) Title: Re: Cloning ECUs ME7.3.1 Post by: certik on January 23, 2015, 01:57:55 PM Thank you. I can download the file, but I can't unrar it. Maybee I have old version of rar plugin. I use totalcommander.
I didn't clone eeprom, because i haven't original one. But clonning working fine, if you clone booth FLASH and EEPROM. My solution do not disable imo. Imo is still active. It (only :-) ) cause le-learn the ECU from bodycomputer (BC) (because i didn't have other source. My original ECU was broken). After this the ECU working like original or cloned one. It have original IDs (I mean IDs printed on label), but fully cooperate with original IMO and BC. But without clone. :-) I don't know, if only on Thesis, it can work in any car with BC by my opinion. Title: Re: Cloning ECUs ME7.3.1 Post by: alfachips on January 25, 2015, 08:37:33 AM Hello friends. I am Alfachips.
I did a clone ecu. I have taken ecu from 147 1.6L with 105 hp and I put on 156 1.8L and the car started normally. Cetrik, can you attach the original flash file from Lancia Thesis 3200 ? Title: Re: Cloning ECUs ME7.3.1 Post by: certik on January 25, 2015, 09:00:38 AM Redtop: I used winrar and i successfully extracted the AR166 file. ;-)
Alfachips: It look like not complete dump, but the same structure as some other I downloaded. Here it is: Title: Re: Cloning ECUs ME7.3.1 Post by: alfachips on January 25, 2015, 11:50:01 AM Thank you Certik.
Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on February 10, 2015, 08:29:26 AM so
if i clone eeprom from one ecu (me 7.3.1) to another (flash on both ecu's is different) car would start or not? thx Title: Re: Cloning ECUs ME7.3.1 Post by: certik on February 10, 2015, 09:01:00 AM In this case, when the flash are different, is unsafe clone whole eeprom. It can work, it can have some unpredictible errors/problems, it can stop working.
It depend on flash program. Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on February 10, 2015, 09:53:43 AM flash different because one ecu from automatic transmission another from manual
engine type and all over are same what do you think about it? Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on February 10, 2015, 11:30:36 AM flash different because one ecu from automatic transmission another from manual engine type and all over are same what do you think about it? You can try to make it virgin as in the instruction attached to the second posting in this thread. Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on February 10, 2015, 11:49:39 AM i download it last night)
will try do it thx Title: Re: Cloning ECUs ME7.3.1 Post by: certik on February 12, 2015, 01:20:45 PM Make it virgin as redtop say is safe way. It will work. ;-)
Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 02, 2015, 03:08:01 PM I do not understand how to calculate chechksum ???
Who can help? thank you Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 02, 2015, 05:50:11 PM original eeprom in file
Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on March 03, 2015, 12:32:40 AM I do not understand how to calculate chechksum ??? Who can help? thank you Seems like you have calculated the checksum correct in your file! (F9DA) Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 03, 2015, 08:29:38 AM redtop you are the best!!
Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 04, 2015, 12:00:22 PM write eeprom to ecu
car dont start no engine error message Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on March 04, 2015, 12:50:11 PM write eeprom to ecu car dont start no engine error message you changed gearbox from Selespeed to manual, right? Maybe it's the wrong flash file for your configuration? Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 04, 2015, 03:32:57 PM you changed gearbox from Selespeed to manual, right? Maybe it's the wrong flash file for your configuration? yes, change. But this eeprom (from donor ecu) work fine with donor body ecu installed on my car, now i want use my old body ecu with donor engine ecu . Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on March 05, 2015, 12:15:12 AM It was an Alfa 147? Maybe you need to do a "proxy alignment" in your body computer?
Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 05, 2015, 06:10:48 AM yes,i do it first)
seems like there is no gasoline, but gasoline is ok) upd it was a bad mass on motor ecu when i tried now all perfect!! Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 11, 2015, 08:41:45 AM one more ecu
attached original eeprom and virgin and there is immo error after virgin thx Title: Re: Cloning ECUs ME7.3.1 Post by: redtop on March 18, 2015, 07:44:57 AM As far as I know you got the checksum right. I have no idea why it doesn't work.
Title: Re: Cloning ECUs ME7.3.1 Post by: DimDim on March 18, 2015, 08:14:50 AM As far as I know you got the checksum right. I have no idea why it doesn't work. first ecu work right second ecu does not work i tried third and fourth ecu and 'virgin' work good Title: Re: Cloning ECUs ME7.3.1 Post by: Kele on May 15, 2016, 10:30:10 AM Can someone check if is this eeprom from me7.3.1 0261206716 virgin?
This dump is readed from ecu that not been virgin.I dont know how in lines 058h and 068h is DAh instead 25h? Title: Re: Cloning ECUs ME7.3.1 Post by: DieselManiac on July 21, 2019, 08:58:19 AM I'm looking for a eeprom dump of a 0261207967 Alfa 147 GTA ECU.
Can someone help me with this, not the engine MAP. Title: Re: Cloning ECUs ME7.3.1 Post by: bonzy on October 25, 2019, 04:34:38 PM I need help, I'm looking for a eeprom dump of a 0261206707 Alfa 147 2.0
Title: Re: Cloning ECUs ME7.3.1 Post by: fluke9 on October 26, 2019, 08:18:36 AM I need help, I'm looking for a eeprom dump of a 0261206707 Alfa 147 2.0 For what exactly ? You can just fille the EEPROM with 0xFF and the ECU will recreate the content after ignition is switched off in the afterrun. Afterwards the ECU is virgin and will pair with the IMMO again. If you remove the K-line wire it will stay virgin forever, but the code lamp is on as the Body computer will detect no communication. Title: Re: Cloning ECUs ME7.3.1 Post by: bonzy on October 28, 2019, 01:46:50 PM For what exactly ? You can just fille the EEPROM with 0xFF and the ECU will recreate the content after ignition is switched off in the afterrun. Afterwards the ECU is virgin and will pair with the IMMO again. If you remove the K-line wire it will stay virgin forever, but the code lamp is on as the Body computer will detect no communication. Hi, I needed to clone the 2.0 ecu to the 1.6 after the engine change. But I managed to find it and it's all right. It works. Title: Re: Cloning ECUs ME7.3.1 Post by: bonzy on October 28, 2019, 01:54:15 PM Hi, I needed to clone the 2.0 ecu to the 1.6 after the engine change. But I managed to find it and it's all right. It works. Exactly I needed the eeprom of the alfa romeo gt 1.8 twin spark (0261208725-1037370360) because the engine is 1.8, I found the flash file but I miss the eeprom file. But until I find it I have to be satisfied with this.Title: Re: Cloning ECUs ME7.3.1 Post by: fluke9 on October 28, 2019, 02:05:11 PM Exactly I needed the eeprom of the alfa romeo gt 1.8 twin spark (0261208725-1037370360) because the engine is 1.8, I found the flash file but I miss the eeprom file. But until I find it I have to be satisfied with this. You dont need the EEPROM data at all. Flash the bin matching your engine to the ECU (almost all 4 CYL ME7.3.1 are the same hardware). Then write a file created in the hex editor with all FF to the EEPROM (CSpin4.7). Turn off ignition, wait ~10 seconds, turn on ignition. The EEPROM has now been recreated by the ECU, as this is exactly what happens in factory. You then have a "brand new" virgin ECU. Title: Re: Cloning ECUs ME7.3.1 Post by: bonzy on October 28, 2019, 03:06:35 PM You dont need the EEPROM data at all. I've just tried it but the machine doesn't start, or at least it starts but has errors and turns off. I tried to read the eprom after this and the file was encoded up to a certain point then there are all "00". I attach image.Flash the bin matching your engine to the ECU (almost all 4 CYL ME7.3.1 are the same hardware). Then write a file created in the hex editor with all FF to the EEPROM (CSpin4.7). Turn off ignition, wait ~10 seconds, turn on ignition. The EEPROM has now been recreated by the ECU, as this is exactly what happens in factory. You then have a "brand new" virgin ECU. Title: Re: Cloning ECUs ME7.3.1 Post by: bonzy on October 28, 2019, 03:53:46 PM You dont need the EEPROM data at all. Can you check if I did it right?Flash the bin matching your engine to the ECU (almost all 4 CYL ME7.3.1 are the same hardware). Then write a file created in the hex editor with all FF to the EEPROM (CSpin4.7). Turn off ignition, wait ~10 seconds, turn on ignition. The EEPROM has now been recreated by the ECU, as this is exactly what happens in factory. You then have a "brand new" virgin ECU. Title: Re: Cloning ECUs ME7.3.1 Post by: fluke9 on October 29, 2019, 02:53:20 AM Can you check if I did it right? Eeprom was recreated correctly, the empty sections are normal (they are unused), but they have the correct checksum to the right. Also the ECU already paired itself with the IMMO correctly which you can see on the 0x25 bytes (which are after or before the immo code, dont remember which way round) on page 5&6. If its unpaired its either 0xDA or empty. Did you delete all the error codes and try to start again ? If it does not work it is more like hardware around your ECU than the ECU itself, everything looks totally fine. If it starts and then turns of it is NOT the immo, if the immo is active it will never start for these ecus as there is NO injection at all then. Title: Re: Cloning ECUs ME7.3.1 Post by: bonzy on October 29, 2019, 03:13:18 AM Eeprom was recreated correctly, the empty sections are normal (they are unused), but they have the correct checksum to the right. Also the ECU already paired itself with the IMMO correctly which you can see on the 0x25 bytes (which are after or before the immo code, dont remember which way round) on page 5&6. If its unpaired its either 0xDA or empty. Did you delete all the error codes and try to start again ? If it does not work it is more like hardware around your ECU than the ECU itself, everything looks totally fine. If it starts and then turns of it is NOT the immo, if the immo is active it will never start for these ecus as there is NO injection at all then. I made a diagnosis and the program did not give errors. But it appears in the instrument panel. I also tried to load this eeprom virgin on the 2.0 ecu that normally works and that doesn't work either. Then I reloaded the eeprom of 2.0 and it works again. |