F150 Lightning FORScan thread - Version 2

[B177y]

So my truck has been at the dealer for three full days to try to fix the Apple play issue that I’ve been having as well as trying to fix the fact that I have not had an OTA since October. I’ve had it in there twice and they have told me they have updated the modules each time. They finally called me and told me that it’s taken three days because they had to work with the mothership.

I was wondering if anybody out there could check to see if I have all the updates if I provide my VIN I don’t have that ability and would like to know before I head to the dealer to get my truck. I would really appreciate any help anybody could give.

You may want to check this thread:
FDRS/PTS VIN check

Sponsored

 

[bmwhitetx]

BCM 726-42-01 x2x2 xxxx xx--
BCM 726-38-01 xxxx 64xx xx--
example values are 64 =100%, 4B =75%, 32 = 50%, 19 = 25%, 0A =10% (default).

2024 Lariat, it appears my truck defaults to 100% brightness and the 726-42-01 was also set with the x2x2 value. I tried changing the value to 10% and noticed no change on the DRL.

You might double-check your values or you bought a used truck that someone modified. I have As-Built data on over (80) 2022-2025 Lightnings of all trim levels and every one of them has:
BCM 726-42-01 x0x0 xxxx xx--
BCM 726-38-01 xxxx 0Axx xx--

EDIT: Hold on, you were asking about this last year - sure you didn't change your values then and forgot?

 

[bmwhitetx]

I love that you have a ton of as-built files. Do you have them on a git hub or anything similar? Members smarter than I could possibly make some fancy programs against that data.

Not a database per se. I have the .ab files and window stickers that I have slowly accumulated. I then built an Excel spreadsheet where I can enter any parameters I want (with the highlighted byte/nibble) and a macro loops through all the As-Builts (plus a few ICE) and shows me the values.

Here is a sample:

(VIN column clipped to mask VINs)

I've built databases in Access, SQL, SAS, etc. in my career but for things like this I still love Excel and VBA. Quick and easy.

 

[SNBI18]

You might double-check your values or you bought a used truck that someone modified. I have As-Built data on over (80) 2022-2025 Lightnings of all trim levels and every one of them has:
BCM 726-42-01 x0x0 xxxx xx--
BCM 726-38-01 xxxx 0Axx xx--

EDIT: Hold on, you were asking about this last year - sure you didn't change your values then and forgot?

Your right! So I did the Lightbar mod last year which did nothing visually. It's been a while since I visited here and saw the DRL mod on page 1 thinking it was something different.

 

[bmwhitetx]

I'm think more along the lines of data analysis AI models and big data tools. With all the cross-dependencies in the as-built files there would need to be a lot of cross checking for changes in one area to changes in others.

In truth you may need a listing of options and features for each vin to have that make more sense.

I wonder if the motorcraft site would allow bulk scraping.

One issue is that a VIN itself carries very little info other than model year and battery size. Options like MaxTow, TowTech are not there AFAIK. So the labor-some part is getting a window sticker and checking Order Guides to reveal features. I do note the major options (or deletes) in my description field. Have thought about separating the major options out but haven't needed to.

So far my system is doing great answering the questions I'm asking. My foremost reason is making sure when someone posts a FORScan mod that it makes sense with our truck's As-Builts.

Too many examples of folks blindly applying ICE mods or mods for another trim and messing up other options.

I've developed another spreadsheet where I can view the software version (with year) of all the modules for each truck. It does appear the 2025's have a few new things but I need to look into that more. I'm especially interested in the IPMA and APIM - could indicate whether we could support BC 1.5 although I suspect @rugedraw has already figured it out!

I need some of our new 2025 owners to try FORScan.

 

[rugedraw]

One issue is that a VIN itself carries very little info other than model year and battery size. Options like MaxTow, TowTech are not there AFAIK. So the labor-some part is getting a window sticker and checking Order Guides to reveal features. I do note the major options (or deletes) in my description field. Have thought about separating the major options out but haven't needed to.

So far my system is doing great answering the questions I'm asking. My foremost reason is making sure when someone posts a FORScan mod that it makes sense with our truck's As-Builts.

Too many examples of folks blindly applying ICE mods or mods for another trim and messing up other options.

I've developed another spreadsheet where I can view the software version (with year) of all the modules for each truck. It does appear the 2025's have a few new things but I need to look into that more. I'm especially interested in the IPMA and APIM - could indicate whether we could support BC 1.5 although I suspect @rugedraw has already figured it out!

I need some of our new 2025 owners to try FORScan.

When the latest BBC IPMA software first showed up in FDRS for 2021 ICE trucks in September, we were very excited to find files in it with 2026 part numbers. The real gurus suspected it was 1.5 because the ACJ IPMA software we had prior to that was supposed to be 1.4 based on the few known Mach E's that got the 1.4 OTA. So they tried to enable auto lane change with it, but it didn't work.

