Adaptive LED lighting turned on-wow

[Almaretto]

Originally Posted by M3WAL

I have a 16 with LEDs...Im confused this coding makes our lights brighter at all times? or just the LED angel eyes?

It makes them appear brighter as they become dynamic and different aspects can be on without glaring other drivers.

[nguyelt]

Originally Posted by Almaretto

It makes them appear brighter as they become dynamic and different aspects can be on without glaring other drivers.

I have been trying to code the anti dazzle on my 2017 F82 but keep running into the glaring other drivers issue every time I do a test drive. Do you have any advice? I was following the guide posted by dmnc02 on another thread but am not sure what I need to VO code in the FLA3 folder (dont have KAFAS)
https://f80.bimmerpost.com/forums/sh...2&postcount=60

This is what I have done so far:
1. Removed 5AP & 8S4 from FA/VO
2. Coded FEM_BODY
3. Coded LHM [43] and LHM [44]

[Almaretto]

Originally Posted by nguyelt

I have been trying to code the anti dazzle on my 2017 F82 but keep running into the glaring other drivers issue every time I do a test drive. Do you have any advice? I was following the guide posted by dmnc02 on another thread but am not sure what I need to VO code in the FLA3 folder (dont have KAFAS)
https://f80.bimmerpost.com/forums/sh...2&postcount=60

This is what I have done so far:
1. Removed 5AP & 8S4 from FA/VO
2. Coded FEM_BODY
3. Coded LHM [43] and LHM [44]

You need to VO code TMS and KAFAS as well.
Then, FDL code both LHM's & FRM using Cheat Codes.

[nguyelt]

Originally Posted by Almaretto

You need to VO code TMS and KAFAS as well.
Then, FDL code both LHM's & FRM using Cheat Codes.

I have FLA3 instead of KAFAS. How do I VO code FLA3 and TMS? Is there anything I need to FDL code in FLA3?

[Almaretto]

Originally Posted by nguyelt

I have FLA3 instead of KAFAS. How do I VO code FLA3 and TMS? Is there anything I need to FDL code in FLA3?

VO coding takes care of everything in FLA3 & TMSx2.

https://www.bimmerfest.com/forums/sh...d.php?t=983245

[Nunaat]

Hello everyone, I note that there is a great level of knowledge in this forum. It's formidable. I have dared to install adaptive led lci headlamps (552) from xenon without adaptation(522). I added the pins 9 and 10 that go from the led connector to fembody, but previously changed 522 by 552 in fa.and detected CAF in FLE43 and FLE44 but it was not the exact ilevel, but once connected the headlights were turned on but a section of the drl. to solve it I did coding vo to fembody and then the LEDs went off completely. Now the modules FLE43 and FLE44 do not appear in esys. What can I do to solve this big problem? doing fdl code in fembody would it help?
Thank you very much for your help.

[Almaretto]

Originally Posted by Nunaat

Hello everyone, I note that there is a great level of knowledge in this forum. It's formidable. I have dared to install adaptive led lci headlamps (552) from xenon without adaptation(522). I added the pins 9 and 10 that go from the led connector to fembody, but previously changed 522 by 552 in fa.and detected CAF in FLE43 and FLE44 but it was not the exact ilevel, but once connected the headlights were turned on but a section of the drl. to solve it I did coding vo to fembody and then the LEDs went off completely. Now the modules FLE43 and FLE44 do not appear in esys. What can I do to solve this big problem? doing fdl code in fembody would it help?
Thank you very much for your help.

VO code Fem & FLE. Then, you need to initialize in ISTA+.

[ibrennan]

Originally Posted by pmooiweer

I’ve been running with GFHB coded on my MY18 F80 (July 2017 Production date) since October of last year and have not had any issues. Light tunneling works when following traffic (inner high beams switch off and outer high beams swivel towards the side of the road) and high beams swivel and switch off properly for oncoming traffic (inner high beams switch off, outer high beams swivel to the side of the road and left outer high beam switches off just before oncoming traffic enters its light cone). I have never had anyone flash their high beams at me.

