Adaptive LED lighting turned on-wow

[audioMeth]

nvm pmooiweer posted while i was typing this up

so if i go back and set byte 4 to 04 (vs 00 as previously done) and leave LM_ID_LT04 and LM04_Name as werte 00 i should be good to go?

POLI1_Idx 00, 00, 00, 04, 00, 00, 08, 00, 00, 00
POLI2_Idx 00, 00, 00, 04, 00, 00, 08, 00, 00, 00
POLI3_IDX 00, 00, 00, 04, 00, 00, 08, 00, 00, 00
WELL1_Idx 00, 09, 09, 04, 00, 00, 0A, 00, 00, 00
WELL2_Idx 00, 00, 00, 04, 00, 00, 0B, 00, 00, 00
WELL3_Idx 00, 00, 00, 04, 00, 00, 0B, 00, 00, 00
WELL4_IDX 00, 00, 00, 04, 00, 00, 0B, 00, 00, 00
FMH_Idx 00, 02, 02, 04, 00, 00, 0B, 00, 00, 00
REMLI_Idx 00, 02, 02, 04, 00, 00, 0B, 00, 00, 00
SIDEMRKLGT_Idx 00, 00, 00, 04, 00, 00, 00, 00, 00, 00

[pmooiweer]

Originally Posted by audioMeth

nvm pmooiweer posted while i was typing this up

so if i go back and set byte 4 to 04 (vs 00 as previously done) and leave LM_ID_LT04 and LM04_Name as werte 00 i should be good to go?

POLI1_Idx 00, 00, 00, 04, 00, 00, 08, 00, 00, 00
POLI2_Idx 00, 00, 00, 04, 00, 00, 08, 00, 00, 00
POLI3_IDX 00, 00, 00, 04, 00, 00, 08, 00, 00, 00
WELL1_Idx 00, 09, 09, 04, 00, 00, 0A, 00, 00, 00
WELL2_Idx 00, 00, 00, 04, 00, 00, 0B, 00, 00, 00
WELL3_Idx 00, 00, 00, 04, 00, 00, 0B, 00, 00, 00
WELL4_IDX 00, 00, 00, 04, 00, 00, 0B, 00, 00, 00
FMH_Idx 00, 02, 02, 04, 00, 00, 0B, 00, 00, 00
REMLI_Idx 00, 02, 02, 04, 00, 00, 0B, 00, 00, 00
SIDEMRKLGT_Idx 00, 00, 00, 04, 00, 00, 00, 00, 00, 00

Not sure how you got those values for LMM_ID_LT04 and LM04_Name; those are ECE settings, not US. I'm not sure whether setting them to 00 will disable the sidemarkers and still enable GFHB. I would leave them at the US settings:
- LMM_ID_LT04 should be 04, referring to LM04.
- LM04_Name should be 0D, or 14 decimal, referring to SideMarkerLight 1 (SML1).

When you set byte 4 of the _Idx values that you listed to 04, the Sidemarkers will be controlled by the settings in LmmIdx04_Intensity, LmmIdx04_Timeon, etc. in Group 3005 of your FLE settings (and setting them to 0C links them to LmmIdx12 settings). LmmIdx04_Intensity should be set to 00, running your sidemarkers at 0% intensity, i.e. off (and LmmIdx12_Intensity is set to 64 or 100%). All of these settings are included in my cheat codes.

[Mr. Hankey]

Originally Posted by Almaretto

There are two thresholds. One for HBA (on/off) and another set for NGHB (tunneling); the ladder enables at 41 mph and continues above 38 mph. I do not recommend changing them, but they can be found in Fem_body and KAFAS.

Originally Posted by biggal76

