Anti Dazzle Solved

[alphaod]

I don't have the driver's side hump with auto low beam on.

[iconoclast]

Originally Posted by alphaod

I don't have the driver's side hump with auto low beam on.

is your's coded correctly?

if i put the vehicle in reverse or initiate the fog lights the double hump comes back:



as soon as i put in drive or auto it disappears but the passenger side remains. this is indicative of "tourist solution". i have a feeling mine is coded improperly as yours may be too.

[Irishfan]

Hey All - I posted this to the Bimmerfest coding forum, but it seems like this might be a better place to get some insights. Thanks in advance for any help!

So, last December, following the excellent instructions on the PDF that circulated a while back (dated Dec. 14, 2015), I was able to successfully code the glare-free high beams on my pre-2016 F15. They worked amazingly well!

However, unfortunately, the car was brought in for service for an unrelated issue, and the system was re-coded to factory settings. I've since re-instated all my old settings, and the only thing that doesn't work the way it used to is - you guessed it - the glare free high beams. I've checked and re-checked that the appropriate VO codes are removed and changed the appropriate values in the two LHM ECU's (all sixteen of them are correct, including werte values). However, the high beams still won't function like they used to - they're back to the very distinct on/off USA functionality.

Does anyone have any ideas on how to proceed? I really miss this feature.

Before anyone asks, I'm not sure what version of the F15 software was installed by the service update. For reference, the update took place in the first week of April 2016. If there's a better way to tell what version I'm using, I'd appreciate a quick tutorial. Thanks!

[alphaod]

Originally Posted by iconoclast

is your's coded correctly?

if i put the vehicle in reverse or initiate the fog lights the double hump comes back:



as soon as i put in drive or auto it disappears but the passenger side remains. this is indicative of "tourist solution". i have a feeling mine is coded improperly as yours may be too.

Yeah not sure if it's correct or not, but I followed the directions to the letter, checked and double-checked.

If I put into reverse I get the double humps. Otherwise it's only passenger-side hump. If I look at the light, clearly part of the driver's side LED is shut off.

They come back on when GFHB is working, with manual highbeams, when in reverse, and when fog lights are on.

[iconoclast]

exact scenario i have... coding was done properly but this is the end result. as you stated above i can clearly see one of the diodes are not illuminated on the driver's side but once i go into reverse or put the fogs on or manually engage the headlights the lighting returns to the traditional NAR double hump beam pattern. very odd behavior.

[Hang0ver]

Originally Posted by iconoclast

exact scenario i have... coding was done properly but this is the end result. as you stated above i can clearly see one of the diodes are not illuminated on the driver's side but once i go into reverse or put the fogs on or manually engage the headlights the lighting returns to the traditional NAR double hump beam pattern. very odd behavior.

Same as you described for me. Did you test if the anti dazzle is working or not?

[dmnc02]

Originally Posted by iconoclast

if i put the vehicle in reverse or initiate the fog lights the double hump comes back:

This is normal behavior. See this post for an explanation of what is happening.

[iconoclast]

Originally Posted by Hang0ver

Same as you described for me. Did you test if the anti dazzle is working or not?

it works perfectly fine. drove in the fog and late at night and it operates as designed but i fear i am not getting all the light i could or should since it appears there is a tourist solution feature enabled judging by the beam pattern.

Originally Posted by dmnc02

This is normal behavior. See this post for an explanation of what is happening.

excellent! thank you very much for the help. when i coded my audi vehicles the functionality of "autobahnlicht" was similar to that of bmw's anti-dazzle however the beam pattern remained the same whether you coded for e-code headlights or NAR but then they changed if you enabled the "tourist solution" which then dips the driver's side headlight. which is the beam pattern i see when in bmw's "city mode". thanks for the explanation!

[dmnc02]

Originally Posted by Almaretto

So I finally got around to coding my F15, and I had a couple questions about the NGHB values.

2016 F15 xdrive40e with Zeitkriterium 0815 & F025-15-11-503.

After removing 5AP and 8S4 and VO Coding, I used TM NCD / CAFD Tool to compare my FLE 43 (Left = CAFD_000024C3_008_010_000.ncd) to posted FLE (Right = CAFD_000024C3_008_007_002.ncd).

Besides the required posted changes (NGHB F15 v2 - Jan 8, 2016), I had some additional differences and wondered if those were required as well.

There is a set of values that are completely different:

LWR_STROM_HALT_TT	Left: F020Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F030Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F010Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F045Wert = 39	Right: F010Wert = 50
LWR_STROM_HALT_TT	Left: F015Wert = 39	Right: F010Wert = 50

LWR_VORBEST_ZEIT	Left: F020Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F030Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F010Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F045Wert = 07	Right: F020Wert = 00
LWR_VORBEST_ZEIT	Left: F015Wert = 07	Right: F020Wert = 00

