Cheat Sheet for F10

Click Here for F10 Cheat Sheet
(Opens google spread sheet)


Thanks to DreamCar for all the work to put these docs together. I've been doing some coding of my 2013 F10 and have imported his PDF into this Google Spreadsheet and made some updates based on my experience.

I've marked items that I (1) confirmed are working on the 2013; (2) do not exist; (3) exist but aren't working for me (could be something I'm doing wrong). I also noted that the HU_CIC module shows up as HU_NBT on my car.

There's still some formatting cleanup that needs to be done on the description column.

If anyone wants to update this sheet, send me a PM with your google email and I'll open modify access to the doc.

Thanks to stephens lets try to keep this updated.

Stephens can you please provide mod access to Shawn and Jeg23 for this

Yes, I just need their gmail address to enable it in Google Docs. I got your PM and you should now have access.

Can I get this updated sheet for the F10?

Click in the link to view or make your own copy of the sheet. PM me with your gmail address if you want to modify the sheet.

Here is my gmail: drevork@gmail.com

I want to add the code for the HUD blinker to work for the 2013: KOMBI 3008 -HUD_PIA_BLINKER = activ, also note the option does not appear in Settings.

You're all set. Thanks for updating the sheet.

Thanks, sheet is updated.

Can I get this updated sheet for the F10?

Great Cheatsheet. Thank you very much! Used it for my first coding last night. I ran into one dead end; in rows 20 and 21 there is a reference in the "Description" column that reads "requires ASP_BEIKLAPPEN_BEI_KOMFORTSCHLIESSEN..." but there is no mention of which module, Section, and Function Value this setting can be found. If you have this missing information, would you please append it to your F10 Cheatsheet?
Thank you!

Originally Posted by MWPos

Great Cheatsheet. Thank you very much! Used it for my first coding last night. I ran into one dead end; in rows 20 and 21 there is a reference in the "Description" column that reads "requires ASP_BEIKLAPPEN_BEI_KOMFORTSCHLIESSEN..." but there is no mention of which module, Section, and Function Value this setting can be found. If you have this missing information, would you please append it to your F10 Cheatsheet?
Thank you!

It is in FRM.

ROW 30 ON THE spreadsheet - 3020

spadae2 and Shawnsheridan,

Thanks for the pointer, and thank you also for not punctuating your replies with ", you moron."

F10 sheet updated with Brake Force Display option. Fixed INBAND RINGING default, and option.

Updated again, some of the updates need the 2013 integration, well at least 48.x. Others did the hard part, just trying to help out. Added colored lines options in extended display, HUD entertain_list/phone_incoming-recent calls/voice, commands in HUD.

I think there are some mismatches in columns, specially columns J and K. The obvious example is row 30 which is the prerequisite for closing mirrors and windows from C.A and FOB, but column K is talking about interruptions from opening door for rolling windows.

Can you PM me your gmail login and I will give you access to the sheet so you can make any changes.

I did not update those outside columns. I noticed the were scrambled a litttle, but the codes are correct. I will take a look tonight and update what I can quickly.

Easy question: Do the X's in the car year columns (2011/12/13) for each coding row indicate the row's applicability to that year, or that the row has been validated in that year model? I'm supposed to help a 2013 535i owner do some coding tomorrow so I may be able to fill in a few X's if the "X"'s absence means that the item has not been validated.

Originally Posted by MWPos

Easy question: Do the X's in the car year columns (2011/12/13) for each coding row indicate the row's applicability to that year, or that the row has been validated in that year model? I'm supposed to help a 2013 535i owner do some coding tomorrow so I may be able to fill in a few X's if the "X"'s absence means that the item has not been validated.

Good question. I have used the X when I have confirmed that the value exists in my 2013 model year. Not necessarily that it works as it has in years past. This sheet pre-dates my participation on this forum so others may have a different take on how they've used it.

Originally Posted by gstephens

Good question. I have used the X when I have confirmed that the value exists in my 2013 model year. Not necessarily that it works as it has in years past. This sheet pre-dates my participation on this forum so others may have a different take on how they've used it.

Originally Posted by MWPos

Easy question: Do the X's in the car year columns (2011/12/13) for each coding row indicate the row's applicability to that year, or that the row has been validated in that year model? I'm supposed to help a 2013 535i owner do some coding tomorrow so I may be able to fill in a few X's if the "X"'s absence means that the item has not been validated.

I do not maintain the online Cheat Sheet; however, I authored the original, .PDF versions 1, 2, 3, and version 4 which is pending release.

My intent with the Year Column and "X" was to identify which FDL Codes were confirmed to work on each production model year; however, it proved to be a futile effort as each Model Year, BMW has 3 distinct sub periods of production where changes can occur, as well as there are too many other variables in each cars configuration, as well as differences with ISTA/P versions, all of which combined makes it far too difficult to track which codes work on which model year and production period, and with which options.

In the pending version 4, I have already removed the model year information, and if I know an FDL Code has some sort of requirement, be it date or option code or dependent upon other FDL Codes, I simply make note of this in the Description field.

Thank you Shawn.

Yes thanks. When you start coding the car you will notice the changes and where to find them for each car that you code.
ER


Sent from BimmerApp mobile app

Great cheat sheet! Can you give mnslinky@gmail.com access, please? I have a friend (who's a Germany native) coming over in the next couple weeks to help me decipher other modules/variables. I'd like the ability to update the sheet and, perhaps, make it easier to read.

Was this ever updated?


Sent from BimmerApp mobile app