So on the purchase of my new car I decided to also pick up VCDS. I'd never owned it before, but I thought I'd grab it, just the cheapest 3 VIN version and I'd be able to complete any changes now, and in the future, myself.

Now the first hurdle I find is the secrecy surrounding VCDS. I appreciate it's not that user friendly, but finding information out there on how to code is just proving to be a nightmare. I genuinely thought I'd be able to Google something like "Activate second rear fog-light via VCDS, Octavia Mk3" and I'd have so many results I wouldn't know what to do with them - alas that is not the case.

 

On the car as per signature, I'm attempting to activate three things and I'm hitting a brick-wall immediately. I am now wondering if anyone has actually completed these on a Facelift Octy, using any new version of VCDS or if there is just an assumption these settings still work?

 

1. Activate Secondary Rear Foglight

This may not be a VCDS issue. I've followed the directions as per the threads and also the addition, where the second foglight by default has brightness set to 0 and needs changing to 100.

Alas even after going through all of that, the second rear foglight does not switch on. Is it simply possible that the cluster no longer has the LED wired up in the facelift?

It seems madness if that is the case, requiring different clusters for the UK market. Has anyone managed to activate this on a Facelift Octy?

 

2. Activate HBA

The directions for this one in the sticky are using VCDS 14, so I thought with it being more up to date I might have better luck,

First step in the sticky find the channel "(2)-Assistance Light Functions-Menuesteuerung FemlichtAssistent"

I appreciate many of the channels seem to be renamed now, however that channel does not exist either with or without the preceding (2). I'm not going to proceed further into the instructions when the first step fails.

 

3. Activate Traffic Sign Recognition

An immediate fear as the sticky is showing screen grabs from VCDS 12.

Get to one of the steps and once again, controller channel does not exist as per the screengrabs, there is nothing with a similar name and that is it. I can proceed no further.

 

So have people coded the above on a Facelift Octy without problems? Have you got any pointers here?

 

The "secrecy" I mention in my thread title is that there seems to be a "VCDS Club" that is incredibly difficult to become a member of. Existing members have all been users for a long time and I'm sure had to use even unfriendlier interfaces than is currently available.

It's not so much a fear of passing on the information, but a reluctance. Find somebody near by who can help, great, I'm always generous with beer tokens, but this was precisely why I decided to buy my own VCDS this time around, to avoid all that.

 

I'm guessing this is partly my fault. I should have researched further and as a potentially new user I should have asked more questions prior to purchase.

I made the mistake of assuming the sticky thread remains relevant for newer vehicles, despite being created with rather old versions of the software and I also just assumed there would be plenty of coding instructions out there.

I've spent £225 on this, so not a huge amount, but I'm thinking right now I might as well see if I can sell it on with the 2 remaining VIN registrations and recoup a little.

Try here...

https://forums.ross-tech.com/forum.php

Please don’t take offence, but you may have not searched enough on the forum. My thread on enabling HBA is Here

 

Regarding the rest, you need to bare in mind that the settings/names may have changed but if you search the adaptation channels, you will probably find the settings you need. Unfortunately, whilst I’ve enabled both the TSR and second fog light, this was through much experimentation and I can’t recall the exact steps you would need to follow.

 

The most important tip I can give is to make sure you’ve got a full auto scan saved and leave the log file running whilst you make any changes. Bets of luck.

Just now, Kenny R said:

Try here...

https://forums.ross-tech.com/forum.php

 

I think he has... https://forums.ross-tech.com/showthread.php?16499-Newbie-VCDS-user-Octavia-vRS-2017-coding-help 

I work with software for a living, I just picked up CarPort and it still took me a good 15 minutes to work out how to apply the settings I wanted to a specific controller. I've been using the software on and off for the last 10 years.

It helps that I speak both languages, but this is hard. And there's not necessarily an "undo", either.  

I'll reiterate: I see the difficulty as being partly *wanted*; VCDS has the potential to screw things up royally.  It's not meant for newbies, there are no safeguards. This is why OBDEleven and Carista exist. 

 

