superbPerhaps

Rear wheel bearing scrubbed off the magnetic reluctor ring?

Thats brilliant - thank you. I'll pass that on to my dad and see if it helps.

yes to all positions - including second drive after first stop. dataset/parameters I dont know. not sure what I need to check and verify that. I have vcds and autel and I think somewhere I have a knockoff odis adapter but I've never done anything with that

yes. or supposed to be

5Q0 959 760 B

Could someone please share the coding for kodiaq memory seats? My parents had one of their seat modules fail. They replaced it but now the memory functions dont work and they have loads of errors about no basic settings for all the movement. We've tried many times to follow the procedure for sorting the basic settings- forwards,backwards, up, down etc to no avail. Is there a specific order for the various movements? My dad tried doing factory reset but that hasnt helped. (but may have deleted the coding) Searching around I see loads of people having similar issues but no definitive working fix. I have vcds and an autel 808 and have tried both to fix. ran norming and standardization. Their car is a 2017 kodiaq 4x4 dct diesel with memory seats for driver and passenger. The long coding presently in place is 0014 0000 0000 0000 01A4 8180 8080 0000 0000 8181 0000 00F4 00 Many thanks

For anyone else with the same problem, part number seems to be 1K0 505 491 - currently £17.61

Hoping someone can share the abs coding they have for a similar model (or a link to something that explains how the coding should be generated?) I'm struggling to code a replacement abs module - vcds just fails with an out of range message. VIN: TMBKF73T5E9011570 My original coding and the coding generated by vis4vag both get rejected. original: 863D6016092300FB611006EB90190092340000 vis4vag 843D6016092300FB211006EB90190042350000 Log file doesn't show an error - implies coding worked? Address 03,1K0 907 379 BL,recoded (Long Coding),from,00000000000000000000000000000000000000,to,863D6016092300FB611006EB90190092340000,(33361/790/00052), -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- I see *lots* of people on various vag forums having much the same problem but can't see any real explanation of what the problem is. The scan info from my original module looks identical to the replacement (other than the coding) Address 03: ABS Brakes Control Module Part Number: 1K0 907 379 BL Component and/or Version: ESP MK60EC1 H31 0152 Software Coding: 863D6016092300FB611006EB90190092340000 Work Shop Code: WSC 33361 VCID: 7DF07450E4258AA7CE-8028 Advanced Identification Identification: TT1-03A Revision: 00H31001 Date: 07.06.13 Manufacturer number: 0301 Test stand number: 0A0E Flash Status Programming Attempts(application): 0 Successful Attempts(application): 0 Programming Status: 00000000 Flash Date: 2000.14.00 Flash Tool Code: 00000 000 00000 Misc. Hardware number: 1K0 907 379 BL Workshop System Name: J104 VCDS Info: VCID: 7DF07450E4258AA7CE-8028 Labels: 1K0-907-379-60EC1F.CLB

Thats a very good point - something else to look at anyway.

I did think about it - but if it was that then I'd expect the speed sensors to be consistently giving odd results rather than both of them showing odd results at the same time . that implies connection issues to me.

I've got a few questions re ABS problems - I've read a lot of threads here and elsewhere but still issues. I have a 2013 Superb Estate (facelift) 2.0tdi 170. Had warning lights come on around xmas and vcds said faild left rear wheel sensor. Replaced sensor and all good for 6 weeks and same error but rear right. OK replaced rear right sensor. Another week and the lights are back and vcds says both rear sensors. Had a look at live data and what seemed to happen was that they read ok most of the time then would both give a much lower reading. So all wheels showing 30 mph then suddenly the rears would show 5mph before going back up to 30 - no skids involved! Sensor connectors all seem ok. Reading around I wonder if this is the start of controller failure? I've read about the connectors not being soldered just push fit and thought maybe a vibration or pothole together with loose connection or corrosion is causing a problem? I cant find any supplier stocking the controller - several have it as out of stock. Bought a used unit from ebay (same part number and from a superb2) , but when I try to code it with the long coding from the original unit I just get an error (out of range). Then I read that I might need to program my vin into the unit before I can code it? I found vis4vag and see that they can generate a code - using my vin, plus controller part no 1k0 907 379 BL and controller ID :03. but they also want extra info - I have to select Vacuum sensor- no, vacuum sensor yes, type A or type 2 Anyone tell me what these 4 options mean and how I tell what I have? I've got all the seemingly usual errors about needing sensors calibrating, but I see conflicting info about whether it matters if I code the controller before calibrating or vv or doesn't matter. Anyone been through this and have suggestions?

Anyone done this?

Anyone done this? My drivers seat bolster is collapsing and I like the mk3 seats. but I have a mk2...

I'm just wondering about replacing the seats in my 63 plate estate. They're getting a little tatty and I thought it was worth asking if anyone has swapped out their seats? Current ones are heated/electric in the front. Any other options? thx

Vag tool will work. I would clean the egr as a matter of course and also check stuff like engine mounts.