[DarkstarZero]

I've seen a bunch of how-to's and videos and conversations about coding VLD and Anti-Dazzle on G20s and G05s, etc. But nothing on the G07 specifically beyond just, delete 5AP and recode BDC_Body3. Which I've done but it doesn't work great.

But there's more to it than that, in order for it to work properly on the G05 with Laser, for example, you have to code KAFAS4, but that doesn't exist on the G07...

So in short, is there a cheatsheet list similar to https://drive.google.com/file/d/1T9_...zktodsFwa/view for the G07 or a how-to document somewhere for this that is specific to the G07?

[jmciver]

The X5 (G05) and X7 (G07) are the same when it comes to the headlight variants and the software to control them inside the vehicle, including coding the anti-dazzle feature. VO coding is required, and based on info posted by a known and respected coder in another thread I found, it requires the following:

1) Remove 5AP from your Vehicle Order (VO) and save this VO back to your vehicle.

2) Code the following modules with the new VO saved to your car: BDC_Body, HU_MGU, FLM (both of them), and KAFAS (the X7 has all of these modules).

He also mentions, that some additional FDL coding may be required. I did the VO coding above, but I am not sure if the anti-dazzle feature is working properly. At least not when compared to my M3 where the beam forming is very apparent, but on my X7, it just seems like simple high/low beam operation. So I may go back in to see what other FDL coding tweaks may be necessary to get it working properly.

Also, I have the adaptive LED headlights, not the Laser headlights on my X7. However, the anti-dazzle feature is supposed to be available on both headlight variants - so the coding above should be applicable to both headlight variants. And for those of you reading this post that are wondering, BimmerCode can't do this type of coding (or VO coding). You need a coding program like E-Sys installed on a PC.

[DarkstarZero]

Originally Posted by jmciver

The X5 (G05) and X7 (G07) are the same when it comes to the headlight variants and the software to control them inside the vehicle, including coding the anti-dazzle feature. VO coding is required, and based on info posted by a known and respected coder in another thread I found, it requires the following:

1) Remove 5AP from your Vehicle Order (VO) and save this VO back to your vehicle.

2) Code the following modules with the new VO saved to your car: BDC_Body, HU_MGU, FLM (both of them), and KAFAS (the X7 has all of these modules).

He also mentions, that some additional FDL coding may be required. I did the VO coding above, but I am not sure if the anti-dazzle feature is working properly. At least not when compared to my M3 where the beam forming is very apparent, but on my X7, it just seems like simple high/low beam operation. So I may go back in to see what other FDL coding tweaks may be necessary to get it working properly.

Also, I have the adaptive LED headlights, not the Laser headlights on my X7. However, the anti-dazzle feature is supposed to be available on both headlight variants - so the coding above should be applicable to both headlight variants. And for those of you reading this post that are wondering, BimmerCode can't do this type of coding (or VO coding). You need a coding program like E-Sys installed on a PC.

Yikes, then what did I do wrong where I couldn't find KAFAS? It's supposed to be S18A chassis right? Ending in 0000?

[DarkstarZero]

Originally Posted by DarkstarZero

Yikes, then what did I do wrong where I couldn't find KAFAS? It's supposed to be S18A chassis right? Ending in 0000?

Ah, it was because the car was not in diag mode and engine was off.

[thenew3]

If you have a working procedure, I would appreciate if you could post the steps here. I'm sure others would appreciate it as well. thanks.

[jmciver]

Originally Posted by thenew3

If you have a working procedure, I would appreciate if you could post the steps here. I'm sure others would appreciate it as well. thanks.

Unfortunately, a full tutorial from scratch about how to code anti-dazzle on the X7 using E-sys would be beyond the scope of this thread - and very long . There is a lot of info on the net regarding BMW coding tutorials. But basically, you need to get the hardware (an ENET cable), get the software, then install it on a PC, and then start coding (both FDL and VO coding). Once you understand how to VO code, the guidance I provided above will make better sense about what you need to do to get anti-dazzle working. The video below is a fairly recent one and can get you started on the basics of coding:

[jmciver]

Originally Posted by DarkstarZero

Ah, it was because the car was not in diag mode and engine was off.

Glad you figured it out. But the engine being on or off does not matter - you can code with the engine running or not. But being in diagnostic mode on G-series BMWs does matter .

[ifr]

Originally Posted by jmciver

