Immo2 or immo3? I know you said 3, but AFAIK 99 should be immo2. Do you have the cluster dump?

ECU guys and IMMO cluster guys need to have a summit. Cluster guys know where the IMMO data is kept, but according to Bentley service manual, the MY1999 A8 did not have IMMO. The MY2000 did, so it is possible yours came equipped because of rolling change on the production line. If it did, it will be an IMMO-3.

I believe the 5 digit pin is accessible from any IMMO equipped cluster using VAG Tacho. The 14-digit IMMO identification number is easily lifted from a bin dump of the cluster's EEPROM. What is missing that makes the whole ensemble work together when new parts are introduced is the SKC, a 7-digit, valid for one-day only number that will allow a tech to adapt a new or replacement ECU to an existing IMMO equipped cluster while retaining all of the IMMO protections.

Nyet-

VAG TACHO IS CRAPPPPPPPPP

Vag K+can is where it's at, and I've posted the NEWEST version that works without a proprietary interface. I can post it again if you like?

Here you are. The last version of vag k+commander confirmed working with non-bundled cables. You don't have to do anything to the cable to make it work. No special drivers, no serial number changes, NOTHING. Just make sure when you connect to select K-line protocol, rather than CAN.

You will have to edit the tester.ini file with your cables VCP settings. I know you guys reading this now don't need an explanation, but for future readers, just right click on the TESTER.INI, and open it with NOTEPAD. Under the COM section, change KWP=to your cable's port number. Then run the program. Easy as pie.

Just wanted to say massive thanks to ddillenger I been trying to find a version to work with a dumb cable and this was perfect.
Managed to do MTE and illuminated dials on my cluster so thanks again

Hi.

I am based in the UK and the audi A8 (facelift) from 1999 to 2001 appears to use immo 3.  On VCDS the engine and immobiliser controllers show two numbers, the VIN registration and the immobiliser number.

I still haven't been able to extract the PIN from the malfuctioning cluster.  The new cluster is recognised as a KOMBI INSTRUMENT VD0 D23 by VCDS but the old unit controller can't be opened by VCDS(its appears to have been damaged by a voltage spike).

I have considered using various software packages to look for the PIN or download the faulty cluster's EEPROM, but I am concerned about blocking the EEPROM and then be left with only the engine management unit to interrogate.  I  dont want to risk blocking the ECU EEPROM by looking for the PIN there.  The engine mangement is a Bosch Motronic 7.1.

As I can't find the information how to use the cluster dump to calculate the PIN I am going to go for a read of the old cluster EEPROM and rewrite this to the new cluster.

The car should then start without any need for key matching.  The other alternative is to desolder the EEPROM and refit it to the replacement cluster.  If the soldering isn't perfect this will probably lead to problems.  Not sure I should learn surface mounted component soldering on this project. 

I am going to use an auto locksmith with professional equipment to do a read and rewrite the EEPROM to the replacement cluster.  I will of course keep the bin file and see if the pin can be found, using VCDS to attempt log-ins of the calculated PIN.


Let you know how it goes

From the few immo III cluster dumps that I've seen (and been able to compare to matching 95040.bin),  I have noticed that the skc is paired three times consecutively, and this only seems to happen in one place in the file, somewhere near the vin/immo ID portion, but the actual hex-address, and even the information immediately around the data varies. But again, I only have two immo III cluster dumps to look at. I hope this helps.

there are other places where pairs repeat, but those either repeated more than three times, or less.

Edit: