[sfinks2]

Hello;

The car is e61 520d from 2007 with adaptive xenons turning to sides when steering wheel is turning. It also has H7 lights.

My lights started to behave strange (turning lights blinking fast etc.) so I have replaced LMA module to the one of the same part number (9137776). Directly after replacememnt everything seemed to work ok.

PROBLEM 1:
The "new" module is recognised in INPA, ISTA etc. as part number 9203082, which is different ECU family. I have discovered that the part number was changed in AIF records (perhaps in some other places too).

After this change based on "new" part number the module "belogs" to different ECU family than before and I want it back. 

How can I program it back (in AIF) to be recognised as 9137776? Is it possible to change module's part number in Tools 32 (AIF SCHREIBEN)? Or maybe some other way (I have Standard Tools, ISTA D+P)

PROBLEM 2:
To code the module to my car I have changed the VIN and FA in it, and coded it with empty MAN. Now I have even more strange behavior (fast blinkig turning lights, several bulbs errors popping up etc.).

What could be the reason? Is it something wrong with my FA? How to fix it? 


Any help would be very much appreciataed as such lights make the car not usable.

Thanks in advance and regards

[NeRkO20]

So it is a Pre-LCI model (H7 for High beam)

If it is same Part number it should work after coding. I think you mean with "partnumber" the "zusb"?

Zusb will change after update (flashing).

For coding u don´t need to change VIN, just VO-code the LMA

Do you have some fault codes in LMA?

[Alessandro Frisella]

you have to program the zubs you are interested in and then code to get the right functions
hoping your form is not ruined

if you need help I'm available, but give me time to translate, I use google translate.
if I have been of help to you, press thanks and reputation

[sfinks2]

Thanks Alessandro

My LMA directly afeter transplantation worked fine. Then:
* VIN change - done OK
* FA write as per CAS - done OK
* Programing ECU with WinKFP - done OK
* Coding with empty MAN - done OK
and now I have a blinking Christmast Tree - errors everywhere.
I thought that coding with empty MAN should give me the standard factory settings according to my VIN but something apparently does not work.

Thank You guys.
I will try some detailed coding and come back with feedback.

[Node]

I don't understand your problem. 9203082 and 9137776 are THE SAME LM460 module. Just 9203082 is the LAST firmware version for it, while 9137776 is much OLDER. AIF has NOTHING to do with your problem.

If you want to downgrade it to 9137776 you will have to find old daten files and flash. But I have no idea why you would want to do that. Solve your coding (or maybe car, given old LM seems to have had same behaviour as new one) issue and you will be done.

[sfinks2]

I don't understand your problem. 9203082 and 9137776 are THE SAME LM460 module. Just 9203082 is the LAST firmware version for it, while 9137776 is MUCH older. AIF has NOTHING to do with your problem.

If you want to downgrade it to 9137776 you will have to find old daten files and flash. But I have no idea why you would want to do that. Solve your coding (or maybe car, given old LM seems to have had same behaviour as new one) issue and you will be done.

Thanks.

How can I know that this is the same module? Used to be "family" LM2_E6X_C33 and now is something else....

Before coding / programming worked well with wrong VIN/FA so I think the car is OK. Where my coding problem may be?

Wodner why coding with empty MAN dod not work. Is it normal?
Looks like I need to code it manually option-by-option....
Pity

[bmchicago]

just use ISTAP if you cant figure it out with NCS.

[Node]

I don't understand your problem. 9203082 and 9137776 are THE SAME LM460 module. Just 9203082 is the LAST firmware version for it, while 9137776 is MUCH older. AIF has NOTHING to do with your problem.

If you want to downgrade it to 9137776 you will have to find old daten files and flash. But I have no idea why you would want to do that. Solve your coding (or maybe car, given old LM seems to have had same behaviour as new one) issue and you will be done.

Thanks.

How can I know that this is the same module? Used to be "family" LM2_E6X_C33 and now is something else....

Before coding / programming worked well with wrong VIN/FA so I think the car is OK. Where my coding problem may be?

Wodner why coding with empty MAN dod not work. Is it normal?
Looks like I need to code it manually option-by-option....
Pity

