NefMoto

Hello,

I bought a cheap AUQ(-engine code) ECU from a Skoda Octavia VRS, the ECU is stock acording to the seller. I wanted to try it on my A3 1.8T AUM(-engine code), but of course the new ECU must be paired with the instrument cluster. I managed to retrieve the login codes for both ECUs using Vag-Commander, and followed the steps from the Ross-Tech website for Immo3 ECU-Swapping:

All steps work fine until the final step, when I hit "Test" button the values change to "32000" but I get the message "SYSTEM" "Not OK", in the two upper message boxes from VCDS, instead of car's VIN and immo-id.

Skoda AUQ ECU part number: 06A 906 032 HN
My car's ECU, AUM, part number:06A 906 032 HJ
From what I read, AUQ(180HP) and AUM(150HP) engines are phisically the same. Soft coding-ul is the same in both ECUs and both ECUs are ME7.5

Am I missing something or the Skoda ECU is not compatible with the Audi Instrument Cluster?
Is there a (easy) way to make the new ECU to work on my car?

Any help greatly apreciated!

HJ and HN are crossflashable , but not interchangable.
I don`t think any 180 <--> 150 ECU would work.What you are trying to do won`t work ,at least not that I know of .

If the ECU is compatible or not im not 100% sure on that.
Someone else can chime in on that.
However if you get the "system not OK" on a ECU that is compatible here is what you do.

Go into the CANBUS gateway.
Go into coding and even if you keep the same coding, you must clear out what is there and re-type it in.
Press do it, done ok
and then perform the adaptation with the ECU.

should have left cluster alone and immo off the ecu... this would have left your dash and key  paired with out any issue. then you could have swapped ecus with out any problem at will.
did you backup your eeprom from your cluster before you tried modifying it? If so just write the orig back immo off the ecu and call it a day

otherwise ask adam hes running hn software on hj

I did no EEPROMs backups. I just read the login codes for the both ECUs using Vag-Commander then I followed the Ross-Tech steps for ECU swapping. Did VCDS modified the cluster's EEPROM when I followed those steps? I swapped back the original ECU and I had no issue in starting/using the car.


I'm not sure I have time today to try this, but I definitely want to give this a try. In case the ECU-IC pairing is successful and afterwards I want to plug back my original ECU, is it a direct swap or I have to do the adaptation again? If the ECU must be re-adapted afterwards, can this be done any number of times?

I kept reading around this forum(great forum BTW) and got another idea.  Lets say I manage to read the original ECU's 94050 EEPROM and write it on the new ECU, using the argdub's tool...will this bypass the immo? I know I could just disable the immo, but I would prefer to keep it on(not that a 12 years old A3 would be a desirable car for thiefs ;D).

This is not an urgent issue. My original ECU was remapped two months ago to 190HP(tested on dyno), but I have some doubts regarding the quality of the map and wanted to compare it with the "stock" 180HP and afterwards decide which one to keep.

If I were you I would just clone EEPROM from your ECU into AUQ ECU in the beginning...

At this point everything should be fine.
The cluster will not have changed and Since the ECU is a used one even if it did it would not matter.
But when you get system not ok nothing will have adapted/changed.

Clone the eeprom in the ECU and try that.

Will that ECU work in your car? That is still debatable though.

There is one small issue - Audi A3 had special instrument cluster for some 1.8T engines. I can not check it ATM but AFAIR 180HP used different cluster... And this is why you might have had issues with immobiliser adaptation.

Clone the ECU or Immo off it and test.
Easy peasy..

Seems easy now to clone the EEPROM or to disable the immo, but 3 days ago I had zero knowledge about this kind of stuff.  Immo ON seems kinda pointless now  ;D
One thing is not exactly clear to me, can I enable bootmode(with ECU case open and grounding "Pin24")  for writing via OBD port with the ECU connected to the car? Or must this be done on a bench?

A bit busy these days, but I will come back with the results when I will have the time to attempt the job.