You are playing at your own risk. 

 

 - Bret

Edited 27 November, 20187 yr by brettikivi

There's a secret VCDS club!? Where do I get my invite

 

In all seriousness, if such a thing does exist then I've never come across it. All common adaptions (including the ones you're after) are covered in various guides which are freely available.

 

You need to remember that VCDS is primarily a diagnostic tool. One of it's functions happens to allow changing coding and adaptions in control modules that support it, fortunately this is very handy for enabling features or tweaking existing ones. It doesn't matter what version of VCDS was used to create the guide, assuming the controller you're modifying is the same, the procedure will be almost identical. The only obvious exception is where the adaption channel names changed slightly but you'll probably still find them without too much effort.

 

As for the rear fogs, yes, it's completely possible the fog LED is only fitted to one side as it's been known to happen on other VAG cars. You could always go and take a look at your cluster as you should be able to see them if they are fitted...

 

From what you've said, it appears you're trying to use guides for older cars on a car with newer controller so it's not surprising you're having issues.

 

I'd suggest taking time to check this guide out. Yes, it's in German (google translate helps) but has most things included. It's been mentioned in plenty of places on the forums already.

 

If you want help, start by posting a full autoscan and adaption maps for 09, 5F and A5. You should also add exactly what you've tried so far.

 

If you're still stuck, drop me a PM and we might be able to take a look together.

I get where you are coming from, getting to grips with VCDS adaptions has been incredibly challenging for me and when I needed help with naive newbie questions it wasn't really there especially on the Rosstech forum which did surprise me, all I have ever got was a request to post an auto-scan so they knew I had a genuine package, nothing beyond that.

 

I find it really confusing to use and the manual is of little help but a lot of that probably comes down to  the software in the modules.

 

Everybody using 3 word acronyms does not help either as I have no idea what they are talking about, if its a feature relative to me, for instance what is the HBA that you refer to?

 

I still dont know what is the difference between adaptations and coding or why there is a need for both, alos took me ages to realise that I needed to click on each data block or whatever they are called in the long coding helper to see all the available coding options, I was only aware of the ones that came up for the first block, also that there were other (presumably sub) controllers that I could open but that were hidden, still dont know what they are though or what can be done as its written in German.

 

I would say for every thing that I find and understand/master there are also 10 others that make no sense to me at all.

 

Currently struggling (after coding) with coming home lights that work but leaving home ones that dont (or perhaps I dont understand how they are supposed to function) that I have now lost the lights on buzzer and daylight running lights that dont appear to work either.

There are some differences to VCDS tweaks on Mk3's and Mk3.5's as I have found out first hand. Some of the tweaks are comparable but a lot are different to what are posted on the mk3 vcds tweaks page.

 

Make sure you do a back up of your settings before you start, just in case you accidentally make a complete horlicks of it.

 

Do your research thoroughly, but if in doubt, leave well alone.

@J.R. - HBA is high beam assist in this instance. It can also mean hydraulic brake assist but it less commonly used. The acronyms are just something you'll need to learn as you go, in most cases google or asking the poster will give you an answer.

 

The VCDS forums are for owners of genuine interfaces and there are quite a number of clone interface users that try and get support. By posting an autoscan it means not only can rosstech see it's a genuine interface, it also shows a lot of information about how your car is built and configured. It really is incredibly useful to see what a car is made from and how it's configured along with any fault codes before offering advice. I've had a quick search on the rosstech forums but couldn't see any obvious threads from you so it might be worth bumping it.

 

Cars are now (for better or worse) complex computers with a myriad of functions and features. You need to remember is that VAG didn't design them to allow easy activation of other features or even tweaks to existing ones. Even dealer level tools don't offer per byte/bit descriptions like VCDS does...

 

I think you're worrying about the difference between coding and adaptions too much. Only the VAG engineers are likely to know why something would be one or another. As far as I'm concerned, both are just ways to change the behaviour of a module and most guides are pretty clear which something uses. VCDS can only show you what a module allows, they aren't making the choice what should be part of the coding/lcoding or adaptions.

 

