Need halp reading PIN code for cluster swap

[GJF47]

Hi. I am trying to swap the cluster over in my car. The old cluster died so I bought a used one. I used Vag Commander to read the PIN for the original cluster, which worked fine, but when I try to read the PIN for the new cluster it wont work.

First it comes up with 'Trying different logins' and then 'security access key not accepted. retrying in 5 seconds'. Then it will just say 'Check security access key' and then 'Cannot autodetect device'.

Any idea what is wrong here? Everything was fine with the original cluster but it just wont read the new one.

 

[Bondiblu]

Hi. I am trying to swap the cluster over in my car. The old cluster died so I bought a used one. I used Vag Commander to read the PIN for the original cluster, which worked fine, but when I try to read the PIN for the new cluster it wont work.

First it comes up with 'Trying different logins' and then 'security access key not accepted. retrying in 5 seconds'. Then it will just say 'Check security access key' and then 'Cannot autodetect device'.

Any idea what is wrong here? Everything was fine with the original cluster but it just wont read the new one.

Where's the cluster from? Is it definitely a known worker? and is it definitely plugged in and latched correctly?

 

[GJF47]

The cluster is from a breakers. Its from a LCR. What do you mean by known worker? I've ran all the output tests using VagCom and they worked fine. It is definitely plugged in correctly yes. I've even taken it out and put the original back in and it read the PIN straight away. Put in the new one and it wouldn't read it again.

 

[Bondiblu]

I meant did you know if it definitely worked fine before. Sounds like the immobiliser IC could be corrupt. Are you able to read out the IC? If you've already got a k+can commander, you could potentially deactivate the immobiliser in the ECU then you wouldn't have to code it in, even if just to prove everything else works.

 

[GJF47]

How would I go about deactivating the immobiliser ? I've got Vag Commander, VagTacho and VagCom. Should I send the cluster back do you think?

 

[Bondiblu]

If you bare with me, I will try have a look tomorrow evening, and refresh my memory, then get back to you. Possibly immobiliser defeat has been used on the previous car or something like that. Silly question, but I take it the car doesn't start with the new clocks in?

 

[GJF47]

No it doesn't start mate. Well, it does start but cuts out in a few seconds. I'm going to try Vag Commander on my own car (the car im changing the cluster in is my Father's) tomorrow as well to see if it reads the PIN for that.

 

[JamesL]

Do you know what year LCR the clocks came out of? I seem to remember years ago reading about similar issues on Ed38 in golfs - some of the clocks changed slightly in terms of software etc in different years? Maybe because its a different year clock that's causing you issues, if anything changed?

 

[Bondiblu]

Do you know what year LCR the clocks came out of? I seem to remember years ago reading about similar issues on Ed38 in golfs - some of the clocks changed slightly in terms of software etc in different years? Maybe because its a different year clock that's causing you issues, if anything changed?

I think you might be correct. @GJF47 What software ver are you using? I'm using Vag k+can commander 1.4

 

[GJF47]

Do you know what year LCR the clocks came out of? I seem to remember years ago reading about similar issues on Ed38 in golfs - some of the clocks changed slightly in terms of software etc in different years? Maybe because its a different year clock that's causing you issues, if anything changed?

I can't tell what year the car was. I've just checked on the listing for other parts that came off the car but the plates have been removed. The other parts are listed as being code BAM 225 so I'm guessing that it is '03 on.

I think you might be correct. @GJF47 What software ver are you using? I'm using Vag k+can commander 1.4

I'm using Vag K+Can Commander 1.4 as well.

I've tried using VagTacho and it finally connected after about 30 attempts but it came up with 'Password:14' and then some other error and then disconnected.

 

[Bondiblu]

Ok, just tried my 56 plate Ibiza cupra. At first it wouldn't read, but managed to sort it.

Connect cable, turn key on, open software, select connect type k-line then select instrument / immo. Once that opens, try click "reset ECU" first, wait for that to complete, then click "read" and see if that makes a difference. never had this issue on my 52 plate Ibiza.

 

[GJF47]

That is how I have been doing it mate. I didn't reset the ECU first time but I have done it since then. I use exactly the same process on the original cluster that has died and it reads the PIN first time. I'll give it another go when I get home from work though.

With the original cluster it connects and reads all the different blocks until the mileage and pin come up. With the new one it says connected but then say 'Trying different logins' and then 'Security key not accepted'. None of that happens with the original cluster.

 

[Bondiblu]

That is how I have been doing it mate. I didn't reset the ECU first time but I have done it since then. I use exactly the same process on the original cluster that has died and it reads the PIN first time. I'll give it another go when I get home from work though.

With the original cluster it connects and reads all the different blocks until the mileage and pin come up. With the new one it says connected but then say 'Trying different logins' and then 'Security key not accepted'. None of that happens with the original cluster.

Ok, well I'm running out of ideas then. Either the clocks are slightly different and not supported or the info in the chip has been tampered with and therefore 'Security key not accepted'.

If you connect to the engine as I've already said you could potentially deactivate the immobiliser that end. I would suggest saving backups of the EEPROM before attempting that, and I've only attempted it on the EDC15 ECU's, so not sure it'll work on the ME7's (assumption made here).

 

[GJF47]

I have phoned the place I bought them from and they say the LCR was an '04 or '05 plate. They said if I am still having problems getting the PIN then I can return the clocks so if I don't have any joy over the weekend then I'll send them back and order another set. I would rather do that than mess around and cause damage to something to be honest

 

[Bondiblu]

I have phoned the place I bought them from and they say the LCR was an '04 or '05 plate. They said if I am still having problems getting the PIN then I can return the clocks so if I don't have any joy over the weekend then I'll send them back and order another set. I would rather do that than mess around and cause damage to something to be honest

If it's an 04 /05 then it may not be supported, ver 1.4 is meant to support only some Seat's pre 2004 thats what the documentation says, though as mentioned it works ok on my 56 plate. Keep us posted.

 

[GJF47]

Hmm maybe I'll make sure the cluster is from an '03 or earlier then if I have to order a new one. Thanks for the help anyway mate, I'll update this if I get any luck with it

 

[GJF47]

Bit of an update - I just tried to read the PIN from the cluster of my own car which is an '02 LCR and it came up with the same error message. Seems that the only one it is working with is the original from the Toledo!