Used ECU and instrument cluster replacement

[martincitouy]

Some clusters are not swappable after certain millage... is this a color cluster? the navigator one? google for RB4 or RB8 crypto clusters

In that case you need to virginize it in order to match the ECU and make the IMMO work.

You can do the viriginize thing with a blue cable and a special software.... then just VCDS

After that you need to recode your keys again to match your keys to the new IMMO

[diwasas]

It is red cluster screen not color. Not sure what you mean by saying "navigator". The milleage was set to "0" when I bought it. I did nothing with milleage correction yet.

[diagnosticator]

It is red cluster screen not color. Not sure what you mean by saying "navigator". The milleage was set to "0" when I bought it. I did nothing with milleage correction yet.

The ECU immo chip, has the ECU SKC stored on the eeprom. With the SKC, you can adapt the ECU to the instrument cluster, and correct the immo ID with the VIN of your A4, so that the immo ID is adapted to your VIN. Then the IC is adapted to the ECU and immo. You will need to read the 95040 immo chip eeprom in the ECU, then view the hex dump in a hex editor. The SKC is at bits 32 and 33, then you swap 32 and 33, then convert the hex number to decimal and add a leading zero.
For example, 32 and 33 have the hex values of B8 05, swap > 05B8h = 1464d add a leading zero, the SKC is 01464.
With the ECU SKC, you should be able to adapt the VIN and the IC/immo to the ECU with VCDS.

Ref: NefMoto ME7_95040.exe Command line immo chip reader software. There is also a GUI version as well See www.nefariousMotorsports.com

[jaydeff]

The ECU immo chip, has the ECU SKC stored on the eeprom. With the SKC, you can adapt the ECU to the instrument cluster, and correct the immo ID with the VIN of your A4, so that the immo ID is adapted to your VIN. Then the IC is adapted to the ECU and immo. You will need to read the 95040 immo chip eeprom in the ECU, then view the hex dump in a hex editor. The SKC is at bits 32 and 33, then you swap 32 and 33, then convert the hex number to decimal and add a leading zero.
For example, 32 and 33 have the hex values of B8 05, swap > 05B8h = 1464d add a leading zero, the SKC is 01464.
With the ECU SKC, you should be able to adapt the VIN and the IC/immo to the ECU with VCDS.

Ref: NefMoto ME7_95040.exe Command line immo chip reader software. There is also a GUI version as well See www.nefariousMotorsports.com

To add to this, if your immobilizer is already off then you'll also have to change bytes 0x12 and 0x22 from 02 to 01 to re-enable it (unless VCDS is somehow able to re-enable it. I don't know too much about this so somebody correct me if I'm wrong).

From my understanding, there is also an immobilizer key stored at 0x34-0x3A (and mirrored on the next line) which must match the cluster's in its EEPROM. Does VCDS take care of this matching?

[diwasas]

The ECU immo chip, has the ECU SKC stored on the eeprom. With the SKC, you can adapt the ECU to the instrument cluster, and correct the immo ID with the VIN of your A4, so that the immo ID is adapted to your VIN. Then the IC is adapted to the ECU and immo. You will need to read the 95040 immo chip eeprom in the ECU, then view the hex dump in a hex editor. The SKC is at bits 32 and 33, then you swap 32 and 33, then convert the hex number to decimal and add a leading zero.
For example, 32 and 33 have the hex values of B8 05, swap > 05B8h = 1464d add a leading zero, the SKC is 01464.
With the ECU SKC, you should be able to adapt the VIN and the IC/immo to the ECU with VCDS.

Ref: NefMoto ME7_95040.exe Command line immo chip reader software. There is also a GUI version as well See www.nefariousMotorsports.com

Many thanks for this information! I'll try to dig more info from this forum.

To add to this, if your immobilizer is already off then you'll also have to change bytes 0x12 and 0x22 from 02 to 01 to re-enable it (unless VCDS is somehow able to re-enable it. I don't know too much about this so somebody correct me if I'm wrong).

From my understanding, there is also an immobilizer key stored at 0x34-0x3A (and mirrored on the next line) which must match the cluster's in its EEPROM. Does VCDS take care of this matching?

About turning off and on immo, not sure it was VCDS or other software, but there was a button smth like "Immobilizer is on" and "Immobilizer is off", so it was one button click to turn it on or off :)

[diagnosticator]

Many thanks for this information! I'll try to dig more info from this forum.



About turning off and on immo, not sure it was VCDS or other software, but there was a button smth like "Immobilizer is on" and "Immobilizer is off", so it was one button click to turn it on or off :)

You can't turn the immo off or on with VCDS, but you can change the byte values in a hex editor. The checksum may need to be corrected after changing the byte values.