AHL_STROM_HALT_TT	Left: F020Wert_SA552_ECE = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F020Wert_SA552_WL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_ECE_LA_LL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_ECE_LA_RL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F030Wert_SA552_US = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_ECE_LA_LL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_ECE_LA_RL = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F010Wert_SA552_US = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_STROM_HALT_TT	Left: F015Wert = 39	Right: F010Wert_SA552_ECE_LA_LL = 50
AHL_VORBEST_ZEIT	Left: F020Wert_SA552_ECE = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F020Wert_SA552_WL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_ECE_LA_LL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_ECE_LA_RL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F030Wert_SA552_US = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_ECE_LA_LL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_ECE_LA_RL = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F010Wert_SA552_US = 07	Right: F020Wert = 00
AHL_VORBEST_ZEIT	Left: F015Wert = 07	Right: F020Wert = 00

Then, there is a set of values, where drop-down is different, but same werte:

LWR_V_MIN	        Left: F020Wert = 64 00	Right: F010Wert = 64 00
LWR_V_MIN	 	Left: F030Wert = 64 00	Right: F010Wert = 64 00
LWR_ACC			Left: F020Wert = E0 2E	Right: F030Wert_F34_SA5A2_ECE = E0 2E
LWR_ACC			Left: F030Wert = E0 2E	Right: F030Wert_F34_SA5A2_ECE = E0 2E
CORNL_Idx		Left: F030Wert_SA552_US = 01 01 01 01 01 01 01 01 01 01	Right: F020Wert = 01 01 01 01 01 01 01 01 01 01
ECO1_Idx		Left: F030Wert_SA552_US = 01 01 01 01 01 01 01 01 01 01	Right: F020Wert = 01 01 01 01 01 01 01 01 01 01
SIDEMRKLGT_Idx		Left: F015Wert_SA552_SAE = 01 01 01 0C 01 01 01 01 01 01	Right: UNKNOWN = 01 01 01 0F 01 01 01 01 01 01


LmmIdx00_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx01_Intensity	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_TimeOn		Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_TimeOff	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx01_Priority	Left: F030Wert_SA552_US = 0F	Right: F020Wert = 0F
LmmIdx02_Intensity	Left: F010Wert_SA552_US = 5D	Right: F015Wert = 5D
LmmIdx04_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx06_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx07_Priority	Left: F030Wert_SA552_US = 01	Right: F030Wert_SA552_ECE_LA_LL = 01
LmmIdx07_RampType	Left: F030Wert_SA552_US = 00	Right: F020Wert = 00
LmmIdx09_Priority	Left: F030Wert_SA552_US = 03	Right: F015Wert = 03
LmmIdx10_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx10_Intensity	Left: F030Wert_SA552_US = 64	Right: F030Wert_SA552_ECE_LA_LL = 64
LmmIdx10_Priority	Left: F030Wert_SA552_ECE_LA_RL = 02	Right: F030Wert_SA552_ECE_LA_LL = 02
LmmIdx12_Priority	Left: F030Wert_SA552_ECE_LA_RL = 03	Right: F030Wert_SA552_ECE_LA_LL = 03
LmmIdx13_Intensity	Left: F030Wert_SA552_US = 64	Right: F010Wert = 64
LmmIdx14_Priority	Left: F030Wert_SA552_ECE_LA_RL = 04	Right: F030Wert_SA552_ECE_LA_LL = 04
LmmIdx14_Priority	Left: F030Wert_SA552_US = 04	Right: F030Wert_SA552_ECE_LA_LL = 04
LmmIdx14_ErrorImpact	Left: F030Wert_SA552_US = 01	Right: F015Wert = 01
LmmIdx15_Intensity	Left: F030Wert_SA552_ECE_LA_RL = 64	Right: F030Wert_SA552_ECE_LA_LL = 64


LM06_CURRENT_BINNING_CLASS0	Left: F045Wert = 20 03	Right: F015Wert = 20 03

Also, just to confirm, FLE 43 and FLE 44 get the same changes (ie right vs left does not matter)?

Thanks

I have been away from the forum for a few weeks, so I am resurrecting some old unanswered posts

It is normal for BMW to slightly tweak the settings from one release of PSdZData to the next and this can be due to a variety of reasons. I clearly stated in post #108 that the CAFD/NCD file was being posted only as a temporary solution and should not been used on cars with newer CAFDs (the PDF is the only relevant source for those cars). The changes you noticed refer to the operating parameters for the stepper motors in the headlight and should be left to their factory values (they are not listed in the PDF).

As for the parameters that have different literal values but the same Werte values, this is due to mapping inconsistencies in E-Sys Launcher (PSdZData is now trimmed and the literal values are mapped back dynamically by E-Sys Launcher, a process that is not error-proof). The Werte values are all that matters and that is the reason they are listed in the PDF.