See https://github.com/packetpilot/bmw-f...ster/pmooiweer for e-sys/Tokenmaster cheat codes, assuming you have Lane Departure Warning (KAFAS2) camera. Some posters have reported high beam “leakage”, but I have not experienced this myself. I’ve only had a couple of instances where GFHB tunneling didn’t kick in when following traffic. In both instances I followed cars with abnormal LED taillight patterns, e.g. uninterrupted rear light bar across the width of the car instead of distinct taillights.

I just wanted to chime in on this, I've been trying to code my 2018 M3 CS, and am having a hard time doing so. I'm pretty familiar with coding, and did it on my 2016 many times, along with helping some other people with theirs.

When using the cheat code you posted on GitHub (thank you for this btw) I'm seeing leakage of light onto the car in front of me mostly. After driving almost 3 years with my coded 2016 I knew right away something wasn't right.

I believe there is some sort of 2018 2.0 ECE coding settings we are missing. How do we go about finding a recent production 2018 ECE coding settings to compare with?

[Rewted]

This is on by default in Canada, no?

[Almaretto]

Originally Posted by Rewted

This is on by default in Canada, no?

This is off, from factory, in North American vehicles.

[snareman]

Originally Posted by ibrennan

I just wanted to chime in on this, I've been trying to code my 2018 M3 CS, and am having a hard time doing so. I'm pretty familiar with coding, and did it on my 2016 many times, along with helping some other people with theirs.

When using the cheat code you posted on GitHub (thank you for this btw) I'm seeing leakage of light onto the car in front of me mostly. After driving almost 3 years with my coded 2016 I knew right away something wasn't right.

I believe there is some sort of 2018 2.0 ECE coding settings we are missing. How do we go about finding a recent production 2018 ECE coding settings to compare with?

I've been told by several coders that it isn't possible on the 2018's because of a change in one of the lighting modules. Damn frustrating

[Almaretto]

Originally Posted by ibrennan

I believe there is some sort of 2018 2.0 ECE coding settings we are missing. How do we go about finding a recent production 2018 ECE coding settings to compare with?

E-sys Coding-Verification can generate files, but hardware differences lead to light leakage.

[pmooiweer]

Originally Posted by ibrennan

I believe there is some sort of 2018 2.0 ECE coding settings we are missing. How do we go about finding a recent production 2018 ECE coding settings to compare with?

Like others stated, I believe there are hardware differences between the headlights that were installed in the earlier MY18 F80’s and the current ones that seem to be causing this. My guess is that ECE headlights now differ from the US version.

Having said that, I’d be happy to double-check any differences between the US and ECE settings for your FLE CAFD. I can perform the same analysis I originally did to figure out the proper values for FLE settings to enable GFHB.

If you could PM me a copy of your original (as shipped) FA file (connect to the car, read the FA and save it in e-sys), as well as your original (as shipped) CAFD settings, I can do a detailed analysis to see whether the settings differ from my cheat codes. The CAFD settings are saved in e-sys whenever you read the ECU data (e.g. right-click the CAFD entry for the ECU in the e-sys SVT panel in Coding mode and select Read Coding Data). I should only need the FLE CAFD (CAFD_000024C3_xxx_xxx_xxx), but to be safe also send the FEM_BODY (CAFD_00000794_xxxx) and, assuming you have KAFAS2, that CAFD (CAFD_00001148_xxxx) as well. If you installed e-sys with default settings, the .ncd files needed will be in C:\Data\CAF and the FA XML file will be in C:\Data\FA. If you’ve made any coding changes in the CAFD files I need, simply first VO code the ECU (right-click the ECU in the e-sys Coding module and select Code).

[CanAutM3]

Originally Posted by Almaretto

E-sys Coding-Verification can generate files, but hardware differences lead to light leakage.

I tried to code the VLD and NGHB on my 2019 M4cs, but I am at loss. There doesn't seem to be an LHM module.

Any clues on where/what I should look for?

[Almaretto]

Originally Posted by CanAutM3

I tried to code the VLD and NGHB on my 2019 M4cs, but I am at loss. There doesn't seem to be an LHM module.

Any clues on where/what I should look for?

2018+ have FLE.

[CanAutM3]

Originally Posted by ibrennan

I just wanted to chime in on this, I've been trying to code my 2018 M3 CS, and am having a hard time doing so. I'm pretty familiar with coding, and did it on my 2016 many times, along with helping some other people with theirs.

