|
elRey
|
 |
« on: March 14, 2011, 12:56:09 PM »
|
|
|
Can you take a stock 1.8T bin and flash it onto a similar hardware 2.0L 8v ECU to get a 1.8T ECU?
i.e.
06A906032HS 0261207446 bin onto a 06A906032FP 0261207357 ECU
Thanks,
Rey
|
|
|
|
|
Logged
|
|
|
|
AmIdYfReAk
Full Member
Karma: +9/-0
 Offline
Posts: 129
|
|
« Reply #1 on: March 14, 2011, 02:28:28 PM »
|
|
|
I'd give it a try, As long as the hardware is the same ( Cpu, flash, etc )
Edit: Though, i would do a galleto dump of the 800, and a dump of the eeprom, and clone them to the 2.0 ecu.
|
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #2 on: March 14, 2011, 03:04:36 PM »
|
|
|
I think I will try it.
What happens if I don't clone the eeprom?
|
|
|
|
|
Logged
|
|
|
|
AmIdYfReAk
Full Member
Karma: +9/-0
Offline
Posts: 129
|
|
« Reply #3 on: March 14, 2011, 07:32:49 PM »
|
|
|
To be honest, I'm not sure.
all i know is, if you do the eeprom, along with the 800 chip... it *IS* the "old" Ecu.
Reading up on the cloning thread goes a little more in depth then i can.
|
|
|
|
|
Logged
|
|
|
|
robin
Full Member
Karma: +20/-1
Offline
Posts: 139
|
|
« Reply #4 on: March 16, 2011, 08:21:32 AM »
|
|
|
Doubt the 2.0L ECU has the N75 driver or the proper injector / spark drivers... it's a hardware limitation most likely, not software...
|
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #5 on: March 16, 2011, 09:20:47 AM »
|
|
|
injector and spark drivers are there. I've ran a 1.8T ECU in a 2.0L car. N75,N205,N249 drivers are another story. I'll compare them and see. Tho in my application I don't use any of those. |
|
|
|
« Last Edit: March 18, 2011, 11:29:04 PM by elRey »
|
Logged
|
|
|
|
|
eliotroyano
|
|
« Reply #6 on: March 18, 2011, 11:23:56 PM »
|
|
|
Can you take a stock 1.8T bin and flash it onto a similar hardware 2.0L 8v ECU to get a 1.8T ECU?
i.e.
06A906032HS 0261207446 bin onto a 06A906032FP 0261207357 ECU
Thanks,
Rey
As soon as you have the same family ECUs with it same board and at least associated and needed drivers or ICs, it can work. I have been playing with the same mix, but my case is M5.9.2 06A906018ES 2.0L 8V AEG engine ECU with a M3.8.3 06A906018CG 1.8T AGU engine flash software with sucess. |
|
|
|
« Last Edit: March 18, 2011, 11:40:44 PM by eliotroyano »
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #7 on: March 19, 2011, 01:50:26 PM »
|
|
|
Just flashed a 06A906032KR bin onto a 06A906032FN ECU with success.
Ran the car just like the KR did.
KR = 2002-2005 1.8T AWP New Beetle 4spd auto
FN = 2002 1.0L 8v AZG 5spd manual
note: both ECUs were IMMO 'matched' to the car before all this. I had the SKC code for both.
|
|
|
|
|
Logged
|
|
|
|
|
eliotroyano
|
|
« Reply #8 on: March 19, 2011, 09:36:36 PM »
|
|
|
Just flashed a 06A906032KR bin onto a 06A906032FN ECU with success.
Ran the car just like the KR did.
KR = 2002-2005 1.8T AWP New Beetle 4spd auto
FN = 2002 1.0L 8v AZG 5spd manual
note: both ECUs were IMMO 'matched' to the car before all this. I had the SKC code for both. This are good news, great friend......About the eeprom immo match is ok, but you could use the oem immo in the donor ECU to clone it completely. That way you avoid immo match and ecu dtcs that it could generate. Anyway great to read that works excellent. |
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #9 on: March 19, 2011, 09:48:35 PM »
|
|
|
I also tried three other files with mixed results.
All on the 032FN ECU:
4B0906018DA -> complete failure. Flashed fine, but no communication afterward.
06A906032LP -> flashed and communicated fine, but IMMO blocked. even though it showed correct VIN/IMMO
06A906032HS -> another complete success like 032KR. ran fine.
|
|
|
|
|
Logged
|
|
|
|
|
eliotroyano
|
|
« Reply #10 on: March 19, 2011, 10:02:51 PM »
|
|
|
I also tried three other files with mixed results.
All on the 032FN ECU:
4B0906018DA -> complete failure. Flashed fine, but no communication afterward.
06A906032LP -> flashed and communicated fine, but IMMO blocked. even though it showed correct VIN/IMMO
06A906032HS -> another complete success like 032KR. ran fine.
Friend remember that you need the same board architecture, ICs and Motronic family to do a cross-flash. About the serial eeprom data aka "immo" it should match the flash eeprom to avoid issues. |
|
|
|
|
Logged
|
|
|
|
|
eliotroyano
|
|
« Reply #11 on: March 19, 2011, 10:25:00 PM »
|
|
|
I also tried three other files with mixed results.
All on the 032FN ECU:
4B0906018DA -> complete failure. Flashed fine, but no communication afterward.
06A906032LP -> flashed and communicated fine, but IMMO blocked. even though it showed correct VIN/IMMO
06A906032HS -> another complete success like 032KR. ran fine.
My advice is to use a flash+serial eeprom data match to avoid issues and after that you could do the ecu immo match, that is the case for 06A906032xxxx family. The immo data configuration could change between different flash software. The 4B0906018DA could use a different data architecture in a different eeprom type (boot sector type "B" or "T") and it seems to not been working. I am not sure about that but can explain you the total failure after reflash. |
|
|
|
« Last Edit: March 19, 2011, 10:27:04 PM by eliotroyano »
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #12 on: March 23, 2011, 03:30:56 PM »
|
|
|
I was going of this post in a different thread: Reprogramming the EEPROM won't help. The immo in the car is still the same and the data in the eeprom perfectly matches with the immo (as it did before). The two images must be made for different immo versions. The original one matches with the instrument clusters immo version, but the new image uses a different immo version and therefore can't talk to the immo in the car. The immo data in the ME7's eeprom is stored always at the same places, independent of the used immo version. You can only disable the immo to run the new image. Or if you are a really good hacker, you can replace all immo functions in the new image with the correct ones for your car  . |
|
|
|
|
Logged
|
|
|
|
|
eliotroyano
|
|
« Reply #13 on: March 23, 2011, 03:55:03 PM »
|
|
|
I was going of this post in a different thread: Reprogramming the EEPROM won't help. The immo in the car is still the same and the data in the eeprom perfectly matches with the immo (as it did before). The two images must be made for different immo versions. The original one matches with the instrument clusters immo version, but the new image uses a different immo version and therefore can't talk to the immo in the car. The immo data in the ME7's eeprom is stored always at the same places, independent of the used immo version. You can only disable the immo to run the new image. Or if you are a really good hacker, you can replace all immo functions in the new image with the correct ones for your car . That is understandable friend. Using flash+eeprom data match you avoid issues about ECU operation, but it relationship with cluster/immo is another story. That is the reason that I suggest you to use that ecu data match (flash+eeprom) and after that try to sincronize ECU-Cluster-Immo. It is true that immo data in the ME7's eeprom is stored always at the same places, independent of the used immo version. It is the same case for other Motronic families. But If cluster doesn't accept the ECU (immo related issues) the only option is immo disable or bypass. |
|
|
|
|
Logged
|
|
|
|
learning1
Newbie
Karma: +3/-0
Offline
Posts: 9
|
|
« Reply #14 on: April 08, 2011, 11:17:36 AM »
|
|
|
FOR ME7.1/7.5 (7.5 contians immo on/off data but no car specific) 7.1 car specific.
All ecu are the same hardware.
FOR ME 7.5 the end chip 24C04 is not required to be copied from original but a good idea.
FOR ME 7.1x required copy of 35080/5P08
Desolder from the donor ecu if no programmer 8 pins and swap.
Pay attention to Flash size of FLASH
ECU's coming with 400BB are 512k (4 meg)
ECU with 800bb are 1mb (8meg)
AM29F800 ECU can take 400bb IC often.
AM29400 ECU does not have the function to support 800bb in the processor.
There are some other coding issues at times.
Most recommended is to use the original ECU and make your MAP changes with the original file. Adjust the scaling in the FLASH for any parts like MAF/injectors changed.
1.8T has differences like Variable CAM timing and boost depending on engine code.
Don't change software unless you change the motor.
Better to re-map for the motor properly.
Wrong ECU Flash will cause damage to the motor guaranteed.
Always log your motor after reflash.
|
|
|
|
« Last Edit: April 12, 2011, 04:01:20 PM by Tony@NefMoto »
|
Logged
|
|
|
|
|
