Used ECU and instrument cluster replacement

[diwasas]

Hi!

Car does not have its original ECU and Instrument cluster, both are replacements from other cars (I have instrument cluster PIN code). and the only way to drive a car at the moment, is with disabled immobilaizer. We have tried various adaptations and other stuff with VAG-COM, but no luck at all. I think the main problem is that both components was replaced at the same time, so none of them does not contain original immo info (or smth like that). While doing adaptation, at some point I'm always getting "SYSTEM NOT OK"

So, my question is: is there any chance to adapt new components to my car, that immo can work again at home or the official dealer is the only way to go?

1.9TDI 96kw.

Thanks.

[drjonez]

You'll need to directly rewrite the immo on both the ECU and cluster, at the EEPROM level.

You're correct- because you replaced both at the same time there is no way to do it with VCDS.

[walky_talky20]

Doctor, can you explain why not?

Can't we just pretend the car IS the junkyard ECU donor car, and we have just changed only the cluster? If we pretend as such (and we close our eyes and *believe*) could we not proceed as normal with VCDS?

[diwasas]

Thanks for the replies! I'm not good at this VCDS stuff, but as I remember VCDS can read EEPROM, or I'm wrong? Maybe it would be enough to fix only ECU in this way, so after that instrument cluster could be adapted in normal way, because ECU would have car's immo info already?

Other question is can these immo problems cause "communication errors" on other components?

01317 - Control Module in Instrument Cluster (J285)
49-00 - No Communications
01330 - Central Control Module for Central Convenience (J393)
49-00 - No Communications
00466 - Control Module for Steering Column Electronics (J527)
49-00 - No Communications
00457 - Control Module for Network (J519)
49-00 - No Communications
00474 - Control Module for Immobilizer
49-00 - No Communications
01320 - Control Module for Climatronic (J255)
49-00 - No Communications

Or these problems are not related and I have to solve this in other way?

[diagnosticator]

Thanks for the replies! I'm not good at this VCDS stuff, but as I remember VCDS can read EEPROM, or I'm wrong? Maybe it would be enough to fix only ECU in this way, so after that instrument cluster could be adapted in normal way, because ECU would have car's immo info already?

Other question is can these immo problems cause "communication errors" on other components?

01317 - Control Module in Instrument Cluster (J285)
49-00 - No Communications
01330 - Central Control Module for Central Convenience (J393)
49-00 - No Communications
00466 - Control Module for Steering Column Electronics (J527)
49-00 - No Communications
00457 - Control Module for Network (J519)
49-00 - No Communications
00474 - Control Module for Immobilizer
49-00 - No Communications
01320 - Control Module for Climatronic (J255)
49-00 - No Communications

Or these problems are not related and I have to solve this in other way?

If you clear all those DTC, do any of them reoccur? The No Comms is not associated with the immo, it is likely due to the IC and ECU not adapted to each other.

[diwasas]

Not sure about all, but most of them reoccurs. As drjonez suggested about directly rewriting immo to EEPROM, it is unclear to me what to rewrite? Because not having old ECU, there is no orginal immobilizer info anymore.

