NefMoto

I have just bought an ECU the same as mine (06A906032HN) so I can work on a switch-able map setup without risking my original HW.  ;D

Ideally I would like to have the immobiliser working with the new ECU so I have a couple of questions.

Is it even possible?

If I read the serial EEPROM and write to the new ECU's device, will that do it?
Are the key transponder codes also stored in the ECU?

I've dumped the EEPROM, but this thread...
http://www.nefariousmotorsports.com/forum/index.php?topic=89.0title=
suggests that some areas may not have read (protected?). The dumped file is 512bytes which is a full 4 Kbit as per the M95040 but the last 166 bytes are 00 so could be this was a protected area?

I don't mind opening the new ECU but I'd rather not violate the original if I can help it.

Any comments gratefully received.

This is something I will be trying very soon myself. Although I'm going one step further and am buying an ECU with a different suffix at the end - hope it will work!

I will crack the case of the used ecu I am buying and dump the eeprom with a programmer and compare to a k-line dump.  When done I will report back.

That's a good point actually. I can also compare the dumps from K-line vs SPI on my new ECU, cheers.

Yes, just copy eeprom to make ecus interchangeable (clone) or you can adapt the ecu with rosstech procedure if you dont want to desolder, but being your car immo3 you will need both pin codes. The third option would be immo defeat the new ecu.

In volkswagen cars immo is integrated with instrument cluster and eeprom can be read through diagnostics port.

I understand thank you.

I wont have the SKC's for the new ECU so cloning is the way to go. Hopefully the EEPROM dump I have is 100%. I'll post back once I've verified it.

Thanks.

For the sake of keeping the thread complete, here's the Vag-com process http://www.ross-tech.com/vag-com/cars/Immo3-ecu-swapping.html

Hmm,

Plugged the new ECU (as I received it) to dump the flash prior to reprogramming / cloning, but it wont read as the "preconditions are not met" and it has to be installed in the car (which it is).

Is this because the immo3 is not yet matched to the instrument cluster and is therefore preventing the flash read?

I've attached the log from the session fyi.

Cheers.

yep, if the ecu is not correctly authentifying with the immo it will not allow to turn on a
programming session for reading or writing the flash.
If you turn off ignition and then try to start the programming session, there is a kind of endless loop in the ecu, giving a responsePending answer forever, so also no success.
You first have to copy the contents of the eeprom from your working ECU  into the new ECU, then reading/writing flash should work.

Thanks for attaching the log file. I was never 100% sure what that specific precondition requirement was, so I called it "ECU must be installed in car". But if the ECU was installed in the car without the immobilizer paired, then maybe the precondition should actually be "Immobilizer: ECU is not authenticated with Instrument Cluster".

I recently had this same problem with a VW 2.8l VR6 ECU - part # 022906032CS. I was able to read the ECU on the bench with Tony's software by removing the immobilizer. My ECU is Motronic 7.1.1 and only requires 4 bytes to be changed in the serial eeprom. I am not sure if they are all the same or not.

I also read the eeprom using Vag K+CAN and a proper programmer, the dumps are quite different. The Vag K+CAN dump is enough to see the immobilizer settings, IMMO ID, VIN and PIN but it is incomplete. So a 100% clone should really done by reading/writing the serial eeprom.

Oh,

That's a shame but I'm not sure it's the same situation with the ME7.5. Were both EEPROM dumps the correct size?

They are different sizes. The Vag K+CAN eeprom dump was clearly taken from ram as some stuff is duplicated in the original eeprom that isn't in the Vag K+CAN dump.

Vag K+CAN also offers a write feature, I have tried it several times but no data has ever been written to the eeprom.

So I was successful in cloning my ME7.1.1 ECU today. I used an ECU from a 2.8 litre VR6 but programmed in the entire flash and eeprom images from my original 3.2 litre ECU. The eeprom was read/written using an UPA USB programmer. The flash was written by Galletto as Tony's program seems to not like R32 ECUs.
Even with Galletto I had a "change speed" error when trying to write the flash but it was fixed when I bypassed the immobilizer. After flashing the ECU I re-enabled it.

