NefMoto

Hi all, Just managed a dump of the above cluster. Wondering if it is okay. Need the SKC to replace cluster via VCDS and a new key.
Not sure what address the SKC i8N2920980A M73 D14 clusters located.

Thanks

Alan

test 00286

Hi,elektronik13

Thanks, Ill try that and get back to you.

Did the dump look complete? Not worked with may clusters and looked a bit short!

yes is short
try only once if it doesn't work read all flash and put it here as binary
save the file this way

file as read

06429 is ok
if you do it correctly the old key will work too

06429 is ok
if you do it correctly the old key will work too

So SKC is 06429?

I am right in thinking I need the pin from the new (used) cluster also?

rather, you definitely need it

So i could just dump that eeprom from the replacement to extract it?

give eeprom new dash then I'll give you Pin

OK, likely be tomorrow

Cheers

Thanks
your health

Hi,  I have the dump from the replacemet cluster, any ideas for the SKC in this would be great.

Alan

pin 01502

Hi elektronik13.

just checking 01502?

I had a quick guess at 01582  :) Shows what I know!

Away from the car today now.. Can I verify the replacement cluster pin by VDCS in the car?

Regards

Alan

UPDATE.

Well the clusters are swapped, and I've tried to do the adaptation with VDCS but run into a problem. I can log into the ECU with the old cluster PIN (and the old cluster).  And I can log into the replacement one with its PIN so the PINs check out ok. But I'm getting to the end of the adaption when you enter the old PIN to adapt the Replacement cluster, it comes back with 'sysytem not ok' message. Also having trouble changing the soft coding, but I'm not that bothered by that.
Quetion is, can the eeprom be cloned to the new cluster from the above dumps? or change the eeprom to enable the IMMO code to be changed?

Regards

Alan

online help is possible

I am on the VDCS forums but they seem at a loss. All values seem to be correct for an adaptation to happen.
I'm currently slogging through the webs looking for a solution... not fun :)

System not ok = either pin entered incorrectly to many times check lock timers on vcds..
Or incompatible ie immo 2 and immo 3 if this is the case when adapting don’t use channel 50 just channel 21 enter cluster pin enter number keys test save cycle ignition...immo 2 ecu doesn’t have a skc like immo 3 so they can’t be paired together...or if u immo off you need immo on to pair anything

Hi stuydub,  Lock timers show 0.0 in all fields. Cluster reads as IMMO3 on ID for VCDS and is an identical part number as the old, right down to the A. Same year of manufacturing.
I really want the IMMO on but the car is sitting and I would like to move it! :D
Old PIN extracted from cluster and logs into old cluster and ECU fine. New PIN logs into new cluster fine, but just won't adapt...
Also, may be of note, but the soft coding on the old cluster was 00444 (no options) and the new cluster was 05444 (4WD extended tank)
New cluster wont take the old soft code 00444.. It did take my mistake 04444.. and then took 05444 but not 00444. So it is codable?
I am getting an "unauthorised key intermitant" code, but I was expecting that, as the key would now not be chipped to the cluster...
I will look at ch21 and let you know.

Alan

Update, it's defo IMMO 3 CH21 is key adaption, which it will not complete due the cluster not being paired to the ECU for IMMO.
Tried every thing,. Lock times are 0.0 as all the PINs are correct..

Can I ask what tool you used to pull the bin from the cluster?

I am trying to do this same thing with my 2002 TT 180 AWP, but I am not able to get a full EEPROM read from either cluster.  I am trying to use VAG Commander 2.5 and am only getting partials from both clusters. 

Does that mean that both clusters have issues?

I am working on getting the SKC from the same cluster.  I checked and your 6429 comes from the 2 bytes preceding the AUZ.... immo SN which is consistent with other sources for where to get the SKC.  However down below your SKC of 1502 does not match the 1582 that comes from the 2 bytes preceding the AUZ in the .bin file.  Was that a typo?  Or? 

elektronik13 - can you confirm which PIN, 1502 or 1582, worked?

Did you ever get this to work?