Originally Posted by plumkrazy80

Yes, I did indeed figure this out. No payment needed, lol. I'm glad I can contribute to the forum. Everything on the headlights is working properly as intended from the factory. I set off down this path, because I was reading everything on these forums about the issues with the RR and TRS harnesses and didn't have a good feeling about them. I didn't want to be constantly setting overcurrent faults and eventually brick the BCM and have to replace it. I know that these type of FET circuits can only handle so many faults like that before they shut them off permanently. It seems that Ford has the tolerances on the headlight circuits set up pretty tight, which is why so many people are having lights shutting off and setting faults.

I figured it all had to be programming because of the FET circuits that control the headlights and the BCM is the same physical part number between the Halogen vs LED. I work for a company that uses these smart fuse box type products in our equipment and have a little familiarity with them and what is possible. So I started researching the wiring inputs into the BCM and found that there are only 4 wires different between the Halogen vs LED. 2 Turn Signal inputs (since the LED's are low current the BCM needs these to determine if there is an outage) and 2 Daytime Running Lamp circuits. I pulled the connector off of the BCM that these wires are supposed to go into and found the Tyco connector housing part numbers and contacted Tyco to get the correct terminal part numbers. I ordered them and them crimped the terminals on and ran my wires. After that, it was all BCM programming with Forscan. Since I have a Lariat and the LED's are offered as on option on this level, I basically just found the VIN of a truck optioned similar to mine and dowloaded it's As Built Data to compare to mine. It took multiple tries as I found that some parameters needed others to even program and set the option properly. I'll detail this more when I do my write up.

The only issue i have so far is that I have a few communication and invalid message faults that have popped up. I assume from controllers looking for modules/messages that I don't have. Nothing that comes up on the Instrument Cluster, so the typical user wouldn't know they were even there, but I know they are there from doing a DTC scan. I was going to play around with a few more settings in Forscan and see if I could figure them out. I could honestly leave it as is and be happy, but I'm a bit of a perfectionist and want everything to be 100% clear and no faults.

We'll have to see, if I can't figure it all out, I may need some help from Livinitup as I think he dives deeper into Binary on the hex configuration settings. I know a little bit about hex and CAN messages as I use CANalzyer and monitor messages for my testing job, but I don't typically go down into binary. I know how to convert them to binary, but if he already has something set up, he may be way quicker at it than me trying to figure it all out from scratch.

As soon as I got all this figured out and was fault free, I was going to start a thread just for this so it could be easily referenced.

Sorry for my slow responses on this too. Work is a bear now with long hours and the family has been taking up the rest of my time, so I haven't had much time to devote to finishing it up. I'll stick with it though. Anyone is always welcome to PM me to get any details they may want until I get the thread up when finished.

Originally Posted by plumkrazy80

As soon as I got all this figured out and was fault free, I was going to start a thread just for this so it could be easily referenced.

Originally Posted by remltr

Anybody with a specific power point setting find that it works inconsistently?

I have mine set to 1 second. It very rarely works. I'd say it works maybe 10 to 20 percent of the time.

I have a dashcam that will shut down when the setting works, otherwise I have to manually shut it down.

Originally Posted by remltr

Anybody with a specific power point setting find that it works inconsistently?

I have mine set to 1 second. It very rarely works. I'd say it works maybe 10 to 20 percent of the time.

I have a dashcam that will shut down when the setting works, otherwise I have to manually shut it down.

Originally Posted by Livoniabob

I have always had this problem.. only sure bet is to do my fuse box jumper mod for true 24/7 operation..
But that's a different problem than you have. My dash cam is powered from the passenger side fuse box and is always on with power on and off with power off.. It was a easy job to run the cord down the A pillar and tap a fuse..

Originally Posted by viper_crazy

Curious, how did you guys (the ones who made the spreadsheet) figure out which asbuilt values were for which feature and how to change them and figure out the calculations for the values?

I'd like to start playing around with my wife's Focus Titanium but aside from the plain English, and a few tips from YouTube, there is no list or information spreadsheet for those who also have a Focus. Also, the Focus doesn't have near as many values as the F150 does.

I know there's a program called Focccus (apparently nothing to do with the car) but it doesn't work with my modified ELM very well, but Forscan works like a champ, so I want to Forscan map the modules of these mods that guys are doing.

Originally Posted by Firerunner

That's the only way I have found to consistently turn my dash cam off also.

Originally Posted by lucas8888

Comparing other trim levels as built data and/or trial and error.

Yeah focccus is for ccc based vehicles.