airline tech
Well-Known Member
- Joined
- Aug 24, 2022
- Threads
- 28
- Messages
- 4,458
- Reaction score
- 8,520
- Location
- Midwest - KS
- Vehicle(s)
- 2022 Ranger Lariat-Super Crew, Cactus Gray
- Occupation
- Aircraft Tech
- Thread starter
- #16
It was my understanding that it was the last 4, but after checking it is only the last 2. But I'm still learning.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.![]()
I just was noting that the that Hex Line should change automatically and should not have to be manually altered. (726-50-01)
The above settings are to set it to Factory (As-Built) for the trucks that came with LED headlamps and you are swapping from Halo to Factory LED. I am not (100%) positive that these settings work for all aftermarket, since aftermarket uses different forms of lighting on the DRL's, they are all not an exact copy of factory. Plus, the settings are (NOT) including any (ADD) to the DRL LED strip.
Since I switched from Halo to LED, this DRL Option screen may still be altered to use a different setting, so for owners that still have Halo's and want to (ADD) an extra lighting option to the factory (Lo-Beam) such as Fogs
or
Factory LED and want to (ADD) extra lighting to the factory LED strip
and the current poster (JPrime84) has both lines set to (Dedicated DRL), this is what is generating a BCM trouble code, and by changing the DRL option to (Incorrect Value or Not Configured) he will be telling the truck that there is not any (Addition) additional lighting he wants to include with the DRL strip. The important words in that are (Not Configured), now if he wants to add Fogs etc, this is where to do it.
The problems arise when other owners have swapped to aftermarket headlamp housings and have an extra wire harness tapped into the factory harness, sorry can't remember the brand that does this, then you have to play with the settings some to find the correct setting that the truck likes. (I think it was Alpha Rex) or similar to that.
Sponsored
. I feel like a dumb ass, wasted about an hour of my time yesterday double checking everything lol
.