As soon as you post your autoscan in your other thread, it might be possible to suggest some coding changes to help resolve your issue.

 

It might also be helpful to add some screenshots when you're unsure of things. If we can see what you're seeing, it might help explain things

Thanks for that, makes a lot of sense, too cold to go out with computer today but I have done a RTFM and can now see how the coming home function is supposed to work and probably is in fact, also may explain the loss of the lights on warning buzzer.

 

Doing screenshots is as challenging for me as posting a photo (in fact just getting a photo from my camera to the computer is now beyond me) or an auto-scan, ask me to rebuild your gearbox or differential or faultfind/diagnose electrical faults and I have no trepidation

 

You are the one person that I can always count on for good advice even if it means telling me how wrong I am (HID conversion)

I have a list of adaptations for FL cars on my laptop at home I can copy over. It’s been copied before but it’s written in German so you’ll need google translate but everything is there. The adaptation channel maps are different from the PreFL so please don’t follow the guides linked at the top of this forum because they won’t work for you.

32 minutes ago, SashaGrace said:

I have a list of adaptations for FL cars on my laptop at home I can copy over. It’s been copied before but it’s written in German so you’ll need google translate but everything is there. The adaptation channel maps are different from the PreFL so please don’t follow the guides linked at the top of this forum because they won’t work for you.

Would also be interested in info about FL cars!

 

Had also been thinking about the same changes as stoofa but hadn't got as far as taking the plunge with VCDS or OBDEleven

7 hours ago, wg100 said:

Please don’t take offence, but you may have not searched enough on the forum. My thread on enabling HBA is Here

 

Regarding the rest, you need to bare in mind that the settings/names may have changed but if you search the adaptation channels, you will probably find the settings you need. Unfortunately, whilst I’ve enabled both the TSR and second fog light, this was through much experimentation and I can’t recall the exact steps you would need to follow.

 

The most important tip I can give is to make sure you’ve got a full auto scan saved and leave the log file running whilst you make any changes. Bets of luck.

 

Hi,

No, for some reason when searching I did not come across your thread. I will have a read of this tonight and see if it's something I can try tomorrow (after backing everything up first of course).

Couple of questions from your instructions.

 

What do you mean by "conduct a soft reset after each change"? Not an option I've come across during my limited exploration of VCDS

Reset Light menu to factory settings after coding - what is the process for doing that?

 

Thank you, it would appear I was probably being premature in my thoughts of some massive conspiracy just against me

3 hours ago, Stoofa said:

 

Hi,

No, for some reason when searching I did not come across your thread. I will have a read of this tonight and see if it's something I can try tomorrow (after backing everything up first of course).

Couple of questions from your instructions.

 

What do you mean by "conduct a soft reset after each change"? Not an option I've come across during my limited exploration of VCDS

Reset Light menu to factory settings after coding - what is the process for doing that?

 

Thank you, it would appear I was probably being premature in my thoughts of some massive conspiracy just against me

1. You’ll see a check box for a soft reset when changing an adaptation channel.

 

2. Press the car button on your infotainment unit, Go to the settings menu and under reset to factory settings, choose to reset the lights. (I’m not actually In my car as I write this, so I’ll check for correctness in the morning!).

I've not tried enabling the second fog light yet but it does appear to be more involved that the Mk2 for instance which was simply one value you enable under Long Coding.

 

As mentioned VCDS is very powerful considering you can purchase this for a relatively reasonable price and perform loads of tweaks which would cost a fair whack at a dealer.

Some dealers either wouldn't perform these for you or even know it was possible!

 

Like mentioned it's a cracking diagnostic tool first and foremost but gives you the ability to not only tweak things but also enable new things on your car should you install them.

Even a simple replacement of a window and lock module required new coding on my Mk2 for the windows to work properly.  

 

I've noticed that depending on the car or the age or even the version of VCDS sometimes you need to hunt for the correct section. It is one of those programs you have to just sit down with and explore. 

