I should also add that I have some hardware arriving tommorrow: 1) Galletto V54 clone 2) VAG-ECU tool that should give OBD access to the 95040 memory and EEPROM contents 3) VAG-TACHO and 4) blank transponder chips (just in case I ever have to re-program any keys).

So hopefully that should allow me to do an in-car re-programming of the new 559E ECU that will arrive on Monday without having to go through the whole bench flash / bootmode routine :p

Another question I had that really didn't a confirmed answer was this: Which pins require 12V to the harness?

Based on this picture I got on this site, I ran power to pins 3, 21 and 62



However one of the early responses in this thread suggested that the way I had it set up was incorrect. 

So just to be clear, which pins require power?

Well, consistent with the rest of my life, I tend to learn my lessons the hard way lol.

Fortunately, whenever I do, I end up taking every opportunity to learn what I did wrong along the way, so it works out better in the end. It's just kind of frustrating to get there sometimes


As well, I want to clear up a few points on getting the immobilizer to work with the new ECU.

Now, I can advise that I've used argdub's tool to read and save my ECU's original 95040 coding

Now, can I just transfer that my stock ECU's 95040 read directly to the new ECU, plug it in and go?

Unfortunately, since my old ECU had a reflash on it, I can't completely clone the new ECU with both the EEPROM read and the 95040 from my old ECU. Only the 95040 read is any good.

With that in mind, will there be some other coding stored elsewhere in the new ECU (i.e. EEPROM contents or otherwise) that would conflict with my old ECU's 95040 coding?

In that case should I use the 'immo off' file that argdub posted?

Now, in argdub's immo off file, when I open it in a hex editor, I see that the VIN number and the cluster coding is represented by a bunch of XXXXXXXXXX in the sidebar (red circle). Am I correct in assuming that I transfer the VIN and cluster info from my original ECU (yellow circle) to those areas? Also, what about the info in the blue areas, does it need to be transferred as well?

Or do I just use the 'immo off' file as-is?


Finally, am I correct in assuming that if I do have to insert any new information into any 90540 file that I'll need to make checksum corrections as well (I do recall seeing someone had posted a checksum corrector in the 'understanding the immobilizer' thread)

The other option is, if the hardware I have coming works properly, I may choose to recode the cluster and re-code my key with a new transponder blank to make the car work with the new ECU.

That said, my read through some of the threads here indicates that trying to re-code clusters carries it's own risk that you can fry something in the cluster and then you're really SOL and ripping out your dash to boot....

My concern with trying to recode the 95040 file is that these later ME7.1.1 ECU's carry additional immo coding in a chip other than the 95040 chip

You can easily burn out ecu components if you flash the wrong file. Boot mode working means absolutely nothing.

Hmm, this is the first I've heard of an improper file itself burning out ECU components, please elaborate.

Also, any input with respect to the immo question above? I'd appreciate any feedback from either yourself or the other senior members on the matter.

While the immo thread that I referenced is immensely helpful, there are some unanswered portions for me I want to clearly document in case anyone has similar questions.

So just to be sure, change from the values on the left to those on the right?

"First I've heard" implies long term experience. Why not start with "I don't know anything about EE"?

Anyway: set up an I/O wrong and you can easily end up having a sensitive device sink too much current. I've popped the top of an FPGA with a single bit error. It literally exploded.

Just one of many, many, many ways things can go wrong.

That's a seconds golden piece of information I've gotten from this thread already. Never even occurred to me that there could be fatal hardware errors by flashing a wrong file. Maybe I've just been lucky so far as I've done my share of mistakes like flashing ME7.1.1 file to a ME7.1 ecu (tired, not concentrating, picked a wrong file from folder). I immediately figured what was wrong when car didn't start but never thought I could have bricked the ecu.

I've learnt more from reading about other peoples problems (exactly like this thread) than just reading how something SHOULD have been done. All the information is there but this way burns a better lasting memory imprint than browsing through pages of instructions and not knowing what does what. This might sound bad, but for the rest of us beginners it's a good thing that someone is stupid/brave enough to make these mistakes and definitely brave enough to admit them and ask afterwards. This is intended as a compliment, not an insult