Available Tables/Maps for Tuning
Let us analyze MG Flasher’s v7.3 map pack and dive deeper into the available tables and codewords. You can acquire map packs as A2Ls or XDFs from our GitHub Repo, as described here: Custom Tuners - Map Pack Guide for Custom Code.
When we focus on just the Flex Fuel related maps from Custom Code, we see many categories appear:
Custom Code v7.3 Map Pack
Basic Settings:
Codewords
Here are some codewords that are common for all map slots:
Description | Name |
---|---|
Set 1 (true) to use each Flex Fuel map slot and 0 (false) to use only Slot 0 | CW_UseMultipleFlexFuelSlots___MGF_CC |
Set 1 (true) to use Pump Fuel map slots for lower bounds when Blend Factor is greater than 100% and 0 (false) to use Flex Fuel #1 map slots | CW_UsePumpFuelMapWhenBlendFactorIsGreaterThan1___MGF_CC |
Set 1 (true) to enable function and 0 (false) to disable function | CW_FlexFuel___MGF_CC |
Set 1 (true) to enable function and 0 (false) to disable function | CW_FlexFuelBlending___MGF_CC |
Set 1 (true) if flex fuel sensor is installed on PT-CAN2 and 0 (false) if not installed | CW_SensorEthanol___MGF_CC |
Slot 0
Slot 0 can be used for all slots when CW_UseMultipleFlexFuelSlots___MGF_CC is disabled. Within each slot folder, we have 5 sub folders to further organize the maps, Blenders, Codewords (per slot), FF1, FF2, Sensorless Values. Map organization is shown below and describe in the Seven Tuning Categories sub section (below).
Slot 1-4
Map layout is the same as slot 0, but only used when CW_UseMultipleFlexFuelSlots___MGF_CC is enabled.
Seven Tuning Categories
Tables are grouped together into Seven tuning categories:
Boost
Maximum target boost pressure due to boost pressure sensor diagnosis (BMWtchsp_p_ReqMax_C)
Fuel Correction
Kennfeld Beginnwinkel ES1 Warm (KF_PHA_H_B1_W)
KF_PHA_H_E1
Map pre-control correction bank 1 (KF_FRKKORRF_1)
Fuel Targets
Base lambda in the homogeneous bank 1 (KF_LABAS_1)
Ignition
Basic firing angle path 1 (KF_ZW_PF1)
Basic firing angle path 2 (KF_ZW_PF2)
Basic ignition angle overflush path 1 (KF_ZW_UESP_PF1)
Basic ignition angle over-scavenging path 2 (KF_ZW_UESP_PF2)
Basic ignition angle path 1 safe (KF_ZW_S_PF1)
Basic ignition angle path 2 safe (KF_ZW_S_PF2)
Map for ignition angle vanos in stop F_basis=1 path 1 (KF_ZW_VP_PF1)
Map for ignition angle vanos in stop F_basis=1 path 2 (KF_ZW_VP_PF2)
Knock
Knock detection factor map cylinder counter 0 (IKCtl_FacKnockDetThd0_GM)
Knock detection factor map cylinder counter 1 (IKCtl_FacKnockDetThd1_GM)
Knock detection factor map cylinder counter 2 (IKCtl_FacKnockDetThd2_GM)
Knock detection factor map cylinder counter 3 (IKCtl_FacKnockDetThd3_GM)
Knock detection factor map cylinder counter 4 (IKCtl_FacKnockDetThd4_GM)
Knock detection factor map cylinder counter 5 (IKCtl_FacKnockDetThd5_GM)
Load Control
Characteristic maximum permissible filling over speed (KL_RF_MAX)
Characteristic of the maximum permissible filling over the speed when flushing (KL_RF_MAX_UESP)
Wastegate Control
Correction of pressure difference f. P-part of the performance-based boost pressure controller (X-Axis does not switch, BMWtchctr_p_DifCrtnPp_M)
Wastegate Position - for pilot control (BMWtchctr_pct_WgBasc_M)
D part of the performance-based boost pressure controller (X-Axis and Y-Axis do not switch, BMWtchctr_pwr_Dp_M)
Compressor map with required compressor / turbine performance (X-Axis does not switch, BMWtchctr_pwr_Pctl_M)
Blenders
Each of the 7 tuning categories gets their own blending factor maps, for each map slot. Details on these maps are described here: Understanding Map Blending: How Flex Fuel Maps Work.
Map name examples: FlexFuelBlendFactor___FuelCorrection_Slot_0___MGF_CC, FlexFuelBlendFactor___FuelTargets_Slot_1___MGF_CC, FlexFuelBlendFactor___FuelTargets_Slot_2___MGF_CC, etc.
Codewords (per slot)
Each slot can have flex fuel blending enabled individually using codewords like CW_FlexFuelBlending_Slot0___MGF_CC.
FF1 and FF2
These two folders contain the same layout of 7 tuning category maps, but with their own respective slot and fuel type.
Flex Fuel 2 (FF2) maps require valid calibration data, even if you do not use it, regardless if you keep blending factors at 100% or lower. This can be easily avoided by generating a stock map binary files from the app with Custom Code v7.3.
Related content
MG Flasher @ 2025