[Almaretto]

Originally Posted by MrMarvin

Alright, but the 04 value gives me 100% as of now, so the 64 is basically the same? Or maybe the 04 value isn't 100%? Sorry if i'm being dumb!

LHM/TMS & FLE ECU Light modules are a bit more complicated, but there is still some logic.

I do not have all details of your CAFD, but I believe this is correct:

• 04 hex = 04 decimal
• Then you go to LmmIdx04_Intensity = 64 hex = 100 (%) decimal

My F015's FLE's (CAFD_000024C3) are a little different, but hopefully this example further explains architecture:

• DRL_Idx:
  • 01 01 0A 01 01 01 01 01 01 0B
    • 0A hex = 10 decimal
    • LmmIdx10_Intensity: 64 = 100% DRL
• POLI1_Idx:
  • 01 01 0C 01 01 01 01 01 01 0B
  • 0C hex = 12 decimal
  • LmmIdx12_Intensity: 29 = 41% Angel Eye with low beam

So, to change brightness (ie intensity), you have two options:

1. Change the werte in section 3004 (eg, POLI_IDx, POLI_IDx, POLI_IDx for low beam)
   • It can get a little confusing because larger hex can reference smaller numbers (eg, 0A --> 10 --> 100% vs 0C → 12 → 41%). You cannot simply change 04 to 64 because there are only 26 (ie LmmIdx##, where ## = 1-26)
2. Change the corresponding werte in section 3005 (eg, LmmIdx##_Intensity)

[userix]

Originally Posted by Almaretto

LHM/TMS & FLE ECU Light modules are a bit more complicated, but there is still some logic.

I do not have all details of your CAFD, but I believe this is correct:

• 04 hex = 04 decimal
• Then you go to LmmIdx04_Intensity = 64 hex = 100 (%) decimal

My F015's FLE's (CAFD_000024C3) are a little different, but hopefully this example further explains architecture:

• DRL_Idx:
  • 01 01 0A 01 01 01 01 01 01 0B
    • 0A hex = 10 decimal
    • LmmIdx10_Intensity: 64 = 100% DRL
• POLI1_Idx:
  • 01 01 0C 01 01 01 01 01 01 0B
  • 0C hex = 12 decimal
  • LmmIdx12_Intensity: 29 = 41% Angel Eye with low beam

So, to change brightness (ie intensity), you have two options:

1. Change the werte in section 3004 (eg, POLI_IDx, POLI_IDx, POLI_IDx for low beam)
   • It can get a little confusing because larger hex can reference smaller numbers (eg, 0A --> 10 --> 100% vs 0C → 12 → 41%). You cannot simply change 04 to 64 because there are only 26 (ie LmmIdx##, where ## = 1-26)
2. Change the corresponding werte in section 3005 (eg, LmmIdx##_Intensity)

I got my left side to work with 100% rings with lowbeams, but I can't get the right to go 100%. I checked both FLE modules and having changed the first FLE POLI1_Dx to 64 hex, the second FLE module already changed to 64 hex for POLI1_Dx by itself, but the right rings still stay at 41% with lowbeams.

[stu14t]

Originally Posted by userix

I got my left side to work with 100% rings with lowbeams, but I can't get the right to go 100%. I checked both FLE modules and having changed the first FLE POLI1_Dx to 64 hex, the second FLE module already changed to 64 hex for POLI1_Dx by itself, but the right rings still stay at 41% with lowbeams.

It sounds like you haven't coded the second FLE correctly and it is still holding the first ncd file. Make sure you load both CADF files and code them individually.

I think I may be misunderstanding what you say but you should not be setting the POLI_idx to 64. as Almaretto says, it should be the corresponding LmmIdx Intensity associated with the DRL

[MrMarvin]

Originally Posted by Almaretto

LHM/TMS & FLE ECU Light modules are a bit more complicated, but there is still some logic.

I do not have all details of your CAFD, but I believe this is correct:

• 04 hex = 04 decimal
• Then you go to LmmIdx04_Intensity = 64 hex = 100 (%) decimal

My F015's FLE's (CAFD_000024C3) are a little different, but hopefully this example further explains architecture:

• DRL_Idx:
  • 01 01 0A 01 01 01 01 01 01 0B
    • 0A hex = 10 decimal
    • LmmIdx10_Intensity: 64 = 100% DRL
• POLI1_Idx:
  • 01 01 0C 01 01 01 01 01 01 0B
  • 0C hex = 12 decimal
  • LmmIdx12_Intensity: 29 = 41% Angel Eye with low beam

So, to change brightness (ie intensity), you have two options:

1. Change the werte in section 3004 (eg, POLI_IDx, POLI_IDx, POLI_IDx for low beam)
   • It can get a little confusing because larger hex can reference smaller numbers (eg, 0A --> 10 --> 100% vs 0C → 12 → 41%). You cannot simply change 04 to 64 because there are only 26 (ie LmmIdx##, where ## = 1-26)
2. Change the corresponding werte in section 3005 (eg, LmmIdx##_Intensity)

Thanks for the info! Really appriciate it, i definately have to explore this further. Right now this is a bit above my level, but i'll get there.

[Almaretto]

Originally Posted by MrMarvin

Thanks for the info! Really appriciate it, i definately have to explore this further. Right now this is a bit above my level, but i'll get there.

[myszano1]

Originally Posted by Don Juan

These were the best 2 explanations I found after hours of searching for my 2016 F15. It is finally coded with bright DRLS!! thank you guys.....

NOw is you please can help me decipher where the damn drl files are for an I3 Will appreciate tremendously...I did the original changes to :
Increase DRL Brightness to be brighter (increases voltage to the LED Bulbs)
3062  MAPPING_STANDL_V_L_PWM_LEVEL_1 set to: 13.7v/100%
3062  MAPPING_STANDL_V_R_PWM_LEVEL_1 set to: 13.7v/100%
3062  MAPPING_PARKL_1_V_L_PWM_1_LEFT set to: 13.7v/100%
3062  MAPPING_PARKL_1_V_L_PWM_2_RIGHT set to: 13.7v/100%
but nothing

here is a screen shot of my files... any help will be much much appreciated

Hi, anyone know how to change brightness parking DRL.
Dlr i have 100%
parking I have 100% but want to dim to 50%
and drl with low beam I have 8%.


Also I dont have in esys "MAPPING_PARKL_V_L_PWM_LEVEL_1 "

Please advice guys.

Cheers

[Almaretto]

Originally Posted by myszano1

Hi, anyone know how to change brightness parking DRL.
Dlr i have 100%
parking I have 100% but want to dim to 50%
and drl with low beam I have 8%.


Also I dont have in esys "MAPPING_PARKL_V_L_PWM_LEVEL_1 "

Please advice guys.

Cheers

http://f30.bimmerpost.com/forums/sho...d.php?t=696777

[Jdmdc5teg06]

I wanted to code my angel eyes DRL (not with my low beams, just DRL and welcome light) to 100% the other day but they didn't get as bright as they should've been. One of my other friends that's a member on here as well did his halo's the same way that night and his got so bright that they looked washed out but they actually worked for him. We both followed the same f30 cheat sheet and changed the values through FEM_BODY. We also both have retrofitted lights, not the factory angel eyes. Where else should I look to change the values of mine? It currently say they're running at 100% but they're not the brightest they can go. They are nowhere "washed out". I just want to see how it looks like with my BSM during the day since mine during the day look dim

[stu14t]

Originally Posted by Jdmdc5teg06

I wanted to code my angel eyes DRL (not with my low beams, just DRL and welcome light) to 100% the other day but they didn't get as bright as they should've been. One of my other friends that's a member on here as well did his halo's the same way that night and his got so bright that they looked washed out but they actually worked for him. We both followed the same f30 cheat sheet and changed the values through FEM_BODY. We also both have retrofitted lights, not the factory angel eyes. Where else should I look to change the values of mine? It currently say they're running at 100% but they're not the brightest they can go. They are nowhere "washed out". I just want to see how it looks like with my BSM during the day since mine during the day look dim

What have you retrofitted? LED or Xenon?

Are they OEM or third party lights?

[Jdmdc5teg06]

Originally Posted by stu14t

What have you retrofitted? LED or Xenon?

Are they OEM or third party lights?

Sorry I thought I disclosed that information as I was thinking it lol. We both have third party LED retrofits. They both work the same as factory and light up as factory. Have the same DRL led module etc.. I'm just not sure why his got coded to extremely bright and mine got brighter, but not as bright as his.

It's not a big deal at all to me as I only wanted to see what they looked like in my car but I definitely want to try it out and see. We only coded 2 files under FEM_BODY... which are these

MAPPING_TAGFAHRL_V_L_PWM_LEVEL_1 (set at 64 - 100%)

MAPPING_TAGFAHRL_V_R_PWM_LEVEL_1 (set at 64 - 100%)



I'm only looking to change the brightness on the daytime running lights, not while my low beams are on.

[stu14t]

Adding non OEM lights to the mix adds a whole new dimension to things.

Bit strange your friend got it to work and your's didn't

[Jdmdc5teg06]

Originally Posted by stu14t

Adding non OEM lights to the mix adds a whole new dimension to things.

Bit strange your friend got it to work and your's didn't

Exactly lol. I even coded them to 32- 50% and mine dimmed to 50% and I took it back up to 100% but it's still not the brightest. Oh well, I guess I'll just leave them how they are. Should I try changing anything on what I was reading earlier in this thread? or is that only for DRL with low beams?

[stu14t]

Originally Posted by Jdmdc5teg06

Should I try changing anything on what I was reading earlier in this thread? or is that only for DRL with low beams?

It is for DRL with low beams but the process is generally the same and can be adapted. The issue is, there are different methods for different headlights.

The changes in FEM are primarily for cars with xenon headlights. If you have a LCI F30 with LED, then a different method is needed within two modules call FLE's. And if you have a pre-lci F32 with adaptive LED, you adjust values in the TMS modules.

Your non-OEM lights may or may not add custom modules and / or coding to the mix too.

[Jdmdc5teg06]

Originally Posted by stu14t

It is for DRL with low beams but the process is generally the same and can be adapted. The issue is, there are different methods for different headlights.

The changes in FEM are primarily for cars with xenon headlights. If you have a LCI F30 with LED, then a different method is needed within two modules call FLE's. And if you have a pre-lci F32 with adaptive LED, you adjust values in the TMS modules.

Your non-OEM lights may or may not add custom modules and / or coding to the mix too.

Thanks for your help dude! Greatly appreciated. I was confused when you asked what lights we have retrofitted. They aren't LED... they are the xenon lights that came on the pre LCI F30, not the lci led

[juju00799]

Hello all,

I try to modify to full brightness on Mini F57 2017 with FLE module.

I've this type of were value : 03, 03, 03, 03, 0A, 0A, 03.

Anyone know which value to have full brightness with headlight on ?

Thanks

[Almaretto]

Originally Posted by juju00799

Hello all,

I try to modify to full brightness on Mini F57 2017 with FLE module.

I've this type of were value : 03, 03, 03, 03, 0A, 0A, 03.

Anyone know which value to have full brightness with headlight on ?

Thanks

Werte values correspond to LmmIdx##_Intensity in 3004.

Without more information, it would be hard to advise.

[Pedrom92]

Hello, anyone know values for change welcome lights to 100% brightness in BMW F31?
Thanks

[Almaretto]

Originally Posted by Pedrom92

Hello, anyone know values for change welcome lights to 100% brightness in BMW F31?
Thanks

It depends on headlight type and year.

[Pedrom92]

Led headlights non adaptative, FLE module. My car is 2013 but i retrofit headlights. Donor headlights is 2018.

[Almaretto]

Originally Posted by Pedrom92

Led headlights non adaptative, FLE module. My car is 2013 but i retrofit headlights. Donor headlights is 2018.

This may help: https://f30.bimmerpost.com/forums/sh...9&postcount=29

Basically have to compare DRL_Idx to POLI1_Idx to discover which bit is halo. Then, modify WELL1_Idx, WELL2_Idx, WELL3_Idx, & WELL4_Idx accordingly or corresponding intensity level in other section.

[bringmywallet]

Originally Posted by Almaretto

LHM/TMS & FLE ECU Light modules are a bit more complicated, but there is still some logic.

I do not have all details of your CAFD, but I believe this is correct:

• 04 hex = 04 decimal
• Then you go to LmmIdx04_Intensity = 64 hex = 100 (%) decimal

My F015's FLE's (CAFD_000024C3) are a little different, but hopefully this example further explains architecture:

• DRL_Idx:
  • 01 01 0A 01 01 01 01 01 01 0B
    • 0A hex = 10 decimal
    • LmmIdx10_Intensity: 64 = 100% DRL
• POLI1_Idx:
  • 01 01 0C 01 01 01 01 01 01 0B
  • 0C hex = 12 decimal
  • LmmIdx12_Intensity: 29 = 41% Angel Eye with low beam

So, to change brightness (ie intensity), you have two options:

1. Change the werte in section 3004 (eg, POLI_IDx, POLI_IDx, POLI_IDx for low beam)
   • It can get a little confusing because larger hex can reference smaller numbers (eg, 0A --> 10 --> 100% vs 0C → 12 → 41%). You cannot simply change 04 to 64 because there are only 26 (ie LmmIdx##, where ## = 1-26)
2. Change the corresponding werte in section 3005 (eg, LmmIdx##_Intensity)

Thanks Almaretto!
Had to read your post a couple of times, but now i was able to code my standing lights to 62% (3E) and my parking lights to 30% (1E in the unused LmmIdx26)

[acmilangr]

Originally Posted by dmnc02

I am assuming that this is a US-spec F30 with the non-adaptive LEDs.

If so, the easiest way to change the halo rings to 100% when used as position lights is to set POLI1_Idx, POLI2_Idx and POLI3_Idx in both FLEs to

00, 00, 00, 05, 00, 00, 04, 00, 00, 00.

To change them to 60% instead, set POLI1_Idx, POLI2_Idx and POLI3_Idx in both FLEs to

00, 00, 00, 05, 00, 00, 0F, 00, 00, 00

and then code

LmmIdx15_Intensity = 3C
LmmIdx15_Priority = 03

(edit the Werte values directly) in both FLEs.

Hello. I know this is old, but i have a question
What LmmIdx15_Priority value is for?