Updated Findings for Lariat Headlight Swap

[airline tech]

Can we get these settings posted to the ForScan Spreadsheet?

I have completed my Lariat - Factory LED Downgrade back to AS-Ordered - Now the truck is HAPPY, Bye-Bye Halo's

i had searched through the posts here and found some conflicting info on the correct settings for ForScan after the swap
I compared 3 Lariat's (As-Built) data, and these are the settings that they all have.

Lariat As-Built Compare (From 3 Trucks) (All Match these settings) (With Factory LED's)

BCM
726-26-02 - 0000-0001-0056
726-45-01 - 0A01-1000-008E
726-50-01 - 108E

The various posts state an array of options on these setting but to get it to Factory LED (The LED Strip) as your DRL these are my findings



DRL Configuration to (Dedicated DRL)

Set this option to (16) Dedicated DRL - this will automatically set 2-Lines of Hex Code for you.
NOTE: the (16) is a Binary code that is converted to HEX (Inside of the As-Built) Files

Here are the 2-Lines of Codes it sets

BCM
726-26-02 - 0000-0001-0056 (Matches my Lariat compare search-As-Built)
726-50-01 - 108E (Matches my Lariat compare search - As-Built)

Now set Allowed DRL Options:

NOTE: The Paragraph at the top
If you have only (1) option for DRL, such as Factory LED Headlights, this will show due to the fact that it matches the (16) Binary code you set in DRL Configuration PLUS
This option ONLY modifies (In addition) (Plus) the standard factory DRL.
So, this normal - As I have not added any special (extra) DRL options to the configuration


So, with this selected, here is the last Hex Line of code that is changed (Automatically)

726-45-01 - 0A01-1000-008E (Matches my Lariat compare search-As-Built)

If you do not see this option (highlighted) then go into the As-Built File and manually change it, then when you go back to the (Module) Easy way, this will be shown


If you select (31) (+) Dedicated DRL here, you will see the As-Built Hex Line change to this

726-45-01 - 0A01-1F00-008E - ----This does not match factory settings
Others have posted that you need to set it to this, and it does work, as I have operational checked the Headlight's and DRL's using this one (1F00) and (1000)

Edit:
Note: US Version Trucks - DRL's only operate with Headlamp Switch in (Auto)
and US Version Trucks (DRL's) only operate (On & Bright) in any (Gear) position except Park and as long as Headlamps have not been turned on due to low light conditions from (Auto Headlamps), to ops check in your driveway, place truck in Neutral and set Parking Brake on a bright sunny day.
I added this little note as some have not read the fine print of the owner's manual and creates confusion on proper operation.

If you want your DRL's to be always on (Including with Headlamp Switch in (OFF) like our Candian Neighbors are required to have, then make one other change in Forscan and that is in easy mode - DRL Conditions , when you select a change here you will have (2) options (A or B) , As of this writing I cannot remember what the US Version is set at, I believe Option (B), so change to Option (A)
Rangers have 2 types of DRL (Conditions)
Conventional - (Always On - Even with switch off - (option A) - I think (Candian Trucks)
Configurable - Only (On) with Headlamp switch in (Auto) - option B - I think. (US Trucks)
Without hooking up Forscan, I may have the options ( A & B) backwards


Operational Check:

1. LED Strip - On and Bright
a. With Headlight switch in Auto (Daylight) - So DRL Mode

2. LED Strip - On and Dim
a. Headlight switch in (Headlight) and (Auto - Nighttime)
b. Headlight Switch in Park Lights
c. Activation of Entry / Exit Lights along with Park Lights, Bed Lights, Puddle Lights, Door Locks Activation Etc.

I know there have been quite a few posts on this subject and I wanted to pass along my findings
to clear it up
These are the confirmed settings for the Lariat Factory LED Upgrade, now it should also clear it up for those who have installed the (aftermarket) options. With the attached pics, you can see it more clearly and visualize what changes you want to make

Here are the changes each selection makes to the Hex Line

726-45-01 - (0A01-XXXX-008E)
None: 0100
All Options: 7F00
Low Beam: 0300
Hi-Beam: 3F00
Ft Fog: 0700
Ft Turn: 0F00
Dedicated DRL: 1F00
Incorrect Value or Not Configured - 1000 (Factory Lariat Setting (LED)


Hope this helps

22 Ranger Lariat Screw Cactus Gray


Edit: Jan 18, 2025

Since there are numerous reports of Aftermarket LED Lighting issues due to the manufacture requirement to (Add) Tapped Power for the (DRL) Circuit. I believe this tapped power is creating the issues and how the BCM reacts to the tapped power.
I believe the reason for the Aftermarket (side) for adding a tapped power source is to (eliminate) the perceived need for any Forscan changes.
They cannot market (Headlights) if it requires a (Forscan) change to operate properly.
So they add tapped power as a work around.
The problem is (I do not think the BCM) likes the tapped power source and it is still trying to power the headlamps as (Halo's) - The BCM does not know that you have LED's installed unless you tell the BCM that they are installed.

This is the reason for Forscan changes.

I do not have (Aftermarket) lights as I have factory LED
I cannot see exactly how the Aftermarkets are wired internally and the reasoning or requirement for adding Tapped power.
It MAY be possible to eliminate that tapped power and only make Forscan changes and still get the full functionality of them or still use the Tapped power and just make changes with Forscan.
It is sad and frustrating that some are having issues, it should be a Plug & Play and walk away with NO ISSUES, thats not the case. So all I can do is offer some possible solutions for the issues and hope that we hit the (Golden Nugget) for a fix.

I have found some additional settings that (MAY) change any (operational) issues you are having with any Aftermarket - Assembly and the following lines need to be checked to see how they are set.
By changing the following to match (Factory-LED) settings MAY fix the issues.

I found 3 As-Built files that may tie into the issues for the Aftermarket Lights
IDK - If any of these are tied to the (Easy Way) Config Settings and may not be getting touched or changed if you are only using the (Easy Way)

Check these Files:

BCM:
726-24-01
0000-00C0-D0E2 (Factory - Halo)
0000-0000-D022 (Factory - LED)
Specific's - DRL DTC (Inhibit or Normal)
xCxx = C-Inhibit ----X0xx (Normal)
So, for the factory Halo's it is set to inhibit and with LED is set to normal.

726-29-01
0000-0000-0259 (Factory - Halo)
0000-0000-0158 (Factory - LED)
Specific's - VRMS Target Configure
x2xx - Type 2 -- 01xx - Type 1
So, Type 2 = Halos Installed & Type 1 = LED's Installed
So, this is a voltage supply setting but not clear what light circuit it is actually for.
Headlights or DRL Circuit or Park & Turn

726-61-02
1600-0000-01A7 (Factory - Halo)
1601-0100-01A9 (Factory - LED)
Specific's - LF & RF DRL Lamp Circuit Configure
xxx0-x0xx (Not Used) ---- xxx1-x1xx (Used)

So, it may be possible that one if not all of these As-Built files may fix the issues you are having with the Aftermarket Headlamp Assemblies, it's going to be a TRY THIS setting until someone posts hey this (FIXED) the issue or (NO HELP)

So, if you are swapping from Halo's to any LED assembly and are having issues with them, check the above files and change to the (Factory-LED) settings if they are not already set.

Hopefully, this might help resolve the issues.

Sponsored

 

[cfhgarza]

I would just like to add that if you don't have the settings just right you will have lighting problems, some dangerous.

When I originally did mine I had several issues.
First issue: lowbeam would randomly blink for a split second.
Second issue: DRL strip on driver's side would work intermittently. I believe this is related to the "allowed DRL" setting but I could be wrong.
Third issue: Break lights would intermittently stop and cause a hyper flashing turn signal. Restarting truck would fix temporarily.

Looks like you have the same hex codes as I have. No issues with them

Try these instead of above. This has worked (so far) to make my lights work without all the BCM issues that this configuration has been causing. Try this out.

726-26-02 needs the * number to be a 1 for factory LED xxxx xxx* xxxx

726-45-01 * numbers changed to 1000 to enable DRL xxxx **** xxxx

726-50-01 change the only 4 numbers to 108E which chooses the dedicated DRL

 

[AvockAdoo]

I used the other Lariat Swap thread to set mine up, 2+ months later I havent had a single hiccup. Prior, I was running Morimotos and they were wreaking havoc on my electrical system - hope they didnt cause any lasting damage.

Here's the link to the thread I used. IIRC, it post 121 or something like that which holds the keys. I changed everything using the HEX settings, nothing in "easy mode". Also, mine was an XLT - now its almost fully an XLariaT

XLT to Lariat Headlamp Upgrade | Page 9 | 2019+ Ford Ranger and Raptor Forum (5th Generation) - Ranger5G.com

 

[airline tech]

Yes, I saw the post #121 and then the one on using Allowed DRL Options (+Dedicated DRL) but when I did that it set 726-45-01 to a different code than Post #121. I was frustrated and dug into the As Built comparisons to see what they are actually supposed to be. Now I know that some will be doing drop in LED to their existing housings, so I added the screenshots to help them configure what they want before they are hooked up and rushing to get it done before the truck's battery dies. and not paying attention to the paragraph at the top of the Allowed DRL Options screen.
I would like to see these settings posted to the Spreadsheet, as this is the FIRST place I looked. The F-150 spreadsheet can throw you off too, not all of the codes will transfer to our ranger

 

[veedubtuner]

I thought the OEM LED headlights were Plug and Play? I watched a youtube vid where they guy swapped from factory halogens to factory LED and they worked fine.

 

[airline tech]

Plug and Play Yes- As far as Wiring Harness goes- In fact I referenced this Video when I swapped mine. It's a good video and he did a great job. The wiring harnesses are the same going to the headlights, which the wiring diagrams show (no difference) but the headlight assembly itself is pinned differently (internally) and you need to configure the BCM to acknowledge that the Leds are installed.

The wiring diagrams only show the harness side, they do not show the internal difference of the headlight assemblies see attached PDF below of the headlamp connector
The BCM needs to be programed to adjust power output between pin 5, pin 6 and pin 7.

So, the term - plug and play - is only partially correct

My DRLs (LED Strips) did not function until the ForScan Changes, due to the fact that the BCM still thinks the headlights are halo's and is suppling power to the Low Beam for the DRL Function (internally within the headlight assembly)
Some may have them work correctly - (IDK), but the BCM does not change itself automatically

Operational Difference Between the Assemblies:

Headlight Function:
As far as headlight function itself (High and Low Beam) - They function the same, just the different way of providing the light. Led uses a Single light source with a shutter that switches between Lo and High Beam vs using separate bulb's (Low and High) in the Halos

Parking Light:
Halo's use the Parking Light (7444NA-Amber) as dual purpose - Park and Turn and also dims and brightens. (Dual Filament) - It is also on Dim with the Low Beam (DRL)

LED: Uses the same bulb (dual filament) (7444NA-Amber) but is only wired for (1) function - Turn Signal and no function at all for Park Light, so it has no dimming function (only bright-for turn signal)
The Parking Light function is now moved to the LED (DRL) Strip-(Dimmed)

DRL;
Halo's: Use Low beam portion of the headlight and parking light (7444NA-Amber)- Dimmed

LEDs: Use the LED Strip as DRL - It is Bright as (DRL) and DIM as (Parking Light) - White, No Amber Color-with the LED Strip

Just a FYI:
Anytime you use ForScan- all you are doing is providing a Power and Ground for the outcome you are seeking - (say the popular Bambi-Mode) you are allowing a Ground for the Fog Lights when the (High Beams) are on, when in normal operation (Factory) the Ground is broken (taken away) and they turn off, even though the switch is on


Hope this Helps - understanding the difference

 

[jprime84]

Just made an account to say thanks and bump this thread as I googled my way to it (and others mentioned here) ultimately to success on my XLT upgrade to OEM lariat lights.

 

[jprime84]

Well shoot, I might have celebrated early. Did a long drive today, and noticed my DRLs were off in the reflection of the car in front even though I was in auto headlight mode. I disabled and renabled them in the vehicle settings while driving, and they came on again. However, within 5 minutes they were off again.

I couldn’t find a pattern to it. I would reset them and sometimes they would turn back off in seconds, other times they would turn off 10 minutes later. Once, i am pretty sure that one side turned off for a while and then the other side did later.

forscan changes I made were to the DRL allow modes (set to dedicated) and then the drl mode itself to dedicated. Ill pull the hex values tomorrow. Anyone else seen this?

Edit:

Found this from the system operation document

Is there a setting somewhere to change the voltage going from halogens to LEDs on the drls?

 

[airline tech]

The settings need to be exactly as I posted - or you will get errors - it appears that you have DRL set to the low beams still and they are auto turning off

 

[jprime84]

The settings need to be exactly as I posted - or you will get errors - it appears that you have DRL set to the low beams still and they are auto turning off

I thought that I had done that, but I used the easy mode instead of the direct input. Ill try that today.

 

[jprime84]

For completeness, here is the DTC I ran into:

Codes set after I had done the above in the easy mode (or me screwing up, either way):

This time, I set the values manually in the direct entry screen to the values OP shared in the first post. Function tests are good, but then again they were as well before just sitting in the driveway. I'll take it for a spin later and see whats what. Time for work now though.

 

[airline tech]

It's not in this thread but some have stated they had to (easy mode) set the Allowed DRL Options first then set the DRL Configuration, either way in the (Allowed DRL Options, you need to see
this:
I know it's an odd verbiage to see, but the Hex Code is what is important, and this line puts the hex code to match factory settings. This is the one that screws owners up, as this is (+) addition to factory DRL and they select (+) Dedicated DRL here, so with that selected here you are creating a BCM error code.

Plus, just a FYI, if you put truck in neutral (SET PARKING BRAKE) you can check full operation from your driveway. The DRL's operate in any gear except park and Auto Headlights are not activated by low light conditions - ***Unless you have Canada Version where DRL's are mandated to be on all the time.


and DRL Configuration needs set to this:

If this does not work, then set them manually to this:

BCM
726-26-02 - 0000-0001-0056 (Matches my Lariat compare search-As-Built)
726-45-01 - 0A01-1000-008E (Matches my Lariat compare search-As-Built)


This one should change Automatically with the above (2) changed as this is just a checksum code generated by the above (2) settings.

726-50-01 - 108E (Matches my Lariat compare search - As-Built)

Hopefully this clears it up for you.

 

[veedubtuner]

I swapped my lights almost as soon as I got the truck, seem to be working fine (no weird CEL's) but then again I don't see them from the outside when I'm driving lol. Few times I've used the headlights they seem fine (and properly adjusted surprisingly lol) and the DRL's come on when I unlock the truck and I get no hyper flash with the turns. I did just order the cable though from Amazon and I'll make the changes posted as I don't want any future issues.

 

[Trigganometry]

Thanks for this! I’m swapping out my halogens soon with the LED lariat lights. Should be a painless experience with what you have documented here! Appreciate it very much ?

 

[Big Blue]

If this does not work, then set them manually to this:

BCM
726-26-02 - 0000-0001-0056 (Matches my Lariat compare search-As-Built)
726-45-01 - 0A01-1000-008E (Matches my Lariat compare search-As-Built)


This one should change Automatically with the above (2) changed as this is just a checksum code generated by the above (2) settings.

726-50-01 - 108E (Matches my Lariat compare search - As-Built)

Just some info from a member that was making changes in FORSCAN before the easy configuration menus were a thing. In the As-Built HEX lines the last two characters in each line are the check-sums for that line and will update automatically. doesn't matter how many character in line, always last two. Also each as-built line may control multiple features. This is seen, if you dig into the F150 spreadsheet. Lastly the easy configuration menus will make required changes to multiple as-built HEX codes with one selection.

As far as the "Allowed DRL Options" selection. When I changed my '19 XLT to use my fog lights as DRLs, I simple changed that selection to "All Options" and have had no issues. As I do not have a Lariat I do not Know why it is set to the HEX value you found. Other than the HEX number 1000 is equivalent to the decimal 16. Other than being one more than 15 it does not appear to be a valid option in Forscan at least.

As far as the "10" in the as-built line 726-50-01, I have no idea what it does, but it evidentially needed to change for this to work.

You are correct the as-built values are the important ones as they are what is written back to the module. The configuration files are just there to make it easier to manipulate the as-built files.

Something I cannot stress enough, is anyone using Forscan should first make backups of all of their as-built files before making any changes. This makes it very easy to reverse any changes that do not work or are not to your liking. intermediate backups also help so you don't have to start from scratch if a later change doesn't work.

Sorry for the long post, but had to clear up the checksum issue. Good work on doing the as-built comparisons to hopefully put this issue to bed. trying to decipher the as-built file ahs driven a a few of us to drink for some time. still looking for what to change to increase the lane change flashes.

Sponsored