All BMWs Coding lighting

I coded some features today.

After coding, I noticed that when I switch off the car, the headlights switch off straightaway, instead of staying in for 40 seconds per the pathway lighting setting.

Has anyone else experienced this?

Also I coded the FLA_Aktiv feature to be on (M5 doesn't have this option) and this is also not working even though I changed the setting to automatisch. I don't know if these 2 things are related. The only other lighting mod I did was switching off side markers.

Originally Posted by Stealth.Pilot

I coded some features today.

After coding, I noticed that when I switch off the car, the headlights switch off straightaway, instead of staying in for 40 seconds per the pathway lighting setting.

Has anyone else experienced this?

Also I coded the FLA_Aktiv feature to be on (M5 doesn't have this option) and this is also not working even though I changed the setting to automatisch. I don't know if these 2 things are related. The only other lighting mod I did was switching off side markers.

What is the Pathway Lighting set for under the iDrive Lighting Options?

For AHB, BMW changed the behavior of FLA_AUTO_AKTIV from "aktiv" to "automatik", and now apparently the Lights need to be cycled before AHB works. You should read this thread if you haven't already:

http://www.bimmerfest.com/forums/sho...d.php?t=644297

wdimagineer retrofitted the stalk in his M5, which if I understood him correctly he still needs to cycle the lights for AHB to work, but it is easier from the stalk.

Originally Posted by shawnsheridan

What is the Pathway Lighting set for under the iDrive Lighting Options?

For AHB, BMW changed the behavior of FLA_AUTO_AKTIV from "aktiv" to "automatik", and now apparently the Lights need to be cycled before AHB works. You should read this thread if you haven't already:

http://www.bimmerfest.com/forums/sho...d.php?t=644297

wdimagineer retrofitted the stalk in his M5, which if I understood him correctly he still needs to cycle the lights for AHB to work, but it is easier from the stalk.

I have pathway lighting set to 40 seconds.

Originally Posted by Stealth.Pilot

I have pathway lighting set to 40 seconds.

Strange. I don't know of any other instance where this has happened.

Right Click in your FRM ECU (the ECU itself; not the underlying CAFD, and select CODE) to reset to your Footwell module, and see if it returns to normal.

Originally Posted by shawnsheridan

Strange. I don't know of any other instance where this has happened.

Right Click in your FRM ECU (the ECU itself; not the underlying CAFD, and select CODE) to reset to your Footwell module, and see if it returns to normal.

I am wondering if I am using the right coding data.

I installed the 48.1 data you linked me yesterday. Then when connecting to the car, I selected F10. Is there a different selection for the M5?

Also it doesn't have HU-CIC it has HU-something beginning with L. It did strike me as odd that the files are different.

Originally Posted by Stealth.Pilot

I am wondering if I am using the right coding data.

I installed the 48.1 data you linked me yesterday. Then when connecting to the car, I selected F10. Is there a different selection for the M5?

Also it doesn't have HU-CIC it has HU-something beginning with L. It did strike me as odd that the files are different.

You have the right coding files. 48.1 is universally good, and F10 is the correct target for your new M5. Your HU_CIC is HU_NBT because you have the new iDrive system in your MY 2013. You also will not find a CMB_MEDIA or CMB_ECALL module, as your Combox functions are built into in the Head Unit, and not a standalone module.

Originally Posted by shawnsheridan

You have the right coding files. 48.1 is universally good, and F10 is the correct target for your new M5. Your HU_CIC is HU_NBT because you have the new iDrive system in your MY 2013. You also will not find a CMB_MEDIA or CMB_ECALL module, as your Combox functions are built into in the Head Unit, and not a standalone module.

Another issue I ran into was that I could not find ASP_Beiklappen_Bei_Komfortschleissen in the CAS file. Without changing this to aktiv I could not activate comfort access door mirrors.

Originally Posted by Stealth.Pilot

Another issue I ran into was that I could not find ASP_Beiklappen_Bei_Komfortschleissen in the CAS file. Without changing this to aktiv I could not activate comfort access door mirrors.

What is the name of your CAS CAFD file?

Originally Posted by shawnsheridan

What is the name of your CAS CAFD file?

I'll get back to you in 2 days. Just have a short trip to SAN.

Originally Posted by Stealth.Pilot

Another issue I ran into was that I could not find ASP_Beiklappen_Bei_Komfortschleissen in the CAS file. Without changing this to aktiv I could not activate comfort access door mirrors.

This should be in the FRM module.

Originally Posted by TRIPLE_O

This should be in the FRM module.

Good catch. I missed that.

Originally Posted by Stealth.Pilot

I have pathway lighting set to 40 seconds.

Stealth:

Make sure your light switch is set on automatic.