[kubax86]

Originally Posted by Restrected

I apologize for being a complete noob but i have my coding setup ready and it does code properly. What do i do? i have a 2020 330i. when you turn on the car the lights self level so i am assuming i can enable this?

This can be done if you have 552 or 5AZ option which means either Adaptive Headlights or Laser Headlights

[xnick101]

Has anyone figured out how to do this with Bimmercode? There's a video on youtube on how to enable anti-dazzle headlights on an X5. Potentially similar on our cars.

[Almaretto]

Originally Posted by xnick101

Has anyone figured out how to do this with Bimmercode? There's a video on youtube on how to enable anti-dazzle headlights on an X5. Potentially similar on our cars.

Not possible on Bimmercode because you do not have access to FLM or KAFAS.

[dantwaddell]

xnick101 I successfully coded it using only Bimmercode. The FLM (front lighting module) items are available in the BDC (Body Domain Controller) section for Bimmercode with the G20. The KAFAS items are not changeable, however, so optimization for staying on longer with street lights / signs isn't possible; you'll need Esys for that. But basic functionality plus some parameter editing to improve performance is possible.

Basic functionality is in BDC section with the following changes:

PARAMETER						US VALUE			ECE VALUE
C_HBA_DIM_ENA:					disable [00]			enable [01]
C_HBA_GFHB_ENA:				disable [00]			enable [01]

As siegester mentioned on page 7, the following parameters improve performance:

PARAMETER						US VALUE			ECE VALUE
C_AFS_ECO_LEVEL_3_ENA			disable [00]			enable [01]
C_AFS_ENA						disable [00]			enable [01]
C_BLC_PRE_ENA					disable [00]			enable [01]
C_CLC_CURV_V2					US [3C]				ECE [23]
C_CLC_CURV_V3					US [46]				ECE [28]
C_CLC_EXT_ENA					disable [00]			enable_roundabout [01]
C_HBA_DIM_ENA					disable [00]			enable [01]
C_HBA_GFHBA_ENA_V_HI			55km/h [37]			standard [3C]
C_HBA_GFHB_ENA				disable [00]			enable [01]
LUT_AFS_CODRV_HOR			Laser_US/G007_US	standard/init 
LUT_AFS_DRV_HOR				Laser_US			F040_G005_AHL/G015_G020_Laser
LUT_FLC_FORWARDLIGHTING_Y	no_AFS [00 00 14]	AFS [00 00 00]

The one deviation I made was to set C_HBA_GFHBA_ENA_V_HI to the lowest speed (I think 47 kph). I believe this makes it turn the highbeams on at a lower speed. I confirmed mine turns on at about 30 mph. Note that when you are testing, the system will not fully engage at lower speeds or if there is enough ambient light from street lights (it may just be regular on/off high beams for those cases). So go somewhere that's actually dark to confirm performance. I was fooled a few times while changing settings thinking it wasn't working.

I find that it works quite well. The highbeams definitely tunnel around cars that I'm following, and turn off for opposing traffic while still staying on in my lane.

I am driving a 2022 M340xi (North America).

[kamil97]

I don't see any options in BDC_BODY3 Lamaster 1/2/3
My car: BMW G20 2020 with laser lights.
Has any one of you experienced this ?

[Almaretto]

Originally Posted by kamil97

I don't see any options in BDC_BODY3 Lamaster 1/2/3
My car: BMW G20 2020 with laser lights.
Has any one of you experienced this ?

There are many options in E-sys with BDC. You must be doing it wrong.

[homerjay]

Followed the instructions here, but I FUBARd my BDC_BODY3 coding. Error message after coding complete on this ECU and No lights, turn signals.

When I tried coding back to the original, the attached screenshot is the error I received.

Running Launcher Pro 5.1
E-Sys 3.40.2
PSdzDATA 4.36.71

US-spec 330i with laser lights.

i-level on my car is 03/2021.50
Selected S18A when connecting to my car.

[Almaretto]

Originally Posted by homerjay

Followed the instructions here, but I FUBARd my BDC_BODY3 coding. Error message after coding complete on this ECU and No lights, turn signals.

When I tried coding back to the original, the attached screenshot is the error I received.

Running Launcher Pro 5.1
E-Sys 3.40.2
PSdzDATA 4.36.71

US-spec 330i with laser lights.

i-level on my car is 03/2021.50
Selected S18A when connecting to my car.

When you read ECU, are you missing cafs or are any corrupted? You may need to inject.

[homerjay]

Originally Posted by Almaretto

When you read ECU, are you missing cafs or are any corrupted? You may need to inject.

It appears to be corrupt when I select “Read ECU”.

[Almaretto]

Originally Posted by homerjay

It appears to be corrupt when I select “Read ECU”.

That would explain functions not working. You need to inject CAFs to fix.

[smithf80]

Anyone have issues with Auto high beams just shutting itself off? As in you need to re-enable it with the button on the stalk. it happens randomly, sometimes I turn it on and it just right back off and it takes 2-3 tries before it "stays" on.

[homerjay]

Originally Posted by Almaretto

That would explain functions not working. You need to inject CAFs to fix.

Luckily got in touch with Steve at codemybimmer and got me back up that morning. GREAT service! I had some issue with Launcher corrupting my system 🤷*♂️

[Max Caviar]

My order is still pending production. But the "standard equipment" listed includes "Decoding for no-dazzle hgh bm."