[dmnc02]

Originally Posted by E90325M

E-SYS: 3.27.1
E-Sys Launcher Premium: V2.0.
PSdZData: V.57.2_PSdZData_Lite.
Vehicle: 2016 X5 Xdrive 35i M-Sport (built Oct.2015)

Hey, guys, I finally begin my 2016 X5 coding. My car come with U.S $1900 Lighting Package so I believed that it should be able to code Anti-Dazzle, correct?

Anyway, I begin to follow the PDF V2 Appendix 2 instructions step by step. After I finished the step 1, I start to modify 22 + 79 functions both in FLE according to the PDF contents. But only modified some of them I found some functions did not have the value "F015Wert" from Edit-->drop-down menu. I checked more afterward,indeed there are a lot conflicts with the PDF table and I have to stop it.

Here are some examples:

FLE ECU "H_Plus4_Idx" does not has value “F015Wert”.
FLE ECU "WELL3_Idx" has default value "Unkown" and no "F015Wert" value to be choosen.
FLE ECU "PANICMODE_Idx" has default value "Unkown" and no "F015Wert" value to be choosen.
......

Then I download the modified ncd file provided by dmnc02 and use the method to program the ncd file into my car. Last night, I drive out and try to verify the Anti-dazzle function. but It seem Anti-Dazzle does not work as expected...

Today, I connected my car again and read out the FLE ECU config data and compared with the downloaded one. They are different on the bottom of file.

any help and thoughts?

This is a good example of the mapping issues with E-Sys Launcher mentioned in my post above.

In your case, if you simply update your version of E-Sys Launcher to the current version, one of the literal values that appears as "Unknown" with the version you are using will magically change to "F015Wert".

[Almaretto]

Originally Posted by dmnc02

It is normal for BMW to slightly tweak the settings from one release of PSdZData to the next and this can be due to a variety of reasons. The changes you noticed refer to the operating parameters for the stepper motors in the headlight and should be left to their factory values (they are not listed in the PDF).

I was guessing that to be the case, but thanks for the confirmation.

[E90325M]

Today I got my 2016 X5 35i M-sport (with Lighting package) Anti-Dazzle function enabled and went out for test drive for 15 minutes and I thought Anti-Dazzle function was properly enabled this time...
I was following the simple steps which dmnc02 gave.

Coding thread here: http://f15.bimmerpost.com/forums/sho...k+door&page=90

The software versions I used listed at below:

E-SYS: 3.27.1
E-Sys Launcher Premium: V2.5.3.108.
PSdZData: V.58.2_PSdZData_Lite.
Vehicle: 2016 X5 Xdrive 35i M-Sport (built Oct.2015)

Previously I followed the V2 PDF steps to program 22+79 and it didn't make the Anti-Dazzle function worked as expected. If you have a 2016 X5 35i with LED then you can follow this simple steps for a try. Luck that your car will be Anti Dazzle enabled!!!

