Have you retrofitted LCI or facelift headlights to your BMW, but still have warning messages, missing lighting functions or an incorrectly aimed beam? This does not automatically mean only coding remains to be done. A headlight conversion requires the vehicle series, production date, lamp type, control units, wiring, vehicle configuration and permitted lighting functions to be compatible.
This guide helps assess the situation before buying parts and after a completed conversion. It distinguishes coding and programming from electrical diagnosis, mechanical adjustment, calibration and approval checks. A universal parts, pin or coding list would not be responsible for headlights: pre-facelift, LCI, market versions and equipment can differ significantly even within the same vehicle series.
Short answer: when does an LCI headlight need coding?
Coding may be needed if, after a technically suitable conversion, the vehicle is still configured for its original lighting equipment. Depending on the BMW, this involves the vehicle order, the relevant body or lighting control unit and installed headlight modules. Coding cannot repair a missing power supply, incorrect pin assignments, damaged wiring, an unsuitable lamp or faulty mechanics.
The correct sequence is therefore to identify parts, check installation and electrics using vehicle-specific documentation, read the control units, establish the intended software procedure, and then check the beam pattern and every function on site. The Bimmerfit service starts only after a vehicle and parts assessment: BMW LCI/facelift headlight coding.
Still unsure what is causing the fault? If a headlight stays dark or the beam is aimed too low, have the electrics or alignment checked on the vehicle first. If the vehicle can communicate with diagnostics, remote ISTA diagnostics can help assess stored faults in reachable lighting modules. For a rear-light conversion, see the LCI rear-light guide.
What does LCI mean at BMW?
BMW uses LCI as an abbreviation for “Life Cycle Impulse”, meaning a model update within a vehicle series. Front-headlight design and technology can change during this update. Similar bodywork does not mean pre-facelift and LCI headlights are electrically interchangeable. Even a headlight that fits externally may have different lighting modules, connectors, wiring, data communication or software requirements.
A retrofit therefore needs more than the model and year. The production month, body variant, market version, original lighting equipment and complete part numbers of all new components matter. For an F30, for example, “F30 LCI” alone is not enough; halogen, xenon, LED and adaptive versions must not be treated as equivalent without technical evidence.
Distinguish halogen, xenon, LED and adaptive lighting
The original and desired lighting technology determine the scope of the conversion. Changing within the same technical family can involve different work from changing halogen to xenon or LED. Adaptive functions also require suitable lamps, control units, sensor information, wiring and vehicle configuration. A visible LED light signature does not prove that every adaptive function is supported.
| Original or target system | Particular checks before proceeding | What coding cannot replace |
|---|---|---|
| Halogen | Lamp type, connectors, power supply, bulb monitoring | Suitable hardware and wiring |
| Xenon | Ballasts, ignition technology, levelling and cleaning requirements of the specific version | Components, installation and required equipment |
| LED | LED modules, drivers, cooling, communication path and part numbers | Faulty LEDs, modules or connector contacts |
| Adaptive lighting | Complete system equipment, sensors, modules, initialisation and adjustment | Mechanical repair, calibration or a test station |
This table provides orientation, not approval. The intended combination for the specific vehicle is checked using vehicle data and BMW parts information.
TMS, LHM2, FLM or FLE: why the module name matters
Depending on the generation, BMW uses different names and architectures for headlight and lighting modules. BMW service information refers to TMS, LHM2 and FLM, among others; other lighting control units may be involved in further generations. These names are not interchangeable and should not be copied from a tutorial for another vehicle series.
A BMW service bulletin for the F15 and F32, for example, mentions TMS-3 in connection with adaptive xenon or LED headlights. Another document for selected F15, F25, F32 and F33 vehicles mentions LHM2 and requires diagnosis of the BDC or FRM and LED main light module first when communication faults occur. For the G07 LCI, BMW describes a software-related case in the FLM (BMW SIB 63 06 14, BMW SIB 63 09 14, BMW SIB 63 04 22).
These cases illustrate model dependence, not a universal repair procedure. Before buying used modules, document the label, complete part number, hardware and software versions, and donor vehicle.
Which parts must be compatible before installation?
- left and right headlights for the correct body and market version,
- all intended lighting, driver or headlight modules,
- connectors, adapters and wiring kit for the original and target equipment,
- where applicable, sensors and further components for the required function,
- mechanical mounts, seals, height adjustment and undamaged housings,
- suitable software and vehicle configuration.
An identical connector or mechanically suitable housing is not complete proof of compatibility. Aftermarket headlights may use their own electronics or resistors and behave differently from original parts. For a retrofit kit, the manufacturer, product number and complete installation instructions are needed.
Typical symptoms after a retrofit
| Symptom | Important initial check | Possible next step |
|---|---|---|
| The headlight remains completely dark | Power supply, ground, fuse, connector, module communication | Local electrical checks and diagnosis |
| Only the daytime running light or dipped beam works | Lamp version, modules, pin assignments, fault codes | Compare parts and functions |
| The headlight aims significantly too low or does not perform a reference run | Mechanics, adjustment, sensor values, module faults and software | ISTA test plan and mechanical inspection |
| The light flickers or fails intermittently | Connector contact, module, power supply under load, moisture, software version | Reproduce the fault and read complete diagnostic information |
| Check Control warning despite a visibly working function | Lamp type, monitoring, vehicle order and electrical condition | Establish hardware plausibility first, then assess coding |
| Adaptive lighting does not work | Complete system equipment, sensors, modules, initialisation | Diagnose the entire functional system |
One symptom does not reliably identify the cause. For the F15/F32, BMW documents both a TMS coding error and faulty headlight mechanics as possible causes of headlights aiming too low. “Just code it” without diagnosis is therefore not a reliable repair plan.
Vehicle order, coding and programming are different steps
The vehicle order describes the intended equipment of the vehicle. A complete, supported retrofit may require this equipment configuration to be adjusted. The relevant control units are then coded for the confirmed configuration. Programming or a software update is a separate process and is planned only when required by the vehicle, module condition and measures plan.
BMW service bulletins limit software remedies to specific vehicle series, production periods, symptoms and integration levels. The FLM software fault described in SIB 63 04 22, for example, concerns only a defined G07 LCI case. This must not be taken to mean that the same update resolves every instance of flickering after a retrofit.
Personalised adjustments may need checking again after a later vehicle software update. See the separate guide BMW coding lost after a software update.
Coding problem or a connector and wiring fault?
If only one side does not light up, a local fault involving power supply, ground, connector, wiring, module or headlight is particularly plausible. If both sides behave identically and hardware is demonstrably installed correctly, the vehicle configuration may become more relevant. This is still a prioritisation, not a remote diagnosis.
BMW SIB 63 09 14 describes flickering or failed LED headlights on certain vehicles and identifies a poor connection at the headlight connector or LED main light module as the cause. The prescribed diagnosis starts with a vehicle test and communication faults, not disabling bulb monitoring. Coding does not repair a corroded pin or broken wire.
If the starting condition is unclear, BMW remote diagnosis with ISTA can record stored faults and communicating control units. Voltage, signal and wiring checks are still performed on the vehicle.
What applies to used headlights and lighting modules?
Used parts can make technical sense, but require careful comparison. Beyond the complete BMW part number, the index, module variant, original equipment and visible condition matter. A used headlight may have damaged mounts, moisture, internal repairs or unsuitable modules even when its housing looks correct externally.
A replacement module may need coding, programming or initialisation. What is permitted and technically possible depends on the module and vehicle. The BMW control-unit adaptation page provides a general overview. Before buying parts, obtain photos of the complete original and replacement labels.
Headlight adjustment and calibration remain on-site work
After installation and software work, the actual beam pattern must be checked with suitable test equipment. Section 50 StVZO requires, among other things, that headlights can be adjusted and are secured so they do not move unintentionally; it also contains requirements to limit glare (Section 50 StVZO).
Adaptive systems may require additional initialisations, reference runs or vehicle-specific test procedures. The exact BMW repair instructions for the vehicle and equipment take precedence. A remote connection cannot measure the real light-dark cut-off at a test station and replaces neither adjustment nor necessary calibration.
Approval, approval markings and public-road use
Successfully controlling a headlight does not automatically establish approval for road use. In Germany, Section 49a StVZO sets out principles for lighting equipment and specifies, among other things, that lamps may use only light sources intended for their design. Annex VIIIa lists condition, design, permissibility, function and headlight adjustment as inspection criteria (Section 49a StVZO, Annex VIIIa StVZO).
UN Regulation No. 48 concerns vehicle approval with respect to the installation of lighting and light-signalling devices. Which version applies to a specific vehicle and country must be professionally assessed (EUR-Lex: UN Regulation No. 48).
Bimmerfit does not issue vehicle operating approval or perform statutory roadworthiness inspections. Component markings, installation, required equipment, adjustment and any necessary approval inspection are clarified with a qualified workshop or inspection body before use on public roads.
A sensible diagnostic sequence
- Document original and target equipment: Record the VIN, production month, body style and market version, and keep photos of the original and replacement headlights.
- Record all parts: Collect the numbers of every lamp, module, adapter and wiring kit.
- Check installation locally: Inspect mounts, sealing, connectors, pin assignments, power supply, ground and fuses using the correct wiring diagram.
- Read the vehicle: Record communication, fault codes and relevant status values of the lighting and body control units.
- Establish the software procedure: Do not confuse vehicle order, coding, programming and initialisation.
- Check functions while stationary: Check daytime running, position, dipped-beam, main-beam, indicator and adaptive functions individually, only where present.
- Have the beam pattern professionally adjusted: Use a test station and vehicle-specific instructions; then have permitted use confirmed.
The ENET or K+DCAN for BMW and MINI guide explains which connection may suit the electronic assessment. The cable is confirmed only after the vehicle assessment.
What Bimmerfit can handle remotely
After technically complete installation, Bimmerfit can check vehicle data, control-unit communication and the starting configuration for a supported combination. Depending on the findings, the agreed vehicle equipment and relevant control units are adjusted, or a suitable programming procedure is agreed.
- assess the VIN, production configuration and documented parts combination,
- check fault memory and communication with the relevant modules,
- adjust vehicle order and coding for a confirmed retrofit,
- establish a necessary software procedure only from specific findings,
- check electronically accessible functions together with you.
Installation, repinning, wiring repairs, moisture removal, mechanical headlight adjustment, light measurements, calibration requiring workshop equipment and statutory approval inspections cannot be performed remotely. Further technically completed conversions are listed under BMW & MINI retrofits.
Information we need before the appointment
- the last seven characters of the VIN, model, production month and body style,
- the original lighting equipment and desired LCI/facelift version,
- photos of complete part numbers for all headlights and modules,
- the manufacturer and product number of an aftermarket or adapter wiring kit,
- installation instructions or the vehicle-specific wiring diagram used,
- complete fault codes and a photo or video of the visible symptom,
- which lighting functions actually work on the left and right,
- details of previous software updates and used parts.
Rear lights need their own assessment route. See BMW LCI rear-light retrofit and coding. General remote services are grouped under BMW remote coding.
Frequently asked questions
Do BMW LCI headlights always need coding?
Not every parts combination follows the same procedure. A genuine pre-facelift-to-LCI retrofit may require adjustments to the vehicle order and control-unit coding. Whether programming or initialisation is also needed is checked using the vehicle, lamps and modules.
Can coding repair a completely dark headlight?
Only if the hardware is demonstrably functional and the correct software configuration alone is missing. Power supply, ground, fuse, connector, wiring, module and headlight must be checked first.
Why does a headlight aim too low after the conversion?
Possible causes include mechanics, adjustment, sensor values, module faults, initialisation or a series-specific software issue. BMW documents both a TMS coding error and a jammed mechanism for certain F15/F32 vehicles. The specific diagnosis determines the cause.
Can used TMS, LHM or lighting modules be used?
An assessment is possible, but not a blanket approval. Part number, variant, hardware and software versions, donor vehicle and condition must match. Further software work may be needed depending on the module.
Is headlight adjustment included in the remote service?
No. After the conversion, the actual beam pattern must be checked and adjusted on site using suitable equipment. Remote coding does not replace mechanical adjustment or necessary calibration.
Is the conversion automatically road-legal after successful coding?
No. Coding feasibility and approval are separate questions. Parts, approval markings, installation, light sources, equipment, adjustment and any required inspection must suit the vehicle and country of use.
Technical and legal sources
- BMW SIB 63 06 14: One or Both Headlights Are Aimed Downwards
- BMW SIB 63 09 14: LED Headlight Malfunction
- BMW SIB 63 04 22: Low Beam/Cornering Light Flicker
- Section 50 StVZO: dipped-beam and main-beam headlights
- Section 49a StVZO: lighting equipment
- Annex VIIIa StVZO: inspection criteria
- EUR-Lex: UN Regulation No. 48
Get a free initial LCI headlight assessment: Send the model, production month, last seven VIN characters, photos of part labels and a short description of the conversion via WhatsApp. Before booking, we explain whether parts, wiring, diagnosis, coding, programming, adjustment or approval needs clarifying first.
Bimmerfit is offered by the independent Altin & Yaman GbR and has no commercial affiliation with BMW AG or MINI. The trademarks are used solely to describe the supported vehicles.