So - I must apologize in advance to the contributors on this thread, but notwithstanding the very-clever work done on the "Lighting configuration hypothesis" - something is seriously amiss here: to be brutally frank (or, I can be earnest if you want) the numbers just don't stack-up (I think)
Let's start with the basics: in my Audi A3,
IDE05145-Light configuration has the following setting ( = SW:5Q0-937-084-CQ HW:5Q0-937-084-CG;Component: MQBAB H H36 0253):
Code:
0C 34 00 14 02 00 64 03 00 00 00 00 00 00 00 00 0C 3E 00 15 04 00 64 05 00 00 00 00 00 00 00 00 04 48 00 4A 08 09
1A 1E 00 1A 14 00 7F 06 00 9A 04 4C 00 4C 08 0A 1A 1E 00 1A 14 00 7F 07 00 9A 01 48 00 49 14 08 7F 1E 09 7F 00 00
00 00 00 00 01 4C 00 4B 14 08 7F 1E 0A 7F 00 00 00 00 00 00 03 49 00 1A 0B 0F 7F 1E 00 7F 00 00 00 00 00 00
03 4D 00 1B 0C 0F 7F 1E 00 7F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2E 00 00 04 2E 00 64 00 00 00
00 00 00 00 00 00 02 37 00 1E 0D 0F 7F 00 00 00 00 00 00 00 00 00 02 41 00 1F 0E 0F 7F 00 00 00 00 00 00 00 00 00 17
38 00 5F 12 00 64 00 00 00 00 00 00 06 00 80 17 42 00 60 13 00 64 00 00 00 00 00 00 07 00 80
Now, this code-string will probably appear on your screens as very long number - but according to MS-Excel, the Byte count =224. If I divide 224 by the suggestion that each Lighting configuration-set ("config-set") has been allocated 16 x bytes - I get 14 x lamps (or, 7 x lamps for each headlight fitting).
For most (all?) platform vehicles, there is generally 35 x Leuchte-sets in total - and of these, there are indeed 14 x Leuchte-sets that can be considered as beloging to the front of the vehicle if the fog-lights are included. The fog lights should be included because sometimes the allied Leuchte-sets are used for the "all weather" lights, which are inbuilt into the headlight assembly.
So far so good - but:
As we are all aware, each Leuchte-set has 19 x adaptation channels. So, the hypothesis thus far postulated begs the question: how are the 16 x Bytes in the config-set allocated to 19 x adaptation channels in the Leuchte-set? Or, asked another way - which 3 x adaptation channels don't have a matching Byte in the config-set- and why?
There is an obvious answer for one of the Leuchte-set channels:
Lichtansteuerung HD AB is really only useful for the rear lights because it determines what happens when the hatch is open/closed. Clearly there is no need for a Byte in the config-set to mirror this channel setting because for the front lamps, the value is always set to "Always". This leaves 2 x channels per Leuchte-set without a corresponding config-set Byte - any ideas?
Don
PS:
Edit: Dimming Direction (maximize/minimize) is encoded in the brightness byte, as far as I see. Everyting below $80 is "maximize" (0-127 [$00-$7F]). Everything from this value on is "minimize" (0-127 [$80-$FF]). At least this is what I consider when looking at Somnus posted configuration for the DRLs - I suspect they turn while signal indicator is active on that specific side...?
@TBAx - again my apology, but in trying to apply the stuff already suggested in this thread to the Leuchte-sets in my Audi - I'm fairly certain that the Byte value
9A is the code for minimize. As support for my contention here is an extract from an early post from Somnus
I zeroed out the following lines for Leuchte4TFL
Code:
01 3A 00 49 14 00 7F [B][U]06 00 9A [/U][/B]08 09 7F 00 00 00
which
disabled the dimming when the turn signal was activated (06 00 9A), and the Parking light and Side Light (08 09 7F).
On my Audi - DRL wink happens on
Leuchte SL VLB10 and the associated command
Blinken links aktiv (beide Phasen) is placed on the Lichtfunktion GH pair - so the "minimze" setting happens further down the Leuchte-set than in Sonnus's case. Here is the comparable Byte-string on my car for
Leuchte SL VLB10:
Code:
04 48 00 4A 08 09 1A 1E 00 1A 14 00 7F [U][B]06 00 9A[/B][/U]
Notice the same pattern, ending in 9A-which I suspect is the code for minimize (I think)
EDIT: and my hunch (albeit said with much less commitment) is that "maximize" has the code
00
