View Single Post
      04-30-2013, 11:55 AM   #181
tom @ eas
General
tom @ eas's Avatar
United_States
8108
Rep
18,798
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]
Quote:
Originally Posted by bicoastalbmw View Post
A BMW Specialty Shop in San Diego was unable to code my 2007 Post 03/2007 E90 rear tail light LCI upgrade today..flicker, no reverse lights, outter lights brighter than inner lights and fast signal with error lights.

They suggested I may need the FRM 3 Module (shows up as possible recommendation on EAS Web they were referencing).

When I spoke with EAS (for whom I'm waiting for a quad rear diffuser), they indicated that I shouldn't need the FRM.

I've read all the posts - and sorry - still some confused. It's a 90 mile drive - but worth it if corrects the issue - just wondering if the FRM may be a requirement still?

Any direction is appreciated.

JD
FRM3s are no longer required. We go over this slightly in Post 91:

Quote:
Originally Posted by tom @ eas View Post
Today was a milestone in programming, we are now able to program LM2 modules. In this entry, our friends at VF Engineering will be returning with their M2 Widebody Fighter Pilot for programming:



You might remember in an earlier post that we performed the LCI update on VF Engineering's 2008 Widebody M3, leaving the LM2 module installed for further R&D.



Disregard the EAS button in the video - that's top secret

As seen in the video, we have successfully coded out BulbCheck with no errors present on the dash or iDrive display.

Overview:
- Flickering removed during startup
- Blinker operates at normal speed
- Bulb out errors are no longer present

What does this mean?
FRM3 modules are no longer required for LCI updates.

Would you recommend a FRM2 or FRM3 module for my LCI upgrade?
We still recommend a FRM3 module for upgrades. The coding is performed differently in which any dealer updates do not affect programming that is already present. FRM2 modules are coded different in which BulbCheck is disabled, but can be overwritten if the FRM module is updated. Typically FRM modules are not updated in this fashion, but those looking to save a few bucks can't go wrong keeping the FRM2.

What's in store for the future?
As in the past, we will be handing our notes over to autologic, in which local programming facilities (including our competition on the forum) will now have access to the coding for local programming.

Last Note:
Unfortunately, this may be our last Q/A session. While this is informative to the forum members, it has also trained our competition here (LCI Taillamp upgrades, Folding Mirrors, City Lamps) on the forum, using the literally hours of hard work and late nights we've logged to compete against us. While it's not typically the fashion in which we work - it seems the competitiveness in the market is driving things in this direction, which prevents these types of things from happening.

As thanks for those that have supported us - we will be providing FRM2 coding for the next 5 people that make an appointment at no charge, no matter where your taillamps were purchased. Its our way of saying thanks, and allowing those looking for an experienced programming facility to suit their needs.

Without you - these types of projects would not have been possible.
You're not too far away in San Diego (we're in Anaheim). Drop by and I can have you coded in a matter of minutes.

Quote:
Originally Posted by Fortyb View Post
Do like i did give TOM are someone at EAS a call when you have the Auto logic hooked up and let him walk you are the shop through the Process...it worked out great for me....And i have a 2007 with the FRM2 module..
Appreciate the feedback, thanks!
__________________
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
Appreciate 0