NCSExpert Code Mods
Hi Blood it is amazing
just did it on mine - only differences is I have LMA 1 and the sentence: "B 00340500,0010,95,71,00,83,0A,00,51,00,14,53,01,15, 59,04,00,00" was slightly different, just changed the value of 95 to 97 and it is working perfectly.
Did you compare the FSW files after coding?
The only differences I can see is than the:
BLINKIMPULS_WARNBLK wert_01
disappeared from the new FSW trace file.
In this case just maybe delete this from the FSW and code it as usually do the job?
This may do the job for the rain sensor sensitivity as well on the Idrive menu?
Even maybe welcome lights for LMA1 owners?
Definitely looks like you opened a "PANDORA BOX" for all of us E60/61 owners.

just did it on mine - only differences is I have LMA 1 and the sentence: "B 00340500,0010,95,71,00,83,0A,00,51,00,14,53,01,15, 59,04,00,00" was slightly different, just changed the value of 95 to 97 and it is working perfectly.
Did you compare the FSW files after coding?
The only differences I can see is than the:
BLINKIMPULS_WARNBLK wert_01
disappeared from the new FSW trace file.
In this case just maybe delete this from the FSW and code it as usually do the job?
This may do the job for the rain sensor sensitivity as well on the Idrive menu?
Even maybe welcome lights for LMA1 owners?
Definitely looks like you opened a "PANDORA BOX" for all of us E60/61 owners.

