[TheNine90]

Check the coding for the headlight levelling. Can you do reference run for the headlight and see if they move

[AntiTGU]

All wiring for leveling headlights is working, I rang from fem to each headlight. The headlights themselves look factory and serviceable. But it is not exactly. I have no guarantees that the problem is not in the headlights. I think it's a matter of coding. help with coding. I code FEM and FLE under US - leveling does not work, I encode under Euro - the same thing. does not work (((. I've never seen those headlights move. The leveling test does not pass through diagnostics and they do not move.
Check the coding for the headlight levelling - What exactly are the parameters? in FEM or FLE? I have saved CAFD

[TheNine90]

Fem
lwr_ahl_type

[AntiTGU]

LWR_AHL_TYP == auto./dyn. LWR [02]

[Ovas]

Hello guys

I have F36 USA. I take off adaptive headlights and install lci led (europe).
So whats process now with coding? What i have to change? Better ussing esys or ista?
Pls help. Can please explain consistently. Pm with photos or here

[lllRazorlll]

Has anyone who has retrofitted pre-LCI OEM adaptive LED headlights to a 435i experienced any issues with low battery warnings? I am seeing messages pop up for a low battery and when the car is turned on to ignition but not started, everything shuts down.

I also noticed that none of the exterior welcome lights are working when unlocking the car. Any help would be appreciated

[TheNine90]

Originally Posted by AntiTGU

LWR_AHL_TYP == auto./dyn. LWR [02]

Try ohne

Originally Posted by Ovas

Hello guys

I have F36 USA. I take off adaptive headlights and install lci led (europe).
So whats process now with coding? What i have to change? Better ussing esys or ista?
Pls help. Can please explain consistently. Pm with photos or here

Remove 524 and add 552. Then change typecode to ECE.

[grahams]

Hi All,

Can I ask for some assistance with coding standard BMW LED to > BMW Adaptive LED (AHL).

Build 11/2016 F31 335d
UK Car, right hand drive, left driving
Type code 8L12
Came standard with LED 5A2

Modules are those from my car (as they as LED/AHL are cross compatible)

Have a problem coding the FLE and REM
Remove 5A2, add 552, calculate, save, load into coding.
Right click FEM_BODY > Code > Successful
FLE43/FLE44/REM, 2 Errors
cdDeploy FinishedWithError
cafd_000024c3-008_035_000 Finished With Error

ESYS PXdzData 4.43.10 - full data

All support much appreciated.

[TheNine90]

Which error exactly is it? Can you try coding without launcher

[grahams]

Originally Posted by TheNine90

Which error exactly is it? Can you try coding without launcher

Hello
I'm coding without a launcher.
The final box shows

FLE[43]
cdDeploy FinishedWithError
cafd_000024c3-008_035_000 FinishedWithError

Full Log