After I verified the cloned ECU worked with the factory flash I flashed in a tuned R32 file. I am not sure who did the file but it was taken from the ECU of a crashed R32. I can't really say if its made any difference yet, the roads were wet with a little snow tonight and a tune can only offer 10 to 20 HP max.

So cloning an ECU is no problem, and can work even with slightly different part numbers if the hardware is the same.

btw, if anyone wants to take a look at the tuned file versus the stock file let me know and I'll post or PM the images.

you can get the 5 digit pin codes from the 95040 read.

Could you detail how to identify the code from the dump? Is this the usual 4 digit plus leading 0 that is readable via vag commander?

I'll clone if I can, but this'd be a good backup plan. At the moment the snow is stopping me getting anything useful done which is frustrating as hell.


Thanks.

yes, 4 digit plus leading 0. 0x32 and 0x33, swap hex bytes, so format is 3332, convert to decimal.

Ooh so it is, Thank you.

I'm looking to do this also.  Same engne; same ECU.  I also bought a "spare" to mess around with.  I'd like to see the files.  The ECU that came with the engine supposed to have APR tune.  I'm interested to see the difference between this and the stock one I just bought.

So if I'm following, you wrote the stock 3.2 files to a 2.8 ECU (the 032CS box, the same one I have), then flashed it with someones unknown tune?  Interesting.  Did you happen to check to see how similar they are internally?  It might be interesting to seek the changes between stock 3.2 and unknown tune and stock 2.8 and APR tune?  I wonder how the tunes might compare?  This is the ECU you wrote to, correct?

(http://i1113.photobucket.com/albums/k514/ssgacc/2002_Bora_28_24V_ME711.jpg?t=1293775274)

Thanks, Jim

This is great. I'm looking to write an mbox file to an abox for a b5 s4. If anyone has done this with success plese chime in. Only difference i know of is the maf and esp coding, so the hardware should be the same

Also I'm not sure if I put it into the car to use to tony's software will i need to recode my instrument cluster temporarily for it to boot properly before flashing.
I'm still trying to wrap my head around some of these concepts, so please excuse me if this wouldn't apply to what I'm trying to do.
*edit* I found the correct thread that covers this specifically, and it seems that you would have change the coding in eeprom to keep esp functioning, but apparently esp can be turned on and off via vag com.

You can flash an M-box file to an A-box ECU without trouble. If you have an "A-box car" (2000 6speed) then you will need to do the MAF conversion and also change the instrument cluster code with Vag Com.

The car will start and run without changing the instrument cluster code but you will get a CEL.

^^^ thanks... i have a j box car(2001 tip) which had an Lbox running in it, which i'm almost done converting to a manual.  I was just more concerned with putting an a box in and having some error from my cluster being coded for m that would prevent me from flashing... you cleared that up for me though so no worries.

As a tip if the ECUs comes from the same family (uses the same basic board, drivers, processor and connector pinout or wiring), with just copy the flash and eeprom (or adapt the ECU) you are done. I have playing with old M383 and M592 ecus and both uses the same board with only one or two drivers differences, basically CAN communications and 2nd cat O2 driver.

Friend sorry to ask but that method only work with ME7.5.x ECUs?

This information is stored in the same way for ME7.1 and ME7.5.

Ok thanks friends, I ask because I playing around with some old ECUs, M383 and M592, and I thought that pin can be found the same way.

hey i know this is an older thread, but i was wonderig if you ever got your situation solved, seeing how i have a similar problem with a secondary ecu for my rs6........any guidance would be appreciated...thanks

You can use argdubs tool to read/write the ECU in bootmode. You will have to specify the CSpin though for write.

Read the eeprom programmer sticky.

I haven't opened my ECU yet, but I think of cloning it. Just for safety reasons. So the question is: will it be possible to make a clone from 8e0909518AS (going to buy) for 8e0909518AF (using) ecu?
Different product numbers means different hardware. Is it always true?

Those ecus are compatible.

Many sorries to all, i wrote the number wrong. Going to buy 8e0909518AK. Is it compatible too for my 518AF? Sorry again.

P.S. Thanks a lot for reply

few mins later: OMG, Found here http://nefariousmotorsports.com/forum/index.php?;topic=6011.0 . Thanks a lot again.