BMW G05 coding list
The changes G05 X5 owners (and G06 X6 and G07 X7 owners: they share most modules) code most, which module each one is in, and what to check before you code.
Before you start
- Your software level decides what is possible. The same change can sit in a different setting, or be gone, after a BMW software update (I-step). Read your car's I-step first: Expert Mode > VCM > Integration I-Steps.
- Newer cars may need BMW-signed coding. Some modules on cars built from about 2021 use secure coding (NCD 2.0) and refuse coding that E-Sys signs itself. See NCD 2.0 and secure coding.
- Back up first. Make a full backup of the car before the first change, and keep the battery on a charger while you code.
- Module names vary. The table shows the module most G05s use; a car with other equipment or a later facelift (LCI) can have it elsewhere.
Popular G05 codings
| Change | Module (usual) | Notes |
|---|---|---|
| Digital speed in the instrument cluster | DKOMBI4 | Shows your speed as a number. |
| Start-stop remembers your last choice | DME, BDC_BODY3 | |
| Fold mirrors when locking | BDC_BODY3 | Also: unfold when unlocking. |
| Open and close windows and sunroof with the key | BDC_BODY3 | Hold the key button. |
| Comfort turn signal: 3 or 5 flashes | BDC_BODY3 | |
| Mirror tilts down in reverse | BDC_BODY3 | Needs memory mirrors. |
| Welcome and coming-home lights | BDC_BODY3 | |
| Ambient light colours and brightness | BDC_BODY3 | Needs ambient lighting. |
| Lock and unlock beep | BDC_BODY3 | |
| Sport displays and G-meter in iDrive | HU_MGU or HU_NBT_EVO | |
| Legal disclaimer off at start | HU_MGU or HU_NBT_EVO | |
| Tyre temperatures shown with the tyre pressures | HU_MGU or HU_NBT_EVO | Needs tyre pressure sensors with temperature. |
| Video while driving | HU_MGU or HU_NBT_EVO | For passengers only: the driver must not watch. Illegal in many countries while driving. |
| Seatbelt chime off | ACSM_5 | A safety warning: a shorter chime is the safer choice. |
| Automatic lane change, speed limit assist | SAS3, HU_MGU | Needs the matching driving assistant hardware (option codes in the vehicle order). |
| xDrive status screen in iDrive | HU_MGU or HU_NBT_EVO |
How to code these with E-Sys
- Connect, then in Expert Mode > Coding: Read the vehicle order, Activate FA, and Read SVT.
- Select the module's CAFD and press Read Coding Data.
- Open the CAFD, right-click the .ncd file under it and choose Edit FDL.
- Find the setting, change its value and save. Then select the CAFD and press Code.
In plain E-Sys many G05 settings show only as dots or German short names. E-Sys MAX shows every setting in English, and its What can I code? list shows the ready-made changes that fit your car's modules, applied with one click in the FDL-Editor. More in FDL coding and setting names by model.
Questions
Does this list work for the G06 X6, G07 X7 and F95 X5 M?
Mostly yes: they share the same modules. M models have extra M settings, and the head unit can differ by market and build date.
Will a BMW update undo my coding?
It can. A dealer visit or an over-the-air update can write the vehicle order and code the car again. Keep your coding history so you can put your changes back.
Can coding damage the car?
Coding changes settings, not software, and a module can be coded back. Back up first, keep a charger connected, and change one module at a time.
Every G05 setting in English
Connect, open a module, and E-Sys MAX lists the changes that fit your car. Free for 3 days.