So, remember this axiom when making FORSCAN changes.
1) Check your current and change to values twice. Write them down with a paper and pen, or if you’re too cool for that, use your notes app. TYPE it, don’t dictate it and VERIFY IT.
2) while you’re making the change, and in FORSCAN, verify the current values are correct to what you noted previously. If not, stop, return to the beginning and start over.
3) if the values were correct, change 1 AND ONLY 1 feature at a time, start to finish.
4) VALIDATE FUNCTION after the key/ignition cycle. Revert if it didn’t work.
5) If you got this far and things are Fùcked up, blame Noah at
@The Car Stereo Company
now. I’m not sure where it is now, but the “as built” data by VIN used to be on etis.ford.com - we’ll need someone more currently versed in Forscan to help with the current location of the as built data. My last FORSCAN updates were...4+ years ago.
I do know that backups are One module at a time. Not just one big backup, you have to backup each individual module one by one. It’s time consuming, about an hour all in, but, if you go in without a backup, this outcome is a distinct possibility.
Have you checked the
https://www.fordraptorforum.com/threads/forscan-changes-tweak-your-truck.52149/ thread, recent posts for info on the “as built” data?