When you import a US-spec BMW to Europe, the software differences go far beyond a simple language setting. Out of the factory, US vehicles carry unique type keys, region-locked infotainment parameters, side-marker logic, and combined brake/turn-signal wiring.

However, attempting to copy-paste coding values from a random online manual is a recipe for broken features or fault codes. Why?

1. Control Unit Architecture Varies: Older F-models rely on the Footwell Module (FRM). Newer chassis use Front Electronic Modules (FEM_BODY) paired with Rear Electronic Modules (REM), while late-model F-series use Body Domain Controllers (BDC).
2. Hardware Differences: US taillights often ship with red lenses where brake and turn signals share physical LEDs. EU regulations mandate amber turn signals that operate completely independently from the brake lamps.
3. Firmware / CAFD Differences: The same parameter name in an early NBT head unit might be renamed or shifted to another sub-folder in an NBT EVO or iDrive 6/7 unit.

Golden Rule: Always inspect the actual hardware, pin assignments, and installed ECU tree before writing a single line of code.

2. Pre-Coding Safety Checklist & Required Tools

Before touching the vehicle order, set up a stable workspace. Software coding drops the battery voltage quickly, and an ECU voltage brownout mid-flash can brick a module.

Core Requirements:

• Interface: ENET Cable (Ethernet to OBD2) or BMW ICOM interface.
• Software: E-Sys (with launcher/pro-token) and up-to-date PSdZData (Full or Lite depending on whether you are flashing or just coding).
• Diagnostic & Verification: ISTA+ (for reading/clearing fault codes post-coding).
• Power Supply: High-quality regulated battery charger/power supply (holding a steady 13.5V – 14.0V). Do not use a trickle charger.

Mandatory Checklist:

• [] Read and save the original Vehicle Order (FA.xml). Store it in multiple backup folders!
• [] Save the current vehicle state (SVT_actual.xml).
• [] Export a complete backup of all CAFD files (FDL read-outs) for every module.
• [] Confirm the exact original US Type Key and locate the exact matching EU Type Key counterpart.
• [] Clear all existing DTCs in ISTA+ before starting so you begin with a clean fault memory.

In the BMW coding world, work is split into two primary methodologies:

FA/VO Coding (Vehicle Order)

When you modify the vehicle’s master profile (FA) by changing its type key or SALAPA elements (option codes), and then Code a target ECU, E-Sys automatically calculates and writes the factory-default settings for every parameter in that module based on BMW’s official engineering matrix.

• Pros: Clean, factory-grade transition. Automatically fixes dozens of sub-parameters in one go.
• Cons: Overwrites any custom FDL tweaks you previously performed on that ECU.

FDL Coding (Function Data Line)

FDL coding involves manually editing specific hex values or drop-down parameters directly inside a single CAFD file without altering the master Vehicle Order.

• Pros: Surgical precision. Allows you to tweak single features (like turning off legal disclaimers) without affecting anything else.
• Cons: Takes longer to configure across multiple modules and requires precise parameter knowledge.

5. Step-by-Step: Changing the Vehicle Order (FA) in E-Sys

Let’s walk through a real-world scenario using an F30 Sedan with an N20 engine.

Step 1: Connecting and Backing Up

1. Connect your ENET cable, open E-Sys, and select your target chassis (e.g., F030).
2. Read FA from the vehicle, click Save, and name it FA_ORIGINAL_US.xml. Keep this file safe!

Step 2: Editing the Type Key

1. Navigate to FA Editor in E-Sys.
2. Expand: FA $\rightarrow$ FZAuftrag $\rightarrow$ Type.
3. Locate the Typekey element.

• US Example: 3B13 (US-spec F30 328i)
• Change to EU: 3B11 (EU-spec F30 328i)

Important Note: You cannot pick a random EU type key. It must match your chassis, engine variant, steering orientation (LHD/RHD), transmission type, and emissions level!

xml

<!-- Example E-Sys FA Type Key Adjustment -->
<Type>
    <Typekey>3B11</Typekey> <!-- Converted from US 3B13 -->
    <Entwicklungsbaureihe>F030</Entwicklungsbaureihe>
</Type>

Step 3: Modifying SALAPA Elements (Option Codes)

Under FZAuftrag $\rightarrow$ SALAPA-Element, you will find the string of 3-digit factory option codes. Modify the country-specific entries:

Add EU Option Codes:

• 548 – Odometer in Kilometers
• 698 – DVD Area Code 2 (Europe)
• 851 – German Language (or your target EU language code)

Remove US Option Codes:

• 645 – US Radio Control
• 655 – Satellite Radio (SiriusXM - not supported natively in EU)
• 697 – DVD Area Code 1 (US)
• 853 – Language Version English (if changing base language setup)