As said, always do a full scan before hand and also take some screenshots of the different values before making any changes, at least this way you can revert them to the original value.

 

I noticed that decreasing the main beam assist values were actually in a different place to the VCDS guide which is a sticky in this forum. I think the guide suggests going into module A5, yet mine was actually listed as Main Beam.

This is just one example where sometimes its a case of having a hunt depending on your model.

 

VCDS was designed way before it was common place to have large buttons to enable things such as the OBDEleven but sometimes that can be part of the fun because you can see so much detail at a low level.

It's a bit like Android vs Apple OS. 

 

The RossTech forum can sometimes seem a little bit 'clicky' but I think generally that is because so many people out there have a cloned or hacked version of their product, so they are always cautious of new users. 

Even I have had some sarky replies but I think that is just genuinely because they are all techies so probably 'don't suffer fools gladly'. 

 

That being said, there are some things you cannot do, and that probably won't be a limitation on VCDS, more over a limitation with the cars systems.  One thing I've not managed to tweak is disabling the rear view camera as the default display but show the regular reverse sensor display. Even the chaps over at Ross Tech have been stumped.

 

Overall though, it is a tool work keeping hold of, even when you come to change your car, if you keep within the VAG cars this will be useful again. 

Getting free support and free updates on the tool is also a cracking bonus.

 

 

 

https://onedrive.live.com/redir?resid=3AE6945C79E4C9E!17729&authkey=!AMn8y885S2R-6Xg&page=View&wd=target(Wichtiger Hinweis.one|637bc8bf-9baf-49ac-b1ba-467127f286af%2FHinweis|25dc0849-6ec5-48f2-8d85-3cabe27d4f86%2F)

 

Here is the link to a load of coding tweaks for a load of different cars including the Octy FL and PFL. It's all in German, so you'll need Google translate handy to translate what you need, but it's minimal extra effort. I've gotten used to doing it on the fly at this point.

Cheers all for the pointers etc, but I'm now done.

I just followed the instructions for HBA to the letter. Stopping at every single point to make sure I was indeed selecting the right channels and making the right changes.

Get all the way through to the point where you factory reset the lights and nothing, no HBA option appeared at all.

Completed the rest of the coding anyway and nothing. Even did a complete factory rest on everything (so had to put radio stations back etc) still nothing, option doesn't appear.

 

I've tried following through to get traffic light recognition switched on and again, following everything through perfectly and nothing.

Throw in the fact that it would appear my near-side rear cluster doesn't have the wiring in place for the second foglight.

 

I had a little ODBC reader that cost me £5 which worked with Carrista for getting fault codes on my Mk2.5 - may as well see if that still works with my new car for any future diagnostics work.

 

Time to see if these things have any resell I fear. Anyone buying it will have a fully functioning cable, but they get no support from Ross-Tech. I'll attempt to claw back as much of my outlay as I can.

 

Cheers again.

What support are you expecting from rosstech? Your cable is functioning perfectly normally, you just don't know how to use it...

 

I've tried to help but you've still not posted any requested information!

Put up an auto scan and we’ll have a look at what’s what.

Yes, don't give up yet. There are plenty of people who would be prepared to help, as already evidenced.

Might be worth trying to take a few screenshots of your attempts too so we can see what you are setting. VCDS will normally confirm any changes first and then come up with a message stating something like "codes/values have been accepted by the controller".

 

When you change a value, this should then stay so the next time you go back into that module you will see that new figure. In the case of the drop down menus, again you should see your changes remain after coming out and going back into that module.

 

I have recently done 3 changes to mine. Removed the crazy bong sound when I open the door in D mode, enable the fan LED display when in auto climate mode (why was this never on) and also reduce the activation speed for the main beam assist.

 

I used the posts on this forum to apply these changes - top marks to all who have posted these - thank you!

There are a lot of people who are up for helping on this forum! 

 

5 hours ago, langers2k said:

What support are you expecting from rosstech? Your cable is functioning perfectly normally, you just don't know how to use it...

 

I've tried to help but you've still not posted any requested information!

Not expecting anything from Ross-Tech.

Just aware that if I sell the cable, the new owner won't be able to get any support from them without the "on-boarding fee".

My initial scan from the first weekend I had the car was as follows:

 

Chassis Type: NE-SK37 (3Q0)
Scan: 01 03 08 09 10 15 16 17 19 42 44 4B 52 5F A5 A9 D6 D7

VIN: TMBBE7NE2J0180655   Mileage: 15887km-9871miles

01-Engine -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
10-Park/Steer Assist -- Status: OK 0000
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
4B-Multifunc. Module -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
5F-Information Electr. -- Status: OK 0000
A5-Frt Sens. Drv. Assist -- Status: OK 0000
A9-Struct. Borne Sound -- Status: OK 0000
D6-Light Ctrl Left 2 -- Status: OK 0000
D7-Light Ctrl Right 2 -- Status: OK 0000
-------------------------------------------------------------------------------
Address 01: Engine (J623-CHHA)       Labels:. 06K-907-425-V1.clb
   Part No SW: 5G0 906 259 P    HW: 06K 907 425 B
   Component: 2.0l R4 TFSI  H13 0001  
   Revision: --H13---    
   Coding: 0C1900122424010B0000
   Shop #: WSC 73430 031 00063
   ASAM Dataset: EV_ECM20TFS0205G0906259P 001001
   ROD: EV_ECM20TFS0205G0906259P.rod
   VCID: 3B23349C63EA853F8B7-806E

No fault code found.
Readiness: 0000 0000

-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104)       Labels:* 5Q0-907-379-ESP-V1.clb
   Part No SW: 5Q0 614 517 AQ    HW: 5Q0 614 517 AF
   Component: ESC           H62 0400  
   Revision: 00000000    Serial number: 62647000002281
   Coding: 240793915428216C407D060540C82924C92A8402600294762043F070C029430000000012121212B8586C384E4484EE
   Shop #: WSC 73430 031 00063
   ASAM Dataset: EV_Brake1UDSContiMK100ESP 036010
   ROD: EV_Brake1UDSContiMK100ESP_036_SK37.rod
   VCID: 005983704A8C26E79E5-8054

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J255)       Labels:| 5G0-907-044.clb
   Part No SW: 5E0 907 044 AP    HW: 5E0 907 044 AP
   Component: Climatronic   H04 2001  
   Revision: 00001K00    
   Coding: 0111000400011001100500080010102A
   Shop #: WSC 73430 031 00063
   ASAM Dataset: EV_ACClimaBHBVW37X 006146
   ROD: EV_ACClimaBHBVW37X_006_SK37.rod
   VCID: 73B3DCBC0B3A0D7F937-8026

   Fresh Air Blower Front: 

   Refrigerant Pressure And Temperature Sender: 

   Air quality sensor: 

No fault code found.

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels:. 5Q0-937-08X-V2.clb
   Part No SW: 5Q0 937 084 CQ    HW: 5Q0 937 084 CG
   Component: BCM MQBAB H   H36 0253  
   Serial number: 01001726802262
   Coding: 000000000000000000000000000000000000000000000000000000000000
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_BCMMQB 018001
   ROD: EV_BCMBOSCH_018.rod
   VCID: 094F9E5479B667AFC9B-805C

   Control Unit For Wiper Motor: 
   Subsystem 1 - Part No SW: 5E2 955 119 A    HW: 5E2 955 119   Labels: 5QX-955-119-V1.CLB
   Component: WWS371 170723  051 0915 
   Serial number: 887253F0401720400232
   Coding: 164DDD

   Rain Light Recognition Sensor: 
   Subsystem 2 - Part No SW: 5Q0 955 547 B    HW: 5Q0 955 547 B  Labels: 5Q0-955-547.CLB
   Component: RLHS  047 0105 
   Serial number: S9Y17M09D25H08M17S34
   Coding: 00885D

   Sensor For Anti Theft Alarm System: 
   Subsystem 3 - Part No SW: 5Q0 951 171     HW: 5Q0 951 171 
   Component: Sensor, DWA  005 0316 
   Serial number: 000000000ZY171700ZC4

   Alarm horn: 
   Subsystem 4 - Part No SW: 5QD 951 605     HW: 5QD 951 605 
   Component: Sirene, DWA  005 0314 
   Serial number: 00002856223971904139

