Lightning Software Updates using FDRS

[Mike G]

1 May 24 and there are three more updates in FDRS this morning.

BCM and the two door modules. This appears for both '22 and '23 MY trucks.

Mine also shows the FHCM from last week.

EDIT: I ran these this morning and started with the doors, then the FHCM and ended with the BCM.

The BCM software did update fine...but failed at the end step where the config is written back to the module. Don't know why...tried several times. Says there's an "exception writing to the module". Truck works fine, and at some point they'll figure out the config issue. Left with no DTCs at the end.

Post back if you have the same experience (or different?).

Sponsored

 

[Shadow2222]

Newbie here, going off some recommendations I’ve seen elsewhere while I wait for my name to come up in the mongoose lending order.

Will this power supply and these clips be sufficient for updates? If so, what voltage would I set the knob to? Sorry for the potentially silly question!

 

[rugedraw]

Newbie here, going off some recommendations I’ve seen elsewhere while I wait for my name to come up in the mongoose lending order.

Will this power supply and these clips be sufficient for updates? If so, what voltage would I set the knob to? Sorry for the potentially silly question!

Power supply for sure. 40amps is the minimum recommended for the EV's. As long as the red/black knobs on the PS can unscrew completely to allow the o-ring side of the clip to fit onto the terminals of the PS, I am inclined to say that it will work.

 

[Gimme_my_MME]

If you have not done the power train updates that are currently in FDRS, it is in your best interest to hold off for now

 

[sstevetx]

1 May 24 and there are three more updates in FDRS this morning.

BCM and the two door modules. This appears for both '22 and '23 MY trucks.

Mine also shows the FHCM from last week.

EDIT: I ran these this morning and started with the doors, then the FHCM and ended with the BCM.

The BCM software did update fine...but failed at the end step where the config is written back to the module. Don't know why...tried several times. Says there's an "exception writing to the module". Truck works fine, and at some point they'll figure out the config issue. Left with no DTCs at the end.

Post back if you have the same experience (or different?).

Same modules, but I started with the BCM and got the error at the end writing to the config. Tried a few more times with same result. BCM was still in the list at this point. Tried a PMI saying "No" to original module and it failed. Closed out FDRS, disconnected mongoose and disconnected the LVB for a minute. Reconnected it, plugged mongoose in and started FDRS. BCM was no longer in my updates and I tried several network refreshes just to make sure. I first did a BCM PMI and forgot to say no to the original module, but it was successful. I then did it again saying "no" to original and it was successful. I then did the DDM, PDM and ended with the FHCM.

I still have those SOBDM/SOBDMC DTCs I mentioned before from the last powertrain update, but they aren't causing any issues. I don't have any DTCs besides these 2.

 

[artificial_airspeed]

I updated my 2022 Lariat SR about 2 weeks ago, applied every update in FDRS. During the IPMA update (very lengthy) I had an error and ended up having to PMI the IPMA (which I think also includes PMI for other associated modules in that process?)…..

Long story short - my Controls Tab which contains Drive Modes, 1 Pedal toggle, etc. no longer displays in Sync 4a menus.

Anyone have any ideas I could try to recover?

 

[rugedraw]

I updated my 2022 Lariat SR about 2 weeks ago, applied every update in FDRS. During the IPMA update (very lengthy) I had an error and ended up having to PMI the IPMA (which I think also includes PMI for other associated modules in that process?)…..

Long story short - my Controls Tab which contains Drive Modes, 1 Pedal toggle, etc. no longer displays in Sync 4a menus.

Anyone have any ideas I could try to recover?

Going through the vehicle history of when you did the updates, I do not see successful PMI of the IPMA was completed. The last time you tried the PMI, it said:

Procedure Unsuccesful - WriteDirectConfig Exception writing configuration to module

It seems like the update went through because it does not show you have an IPMA update pending, but it failed to write the config properly. I don't want to say a config procedure on both the IPMA and APIM would 100% work, but that is where I would start.

 

[Mike G]

