Coding Anti-Dazzle and Variable Light Distribution

[alohart]

Alooha Art; Could you try and explain, in detail, what coding steps you performed in order to enable this feature? I have only done a couple of basic coding with my 2019 i3 (hold state of charge, passenger side mirror tilt, etc.), I'd like to do this but don't want to go down the "rabbit hole" and find myself screwing things up.

Did you read my post where I described in some detail the coding procedure I used? If so, what additional information would you like?

 

[TheAirman]

After playing around, I think that the car will only go into the active matrix mode at above 45 mph. So it might be speed dependent. Just like before coding the lights, using auto high beams, the car would never go into high beam automatically until above 25 mph.

The other night, at 35 mph, the car would act like normal auto high beam and dip to low for each approaching car. When I was on a two lane state highway at 45 and above, the lights would go into high beam and stay there even as a car approached, and you could see the segments darken and brighten with the blue light on the whole time. When I was on a 4 line divided highway(55mph+), the lights stayed high the whole time. Never did anyone flash me for blinding them.

 

[TheAirman]

Here's a good a good story I read on adaptive headlights in America:

https://www.cnn.com/2024/02/15/cars/headlights-tech-adaptable-high-beams-cars/index.html

 

[SSi3]

Here's a good a good story I read on adaptive headlights in America:

https://www.cnn.com/2024/02/15/cars/headlights-tech-adaptable-high-beams-cars/index.html

I read this yesterday too and was glad to finally see some explanation as to why OEMs in the US still aren’t activating ADB even tho NHTSA approved them 2 years ago. Even here in Canada I don’t see OEMs activating them, so far only Porsche Canada seems to have turned on their ADB matrix lights as they go into detail about exactly how they work on in their configurator, whereas Porsche US clearly states they aren’t fully matrix.

 

[SSi3]

Snapped a quick pic of my headlight because the lens is speckled with salt spray, so it shows off the separate LED segments quite well. Seems to have 6

 

[TheAirman]

Good catch. I was testing the 45 mph speed theory.

Going through town at 25-35 mph the auto high beams acted normal. When I got to the two lane highway at sped up to 45+, The blue light came on high beam even though a car was coming the other way. No flashing me.

When the car passed, another section of light came on and it got brighter. Must have been those 3 upper segments you show in the picture ?

 

[alohart]

Snapped a quick pic of my headlight because the lens is speckled with salt spray, so it shows off the separate LED segments quite well. Seems to have 6

Or maybe just 3. I don't know what the darker horizontal line between the main segments and the upper segments would be. I can almost imagine that there might be another horizontal line between the main segments and possible lower segments. Assuming that your photo shows the high beam only, I've not read of adaptive behavior that would turn on and off segments above or below the main segments. I could interpret your photo as showing the center segment that could turn off to avoid blinding a driver ahead in your lane and the right and left segments that could turn off to avoid blinding a driver in the opposite lane or the lanes to the left and right on a multilane highway. Apparently, the low beams remain on in this adaptive mode so that turning off segments doesn't result in inadequate illumination.

 

[Ojison]

It seems more segments when high beam is on.

 

[SSi3]

It seems more segments when high beam is on.

Nice! I'll have to try that on mine.

 

[SSi3]

With high beams on, 7 or 8 segments?

 

[jphughes3]

Did you read my post where I described in some detail the coding procedure I used? If so, what additional information would you like?

Alohart; Thanks again. One question with your instructions.

When you say "I chose vaules whose textual descriptions begin wii "i001", the i3 model/ I then noticed that changing the "i001" value also changed the vaules of the testual descriptions beginning with "F015", "F045", "F056" and "M013". I made those changes....."

Do you mean that you had to go to these textual descritions (i.e F015, F045, etc.) and changes those to the "i001" or just the lines you originally changed (i.e. 3073 laMaster1->C_AF; 3073 laMaster1->LUT; 3073 laMaster->C_HBA??????

Thanks,

John

I have 2019 i3 Rex

 

[alohart]

Alohart; Thanks again. One question with your instructions.

When you say "I chose vaules whose textual descriptions begin wii "i001", the i3 model/ I then noticed that changing the "i001" value also changed the vaules of the testual descriptions beginning with "F015", "F045", "F056" and "M013". I made those changes....."

Do you mean that you had to go to these textual descritions (i.e F015, F045, etc.) and changes those to the "i001" or just the lines you originally changed (i.e. 3073 laMaster1->C_AF; 3073 laMaster1->LUT; 3073 laMaster->C_HBA??????

Thanks,

John

I have 2019 i3 Rex

I simply set the 3 parameters that you listed to the values whose textual descriptions had "I001" prefixes. The numeric values underlying these descriptions are hexadecimal numbers (i.e., they begin with "0x") that apparently affect the behaviors of other BMW vehicles as well. This must be why there are descriptions whose prefixes are "F015", "F045", etc., even though their underlying hexadecimal values are the same as those underlying the "I001" descriptions. I had never encountered value choices whose descriptions corresponded to various BMW models. Just ignore any value descriptions that don't have an "I001" prefix.

Another oddity was the value choices for the 3073 LaMaster1->LUT_FLC_FORWARDLIGHTING_Y parameter. The value described by "I001_mit_AFS" is a list of 3 values: 0x9C 0x9C 0x9C. I don't have any documentation that explains any of this, so I don't question it since it seems to do what I wanted.

 

[Jenss4/i3s]

I did the programming over the weekend and have been noticing my car appears to have a hard time with cars directly in front of it. I'm unsure if my headlights are aimed weird or if the system just isn't detecting cars. Is it possible there's a system calibration that is supposed to be done?

 

[tongsli]

Change to I001_enable

 

[tongsli]

 

[Jenss4/i3s]

View attachment 692View attachment 693

Is this from BimmerCode? Mine wouldn't let me select multiple options in each control menu when I was changing the settings alohart listed. Do you currently have the system working on your car?

 

[tongsli]

yes the screen shots are from Bimmercode. I didn't have any problem changing each section and then coding it when I was done making changes. I have not tested it because I live in the City and need to find roads dark enough to try.

I assume you have the full version of Bimmercode?

 

[Jenss4/i3s]

Interesting, I'll have to look at that again. Yes I have purchased the full version of BimmerCode for Android. The way I understood previous posts about the coding was only I001 is for the i3 and the other Fxxx is for other BMW models. In your screenshots there's multiple if the LUT_FLC_FORWARDLIGHTING menus open but the y or x end character is cut off. Did you change settings in both?

 

[tongsli]

I only changed LUT_FLC_Forwardlighting_Y as per Alohart's instructions. Sorry about the cut off, the screen shot shows it that way.

A side note: when you change this section there are multiple lines of I001_Mit_AFS. When you change one, they all change. I assume it's because you are changing 0X9c, 0X9C, 0X9C

 

[Jenss4/i3s]

I'll definitely have to look at my computer again. When I selected I001_MIT_AFS it only changed the one line of it that also changes the 0X9c....... Codes

So far one of my co workers was slaying that on the drive home last night one of my lights was bright and one wasn't. I may also not be aimed left to right correctly.