[TheNine90]

Originally Posted by BIGW0RM

Say that again? How did you accomplish this?

Change typecode to ECE and code the flm modules.
If you have pre lci then you can edit the cafd without change the typecode.

[FC4]

Coded anti-dazzle via BimmerCode…I don’t get what all the fuss is about. Sure it’s a little different than the high beams flashing on and off, but it’s not a big deal.

[jimmy9980]

It will work but your missing coding on three other modules. Which is pretty important I would say considering the cost of these lights if they were to burn out or over work themselves from incorrect coding.just saying.

[Rux]

Originally Posted by FC4

Coded anti-dazzle via BimmerCode…I don’t get what all the fuss is about. Sure it’s a little different than the high beams flashing on and off, but it’s not a big deal.

I found the opposite. It was a huge difference for me. Without ESYS I am to understand the beam is just not as narrow? Meh. I like free. For now.

[backslashv]

Apologies if this has been mentioned elsewhere, but what are the values that need to be changed via ESYS? This seems to not be exactly accurate for iDrive update 11/2022 as per a comment in this thread saying anti-dazzle was disabled in 7/2022 update following that guide.

[Th3DarkSide]

Originally Posted by FC4

Coded anti-dazzle via BimmerCode…I don’t get what all the fuss is about. Sure it’s a little different than the high beams flashing on and off, but it’s not a big deal.

I’m not going to even bother. I had it in my F82s and never used it. I’ve been debating it but it’s something I won’t ever use.

[WolfpackCO]

Hey all - just coded the settings available in Bimmercode for Anti-dazzle. I wanted to ask if the remaining coding is required/recommended in Esys?

I do have Esys and open to coding it myself but haven't been able to find a confirmed/verified step by step process.

Thanks in advance for the help!

[TheNine90]

If you did using bimmercode it should be enough

[TheNine90]

If you have 5AP in FA then you can remove it and vo code BDC, FLM, HU, KAFAS. then redo the coding using bimmercode

[biggripper]

I live in the UK with my US spec G80 and here it’s a must have feature. I’m driving mostly unlit B roads at night, and it gets extremely dark here this time of year. This is a country where Road visibility during the daytime is poor, because of how they allow hedges and other vegetation to grow right up to the side of the road. This means that being able to use every last ounce of your headlights makes a huge difference. Now with anti dazzle coded on, my highbeams stay on nearly 90% of the time when I’m outside my village driving. I can see the headlights selectively shielding cars that I’m following or oncoming cars so that they’re not blinded but the rest of the highbeam is doing its work. The effect is high beam brightness and spread with a clearly visible shadowy demarcation around the other motorists. It’s pretty impressive.

If it’s NOT properly coded in and working 100% correctly, it’s not gonna be that impressive. Furthermore, if you find yourself mostly doing in-city driving, it will not be particularly useful or impressive.

The system seems to know when you’re in the city based on street signs and lights etc, and as a result, won’t activate the highbeams. It’s really on dark country roads and less crowded sections of the interstate/motorway where you’ll see the feature activate.

[Berzerker]

Originally Posted by TheNine90

If you have 5AP in FA then you can remove it and vo code BDC, FLM, HU, KAFAS. then redo the coding using bimmercode

Not exactly the most helpful. Do you know of a step by step guide for what to code in those modules?

[WolfpackCO]

Originally Posted by Berzerker

Do you know of a step by step guide for what to code in those modules?

^this would be super helpful! 🙏🏼

[dmr]

Originally Posted by WolfpackCO

^this would be super helpful! 🙏🏼

I posted this in G87 forum some time ago. That might be what you're looking for:

https://g87.bimmerpost.com/forums/sh...ght=antidazzle

[WolfpackCO]

Originally Posted by discreet_mayor

I posted this in G87 forum some time ago. That might be what you're looking for:

https://g87.bimmerpost.com/forums/sh...ght=antidazzle

thanks discreet_mayor very helpful and much appreciated!

[Berzerker]

Originally Posted by discreet_mayor

I posted this in G87 forum some time ago. That might be what you're looking for:

https://g87.bimmerpost.com/forums/sh...ght=antidazzle

How does this translate to only using BimmerUtility?

[dmr]

Originally Posted by Berzerker

How does this translate to only using BimmerUtility?

Honestly not sure, but the recipe is low-level enough that you should be able to use it with any software that lets you program values in the car's various modules, maybe through some advanced mode?

[Berzerker]

Originally Posted by discreet_mayor

Honestly not sure, but the recipe is low-level enough that you should be able to use it with any software that lets you program values in the car's various modules, maybe through some advanced mode?

So I'm a bit confused. Your post says "recipe to code this using BimmerUtility" but step 1 is doing stuff through eSys as well.

You're saying you used ESYS *and* Bimmerutility? i.e. Step 1 through ESYS, then Steps 2, 2a and 3 through bimmerutility?

Do you know of a good ESYS tutorial relevant to iDrive 8?

[thatguyM4]

I've coded my lights well over a year and no issues what so ever and just using Bimmercode - The only thing I really noticed is that its a little sensitive as to coming on but it works great

[Berzerker]

Originally Posted by thatguyM4

I've coded my lights well over a year and no issues what so ever and just using Bimmercode - The only thing I really noticed is that its a little sensitive as to coming on but it works great

Yes I'm aware that can be done and have already done it, but I'm interested in getting that last 20% of the functionality, hence my questions.

[dmr]

Originally Posted by Berzerker

So I'm a bit confused. Your post says "recipe to code this using BimmerUtility" but step 1 is doing stuff through eSys as well.

You're saying you used ESYS *and* Bimmerutility? i.e. Step 1 through ESYS, then Steps 2, 2a and 3 through bimmerutility?

Do you know of a good ESYS tutorial relevant to iDrive 8?

That is correct. I used esys only in Step 1, because I had found clearer instructions on how to vo code/decode using it, though BimmerUtility is also capable of doing so. You don't technically need esys, but would have to translate step 1 into the BimmerUtility equivalent.

[Berzerker]

Originally Posted by discreet_mayor

That is correct. I used esys only in Step 1, because I had found clearer instructions on how to vo code/decode using it, though BimmerUtility is also capable of doing so. You don't technically need esys, but would have to translate step 1 into the BimmerUtility equivalent.

And BU is completely capable of accessing every ECU on iDrive 8 as well? I noticed ProTool doesn't have access to the same stuff you do on ESYS, so I'm hesitant to buy yet another license to something.

[Hyura]

Having both, BimmerUtility is just an add on to ESys. ESys should have access to all the modules but it’s not labeled so you’ll using BimmerUtility to label what these options are. The amount of labeled options vary from BimmerUtility vs ProTools, but from my experience, BimmerUtility should have a bit more labeled options while on ProTools just have unlabeled options in raw hex values. Still editable, you just wouldnt know what you’re changing.