Does that mean that after market coding won't be needed to get full functionality?

[Almaretto]

Originally Posted by Max Caviar

My order is still pending production. But the "standard equipment" listed includes "Decoding for no-dazzle hgh bm."

Does that mean that after market coding won't be needed to get full functionality?

Decoding = disabling

[Wackjam]

Originally Posted by smithf80

Anyone have issues with Auto high beams just shutting itself off? As in you need to re-enable it with the button on the stalk. it happens randomly, sometimes I turn it on and it just right back off and it takes 2-3 tries before it "stays" on.

I've been having this issue too. Not sure what the fix is. It's a bit annoying.

[Almaretto]

Originally Posted by smithf80

Anyone have issues with Auto high beams just shutting itself off? As in you need to re-enable it with the button on the stalk. it happens randomly, sometimes I turn it on and it just right back off and it takes 2-3 tries before it "stays" on.

Have you tried coding back to factory settings to see if issue is still present?

[Max Caviar]

thank you. will look into bimmercode.

Originally Posted by Almaretto

Decoding = disabling

[tomz17]

Originally Posted by homerjay

Luckily got in touch with Steve at codemybimmer and got me back up that morning. GREAT service! I had some issue with Launcher corrupting my system 🤷*♂️

FYI, for anyone in the future reading this. I had the same experience and completely jacked up the BDC config. Was able to inject the default CAFD using esys (launched directly, without any launcher), then proceed with FDL coding using esys+launcher. As a reminder, if you get into trouble, you can always VO code a module with just vanilla, unpatched esys.

From googling around, I suspect this may be a JVM memory issue since it only affected BDC for me while VO coding the entire module (after removing the anti-dazzle decoding). Everything else worked fine.

[Liquid_Ice]

I coded anti-dazzle this weekend on my 2020 M340i xDrive. I had a similar problem to tomz17 and homerjay, I should not have VO coded using Launcher Pro, was told to only use Launcher Pro for FDL Coding and use Esys by itself (no launcher) for VO Coding.

I provided 2GB to the JVM using Launcher Pro and still had issues so I don't think it was a JVM memory issue. There seems to be something wrong with reading and coding all of BDC when using Launcher Pro, maybe some kind of bug? I wonder if it would have happened with BimmerUtility.

I did the VO coding first then used the Cheat Codes from siegester for FDL coding anti-dazzle in KAFAS4 and BDC_BODY3.

Anyway - drove home tonight and wow anti-dazzle is awesome, I wish I had done this back when I first got the car instead of waiting 3 years to do it. Definitely makes buying the Laser Lights worth it.

It still turns off sometimes, but the highbeams stay on way more often and definitely help with visibility.

[Almaretto]

Originally Posted by Liquid_Ice

I coded anti-dazzle this weekend on my 2020 M340i xDrive. I had a similar problem to tomz17 and homerjay, I should not have VO coded using Launcher Pro, was told to only use Launcher Pro for FDL Coding and use Esys by itself (no launcher) for VO Coding.

I provided 2GB to the JVM using Launcher Pro and still had issues so I don't think it was a JVM memory issue. There seems to be something wrong with reading and coding all of BDC when using Launcher Pro, maybe some kind of bug? I wonder if it would have happened with BimmerUtility.

I did the VO coding first then used the Cheat Codes from siegester for FDL coding anti-dazzle in KAFAS4 and BDC_BODY3.

Anyway - drove home tonight and wow anti-dazzle is awesome, I wish I had done this back when I first got the car instead of waiting 3 years to do it. Definitely makes buying the Laser Lights worth it.

It still turns off sometimes, but the highbeams stay on way more often and definitely help with visibility.

A token is not required for VO coding, but using Launcher should not cause any issue.

Launcher Pro has outdated mapping, so better to use Bimmer Utility for FDL coding.

[Liquid_Ice]

Originally Posted by Almaretto

A token is not required for VO coding, but using Launcher should not cause any issue.

Launcher Pro has outdated mapping, so better to use Bimmer Utility for FDL coding.

Agree it shouldn't cause any issues, but I had no success re-injecting the BDC_BODY3 CAFD's when using LauncherPro (and I corrupted them when using LauncherPro) - but switching to ESYS with no Launcher everything worked fine - so I suspect an issue with LauncherPro.

I was using E-Sys 3.38.2, LauncherPro 5.2.0, PSdZData_Lite_v4.37.42

shawnsheridan was the one who recommended using ESYS with no launcher for VO coding and using a Launcher for FDL coding only.

Wish I knew about BimmerUtility before I paid $50 for LauncherPro (I just bought LauncherPro on 10/14/22)

[Almaretto]

Originally Posted by Liquid_Ice

Agree it shouldn't cause any issues, but I had no success re-injecting the BDC_BODY3 CAFD's when using LauncherPro (and I corrupted them when using LauncherPro) - but switching to ESYS with no Launcher everything worked fine - so I suspect an issue with LauncherPro.

I was using E-Sys 3.38.2, LauncherPro 5.2.0, PSdZData_Lite_v4.37.42

shawnsheridan was the one who recommended using ESYS with no launcher for VO coding and using a Launcher for FDL coding only.

Wish I knew about BimmerUtility before I paid $50 for LauncherPro (I just bought LauncherPro on 10/14/22)

Interesting.

I have occasionally had issue during remote coding for injection, but always good advice to remote unneeded variables to isolate issues.