G05
BMW X5
14.1KVIEWS
90REPLIES
69APPRECIATES
25ACTIVE PEOPLE
04-07-2026LAST POST
07-10-2024
Starting my coding journey to make this G07 specific to me. So far I’ve been using BimmerCode (comfort and expert mode). I also purchased Bimmer Utility for advanced coding (I have not coded, only looked around with BU application).

What I have coded so far:
Comfort +
Window interrupt not active
Close tailgate with remote
M performance up to 200
///M animation
Beep when locking while engine running not active


Next up
Soft close tailgate and anti-dazzle headlights

Soft close - Post state it works but I have not coded this (https://g05.bimmerpost.com/forums/showthread.php?t=2014390&highlight=bimmer+utlity )

3011 APPL_PLG_ SPEED_ PROFILE, 64(Top tailgate)
Code:
ProfileCloseStartNode1PwmPlg - Werte=00, 3Е
ProfileCloseStopNode1PwmPlg - Werte=00, 98
ProfileCloseStartNode2PosPlg - Werte=00, 32
ProfileCloseStopNode1PosPlg - Werte=00, 32

3072 APPL_LTG_SPEED_PROFILE, 69(Lower tailgate)
Code:
ProfileCloseStartNode1Pwm - Werte=00, 25
ProfileCloseStopNode1Pwm - Werte=00, BB
ProfileCloseStopNode1Pos - Werte=00, 96
ProfileCloseStartNode2Pos - Werte=00, 96


I do have a question regarding the anti-dazzle
For the 5 ecu’s that need to be coded, am I just opening and pressing code and not making any changes within them and then opening the KAFAS4 and making changes in the below directories?

I know about the BDC changes they are just not listed here


Anti-Dazzle - (https://g05.bimmerpost.com/forums/showthread.php?t=1742249&page=2 )
read FA, edit FA
* remove 5AP, save FA
* read ÉCU
* code BDC_BODY, HU_MGU, FLM2 [43],
FLM2 [44], KAFAS4.

FDL Coding
KAFAS4
C_FLA_CC_MESSAGE_3:
CC_message_active to no_CC_message [00]
C_FLA_US_SENSITIVITY_MODE:
US to Normal [00]
C_FLA_Country_With_Multiple_Reflectors Inactive aktiv
COUNTRY_VARIATION Europe_RC [01]
C_FLA_BS_ENTER_THRESH Rest of world [03]
C_FLA_BS_EXIT_THRESH: Rest of world [02]



Will update post with outcomes
07-10-2024
The soft close coding parameters for the tailgate on previous X models was due to the setting from the factory was a hard slam.

Does the g07 X7 tailgate close with a hard slam, too? If no, I'd leave it alone. If yes, then coding the tailgate to "slow down" so that it doesn't slam shut will be a relief.

My f15 X5's tailgate would slam shut with a hard THUD and it drove me crazy. Coding it to slow down in its last stage of closure changed it to a gentle soft close and made life much better. :)
07-10-2024
Qsilver7 wrote
The soft close coding parameters for the tailgate on previous X models was due to the setting from the factory was a hard slam.

Does the g07 X7 tailgate close with a hard slam, too? If no, I'd leave it alone. If yes, then coding the tailgate to "slow down" so that it doesn't slam shut will be a relief.

My f15 X5's tailgate would slam shut with a hard THUD and it drove me crazy. Coding it to slow down in its last stage of closure changed it to a gentle soft close and made life much better. :)
Lower and upper tailgate slam. I'm going to play with the bump stops this evening to see if that "softens" the close before I make any coding changes, but currently I have a loud thud as if someone slammed a passenger door.
07-11-2024
Thanks for the update...sounds like the same issue with previous generations. I guess BMW may be defaulting to a hard slam to compensate for owners that may have the cargo area overstuffed...so the hard thud (to close) over-compensates to make sure the tailgate is closed :(

Good luck and I hope you can get it resolved..."I feel your pain"...and truly understand why you'd like a softer close. :thumbsup:
07-23-2024
CoupeLyfe803 wrote
Lower and upper tailgate slam. I'm going to play with the bump stops this evening to see if that "softens" the close before I make any coding changes, but currently I have a loud thud as if someone slammed a passenger door.
I also coded the softer closure for the trunk of my X7 2021. I've tried several values over the last few months. The important thing to remember is that if you soften the closure too much, after a few days the trunk may not close completely!

In short, here's what I've discovered on my end:
- You need to change the values in the HKFM2 module
- ProfileCloseStopNode1PwmPlg = Top door
- ProfileCloseStopNode1Pwm = Bottom door
- 1st Byte = Panel speed at end of closing movement
- 2nd Byte = Closing force (at very end of movement)

In my case, the following values work great:
- ProfileCloseStopNode1PwmPlg -> Werte (00,64)
- ProfileCloseStopNode1Pwm -> Werte (00,A0)

Here is a video of the default trunk closure (note : if the domain of the url is not "dropbox", you have to copy/paste the following link and replace "dropbotwitter" by "dropbox"):
https://www.dropbox.com/scl/fi/0nxaq4qu9mc6l84sa2hxv/Default-closing.mp4?rlkey=v0iu7y7xjm2kxjoa45gggyci5&st=gydhgvgr&dl=0

Here is a video of the softer trunk closure I have coded (note : if the domain of the url is not "dropbox", you have to copy/paste the following link and replace "dropbotwitter" by "dropbox"):
https://www.dropbox.com/scl/fi/tdg598rlfmvct7ahwuu7q/Softer-closing.mp4?rlkey=hhqotr6j78ag9opqanzh64q6s&st=aq0w90xi&dl=0


And as a bonus, here are four other tricks I've coded that I really like:
1) Activate the beeper when the trunk is closed (inside button, keyfob button or foot movement under rear bumper):
- HKL_REMOTECONTROLLIFTGATEBUTTON_BEEPER_ACTIVE -> Werte (01)
- HKL_LIFTGATEBUTTONOUTSIDE_BEEPER_ACTIVE -> Werte (01)
- HKL_LIFTGATEBUTTONLOCK_BEEPER_ACTIVE -> Werte (01)

2) Change the behavior of the inner rocketswitch to close the trunk without having to perform a long press:
- HKL_ROCKERSWITCHPOS1_BUTTON_TYPE -> Werte (05)
- HKL_ROCKERSWITCHPOS2_LONGPRESS_CLOSE -> Werte (00)

3) Program the keyfob button to behave in the same way as the inner rocketswitch, and to close the trunk too:
- HKL_REMOTECONTROLLIFTGATEBUTTON_BUTTON_TYPE -> wert05 (05)
- HKL_REMOTECONTROLLIFTGATEBUTTON_DELAY_CLOSE -> Werte (00,00)

