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

[DV52]

^^^^ What elastica_junkie said!! Go to the Ross Tech directory on the laptop that you used to make the changes. Then go-to VCDS, or VCDS-Beta (depending on which version of software you use), then go to Debug subdirectory. In this subdirectory find the Codinglog.txt file and open it with a text reader (like notepad). You should see a string of records for the before and after values of all the changes that you made with your cable

Or you could read my short paper on what to do when tweaks go wrong (it happens to everyone). You can find nthe document HERE
Don

[limiteded]

Ive installed footwell illumination into a MY14 comfortline.
parts sourced from carsystems.pl

the process of install involves removing the left side lower a pillar trim, front passenger door sill trim, centre tunnel footwell trim to push the wrining to the other side. The cutouts for the lights is already there.
the ground connection is the passenger lower a pillar earth point.
the bcm is behind the glovebox, but this only needs to be dropped down, not removed.
you must disconnect the battery before connecting into the bcm 73 pin plug. Dont take the risk of pulling the plug live and frying the bcm because its lost can bus connection, inputs status and outputs.

the coding i did blind, as the vcds version i had, was not labelled for the bytes for the bcm.
i got my coding from a uk website, and it all worked.
Credit to these people for the coding

Retro fit footwell lights Octy III - Skoda Octavia III (2013 onward) - BRISKODA

the leds are set up for ambient lighting, and this is selectable from the centre screen

[sapz]

Help!!

I was changing lighting settings using VCDS, to change the blink feature while using turn signals and my car lighting is jacked up

Bad Symptoms:

-I'm getting an error saying both my DRL's are out
-The DRL's don't turn on when using Parking lights
-Only left fog works
-only left for lights up for coming up lights

I'm really hoping someone can help me set everything back to default. Here are the changes I made... and the warnings came after (12)-Leuchte2SL I think.. does anyone know the default values for (12)-Leuchte2SL and (12)-Leuchte3SL ?

--------

DRL TURN SIGNAL DIM

If you want the DRL to dim when indicating, make sure:
(6)-Leuchte2SL VLB10-Dimmwert AB 2 and (6)-Leuchte3SL VRB21-Dimmwert AB 3) is 100. 127 causes it to stay bright. There is no difference between 100 and 127 in light output.
Same for the CD Channel brightness. Default is 26, but I like mine at 100. Just don't use 127.

Then simply set:
(12)-Leuchte2SL VLB10-Lichtfunktion E 2 = Blinken links aktiv (beide Phasen)
(12)-Leuchte3SL VRB21-Lichtfunktion E 3 = Blinken rechts aktiv (beide Phasen)
(14)-Leuchte3SL VRB21-Dimmwert EF 3 = 26
(14)-Leuchte2SL VLB10-Dimmwert EF 2 = 26
(15)-Leuchte2SL VLB10-Dimming Direction EF 2 = minimize
(15)-Leuchte3SL VRB21-Dimming Direction EF 3 = minimize


Thanks a ton to anyone who can help!!

[DV52]

Help!!

I was changing lighting settings using VCDS, to change the blink feature while using turn signals and my car lighting is jacked up

Bad Symptoms:

-I'm getting an error saying both my DRL's are out
-The DRL's don't turn on when using Parking lights
-Only left fog works
-only left for lights up for coming up lights

I'm really hoping someone can help me set everything back to default. Here are the changes I made... and the warnings came after (12)-Leuchte2SL I think.. does anyone know the default values for (12)-Leuchte2SL and (12)-Leuchte3SL ?

--------

Thanks a ton to anyone who can help!!

sapz. Hi It's a bummer when tweaks go wrong, but it happens to us all - alas.

As for your question about the default values, the irony is that the answer is resident inside the laptop that you used to make your changes.

Read my reply in post #841 about the records in the codinglog.txt file - default values are there!

My suspicion is that the default values are as follows:

• (12)-Leuchte2SL VLB10-Lichtfunktion E 2=Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht)
• (12)-Leuchte3SL VRB21-Lichtfunktion E 3 = Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht)

But, there are lots of variations with your NAR models up there in the north, so you should confirm this with the records in the codinglog.txt file

Don

[dmc_]

The dashboard lighting—including the infotainment screen—responds to changes in ambient light levels. You may have noticed a brief ray of sun on a cloudy day, for example, causing everything on the dash to get brighter. (You can also test this by shining a light on the sensor. The sensor is in the tach, between the "7" and "8".)

The instrument cluster dials, however, behave differently, especially on MY2016 vehicles.

With the headlight switch in the "off" position, the cluster dims to black when it is dark. This is to remind the driver to turn on the headlights.

Somewhere around MY2016, this "off when dark" cluster dimming behaviour also made its way to the "parking light" (or "side light") position in some markets. While I understand this can help inattentive drivers, I've found a few situations where I would've liked cluster illumination without the main beam.

Many thanks to JonboyGTD on another forum for this VCDS tweak. It allows cluster illumination with the headlight switch in the "parking light" or "side light" position:

Open controller [17-Instruments]
[Security Access-16] > Enter 25327
[Adaptation-10] > Change (1)-Illumination_algorithm-Scale_switching_algorithm from parking_light to lds

Now, my cluster is fully illuminated for all headlight switch positions except OFF. The cluster still follows the "on until dark" dimming curve in the OFF position, and is still responsive to changes in ambient light.

[isaacinsoll]

try 5F-> Byte 23 -> 00 (uncheck all)

How would I do this with obd eleven? Thanks


Sent from my iPhone using Tapatalk

[isaacinsoll]

How would I do this with obd eleven? Thanks


Sent from my iPhone using Tapatalk

Never mind, I was being a noob.

For anybody else, these values are under coding, not adaptions


Sent from my iPhone using Tapatalk

[fabbromix]

Hi, I would like to set the LED daylight U (bi-xenon headlights) when opening doors or using the remote control to unlock / lock the doors but I can not find any posts where I can see the changes to do with vcds.

For the outer rear headlights okay having made change in strings Leuchte20-21BR E20-E21 code working well.

I forgot I do not have the function automatic lights.

[bcometa]

Increase illumination of instrument cluster clocks- Instructions

1. Select 17 - Instrument control module
2. Select Security Access - 16 from the "Open Controller" screen
3. Enter the magic number 20103 and return to the "Open Controller" screen

20103 doesn't work for me. Neither does 25327. I'm attempting to make this chance using ODBEleven. Previously, I've made other changes in "17" ("Dashboard" on OBDEleven), but can't make this one. Any ideas?

Thanks,
Brian

P.S. I searched and couldn't find answer. Please excuse if this has been mentioned before.

P.P.S. To explain further: "20103" is "accepted" in the "security access" screen, but when I actually makes the changes and write them, it prompts for security code again. If I enter "20103" again and press "enter" the password screen goes away for a second then comes back. If I purposely enter the "wrong" code, it says something to the effect of "wrong password, incorrect authentication."

[DV52]

20103 doesn't work for me. Neither does 25327. I'm attempting to make this chance using ODBEleven. Previously, I've made other changes in "17" ("Dashboard" on OBDEleven), but can't make this one. Any ideas?

Thanks,
Brian

P.S. I searched and couldn't find answer. Please excuse if this has been mentioned before.

P.P.S. To explain further: "20103" is "accepted" in the "security access" screen, but when I actually makes the changes and write them, it prompts for security code again. If I enter "20103" again and press "enter" the password screen goes away for a second then comes back. If I purposely enter the "wrong" code, it says something to the effect of "wrong password, incorrect authentication."

Brian: Hello and welcome to the best VW forum south of the equator!!!

I know that it's little solace, but what you describe is a common problem (as I understand) on NAR (North America Region) mk7s with a MY15, or later build. For some unknown reason the boffins at VW apparently decided that 20103 would no longer be the primary security code for the Instrument control module (at address Hex17) - I have no idea why!

As far as I know, no-one has done it yet, but here are a few suggestions as to how you might have the singular honour of being the first to discover the new security Code:

First a bit of theory:

• For all security code discovery processes, you first have to "open" the control module under test (this is essential). To do this, you MUST first enter a valid security code to find the rest of the security codes. This would appear to be a dilemma for the Instrument control module since 20103 is not a valid security code for MY15 and later NAR models. However, my understanding is that 25327 has been successfully used on your cars to solve the problem of the dash lighting not illuminating when the parkers are switched-on. So I beleive that 25327 is a good security code as the "seed" for the security code discovery process
• Security codes are (currently) a 5-digit number, so there are a maximum of 100,000 options that the discovery process must force poll. All of the polling process must be funnelled through the CAN Gateway and in a normal car lot's of other control modules want to also get access to the CAN Gateway. This means that there are many communication clashes on the CAN bus that must be resolved (by re-polling). THE SECURITY CODE DISCOVERY PROCESS IS VERY LONG! As an example, I built a simple CAN bus on a test bench to avoid comms clashes and the end-to-end process for a BCM test took about 10.5 hours (this was the only module connected to the CAN Gateway so comms speed was high)!

Suggestion #1:
OBD11 does have a security code finder facility, but I have never been able to use it successfully. The video below describes the process



Suggestion #2
VCP Pro cables also have a security code discovery process, which I have successfully used (and I know works). These are expensive cables and I assume that you don't own one. So you could find a forum colleague up there in USA that does own a cable and who is willing to participate in project. Given the time that it takes to fully complete a scan of the control module, I suggest that you break-up the exercise into "chunks" (i.e. smaller sessions each polling a section of the 100,000 numbers)

Suggestion #3
I'm happy to attempt the discovery process on my test bench CAN bus (using my VCP Pro cable), but I need a NAR 2016 Instrument control module, which I assume is not cheap to buy and ship down here - but the offer is there!!

Don