BMW Forum - BimmerFest BMW Forums banner

G01 coding of non-glare high beams

12K views 16 replies 7 participants last post by  TheNine90  
#1 ·
I'm working on enabling NGHB on my 2019 G01 with adaptive LED lights and high beam assistant. I've compared the US and ECE settings for the FLM module and noticed changes in some of the FDLs related to "low level" operation of the LED lamps. For example, LM01_BUCK_TOFF (time constant register value for the NCV78763 driver block) is [09] in the US settings but [0A] in the ECE settings. DELTA_I_OFFSET (correction value for current calibration) is also different. The screenshot below highlights all the differences. Any advice whether I should code the Euro values for these FDLs? Or should I ignore them and only code the various LmmIdx, LmmReLut, and function mode FDLs like Blendfreies_Fernlicht_Idx, DRL_Idx, WELL1_Idx, etc.? To put it differently, is there any danger in VO coding the FLM module to ECE specs? This would by far be the easiest solution than messing around with 250+ individual FDLs. I know I would lose the side markers doing that, but I can live without them.
 

Attachments

#3 · (Edited)
Coding KAFAS with ECE works fine, but the high beam assistant will not activate nearly as often. I think primarily due to more aggressive street light detection.

I prefer the ECE behavior, even with standard HBA. Seems to activate less in environments where you don't really need it. But the US spec is better if you're trying to watch the system's behavior in different scenarios with NGHB in lighter environments.

I also have plain ECE coded the headlamps. The sidemarkers go out, but they otherwise operate normally with no errors. It's probably better to have the US lamp module parameters in place, though.

BDC_BODY, you can ECE code 1DF8*, which seems to be where all of the NGHB-related stuff lives. Other ones are not safe to ECE code, there are things like the garage door opener frequency, tail lamps, and some other things that are different.

For clarity, my 2019 G02 does NOT create a proper tunnel despite my many attempts at this coding. I have seen it work correctly on a 2018 with similar coding. I am definitely interested to see if someone has a truly successful result with a US 2019 G01/G02 model. Mine creates this when I run the ISTA+ test pattern, which suggests the dynamic shadowing is not functional.

https://f10.m5post.com/forums/showpost.php?p=20573240&postcount=17
 
#4 ·
How did you run the test in ISTA+?
 
#7 · (Edited)
Huh, when I follow those directions, I am presented with the below. However, when I press "Continue" after selecting Option 1 "Adjust non-dazzle high-beam." it just goes back to the selection menu (first image)? I am running ISTA+ 4.21.12.
Image

Image
 
#6 ·
I still have to write ECE typekey to my FA and rerun ISTA+ to see if this fools ISTA+ into running the diagnostic pattern. The other idea that occurred to me is that maybe the ISTA+ version I am using is too old for my car. The version I have is from March 2018 and my car was made in July 2018. Maybe ISTA+ displays by default "This vehicle is not equipped with non-glare high-beam headlight" because it sees newer headlights and does not know how to deal with them. That's just a theory.
 
#8 ·
Where did you get ISTA+ 4.21.12? My version is 4.10.15. That's the only version I was able to find on this forum (in a thread titled "All BMWs Ista+ download link - no request"). I wonder if my old ISTA+ version is the source of my problem and when I update to a more recent version I will get the same error that you got ("This series is not adjusted anymore with the adjustment aid.") Ideally, we need somebody from Europe with functional NGHBs to run the ISTA+ diagnostic test on their car and tell us whether it works or they also get the "this series is not adjusted anymore ..." error.
 
#10 ·
From another forum which requires donation to register (starts with c and ends with .co.uk). In any case, I agree...I think we need to have a native ECE car test the NGHB functions to see if US headlights can accept proper ECE NGHB functions.
 
#12 ·
An update: I drove an hour away from the city last night to completely dark rural roads. The outcome was majorly disappointing. It's pretty clear that my car is not doing NGHB correctly at all. There was no shadow tunnel like I see in online videos. The high beams were blasting the area around the car ahead of me as well as the car itself. The back of the car was superbly illuminated and when I turned the high beam assistant off, I could see how the area around the car as well as the back of the car all became dark. What's worse is that I often got flashed by oncoming cars. I'd say one in four cars flashed me. I could tell that my left high beam turned completely off once the oncoming car got sufficiently close, but I did not see any "action" as the car was approaching. I think either the oncoming car was supposed to be shielded by the shadow tunnel, which does not form on my car, or the left high beam was supposed to be dipping down as the car was approaching and eventually turn off when the car got too close. Judging from other drivers flashing me, I suspect that they were being dazzled until they got close enough to my car and the left high beam turned off.

I am not sure where this leaves us. I will still try to hunt down a more recent version of ISTA+ and write an ECE typekey to my car, but I am starting to suspect that there is a reason why ISTA+ reports that "This vehicle is not equipped with non-glare high-beam headlight." Maybe BMW used NGHB capable lights on all G01 models early on and later switched to two part numbers: one for North America that cannot do NGHB and the other for the rest of the world. My car carries a July 2018 production date (Time Criteria = 0718). We really need somebody from Europe who has fully functional NGHB to tell us if they can successfully run the NGHB tunnel test using ISTA+.

For the record, here is what I did to enable NGHB:

  1. Deleted 5AP from FA, VO coded KAFAS. This changed C_FLA_GLAREFREE_HIGH_BEAM from "2_Step_FLA [00]" to "GlareFree_FLA [01]".
  2. Deleted 5AP from FA, VO coded BDC_BODY. This changed C_HBA_GFHB_ENA from "G001_disable [00]" to "G001_enable [01]" and C_HBA_DIM_ENA from "G001_disable [00]" to "G001_enable [01]".
  3. Deleted 5AP from FA, changed typekey to ECE, VO coded both FLM modules. This changed 265 settings in each FLM module (and disabled the amber side markers).
 
#14 · (Edited)
I don't think it's a matter of knowledge. I agree that a lot of coders claim they can do it, but what evidence do they provide to prove that it actually works? If they tested their coding changes on a 2018 G01 cars when the redesigned X3 came out and NGHB worked fine on them, the coding will obviously not work if BMW changed the headlights starting with the 2019 model year. That's what I am leaning toward--that my headlights lack the required hardware to perform the anti-dazzle functions. Check out this thread: Anti-dazzle and VLD in 2018 cars?