4) Prevent accidental opening of the trunk while driving by allowing opening ONLY when the gearbox is in position “P”:
- BDC_BODY3 (7083) -> VAM_BOOTLID_OPEN_ONLY_IN_P_IDG_SMO -> aktiv (01)
- BDC_BODY3 (7083) -> VAM_BOOTLID_IN_P_ONLY_LOCKED -> nicht_aktiv (00)

:D
07-23-2024
SimR wrote
I also coded the softer closure for the trunk of my X7 2021. I've tried several values over the last few months. The important thing to remember is that if you soften the closure too much, after a few days the trunk may not close completely!

In short, here's what I've discovered on my end:
- You need to change the values in the HKFM2 module
- ProfileCloseStopNode1PwmPlg = Top door
- ProfileCloseStopNode1Pwm = Bottom door
- 1st Byte = Panel speed at end of closing movement
- 2nd Byte = Closing force (at very end of movement)

In my case, the following values work great:
- ProfileCloseStopNode1PwmPlg -> Werte (00,64)
- ProfileCloseStopNode1Pwm -> Werte (00,A0)

Here is a video of the default trunk closure (note : if the domain of the url is not "dropbox", you have to copy/paste the following link and replace "dropbotwitter" by "dropbox"):
https://www.dropbox.com/scl/fi/0nxaq4qu9mc6l84sa2hxv/Default-closing.mp4?rlkey=v0iu7y7xjm2kxjoa45gggyci5&st=gydhgvgr&dl=0