Glad you figured it out. But the engine being on or off does not matter - you can code with the engine running or not. But being in diagnostic mode on G-series BMWs does matter .

Guess he means he couldn't see KAFAS as the SVT lookup was conducted with the engine off, and not in diag mode.

[jmciver]

Originally Posted by ifr

Guess he means he couldn't see KAFAS as the SVT lookup was conducted with the engine off, and not in diag mode.

Maybe so. When I did this, I connected my PC and ran E-Sys with the engine off and saw everything, which is what I normally do for relatively short coding sessions. Also, interestingly enough, most of the time my X7 goes into diagnostic mode automatically when I connect my ENET cable either using E-Sys or BimmerCode - not sure why the inconsistency though...

[ifr]

Originally Posted by jmciver

Maybe so. When I did this, I connected my PC and ran E-Sys with the engine off and saw everything, which is what I normally do for relatively short coding sessions. Also, interestingly enough, most of the time my X7 goes into diagnostic mode automatically when I connect my ENET cable either using E-Sys or BimmerCode - not sure why the inconsistency though...

I've never known esys to display KAFAS, DSC, SAS without the engine running or diag mode active. If yours is kicking into diag mode automatically then you'll be able to see all ECU, but that's unusual, at least with a standard enet to obd2 cable and esys alone.

[jmciver]

Originally Posted by ifr

I've never known esys to display KAFAS, DSC, SAS without the engine running or diag mode active. If yours is kicking into diag mode automatically then you'll be able to see all ECU, but that's unusual, at least with a standard enet to obd2 cable and esys alone.

Yup, when I used E-sys (in diagnostic mode), I could see all of the ECUs. With BimmerCode, only a subset of the ECUs...

[DarkstarZero]

Originally Posted by jmciver

Yup, when I used E-sys (in diagnostic mode), I could see all of the ECUs. With BimmerCode, only a subset of the ECUs...

How do you get ESYS to put the car in diagnostic mode?

[ifr]

Originally Posted by DarkstarZero

How do you get ESYS to put the car in diagnostic mode?

I'm not sure you can, but would be useful to know if it's possible.

I've always done it manually.

ISTA will put the car in diag mode automatically for identification, fault evaluation and programming.

[jmciver]

Originally Posted by DarkstarZero

How do you get ESYS to put the car in diagnostic mode?

It has been a while since I plugged in my laptop to my X7 (for E-Sys or ISTA) or iPhone with my ENET cable so I could be remembering incorrectly. But I do remember that in some instances, the car went into diagnostic mode automatically. Specifically, I plug in my ENET cable first, then turn on the ignition. The fact that the X7 detected the ENET cable (by going into diagnostic mode) when the ignition turned on did not seem strange to me - I had seen that type of behavior before with diagnostic cables and other cars. The only thing that seemed a little weird was that it did not happen consistently.

Honestly I don't pay it too much attention. Now, any time I plug in my laptop or iPhone I always manually put the car in diagnostic mode.

[DarkstarZero]

Does anyone know how to find the data that's needed to code G07's? Maybe I need a new pszdata? I'm running v.4.27.40_PSdZData_Lite

I don't see any of the options they're talking about here: https://drive.google.com/file/d/1T9_...zktodsFwa/view

For example, they say to change in KAFAS4:
COUNTRY_VARIATION
C_FLA_BS_ENTER_THRESH
C_FLA_BS_EXIT_THRESH:
C_FLA_CC_MESSAGE_3
C_FLA_US_SENSITIVITY_MODE

But I don't see anything that even looks like that. I search for just C_FLA and there's nothing. Most of the values are just numbers, no names like these. And when there are, they are very few and far between. See screenshot.

[srbabu790]

Originally Posted by jmciver

The X5 (G05) and X7 (G07) are the same when it comes to the headlight variants and the software to control them inside the vehicle, including coding the anti-dazzle feature. VO coding is required, and based on info posted by a known and respected coder in another thread I found, it requires the following:

1) Remove 5AP from your Vehicle Order (VO) and save this VO back to your vehicle.

2) Code the following modules with the new VO saved to your car: BDC_Body, HU_MGU, FLM (both of them), and KAFAS (the X7 has all of these modules).

He also mentions, that some additional FDL coding may be required. I did the VO coding above, but I am not sure if the anti-dazzle feature is working properly. At least not when compared to my M3 where the beam forming is very apparent, but on my X7, it just seems like simple high/low beam operation. So I may go back in to see what other FDL coding tweaks may be necessary to get it working properly.

