Forum

Hallo Zusammen,

ich habe einen E60 (07/2003) mit Xenon , Kurvenlicht und Leuchtweitenregelung. 
Ich würde gerne auf den LM2 umsteigen, damit ich Dinge wie Welcome Lights , Heimleuchten usw. kodieren lassen kann.

Kann ich das LM2 einfach austauschen und fertig oder muss ich da irgendwelche Dinge einstellen lassen ?
Worauf müsste ich beim LM2 achten, dass es bei mir funktioniert?

Ich bedanke mich im Voraus.

VG
Dogukan 

DIY aus 5series.net

Before Oct 2006 our cars were fixed with an LM1, after that the LM2 was introduced which has a lot of more functions.

I managed to find an LM2 quite cheap from a breaker. Remember that there are various part numbers depending on what lights you have but in the LM2 there are basically two versions one for Xenons and the other Halogens.

These are the steps that I followed to swap the LCM.

1. The actual swap is very straight forward and just involves removing the screw holding the LCM and pulling downward. There is only 1 screw holding the LCM, the other side is held by a metal catch.
2. Next I had to reprogram the LCM. The LCM is the other module in the car that holds the VO, the other being the CAS.
3. Load NCSExpert and choose the CAS and then choose "Enter FA", just copy the complete VIN number that pops up. Close NCSExpert.
4. Load INPA and check the "Ident" of the LMA module and check the part number there. Note that down. Close INPA.
5. Load WinKFP and choose "Comfort Mode", "Choose ZUSB", in the ECU family choose LM460 and make sure that the part number that you took down in Step 4 shows up on the ZB-Number list, other choose another ECU family. Click cancel and then choose "Update ZUSB" and choose LM460 and click OK. Next click "Enter Vin" and enter the VIN number that you copied in Step 3. Click "Done". You will now see a "Prog ZB-Update", cick that. The module will start getting coded and the UIF will be written, which means that the VIN will have been updated. Close WinKFP.
6. Load NCSExpert and then choose the CAS and then using the "FA_WRITE" job process the LMA ECU. Basically what this does is copies the VO from the CAS to the LMA.
7. When you start NCSexpert and instead of choosing CAS you choose LMA you will notice that the old VIN number still loads. This was a big mystery to me because everywhere I could see my VIN instead of the old VIN in the UIF but yet NCSExpert seemed to find it somewhere. Perform a "Read ECU" and note down the .prg file that NCS is using for the LM2. Close NCSExpert.
8. To fix this load Tool32 and load up the .prg file that you noted in Step 7. (my first time using Tool32 btw)
9. Here using trial and error I found a job called "read_fgvin", which when run showed me the old VIN. I then loaded up the job "write_fgvin" which requires one argument and I supplied the VIN noted in Step 3. I ran the job and then when I ran "read_fgvin" again I saw my VIN.
10. Checked this in NCSexpert again and it was my VIN. Makes me think that I didn't need to run Step 5 (WinKFP) at all to update the VIN because the software on the LM2 was already the most recent. Anyway doing that made INPA detect the correct VIN on my LM2 as previously it was just reporting "yyyyyyy" instead of a VIN number. I was also given to understand that you can used the job "FGNR_Schreiben" in NCSexpert to change the VIN of an ECU but for some strange reason that Job doesn't show up for the LMA ECU.
11. Load NCSexpert "Expert Profile" with a blank .man file and just process the LMA ecu again, this will code the LMA to the new VO.

Job done.

P.S. : This DIY assumes you know how to use the tools mentioned here. Please don't ask me how to use them.