Here is a video of the softer trunk closure I have coded (note : if the domain of the url is not "dropbox", you have to copy/paste the following link and replace "dropbotwitter" by "dropbox"):
https://www.dropbox.com/scl/fi/tdg598rlfmvct7ahwuu7q/Softer-closing.mp4?rlkey=hhqotr6j78ag9opqanzh64q6s&st=aq0w90xi&dl=0


And as a bonus, here are four other tricks I've coded that I really like:
1) Activate the beeper when the trunk is closed (inside button, keyfob button or foot movement under rear bumper):
- HKL_REMOTECONTROLLIFTGATEBUTTON_BEEPER_ACTIVE -> Werte (01)
- HKL_LIFTGATEBUTTONOUTSIDE_BEEPER_ACTIVE -> Werte (01)
- HKL_LIFTGATEBUTTONLOCK_BEEPER_ACTIVE -> Werte (01)

2) Change the behavior of the inner rocketswitch to close the trunk without having to perform a long press:
- HKL_ROCKERSWITCHPOS1_BUTTON_TYPE -> Werte (05)
- HKL_ROCKERSWITCHPOS2_LONGPRESS_CLOSE -> Werte (00)

3) Program the keyfob button to behave in the same way as the inner rocketswitch, and to close the trunk too:
- HKL_REMOTECONTROLLIFTGATEBUTTON_BUTTON_TYPE -> wert05 (05)
- HKL_REMOTECONTROLLIFTGATEBUTTON_DELAY_CLOSE -> Werte (00,00)

4) Prevent accidental opening of the trunk while driving by allowing opening ONLY when the gearbox is in position “P”:
- BDC_BODY3 (7083) -> VAM_BOOTLID_OPEN_ONLY_IN_P_IDG_SMO -> aktiv (01)
- BDC_BODY3 (7083) -> VAM_BOOTLID_IN_P_ONLY_LOCKED -> nicht_aktiv (00)

:D
So we need to perform this coding after every software update..right ?
07-23-2024
srbabu790 wrote
So we need to perform this coding after every software update..right ?
Not necessarily, it depends on how it was done. Some OTA's don't update every module, so if it is an OTA that didn't impact the coded modules, then no, it would not require re-coding. However, dealer updates usually affect them all, so in those instances, it would be required to re-code.
07-23-2024
srbabu790 wrote
So we need to perform this coding after every software update..right ?
I'm not sure I understand the question. In fact, regardless of the version of your iDrive 7 (updated or not), you should have access to these lines of code to modify them with E-Sys, BimmerCode or BimmerUtility.

It is probably the same lines to code if you have iDrive 8 or newer (to check to be sure).

Also, these changes should remain even after an iDrive update, unless you VO-Code the module in question. I've just installed the latest version (07-2024) and all my codes are still there.
07-23-2024
roxxor wrote
Not necessarily, it depends on how it was done. Some OTA's don't update every module, so if it is an OTA that didn't impact the coded modules, then no, it would not require re-coding. However, dealer updates usually affect them all, so in those instances, it would be required to re-code.
Exact! That's why I've kept a backup of the CAFDs for each of the modules I've modified. I've also made an Excel file of all the codes I've customized, so that I'll be able to put them back in a few minutes if the dealer ever resets the system ;)
07-23-2024
I'd like to take this opportunity to add two other options that I found incredibly useful for my X7, and for which I couldn't find anything on the Web!

I discovered that you could customize the behavior of the 2nd-row seat adjustment buttons. In my case, with the captain's seats, there's this button that reposition the seat to its default position.
An image attached to this post, provided by the poster

This famous “reposition button" is in fact a compromise position, where the seat returns to the middle of its longitudinal travel. In short, this “default” position is useless because you almost always have to manually adjust the seat, either to have more space for the 2nd-row passenger, or more for the 3rd-row passenger, depending on the situation.

So in my case, I coded the “Reposition button” to move the seat back to the MAXIMUM position, giving as much legroom as possible to the 2nd-row passenger. In short, it is very useful when there's nobody in the 3rd row.

