I have a 2013 F150. TPMS light has been on since I got this truck 3 years ago. I hooked my scan tool up to it after driving for 30 minutes all sensors are reading accurately all within 1 psi of each other. Has a B124D code active. The light is on all the time constantly not flashing just constantly illuminated. Have tried to train the sensors 2 different times with no success. This truck has had some strange electrical issues since I bought it. The Instrument Cluster has been replaced with used a couple years ago due to a faulty fuel guage. The scan tool can turn the low pressure indicator on and off successfully. I'm assuming the TPMS module is fine since it is reporting proper pressures to the BCM. Am I looking at BCM issue or am i jumping the gun. I have access to a BCM from a truck with the same build date can is use it as test i'm sure it will throw some codes but i'm hoping I will at least be able to see if it makes the light go off am i correct on this assumption?

 

Any electronic accessories routinely plugged-in? e.g. ...

Excerpted from the Ford Motorcraft TIRE PRESURE MONITORING SYSTEM document ...Also ...

HINT/TIP: Put your complete vehicle information (year, model, cab, trim, engine, wheelbase, _x4 drive, mileage, modifications, etc., etc.) in your signature. *Eliminates playing 20 questions when/if a post is made pertaining to your vehicle.
» Edit Signature « *Don't forget to [ save ] it.
.

 

No there is nothing aftermarket on the truck. Nothing plugged in the truck or sitting in the truck. Been like this ever since I bought it. I'm thinkin the dealer knew something because they wouldn't fix the Light, but they fixed the fuel guage for me. The light has been on for the 3 years since I bought the truck.

 

I think I'd cover or disable the light

 

Google FORScan. It's a great tool. I turn off my TPMS for my winter tires that don't have sensors and go old school with a pressure gauge.

 

does your scan tool update in real time? If so Id ride around with it hooked up and see if you can catch one dropping out. A quick google of the code makes it sound like a failure for one to report in at the normal frequency trips it. If not forscan appears to. With Forscan you can also log it to review later, I believe you can do a graph view which should make it pretty easy to spot