NefMoto

i managed to frie my ecu and make my cluster unreadable (think it was soldered to death)
Because of this i cant retrive any information from old units  ::)

The audi workshop wants to replace ecu, cluster, immo box, keys, locks  estimated to 2000-3000 eur. They also claim it's impossible to pair these units without reading the codes from the cars they came from  :o

I have bought a used ecu and cluster also got vcds lite.

I am wondering how to pair these two units, they are from different cars, i have the login for the ecu (got it with the 95040 tool from this forum)
Do i need to virginize ecu, cluster, both maby? havent find a tool to read/ write the cluster eeprom yet.

the vin nr on the car is WAUZZZ8EZ1A020142

Audi A4 1.8t  quattro 2001
ecu: bosh me 7.5 8e0906018b
cluster: i have no idea  ???


Hope someone can help me  :P

You will need a new transponder for your key. The old one can only be tied to one immo ID. After that, adapt the ecu to the cluster, then complete key learning.

Oh i didn't know that i needed a new transponder, thanks  ;)  but how is the adapting process possible when i don't have the login code for the cluster?

Im guessing i have the immo II so i have been reading this page

http://wiki.ross-tech.com/wiki/index.php/Immobilizer_II_Immobilizer_Swapping_(Instrument_Cluster)

You can pull the login code from the cluster dump, use VAG-commander 5.1 or similar.  Or even pull your dump from the clocks and we can tell you the code.  I'm sure vag-com tells you the login code on the actual GUI.  It's either that, or another piece of software.

Either way, it's pretty easy man! :)

I have heard about vag commander, but i dont have the cable to use that program. i have blue kkl 409,1.  What do you mean by "Or even pull your dump from the clocks" i don't understand  ???

Thanks for reply  :)

You can use that cable no problem.  I honestly can't remember what software I used last, but I've got it at home and can tell you when I get there.  I can even put it on my dropbox for you to have a copy.

You've got loads of time to read up while you wait for a new transponder to arrive anyway dude! :)

oh thought i needed a hex-can cable or something like that to use it.

That would be fantastic!  ;D

I tried vag commander 1.4 2.5 3.0 5.1 and 5.5 also two pin readers  and some of them say channel open but i can't do anything and the rest of them don't connect (device no wake up/ no respons, something like that) Also tried vag tacho/ dash but i don't find the device. Tried installing some of the drivers but windows will only accept the driver it downloads from windows update  >:(

tried the k-line and ISO 9141 kwp2000
also tried xp mode, same result

vcds connects fine

I usually use vag eeprom programmer, there's a download somewhere on here, think it's linked from one of the vag commander threads. The clone vag tacho is a pos, don't bother with that.

Work like charm  :D thanks man  ;)

This is the login code i get from the motomoter.dat file 63867 this can't be right?

uploading both the dat and the eeprom file

Sure that's a proper read out?

I have no idea, never done it before, it didn't show the login code in the interface, only softcode i think it was.

So i put the cluster into new mode and read the eeprom, this is what i got
login 9786

But it doesn't work  ???

Here is the eeprom file and a picture, can anyone tell me what im doing wrong?   this is getting annoying   :'(

Did you login with 9786 or 09786?

+1; that's a better read and I can confirm the same login code.  You always stick a 0 at the start of the code though, so that it reads 09786, rather than just 9786.

Good luck! :)

thats what i did, it keeps telling me it's wrong, and that i have to turn the igniton off and try again  ??? :o

Tried with the cluster in new mode and adapted mode and i still cant login, yes i use 09786.
What can cause this?  ???

Is it possible to reset all values in the eeprom and change login pin? i converted 9786 to hex and got 263A, but i cant find the two side by side
Think 260 OB must be the one containing the 3A, but the 26 is all over the file.

Is it explained somewhere how to understand the cluster eeprom? can't find it   :-\

So i found out that if i enter the wrong pin the cluster locks itself for 7 min, and restarts the 7 min each time the igniton is off until the right pin have been input  ::)  So i needed to turn the ignition on and wait 7 min before trying to log in

Finaly was able to log in  ;D

Now i got another problem, either i try to adapt it from the ecu menu or the instrument menu, it tells me that (adaptation) (not ok) and on the instrument it says (key) (not ok)

Is this because off the 95040 immo off change? 
The immobilizer light isn't blinking, but the warning hazard lights is.

Tried to adapt keys (with new transponders) but it says error in the block when i type in new key count  ???

For the umpteenth time, you cannot adapt components that have the immobilizer disabled.

I swear umpteenth was a Scottish word.. You said naw the other day, too..

Immo back on, adapted keys and then i was able to adapt the ecu. Was a pain in the ass  >:(

Now it works, thanks for all the help guys  ;)

I am wondering what hardware did you use? The VCDS?
And where did you get the software? I cant seem to find it anywhere.... I have looked for VAG EEprom programmer

I used vcds-lite and blue kkl 409.1 cable
Eeprom pogramer in attachment, can't find the download i used  ???

Thank you for the info. I have VCDS USB-HEX adapter I will try to read using it and post the results here.

Also does the VCDS adapter need to be in the "dumb" mode?

Yes.

I have attempted to read the cluster EEPROM and no luck. Seems to me that the eeprom programmer will not talk to the USB-HEX adapter by Ross-Tech. The port in the programmer is currently set to USB. Do I need to install USB to COM1 port virtual device software and try again or I am missing something?

Yes, likely.

isn't the cable com? you have com 1 com2 and usb option in eeprom programer? right?

I never managed to make eeprom programmer or commander work with my rosstech lead, blue kkl ones are so cheap there's not much point messing around.

Hexcom cables cannot be com anything without the VCP drivers. Unfortunately, Ross tech doesn't keep them updated. Everyone should bug them about it.