Same modules, but I started with the BCM and got the error at the end writing to the config. Tried a few more times with same result. BCM was still in the list at this point. Tried a PMI saying "No" to original module and it failed. Closed out FDRS, disconnected mongoose and disconnected the LVB for a minute. Reconnected it, plugged mongoose in and started FDRS. BCM was no longer in my updates and I tried several network refreshes just to make sure. I first did a BCM PMI and forgot to say no to the original module, but it was successful. I then did it again saying "no" to original and it was successful. I then did the DDM, PDM and ended with the FHCM.

I still have those SOBDM/SOBDMC DTCs I mentioned before from the last powertrain update, but they aren't causing any issues. I don't have any DTCs besides these 2.

Thank you Steve this is very helpful.

I will go back out and reconnect and do a network scan.

After I did the updates I was advised that a server backend issue might have been what caused this issue. And apparently after it got tweaked the problem no longer exists.

Does Walk Away Lock work on your truck now...even though you don't have the menu toggle in Sync to turn it on and off? It does for me and @ChrisCon.

 

[sstevetx]

Does Walk Away Lock work on your truck now...even though you don't have the menu toggle in Sync to turn it on and off? It does for me and @ChrisCon.

I just tested and walk away lock works on mine too. I verified that I don't have a menu toggle for it under the vehicle config section.

 

[Mike G]

I just tested and walk away lock works on mine too. I verified that I don't have a menu toggle for it under the vehicle config section.

Menu toggle will arrive with the new Sync 1122 when it shows up.

 

[bmwhitetx]

I just tested and walk away lock works on mine too. I verified that I don't have a menu toggle for it under the vehicle config section.

Wait. You guys are getting walk away lock? But no Sync toggle? Did you see in the ICE forum where they are using FORScan to get the toggle?
https://www.f150gen14.com/forum/thr...atabase-spreadsheet.1578/page-205#post-453963
It only works for the 24’s. Not working for earlier because they need the BCM update which it sounds like you have.
Would be curious if you made the changes if you would also get the toggle.

 

[sstevetx]

Wait. You guys are getting walk away lock? But no Sync toggle? Did you see in the ICE forum where they are using FORScan to get the toggle?
https://www.f150gen14.com/forum/thr...atabase-spreadsheet.1578/page-205#post-453963
It only works for the 24’s. Not working for earlier because they need the BCM update which it sounds like you have.
Would be curious if you made the changes if you would also get the toggle.

I checked ForScan for the walkaway lock settings and I don't have a 726-89-02 under BCM. I do have the 726-90-01, but I didn't change it. I did however try changing the "8" bit only in the 7D0-09-05 APIM setting. I figured the BCM is already set since it works. The APIM change ONLY made the setting show up for me. I tested it and it still worked. I changed to disabled and it no longer locked on walk away. Changed it back to enabled and walk away works. cc @Mike G

All the Forscan values in my screenshots are stock for my 22 Lariat after the latest BCM update in FDRS.

From thread link you provided:

Walk Away Lock can be enabled on 2024s only with the following and it's been added to the Common spreadsheet:

BCM 726-89-02 x1x1 x1x1 x1--
BCM 726-90-01 xxx1 xxxx xx--
APIM 7D0-09-05 xxxx 8xxx xx--

Optional - You can also turn on Audible Lock feedback for Walk Away Lock with these:
BCM 726-89-01 x1x1 x1x1 x1--
BCM 726-90-01 x*xx xxxx xx--
APIM 7D0-09-05 xxxx Cxxx xx--

 

[artificial_airspeed]

Going through the vehicle history of when you did the updates, I do not see successful PMI of the IPMA was completed. The last time you tried the PMI, it said:

Procedure Unsuccesful - WriteDirectConfig Exception writing configuration to module

It seems like the update went through because it does not show you have an IPMA update pending, but it failed to write the config properly. I don't want to say a config procedure on both the IPMA and APIM would 100% work, but that is where I would start.

Hey rugedraw, I didn’t want to bug you with a PM but thanks for reading and the suggestion. I will give that a shot.

 

[Mike G]

 

[jlcreasy]

I've newly jumped into the FDRS pond.... Has anyone had issues with FDRS bringing up the Ford Login screen using the Independant Operator/Non-Dealer option? It works on my Win11 desktop but not on my Win11 laptop (freshly loaded OS). When I click login on FDRS I get a dialog box saying Cannot reach FDRS servers....

Sponsored