Skip to content

langers2k

Resident Member
  • Joined

  • Last visited

Everything posted by langers2k

  1. The fan should only normally stay on if you've interrupted a regen cycle and the engine bay is super hot. It shouldn't be a common occurrence or happen every time you stop the engine... How long are your journeys and what mileage has the car done? If it's been sat around a while it might just need a decent journey to fully clear the DPF out, if it's a higher mileage car the DPF may be getting full with oil ash. Might be worth adding where you're based as a local member with VCDS/OBDeleven can check for fault codes and the soot/oil ash loading in the DPF
  2. The part number should be on the rear of the old ones. I think it's 6U0 601 151L
  3. 9977 is a 'fixed' ECU software version I think there is also 5751 and 9978 available for that ECU. The former is pre-fix and as far as I know, can be flashed using ODIS but I've never tried to downgrade an ECU. It's certainly worked for other modules. No idea what a tuner would charge, probably £100-£150 in the UK?
  4. That's not the case with steering modules, although the higher letters are typically newer, it doesn't mean they will support the same features/functionally... There is a helpful page from rosstech: http://wiki.ross-tech.com/wiki/index.php/Steering_Wheel_Control_Module_Versions#Part_Number_5K0-953-569 Bare in mind, that is just the HW part number so you should also consider the SW part number too.
  5. What number are you using? 5K0953569E brings back loads on both eBay and Aliexpress... edit: It might be worth reconnecting it and get a scan with VCDS or similar. This is for two reasons: - to confirm the SW part number - to backup the existing coding This is the module from my old Octavia, it shares the same HW part number as your Yeti but I expect the SW is different Address 16: Steering wheel (J527) Labels: 5K0-953-569.clb Part No SW: 5K0 953 521 BN HW: 5K0 953 569 E Component: LENKS.MODUL 014 0140
  6. Physically it might, although the A4 camera will have a different parameter/dataset on it so it may not work properly given how different the MMI and MIB radios are. I got the one for my Octavia from this seller who was quite helpful: https://www.aliexpress.com/item/4000197729171.html There was spare length in the loom so I just cut it down to size
  7. Nope, the diesel vRS is a 184 The 220/230/245 is the power output in pferdestärke aka PS or metric horsepower. Therefore, if you have 217BHP then you have the 220ps edition
  8. Surely you can just connect it to an appropriately fused, switched ignition live and the problem is solved...?
  9. Just had a quick look at the WD I have and I can only see 4 wires The fold in switch (E263) looks to share the resistor ladder with the other rotational settings which makes sense:
  10. You'll need to add a wiring loom for the camera The camera wash tee's off the existing rear washer.
  11. Pretty sure it's behind the glovebox... It should be described in the owners manual how to access it
  12. Are you able to share the update?
  13. I prefer the chart from the rosstech thread I posted although it basically says the same thing with G12 evo added: What your car has is along the top axis, what you're adding is along the left axis. For a car with G11 originally, look down the left hand column: - G11 is factory - G12 is not compatible - G12+, G12++, G13, G12evo are all mixable with G11 and will protect as well or better In my case, I'd look down the 5th column: - G13 is factory - G11, G12, G12+ are not recommended due to reduced protection - G12++ and G12evo are both mixable with G13 and will protect as well or better
  14. At a guess, it's 5J7 868 522 which is part 14 here:
  15. I think they have a 2014 petrol vRS looking at their old posts. My FL 2018 vRS is loosing coolant so it's not just the pre-FL... it drops from max to min in about 3-4k so it's going in for investigation next week under warranty, the dealer mentioned they had coolant pumps in stock without prompting so it must be pretty common TPI 2049121/3 covers coolant loss and a few of the production changes they've made: • Optimizing filling process of coolant in CW 12/2015. • Measure to ensure tightness of coolant regulator housing, introduced in CW 27/2019. • Measure to ensure tightness of coolant pump, introduced in CW 23/2020. Not that the TPI gives much clue as to exactly where the pump is: This might help though:
  16. I'd ring a few local garages and see if anyone has the correct VW spec coolant. If you're quick, Amazon can get you some tomorrow using prime: https://www.amazon.co.uk/Volkswagen-coolant-G12E050A2-replaces-G013A8JM1/dp/B08BNNMR2G/ G12evo can be added to G13 without issue: https://forums.ross-tech.com/index.php?threads/20182/
  17. Bluetooth won't help... Most of the AA apps on XDA suggest they need root, maybe take a look at AAAD on XDA as that doesn't seem to need root although it may require an out-of-date AA version. This isn't something I've done nor intend to try, the links/videos are to give you a starting point and set you off in the right general direction
  18. As above, the first thing is to see if your car and phone support Android Auto: Once you've confirmed that, you'll probably need to root your phone and install one of the various AA apps to allow video streaming. How to root will depend on your phone, be warned, there is a risk of losing all your data, security concerns and even the possibly of bricking the phone. XDA is a good place to start, they have sperate sub-forums for most common phone models with rooting guides and there are a few AA streaming options here: https://forum.xda-developers.com/f/android-auto-general.3834/ There is also a video guide to downgrade AA here: Personally, I wouldn't want to be rooting my phone or running old apps but that's my view so it may not match yours. Obviously it's your choice but if you have an older, unused phone, I'd be tempted to use that when you want video streaming rather than your main phone
  19. Hopefully it's just another fuse issue as that's pretty easy to solve....
  20. I have Connect but I've not subscribed and it's pretty much useless... - The status page last updated when the PO Connect subscription expired meaning the fuel level, mileage and time until service are all wrong - The health report 'works' in as much as it says "We have not found a defect" although the date is two months out of date and the mileage shows 0 - The trip planner is something I have no use for, I use Waze for nav - The logbook is the same, I'm not going to log my drives - The Skoda dealer address isn't helpful, I know where they are, I bought the car from them - The details page shows me the VIN and that it's a 180KW manual vRS, all things I know It wouldn't be so bad but my phone is always connected by USB and the car is parked in an area with good WiFi coverage. Before they merged the apps, at least I could see the service log but that's missing since the merge... It might be better if I added a datastick and a Connect subscription, looking at the Connect subscription page, probably not. The functions may depend on vehicle age/spec, mine is a MY18. Update: Just hopped in the car and poked all the buttons. It's updated the vehicle status page for the first time in my ownership! Although the health report is still out of date... @varaderoguy I've never used the Connect Lite dongle, how does it compare? I think it does some driving analysis too IIRC? Sorry to @JayLibove if we're going a little off topic, I thought it might be helpful to understand what Connect or Connect Lite actually add as I don't believe either will offer or alert you to firmware/software updates. Edit: Left the car on for 10-15 mins and it has updated the health report inc the mileage. Maybe it just needs more time in WiFi range whilst turned on...
  21. That's nothing to do with adapting or coding... On a working car, it should look similar to this: Address 55: Headlight Range (J745) Labels:. 5M0-907-357-V3.clb Part No SW: 5M0 907 357 F HW: 7L6 907 357 C Component: AFS-ECU H04 0111 Revision: -------- Serial number: -------------- Subsystem 1 - Part No SW: 8U0 941 329 HW: 8U0 941 329 Labels: 3D0-941-329.CLB Component: LeiMo links H01 0005 Coding: 8E0000 Subsystem 2 - Part No SW: 8U0 941 329 HW: 8U0 941 329 Labels: 3D0-941-329.CLB Component: LeiMo rechts H01 0005 Coding: 8E0000 Notice there are two subsystems, one for each headlight. On your scan, you only have one subsystem so for some reason, the AFS master can't communicate with one of the headlights. Given both the old and new module show the same error message, it's likely to be a wiring issue somewhere. You need to check the power, ground and CAN-bus connections... Based on the Octavia and MK6 Golf, the headlight pinout is: - pin 1 is AFS CAN high - pin 2 is AFS CAN low - pin 4 is AFS slave power - pin 5 and 7 are ground As I mentioned previously, on my Octavia both AFS slaves are powered by a single fuse (SC21) but given the replacement modules isn't talking, I just checked the Superb manual and that suggests: - fuse 10 Adaptive left main headlight - fuse 11 Adaptive right main headlight I'd check for power on pin 4 of the headlight and fuse 10/11 as a start. If you've got power, disconnect the car battery and check continuity for the AFS CAN-bus between the headlights and the grounds are good.
  22. Erm, I thought the 1.6 CR was OK to convert but the 2.0CR isn't...
  23. I thought the 1.6TDi was OK with a conversion but the 2.0TDi really don't like it? Not sure which engine the OP has though...
  24. Pretty sure Skoda Connect doesn't alert the owner to any software/firmware updates. Even if you take it for a service at Skoda, they probably won't do any updates either unless it's a safety related recall. The 'best' way to find out about updates is to take a look at the TPI/TSB on erwin for your VIN. Some maybe apply regardless, others may need certain pre-conditions such as a particular symptom or fault code. If you meet the pre-conditions, a local Skoda dealer should be able to apply the update for you if you tell them the TPI. If you don't, they will probably refuse the work

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.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.