<Caf's suchen>
TAL calculation started.
Locally NCD signature calculation started
Processing ncd signing finished
TAL execution started.
<>
Read SVT before TAL execution started.
TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated.
<run()-> Value of 'httpServerActivation': true>
<run()-> Value of 'isDeactivateHttp': false>
<ExecutionID=2023/12/24-20:54:59.857>
<[] prepareTALExecution started [PROGRESS]>
<[] prepareTALExecution finished [PROGRESS]>
<[] prepareVehicleForCoding started [PROGRESS]>
<[] prepareVehicleForCoding finished [PROGRESS]>
<[FLE - 43] prepareECUforCoding started [PROGRESS]>
<[FLE - 43] prepareECUforCoding finished [PROGRESS]>
<[FLE - 43] authenticateECUforCoding started [PROGRESS]>
<[FLE - 43] authenticateECUforCoding finished [PROGRESS]>
<[FLE - 43 - cafd_000024c3-008_035_000] Transaction type: cdDeploy; Message: TA started [TRANSACTION]>
<MCDDiagService<id=62649, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: negative response : requestOutOfRange, link=FLE_43_ETHERNET> [DIAGSERVICE]>
<[] job failed with negative response error:
code: repeat job
description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: FLE_43_ETHERNET
severity: ERROR
[THROWABLE]>
<[FLE - 43 - cafd_000024c3-008_035_000] Transaction type: cdDeploy; Message: TA finished [TRANSACTION]>
<[FLE - 43] -MessageID is used multiple times, so MessageText may be ambiguous-job failed with negative response error:
code: repeat job
description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: FLE_43_ETHERNET
severity: ERROR
[WARN]>
<[FLE - 43] - [Exception - FLE - 43] job failed with negative response error:
code: repeat job
description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: FLE_43_ETHERNET
severity: ERROR
>
<[FLE - 43] prepareECUforCoding started [PROGRESS]>
<[FLE - 43] prepareECUforCoding finished [PROGRESS]>
<[FLE - 43] authenticateECUforCoding started [PROGRESS]>
<[FLE - 43] authenticateECUforCoding finished [PROGRESS]>
<[FLE - 43 - cafd_000024c3-008_035_000] Transaction type: cdDeploy; Message: TA started [TRANSACTION]>
<MCDDiagService<id=62649, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: negative response : requestOutOfRange, link=FLE_43_ETHERNET> [DIAGSERVICE]>
<[] job failed with negative response error:
code: repeat job
description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: FLE_43_ETHERNET
severity: ERROR
[THROWABLE]>
<[FLE - 43 - cafd_000024c3-008_035_000] Transaction type: cdDeploy; Message: TA finished [TRANSACTION]>
<[FLE - 43] There was an error during TAL execution, please check the log files. [WARN]>
<[FLE - 43] - [Exception - FLE - 43] job failed with negative response error:
code: repeat job
description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: FLE_43_ETHERNET
severity: ERROR
>
<[FLE - 43] finalizeECUCoding started [PROGRESS]>
<[FLE - 43] finalizeECUCoding finished [PROGRESS]>
<[] There was an error, please check the log files. [WARN]>
<[] - [Exception - FLE - 43] job failed with negative response error:
code: repeat job
description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: FLE_43_ETHERNET
severity: ERROR
>
<[] finalizeVehicleCoding started [PROGRESS]>
<[] finalizeVehicleCoding finished [PROGRESS]>
<[] finalizeTALExecution started [PROGRESS]>
<[] finalizeTALExecution finished [PROGRESS]>
<TAL execution finished [TAL_EXECUTION_FINISHED]>
TAL-Execution finished with status: "FinishedWithError".
TAL execution finished. Duration: "10s".
<>
Read SVT after TAL execution started.
Read SVT after TAL execution finished.
TAL execution finished.

[TheNine90]

Have you tried flashing the FLE to same software as the vehicle?
Does the FLE appear in svt using READ ECU?

[dumitru.o]

try to calculate TAL and see if esys will suggest to replace modules ( differen HWEL). then you know for sure if the modules are the proper ones or not.

in the same time you will also flash them to the lastest ilevel ( same on both)

[grahams]

Thanks for the the suggestions guys.

The FLEs are those from my LED headlights (non-adaptive). The part numbers between standard LED and Adaptive LEDs are the same. I doubt but is there an ability to virginising if coding to perform a different function?

One adaptive headlight came with a module which confirms the HWEL is the same between adaptive and not.
The adaptive headlight was dated 2020-11-07. Car module 2016-10-21. Both have HWEL written on stating 2FE0 03.01.00

I suspect an istep/coding issue here.

TAL calculating on the latest istep with adjusted FA does suggest a different HWEL.
Current HWEL (2FE0)
Suggested HWEL (2B42)

[grahams]

Originally Posted by dumitru.o

try to calculate TAL and see if esys will suggest to replace modules ( differen HWEL). then you know for sure if the modules are the proper ones or not.

in the same time you will also flash them to the lastest ilevel ( same on both)

As the modules are original to the car I can update them to the latest istep using the original VO. Would you suggest this before proceeding?

[dumitru.o]

Try to calculate tal for ilevel update. If esys calculates different hwel for those modules then are not good for your new headlights

If good (hwel black) then update them and try code again, then initialize

