[PearlWhite]

Hi all

I have a 2017 F30 that came with adapative LED lights from the factory.

Lately I have been getting a Right High Beam Headlight Failure warning popping up on the dashboard and making a "ding" sound every minute when driving.

The high beam headlight and all other lights are actually functioning fine. But the warning message is very annoying.

Speaking to the dealer they said it might be the lighting electronic module board that is malfunctioning, and that it would cost $$$$ to replace (the car is out of warranty).

I am not in the financial position to pay for the replacement right now.

Is there any way to code out such warnings using E-sys?

Much appreciated in anticipation.

[TheNine90]

Which fault code do you have?

[PearlWhite]

Thanks

When I scanned with ISTA, I got code 805B15 - low beam headlights: Open circuit.

Which is funny, cos dashboard said highbeam failure.

I coded AL_R_KURZSCHLUSS and FL_R_KURZSCHLUSS (I think it's something to do with short circuit check) to nicht_aktiv in FEM using e-sys, but the error still shows up.

Is there a parameter relating to general error message display that I can code to inactive?

Cheers

[TheNine90]

That error code can be disabled in fem

[PearlWhite]

Dear TheNine90

Can you please detail how to disable the error message in FEM?

Many thanks,

[TheNine90]

In fem cafd look for dtc inhibit and enter the error code

[PearlWhite]

Thanks for that!

So I have found in FEM CAFD, a parameter called DemDtcInhibition

I found a line that has Werte=00, 00, 00, 00

Replaced it with the relevant error code (805B15) as Werte=00, 80, 5B, 15
I changed the "off" to "initwert"

Please see the first picture attached.

However, when I rechecked to see if the coding was successful, I got what you see in the second picture: the "initwert" got changed to "UNKNOWN". If I changed the "UNKNOWN" back to "initwert", then the Werte value went back to 00,00,00,00


Have I done something wrong?

[TheNine90]

Leave it like that, it wont affect anything

[PearlWhite]

Thanks TheNine90

However, the dashboard, as well as ISTA+ are still showing the same fault code.

Are there any other steps I need to take in e-sys to enforce the DTC inhibition?

Cheers

[TheNine90]

try change the location.
If you put custom data in esys it will show as UNKNOWN

[PearlWhite]

Hi theNine90

Can you explain a bit more on what you meant by "changing the location"?

Thanks

[TheNine90]

put it in dtcinhibition 0 or 1

[stefan28]

I have exactly the same problem. One led on the right side (dimmed beam) does not work when the faultcode is stored. Directly after when i reset the faultocde the lamp works perfect.

When i drive with automatic lights and the light are off beacause of the daylight the faultcode sometimes came back after 1,2 or 3 days. It is something like a bulb check, even when the headlights are off.

I did a software update with esys to version F20-22-11-504, no difference.

Tried to do the above things and tried to delete the faultcode with dtcinhibition. I tried dtcinhibition2 because slot dtcinhibition0 and dtcinhibition1 are used. The fault message front right headlight beam still came back.

@PearlWhite did you find a solution?

[PearlWhite]

Hi Stefan

No, not yet, I haven't fixed the error.

I am starting to think there is another place in the coding parameter to switch off this error display...

Alternatively, if there is a parameter to code out the LED check...

[PearlWhite]

another funny thing is, when I go into the BMW "secret menu" on the dashboard, under the DTC menu, there is no error codes displayed.

Yet the "high beam headlight failure" still popped up in idrive

[stefan28]

Hi PearlWhite,

I think i fixed my problem. After switching the headlight modules from left to right the problem stayed in the right headlight. The led was permanent off in the right headlight, reset did not solve the problem this time.

After i removed the headlight i found where the led bulb is located, and saw a small white connector on a printplate of the led light. The cable holder nearby was not in his position and this gets my attention. The connector felt a litle bit loose and it was possible to press it down a litle bit. I did put some contact spray on it and put the cable mounting (tie-wrap with mounting clip) in place.

After putting the headlight back on, a faultcode and module reset the led in the headlight is working again. The faultcode did not came back after 8 test drives.

You can acces the connector via the round cap (with a plastic cord on it) in the headlight under the hood, i think it is not necessary to remove the complete headlight. it's worth a try to take a look!

[PearlWhite]

Hi Stefan28,

I tried what you did, and no more errors!

Fantastic work.

A hardware fix is always going to be the best method!

Thanks again

[sverig]

I had exactly this problem, I solved it by pulling the contact out through the hatch, the final contact was broken and it was only holding on to the insulation.

[valeron06]

Originally Posted by sverig

I had exactly this problem, I solved it by pulling the contact out through the hatch, the final contact was broken and it was only holding on to the insulation.

I have the same problem too. The daytime running lights, namely the angel eyes, work after coding with ESYS and after 1 day, they malfunction and turn off on their own. What do you recommend me to do?

[ccqwerty]

Did you do the adaptive code out before messing with the clip on the module?
I unplugged mine worked for a few mins then went back to being bad so I’m wondering if I should get the adaptive lightening coded out too