Help need with replacing LEd headlight

[dzvero]

I replaced my headlight and the "new" used one is giving me problems.Turn signal is not working. the turn lights on back and mirror are working but not on the headlight. I think I'm doing it right with Rheingold. I select LHMR and code it to the car, it turns green on next check and all errors related are cleared. Then I select STMR an code it also but its always yellow. I can turn headlights on and off no issues. Any advise how to find if the turn signal module is working or not? Dont wont to buy new one to find out its something else. Also not sure if this is related but I got this error :

[dzvero]

Looks like that error is level sensor related.

[ferrarif1]

Did you "teach-in" the new LED light?

[dzvero]

I think I did. there is no problem with high/low beam etc. Do you have some doc explaining how it has to be done? I did select both ecu's , components triggering and did every item listed there. As I mentioned after that the LHM was clear of errors but STM did stay yellow. I was able to turn headlights on from the switch and they worked. Will try to open the turn signal module tonight. Hope to be bad connection or something easy to fix.

[dmnc02]

The "teach in" procedure is not under the ECU "component actuation" menu, but under Vehicle Management > Service function > Body > Lighting. The turn signal malfunction is exactly what you would get if you did not run this procedure (which, per BMW instructions, is required after a headlight replacement).

[dzvero]

Thanks ! Much appreciated ! Will try tonight.

[dzvero]

Worked , Thank you so much ! I gues I need to reinstall my Instaa as it is missing documents , instructions etc

[te37]

Can the same teach procedure be used if someone were to upgrade from xenon to led headlights?

[dmnc02]

Originally Posted by te37

Can the same teach procedure be used if someone were to upgrade from xenon to led headlights?

Yes, it needs to be performed each time a new LED headlight is installed.

[dzvero]

I disconnected the battery and got errors again. Do I need to teach headlights every time I disconnect the battery? Is that normal?

[dmnc02]

Originally Posted by dzvero

I disconnected the battery and got errors again. Do I need to teach headlights every time I disconnect the battery? Is that normal?

I don't think this is normal. What errors are you getting exactly?

In any case, you could try to "Calculate test plan" in Rheingold and see whether or not it suggests to run the teach in procedure again.

[te37]

Originally Posted by dmnc02

Yes, it needs to be performed each time a new LED headlight is installed.

I was asking if I had Xenon lights and upgraded/ retrofitted to LED headlights if Rheingold is needed to let the car know if has different lights installed? I'm sure its not plug and play.

[dmnc02]

Originally Posted by te37

I was asking if I had Xenon lights and upgraded/ retrofitted to LED headlights if Rheingold is needed to let the car know if has different lights installed? I'm sure its not plug and play.

That is correct: the retrofit is not going to be plug-and-play. A few ECUs will have to be recoded and Rheingold will be needed to initialize the retrofitted LED headlights.

[CaryTheLabelGuy]

Originally Posted by dmnc02

That is correct: the retrofit is not going to be plug-and-play. A few ECUs will have to be recoded and Rheingold will be needed to initialize the retrofitted LED headlights.

Can this coding be done in E-Sys or is ISTA/P required?

[dmnc02]

Originally Posted by CaryTheLabelGuy

Can this coding be done in E-Sys or is ISTA/P required?

All the coding can be done in E-Sys.

[CaryTheLabelGuy]

Originally Posted by dmnc02

All the coding can be done in E-Sys.

Really. I plan on doing this retrofit at some point in the near future, with a pair of F32 LED headlights (on my F82 M4 ZCP).

Can you point me in right direction as far as the actual coding is concerned?

[dzvero]

Originally Posted by dmnc02

I don't think this is normal. What errors are you getting exactly?

In any case, you could try to "Calculate test plan" in Rheingold and see whether or not it suggests to run the teach in procedure again.

It is the same as if i never did teaching. Is also teaching the only step necessary? After teaching they still have errors and deleting them doesnt clear. I have to call each ecu and ecu functions and do some test and it activates them . After that i got no errors until battery is disconnected. Calculate plan shows teaching.

[dmnc02]

Originally Posted by dzvero

It is the same as if i never did teaching. Is also teaching the only step necessary? After teaching they still have errors and deleting them doesnt clear. I have to call each ecu and ecu functions and do some test and it activates them . After that i got no errors until battery is disconnected. Calculate plan shows teaching.

If the test plan shows that the teach in procedure is required, then it is. I am not sure why it happens each time you disconnect the battery.

[dmnc02]

Originally Posted by CaryTheLabelGuy

Really. I plan on doing this retrofit at some point in the near future, with a pair of F32 LED headlights (on my F82 M4 ZCP).

Can you point me in right direction as far as the actual coding is concerned?

It is going to be just VO coding: replace 524 (Adaptive Xenons) with 552 (Adaptive LEDs) in the FA and then VO code FEM_BODY, KAFAS, both LHM, both TMS, ICM, VDC and REM.

[dzvero]

Behavior was right headlight wont remember teaching / adaptation. Turn ignition off and I had to adapt again . Specifically LHMR. So after another flash and disconnecting battery it seems to work.

[lemetier]

Stumbled across this for another reason but think I have an answer incase anyone else runs into a problem with modules after using Rheingold. It appears some tests and service jobs are not actually completing the necessary functions; Headlight Electronics especially. In addition, Service Plan Actions and Test Modules that are not supported by the Boolean plausibility checks of the available VCS OrderData are sometimes being loaded by ignoring Boolean parameters until there are no more remaining to filter or the OK to deploy conditions are met. this continues on and on. For anyone who has used the program for replacement of LED Headlamp components or to perform teach-in/alignment after coding to enable GFHB or VLD, it's worth a look at the session logs in the main program folder. Search for these keywords:

die
fingers crossed
bogus
verbose - a typo for verbote(n)
default
CAS
DME
kein

This doesn't appear to be an installation issue but a problem with the patches utilized to proceed beyond the errors associated with conflicts between the actual vehicle configuration and the saved data both on the computer and in the car itself. The default data for the chassis obtained from the backup data in other modules or a manipulated data set is applied to force the job to process or appear to. This remains until the module is triggered to boot from the still unchanged eeprom backups. For a used replacement component, that backup is no longer valid. Hopefully a few of you will check and report back.

[dzvero]

+1