Here's what to code:
SM2 (select the desired rear passenger seat module) -> SV_RESETPOSITION_SILV_SR2_LNV_PHYS -> Werte (00,01)


I've also configured the “rear passenger side” seat so that it moves back as far as possible, taking into account the presence of the child seat in the 3rd row. Previously, the seat would “hit” the child seat in the 3rd row, the engine would force back and the system would lock up! Now, by pressing the “Reposition button”, the 2nd-row seat moves back as far as possible, stopping just before hitting the 3rd-row child seat:
SM2 (select desired passenger seat module) -> SV_RESETPOSITION_SILV_SR2_LNV_PHYS -> Werte (00,32)

Note: The value “32” corresponds to a 5cm limitation on maximum recoil. You'll need to test different values to find the one that suits your needs.


Now for a second very useful tip. You can program the default reposition for the second-row seat after you've pressed the button to access the 3rd row.
An image attached to this post, provided by the poster

So in my case, I've taken it for granted that when I lower the 2nd-row seat, it's for someone to sit in the 3rd row. The previous problem was that when the back of the 2nd-row seat was pulled up to get it back into place, it would “squeeze” the legs of the person in the 3rd row. We had to wait for it to finish resuming its position before we could move it forward to clear the legs of the person in the 3rd row. Now by default, when I straighten the backrest in the 2nd row, the seat adopts a mid-position, leaving extra legroom for the person sitting in the 3rd row!

Here's what to change:
SM2 (select desired passenger seat module) -> SILV_SR2_EE_REAR_LNV_PHYS -> Werte (00,50)


Here is a video showing how the seat behaves once reprogrammed: (note : if the domain of the url is not "dropbox", you have to copy/paste the following link and replace "dropbotwitter" by "dropbox"):
https://www.dropbox.com/scl/fi/fl81f848izkp8grvdlflr/PXL_20240723_140446453.mp4?rlkey=m5hogrrs47ayah2cllo1q2ssx&st=p0rc8xeg&dl=0


Hopefully it will be useful to others!
:thumsup:
07-24-2024
CoupeLyfe803 wrote
Starting my coding journey to make this G07 specific to me. So far I’ve been using BimmerCode (comfort and expert mode). I also purchased Bimmer Utility for advanced coding (I have not coded, only looked around with BU application).

What I have coded so far:
Comfort +
Window interrupt not active
Close tailgate with remote
M performance up to 200
///M animation
Beep when locking while engine running not active


Next up
Soft close tailgate and anti-dazzle headlights

Soft close - Post state it works but I have not coded this (https://g05.bimmerpost.com/forums/showthread.php?t=2014390&highlight=bimmer+utlity )

3011 APPL_PLG_ SPEED_ PROFILE, 64(Top tailgate)
Code:
ProfileCloseStartNode1PwmPlg - Werte=00, 3Е
ProfileCloseStopNode1PwmPlg - Werte=00, 98
ProfileCloseStartNode2PosPlg - Werte=00, 32
ProfileCloseStopNode1PosPlg - Werte=00, 32

3072 APPL_LTG_SPEED_PROFILE, 69(Lower tailgate)
Code:
ProfileCloseStartNode1Pwm - Werte=00, 25
ProfileCloseStopNode1Pwm - Werte=00, BB
ProfileCloseStopNode1Pos - Werte=00, 96
ProfileCloseStartNode2Pos - Werte=00, 96


I do have a question regarding the anti-dazzle
For the 5 ecu’s that need to be coded, am I just opening and pressing code and not making any changes within them and then opening the KAFAS4 and making changes in the below directories?

I know about the BDC changes they are just not listed here


Anti-Dazzle - (https://g05.bimmerpost.com/forums/showthread.php?t=1742249&page=2 )
read FA, edit FA
* remove 5AP, save FA
* read ÉCU
* code BDC_BODY, HU_MGU, FLM2 [43],
FLM2 [44], KAFAS4.

FDL Coding
KAFAS4
C_FLA_CC_MESSAGE_3:
CC_message_active to no_CC_message [00]
C_FLA_US_SENSITIVITY_MODE:
US to Normal [00]
C_FLA_Country_With_Multiple_Reflectors Inactive aktiv
COUNTRY_VARIATION Europe_RC [01]
C_FLA_BS_ENTER_THRESH Rest of world [03]
C_FLA_BS_EXIT_THRESH: Rest of world [02]



Will update post with outcomes
I can also help you code your outdoor lighting correctly.

First of all, here are a few definitions important to understand :

1) VLD = Variable Light Distribution - It moves your headlights and position the beams on the road depending on steering angle, vehicle speed and the environment (urban, highway, countryside). It's standard on all European cars but is decoded on all North American cars for legal reasons.

An image attached to this post, provided by the poster


2) Anti-Dazzle = GFHBA = Glare Free High Beams Assistant - European spec high beams that enable your car to keep the high beams on without blinding other cars. This is basically a better and more advanced version of High Beams Assistant than North American version that simply turns the high beams on or off depending of the presence of other cars.