[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.

[walky_talky20]

I'm not understanding why there needs to be any rewriting of EEPROMs here. There are only 2 units involved with the IMMO: the ECU and Cluster. There are procedures for replacing each with a used one. The furthest that one should need to be go is to rip the SKC out of one or the other, and then adapt. Code some keys, then smoky AWD burnouts FTW.

Sure, the VIN stored in the ECU and cluster will be some random junkyard VIN, but who cares? I don't see any problem with making this work just using regular VCDS procedures (with key extraction via other tools). Or am just stupid and missing some obvious thing?

[jaydeff]

I'm not understanding why there needs to be any rewriting of EEPROMs here. There are only 2 units involved with the IMMO: the ECU and Cluster. There are procedures for replacing each with a used one. The furthest that one should need to be go is to rip the SKC out of one or the other, and then adapt. Code some keys, then smoky AWD burnouts FTW.

Sure, the VIN stored in the ECU and cluster will be some random junkyard VIN, but who cares? I don't see any problem with making this work just using regular VCDS procedures (with key extraction via other tools). Or am just stupid and missing some obvious thing?

VCDS can't enable/disable the immobilizer. From my understanding OP's immobilizer is currently off and he wants it back on, so to turn it back on you need to write to the ECU immobilizer EEPROM and also match the cluster data for it to work properly.

[diwasas]

VCDS can't enable/disable the immobilizer. From my understanding OP's immobilizer is currently off and he wants it back on, so to turn it back on you need to write to the ECU immobilizer EEPROM and also match the cluster data for it to work properly.

I have two ECUs at the moment, both is from other cars. One is with disabled immo (currently installed into my car), other with enabled, both have identical part numbers. I think you can turn on/off immo easily with vag-tacho or vag-dash.

Diagnosticator provided some links for EEPROM reading. As I understand I can also use VCDS cable for that procedure, just with other soft, no need seperate cable?

According to ROSS-TECH when car leaves the factory, PINs/SKCs is the same for ECU and IC, so the all procedure should be like this(?):

0. ECU replacement is installed into car and immo is ON. (Car starts and immediately off, immo icon is blinking in IC panel).

1. Read ECU EEPROM and get SKC number.

2. Login to IC and type its PIN. (I have PIN code for this IC replacement, but not sure is it correct, though seller ensured that it is correct).

3. Adapt IC to the ECU, and as old IC PIN use that SKC from ECU EEPROM (because we pretend that ECU is "original" from factory and IC is replacement, as I metioned before, that orriginaly ECU and IC PIN sould be the same).

4. Adapt keys to the immobilizer (I have new transponders installed to the keys already).

Correct me if I am wrong.

[walky_talky20]

^That is how I understand it should be. Yes.

I believe you can also do it the other way. (pretending IC is original from factory, and the ECU is the replacement). Either method should work. The only difference being which VIN is kept when completed. Since neither are your real VIN anyway, it doesn't matter.

In my experience the adapting is kinda "fiddly" or stubborn and doesn't always work as promised. As such, you may find better results with one method over the other (ie: adapting IC to ECU or vice versa). If things really don't want to work, then I would look into flashing stuff with a known good image. I once had a junkyard cluster that just refused to adapt. I ended up dumping the eeprom from the bad cluster (needles had failed) and uploading to the junkyard unit. Worked a treat. Good Luck.

[diagnosticator]

You can use the VCDS cable, but it must be set to boot in dumb mode, by un checking "boot in intelligent mode" in the VCDS options screen. Then close VCDS and turn off the ign key for 20 seconds. You must also use the Ross-Tech VCP drivers available on the Ross-Tech website, instead of the regular USB drivers.

http://www.ross-tech.com/vag-com/usb...-com-port.html

The VCP drivers will create a USB COMM port in Device Manager: Ports (COMM&LPT) (virtual comm port,) device. Make sure the COMM 1 is selected in the port advanced properties, and the ME7_95040 command line program is set to use COMM 1 with the command line switch "-p 1" in the command line string. Open a command window with a right click and select "Run as administrator". The command line will look like this:

Drive:\ME7_95040.exe --OBD -r -p 1 -b 10400 "file name.bin"

If reading over the OBD port does not work, then you will need to put the ECU into Boot mode, and the command line will look like this:

Drive:\ME7_95040.exe --BOOTMODE -r -p 1 -b 10400 "filename.bin".

"filename.bin" is the file where the hex dump of the immo chip 95040 will be stored. Open the hex dump file "filename.bin" with a hex editor to view the hex bytes 32 and 33 ( row 3, columns 2 and 3, first column is 0) to use to convert to the SKC, using the procedure: Bytes 32 33> 33 32 > omit space between values, "3332"h (NOT value 3332h!) convert to decimal then add a leading 0. This is the SKC of the ECU.

Example: 32 = B2h, 33 = 05h > swap> 05B2h > convert to decimal> 1,452d, add a leading zero, > 01452 is the ECU SKC. (Not the actual SKC, example only.)

[diwasas]

Yesterday I made a quick try to read EEPROM with my VCDS cable, removed VCDS, installed VCP drivers from ross-tech, it is slelected as COM3 as default now, installed VCDS again with unchecked "remove old USB drivers" and "install standart USB drivers" (or smth like that), uchecked "boot in intelliget mode". VCDS showing that USB drivers is outdated, do not know is that important. Ignition was on. But ME7_95040.exe (v1.31), and VAG K+CAN Commander (v2.5) was unable to connect to my car, it shows "Opening COM3... OK", but at the next step "Initiating communication... fail (0x....can't remember)", I'm getting an error.

Did not try NefMoto ME7 ECU FLASHER yet, can it read ECU EEPROM?

This is device info prom this app:

Name: ROSS-TECH HEX-USB
Type: FT_DEVICE_232R
Chip ID: 0x5C2425C5

Maybe my cable is not compatible? :(

Btw, my laptop is with Win 8.1 x64, VCDS is working fine with this. Also have another with win7 x64, I'll try with this also.

Can anyone post a good link to the tutorial how to put ECU into boot mode? All I found is that I need to ground some pin.

Meeeh.... Maybe you noticed in my earlier post, that my car is diesel car, not petrol. ECU: EDC15P+, 038906019FP BOSCH 0281010729, so I found that I can't read that ECU type with this software... :/

Another chance is try to connect through VAG K+CAN Commander and VCDS cable, it seems to be able to read my ECU.