No fault code found.

-------------------------------------------------------------------------------
Address 10: Park/Steer Assist (J446)       Labels:| 5Q0-919-283.clb
   Part No SW: 5QA 919 283 B    HW: 5QA 919 283 
   Component: PDC 4 KanalH07 0044  
   Serial number: 000308419617275
   Coding: 0601050001
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_EPHVA14AU3700000 009033
   ROD: EV_EPHVA14AU3700000.rod
   VCID: 49CF5E54393627AF09B-801C

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags (J234)       Labels:| 5Q0-959-655.clb
   Part No SW: 3Q0 959 655 BH    HW: 3Q0 959 655 BH
   Component: Airbag VW21   006 0703  
   Revision: --------    Serial number: 003W4PK23QWI
   Coding: 98CCC000000000005C5400CC008800000065
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_AirbaVW21TS6VW48X 001014
   ROD: EV_AirbaVW21TS6VW48X_VW37.rod
   VCID: 0557926455AE03CFAD3-8050

   Side Sensor Driver Front: 
   Subsystem 1 - Part No SW: -----------    HW: 454 003 108 17
   Component: SideSensor_Df  008 0887 
   Serial number: 35700000000669ACC82.
   Coding: 2D2D2D

   Side Sensor Passenger Front: 
   Subsystem 2 - Part No SW: -----------    HW: 454 003 108 17
   Component: SideSensor_Pf  008 0887 
   Serial number: 35800000000F57ACC821
   Coding: 2D2D2D

   Side Sensor Driver Rear: 
   Subsystem 3 - Part No SW: -----------    HW: 454 801 609 17
   Component: SideSensor_Dr  301 0148 
   Serial number: 35100A6D130120000002
   Coding: 2D2D2D

   Side Sensor Passenger Rear: 
   Subsystem 4 - Part No SW: -----------    HW: 454 801 209 17
   Component: SideSensor_Pr  301 0148 
   Serial number: 35200F06606120000003
   Coding: 2D2D2D

   Front Sensor Driver: 
   Subsystem 5 - Part No SW: -----------    HW: 454 802 708 17
   Component: FrontSensor_D  304 0149 
   Serial number: 355002BC305120000006
   Coding: 2D2D2D

No fault code found.

-------------------------------------------------------------------------------
Address 16: Steering wheel (J527)       Labels:| 5Q0-953-549.clb
   Part No SW: 5Q0 953 507 GD    HW: 5Q0 953 549 F
   Component: Lenks. Modul  003 0140  
   Revision: --------    Serial number: 03101704220156
   Coding: 1400
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_SMLSKLOMQB 020002
   ROD: EV_SMLSKLOMQB_VW37.rod
   VCID: 7EA5FD8830785017EC9-802A

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels:| 5G0-920-XXX-17.clb-SRI3
   Part No SW: 5E0 920 956 E    HW: 5E0 920 956 E
   Component: KOMBI         303 0310  
   Coding: 27A5010069808600010A6B021001000000000000
   Shop #: WSC 73430 031 00063
   ASAM Dataset: EV_DashBoardVDDMQBAB 009060
   ROD: EV_DashBoardVDDMQBAB_009_VW37.rod
   VCID: 2E050DC8A09860973C9-807A

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels:| 3Q0-907-530-V1.clb
   Part No SW: 3Q0 907 530 G    HW: 3Q0 907 530 C
   Component: GW MQB High   436 4304  
   Revision: --------    Serial number: 0006875480
   Coding: 030100047F085900EB00026A080F00010001070000000000000000000000
   Shop #: WSC 73430 790 00000
   ASAM Dataset: EV_GatewNF 013023
   ROD: EV_GatewNF_VW37.rod
   VCID: 33331CBC4BBA4D7F537-8066

   Alternator: 

   Multi Function Steering Wheel Control Module: 
   Subsystem 2 - Part No SW: 3V0 919 719 A    HW: 3V0 919 719 A
   Component: E221__MFL-PR6  H02 0160 
   Serial number: 000000000C0297130917

   Battery Monitoring Control Module: 
   Subsystem 3 - Part No SW: 5Q0 915 181 J    HW: 5Q0 915 181 J
   Component: J367-BDMConti  H03 1050 
   Serial number: 75886000001709271A50