An image attached to this post, provided by the poster
An image attached to this post, provided by the poster


Here are the steps to follow to correctly code the “Anti-Dazzle” and “Variable Light Distribution” options:

1) Remove the FA 5AP from your vehicle's SALAPA list. Then apply the modifications. In BimmerUtility, simply “Save” the change and the application will ask you if you agree to apply the modifications to related ECUs.

Otherwise you can “VO-Code” the following modules after removing the FA 5AP:
BDC_BODY3 -> 1DF8 + 7083
KAFAS4 -> 40F9


2) Next, you need to change the following parameters to activate the “Anti-Dazzle” and "VLD" functions :
BDC_BODY3 (1DF8) :
C_HBA_FOG_ENA -> Werte (00)
C_HBA_DIM_ENA -> enable (01)
C_HBA_GFHB_ENA -> enable (01)
C_HBA_GFHBA_ENA_V_HI -> 49km/h (31)
C_HBA_GFHBA_ENA_V_HYST -> Japan_5_km/h (05)
C_AFS_ECO_LEVEL_3_ENA -> enable (01)
C_AFS_ENA -> enable (01)
C_BLC_PRE_ENA -> enable (01)
C_CLC_BLINK_ENA -> enable (01)
C_CLC_CURV_V2 -> ECE (23)
C_CLC_CURV_V3 -> ECE (28)
C_CLC_EXT_ENA -> enable_roundabout (01)
C_CLC_REV_ENA -> enable (01)
LUT_FLC_FORWARDLIGHTING_Y -> AFS (00,00,00)
LUT_AFS_CODRV_HOR -> standard/init
LUT_AFS_DRV_HOR -> F040_G005_AHL/G015_G020_Laser/G07_ECE/G07_Basis_US

BDC_BODY3 (7083) :
AL_MODE_ECO -> LOW_LEVEL_3_DIPB (03)
LIN_VARIANTE_SZL -> szl_r_HW_aic_4Band_fla (30)

KAFAS (40F9):
COUNTRY_VARIATION -> EUROPE_RC (01)
C_FLA_CC_MESSAGE_3 -> no_CC_message (00)
C_FLA_COUNTRY_WITH_MULTIPLE_REFLECTORS -> Active (01)
C_FLA_US_SENSITIVITY_MODE -> Normal (00)
C_FLA_BS_ENTER_THRESH -> Rest of world (03)
C_FLA_BS_EXIT_THRESH -> Rest of world (02)


This should work perfectly, as long as you set your light switch to “Position A”.
:party0030:


UPDATE : After conducting several tests and observations over the past few months, I also suggest these adjustments to further improve the Anti-Dazzle function ;) :

