Coding F80: What worked and what didn't for me

[chetrickerman]

Originally Posted by Almaretto

It should, but I am still confused as to what you hope to accomplish. If you do not want to use windshield wipers, then do not toggle them on. Comparatively, headlamp washers are often disabled through coding to avoid need to frequently refill solution.

I'm removing it for weight purposes

[tom @ eas]

Originally Posted by chetrickerman

Does anyone have any info on coding to remove the windshield washer?

Past models was simply bridging the leads on the level sensor. Can't believe it would change in later years since it's a simple sensor.

[chetrickerman]

Originally Posted by tom @ eas

Past models was simply bridging the leads on the level sensor. Can't believe it would change in later years since it's a simple sensor.

I will try that out, thank you.

[taint]

Just bought a 2018 F80 and I am in TX right now, but my coding computer is in CO. Not a huge deal since I am a sucker and bought the BimmerCode App and WiFi ODB adapter. Side note, BimmerCode app has come a long way and actually is becoming useful, but mostly I use the app and WiFi adapter to do quick changes on my wife's car as well as help people out in a pinch. I knew that I wouldn't be able to VO code anything, but was willing to wait until I got back to CO. Tried to code some stuff I knew wouldn't work (turn signals in HUD, HBA default on, etc.) and did a lot of the other stuff that drives me crazy and I couldn't wait till CO (unlock at engine off, MMI off with door open, etc.). Back on topic, drove the car for the first time at night today. Turned on the HBA and didn't expect anything to happen. Getting on the highway only my right high beam came on and it was away from the car in front. It happened a few other times on the drive. Did BMW change and is anti dazzle now not decoded in 2018s with LEDs and KAFAS? I won't be able to pull the VO until I get to my computer, but wanted to see if anyone else has similar experiences.

[Almaretto]

Originally Posted by taint

Just bought a 2018 F80 and I am in TX right now, but my coding computer is in CO. Not a huge deal since I am a sucker and bought the BimmerCode App and WiFi ODB adapter. Side note, BimmerCode app has come a long way and actually is becoming useful, but mostly I use the app and WiFi adapter to do quick changes on my wife's car as well as help people out in a pinch. I knew that I wouldn't be able to VO code anything, but was willing to wait until I got back to CO. Tried to code some stuff I knew wouldn't work (turn signals in HUD, HBA default on, etc.) and did a lot of the other stuff that drives me crazy and I couldn't wait till CO (unlock at engine off, MMI off with door open, etc.). Back on topic, drove the car for the first time at night today. Turned on the HBA and didn't expect anything to happen. Getting on the highway only my right high beam came on and it was away from the car in front. It happened a few other times on the drive. Did BMW change and is anti dazzle now not decoded in 2018s with LEDs and KAFAS? I won't be able to pull the VO until I get to my computer, but wanted to see if anyone else has similar experiences.

Still decoded.

[taint]

Originally Posted by Almaretto

Still decoded.

Maybe some type of anti dazzle "lite" for the US? Wondering if that will change how I normally code the full functioning LEDs. The tree is much different in the 2018s with ID6 so I am having to do a lot of relearning.

[Almaretto]

Originally Posted by taint

Maybe some type of anti dazzle "lite" for the US? Wondering if that will change how I normally code the full functioning LEDs. The tree is much different in the 2018s with ID6 so I am having to do a lot of relearning.

Only difference is FLE vs LHM/TMS with 2017.

You may have accidentally enabled KAFAS function when coding with app. I would disable until you can properly VO fem and FDL code FLE.

[taint]

Originally Posted by Almaretto

Only difference is FLE vs LHM/TMS with 2017.

You may have accidentally enabled KAFAS function when coding with app. I would disable until you can properly VO fem and FDL code FLE.

I was starting to think the same. I'll fix in the morning. Thanks as always!!

[Almaretto]

Originally Posted by taint

I was starting to think the same. I'll fix in the morning. Thanks as always!!

[toni8284]

for the 2018 F80, the iDrive is touch screen. But it cant use touch screen to input address when driving, what's the code for that?

I believe it works when I was doing ED.

[Almaretto]

Originally Posted by toni8284

for the 2018 F80, the iDrive is touch screen. But it cant use touch screen to input address when driving, what's the code for that?

I believe it works when I was doing ED.

Search for touch speedlock. Why not use idrive control to type?

[Who's on first]

Originally Posted by Almaretto

Search for touch speedlock. Why not use idrive control to type?

PM'd

[Almaretto]

Originally Posted by Who's on first

PM'd

Responded.

[Who's on first]

Anyone been able to find these options for the F8x's?

Damn sweet in the X5.

Here is how I did it with one example changing the solid color orange to green (gruen).

BDC_Body -> CAFD_.... -> 3070 LciMaster, A5 -> Function -> GROUP_0_FARBE_ENSEMBLE_1 -> weiss (was orange) -> AMBIENTE_FARBE_ENSEMBLE_1_LAYER_1 -> gruen (was orange) -> AMBIENTE_FARBE_ENSEMBLE_1_LAYER_2 -> gruen (was orange)

This really all you need to do. There are several LAYERS, if you open up the folder "Ausgelesen" you will find the color matching to your current setup (idrive screen -> settings -> lighting ...).

The section _GROUP_ separates the color schemes.
GROUP_#_FARBE_ENSEMBLE_# is the "dome" sector where you only have 2 color options; orange and white (weiss).
AMBIENTE_FARBE_ENSEMBLE_#_LAYER_# is the "dashboard" color and below.

There are 8 LAYERS but not all of them are active (inakitv), I tried selecting them but could not notice any changes, just FYI.

Colors available:

Dome or _GROUP_ (Top Ceiling) White (weiss) or orange.
Rest of the _LAYER'S : Green (gruen), Pink, Purple (lila), violett, ivory_dynamic_blue (elfenbein_dynamisches_blau or eff_dyn_blau), light/bright blue (hellblau), yellow (gelb), ice blue (eisblau), turquoise (tuerkis) light/bright green (hellgruen), orange, light/bright red (hellrot) and white (weiss).

[Almaretto]

Originally Posted by Who's on first

Anyone been able to find these options for the F8x's?

You can do on an I012 and G030, but not F8x's.

[Who's on first]

Originally Posted by Almaretto

You can do on an I012 and G030, but not F8x's.

Sons of bitches.

[f80er]

Cheat codes seem to break some modules, like FEM. I guess if there are too many selected it will just error out under the code window and not display any of them. Is there a limit to the display?

[tom @ eas]

Originally Posted by f80er

Cheat codes seem to break some modules, like FEM. I guess if there are too many selected it will just error out under the code window and not display any of them. Is there a limit to the display?

Group numbers for specific features can change based on I-step version.

[f80er]

Originally Posted by tom @ eas

Group numbers for specific features can change based on I-step version.

Say what? Is there a way to limit the cheat codes to only show the compatible ones with my version of istep? From launcher pro the only option I have is to include specific users cheat codes or not.

[Almaretto]

Originally Posted by f80er

Cheat codes seem to break some modules, like FEM. I guess if there are too many selected it will just error out under the code window and not display any of them. Is there a limit to the display?

I only load a few authors and have no trouble. Pro Launcher expanded number allowed.

[f80er]

Like who? I did you and alphaboud (sp?) and packetpilot but dont recognize the rest.

[Almaretto]

Originally Posted by f80er

Like who? I did you and alphaboud (sp?) and packetpilot but dont recognize the rest.

I would do ruben_17non for F3x/F8x. You can open xml files in browser or Notepad++ to check out descriptions for potential others.