Use the new VO, not the original one. Your main goal is to see if the modules are the proper ones for your new headlights (nee VO)

Only after that the second goal is to update them.

If the modules are not the proper ones, then it doesn t matter if you update them or not, are useless anyway for the cause

[grahams]

Originally Posted by dumitru.o

Try to calculate tal for ilevel update. If esys calculates different hwel for those modules then are not good for your new headlights

If good (hwel black) then update them and try code again, then initialize

When I leave the VO with 5A2 (not adaptive) LED Headlights. Everything calculates as normal.

If someone with Adaptive has a copy of their HWEL that would help a huge amount. Real OEM shows no difference in part numbers.
The problem is that I would be purchasing identical part numbers which doesn't make sense.


5A2 (original VO)


552 (new VO)

[dumitru.o]

Just as i suspected, modules are not good for the job, you need proper modules for the new adaptive headlights

[grahams]

Originally Posted by dumitru.o

Just as i suspected, modules are not good for the job, you need proper modules for the new adaptive headlights

I see why you say that but help me with one thing, what would you purchase to replace them? The part numbers for 5a2 and 552 are identical for this build date of car. 11/16 8L12

That’s the only reason I expect they moved over HWEL in a subsequent istep and with the right istep HWEL with updated VO would be black. I see a reference to this behaviour in a previous post by Shaun.

[dumitru.o]

Can t comment on that...

I would check ETK and find the proper part # for the LED AHL modules.

I would always update the entire car to the latest ilevel to make sure everything works correctly (all modules have a proper communication with each other)

You do as you decide!

PS: always remember one thing: part # in ETK are one thing and part # on used modules from the car are another! A new module might work for both type of headlights but an used factory module might only work for that specific factory type of headlight!

[grahams]

Originally Posted by dumitru.o

Can t comment on that...

I would check ETK and find the proper part # for the LED AHL modules.

I would always update the entire car to the latest ilevel to make sure everything works correctly (all modules have a proper communication with each other)

You do as you decide!

PS: always remember one thing: part # in ETK are one thing and part # on used modules from the car are another! A new module might work for both type of headlights but a used factory module might only work for that specific factory type of headlight!

Here in lies my conumdrum, the numbers are identical which is a big challenge for purchase if replacement modules are truly required. What you say about same modules but fixed use once programmed makes me think there is a potential and rare use cases for TAL to update the HWEL (know that goes against everything on the internet)

Before proceeding further I’ll update the istep. And interrogate the module which came with one of the lights.

Again thanks for everyone’s assistance so far.

[mrpingu]

Originally Posted by dumitru.o

PS: always remember one thing: part # in ETK are one thing and part # on used modules from the car are another! A new module might work for both type of headlights but an used factory module might only work for that specific factory type of headlight!

grahams
This can be key in your problem. How do you know you have correct modules?

There are several examples where this applies. For example there exists FEM-mid, FEM-High and FEM-max. In ETK only FEM-max is listed as replacement part. So if you have to reorder a spare FEM you always get FEM-max but your car can have come with a FEM-mid. FEM-max supports all function where FEM-mid for example doesn’t have support for Comfort Access.

Not only FEM but also PMA/PDC module exists in 2 variants. Small
Processor and big processor, replacement part is always big processor but if your car is fitted with only 507 (rear PDC), chances are high you got a small processor module and won’t have support for upgrading to PMA. The small processor variant only has support for 4+4 sensors, while the bigger one can also handle the 2 extra sensors for the parkings assistant 5DP.

grahams
So in your case, how do you know you have the part number listed on realoem is also the one in your car?
Because of the different HWEL I suspect BMW has 2 different FLE modules whereas the replacement part is always the better/bigger variant.

What you can try is to calculate TAL and then use Actual HW ids and flash the whole module and see what happens.

[grahams]

Ok that’s a great help. I’ve come across that before but must have archived the knowledge!
Makes sense that factory fit is more specific than replacement parts.

Found a post which states HW 2FE0 is for LED and 2FE1 is required for AHL.

Couple of modules on order so will update once delivered. Great to have made progress.