Hey there guys,

I've recently gotten my USB-OBD Cable and the software along with it (NCS,inpa, etc) I have been reading through this whole forum many many times, as well as bmwcoders, and many people state that within NCS expert and in the LMA module, you are able to control the resistance/brightness of the Angel eyes by changing (PWM_AN_SL_V_AL_1_34 to wert_01) Now a little bit about my car:
I have a 2005 E60 525i. Prod date: 10/04, which apparently has had some dealer update because i was able to code Mp3 > Aktiv and Mp3-CDC > aktiv. I havent checked what Light Module i have, but i am certain it is LM1 even though i was able to disable my Daytime Running Lights, I have no idea how that worked if i have an LM1 Module. Anyways, i am trying to adjust the brightness for the AE, and in the LMA trace file, i do not have any lines along of what it states for me to change (PWM_AN_SL_V_AL_1_34). But i do have this option right after i select the chassis (e60) and hit the back button where it reads the whole car ecu and saves it into a FSW_PSW.TRC. In there there are PWM_AN_SL_V_AL_1_34 values that i CAN change as well as some others ones that i could not find before. Can anyone tell me how and or where else i would be able to find this code? (in which Module to look). My car does not have navi, just a mask unit( i have the MASK module). I also do not have a CAPPL in there and i wanted to enable the seat heater slider, and seat heater comes up in Idrive as well as Welcome lights in menu. I cannot find those options in the LMA trace but they ARE PRESENT in the original whole .trc file. Am i able to code the WHOLE car with that one .trc file instead of doing each module on its own? If so, how would i be able to do it because it gives me some kind of error after i select the basic functions in NCS.

I have included the whole car trace file with all modules, and the separate LMA module after selecting CAS.

Sorry for the wall of text, but if anyone is inclined and experienced with this matter, please offer some guidance.

Thank you alL!

 

You can disable/enable the DRL on LM1. If you have an 05 you have an LM1. But NCS will tell you when you read it. Or use INPA to read the UIF and you'll know.
As far I can see you just need to do more reading. You select E60 CAS and then go to the module and read it. It will dump into a trace file. Copy contents and put in the managment file (.man) and change what you need to and save it. Then upload it to the module.

You do not have a CAPPL because you do not have a CCC you have MASK.
CAPPL is for the CCC applications.
If you do not see options in a module's trace file then it is not part of that module it is stored somewhere else.
What I do is get the whole trace file and modify what I need and then you can upload it (MAN file) to the module that the info is a part of. OR you can upload the MAN file to each module if you're not sure what to do. It's not going to hurt.
Btw, i didn't look at your files I just looked at your post which makes the files illegitimate to me. There's no way you can ruin anything so don't worry. But to answer your last question .. no you cannot code the whole car at one time. you have to do each module on its own but you can use the one modified file. Each module will just take the lines of code that is relevant to it.

 

Thank you for the reply and insight.

I apologize for posting something like this when I should have researched more. I have basically exhausted all the possible (known and safe) coding options based on forum posts and feedback from people, as well as the e60 option spreadsheet.

Okay, so to get this straight. You are saying that once i load up the profile, F1>F3 and select CAS, then hit back and it will show all my modules as well as create a large .trc file of the car.

Now in that large .trc file, there are options that I cannot find in any of my other modules/trc files. If i change them, will it cause any harm?

Once i change my options in the large .TRC file, I can then change the extension to a .Man and go ahead and change ecu and code individual modules with that very same .MAN file and even change lines of code that i could not previously find before? It will not overwrite or add and or confuse any other modules with different lines of code?

Another question I had was, after looking at the e60 spreadsheet, it clearly says that "MY05" (my 2005 e60) I can code VA_SEATCLIMA_SHORTCUT and VA_SEATHEAT_SLIDER, and it is in the CAPPL module. I know that since I do not have CCC, but a MASK unit, i cannot access that module, and I do not see this option in my MASK one. I do however, see it in the whole car .trc file.

Another question to get off my chest, do you have any trusted tutorials/posts where I am able to find more coding options and or lists of option codes that I am able to add to my FA? (I recently added +NAUX and +KMP3 and both work marvelously.! I am trying to find any others that i might adapt to my vehicle.

I am sorry about making you read this large wall of text which is most likely nonsense for you, and appreciate any other input you may offer. Thank you soo much!

 

No you cannot cause harm with NCS. It's just to change options already on the car. However you would have to upload the .man file with the trace file contents to the specific ecu for that ecu to grab the changes. For instance if you change something for the IHKA and you only process the trace file in KOMBI it's not going to do anything for you.




You do not need to change the extension to a .man. Just open the man file and past in the trace file with changed options in it. obviously you would save the original trace file you have and store it away. If no option on it were saved then you could always default the car back to the vehicles' order options.
If you have lines of code that you couldn't find before you're not looking in the right modules.


You do not have a CCC so CAPPL isn't going to work. You may see it in the trace file but that doesn't matter because it's not on your car. For instance the LCI have other options that pre-LCI do not. Put it this way. In the trace file you're going to see many options that will be for upcoming models. Of course they probably require hardware changes and so forth....well not probably, they have. The E60 life cycle is done. So I guess that's that.


No i don't have any docs for that sorry. Large wall indeed. lol. not nonsense they're all good questions. good luck. Sorry I didn't see this earlier

 

Thanks for the good feedback!

 

Which parameter must i change in order to have inactive angel eyes with low beam on? BMW E60 LCI 2009 with xenon headlights.