I have no idea whether this module is supposed to be in your car as no VIN was provided. I have no idea if your car options are correct as they were not provided either. And I have no idea why coding did not work for you as I don't know whether you understand how to use NCSExpert. So unless you provide more information - use ISTA-P to do the work for you.

I also have no idea what "family LM2_E6X_C33" is. Looks like a mashup of various designations including coding index. Which depends on firmware version.

[NeRkO20]

So it is a Pre-LCI model (H7 for High beam)

If it is same Part number it should work after coding. I think you mean with "partnumber" the "zusb"?

Zusb will change after update (flashing).

For coding u don´t need to change VIN, just VO-code the LMA

Do you have some fault codes in LMA?

You didn´t answer to my questions. We don´t know is the car PRE-LCI or LCI.
If PRE-LCI then did you retrofit LCI Headlights?

But at the otherside you are telling Bi-Xenon with H7..that would be then a Pre-LCI headlight.

Let us know the fault codes you have?
What is show in cluster and in Idrive?

Provide us vin and tell us if is the car stock or something modified!?


I can also take a look via teamviewer...

[sfinks2]

Thank you all for so many answers so quickly

Details are:

VIN: WBANJ31040CP82110

FA: E61_#0909*NJ31%0354&ALAT$1CA$320$423$428$431$441$442$494$4A
L$502$508$522$524$534$540$548$587$5AC$610$644$698$6VA$7A4$80
1$818$851$863$879-B110

Retrofited with CIC navigation system (Professional), so manufacturing date was changed to 0909 - what else I do not know as It was done as a service.
Some chip-tuning to DDE was also done but I think it has nothing to do with lights
No other retrofits were done, especially I did not change any lamps.

I have used NCS, winkfp, ISTA (D and P) already, so I know more less how they work, but I do it with exteeme care (lots of reading before I do anything). 
ISTA-P I'm a bit affraid of as I use USB cable (no ICOM) and home-made power supply (server power supply 12V 170A modified to some 14V) but even in Expert Mode ISTA-P requires to program several other modules not just LMA only (keeps to put them back on the list).

Fault codes - I just looked to information on iDrive now (lack of time, will follow up on this if You need info). After NCS coding with empty MAN there was absolutely no light at the rear of the car except registration plate lighting and turning lights were blinking vey fast.

Last evening I spent in my car juggling with LMA coding, specially oprions relating to "toggle sense resistor". Currently the crucial settins are:

PIN_CONFIGURATION_33 - value 2 (is it OK??)
SENSEWID_PIN_04_33 - activ
SENSEWID_PIN_25_33 - activ
SENSEWID_PIN_24_39 - activ
SENSEWID_PIN_40_33 - activ
SENSEWID_PIN_61_33 - activ
SENSEWID_PIN_62_33 - activ
SENSEWID_PIN_63_33 - nicht activ
SENSEWID_PIN_10_33 - activ
SENSEWID_PIN_42 - nicht activ
SENSEWID_PIN_22_68 - activ
SENSEWID_PIN_11_33  -nicht activ
SENSEWID_PIN_05_33 - activ
SENSEWID_PIN_30 - nicht activ
SENSEWID_PIN_64_33 - active

Result:
* turning lights work - OK
* inner tailgate lights - OK
* outer tailgate lights - MISSING, but no error displayed on IDrive
* Brake lights - MISSING with error on IDrive

So, looks like juggling with sence resistor settings do work and I am half way there and kind of half-proud of myself .
If someone can advise me what settings to change to get outer tailgate lights and brake lights back to normal It will be very much appreciated.

I also (secod priority) wanted to code:

1. high beams to be xenon and H7 together


FL_AUS_BEI_BIX_IN_S_FLC - nicht active (was like that already)
PWM_ANST_FL_BIXENON - value 3 changed to value 4

2. blinking ("flash-to-pass") with h7 only and NOT with xenon (want to save my xenon life):

BI_XENON_BEI_LH - activ changet to nicht active


None of the two above options did not work.
Perhaps You have some idea how to make it working?

Thanks for your help so far and hope to hear from you soon.