BDC_BODY3 (1DF8):
Improve the brightness of the high beam headlights :
LUT_AFS_DRV_HOR -> Werte (00,00,00,33,00,00,00,00,00,00,00,00,00,00,00,EB,E B,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00)
LUT_AFS_CODRV_HOR -> Werte (00,00,00,00,00,00,00,00,00,00,00,00,00,00,15,15,0 0,00,00,00,00,00,00,00,00,00,00,00,00,00,00)
Increase the headlight rotation speed to follow the steering wheel rotation almost in real time :
C_BLC_HOR_VEL_MIN -> Werte (99)
Allow the headlights to rotate to both the left and right sides of the road when turning the steering wheel :
C_BLC_DRIVING_ON_RIGHT -> Werte (FF)
Activate the HBA function at ≥ 30km/h (rather than 40km/h) :
C_HBA_ENA_V_HI -> China (1E)
Activation of the cornering lights when the steering wheel is turned approximately 180 degrees:
C_CLC_CURV_POS_DIFF_HI -> Werte (30)
Once the cornering lights have been activated, they deactivate when the steering wheel returns to approximately 90 degrees:
C_CLC_CURV_POS_DIFF_LO -> Kurvenlicht (1E)
Allowing cornering lights although with highbeams :
C_CLC_HIGHBEAM_DIS -> enable (00)
Activation of cornering lights at all speeds, on flasher or steering demand :
C_CLC_BLINK_V0 -> Werte (FA)
C_CLC_BLINK_V1 -> Werte (FF)
C_CLC_CURV_V0 -> Werte (FA)
C_CLC_CURV_V1 -> Werte (FF)
C_CLC_CURV_V2 -> Werte (FA)
C_CLC_CURV_V3 -> Werte (FF)
Activation of cornering lights in roundabout, at speed ≤ 80km/h (rather than 50km/h) :
C_CLC_EXT_ROUND_V_LO -> Werte (50)
C_CLC_EXT_ROUND_V_HI -> Werte (55)

KAFAS (40F9):
Reduce the streetlight detection sensitivity to avoid premature deactivation of the GFHBA function :
C_FLA_LN_US_ECE_BEHAVIOR -> ECE (02)
C_FLA_ALGO_CITY_DETECTION -> Inactive (00)
Improve the speed of reactivation of the GFHBA after crossing an oncoming vehicle :
C_FLA_CONT_OC_MAX_DELAY_CURVE_UP_AHEAD -> Werte (00,FA)
C_FLA_CONTROLLER_TL_OVERTAKE_MAX_TIME_DELAY -> Werte (03,E8)
C_FLA_CONT_OC_NORMAL_TIMEDLY -> Werte (00,96)
C_FLA_CONT_OC_NORMAL_TIMEDLY_HW -> Werte (00,96)

:D
10-14-2024
SimR wrote
I can also help you code your outdoor lighting correctly.

First of all, here are a few definitions important to understand :

1) VLD = Variable Light Distribution - It moves your headlights and position the beams on the road depending on steering angle, vehicle speed and the environment (urban, highway, countryside). It's standard on all European cars but is decoded on all North American cars for legal reasons.

An image attached to this post, provided by the poster


2) Anti-Dazzle = GFHBA = Glare Free High Beams Assistant - European spec high beams that enable your car to keep the high beams on without blinding other cars. This is basically a better and more advanced version of High Beams Assistant than North American version that simply turns the high beams on or off depending of the presence of other cars.

An image attached to this post, provided by the poster
An image attached to this post, provided by the poster


Here are the steps to follow to correctly code the “Anti-Dazzle” and “Variable Light Distribution” options:

1) Remove the FA 5AP from your vehicle's SALAPA list. Then apply the modifications. In BimmerUtility, simply “Save” the change and the application will ask you if you agree to apply the modifications to related ECUs.

Otherwise you can “VO-Code” the following modules after removing the FA 5AP:
BDC_BODY3 -> 1DF8 + 7083
KAFAS4 -> 40F9