No fault code found.

-------------------------------------------------------------------------------
Address 42: Door Elect, Driver (J386)       Labels:| 5QX-959-X93-42.clb
   Part No SW: 5Q4 959 393 E    HW: 5Q4 959 393 B
   Component: TSG FS        011 0032  
   Serial number: 0000278857101 
   Coding: 001C00208001040000001100
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_DCUDriveSideEWMAXCONT 006001
   ROD: EV_DCUDriveSideEWMAXCONT.rod
   VCID: 45D75264152EC3CFED3-8010

   Drivers Door Rear Control Module: 
   Subsystem 1 - Part No SW: 5Q0 959 812 E    HW: 5Q0 959 812 E
   Component: FOND_FHSG_DRV  006 0007 
   Serial number: 00000000000016525724
   Coding: 1D0200

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist (J500)       Labels:| 5Q0-909-144.clb
   Part No SW: 3Q0 909 144 K    HW: 3Q0 909 144 H
   Component: EPS_MQB_ZFLS  506 5072  
   Coding: 9107
   Shop #: WSC 73430 790 00000
   ASAM Dataset: EV_SteerAssisMQB 013144
   ROD: EV_SteerAssisMQB_013.rod
   VCID: 3A2D31986CD0BC37901-806E

No fault code found.

-------------------------------------------------------------------------------
Address 4B: Multifunc. Module (J745)       Labels:* None
   Part No SW: 3Q0 907 338     HW: 3Q0 907 338 
   Component: FCM MQB Low   002 0286  
   Serial number: 24091710800957
   Coding: 000000070100046E00003D01010000000000000000000000000000000000
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_MultiModulContiVW48X 001010
   ROD: EV_MultiModulContiVW48X_001.rod
   VCID: 72BDD9B874200477981-8026

No fault code found.

-------------------------------------------------------------------------------
Address 52: Door Elect, Pass. (J387)       Labels:| 5QX-959-X92-52.clb
   Part No SW: 5Q4 959 392 E    HW: 5Q4 959 392 B
   Component: TSG BFS       011 0032  
   Serial number: 0000276803064 
   Coding: 001C00208001040000001100
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_DCUPasseSideEWMAXCONT 006001
   ROD: EV_DCUPasseSideEWMAXCONT.rod
   VCID: 44D14F601E14FAC7FAD-8010

   Passengers Rear Door Control Module: 
   Subsystem 1 - Part No SW: 5Q0 959 811 E    HW: 5Q0 959 811 E
   Component: FOND_FHSG_PSG  006 0007 
   Serial number: 00000000000016527537
   Coding: 050200

No fault code found.

-------------------------------------------------------------------------------
Address 5F: Information Electr. (J794)       Labels:* None
   Part No SW: 565 035 020 A    HW: 565 035 020 
   Component: MU-H-ND-EU    H54 1163  
   Serial number: A855I0HB026777
   Coding: 03735101FF00000051111201008800002F0101C601200500FF
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_MUHig4CGen2HBAS 001001
   ROD: EV_MUHig4CGen2HBAS_VW37.rod
   VCID: 0B43A45C73CA75BFFB7-805E

   Operating And Display Unit 1: 
   Subsystem 1 - Part No SW: 5E0 919 606 D    HW: 5E0 919 606 D
   Component: ABT_High-2  H50 9130 
   Serial number: SKZ6ZHT2730882      

   Data medium: 
   Subsystem 2 - Part No SW: V03 959 801 JN    HW: -----------
   Component: ECE 2017/2018  --- 0161 
   Serial number: --------------------

   Compact Disc Database: 
   Subsystem 3 - Part No SW: V03 959 800 EG    HW: -----------
   Component: Gracenote2  --- 1016 
   Serial number: --------------------

