If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed, registering will remove the in post advertisements. To start viewing messages,
select the forum that you want to visit from the selection below.
This means you should apply for your renewal now to avoid any disruptions to your membership whilst the renewal process is taking place! NOTE: If you have an auto renewing subscription this will happen automatically.
Above Forum Ad
Collapse
Announcement
Collapse
No announcement yet.
VCDS (VAG-COM) codes and programmable options for Golf Mk7
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)
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.
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:
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
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is in the forum proper. That way you get the benefit of the wider expertise of other forum members! Thank you.
It looks like the "inner L" headlight LED is physically there, but not enabled unless you take a dynamic curve lighting option? Any ideas if it's 'programmable'?
Hi, it's been a while since my last post. Will pick-up my new Golf R-Line (not R) later this week. Have it fully optioned. Does anyone know/have the VCDS tweaks and codes for this model?
One issue I'm particularly cheesed off about are the head lights. Apparently I have the new LED head lights but without dynamic mode which is also indicated by the fact that I only have one LED driving light each side, not two as is the case in euro models. Does anyone know if that can be switched on with VCDS? Yes I do have VCDS.
As you say, the euro GTI/GTD (+R line ?) all have this "inner L" enabled, yet the GTE does not, unless you go for another lighting option..So there's a few GTE owners and yourself wondering if this can be enabled via VCDS.
Has anyone managed to get the Battery SOC status to show up on the MFD? It wasn't enabled on my 92TSI from factory although it seems to be on some other Aus spec cars?
It's not listed in my adaption channels on OBD11 - is there a way to add it?
Picked up my new R-Line last Thursday. Very nice. Have been looking through VCDS but can’t yet find the setting which turns on the inner L and also dynamic function.
Picked up my new R-Line last Thursday. Very nice. Have been looking through VCDS but can’t yet find the setting which turns on the inner L and also dynamic function.
mick: Hi. These features are relatively new, so I suspect that there will be a leaning period before the tweaks get sorted-out. I'm happy to (try-to) provide input if I can, but I need access to the adaptation channel map for the module @ address hex09 on the new R-Line (it's called the BCM, or Cent. Elect. by VCDS)
This is how to make an admap:
Choose the .CSV function and then put a copy of the file on a third party hosting site (like dropbox) - then post a link to the location here.
The other thing that might help is an autocsan from your new car.
Don
PS:I suspect that you have not created any admaps yet. However, I reckon that it's good, basic VCDS hygiene to create an admap for every control module in your car with their virgin settings (i.e. before you make any changes). Then, just keep the database somewhere safe- if you never need to access it, it's a good thing. But the database will be an invaluable reference source if (when?) the brown stuff and the fan meet!
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is in the forum proper. That way you get the benefit of the wider expertise of other forum members! Thank you.
mick: Thanks for the files - what a very interesting car!!!
First - I suspect that your dealer has used the normal Australian VW dealer definition of a pre-delivery check; a car wash and a smile as you hand-over the final bank cheque!! Your BCM has an error that was registered in the car when it had traveled 12 kms (so- probably in the factory, or on the wharf). The fault frequency for the error (called a DTC) is 1, which means that the error hasn't occurred again in any ignition sequence in the subsequent 136 kms. So, I suggest that you clear the error message - more than likely it won't re-appear!
As for your BCM, some intriguing observations:
This is one of the newer type modules that has no code. So no Bytes/Bits to worry about. All the software switches that were in the code-string, are now in adaptation channels. The admap has an impressive channel-count of 2,040!!
The usual method of control for the front headlight assemblies doesn't occur on your car. In former modules, Leuchte-sets were the method of control. On your car, the Leuchte-sets for the main beam lamps, DRLs, front turn signals are all deactivated. Only the low-beam lamps have an active Leutche-set for the headlight fittings - real odd!
You seem to have 2 x new modules that I've not previously seen on a mk7: the modules @ address hexD6: Light Ctrl Left 2 (A31) and @ address hexD7: Light Ctrl Right 2 (A27). These modules don't have a code string. Can you make an admap for these 2 xmodules - please?
Don
Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is in the forum proper. That way you get the benefit of the wider expertise of other forum members! Thank you.
Comment