I was meaning changing speed settings for auto headlights in general (not necessarily the NGHB feature of them. Enables high beams at 23mph, off at 18.

I did this in my 2015 F80 - Auto highs started working about 13 MPH and off at 8 MPH because roads around my house are very dark (this was coded through those 2 codes you found in the KAFAS camera module, same as FLA3 I had in the '15). Non-glare tunneling would then turn on at 55 MPH and off at 45 MPH. I found it annoying at mid speeds (35-50 MPH) as I was more dazzled by watching them tunnel and move around and was distracting me actually....but at highway speeds it was great - having that passenger high beam on down the road while behind other cars was fantastic, especially when at higher speeds. And if I need bright lights just pull the stalk and use high beams normally.

Just coded by '18 this way, but leaving the HBA settings in KAFAS alone....just changed C_HBA_ENA_V_HI and C_HBA_ENA_V_LO in FEM_BODY to werte 58 (about 55 MPH) and werte 48 (about 45 MPH). Will see how it works. Thanks for the cheat codes guys , saved me a ton of FDL programming, will let you know how the differential speeds work in the new system (fingers crossed).

[Deteria]

I got this coded and drove a few times at night. I noticed a lot of occasions when not all stars align and it just never turns on.

Is this feature meant for like a small 1:1 road when only 1 car is in front or coming at you? I feel like on a Texas highway with 3+ Lanes on each side, this feature rarely works.

[Almaretto]

Originally Posted by Deteria

I got this coded and drove a few times at night. I noticed a lot of occasions when not all stars align and it just never turns on.

Is this feature meant for like a small 1:1 road when only 1 car is in front or coming at you? I feel like on a Texas highway with 3+ Lanes on each side, this feature rarely works.

It works if you are in the #3 lane, but need significant distance if you have too many cars on the road.

[taint]

Originally Posted by Deteria

I got this coded and drove a few times at night. I noticed a lot of occasions when not all stars align and it just never turns on.

Is this feature meant for like a small 1:1 road when only 1 car is in front or coming at you? I feel like on a Texas highway with 3+ Lanes on each side, this feature rarely works.

Being in TX also, I notice the frontage roads really effect how it works. I have to get out of the city before it really works.

[Almaretto]

Originally Posted by taint

Being in TX also, I notice the frontage roads really effect how it works. I have to get out of the city before it really works.

Limitations

[drkeng]

so some of you are recoding anti-dazzle for the new 2018 LED's?

I assume NGHB=non-glare high beams and tunneling are both referring to anti-dazzle?

strange that the remote coders don't seem to offer this yet

[Almaretto]

Originally Posted by drkeng

so some of you are recoding anti-dazzle for the new 2018 LED's?

I assume NGHB=non-glare high beams and tunneling are both referring to anti-dazzle?

strange that the remote coders don't seem to offer this yet

Yes, LCI can be coded.

Yes, that is to what NGHB refers.

Then, you are going to wrong coder; I have done it multiple times. It can be even be done on G001 and G030.

[Nickolka]

Originally Posted by pmooiweer

See attached for updated FDL coding cheat codes to enable GFHB and VLD for MY 2018 F80 and F82 chassis. I have added cheat codes for KAFAS and FEM_BODY that allow GFHB/VLD coding without having to first modify the FA and VO coding those ECUs. I've also added options to code FLE with or without sidemarkers (keep in mind that sidemarkers are required by US DOT and you risk getting a ticket if you disable them).

Applying the attached cheat codes for KAFAS and FEM_BODY accomplishes the same as VO coding those modules after removing 5AP and 8S4 from your FA. This way you can leave your FA unchanged (i.e. no need to remove 5AP and 8S4), not disturbing any coding you may have done for KAFAS and FEM_BODY. It also makes future software updates that expect factory FA settings easier (assuming you wrote FA changes back to your car).

As always, place the attached file in your Tokenmaster FDLcodes folder and remember to remove the PDF extension.

Hi pmooiweer,

Was just wondering if there is any harm configuring LB2 to 100% intensity with GFHB in Schlechtwetter_C1_Idx, Schlechtwetter_C2_Idx, Stadt_V_Idx

If I am reading the encoding correctly, I could do this by setting

LmmIdx01_Intensity = 64 (100%), instead of 54
LmmIdx03_Intensity = 64 (100%), instead of 4A

as Idx01 and Idx03 sets are only used for Schlechtwetter_C1_Idx, Schlechtwetter_C2_Idx, Stadt_V_Idx as the rest of the settings TimeOn/Off, Priority, RampType, ErrorImpact are the same between US and EU in Idx2 in US case

One more thing, there were errors reported when I tried applying "FDLCodes - 2018 F80+F82 VLD and GFHB - V3.xml" with v.63.3_PSdZData_Lite database and esys 3.27.1. Some of the FDL Code XX_Value could not be applied as there were not located in the database.

I had to manually update the Werte for these indices to match xls column "Modified ECE Value (enable sidemarkers)". Could you, maybe, update the xml to use actual 10 byte Werte values and re-post for everyone to have easier time using your settings

Applying selected codes...
"07_Value" is not valid for Werte <- Schlechtwetter_C1_Idx (manually edited Werte: 00, 01, 02, 00, 00, 00, 00, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"07_Value" is not valid for Werte <- Schlechtwetter_C2_Idx (manually edited Werte: 00, 01, 02, 00, 00, 00, 00, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"10_Value" is not valid for Werte <- PLI_Idx (manually edited Werte: 00, 00, 00, 00, 00, 00, 08, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"11_Value" is not valid for Werte <- HBBLINK_Idx (manually edited Werte: 05, 02, 02, 00, 05, 00, 0C, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"11_Value" is not valid for Werte <- RAIDALARM_Idx (manually edited Werte: 05, 00, 00, 00, 05, 00, 0C, 07, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"10_Value" is not valid for Werte <- BLINKEN_Idx (manually edited Werte: 00, 00, 00, 00, 00, 00, 00, 0C, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)...OK.
Done

[Nickolka]

Originally Posted by Nickolka

Hi pmooiweer,

Was just wondering if there is any harm configuring LB2 to 100% intensity with GFHB in Schlechtwetter_C1_Idx, Schlechtwetter_C2_Idx, Stadt_V_Idx

If I am reading the encoding correctly, I could do this by setting

LmmIdx01_Intensity = 64 (100%), instead of 54
LmmIdx03_Intensity = 64 (100%), instead of 4A

as Idx01 and Idx03 sets are only used for Schlechtwetter_C1_Idx, Schlechtwetter_C2_Idx, Stadt_V_Idx as the rest of the settings TimeOn/Off, Priority, RampType, ErrorImpact are the same between US and EU in Idx2 in US case

One more thing, there were errors reported when I tried applying "FDLCodes - 2018 F80+F82 VLD and GFHB - V3.xml" with v.63.3_PSdZData_Lite database and esys 3.27.1. Some of the FDL Code XX_Value could not be applied as there were not located in the database.

I had to manually update the Werte for these indices to match xls column "Modified ECE Value (enable sidemarkers)". Could you, maybe, update the xml to use actual 10 byte Werte values and re-post for everyone to have easier time using your settings

Applying selected codes...
"07_Value" is not valid for Werte <- Schlechtwetter_C1_Idx (manually edited Werte: 00, 01, 02, 00, 00, 00, 00, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"07_Value" is not valid for Werte <- Schlechtwetter_C2_Idx (manually edited Werte: 00, 01, 02, 00, 00, 00, 00, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"10_Value" is not valid for Werte <- PLI_Idx (manually edited Werte: 00, 00, 00, 00, 00, 00, 08, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"11_Value" is not valid for Werte <- HBBLINK_Idx (manually edited Werte: 05, 02, 02, 00, 05, 00, 0C, 00, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"11_Value" is not valid for Werte <- RAIDALARM_Idx (manually edited Werte: 05, 00, 00, 00, 05, 00, 0C, 07, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
"10_Value" is not valid for Werte <- BLINKEN_Idx (manually edited Werte: 00, 00, 00, 00, 00, 00, 00, 0C, 00, 00)
Failed to add Code for "Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)".
Enable GFHB WITH sidemarkers (also code FEM_BODY and KAFAS2)...OK.
Done

pmooiweer,

I noticed that your file "FDLCodes - 2018 F80+F82 VLD and GFHB - V3.xml" does not contain the Step 3 from the "NGHB How To_F3x_F8x_v3.pdf" that is part of the e-sys 3.27.1 package under
e-sys.3.27.1\E-Sys\E-Sys Documents\E-Sys Documents\Cheat Sheets

Is it no longer required for 2018 F8x? I looked at the values in the FEM_BODY ncd for my car and they are different from what's in the document. It seems like they should be updated. Thoughts?

I also made the following changes to your v3 xml file in order to make it work with v.63.3_PSdZData_Lite
http://f80.bimmerpost.com/forums/sho...postcount=1298

FLE:
- Split into three separate steps with 1 required and 2 optional ones
<code description="v3.2: (Required step: #1) Enable Euro GFHB: (also code FEM_BODY and KAFAS2)">
-- this step is almost exactly the same as you had it in v3, except I kept LB2 (low beam 2) at 100% for (SchlechtWetter_*_Idx,Stadt_V_Idx)
<code description="v3.2: (Optional step: #2) Enable Euro GFHB: Decrease Low Beam (LB2) intensity in bad weather/city as per Euro spec (also code FEM_BODY and KAFAS2)">
-- this step decreases the brightness of LB2 as per Euro profile
<code description="v3.2: (Optional step: #3) Enable Euro GFHB: Disable sidemarkers (also code FEM_BODY and KAFAS2)">
-- this step is for people who are willing to disable mandatory sidemarkers
- corrected the errors that would get reported when applying the xlm with e-sys Launcher Premium (see Quote above) by using raw Werte values instead of XX_Value

Edits:
- Removed the additional FEM_BODY programming as it is no longer required for 2018 F8x. See post by Almaretto: http://f80.bimmerpost.com/forums/sho...postcount=1310

Please have a look at the attached file and let me know if any corrections are needed.

[Almaretto]

Originally Posted by Nickolka

pmooiweer,

I noticed that your file FDLCodes - 2018 "F80+F82 VLD and GFHB - V3.xml" does not contain the Step 3 from the "NGHB How To_F3x_F8x_v3.pdf" that is part of the e-sys 3.27.1 package under
e-sys.3.27.1\E-Sys\E-Sys Documents\E-Sys Documents\Cheat Sheets

Is it no longer required for 2018 F8x? I looked at the values in the FEM_BODY ncd for my car and they are different from what's in the document. It seems like they should be updated. Thoughts?

Not needed for 2018. VO coding takes care of FEM and KAFAS.

[rob10k8]

Hi all,

I coded my 2015 F32 for NGHBA and everything seemed to work fine. I then read that there was an update with these parameters:

C_HBA_UC1_LBND_THRES_HI Left: F020_LHTR = 28 Right: UNK_PARAM_0 = 27
C_HBA_UC1_LBND_THRES_LO Left: defaultwert (default value) = 0F Right: UNK_PARAM_0 = 1F
C_HBA_UC1_RBND_THRES_LO Left: defaultwert (default value) = F1 Right: UNK_PARAM_0 = E1

and now it seems like tunneling doesn't work properly. At highway speeds, when coming up on a slower moving car, the left beam turns off rather than creating a dark box. I'm FAIRLY sure that this changed when I did the above updates, but not 100%.

Unfortunately, my laptop isn't working so I'm not able to just make the changes to see if that enables tunneling again. I thought I'd ask here in case others have had the same issues.

Thanks!

Rob

[pmooiweer]

I posted my latest GFHB cheat codes on Github a while back. This version no longer requires VO coding; simply follow the instructions at the top of the file.

See https://github.com/packetpilot/bmw-f...ster/pmooiweer

[Nickolka]

Originally Posted by pmooiweer

I posted my latest GFHB cheat codes on Github a while back. This version no longer requires VO coding; simply follow the instructions at the top of the file.

See https://github.com/packetpilot/bmw-f...ster/pmooiweer

pmooiweer,

Any chance you could post the Euro and US ncd files for 2018 in the same repo? It'd be great for all of us to have access to these files in order to hunt for differences

[Nickolka]

Originally Posted by Almaretto

Not needed for 2018. VO coding takes care of FEM and KAFAS.

ok, but the the xml that pmooiweer posted is expected to make all the changes to FEM_BODY without ever VO coding the module. So I am wondering if he had just accidentally missed the Step 3 or it is indeed no longer changes with VO coding.

The codes that we are expected to change to in Step 3 of enabling HGBL actually contain F80/F82, unlike the original codes the are in the FEM_BODY ncd

Does anyone have a Euro CAFD_00000794_016_064_014.ncd from 2018 F80/F82 they could post here?

LUT_AFS_CODRV_VERT

• orig: F030_F34_LEDhigh = 00 00 00 00 00 00 00 18 23
• new: F030_F32/F33/F36/F80/F82/F83_LED = 00 00 00 15 00 00 0A 15 1F

LUT_HBA_DRV_VERT

• orig: F030_F34_LED_High = 00 00 00 00 CD 00
• new: F030_F32/F33/F36/F80/F82/F83_LED_ECE = 2E 3B 00 00 00 00

LUT_HBA_CODRV_VERT

• orig: F020_F22/F23/F87/F88 = 00 00 00 00 00 00
• new: F030_F32/F33/F36/F80/F82/F83_LED_ECE = 2E 3B 00 00 00 00

LUT_HBA_DRV_HOR:

• orig: F030_kein_AFS/bFLA = 00 00 00 00 00 00
• new: F030_F32/F33/F36/F80/F82/F83_LED_ECE = 00, 00, 00, 00, 00, 00

LUT_HBA_CODRV_HOR:

• orig: F020_F20/F21 = 00 00 00 00 00 00
• new: F030_F32/F33/F36/F80/F82/F83_LED_ECE = 00, 00, 00, 00, 00, 00

[Almaretto]

Originally Posted by Nickolka

ok, but the the xml that pmooiweer posted is expected to make all the changes to FEM_BODY without ever VO coding the module. So I am wondering if he had just accidentally missed the Step 3 or it is indeed no longer changes with VO coding.

Dmnc02's PDF is for pre-LCI.

You can create your own NCD's.

[Nickolka]

Originally Posted by Almaretto

Dmnc02's PDF is for pre-LCI.

You can create your own NCD's.

Thanks! I generated the NCD files with 5AP and 8S4 removed from FA and can confirm that the changes in the FEM_01 for GFHB are exactly what pmooiweer added to the posted .xml file and the original Step 3 for 2015' that reprograms LUT_AFS_xxxx and LUT_HBA_xxx seem to indeed no longer be required for 2018's

Now, would you know the way to generate FLE ncd with Euro settings? Do I need the complete Euro FA or mine could be modified to achieve this? I tried switching the country code from Canada 831 to Germany 801 and removing the country code altogether but it always spits out US FLE ncd in the trace

[audioMeth]

Originally Posted by Almaretto

Dmnc02's PDF is for pre-LCI.

You can create your own NCD's.

do you have a list of shortcut posts bookmarked? every time you do this i learn something new and i think it would make a great sticky.

Originally Posted by Nickolka

Thanks! I generated the NCD files with 5AP and 8S4 removed from FA and can confirm that the changes in the FEM_01 for GFHB are exactly what pmooiweer added to the posted .xml file and the original Step 3 for 2015' that reprograms LUT_AFS_xxxx and LUT_HBA_xxx seem to indeed no longer be required for 2018's

Now, would you know the way to generate FLE ncd with Euro settings? Do I need the complete Euro FA or mine could be modified to achieve this? I tried switching the country code from Canada 831 to Germany 801 and removing the country code altogether but it always spits out US FLE ncd in the trace

change your Typenschlüssel to the euro version, 8M93 to 8M91. i tried this a couple days ago and then compared in TM compare tool.

[Almaretto]

Originally Posted by audioMeth

do you have a list of shortcut posts bookmarked? every time you do this i learn something new and i think it would make a great sticky.



change your Typenschlüssel to the euro version, 8M93 to 8M91. i tried this a couple days ago and then compared in TM compare tool.

Commonly asked I do.

Yes, that is how to do it.

[audioMeth]

Originally Posted by Almaretto

Commonly asked I do.

care to share it?

[Almaretto]

Originally Posted by audioMeth

care to share it?

Dozens of bookmarks and not organized into a post that would make sense. Plus, in folders for different chassis or topics.