View Single Post
      08-29-2020, 04:28 AM   #83
Poochie
Luxury at the redline :)
Poochie's Avatar
United_States
9108
Rep
7,563
Posts

Drives: 2016 M2
Join Date: Aug 2012
Location: NYC

iTrader: (3)

Quote:
Originally Posted by RamonRuiz View Post
Quote:
Originally Posted by Poochie View Post
There is no official fix for this issue, decoding the bulb checks is the only viable solution and it remaining active is the actual cause of this error.

The TSB currently available only applies to the pre-LCI, non-LED taillights (see below). You can plug in your VIN and see for yourself.

https://www.automd.com/tsb/bmw_m/

BMW AG is not going to download the Bimmercode APP, ApplePay $30 and then remove everyone's bulb check. For them to officially correct this particular issues, the changes would have implement into a full iLevel software revision, as they don't do individuals lines of coding changes, on an official franchise dealer-level.

So unless it's a federally-mandated recall, I sincerely doubt they're going invest the resources to developing a fix & then update the software of every owner's vehicle, just to address this non critical issue.

My guess is they'll just sweep it under the rug, until the models affected with this issue is eventually phased out of production. 🤫
And adding a resistor so blinkers draw more current as it was with incandescent ones?
A resistor might work in tricking the amperage flow but my in my experience, aftermarket resistor add-ons generates a lot of heat and might require some janky wire splicing.

I don't like the potential of a fire hazard but that's just me..

I still stand behind the fact that coding out the bulb checks is the most clean, efficient and proven method of eliminating this issue and is the root cause of this error.
Appreciate 0