2) Next, you need to change the following parameters to activate the “Anti-Dazzle” and "VLD" functions :
BDC_BODY3 (1DF8) :
C_HBA_FOG_ENA -> Werte (00)
C_HBA_DIM_ENA -> enable (01)
C_HBA_GFHB_ENA -> enable (01)
C_HBA_GFHBA_ENA_V_HI -> 49km/h (31)
C_HBA_GFHBA_ENA_V_HYST -> Japan_5_km/h (05)
C_AFS_ECO_LEVEL_3_ENA -> enable (01)
C_AFS_ENA -> enable (01)
C_BLC_PRE_ENA -> enable (01)
C_CLC_BLINK_ENA -> enable (01)
C_CLC_CURV_V2 -> ECE (23)
C_CLC_CURV_V3 -> ECE (28)
C_CLC_EXT_ENA -> enable_roundabout (01)
C_CLC_REV_ENA -> enable (01)
LUT_FLC_FORWARDLIGHTING_Y -> AFS (00,00,00)
LUT_AFS_CODRV_HOR :
-> standard/init (if you have regular high beams)
-> G05_Laser_ECE (if you have Laser high beams)
LUT_AFS_DRV_HOR :
-> F040_G005_AHL/G015_G020_Laser/G07_ECE/G07_Basis_US (if you have regular high beams)
-> G05_Laser_ECE (if you have Laser high beams)

BDC_BODY3 (7083) :
AL_MODE_ECO -> LOW_LEVEL_3_DIPB (03)
LIN_VARIANTE_SZL -> szl_r_HW_aic_4Band_fla (30)

KAFAS (40F9):
COUNTRY_VARIATION -> EUROPE_RC (01)
C_FLA_CC_MESSAGE_3 -> no_CC_message (00)
C_FLA_COUNTRY_WITH_MULTIPLE_REFLECTORS -> Active (01)
C_FLA_US_SENSITIVITY_MODE -> Normal (00)
C_FLA_BS_ENTER_THRESH -> Rest of world (03)
C_FLA_BS_EXIT_THRESH -> Rest of world (02)


This should work perfectly, as long as you set your light switch to “Position A”.
:party0030:
Thank you for the detailed post on this. I'm going to try to follow this to enable the VLD/anti-dazzle on my 21 X7. I'm planning to use bimmer utility.
10-15-2024
powpig wrote
Thank you for the detailed post on this. I'm going to try to follow this to enable the VLD/anti-dazzle on my 21 X7. I'm planning to use bimmer utility.
Keep us updated! ;)
10-17-2024
SimR wrote
I'd like to take this opportunity to add two other options that I found incredibly useful for my X7, and for which I couldn't find anything on the Web!
...
:thumsup:
SimR's user avatarSimR Been looking for this, thanks! Which coding utility did you do this with?
10-17-2024
I have a 2020 X7 40i. Does the Anti Dazzle require the laster lights or can it be done on the LEDs?
10-17-2024
Apparently the anti-dazzle can be easily coded with Bimercode in expert mode. I was able to do so on my ‘22 Alpina with Laser Lights but haven’t ventured outside of the city to test it out.

Pardon the terrible picture.. :bonk:
An image attached to this post, provided by the poster
10-17-2024
ledphut wrote
Apparently the anti-dazzle can be easily coded with Bimercode in expert mode. I was able to do so on my ‘22 Alpina with Laser Lights but haven’t ventured outside of the city to test it out.

Pardon the terrible picture.. :bonk:
That looks promising! I guess I need to get into coding as well. I'd love to have the anti-dazzle lights feature.
10-17-2024
bmwchicago wrote
SimR's user avatarSimR Been looking for this, thanks! Which coding utility did you do this with?
I prefer Bimmer Utility! Really user friendly and powerful. On your mobile or computer! ;)
12-24-2024
ledphut wrote
Apparently the anti-dazzle can be easily coded with Bimercode in expert mode. I was able to do so on my ‘22 Alpina with Laser Lights but haven’t ventured outside of the city to test it out.

Pardon the terrible picture.. :bonk:
Did you have a chance to check if the anti-dazzle works?
12-24-2024
sharp wrote
Did you have a chance to check if the anti-dazzle works?
Unfortunately I did not. I live deep in the city so it’s never dark enough to see if it’s working properly. By the time I took a road trip to VA I had gotten an over the air software update that wiped out the coding..
03-27-2025
ledphut wrote
Unfortunately I did not. I live deep in the city so it’s never dark enough to see if it’s working properly. By the time I took a road trip to VA I had gotten an over the air software update that wiped out the coding..
Did you get a chance to recode this and see if it worked?