No fault code found.

-------------------------------------------------------------------------------
Address A5: Frt Sens. Drv. Assist (R242)       Labels:| 3Q0-980-65X-A5.clb
   Part No SW: 3QD 980 654     HW: 3Q0 980 654 A
   Component: MQB_B_MFK     H08 1272  
   Serial number: 28081741K10335
   Coding: 0203070100000401000223408150A80084000E200000
   Shop #: WSC 73430 790 00063
   ASAM Dataset: EV_MFKBoschMQBB 001001
   ROD: EV_MFKBoschMQBB_001_VW36.rod
   VCID: 08499B5062BC1EA7D65-805C

No fault code found.

-------------------------------------------------------------------------------
Address A9: Struct. Borne Sound (J869)       Labels: 4H0-907-159.clb
   Part No SW: 5E0 907 159     HW: 4H0 907 159 A
   Component: SAS-GEN 2     H06 0001  
   Serial number: 170907200170
   ASAM Dataset: EV_SoundActuaGen2AU64X 003010
   ROD: EV_SoundActuaGen2AU64X.rod
   VCID: 698FBED459F6C7AF29B-803C

No fault code found.

-------------------------------------------------------------------------------
Address D6: Light Ctrl Left 2 (A31)       Labels: 7P5-941-591.clb
   Part No SW: 7P5 941 591 AD    HW: 7P5 941 591 A
   Component: LED1L         H06 0005  
   ASAM Dataset: EV_LED_PLUS_L_KEBODAVW416 001003
   ROD: EV_LED_PLUS_L_KEBODAVW416_SK26.rod
   VCID: 7EA5FD8830785017EC9-802A

1 Fault Found:
0800 - Bulb for Low-Beam Headlamp 
          C1198 F6 [040] - Over-Temp Protection Active
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 2
                    Reset counter: 0
                    Mileage: 1609 km
                    Date: 2017.12.16
                    Time: 15:29:05

-------------------------------------------------------------------------------
Address D7: Light Ctrl Right 2 (A27)       Labels: 7P5-941-591.clb
   Part No SW: 7P5 941 591 AD    HW: 7P5 941 591 A
   Component: LED1R         H06 0005  
   ASAM Dataset: EV_LED_PLUS_R_KEBODAVW416 001003
   ROD: EV_LED_PLUS_R_KEBODAVW416_SK26.rod
   VCID: 7EA5FD8830785017EC9-802A

1 Fault Found:
0800 - Bulb for Low-Beam Headlamp 
          C1198 F6 [040] - Over-Temp Protection Active
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 2
                    Fault Frequency: 3
                    Reset counter: 0
                    Mileage: 1609 km
                    Date: 2017.12.16
                    Time: 15:27:35

End----------(Elapsed Time: 01:35, VBatt start/end: 12.2V/12.2V)-----------

 

I'll go through the coding again tomorrow and repost the "after" scan.

Sorry, I misunderstood your last post. I took it as you were expecting rosstech to know how to enabled/disable everything on your car. Yes, you are correct, support is limited to the registered owner unless paid for.

 

When you scan it tomorrow, make sure you get adaption maps for 09, 5F and A5 too. A CSV file is fine and I think you can attached it to post.

 

There is a video showing how here: http://www.ross-tech.com/vcds/tour/controller-channels-map.php

Top tip: when you post the scans from a vehicle, I would recommend removing the chassis number (VIN).

 

 

Edited 28 November, 20187 yr by Black_Sheep