text

// SALAPA Element Modification Summary
REMOVE: 645, 655, 697, 853
ADD:    548, 698, 851

Step 4: Calculate & Save the New FA

1. Right-click FA and select Calculate FP. Ensure there are no errors in the execution log.
2. Save the new profile as FA_CONVERTED_EU.xml.
3. Load the new FA into the main Expert Mode screen and select Activate FA.

6. Which Control Units Should You Code?

Once your modified EU FA is active, you only need to Code (VO Code) the modules responsible for country-specific operations.

Do NOT perform a global “Code All” action on the vehicle!

Recommended Modules for VO Coding:

1. KOMBI (Instrument Cluster): Switches units to metric (km/h, °C, 24h clock) and aligns cluster warnings.
2. HU_NBT / HU_NBT2 / HU_EVO (Head Unit): Updates tuner frequency spacing, language options, DVD region, and navigation structures.
3. FEM_BODY / REM (or BDC / FRM): Reconfigures exterior lighting parameters, side markers, and fog lights to EU spec.

CRITICAL WARNING – Safety Modules (ACSM): Never VO Code the ACSM (Airbag/Crash Module) during a standard US-to-EU conversion unless you are trained on airbag system hardware differences. US and EU models use different seat occupancy sensors, knee airbags, and buckle sensors. Coding ACSM with an EU FA will instantly trigger air-bag fault codes that require specialized clearing or hardware coding.

7. Manual FDL Tweaks: Head Unit & Exterior Lights

If you prefer not to VO Code your entire head unit—or if you want fine-grained control over specific parameters—you can perform these targeted FDL edits.

A. Head Unit Adjustments (HU_CIC / HU_NBT / HU_EVO)

1. Disable Legal Disclaimer

• Module: HU_CIC or HU_NBT
• Section: 3001
• Parameter: LEGAL_DISCLAIMER_TIME $\rightarrow$ Change to kein_ld
• Parameter: MACRO_CAM_LEGALDISCLAIMER $\rightarrow$ Change to kein_ld

2. Switch Radio Frequencies to European Grid

US radios skip even decimal frequencies (e.g., 101.1 to 101.3). EU radios require 0.1 MHz stepping and different de-emphasis filters.

• Module: HU_NBT / HU_NBT2
• Parameters:
• RADIO_COUNTRY $\rightarrow$ ece
• FM_DEEMPHASIS $\rightarrow$ 50us
• DISPLAY_FREQ $\rightarrow$ not_active

3. Change DVD Region Code

• Module: HU_NBT
• Section: 3000 ENT_VIDEO_DVD_AREA_CODE
• Parameter: DVD_AREA_CODE $\rightarrow$ Set to 2 (Europe)

DVD Area Code Reference:
Code 1: USA / Canada
Code 2: Europe / Japan / Middle East
Code 3: South East Asia
Code 4: Australia / South America

B. Exterior Lighting & Sidemarkers

US law mandates amber side-marker lights embedded inside the front headlights. European road laws generally disallow amber side running lights.

Deactivating Front US Sidemarkers (FEM_BODY / FRM)

• For FEM_BODY (F30, F32, F80, etc.):
• Module: FEM_BODY $\rightarrow$ Section 3063
• MAPPING_SIDEMARKER_L_OUTPUT $\rightarrow$ off
• MAPPING_SIDEMARKER_R_OUTPUT $\rightarrow$ off
• For FRM (F06, F10, F12, etc.):
• Module: FRM $\rightarrow$ Section 3060
• U_EFF_SM_V $\rightarrow$ Change value from US specification to EU default.

C. Rear Fog Light Activation

US BMWs almost always have the physical wiring and internal circuit board for the rear fog lights installed from the factory, but the button on the dash light switch is blocked or missing, and the function is disabled in software.

1. Software Coding:

• Module: FEM_BODY $\rightarrow$ Section 3060
• NSL_Verbaut $\rightarrow$ installed (value: 01)
• Module: REM $\rightarrow$ Section 3063 (LCELampMapping 2)
• Mapping_Nebelschlussl_L_output $\rightarrow$ nsl_l
• Mapping_Nebelschlussl_L_Function $\rightarrow$ nebelschlusslicht
• Mapping_Nebelschlussl_R_output $\rightarrow$ nsl_r
• Mapping_Nebelschlussl_R_Function $\rightarrow$ nebelschlusslicht
• Module: FEM_BODY $\rightarrow$ Section 3064
• LCE_BEL_LIN_VAR $\rightarrow$ Change to match EU switch variants (e.g., BEL_FLC_NSL).

2. Physical Switch Mod:

Replace the driver-side light switch module with an EU light switch containing the rear fog button, or modify your existing US switch panel (removing the plastic tabs holding the blank button).

8. Tail Light Coding: Separating US Combined Signals to EU Spec

This is where most US-to-EU retrofits hit a snag.

On US BMWs, the rear turn signal and brake light share the same bulb array or LED cluster. When you hit the brakes, the amber/red outer lights illuminate continuously. If you turn on a indicator while braking, that side flashes while the other stays solid.

In Europe, brake lights and amber indicators MUST operate on completely independent circuits. If you simply plug an EU amber tail light into a US-coded car, the amber indicator will stay solid red/amber every time you touch the brake pedal!

US vs. EU Tail Light Mapping Parameters (FRM / REM Example)

To enforce true ECE logic, you must separate the brake signal (BL) from the US turn signal/brake combination logic (FRAZ_BL_US).

Example Parameter Adjustments (FRM Models):

• Module: FRM $\rightarrow$ Section 3080 (FRM_LAMPMAP)
• Locate mapping values: LAMP_MAP_PARA_SATZ_05 & LAMP_MAP_PARA_SATZ_06
• US Logic Parameter: Bv_F010_Wert_02_Fraz_Bl_Us
• EU/ECE Logic Parameter: Bv_F010_Wert_01_Bl_Ueber_Sl2

Raw Hex Data Translation (FRM Lamp Mapping):

LAMP_MAP_PARA_SATZ_05 (Left Outer Light Mapping)
US Raw Hex: 17 1D 0F 64
EU Raw Hex: 17 07 04 64

LAMP_MAP_PARA_SATZ_06 (Right Outer Light Mapping)
US Raw Hex: 18 1D 0F 64
EU Raw Hex: 18 08 04 64

Key Parameter Translation Glossary:

• BL = Bremslicht (Brake Light)
• FRA = Fahrtrichtungsanzeiger (Turn Signal / Indicator)
• FRAZ_BL_US = Combined US Turn Signal & Brake Function
• BL_UEBER_SL2 = Separated EU Brake Light Logic via Tail Light Channel 2

9. Physical Hardware & Pin Assignment Checks

Do not rely solely on software! Changing coding parameters without verifying wiring will cause lighting error codes on your dash.

Before driving on European roads, inspect the following:

1. Connector Pinouts: Ensure the inner and outer tail light plugs carry dedicated wiring for the turn signal pins. On some US models, a wire jumper or missing pin must be run from the Rear Electronic Module (REM) to the outer tail light plug.
2. Amber Lenses: Replace red US outer lens assemblies with genuine ECE-approved tail lights with yellow/amber LEDs.
3. Bulb Monitoring: If you swap halogen housings to LCI Euro LED tail lights, update cold and warm bulb monitoring (KOLD_UEBERWACHUNG / WARM_UEBERWACHUNG) parameters to nicht_aktiv to stop LED flickering and cluster warnings.

10. Post-Coding Quality Assurance Checklist

After writing the new FA and coding your control units, run through this verification routine:

Functionality Test Checklist:

• [] Engine Ignition Check: Does the engine turn over smoothly with no ignition errors?
• [] Cluster Display: Is speed displayed in km/h? Are temperature units in Celsius?
• [] Radio Tuning: Perform a full FM/AM station search. Verify that even-numbered frequencies (e.g., 98.0, 104.2) tune clearly.
• [] Language & Maps: Verify native EU language settings and check that the navigation system accepts European route guidance (note: navigation requires loading ECE map data and an FSC activation code).
• [] Front Sidemarkers: Confirm front amber corner lights are extinguished when low beams are active.
• [] Rear Lights Test (Crucial):

1. Turn on headlights $\rightarrow$ verify tail bar illumination.
2. Press brake pedal $\rightarrow$ verify brake lights illuminate brightly without amber indicators turning on.
3. Keep brake pedal down and switch on the hazard lights $\rightarrow$ The amber turn signals must flash clearly while the red brake lights remain steadily lit.

• [] Diagnostic Memory Scan: Connect ISTA+, clear all temporary shadow codes, perform a full ECU reset, and verify that 0 active fault codes remain in FEM_BODY, REM, KOMBI, and HU_NBT.

Deepen Your Automotive Diagnostic & Coding Expertise

Mastering E-Sys, ISTA, and advanced BMW Vehicle Order manipulations opens up incredible possibilities for retrofits, LCI conversions, and custom tuning.

If you are looking for hands-on, step-by-step video instruction covering advanced BMW software programming, chip-level diagnosis, and retrofit configurations:

👉 AccesstheBMWAdvancedProgramming&RetrofitCourseAccount