Successful FORScan mods for a 2019 Expedition Platinum

[Mr Big]

I just bought a '23 Max Ltd w/ Sync4a (giant screen). I'm desperate to mod some of the factory settings like increasing turn signal change lane flashes to 5, add temps on engine and transmission gauges, turn off seat belt dinging, etc.
First, where were are the drop downs located?
Second, is there a spreadsheet of other possible code changes?
Thanks for your help!

I've not seen whether FORScan works with 2023 Expeditions. I suggest make a backup of your settings before attempting to perform any mods.

 

[GTE-CUP]

I just bought a '23 Max Ltd w/ Sync4a (giant screen). I'm desperate to mod some of the factory settings like increasing turn signal change lane flashes to 5, add temps on engine and transmission gauges, turn off seat belt dinging, etc.
First, where were are the drop downs located?
Second, is there a spreadsheet of other possible code changes?
Thanks for your help!

Were you able to get any codes or a spread sheet on the possible changes for a 23?

 

[Mr Big]

Were you able to get any codes or a spread sheet on the possible changes for a 23?

Many people complain that 2023 Ford models Forscan codes don't work well. So best advice is perform a backup before trying any modifications in case it causes issues. I do see some videos on Youtube that pertains to 2023 super duty, bronco, explorer, etc.

 

[GTE-CUP]

Many people complain that 2023 Ford models Forscan codes don't work well. So best advice is perform a backup before trying any modifications in case it causes issues. I do see some videos on Youtube that pertains to 2023 super duty, bronco, explorer, etc.

So i was able to pull up Forscan on a 2023 Expedition and saw a lot of common options to change just as a way to see what was in the database.
I ended up talking in person later to a ford tech at a dealership and he noted on 2023 and up Expeditions that alterations in Forscan could/have cause(d) the module to become bricked if the FRDS scanned the system. Something along the lines that the FRDS sees the modified value as a corrupt memory location from the factory default. The result would be to remove and replace the dead unit. Not sure why that would result in killing the module.
Is this just misinformation or something I should be concerned about? He also noted that backing up to the asbuilt condition prior to scanning would not cause problems.

 

[Mr Big]

So i was able to pull up Forscan on a 2023 Expedition and saw a lot of common options to change just as a way to see what was in the database.
I ended up talking in person later to a ford tech at a dealership and he noted on 2023 and up Expeditions that alterations in Forscan could/have cause(d) the module to become bricked if the FRDS scanned the system. Something along the lines that the FRDS sees the modified value as a corrupt memory location from the factory default. The result would be to remove and replace the dead unit. Not sure why that would result in killing the module.
Is this just misinformation or something I should be concerned about? He also noted that backing up to the asbuilt condition prior to scanning would not cause problems.

Forscan has a disclaimer stating possible damage, just like many types of software.
As with any programming, whether it's software or firmware, there is always a possibility of causing a malfunction, ending in bricking a device.
I have many years of experience with firmware/software programming and modifications, and have never run into any issues that caused permanent bricking of a device. I "always" perform a complete backup before changing anything in Forscan.

You can find many sources to help you find what works and what doesn't. There are also several .pdf and .xls files available. In the past F-150, 250, super duty sheets are very similar for the respective year of Expedition. I use AS BUILT format whenever available.
From Forscan: "FORScan may support a limited set of functions and configuration parameters for brand new 2021-2025MY models (we work on it)."

 

[GTE-CUP]

Forscan has a disclaimer stating possible damage, just like many types of software.
As with any programming, whether it's software or firmware, there is always a possibility of causing a malfunction, ending in bricking a device.
I have many years of experience with firmware/software programming and modifications, and have never run into any issues that caused permanent bricking of a device. I "always" perform a complete backup before changing anything in Forscan.

You can find many sources to help you find what works and what doesn't. There are also several .pdf and .xls files available. In the past F-150, 250, super duty sheets are very similar for the respective year of Expedition. I use AS BUILT format whenever available.
From Forscan: "FORScan may support a limited set of functions and configuration parameters for brand new 2021-2025MY models (we work on it)."

Just to clarify the claim is that the bricking occurs due to the service tech scanning the FW/SW modified module with FRDS. Something about the service software/FRDS attempting to automatically change or read a previously modified value results in lock/loop/brick. Statment was also aimed that the FW/SW in 2023 and up Exp were different than F150 or older Exp.

 

[Mr Big]

Just to clarify the claim is that the bricking occurs due to the service tech scanning the FW/SW modified module with FRDS. Something about the service software/FRDS attempting to automatically change or read a previously modified value results in lock/loop/brick. Statment was also aimed that the FW/SW in 2023 and up Exp were different than F150 or older Exp.

I'm not sure what you mean about the claim? However, I just took my Ex in for a PCM recall. They flashed the PCM module with new software, using whatever software they use to program firmware and software updates. I didn't lose any settings and their update did not affect my system at all, or any of my FORScan mods, as they were all still there. What I was mentioning is, if one performs any adding, updating, modifying, or hacking, of any device, there is always a risk. I have used FORScan, Fmods, and CyanLabs, and never had any issues. The issues happen when a user does not follow the directions 100%, hence the software disclaimers.