I had also missed the differences between *TAGFAHRL_1* and *TAGFAHRL_2* I note that the variable *DEPENDENCY_FUNC* is different for the two modes. Could the difference between them ("function 1") be use of the check-box in the car's driver UI that selects the DRL functionality? If so *_1* is "DRLs on" and *_2* is "DRLs off"

 

Correction to the last sentence in my last post: should read <If so *_1* is "DRL functionality on" and *_2* is "DRL functionality off">

 

Important not to interpret the language in the parameter names loosely or generically. The “function” (which FUNC is short for) parameters I’ve consistently observed have been specific values with specific meanings — in particular, values in that function list I mentioned. So I’m thinking no to it being a generic on/off linked to a UI that the param block makes no reference to.

Also, over in BMW forums I’ve seen examples where the dependency function — again, a value from the function table — is a function that acts as a control. An example would be a left turn signal as specified dependency — turn it on, and you turn whatever is controlled by the parameter block off (if I’m remembering correctly).

 

It would appear that the connection of the angel eyes to the *TAGFAHRL* system is not done in the list of variables we have been concentrating on. Perhaps the connection is made as a *PART_OF* setting in a different lighting mapping set of variables that cover the wider use of the "leuchtring" (eg. in parking light and headlight clusters as well as DRLs). Worth looking at the full lighting mapping listing to see if there is such a group of variables.

 

Agreed that the connection is assuredly elsewhere.

For my part, I unfortunately don’t have a full list of lighting parameters, and I have no list of known/confirmed intersections with other not-TAGFAHRL-named sections. We’ve hit the limit of my current understanding. For what it’s worth, though, I did go through all the parameters in the LceLampMapping sections (3061-3065) looking for that needle in a haystack, at the end of last year. Didn’t find it. It has to exist somewhere, but I don’t know where.

 

Not sure I understand completely. If the *_1*/*_2* difference in the *FUNC* variable is between 0x00 and 0x06 (called "function_1" - I assume your listing misprints the *_2* value as 0x00 when it should be 0x06) then couldn't function_1 flip its value when the DRL UI checkbox is checked/unchecked?

 

To my knowledge there is no misprint, but I had to hand build the document I have those values in. I’ll double-check it tomorrow.

More importantly, there is nothing in this data stating or suggesting that the FUNC parameter you reference is tethered to the DRL on/off switch in the UI. There are FUNC variables of this kind for many, many base lighting items in sections 3061-3065. Without some specific evidence or documentation that the parameter you’re talking about is tied to that specific UI tick box (or to any viewable UI item at all, actually), it’s an assumption and a maybe at best, requiring some proof, along with definitive information on hex values that will be acceptable to the software (and what those values mean to the software).

 

I tried changing MAPPING_NEBELSCHW_L_PART_OF to 0x04. Sadly the fog light did not come on when the DRL's are activated.

I have reached my own dead-end now on this. We had a good run at it. Our only remaining hope is that a more DRL-knowledgeable person reads this thread and can see what we are missing.