re: welcome lights on a LM1, It would be interesting to compare the trace file of a LM2 and LM1 to see if coding other options is possible, but I get the impression there will be a different number of values available between the two, hope Im wrong, but it will need a comparison of the two and knowing what value determines the welcome light (Easy enough to find I guess if you do a before and after comparison on a car with welcome lights..hint hint
Contributors
Joined: Mar 2009
Posts: 2,553
Likes: 0
From: Essex, UK.
My Ride: 2006 530 d M-sport e60
Hi Blood it is amazing
just did it on mine - only differences is I have LMA 1 and the sentence: "B 00340500,0010,95,71,00,83,0A,00,51,00,14,53,01,15, 59,04,00,00" was slightly different, just changed the value of 95 to 97 and it is working perfectly.
Did you compare the FSW files after coding?
The only differences I can see is than the:
BLINKIMPULS_WARNBLK wert_01
disappeared from the new FSW trace file.
In this case just maybe delete this from the FSW and code it as usually do the job?
This may do the job for the rain sensor sensitivity as well on the Idrive menu?
Even maybe welcome lights for LMA1 owners?
Definitely looks like you opened a "PANDORA BOX" for all of us E60/61 owners.

just did it on mine - only differences is I have LMA 1 and the sentence: "B 00340500,0010,95,71,00,83,0A,00,51,00,14,53,01,15, 59,04,00,00" was slightly different, just changed the value of 95 to 97 and it is working perfectly.
Did you compare the FSW files after coding?
The only differences I can see is than the:
BLINKIMPULS_WARNBLK wert_01
disappeared from the new FSW trace file.
In this case just maybe delete this from the FSW and code it as usually do the job?
This may do the job for the rain sensor sensitivity as well on the Idrive menu?
Even maybe welcome lights for LMA1 owners?
Definitely looks like you opened a "PANDORA BOX" for all of us E60/61 owners.

I need to say a huge thanks to Revtor over at bimmerforums, with out him de-coding the LMA2 nettodata i would never have sussed this out.
Members
Joined: May 2010
Posts: 213
Likes: 0
From: London
My Ride: M3 ZCP EX:2005 BMW 535D Sport, Estate, Steptronic, Carbon Black, Black Dakota leather, Head up Display, Profi Satnav, Bluetooth - only MULF module, Bi-xenon adaptive headlights, Sportseats, Cruise control, Active steeringMods: 19
Model Year: 2011
You can not add functions that dont exist in the modules programming, Thats the correct behaviour madein, the tracefile can not show the new paremeter.
I need to say a huge thanks to Revtor over at bimmerforums, with out him de-coding the LMA2 nettodata i would never have sussed this out.
I need to say a huge thanks to Revtor over at bimmerforums, with out him de-coding the LMA2 nettodata i would never have sussed this out.
I know, I know, but still don't give up.....,
I remember you said once the double hazards are not possible also.....
I'm just wondering, if deleting the "BLINKIMPULS_WARNBLK wert_01" will do the same job, I may try this during the weekend....
Hi Blood it is amazing
just did it on mine - only differences is I have LMA 1 and the sentence: "B 00340500,0010,95,71,00,83,0A,00,51,00,14,53,01,15, 59,04,00,00" was slightly different, just changed the value of 95 to 97 and it is working perfectly.
Did you compare the FSW files after coding?
The only differences I can see is than the:
BLINKIMPULS_WARNBLK wert_01
disappeared from the new FSW trace file.
In this case just maybe delete this from the FSW and code it as usually do the job?
This may do the job for the rain sensor sensitivity as well on the Idrive menu?
Even maybe welcome lights for LMA1 owners?
Definitely looks like you opened a "PANDORA BOX" for all of us E60/61 owners.

just did it on mine - only differences is I have LMA 1 and the sentence: "B 00340500,0010,95,71,00,83,0A,00,51,00,14,53,01,15, 59,04,00,00" was slightly different, just changed the value of 95 to 97 and it is working perfectly.
Did you compare the FSW files after coding?
The only differences I can see is than the:
BLINKIMPULS_WARNBLK wert_01
disappeared from the new FSW trace file.
In this case just maybe delete this from the FSW and code it as usually do the job?
This may do the job for the rain sensor sensitivity as well on the Idrive menu?
Even maybe welcome lights for LMA1 owners?
Definitely looks like you opened a "PANDORA BOX" for all of us E60/61 owners.

Will have to see when I have time to figure out the other two hex codes. (didn't someone wrote up a converter somewhere?) The blinking rate, I am certain, is not the same as the E9x's. Their blink rate is a bit more "elegant" to me.
Regardless, this is a great step forward!
Here's my quick vid:
http://www.youtube.com/watch?v=7gLmpSdvViA
I will take another one when it gets darker, should be easier to see.
Contributors
Joined: Mar 2009
Posts: 2,553
Likes: 0
From: Essex, UK.
My Ride: 2006 530 d M-sport e60
Mine too was different, but I just changed to 97 as well and it works.
Will have to see when I have time to figure out the other two hex codes. (didn't someone wrote up a converter somewhere?) The blinking rate, I am certain, is not the same as the E9x's. Their blink rate is a bit more "elegant" to me.
Regardless, this is a great step forward!
Here's my quick vid:
http://www.youtube.com/watch?v=7gLmpSdvViA
I will take another one when it gets darker, should be easier to see.
Will have to see when I have time to figure out the other two hex codes. (didn't someone wrote up a converter somewhere?) The blinking rate, I am certain, is not the same as the E9x's. Their blink rate is a bit more "elegant" to me.
Regardless, this is a great step forward!
Here's my quick vid:
http://www.youtube.com/watch?v=7gLmpSdvViA
I will take another one when it gets darker, should be easier to see.
Members
Joined: May 2010
Posts: 213
Likes: 0
From: London
My Ride: M3 ZCP EX:2005 BMW 535D Sport, Estate, Steptronic, Carbon Black, Black Dakota leather, Head up Display, Profi Satnav, Bluetooth - only MULF module, Bi-xenon adaptive headlights, Sportseats, Cruise control, Active steeringMods: 19
Model Year: 2011
Is than nettodat different than fsw? It may have more options, but any changes in nettodat we should be able to see in fsw?
Contributors
Joined: Mar 2009
Posts: 2,553
Likes: 0
From: Essex, UK.
My Ride: 2006 530 d M-sport e60
The nettodat is the module functions in hexi-decimel data, by changing the nettodat your changing the module coding data at the programming level. The FSW file can not show non-standard coding values.
Senior Members
Joined: Jan 2007
Posts: 1,747
Likes: 2
From: DRACULA CASTLE in ROMANIA :D
My Ride: 530i N52
Model Year: 2006
Engine: n52


