Jump to content

BlackMountainYeti

New here
  • Posts

    6
  • Joined

  • Last visited

Profile Information

  • Location
    South Wales

Car Info

  • Model
    Yeti

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BlackMountainYeti's Achievements

Rookie

Rookie (2/17)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

1

Reputation

  1. 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.
  2. 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!
  3. I see a lot of references to MIB1 & MIB2 but can someone clarify what these refer to? I have a 2010 vehicle with a Bolero but I can't figure whether stuff to do with MIB is applicable or not. Also, I believe I have a Maxidot display but it doesn't seem to have the full range of functions people soemtimes mention.
  4. I believe it's possible. My car has an aftermarket bluetooth unit that seems to do something similar to what you're talking about. I believe lower spec versions of some cars had a Bolero fitted but no bluetooth, so you have the button for a phone but it doesn't do anything. It looks like a previous owner added a unit made by Dension. This provides bluetooth phone connectivity and I get the usual type of info on the Bloero screen (phonebook, call buttons, caller ID etc). Sorry I can't help much more in terms of how the units are connected - I suspect it's CANbus but I'm not sure. Dension publish their install manual on their website so you can take a look at the info for current units. The direct link for one of them is: https://www.dension.com/files/products/gateway_pro_bt_-_install_guide_0.pdf It looks to me like it connects to CANbus but I'm no expert. I do note that it contains the following text under section 7: Of course to do what you're proposing you'd need to know about programming for the Bolero/MDI so you can send and receive data in the right formats. If you can do that sort of stuff I'm well impressed...
  5. 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.
  6. 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?
×
×
  • Create New...

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.