VCDS (VAG-COM) codes and programmable options for Golf Mk7

[point]

Took delivery of my 7.5 Comfortline with DAP this morning - I'm having trouble getting Adaptive Lane Tracking activated with OBD11 using guides for MY17 MK7s, B8 Passats and MK2 Tiguans - bit of a stab in the dark but has anyone done this on a 7.5 yet?

[cgentil]

Hi,

2012 MK7.

I accessed

17 Instrument
Coding -> Function 10
Byte 1

I'm using latest version VCDS,

I guess the problem is the VCDS .exe itself.

With Portuguese version of VCDS .exe I get all perfect.

With English Version of VCDS .exe I got that problem.

For example, after I checked

17 Instrument
Coding -> Function 10
Byte 1

I get exactly this in Portuguese:



But if I use English version on Byte 1 I got:



And after get gauge sweep good, I accessed on English version and see the "Display Oil temperature" checked, before I've checked the gauge sweep on Portuguese version it wasn't, just after.

So anyone can confirm that's a problem with English version itself?

In last image you can see the Byte 10 but keep in mind that's what I got on Byte 1 in English version. (disregard images only example)

Thanks.

[cgentil]

Hi,
5Q0 955 547 A, it's not possible to make Rain window close with RLHS still?

[Sasquatch1976]

Hi Don.

Have been following you (being an early OBD11 adopter) for quite some time. I have a 2016 Golf GTE (so a MK7) and have lately changed my stock LED rear lights to the darker version from the Golf R. All good here. Its a no brainer 20 minute job. So having changed these My colleague also bought an identical set for his 2014 GTI. We swapped light today but noticed one thing being different. on his LEDs the brake light LEDs ( just 2) that "cross the indicstor le
LEDs (clear ones) on his car is dual color. We both 'kind of ' remember mine as being this as well earlier when doing codings. n
Now mine is simply either just indicstors OR clear (unlit) even jn brake mode.

its hard to explain, so I borrowed a picture from another post And jn perfect childish freehand drawing style I circled the LEDs in question in yellow.

In short:
His is red when lights are on and brighter when braking. Everything OK.
Mine are just not lighting. Only when indicating. We kind of remembers mine as working before.

I have been lookjng through pages and pages of coding history, but cannot for the life of me see the difference.

Are you aware of a separate light channel for just these two LEDs??

thanks jn advance.

[DV52]

Hi Don.

Have been following you (being an early OBD11 adopter) for quite some time. I have a 2016 Golf GTE (so a MK7) and have lately changed my stock LED rear lights to the darker version from the Golf R. All good here. Its a no brainer 20 minute job. So having changed these My colleague also bought an identical set for his 2014 GTI. We swapped light today but noticed one thing being different. on his LEDs the brake light LEDs ( just 2) that "cross the indicstor le
LEDs (clear ones) on his car is dual color. We both 'kind of ' remember mine as being this as well earlier when doing codings. n
Now mine is simply either just indicstors OR clear (unlit) even jn brake mode.

its hard to explain, so I borrowed a picture from another post And jn perfect childish freehand drawing style I circled the LEDs in question in yellow.

In short:
His is red when lights are on and brighter when braking. Everything OK.
Mine are just not lighting. Only when indicating. We kind of remembers mine as working before.

I have been lookjng through pages and pages of coding history, but cannot for the life of me see the difference.

Are you aware of a separate light channel for just these two LEDs??

thanks jn advance.

