When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Here’s the problem I'm having with my 2016- XLT, 3.5L EB, SCREW, 302A package. I added Sealight LED to my front High, Low, and Fog Lights. When I installed just the front led lights I had no issues, no codes, and no hyper blinking.
After I installed the Sylvania LED bulbs to my tail lights, I now have hyper blinking on the driver's panel, and several codes. I've tried over several weekends to eliminate the codes and hyper blinking using FORScan and without success. I'm including several pictures of the error codes that I have hoping someone can help me figure this crap out.
I've tried several times writing new code and saving it, but I just continue to have no success. When writing a new code for a change should I be using the X’s in the code as seen here Should these X’s be actual X’s or zeros?
Thank you in advance for your help and pictures are always helpful.
What is this and how the hell do I fix this code as well?
Last edited by Cuban Cigar; Mar 1, 2020 at 09:18 PM.
Reason: More needed information on a fix.
The only changes you should be making are the "*". Leave the rest as is. As far the tail lights you should be changing 726 27 02. xxxx xxxx x0xx You shouldn't have to change anything if you are changing hi and low beam bulbs only.
The overview is this: my truck came with halogen or standard bulbs. It also constantly tests for bulb outage, to flash a message on the dash if I have a bulb out. When I replace those bulbs with LEDs, they don't have the same resistance and the truck either says I have a bulb out, or more likely, hyper-flashes. So what I did in Forscan is turn off that bulb testing, which is a configurable option.
I did not have to do this for my headlights. I imagine they pull enough power.
So what labmaster02 provided above was the value to set: 726 27 02 xxxx xxxx x*xx Rear bulb turn outage cfg: 1=outage, 0=no outage
The only value I change is where the "*" is, which should be a "1" and I changed it to "0". I'm careful to not change anything else. The x in the spreadsheet is just a place-holder and on my truck those fields have some value. Point is the * is the only value I changed.
I saved it, do what is says to cycle the ignition, and test it. The hyper-flash was gone.
Hope this helps.
Last edited by Whysoangry; Mar 1, 2020 at 09:04 PM.
I did this change in the BCM module several times, but I'll try it again. Should I do a restore to factory settings reset prior to trying it again?
In your original post on the third picture you are showing the address for the headlight outage not the tail lights. Are you sure you're changing the right address?
In your original post on the third picture you are showing the address for the headlight outage not the tail lights. Are you sure you're changing the right address?
I didn’t install the front LED bulbs at the same time as the rear taillights. I liked the brightness of the Front LED lights. I went ahead and replaced the rear lights, this is when Hyperflashing started on my truck turn signals.