Also, I have the adaptive LED headlights, not the Laser headlights on my X7. However, the anti-dazzle feature is supposed to be available on both headlight variants - so the coding above should be applicable to both headlight variants. And for those of you reading this post that are wondering, BimmerCode can't do this type of coding (or VO coding). You need a coding program like E-Sys installed on a PC.

Learned about this anti-dazzle feature recently. Were you able to fully turn this feature on after your decoding ? I am trying to understand if the 2022 X7 M50 laser headlights really have this capability inbuilt within the hardware for US models ?
Thanks

[Boulder]

Originally Posted by srbabu790

I am trying to understand if the 2022 X7 M50 laser headlights really have this capability inbuilt within the hardware for US models ?

They do.

[gsobol]

Originally Posted by PinkNinja400Guy

They do.

Control modules are the same, all LED components are the same, I believe the entire headlight assembly appears to be the same. The only difference is the Laser diode module.

EU headlights are using Class 3R laser with power less than 60mW in wavelength between 400~700nm

US headlights are using Class 2 laser with power less than 20mW in wavelength between 400~462nm

which in turn halves the light throw distance on US vehicles to only 300m from the EU 600m.

However, this does not in any way impact the VLD or Anti-Dazzle capability of the US headlights. They are still capable to do everything the EU headlights can. Many people on this forum have coded their pre-LCI US vehicles and are very happy with the results - I know I am.

[srbabu790]

Originally Posted by gsobol

Control modules are the same, all LED components are the same, I believe the entire headlight assembly appears to be the same. The only difference is the Laser diode module.

EU headlights are using Class 3R laser with power less than 60mW in wavelength between 400~700nm

US headlights are using Class 2 laser with power less than 20mW in wavelength between 400~462nm

which in turn halves the light throw distance on US vehicles to only 300m from the EU 600m.

However, this does not in any way impact the VLD or Anti-Dazzle capability of the US headlights. They are still capable to do everything the EU headlights can. Many people on this forum have coded their pre-LCI US vehicles and are very happy with the results - I know I am.

Thanks for those details. So I presume, after coding you are able to experience the same effects as the EU cars.. right ?
Did you code it yourself ?

I am still a bit cautious about the coding part, that I don't end up messing up something else and ruin my warranties.

[gsobol]

Originally Posted by srbabu790

Thanks for those details. So I presume, after coding you are able to experience the same effects as the EU cars.. right ?
Did you code it yourself ?

I am still a bit cautious about the coding part, that I don't end up messing up something else and ruin my warranties.

Yes, the functionality is the same. Yes, I have coded it, but if you are not comfortable with the process, please reach out to an experienced coder, such as Ben at RG Sport: rgsportshop@gmail.com

[B///MWGuy]

Originally Posted by DarkstarZero

Does anyone know how to find the data that's needed to code G07's? Maybe I need a new pszdata? I'm running v.4.27.40_PSdZData_Lite

I don't see any of the options they're talking about here: https://drive.google.com/file/d/1T9_...zktodsFwa/view

For example, they say to change in KAFAS4:
COUNTRY_VARIATION
C_FLA_BS_ENTER_THRESH
C_FLA_BS_EXIT_THRESH:
C_FLA_CC_MESSAGE_3
C_FLA_US_SENSITIVITY_MODE

But I don't see anything that even looks like that. I search for just C_FLA and there's nothing. Most of the values are just numbers, no names like these. And when there are, they are very few and far between. See screenshot.

I'm experiencing the same issue as this person. I just can't find "COUNTRY_VARIATION" and most of the functions in KAFAS4 are "UNBELEGT". I'm using 4.49.20 PSDZData Lite with Esys 3.30.1.

Perhaps I need full PSDZData version?

[SimR]

Originally Posted by B///MWGuy

I'm experiencing the same issue as this person. I just can't find "COUNTRY_VARIATION" and most of the functions in KAFAS4 are "UNBELEGT". I'm using 4.49.20 PSDZData Lite with Esys 3.30.1.

Perhaps I need full PSDZData version?

Do you use the "E-Sys Launcher Pro" to start your app? I think it is mandatory to access FDL coding... Otherwise, you can buy the Bimmer Utility application (about 100$ I think). It is by far more user friendly to code, and many other features. I personally use E-sys to flash ECUs, modify i-Step level and fix broken cafds only.