Yeti key-coding-related problem

[BlackMountainYeti]

I recently bought a 2010 Yeti 1.2TSI that came with only one key (I'm led to believe that's not massively unusual). So I've been to a local car electronics specialist who do a replacement key service. They cut and coded a new key using a genuine Skoda blank (part No. 3T0 837 202 H). All seemed OK but then when starting the car with the new key the immobiliser cut in.  I've asked them to sort it out and they agreed without any argument it's their problem to solve (and they seem genuine guys, not cowboys). The car is going back to them in a week's time. However an additional problem has now revealed itself...

 

For some reason the remote unlocking on the fob now only unlocks the driver's door. It first happened when I unlocked it with the new key (which works as a remote even though it has problems with the immobiliser). However it also now seems to be the case with the original key too. I wonder has something been altered in the car's settings, either while engineers had their gear hooked up or as a result of me dim-wittedly using the wrong key?  If so, is it something that can be easily undone with the car's own controls or will it require external kit (eg. VCDS)?

 

Also, what are the odds on the coding problem with the key being sorted easily? Is it likely the new key can be made to work or is there something about that Skoda part which causes issues with a Yeti? Is there another variant of the key blank that would have some slightly different format for coding?

 

[ejstubbs]

You can change the setting for what the door opening button does via the Maxidot (IIRC there's a one-click-for-driver's-door-two-clicks-for-all-doors, setting, which could be what yours has got changed to).  Why it should have been changed as part of the work involving the new key I can't say, but you should be able to change it back.

 

No idea about the coding issue with the new key, I'm afarid.

[Ryeman]

Perhaps it’s in ‘hijack’ mode.  Does a double click open all doors.

IIR it was selectable in options.

[langers2k]

My understanding is as follows.

 

If you were to order a key from a Skoda dealer for your Yeti, it would arrive pre-coded to your car using it's original CS/PIN. The dealer tools would then complete the final pairing to the car to allow the immobiliser and remote to work.

 

Depending where the key came from, it might not have the correct CS/PIN set in the key which would cause the immobiliser to activate. The remote part is separate so it's entirely plausible to code one part but not the other.

 

Most obvious options:

- if the key is pre-coded, a Skoda dealer using official tools can pair it, if it's not pre-coded, they can't

- some companies will simply clone the original key data to the new key, this isn't ideal as it's not possible to block one key (assuming it was lost) and not the other

- a good auto-locksmith should be able to extract the CS/PIN to pre-code the new key, once done, it can be paired to the immobiliser

 

It should be the same procedure as a similar aged MK6 Golf as the immobiliser system is identical.

[BlackMountainYeti]

Many thanks for such speedy responses.  Door locking issue is now (I think) resolved via car's own settings.

 

The people I used definitely extracted a PIN (5 digits I think) using a fairly heavy-duty piece of information technnology connected via a lead that plugged in under the dash (I'm making a wild guess that you plug into the CAN bus there - is that correct?).

 

There was some muttering about formats for coding data but I didn't fully absorb the explanation. I'm wondering if they didn't have the Yeti as a specific menu selection and they perhaps used another Skoda as a default. Maybe, as per langers2k, the Mk6 Golf is the appropriate equivalent. I'm just guessing here.

 

Will report report again as and when I learn more.

[valep]

On ‎26‎/‎03‎/‎2019 at 09:16, ejstubbs said:

You can change the setting for what the door opening button does via the Maxidot (IIRC there's a one-click-for-driver's-door-two-clicks-for-all-doors, setting, which could be what yours has got changed to).  Why it should have been changed as part of the work involving the new key I can't say, but you should be able to change it back.

 

No idea about the coding issue with the new key, I'm afarid.

When you had two keys each one could be used to set it up differently 

[Brijo]

It's a personal safety thing.  E.g.:  

 

One click unlocks all the doors.  Anyone can immediately get in any door.  Might be OK for the key used for the school run. 

OR

One click only unlocks the driver's door.  The other doors aren't available (perhaps for those gentlemen loitering around the carpark) while you (or, more importantly, SWMBO) is getting in.  

 

 

Edited 28 March, 2019 by Brijo

[BlackMountainYeti]

On 26/03/2019 at 14:55, BlackMountainYeti said:

The people I used definitely extracted a PIN (5 digits I think) using a fairly heavy-duty piece of information technnology connected via a lead that plugged in under the dash (I'm making a wild guess that you plug into the CAN bus there - is that correct?).

 

There was some muttering about formats for coding data but I didn't fully absorb the explanation. I'm wondering if they didn't have the Yeti as a specific menu selection and they perhaps used another Skoda as a default. Maybe, as per langers2k, the Mk6 Golf is the appropriate equivalent. I'm just guessing here.

 

Will report report again as and when I learn more.

 

The outcome is the independent auto electronics firm gave up in the end and gave me a full refund.  Key coding seemed to go OK but when I then started the car with the new key the immobiliser cut in and Maxidot displayed a message about an engine fault. After consulting their hardware and software suppliers they concluded it wasn't possible for them to do these particular Skoda keys.

 

In the end I had to go to a Skoda dealer (at higher cost as you might expect). Curiously their first effort ran into the same fault as above. Immobiliser cut in when trying to use new key. I noticed the Maxidot display was showing what seemed to be a fault code ("2-3") in place of the mileage reading.  I queried this with the Skoda technician who told me it was what showed when you were part way through a coding process - it indicates key 2 out of 3 keys. The tech was baffled by this, as he was adamant that key coding completed OK and he'd driven the car out of the workshop with the new key. He went away and had another shot at coding and everything is now fine.

 

I guess coding isn't always straightforward even if you're a Skoda dealer!

 

[Stjepan]

well IMMO system for engine start is diferent story..realy its not that simply as most folks think..on YETI its some kind of early golf 6..remote for door locking is diferent story dont have any relation with imo chip inside ..they only share same plastic key box...

you can play how much you like with remote coding/learning ..but with immo part DONT IF you dont know what you doing..IF you delete data for remote its easy to recover it..but IF you delete immo data it will be tough yob even for dealer with original licence

Edited 21 June, 2019 by Stjepan

[Eddie-NL]

On 17/06/2019 at 17:22, BlackMountainYeti said:

 

The outcome is the independent auto electronics firm gave up in the end and gave me a full refund.  Key coding seemed to go OK but when I then started the car with the new key the immobiliser cut in and Maxidot displayed a message about an engine fault. After consulting their hardware and software suppliers they concluded it wasn't possible for them to do these particular Skoda keys.

 

In the end I had to go to a Skoda dealer (at higher cost as you might expect). Curiously their first effort ran into the same fault as above. Immobiliser cut in when trying to use new key. I noticed the Maxidot display was showing what seemed to be a fault code ("2-3") in place of the mileage reading.  I queried this with the Skoda technician who told me it was what showed when you were part way through a coding process - it indicates key 2 out of 3 keys. The tech was baffled by this, as he was adamant that key coding completed OK and he'd driven the car out of the workshop with the new key. He went away and had another shot at coding and everything is now fine.

 

I guess coding isn't always straightforward even if you're a Skoda dealer!

 

if the 2 -3 is showing that would refer to the key programming.

it is either incorrect or not completed

[BlackMountainYeti]

23 hours ago, Eddie-NL said:

if the 2 -3 is showing that would refer to the key programming.

it is either incorrect or not completed

 

That seems to be the case, but the Skoda technician couldn't work out why. He said the key programming seemed to complete correctly. Also, the vehicle was seemingly then driven with the new key. He went away and did the key coding a second time and then all was OK.