langers2k

I had a similar leak on my second-hand 2018 vRS 245 which was fixed under warranty. You might want to try taking it to a Skoda garage as there is TPI 2049121/4 related to this. Including changes to how they were fitted: Even if they won't cover the full cost, you might get some good-will if it does match with the TPI

Without diagnostics, you would just be guessing and throwing parts at the car... I don't know where you're based but plenty of members here have VCDS or OBDeleven and should be able to perform a scan pretty easily: - map: https://www.briskoda.net/forums/topic/224376-vcds-owners-map/ - list: https://www.briskoda.net/forums/topic/262215-list-of-vcds-owners-previously-known-as-vag-com-vcp-owners/

You should get it scanned with VCDS or similar, that should help narrow down the problem pretty quickly. A failed sensor or even buzzer can cause the park pilot to stop...

I think switching the front/rear fog light wires at the switch is the only way to achieve this 👍

If you have future issues, you'll need to take the fusebox apart to clean the contacts. I'd suggest keeping your eye on it as it can melt the fusebox due to the heat

Yes - check the fuse I mentioned...

Possibly the CAN-bus gateway? They tend to be quite reliable but you'll need to check which version you have before buying a replacement. It'll also need coding in after replacing.

You might need a little more description than 'the thing' 🤣 The ECU will connect to various sensors and controls on the engine. It'll also connect on to the powertrain CAN-bus which is how it communicates with other modules in the car, including the immobiliser and steering wheel controller to start it.

It'll be the normal issue that causes this Check the 30a fuse 16 in the engine bay fusebox. It tends to corrode causing overheating, bad connections and will disable all the lights you've mentioned. Ideally, you need to open the fuse box, clean/tightening the fuse terminals and possibly replace the fuse👍 Random example:

It is much more expensive over here unfortunately. Comparing direct vs Spain vs UK for example: 3-VIN HEX-V2 - $199 (€182) - €299 - £225 (€259) 10-VIN HEX-V2 - $299 (€273) - €399 - £299 ($345) Guess that makes the Spanish licence approximately €50 or so. Just be careful, anything significantly cheaper than that is likely to be a cloned interface which is not supported by Ross-tech. If you know anyone that's going to be in the US soon, they could bring one back for you 😉

Official distributor list is here: https://www.ross-tech.com/distributors.php If you want it in Spanish, you'll need to buy directly from one advertising it in Spanish (it will also include the English version): If you buy from an English distributor, it will only work with the English VCDS version as it's the distributors who create the translated versions

Reversing can also sometimes dislodge a stuck stone (assuming it's that).

As above, the chamfer is completely normal... Random new example pads:

Probably worth getting the cars scanned with VCDS or similar to give some better clues

I think I used Fuelly in the past but at the moment I'm using Fuelio https://www.fuel.io/

Cornering fogs were an option but the headlights also have a cornering light function. It's not massively bright or obvious so you've probably missed it 👍

All I can do is repeat myself. If your stock byte 18 is 00 (00000000) don't mess with it! The lighting configuration on this age of car is mostly contained within some 40-50 bytes in the BCM EEPROM. If you set byte 18 to a non zero value, it will overwrite this section of EEPROM with a new configuration. If your stock byte 18 is 00, this typically means that none of the byte 18 values contain the correct lighting configuration for your car and instead, the factory tool had to set the lighting configuration directly in the EEPROM. If you change it, you CANNOT get the original configuration back using VCDS as it's unable to directly access the EEPROM. Just as an example, the Yeti came with multiple lighting options which would require different configurations and yet there is only single byte 18 option for a Yeti. I would expect 1D is close to your original config but given your byte 18 is 00, it will not match it identically. As for 1C, I expect that just zero's the entire lighting config. It will not clear lighting fault codes... If you really want to mess with the lighting config, you need VCP or ODIS as they can backup the original config and allow targeted changes to each lighting channel. I have nothing more to add. You've been warned so good luck 👍

Just found a December 2022 brochure, at that point the virtual cockpit was an option on the Sportline.

I can only imagine there was a spec change at some point. Having a quick look at used approved cars, earlier ones seem to have digital displays but later ones have virtual cockpits. At a guess, I'd imagine cars with a build date (not registration date) after around May probably get a VC whereas previously they didn't.

Looking at the latest online brochure and owners manual, there are three instrument cluster options: - Analog instrument cluster with MaxiDot display - Digital display - Virtual cockpit The Amundsen Package Plus or Columbus Package should include the virtual cockpit. The former appears standard on a Sportline. Brochure: https://www.skoda.co.uk/_doc/c63f4efb-a760-4a48-931f-baad88d42aa6 Manual: https://digital-manual.skoda-auto.com/w/en_GB/show/9806f7dd179233d9a8f4adffa86b1a5f_2_en_GB

That depends what your original byte 18 value is. If it's 00, it means none of the 'defaults' are completely correct for your car and you should not change it. If it's some other value, then you can probably restore the config by changing it back to the default. Still - some people have had issues even after restoring the original value which is why it has such a large warning now

Your VCDS is out of date and needs updating. There used to be a massive warning regarding byte 18 so I wouldn't suggest messing about with it. To fix the bulb out warnings properly, you'll need something like VCP or ODIS which can directly edit the lighting EEPROM. VCDS cannot do this

VCDS keeps a log of every change you've made, I'd suggest reversing each change in turn until the original behaviour returns

Ignore what Marcii is saying, I'm not sure why they are quoting my post from another forum regarding enabling cornering fogs but it certainly won't have any relevance to your issue, That being said, the behaviour you've described does sound a little odd. - Is this a new issue? - Have you had any coding performed? - Any errors on the dash/infotainment? - Do you have access to VCDS or similar to perform an autoscan to check for any fault codes etc?

There are three options for TSR changed by setting Road sign detection fusion mode in A5: - Electronic horizon which only uses satnav data - Sign recognition which only uses camera data - Fusion which combines the two, this is the factory default When the camera does pick up a speed limit sign, that'll normally override the satnav data as it's likely a temporary speed limit (roadworks/traffic etc). If it doesn't see a repeater after some distance, it should resort back to the satnav data. If you haven't already, make sure the satnav has the latest maps installed... Annoyingly it can sometimes pick up signs from side streets, parallel roads and once even from the back of a truck Given your original description, it does sound like the above may have occurred and it's working normally.