I managed today to read/write the EEPROM from the AUQ ECU, I plugged it in my car, the immo light goes off , I can crank the engine but is not starting.. When I crank the engine, the ESP light is flashing. I scanned the engine/instrument cluster for errors but no error is found.

So I guess the AUQ ECU is not an easy swap on an AUM engine for the extra 30hp.

Edit: Nevermind what I said. It's working, I didn't found any issue so far.
First try: copied the AUM EEPROM with immo off on AUQ ECU=>not working
Second try: original AUQ EEPROM with immo off=> works perfectly(so far)

I will update if any issue appears.

Thank you to all for the guidance!

IMHO you just found what I thought - AUM and AUQ ECUs despite both being IMMO3 have different immobilizer routines and that is why in A3 they need different instrument cluster (AUQ and ARY engine codes upto MY2001).

My instrument cluster appears to work correctly with the AUQ ECU. So far I didn't noticed any issues in running the car with the AUQ ECU, but tomorrow I will do some more testing.

It will work correctly because you are using ECU without immobilizer...

Yeah, that's correct.

But the reason you can't use the AUM immo is because they're different.  Good information to know!

you can make a mix of two eeproms from your original aum and donors auq.
i had same issue and had successfully solved it. all you need is to move immo key, vin, login(pin) into new eeprom.
or you can make immo off. your problem is that cluster can't write immo key into new ecu, but it can be done manually

Are you referring to the seed value in the eeprom when you refer to the immobilizer key? Address?

I do this in clusters all the time.
When putting a R32 or GLI cluster in a GL or GLS and VCDS will not adapt it.
Simply move over the data for the immo, PIN, vin and key data, and its done.

I made the AUQ ECU to work with IMMO ON on my car. I copied from my original AUM ECU to the AUQ EEPROM  the following:
-VIN
-SKC
-IMMO ID
-Instrument Cluster Code(Key code?)

After that, I fixed the Checksums(using turboat's 95040Tool) and everything worked like a charm.

Thanks again for the help!

If you are talking about Mk IV Golf you are wrong as I swaped R32 cluster into TDI (IMMO3) many times without any issues.
And what will you do if you will be faced with non VDO cluster?

I didnt say it cannot be adapted, just in some cases I have had it wont adapt.
Sometimes it will sometimes it wont. Rather than messing around with it I do it manually and its done.
And if you don't have all or any of the keys present this is a great way to do it so you dont have to re-adapt the other keys later.

Just makes my life easier.

Also great for re-using old immo pills, and swapping other non-compatable clusters like you mentioned.

Not always necessary but easier for me.

034h & 044h, 7 bytes right after SKC represent the immo key (it's handshake key between ECU and Instrument Cluster(IC)). IC's eeprom stores the same key. When these keys match - immo validation successfully passes. You can make them equal manually (both in ECU and in IC), in this way you can bind almost any IC to any ME7x ECU (and i think M3.8.x & M5.9.x too).
Look at the attached picture, field #2 in left (ECU) and right (IC) side.

A non-vdo cluster, if it's bind to a bosch motronic ECU, should store the immo key somewhere in it's eeprom (because bosch uses this "handshake" technique). Using pair of dumps for IC's and ECU's eeprom you it should be easy to find the key location unless the IC eeprom is encrypted.

Thanks :)

+1

And here comes trouble ;) For example Golf IV 1.6 with non Bosch ECU and non VDO cluster :D
We are far away from topic but still it could be useful for someone to know how to solve immobilizer adaptation issues...

My instrument cluster is made by Jaeger(...and it's made full of fail: fuel level needle is off by half a tank, trip km shows random characters, when is very hot or very cold outside the DIS lines get faded in corners and sometimes it does this https://www.youtube.com/watch?v=zGb3CPRWHuo (https://www.youtube.com/watch?v=zGb3CPRWHuo). Wanted to fix it/replace it but got used to the issues)