Sasquatch1976 - I always encourage folk not to follow me (I'm just an average Joe, nothing worth following).

As for your problem - if you are referring to the LED at the intersection of the brake and indicator light, then the normal fix is as follows:
Depending on the version of the central electrics module, search for either, Driving light and parking light for older modules, or Aussenlicht_Heck for newer modules. Then select Schlusslicht mit Bremslichtfunktion and set as active.


Don

[cgentil]

Hi,

DV52, have you found a solution to rain close with 5Q0955547A?

[Sasquatch1976]

Sasquatch1976 - I always encourage folk not to follow me (I'm just an average Joe, nothing worth following).

As for your problem - if you are referring to the LED at the intersection of the brake and indicator light, then the normal fix is as follows:
Depending on the version of the central electrics module, search for either, Driving light and parking light for older modules, or Aussenlicht_Heck for newer modules. Then select Schlusslicht mit Bremslichtfunktion and set as active.


Don

Hi Don. Thank you for answering. I will try not to stalk you then.
And man my typing and or spelling skill must have lacked yesterday when I made the post....

I will try it out. If my picture somehow did not make it (cannot see it here from Tapatalk) then yes it sounds like the ones you mention. Just the two LEDs being all clear for the indicator. They must have dual color feature as they are red (wheb DRL il on) and even work as braking also. (High intensity output)

Regards
Allan



Sent from my iPhone using Tapatalk

[szurke]

Hi,

DV52, have you found a solution to rain close with 5Q0955547A?

Rain closing working only in module 5Q0955547 for 2015 MY, but it not working an another RLS module-example 5Q0955547A
Rain Close can drain your Battery since the Car won't go into Sleep mode, that's why it is not used anymore.

[csingh]

Hi all,

I've come across this page which has lots of options:

Volkswagen MK7 Golf OBDeleven / VCDS Tweaks List – AutoInstruct

Amateur question - using the example below, when it refers to byte and bit, what exactly is it referring to?

Oil Temperature Display in Cluster
Displays the engine oil temperature in the cluster.

Select Control unit 17
Control unit long coding
Byte 10
Bit 01 Activate

When I go into the long coding menu, there is a bunch of fields which can be updated but nothing named byte or bit.

Thanks in advance

[DV52]

Hi all,

I've come across this page which has lots of options:

Volkswagen MK7 Golf OBDeleven / VCDS Tweaks List – AutoInstruct

Amateur question - using the example below, when it refers to byte and bit, what exactly is it referring to?

Oil Temperature Display in Cluster
Displays the engine oil temperature in the cluster.

Select Control unit 17
Control unit long coding
Byte 10
Bit 01 Activate

When I go into the long coding menu, there is a bunch of fields which can be updated but nothing named byte or bit.

Thanks in advance

csingh: Very good questions indeed! To properly answer your question, I would need a lot of text - this is only a short response and I suggest that you do further research on the topic

This is a thread about VCDS, but I'm assuming that your question relates to your use of OBD11. It doesn't matter what diagnostic tool you are using because the next part of my response is the same -regardless of the tool

At a very fundamental level, control modules in VW cars (well, all control modules really) have 3 x elements of software in their DNA: Firmware, Adaptation channels and Code.

Firmware - as the name implies is the set of instructions that tell the control module how to behave. Firmware is usually installed into the control module at the factory, but it can be upgraded to later versions of software by the car dealers. VCDS cables and OBD11 dongles cannot alter firmware - if you want to do this, then you will need something like a VCP cable, or you will need a dealer tool like ODIS.

The firmware in a control module uses adaption channels and code as its "initiating states" when it operates the car. A Golf mk7 will have around 4,500 different adaptation channels in total depending on the options fitted. Of this total, there are about 40% (around 1,800-ish) adaptation channels that reside in the one control module that OBD11 calls "central electrics". There is a far smaller number of accessible Bytes/Bits in the code-string on a mk7.

Adaptation channels and code are the two items that can be changed by VCDS and OBD11 ( you can also use VCP and ODIS). The difference between adaptation channels and code is an interesting question - it's a question that not even the wise folk at Ross-Tech has been able to answer. But from my amateur perspective, I like to think that code is used to tell the control module what hardware equipment (i.e. sensors, transducers) is installed in the car - and adaptation channels are used to tell the control module how to use that equipment. It's handy to think about code as being a series of software switches that you can turn ON/OFF. Adaptation channels can also be simple binary state switches, but they can also be a logic state that can be selected from a range of possible options.

So, when a tweak instruction refers to a "Byte", or a "Bit", it is talking about changing the code part of a control module (as distinct from the adaptation channel). The code in a control module uses digital nomenclature: specifically it is written in the 2 x primary elements of digital mathematics - those being hexadecimal and binary. Hex is a system of counting based on the number 16 (as distinct from decimal which is based on the number 10). Hex numbers use the numbers 0, 1, 2, 3 ....9 and then the alpha characters A, B...F. So, you can see that with the one hex number, it is possible to represent 16 different states. Any hexadecimal number can be translated into an equivalent binary number. For example, hex B = 1011 in Binary.

In a control module, when a code has a long sting of hex numbers, each set of neighboring numbers are joined together into what 's called a "hex-pair". Each hex-pair is called a Byte and each hex-pair is given a Byte number
For example, the code-string 184AB059 becomes the hex-pairs 18 4A B0 59 and (reading from the LHS) Byte 0=18, Byte 1=4A, Byte 2=B0.........

As I said, any hex number has an equivalent binary value and each hex-pair (or Byte) can be written as a set of 8 x binary digits. So in the example above Byte 0 = 18 (in hexadecimal) and in binary, this equals 0001 1000
Each of the ones/zero in a binary string is a Bit and each one/zero is given a Bit number - but the Bit numbers are read from the RHS (don't ask me why!). So in the example for Byte 0 above:

Bit7=0
Bit6=0
Bit5=0
Bit4=1
Bit3=0
Bit2=0
Bit1=0
Bit0=1

Ok that's all the digital maths that I will inflict on you. In terms of how to access the code and adaptation channel part of an OBD11 device, this is done from the screen below



First, notice that this screen is about the central electrics module. Note also the number 09 in the red circle. Each control module has its own "address". In this case the address of the central elelctrics module is hex09 (yes the same hexadecimal system that is used in code numbering). In your instructions, the tweak says "Select Control unit 17". This means that you need to go to the control module with address hex17 - which in OBD11 speak means the dashboard module.

Anyhow, see the section labelled "Long coding" in the screenshot above- this is the tab that will take you to the code section of the control module. When you select this, you will see the screen below:



If you don't get this picture, then press the 0/1 symbol on the top line of the screen that you have and it will take you to this screen.

Notice the Byte and Bits for this control module. I've chosen a very simple example for this reply - this screenshot is from the Rain/Light/Humidity sensor in a mk7. This particular control module has only 3 x Bytes (see the top line). You can move to the next Byte by pressing the ">" symbol on the bottom of the screen (or the "<" symbol to move to the left). For the Bits, any vacant box is logic 0 and when a tick is placed in a box, it's a logic 1

Don