Once the OTA for BC 1.4 was rolled out in December, we knew BBC was the official 1.4 release.

BC 1.5 will require newer IPMA software and/or GWM software to allow it to work. An APIM update may be needed to add a button to the touchscreen for it to be turned on and off, but I don't think we need an APIM update for it to actually work.

My truck already harasses me to let me know a lane change is available when the vehicle in front of me is going slower than I am, so we can't be that far away from it.

 

[bmwhitetx]

Your right! So I did the Lightbar mod last year which did nothing visually. It's been a while since I visited here and saw the DRL mod on page 1 thinking it was something different.

So between last year and now, I added a note to clarify that mod is not about the light bar. Instead the mod changes the DRL's shown here. You probably should change them back to 10%. Folks found that it looks like you have your brights on all the time and other drivers will flash you.

 

[astrand1]

Hey all. So question. 23 lariat ER. I asked before and I’ve also checked my work. But I still don’t have the bed cam when moving over 8mph. Wondering if anyone else has this issue. On my 22 PB it worked at any speed. Also this is an odd ball question. Living in MI we go over to Canada fairly often. In the aforementioned 22 PB my cluster would ask if I wanted to change to KPH once we crossed into Canada. I’ve noticed that the lightning does not ask and it does not have a setting in the cluster to get that prompt. Any thoughts?

 

[Scorpio3d]

Welcome to the forum - I see DFW for the location- there are quite a few of us here on the forum from the area..

Ditto!

We’re taking over this mother…???

 

[GoodSam]

don’t have the bed cam when moving over 8mph

My 2022 XLT bed cam works at any speed, if it is not in blue screen fail mode which happens too often along with Ford Nav location fail (currently my truck shows its location in the ocean).

 

[astrand1]

My 2022 XLT bed cam works at any speed, if it is not in blue screen fail mode which happens too often along with Ford Nav location fail (currently my truck shows its location in the ocean).

Nope it’s not that. Works just fine when stopped or slow speed. Fortunately I’ve not had either issue. The button is there but does not do anything at speed. I know it’s just a setting that needs to be changed in forscan was hoping someone might have an idea.

 

[Henry Ford]

Hey all. So question. 23 lariat ER. I asked before and I’ve also checked my work. But I still don’t have the bed cam when moving over 8mph. Wondering if anyone else has this issue. On my 22 PB it worked at any speed. Also this is an odd ball question. Living in MI we go over to Canada fairly often. In the aforementioned 22 PB my cluster would ask if I wanted to change to KPH once we crossed into Canada. I’ve noticed that the lightning does not ask and it does not have a setting in the cluster to get that prompt. Any thoughts?

In the APIM easy mode search for "speed" or "at speed." It will bring up all the cameras with options to work at speed. You should be able to see if the option was turned off for the bed camera.

 

[bmwhitetx]

Nope it’s not that. Works just fine when stopped or slow speed. Fortunately I’ve not had either issue. The button is there but does not do anything at speed. I know it’s just a setting that needs to be changed in forscan was hoping someone might have an idea.

From post 1, reapply black box fix, even though you may not have black box.

Remove "Full view not available" message on reverse camera screen while in motion (source)
APIM 7D0-02-02 xxx* xxxx xx-- If 0 change to 1, if 2change to 3, if 4 change to 5, if 6 change to 7.
Note: reset APIM after the change. See this post for how to reset a module.

Enable cameras at speed - if you have lost the ability to see the bed camera while driving, try doing the Remove "Full view not available" message mod above.

 

[rugedraw]

Nope it’s not that. Works just fine when stopped or slow speed. Fortunately I’ve not had either issue. The button is there but does not do anything at speed. I know it’s just a setting that needs to be changed in forscan was hoping someone might have an idea.

IPMA

706-02-02

xxxF CExx xx--

Edit: Btw, I think the changes I sent you to enable BC 1.4 a while back ago contained an error. While you're in there, check this setting in the APIM and if it is a 4, change it to an E:

7D0-09-05

xxxx xxEx xx--

 

[bmwhitetx]

IPMA
706-02-02
xxxF CExx xx--

Hey Javier, when I look at my As-Built database, all 22-23 Lightnings (except certain Pros) already have xxxF CExx xx-- (but @astrand1 should confirm his still has that).

But the 24's and 25's have xxxF CAxx xx-- (except certain Pros)
The difference between A and E is something called FeatureCfg_DPAC_OffRoadOverlay (FCDPACORO). It's disabled in the 24 and 25's ("A").

Is the intent of your change above just to flip FeatureCfg_DPAC_ViewCtlAtSpeed (FCDPACVCAS) to Enabled?

Alex - let us know what your before values were for IPMA and APIM.

Sponsored