The answer is: It depends.

Did you make FORScan changes in the same module that is being updated? If so, then the answer is: Yes, it is a possibility that your FORScan changes can be overwritten. Further, there have been a few cases in the past where users were advised to revert their FORScan changes BEFORE applying an update (manually, with FDRS), but this is typically not necessary.

Bottom line, you should be keeping a log with all the FORScan changes you've made. I keep a copy of the spreadsheet locally. If I make a change, I log the date I made the change, as well as the old value and the value I change it to, on the same line in the spreadsheet. When the spreadsheet is updated, I transfer my old/new changes to the new spreadsheet (although I keep the old one, too).

 

Months/years of people complaining that they are not getting updates has not turned into people complaining that the are getting them.

Oh, how times change ...

 

I think this depends on several factors that we may not even be aware of them all. I was told that if a foreskin change has been made for a long enough period of time since the vehicle talks back-and-forth to Ford that for scan changes would become your as built making it more important to save your original as built.
If this is the case, then when you do an update, may think the changes are your current as built. They may save a copy of all your information on the module before they write over with the update and only the areas they need to change.
I updated damn near every module in my 23 using FDRS.. PCM, APIM, DSP, FACM, IPC, SCCM, airbag, module, power steering control module, ABS… etc.

And none of my forscan changes were affected. I had all of the common foreskin changes, including temperatures on the gauges, fog with highbeam, disable double horn honk.. etc. Even the Active matrix headlights are enabled didn’t change.

 

This has been my experience as well. I suppose if you made a change and received an update soon after it may revert back but like stated these changes sync back to the Ford server and are incorporated into your as-builts in the Ford system. I have never had one overwritten with updates. As you make changes you can verify the changes have synced back here, https://www.motorcraftservice.com/AsBuilt.

 

Your truck is on Sync 23159 which is only one version behind the latest and you received a BCM update recently. You are a bit behind, but nothing to worry about, imo.

 

FORScan changes will eventually become your new as-built data once the truck syncs up with the server or a network scan is done with FDRS. There is no set time frame as to how often a truck syncs up, so if you made APIM changes today and get an APIM update tomorrow, chances are the FORScan changes will get wiped.

 

Thanks. Is there a way to shut off the modem so it can’t update?

 

I wouldn't do that. If you don't want it to auto update, then just disable the auto update in Sync.

 

Gosh dang it. Another software update fail.

Maybe I didn't drive my truck enough this week for the battery. You would have thought with all the running around it would have been healthy.....

 

Since I updated everything a couple months ago with FDRS the only updates I’ve gotten are updates to make the truck receive updates easier. lol