When using the cheat code you posted on GitHub (thank you for this btw) I'm seeing leakage of light onto the car in front of me mostly. After driving almost 3 years with my coded 2016 I knew right away something wasn't right.

I believe there is some sort of 2018 2.0 ECE coding settings we are missing. How do we go about finding a recent production 2018 ECE coding settings to compare with?

I just coded NGHB and VLD on my 2019 M4cs and went for a test drive. It seems to work fine on my car . I didn't get a single flash.

Note that the cheat codes you referenced are incomplete/inacurate. As other posters have subsequently pointed out, some of the "values" don't work and the actual array needs to be entered. I did not use cheat codes and proceeded to do it the old fasion way by manually editing each parameter one by one. It was long, but it ended up being a good thing because I also found out that some variables in the FLE modules had slightly different names than the cheat codes.

[danchee]

Originally Posted by CanAutM3

I just coded NGHB and VLD on my 2019 M4cs and went for a test drive. It seems to work fine on my car . I didn't get a single flash.

Note that the cheat codes you referenced are incomplete/inacurate. As other posters have subsequently pointed out, some of the "values" don't work and the actual array needs to be entered. I did not use cheat codes and proceeded to do it the old fasion way by manually editing each parameter one by one. It was long, but it ended up being a good thing because I also found out that some variables in the FLE modules had slightly different names than the cheat codes.

Would you be willing to provide a write up for the new setup?

[FlyingLow78]

Originally Posted by CanAutM3

I just coded NGHB and VLD on my 2019 M4cs and went for a test drive. It seems to work fine on my car . I didn't get a single flash.

Note that the cheat codes you referenced are incomplete/inacurate. As other posters have subsequently pointed out, some of the "values" don't work and the actual array needs to be entered. I did not use cheat codes and proceeded to do it the old fasion way by manually editing each parameter one by one. It was long, but it ended up being a good thing because I also found out that some variables in the FLE modules had slightly different names than the cheat codes.

Very interested to know what was different between your coding and the cheat code!

[jzhu625]

I need to get this done, anyone in NYC does it?

[CanAutM3]

Originally Posted by danchee

Would you be willing to provide a write up for the new setup?

Originally Posted by FlyingLow78

Very interested to know what was different between your coding and the cheat code!

Sure, see attached .pdf for the two FLE modules.

I incorporated the changes specified by Nickolka in posts #1308 and #1309 of this thread and modified the HX_Xxxx variables for H_X_Xxxxx as I found them in my ECUs.

[pmooiweer]

Originally Posted by CanAutM3

I just coded NGHB and VLD on my 2019 M4cs and went for a test drive. It seems to work fine on my car . I didn't get a single flash.

Note that the cheat codes you referenced are incomplete/inacurate. As other posters have subsequently pointed out, some of the "values" don't work and the actual array needs to be entered. I did not use cheat codes and proceeded to do it the old fasion way by manually editing each parameter one by one. It was long, but it ended up being a good thing because I also found out that some variables in the FLE modules had slightly different names than the cheat codes.

The cheat codes should work fine as long as you use a recent version of TokenMaster’s Launcher and PSdZDATA files. I can post cheat codes with hex values instead of CAFD presets as well, but they’d be the same as the ones Nikola posted a while back.

I’d also be happy to check any potential differences between MY18 versions (i.e. between original MY18 headlights and current Icon headlights). I just need someone to send me their original, as shipped FA file and CAFD files for FLE and FEM_BODY. I can use those to analyze differences between European and US settings, and can also compare against my cheat codes. Anyone, please feel free to PM those to me; see my earlier post on what I need.

[snareman]

Originally Posted by pmooiweer

The cheat codes should work fine as long as you use a recent version of TokenMaster’s Launcher and PSdZDATA files. I can post cheat codes with hex values instead of CAFD presets as well, but they’d be the same as the ones Nikola posted a while back.

I’d also be happy to check any potential differences between MY18 versions (i.e. between original MY18 headlights and current Icon headlights). I just need someone to send me their original, as shipped FA file and CAFD files for FLE and FEM_BODY. I can use those to analyze differences between European and US settings, and can also compare against my cheat codes. Anyone, please feel free to PM those to me; see my earlier post on what I need.

I was told by several internet based coders that the 2019's can't be coded because of them having a different module or something like that compared to the 2018 and prior.