[PsychDoc]

I believe these cars come pre-programed for this technology even though it's not implemented at the time of production. I know there have been regulatory obstacles regarding this but I was wondering if these have been resolved and if this feature is now something that can be activated by dealerships or coded in some way.

It's a really great technology and it would be nice if it could be utilized.

Anyone have any information or updates?

[OHV_44]

https://www.bimmerfest.com/threads/a.../post-13894664

[OHV_44]

Manual site 171:

[MikeElmendorf]

OHV - PsychDoc is referring to the full adaptive LED headlight functionality (the “light tunneling” that keeps the highbeams active much more).

They are currently not permitted under NHTSA regulations, BUT there was language in the Bipartisan Infrastructure Bill authorizing this type of headlight in the US. NHTSA has to promulgate regulations to make it so. It will happen, just a question of when.

Currently all US-bound BMWs (not sure how other manufacturers handle it, but probably similar) have this function disabled through coding at the factory. If you look at your build sheet, you’ll see it.

Previously it could be enabled through coding. With iDrive 8.5 being locked down with some sort of BMW-side verification as I understand it, such coding is not possible on the newer vehicles.

However, given that the functionality is fully there and just disabled by coding, this seems ripe for something that will be available for purchase in the iDrive store once NHTSA does their job and issues the regs authorizing these types of headlights in the US. I’d bet on it.

[arkhi]

The NHTSA did issue the regs. They've been out for almost 2 years now. They're a little bit more complex and more stringent than the EU, with different requirements than the EU.

BMW and other car manufacturers will have to retest and reengineer, so I honestly do not expect currect cars to have these features enable by BMW ever, especially if it will require different hardware.

OP, you can try VO coding your car and wait for a software update. Apparently, someone on the i7 forum was successful with activating anti-dazzle and VLD with that.

[note46]

short answer, not if you have iDrive 8.5... however, there are some that had it activated via a vendor who programmed it on their 8.5 car. I can't remember which vendor.

On my iDrive 8 car, yes I activated anti-dazzle.

[COBodom]

So on my specs sheet I have this thing called "5AP - Decoding for no-dazzle high-beam assistance" prior to car delivery I thought BMW would finally enable the functionality (now that it's been legal for a while). Long behold, I am unable to get it going on my G60.

Clearly, I misunderstood that line item on the specs sheet as "decoding" means BMW is turning it OFF. They are explicitly letting us know...it wont work.

I had this coded on F10 and G30. It works great.

[wknddrivr]

Hoping this can be coded. It’s enabled on my 2022 Mercedes e450 and makes such a massive improvement driving on rural roads. On the new Mercedes models it seems you can still enable it, but not seeing tons of posts on BMWs with iDrivr 8.5.

I’d love to switch back to BMW as I just like BMW better, but not being able to code the split beam headlights, no massage seats, and no wagon in the US have me strongly considering a 2024 or 2025 e450 even though I’d much rather move back to a 540

[CaboM4]

It can be coded. Just did it on my i7 tonight (MGU22 running iDrive 8.5). Remove 5AP from your VO, and accept a OTA software update. It will code the car based on the modified VO in the car and you will have them.

I used BimmerUtility to modify the VO, but assume ESYS would work as well. No CAFD files are required to modify and write the VO to the car. The missing CAFD files are the current issue with "regular" coding as we know if for pre-Coding 2.0 implementation (read every new vehicle released prior to iX).

[MikeElmendorf]

Cabo - That is interesting and great news. Can you provide some details on how to do this and exactly what is needed? I’ve only used BimmerCode previously but willing to do whatever to accomplish this.

[MikeElmendorf]

I am looking into this now—I presume their ENET adapter is different than the OBD adapter I previously used for Bimmercode?

[grumpysysad]

Originally Posted by CaboM4

It can be coded. Just did it on my i7 tonight (MGU22 running iDrive 8.5). Remove 5AP from your VO, and accept a OTA software update. It will code the car based on the modified VO in the car and you will have them.

I used BimmerUtility to modify the VO, but assume ESYS would work as well. No CAFD files are required to modify and write the VO to the car. The missing CAFD files are the current issue with "regular" coding as we know if for pre-Coding 2.0 implementation (read every new vehicle released prior to iX).

It worked for my 540i, I did this when I got it and now with the 03.2024/57 update I got the feature.

Thanks for the tip

[MikeElmendorf]

Can confirm that the approach Cabo suggested works. Very happy to have them back on the i5.

[COBodom]

Snap...I just did the software update. Wish I read this thread earlier.

[lilstevie]

Originally Posted by grumpysysad

It worked for my 540i, I did this when I got it and now with the 03.2024/57 update I got the feature.

Thanks for the tip

Probably a dumb question, particularly as this may also be a LHD vs RHD issue, but I’ve been having problems even finding where the OBDII port is hidden. On my previous BMWs there was a little plastic cover you flipped out but hunting around under the dash on the drivers side I’ve found absolutely nothing so far

[RichardInCA]

Originally Posted by MikeElmendorf

Can confirm that the approach Cabo suggested works. Very happy to have them back on the i5.

Can you say more about how you did that Mike for those of us who haven’t used Bimmerutility before?

[paprmkr]

Originally Posted by MikeElmendorf

I am looking into this now—I presume their ENET adapter is different than the OBD adapter I previously used for Bimmercode?

just leaving it stock is best thought was your way

[MikeElmendorf]

Richard - You need to use BimmerUtility to code the VO to remove 5AP (which removes the disabling of the anti-dazzling functionality).

Paprmkr - I see you are attentive to what I have to say. I appreciate that. That's how I feel when it comes to gluing things on to the car; enabling a feature that is built into the vehicle and should be functional for the US market, save the slow pace of the NHTSA, is entirely different.

[paprmkr]

It’s not about fast trust me. I come from the lowerider world in the days. It’s about looking good and clean
If you didn’t like the options or not all there we did sign the dotted line with whatever
Just I’m a very observant person part of my job. So guilty on that. About glue. No tape yes plus fastener. Remember make it look right with that said I do agree not all be attached. Oriellys pats or PepBoys
You they one that said stock and criticized is with taped on stuff. Glad you like your plain. Reason the sell differ t colors and options I guess
I only respond to those that go on here and hate of what other ideas are with Thier cars
So you do you and either like or shu up

[RichardInCA]

Originally Posted by MikeElmendorf

Richard - You need to use BimmerUtility to code the VO to remove 5AP (which removes the disabling of the anti-dazzling functionality).

Thanks Mike - so do you use the ENET adapter or an OBD port? Does it only activate AFTER receiving an OTA update - or does making the change trigger an OTA update somehow?

[MikeElmendorf]

Richard - I used the BimmerUtility wireless ENET adapter that goes in the OBD port.

You make the change and then you have to wait until the next OTA update.

I had an update at the dealer to address an issue and it did not work after that. It did, however, after the OTA.

Credit again to Cabo for originally advising on this.

[MikeElmendorf]

Richard - I used the BimmerUtility wireless ENET adapter that goes in the OBD port.

You make the change and then you have to wait until the next OTA update.

I had an update at the dealer to address an issue and it did not work after that. It did, however, after the OTA.

Credit again to Cabo for originally advising on this.