View Single Post
      05-15-2010, 02:15 AM   #1
tom @ eas
General
tom @ eas's Avatar
United_States
8058
Rep
18,786
Posts

Drives: BMW
Join Date: Nov 2005
Location: Anaheim, CA

iTrader: (19)

Garage List
2018 BMW i3s  [0.00]
2010 BMW M3  [6.50]
2015 BMW M4  [5.25]
▀▄ eas - 2011 LCI Taillight Retrofit Overview - Q&A

The release of the 2011 LCI (Life Cycle Impulse) introduced some minor improvements to the vehicle. On the exterior side, most noticeably with the taillights. This DIY will give a quick overview for those to update their lighting to update the rear of their 07-10 3-series Coupe or Convertible to appear like the 2011 models.


An LCI Upgrade consists of inner/Outer taillamps, trunk lamps (4 total) and Plug and Play (PnP) harnesses.



Our example will be performed on a 2010 M3 Convertible, which is the last production year of the Pre-LCI lamps:


























On pre-LCI vehicles (>2011), there are a series of "checks" that are performed when the ignition is turned on.

Once of these processes is called "BulbCheck", which sends small voltage pulses to the various exterior lamps of the vehicle and expects a load on the circuit - which a stock halogen bulb would give. The voltage used is very small, not enough to light up the bulb - so it's never seen.

LEDs require very little voltage to operate, and can pick up these pulses - which is the "flickering" seen when the ignition is activated: BulbCheck in action. This also results in errors on the instrument cluster/iDrive screen since the vehicle thinks the bulbs are non-functional. Coding will tell the vehicle (4 different control modules) that LED lamps have been retrofitted and that BulbCheck isn't required in those specific fields any longer, allowing the vehicle to operate like normal.

Here's a quick video of the LCI taillamps in action to show the differences before coding and after coding is performed:



The LCI Taillamps are 100% functional after installation as seen in the component test, I want to make sure everyone is clear that the vehicle is not unsafe to drive if the end user has not yet had a chance to get the vehicle coded.

Do keep in mind that coding is required for a proper installation and targets correcting the bulb-out indicators on the instrument cluster/iDrive as well as pre-ignition flickering upon startup. This will also ensure that no future errors are present if the vehicle should ever visit the dealer for other service updates or maintenance work.

The following modules are coded:

Car Access System (CAS)
Junction Box Electronics (JBE)
Footwell Module (FRM)
Instrument Cluster

BulbCheck is removed for only the lamps that were replaced by LEDs, all other monitoring systems are kept in place.

A LOT of work has gone into making sure this was performed correctly - even providing log sessions of 16 different vehicles, including making a trip to the dealership to scan vehicles with pre-equipped LCI builds in log comparisons.

Coding will also allow the vehicle to pass all verification and safety checks, as well as not provide any issues if the vehicle is ever brought in for service - since we are using original BMW parts and proper coding has taken place, rather than attempting to "band-aid" the situation with add-on resistors (which are dangerous).

Here are some shots of the FRM2/FRM3 location underneath the driver's side footwell:



You do not need to upgrade to FRM3 for LCI Coding!For those looking to inspect what type of FRM they have, the part label will have either FRM2 or FRM3 displayed, we have the ability to code either FRM2 or FRM3 modules:



Thanks for reading, feel free to respond with any questions - with the intention of keeping this a technical-specific thread.
__________________
Tom G. | european auto source (eas)
email: tom@europeanautosource.com · web: https://europeanautosource.com· tel 866.669.0705 · ca: 714.369.8524 x22

GET DAILY UPDATES ON OUR BLOG · FACEBOOK · YOUTUBE · FLICKR · INSTAGRAM

Last edited by tom @ eas; 11-27-2012 at 07:00 PM..
Appreciate 0