I coded mine with e-sys - not sure if the process is the same on Bimmercode. On Esys, you needed to add codes to the vehicle order VO, then it would add the options in to each module automatically when you recoded them.
These are the (rough) steps for the esys coding:
Click ‘read ECU’ and select an F56 model from the drop down (not one that has direct in the title). Follow these instructions
How to VO Coding?
How to VO Coding? 1. What I need? I have e-sys 3.22.5 (payed version) & 49.0 can make change vo with esys? 2. If VO coded... Can revert to Original VO? Thanks...
www.bimmerfest.com
https://www.bimmerfest.com/forums/attachment.php?attachmentid=327696&d=1338725691
You need to remove the code for your existing wheel from the SALAPA elements. Full list of options below:
Full Option Code List for VO Coding (SALAPA Elements)
Hi, After retrofitting NBT to my F30, I struggled to find what option codes i needed to add/remove to successfully VO code HU_NBT. The list is extensive ('S' prefix isn't displayed on your SALAPA list. Neither are the suffixes- just middle 3 digits): Full BMW VO FA List: S000A Dummy-SALAPA...
www.bimmerfest.com
My new wheel was S249f (you only use the 249 in the SALAPA list). You then calculate the FP from the VO window, save it and return, load the new VO in the ecu editor, calculate again and then code to the modules. This part was heart in mouth time as the radio head unit will tell you you need to take it to Mini for an update, but once it finishes flashing the modules it’s fine. I forget which modules you need to code to, but it was certainly ABS, BKombi and possibly one or two others, though you could theoretically recode all modules if you wanted to. Then I restarted the car and everything worked as it should.
Below is the list of 'elements' in my VO. So the new wheel element was '249' and the cruise control element was '544'. Having both of these present meant the car coded the correct options when I recoded the module.