Originally Posted by dmnc02 View Post
In case somebody else with a 2016 wants to try activating Anti-Dazzle as 08bmw128i did, I posted the relevant coding on the other forum (http://www.bimmerfest.com/forums/sho...&postcount=925), but it might be worth repeating here:

STEP 1

Remove 5AP and 8S4 from FA and VO code BDC_BODY, FLA or KAFAS (whichever is present) and both FLEs.

STEP 2

FDL code the following 5 parameters in both FLEs:

Stadt_V_Idx: F015Wert = 04 01 01 01 02 03 01 01 05 01
SAE_Idx: F015Wert = 04 01 01 01 02 03 01 01 01 01
H_plus4_Idx: F010Wert_SA552_US = 04 01 01 01 02 03 01 01 01 01
Blendfreies_Fernlicht_Idx: F015Wert = 01 06 01 01 06 06 01 01 01 01
Volles_Fernlicht__Lichthupe_Idx: F015Wert = 07 07 01 01 07 07 07 01 01 01

NOTE

The above requires adaptive LEDs (option code 552) and High Beam Assistant (5AC). It also requires a 2016 model with the new FLE ECUs for the headlights.

If you coded your car before, please don't VO code BDC_BODY (that will erase all coding you have done), Just VO code both FLEs then followed the step 2 above.

Thanks dmnc02 and 08bmw128i

[yk1988]

I just coded my f16 build 11/15 yesterday, spent 2 hrs on change all the values,no error code during the process.

But i dont know how to enable the GFHB? Just press the "HBA" button? Does it also come active if i turn high beam on manually?

I did a test drive with "HBA" turn on, but the high beam didnt turn on all the time, maybe too many street light? It is in the city.

[dmnc02]

Originally Posted by E90325M

Today I got my 2016 X5 35i M-sport (with Lighting package) Anti-Dazzle function enabled and went out for test drive for 15 minutes and I thought Anti-Dazzle function was properly enabled this time...
I was following the simple steps which dmnc02 gave.

Coding thread here: http://f15.bimmerpost.com/forums/sho...k+door&page=90

The software versions I used listed at below:

E-SYS: 3.27.1
E-Sys Launcher Premium: V2.5.3.108.
PSdZData: V.58.2_PSdZData_Lite.
Vehicle: 2016 X5 Xdrive 35i M-Sport (built Oct.2015)

Previously I followed the V2 PDF steps to program 22+79 and it didn't make the Anti-Dazzle function worked as expected. If you have a 2016 X5 35i with LED then you can follow this simple steps for a try. Luck that your car will be Anti Dazzle enabled!!!

If you coded your car before, please don't VO code BDC_BODY (that will erase all coding you have done), Just VO code both FLEs then followed the step 2 above.

Thanks dmnc02 and 08bmw128i

I am glad you are happy with the way NGHB is working on your F15. However, if you find that the V1 coding works better on your car than the V2, I strongly suspect that something might not have been coded correctly in V2: it is a long coding and missing one FDL can mess up everything.

My suggestion would be to give V2 another try at some point down the road. If you send me you NCD files, I can even confirm your coding. As you mention, once you have VO coded BDC_BODY, there is no need to do it again and so recoding NGHB will not cause you to lose your other coding.

[dmnc02]

Originally Posted by yk1988

I just coded my f16 build 11/15 yesterday, spent 2 hrs on change all the values,no error code during the process.

But i dont know how to enable the GFHB? Just press the "HBA" button? Does it also come active if i turn high beam on manually?

I did a test drive with "HBA" turn on, but the high beam didnt turn on all the time, maybe too many street light? It is in the city.

In order to enable GFHB, the light switch must be in the "Auto" position, your speed must be above 45mph, the ambient lighting must be below a given threshold (this is due to European regulations that forbid the use of high beams in urban centers with street lighting, although the threshold is set higher for North American vehicles) and the traffic around you must allow the activation of the tunnel without creating glare for other drivers.

[E90325M]

Originally Posted by dmnc02

I am glad you are happy with the way NGHB is working on your F15. However, if you find that the V1 coding works better on your car than the V2, I strongly suspect that something might not have been coded correctly in V2: it is a long coding and missing one FDL can mess up everything.

My suggestion would be to give V2 another try at some point down the road. If you send me you NCD files, I can even confirm your coding. As you mention, once you have VO coded BDC_BODY, there is no need to do it again and so recoding NGHB will not cause you to lose your other coding.

Absolutely I'll try when I find another opps. At the moment seems V1 worked on my car.

[yk1988]

Originally Posted by dmnc02

In order to enable GFHB, the light switch must be in the "Auto" position, your speed must be above 45mph, the ambient lighting must be below a given threshold (this is due to European regulations that forbid the use of high beams in urban centers with street lighting, although the threshold is set higher for North American vehicles) and the traffic around you must allow the activation of the tunnel without creating glare for other drivers.

I see, another question.

In my ECUs, i didn't see KAFAS, i only have KAFAS2. Is that normal?

[dmnc02]

Originally Posted by yk1988

I see, another question.

In my ECUs, i didn't see KAFAS, i only have KAFAS2. Is that normal?

Yes, it is: that is what I have seen in all recent cars.

[t33h00]

https://goo.gl/photos/kJYF5MtnrASw7poT9
It works extremely fine on the busy roads.

[mntbiker]

I am in the middle of coding this (intense...) and I'm wondering if I can apply my ncd file with changes to both FLE ECUs or if I have to change the properties in each one. Are these ECUs the same? The CAFD files have the same exact file name...

2016 F15 built in late July

EDIT: I saw in post 108 where the CAFD was attached that you can use the same file for both FLEs. Hope that was right.. because I just did it. No errors or anything. I am going for a test drive in 1-2 hours once it gets dark enough. That was the most intense coding I've ever done...

My CAFD filename is: CAFD_000024C3_008_010_000.ncd

EDIT 2: It works! I used the "Appendix 2" section of the PDF from Jan. 2016 (v2) and followed the guide. I was able to test it out tonight and it's working just like I saw in the videos posted in this thread. The tunnel was appearing and none of the cars I was following or driving past seemed to be getting blinded. Very awesome.

Thanks to everyone who put the time into this effort. You are all amazing. Now it's time to code the F80!

[compsyndrome]

I've looking for an answer to this question:

Can you code HBA on Xenon equipped F15? No anti-dazzle features but rather auto off/on of the high beams?

[TheUltimateDrivingManiac]

Change the last figure of the vehicle type from 3 to 1 in FA (no need to save it in the car) and code LHM or FLEs to avoid that boring Step 2

Good luck!