Ah, thank you Don! It was late, and I had spent way too long upside down underneath my dash when I wrote this. I may have confused which addresses I have access to long coding. I believe I was able to figure this out and will be moving forward with the coding today.Sean: great to read that your learning curve progresses unabated !!
Whilst I personally reckon that whoever authored the descriptors for the software switches on the Long Coding Helper (LCH) screens have done an excellent job - I'm not sure that you should expect great clarity from these labels (mostly because of the short, allowable field length)
In regard to your question - perhaps I can share a suggestion that I use in such occasions in the hope that it might help; as you may have understood, the new HEX series cables/dongles allow the user to access 2 x separate LCH screens; the normal VCDS screens and the so-called "Yellow" screens. As a personal aside, I ignore entirely the "risk" message that VCDS displays regarding the veracity of the information in the yellow screens - I've compared this information with other well known and well respected diagnostic devices and the data seems to be identical to that in the VCDS yellow LCH screens. I personally have complete confidence in this information
So - when I'm puzzled about the meaning of the descriptor in the LCH screen, I often find it instructive to look at the descriptor on the other screen version. This approach isn't always successful - but it often does help!.
In respect of your particular question - here is the comparison:
As you can see - the yellow LCH screen says that this Bit refers to the Dynamic AFS light. Of course leveling is normally part of non-incandescent headlight fittings (by law in most countries) - but I'm not sure why the non-yellow screen refers particularly to "levelling".
I'm tempted to believe the (risky) yellow LCH screen; I'm guessing that Byte 4, Bit 3 enables the light on the dashboard that indicates when high-beam assist is operational (i.e. the blue high-beam light with "AUTO") - I think. I've checked a couple of cars on my database and the long-code strings tend to confirm my hypothesis!!
I've also looked at the WD and there is no physical wire from J285 (i.e. the hex17 module) to any component on the dynamic AFS system - so I assume that the Bit 3 software switch is purely a CAN message enabling facility - I think
Don
PS: Interesting spelling of "leveling/levelling" ; label clearly authored by a non-American!!
PPS: Confused about reference to hex17 module and "decoding a long code to adaptation"; the task of translation of long-code to channels is ONLY required on BCM for late model MQB vehicles!
I was able to finish most of my install, but my harness connector for the Fuse box must be incorrect as I can't get it to engage from the rear even with the lower lock undone. I'll more than likely just snip it and use a tap a fuse/piggyback fuse connection for power.
I'll update if I run into any issues, but I think I have most of the coding sorted now along with Zero815's walkthrough on NAR Bi-xenon to Osram.
Thank you,
Sean