Printable View
Lights are daytime running thanks to the changes in the adaptation
Thanks Don
When the dipped headlights are on, they do not light up as daytime running lights
Parking lights do not work after removing the key, do not light up in the front lamps. they only light up in the rear lamps
@memus: I think that you are saying that my suggestions worked (at least in part)- but I'm not entirely sure?
In regards to the dipped headlight matter - yes, that's the way that VW coded the Leuchte-sets for the left/right side DRLs. As factory set, the DRLs were coded so that they did NOT illuminate when the low-beam lights turned -ON. This is because the DRLs (on genuine OEM headlight fittings for a mk7 that used incandescent lamps) shared the same physical lamp base as the high-beam lamp (i.e. it's a H15 lamp base with 2 x separate filaments). This means that the incandescent DRL lamp also shared the same reflector as the high-beam lamp - which as you will know, does NOT have cut-off characteristic. So just as illuminating the high-beam lamp would blind on-coming vehicles, it must have been considered by VW that turning-ON the DRLs during night-time would do the same (I guess)
As factory-set and other than the normal daylight function, incandescent DRL lamps were coded on a mk7 to turn-on ONLY when the rotary light switch was in the Attachment 55139 position (i.e. when dipped-beam was OFF) and in this mode, the DRLs were dimmed to 31%.
So, if you are of the opinion that your LED DRLs won't blind on-coming vehicles - try this (I wote a more fulsome instruction-set HERE):
For Leuchte4TFL LB4 and Leuchte5 TFL RB32
- ONLY IF Lichtfunktion E is set to Standlicht vorn (Positionslicht; Begrenzungslicht), change to Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht)
- With the above change made, adjust the illumination level to suit night-time operation of the DRL by tweaking the value of Dimmwert EF (factory setting=31). I'm not sure if the LEDs in your new fittings will tolerate dimmed operation - if not, you might need to set the channel to max value = 100. In this case, make sure that the blinding effect for on-coming vehicles doesn't happen - please
Again, don't make these changes if the existing setting for Lichtfunktion E is not as indicated.
OK, next matter !
It's not clear to me what you mean by "Parking lights do not work after removing the key, do not light up in the front lamps. they only light up in the rear lamps".
On a Golf mk7, the Parking-Lights/Position-Lights "do not work after removing the key" as factory coded (unless the turn-signal stalk is left in one of the car-side positions). This is normal behavior!
If your "rear-lamps" do remain switched-ON as Parking Lights after key removal - then I'm guessing that they are coded as Coming/Leaving Home - is this what you are referring to?
If you want the side-lights to operate as CH/LH, do this:
For Leuchte2SL VLB10 and Leuchte3SL VRB21
- Lichtfunktion C >Coming Home oder Leaving Home aktiv
- Dimmwert CD > 127 [100]
Again, I don't know if the side-lights are LED, or incandescent. If the latter, use the square bracketed value
Don
Hi All, I've just started playing with a 2019 Golf Wagon, boy what a learning curve! Slowly getting the hang of it.
I haven't been able to find what this actually changes, as I'd like to change it in VCDS: https://obdeleven.com/supported-vehi...-roller-blind=
I'm also looking to see if it's possible to not have the front fog lights come on, if the rear fog light is on. I find it strange, as for example during the night it's not legal here to have the front fogs on with the headlights, however you can with the rear fogs. But you can't get the rear on without the front!
@yorky: Hi and welcome to the wonderful world of VW coding!! I'm sure that you will have an enjoyable learning experience as you navigate the mysteries of diagnostic devices - like VCDS!
So, as for your specific question - I don't know the answer, but I can make a suggestion that might enable you to find a way forward.
Not sure if you are aware, but the modules in your Golf mk7.5 use 2 x different protocols for messaging to one another. The primary skeleton for communication is called CAN (Controller Area Network) and it's the high-speed facility that connects most of the key modules together.
Separate to this is something called "LIN" (Local interconnect network). As the name implies, LIN is a localized smaller network that lots of modules use when the thing being controlled is really only of interest to a single CAN module. On LIN based system, there is ONE LIN-master module (this module is also a CAN based module) and up-to 16 x LIN-slave modules
The reason for describing this is because the Sunroof Roller Blind module is a LIN-slave to a LIN-master module which VCDS calls the Cent. Elect. module (J519) . In the VW wiring diagrams, the Sunroof Blind module is known as "J394". If you look at the SCAN for this car- you should find the Sunroof Roller Blind module reported like this:
Of course the details on your car will be different -but notice Subsystem 4 and notice also that this module has a "Coding" string - which VCDS calls "Long-Code.Code:
-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519) Labels:| 5Q0-937-08X-MV1.clb
Part No SW: 5Q0 937 087 AA HW: 5Q0 937 087 AA
Component: BCM PQ37BOSCH 028 0163
Revision: -------- Serial number: 865802071600X9
Coding: 005118464041826969E44000001407201800000000000000000000000000
Shop #: WSC 00066 790 00200
ASAM Dataset: EV_BodyContrModul1UDSBosc 015001
ROD: EV_BCMBOSCH_015.rod
VCID: FAB7F1BE7DAE8E9B89-80AE
Control Unit For Wiper Motor:
Subsystem 1 - Part No SW: 5GM 955 119 HW: 5GM 955 119 Labels: 5QX-955-119-V1.CLB
Component: WWS 160810 043 0581
Serial number: 160817225010
Coding: 0E4DDD
Rain Light Recognition Sensor:
Subsystem 2 - Part No SW: 5Q0 955 559 B HW: 5Q0 955 559 B Labels: 5Q0-955-547.CLB
Component: RLS 042 0105
Serial number: S3Y16M06D29H07M39S07
Coding: 00A8DD
Sun Roof:
Subsystem 3 - Part No SW: 5G0 959 591 A HW: 8V3 959 591 A
Component: J245 PS22.409 H03 0004
Serial number: 0000FST000XU77500000
Coding: 191800
Roof Blind:
Subsystem 4 - Part No SW: 5G0 959 591 A HW: 8V3 959 591 A
Component: J394 PS22.409 H03 0004
Serial number: 0000FST000XU6PM00000
Coding: 191800
No fault code found
So, my guess is that you will find the answer to your question if you navigate to the Subsystem 4 module -> then select Coding -> then select Long Coding Helper -> then look through the descriptors on the Bits for each Byte
As for your front fog light question - yes this is possible. Do this:
In the Cent. Elect. module @ address 09 - go to Adaptation and make these changes:
for Leuchte12NL LB45 and Leuchte13NL RB5
- Lichtfunktion G > Nebelschlusslicht wenn kein Anhaenger gesteckt (not active)
- Dimming Direction GH 13 > minimize (maximize)
The setting in brackets above are the existing values - ONLY proceed if these are current in your module
Don
Thanks! I've read a lot of your posts, and your dedication to public knowledge is simply fantastic.
I'll have a look for that subsystem shortly, and look at the fog light thing, that's awesome that it's as easy as that!
A couple more questions popped into my head, I've just received some LED front fog lights, and a straight swap hasn't brought up any faults. Does this mean I don't need to change any codes? It's this one (they are extremely bright!) VW Golf Mk7 Remnant LED Fog Light 6000K (Pair)
– Supernova Lighting
And I've tried to enable the alarm via the below link (and I've seen similar settings around as well, no I don't have the factory alarm), however VCDS says in the coding of 09 (BCM PQ37BOSCH xxx xxxx) current coding all zeros and it can't access it. Any ideas if it's still possible to enable the alarm via horn? I've done all the adaptions.
How to activate anti theft system alarm on VW Golf 7 /VCDS VAG tutorial/ - YouTube
Subsystem 4 (J394) in VCDS comes up with the message no coding information is available. Should I send that off to Ross Tech? The auto scan of 09 only displays the first subsystem component I think, and I'm not sure what the controller channel map is.
The fog light thing worked very well, thank you :)
Many thanks for the kind words - and yes, I do happen to believe in the value of sharing information on public forums like this. DIY is not everyone's thing - but for those folk that are interested, knowledge is crucial to a successful experience!!Quote:
Originally Posted by yorky
hmm........ this ain't the first time this question has been asked!! If incandescent lights have been replaced with LED version lamps and no errors have resulted, the answer to your question is - it depends on what type of person you are!! :rolleyes:.Quote:
Originally Posted by yorky
I'm a simple bloke - so I like to segregate DIY-ers into 2 x categories: those that simply want an outcome and those that want a technically correct outcome!! I make no value judgement between the two; neither is better than the other - they are just different!!
The module that controls the 35 x exterior lights on a mk7/mk7.5 is a very sophisticated device (see the bare motherboard below) This module can differentiate between incandescent and LED lamps and it can manage the operation of both lamp types differently. Incandescent lamps can be managed with analogue controls and LED lamps can use digital control methods.
The module (lets call it the "BCM" - for Body Control Module) is told which lamp type is plugged into the lamp socket by the setting on the Lasttyp channel in the Leuchte-set. For this car, the BCM believes that incandescent lamps are still installed for the front fogs and it is operating the new LED lamps in analogue mode. Ain't nothing wrong with this because there are no errors!! However, the BCM is being told porkies!! I have an engineering background - so I personally NEVER lie to BCMs!!
https://www.vwwatercooled.com.au/for...g9O0png1-1.jpg
So, here's the thing about "the coding of 09" (again, let's call this the BCM) - around mid 2016, the deities on the VW mother-ship decided to fundamentally change the design of BCMs on MQB platform cars like your Golf. As a result of these changes, ALL newer BCMs lost their long-code strings and these software switches in the older modules were transferred to the adaptation channel database in newer modules. This had the impact of increasing the already huge adaptation channel count in the BCM even more and VCDS started to reported "coding all zeros" in newer modules. Clearly this car has a newer module because it's a MY19 vehicleQuote:
Originally Posted by yorky
So, the long-code change in your video is Byte 12, Bit 4 - in newer BCMs, this translates to:
- IDE04928-ENG141960-Anti-theft device-Anti-theft alarm system
I'm really not sure that this tweak will work - but I suggest that you give it a try. As I said, newer BCMs have a different adaptation database. If you look at the way that adaptation channels are reported by VCDS, they have following structure:
- Parent TAG-Child TAG-Parent Name- Child Name
Look at the anti theft channel above and you should recognize the structural elements which are separated by "-" (ignore the "-" in "Anti-theft")
The words that I've used in my structure above are NOT Ross-Tech sanctioned - these terms are my words which I've thieved from the structure of relational databases. My observation of the structure of adaptation databases in modules is that a Parent TAG/Name may be repeated on more than one Child TAG/Name channels - but a Child TAG/Name may not (meaning that Child TAG/Names are unique in the database)
On your newer BCM, some of the Parent TAG/Names also changed. So, when finding the adaptation channel names in your video - search instead for the Child Name
hmm........ OK, I'm not entirely sure what is being said about J394 on this car! To repeat my previous reply, J394 should be reported like this:Quote:
Originally Posted by yorky
Roof Blind:
Subsystem 4 - Part No SW: 5G0 959 591 A HW: 8V3 959 591 A
Component: J394 PS22.409 H03 0004
Serial number: 0000FST000XU6PM00000
Coding: 191800
If your version J394 has an entry like that bolded above - it will have a long-code string. However, VCDS may not have a label file (which populates the software switch descriptors in the long code helper screens) for the module. This can result in your message.
Don
Thanks Don, I've set the fog's to allgemeine LED.Quote:
Originally Posted by DV52
I also found the alarm in the adaptations... Swear I searched for it before but anyway, enabled and the horn goes bananas if I open the door without disarming woo!
The roof blind is that subsystem, however the code is 191900.
Couple other questions.
I had seen a couple of ways of getting the battery State of Charge (SOC), with one being to hold the trip reset with the vehicle off, and another being an adaptation I think. However neither work for me. Do you know of a current way of displaying this?
This ones probably not for here, however one of the FM radio channels is coming through way louder than the rest, which is odd, as several other cars I've been in recently don't do it. Seen anything that has anything to do with that?
Then next up, learning some more about lights. I'm going to first try enabling the inner boot lights as brake lights as well. I've come across your document "How MQB platform vehicles control external lights - preliminary observations", however there is no date on it, was there only one version of that?
I tried "State of charge " and because most of the models dont have the module on the battery it wont work. Spent hours before I found out why. If only wires at end of - terminal it wont work . Needs a little box there.