Forscan New User Best Practices

Modman

Moderator 🛠️
Staff member
Founding Member
Joined
Jun 25, 2021
Messages
7,669
Reaction Points
14,837
Location
SE Michigan
Current Ride
22MY F250 Star White Lariat Tremor
Current Ride #2
22MY Winnebago Voyage 2831RB
Happy New Year Forscan users!

I have started to compile a “Best Practices” summary to help with the repeat questions I (and probably others) have received. This is intended to be neither a full tutorial on Forscan nor instructions for any specific changes as there are plenty of other good references already in existence. My hope is that by documenting this it provides some basic guidance to new users and a consistent post to refer back to as people receive their vehicles and want to make updates. I am open to input if there are items I missed that would be helpful and will edit this post accordingly (@ccw @MiTremor906 @SomethingRandom @BroncoHooves @PapaRaptor )
  1. Preparation: Before you even take possession of your truck there are things you can do to get ahead of the game and set yourself up for success. These will also serve as good reference tools ongoing if you encounter issues or have questions:
    1. Once you have a VIN and your vehicle is in production you can access the “As-Built” data from your control modules (more detail on this below). Go to https://www.motorcraftservice.com/AsBuilt and enter your VIN
      1. The data listed for your vehicle should be copied and saved as a backup just in case!
      2. Highlight the entire page starting with “Module” at the top and ending with “End of information” at the bottom
      3. Ctrl-C to copy
      4. I pasted mine into Excel and selected “Keep Source Formatting” it will look like this, but will be ~835 rows of data.
        1641328411367.png
    2. Download and take a look at the various summary spreadsheets available:
      1. 2022 SuperDuty - https://www.fordtremor.com/threads/forscan-for-2022.5886/
        1. Specific to the changes for this model year, but not fully populated yet
      2. 2020-21 SuperDuty - https://www.forscan.org/forum/viewtopic.php?t=13978
        1. USE WITH CAUTION FOR 22MY - Good reference as many changes are common for the 22MY SD
      3. 2021 F150 - https://docs.google.com/spreadsheet...Nwyqu5v3dgpbluvJcezUItTSVI/edit#gid=364824617
        1. USE WITH CAUTION FOR 22MY – Good reference as many changes are common for SYNC4 and not yet mapped for the 22MY SD
    3. There are many online resources to look at while you are waiting:
      1. https://forscan.org/ – Good forum for tutorials, answers to many common questions, also where you access/download the software…
      2. Our own Tremor forum has specific threads for 2020, 2021, and 2022 model years
      3. Ford Truck Enthusiasts can also be very helpful: https://www.ford-trucks.com/forums/1668884-2022-forscan.html
      4. YouTube
  2. Hardware: You will need two things to execute your dream electronic customization of your truck. A laptop and an OBDII interface adapter.
    1. Laptop. I use an PC laptop that is probably ~7yrs old but works just fine for this purpose. I updated to Windows 10 but otherwise the specs can be found here if you would like to compare: https://specspro.net/laptops/1250-toshiba-satellite-c55-a5302/
    2. Adapter. Don’t mess around here and I do not recommend getting one with a Bluetooth interface – wired is the way to go 🔌. This is the one recommended by Forscan.org and the one I purchased: https://www.obdlink.com/products/obdlink-ex/?ref=forscan (can also be purchased on Amazon…)
  3. Software: Pretty straightforward, but I thought it was worth mentioning…
    1. https://forscan.org/
    2. I recommend purchasing the extended license as it helps to support the developers of this fine product!
    3. Check for updates and always run the latest version! This is very important for model years with significant changes like 2022. There has been much improvement from the initial to the current release for our trucks.
  4. Practice: “Practice does not make perfect, only perfect practice makes perfect” - Vince Lombardi. In this case it helps to just do some trial runs and get familiar with things.
    1. Once you have your laptop, adapter, and truck (obviously):
      1. Connect everything up and update/download any drivers (should happen automatically)
      2. Get familiar with the interface and the key sections in the software
      3. Open up some modules and look at what is there without changing anything
    2. Some modules have two distinct ways to access the settings:
      1. “As-Built” which is the same hexadecimal memory address and settings shown on the Motorcraft site
      2. “Plain English” which is more conversational – disable, enable, etc
      3. Not all modules have both. If there is a Plain English version changing this will also change the As-Built
      4. More detail available in my post here: https://www.fordtremor.com/threads/forscan-for-2022.5886/post-168312
  5. Documentation:
    1. Use the Motorcraft As-Built info to your advantage:
      1. The data listed for your VIN should be copied and saved as a backup just in case! (I just got Déjà vu writing this. I wonder why, hmmm… 🤔)
      2. Copying to Excel (or any other program of your choice) allows you to save the initial data, and use it to keep track of any changes you make, like this:
        1641328874073.png
    2. Document what you change.
      1. Hand written, Excel, take a picture, whatever works for you
      2. I have used all methods – just use at least one of them, please! 🙏
    3. Backup in Forscan:
      1. Save a module BEFORE you make any changes and then save a copy with a different name AFTER you make changes.
      2. If you are proactive you can makes copies of the most used modules before you start: Body, IPC, APIM
  6. Other Thoughts:
    1. Backup, backup, backup your data. If your are not sure, back it up again!
    2. Early in a model year the Plain English domain may or may not work as intended. It gets more accurate over time with each updated Forscan release.
    3. When working in the As-Built module, do not take the entire memory address from someone else's truck without understanding the potential unintended consequences. The settings in a single memory address can (and most of the time do) control multiple functions.
    4. When in doubt, ask. There are lots of people willing to help on this forum or others. Most questions can be answered quickly before an issue is created and you enter into “what did I just do” mode 🙀
 
Last edited:
I'll add that if you have a Mac, you can download VirtualBox for free and an evaluation copy of Windows. However, you might save alot of frustration by just buying a cheap Windows laptop just for Forscan. VirtualBox updates and graphics windows can be problematic on Mac, let alone passing the OBDLink USB device on through from the Mac into VirtualBox.

I have a Mac and it's a delicate balancing act every time there's a VirtualBox update. For how infrequently I need Forscan, it works for me.

Also disappointing how the lifetime Forscan license is no longer sold. We need to get them to bring that back out @Modman
 
I'll add that if you have a Mac, you can download VirtualBox for free and an evaluation copy of Windows. However, you might save alot of frustration by just buying a cheap Windows laptop just for Forscan. VirtualBox updates and graphics windows can be problematic on Mac, let alone passing the OBDLink USB device on through from the Mac into VirtualBox.

I have a Mac and it's a delicate balancing act every time there's a VirtualBox update. For how infrequently I need Forscan, it works for me.

Also disappointing how the lifetime Forscan license is no longer sold. We need to get them to bring that back out.
My Tremor is too snobby for a PC - She only allows a Mac to touch her. Well, a Mac, and her Mac Daddy! Haha
 
@Modman 👍well done. My tidbits to add:

1) back up the modules before you make any changes
2) back up everything
3) some od your trucks addresses won't show up on the motorcraft website. (This is a big reason to backup items. We learned this with troubleshooting your heated steering wheel. My truck had additional addresses in forscan that didn't show up on the website.)
4) I'd also recommend watching some YouTube videos of other people changing things to help get familiar with it. Good to do before you get the truck and again right before you dive into it.
5) also don't recommend the Bluetooth adapters but they are handy to check fault codes and can use your phone but only as viewing faults and not changes to forscan.
6) forscan isn't as scary as it sounds and if you follow the above recommendations you will be fine.
7-10) back up everything.
 
Happy New Year Forscan users!

I have started to compile a “Best Practices” summary to help with the repeat questions I (and probably others) have received. This is intended to be neither a full tutorial on Forscan nor instructions for any specific changes as there are plenty of other good references already in existence. My hope is that by documenting this it provides some basic guidance to new users and a consistent post to refer back to as people receive their vehicles and want to make updates. I am open to input if there are items I missed that would be helpful and will edit this post accordingly (@ccw @MiTremor906 @SomethingRandom @BroncoHooves @PapaRaptor )
  1. Preparation: Before you even take possession of your truck there are things you can do to get ahead of the game and set yourself up for success. These will also serve as good reference tools ongoing if you encounter issues or have questions:
    1. Once you have a VIN and your vehicle is in production you can access the “As-Built” data from your control modules (more detail on this below). Go to https://www.motorcraftservice.com/AsBuilt and enter your VIN
      1. The data listed for your vehicle should be copied and saved as a backup just in case!
      2. Highlight the entire page starting with “Module” at the top and ending with “End of information” at the bottom
      3. Ctrl-C to copy
      4. I pasted mine into Excel and selected “Keep Source Formatting” it will look like this, but will be ~835 rows of data.View attachment 43112
    2. Download and take a look at the various summary spreadsheets available:
      1. 2022 SuperDuty - https://www.fordtremor.com/threads/forscan-for-2022.5886/
        1. Specific to the changes for this model year, but not fully populated yet
      2. 2020-21 SuperDuty - https://www.forscan.org/forum/viewtopic.php?t=13978
        1. USE WITH CAUTION FOR 22MY - Good reference as many changes are common for the 22MY SD
      3. 2021 F150 - https://docs.google.com/spreadsheet...Nwyqu5v3dgpbluvJcezUItTSVI/edit#gid=364824617
        1. USE WITH CAUTION FOR 22MY – Good reference as many changes are common for SYNC4 and not yet mapped for the 22MY SD
    3. There are many online resources to look at while you are waiting:
      1. https://forscan.org/ – Good forum for tutorials, answers to many common questions, also where you access/download the software…
      2. Our own Tremor forum has specific threads for 2020, 2021, and 2022 model years
      3. Ford Truck Enthusiasts can also be very helpful: https://www.ford-trucks.com/forums/1668884-2022-forscan.html
      4. YouTube
  2. Hardware: You will need two things to execute your dream electronic customization of your truck. A laptop and an OBDII interface adapter.
    1. Laptop. I use an PC laptop that is probably ~7yrs old but works just fine for this purpose. I updated to Windows 10 but otherwise the specs can be found here if you would like to compare: https://specspro.net/laptops/1250-toshiba-satellite-c55-a5302/
    2. Adapter. Don’t mess around here and I do not recommend getting one with a Bluetooth interface – wired is the way to go 🔌. This is the one recommended by Forscan.org and the one I purchased: https://www.obdlink.com/products/obdlink-ex/?ref=forscan (can also be purchased on Amazon…)
  3. Software: Pretty straightforward, but I thought it was worth mentioning…
    1. https://forscan.org/
    2. I recommend purchasing the extended license as it helps to support the developers of this fine product!
    3. Check for updates and always run the latest version! This is very important for model years with significant changes like 2022. There has been much improvement from the initial to the current release for our trucks.
  4. Practice: “Practice does not make perfect, only perfect practice makes perfect” - Vince Lombardi. In this case it helps to just do some trial runs and get familiar with things.
    1. Once you have your laptop, adapter, and truck (obviously):
      1. Connect everything up and update/download any drivers (should happen automatically)
      2. Get familiar with the interface and the key sections in the software
      3. Open up some modules and look at what is there without changing anything
    2. Some modules have two distinct ways to access the settings:
      1. “As-Built” which is the same hexadecimal memory address and settings shown on the Motorcraft site
      2. “Plain English” which is more conversational – disable, enable, etc
      3. Not all modules have both. If there is a Plain English version changing this will also change the As-Built
      4. More detail available in my post here: https://www.fordtremor.com/threads/forscan-for-2022.5886/post-168312
  5. Documentation:
    1. Use the Motorcraft As-Built info to your advantage:
      1. The data listed for your VIN should be copied and saved as a backup just in case! (I just got Déjà vu writing this. I wonder why, hmmm… 🤔)
      2. Copying to Excel (or any other program of your choice) allows you to save the initial data, and use it to keep track of any changes you make, like this: View attachment 43115
    2. Document what you change.
      1. Hand written, Excel, take a picture, whatever works for you
      2. I have used all methods – just use at least one of them, please! 🙏
    3. Backup in Forscan:
      1. Save a module BEFORE you make any changes and then save a copy with a different name AFTER you make changes.
      2. If you are proactive you can makes copies of the most used modules before you start: Body, IPC, APIM
  6. Other Thoughts:
    1. Backup, backup, backup your data. If your are not sure, back it up again!
    2. Early in a model year the Plain English domain may or may not work as intended. It gets more accurate over time with each updated Forscan release.
    3. When working in the As-Built module, do not take the entire memory address from someone else's truck without understanding the potential unintended consequences. The settings in a single memory address can (and most of the time do) control multiple functions.
    4. When in doubt, ask. There are lots of people willing to help on this forum or others. Most questions can be answered quickly before an issue is created and you enter into “what did I just do” mode 🙀
this is awesome and was a lot of time and effort for this info.
 
^ what he said!

I’m ready to dip my toes into this Forscan pool. I replaced the stock tires (non-Tremor) with 295/70-18 so need to get the settings changed for that and the door open chimes drive me NUTS.

I’ve got the recommended adapter ordered and working on the laptop angle now. Have the As-Built files as well and pasted into a spreadsheet as described above.

I’ve read this whole thread and the 2022 Forscan thread so far.

Have one question tho. After one makes changes with Forscan and needs to take the truck in for warranty work, do you guys revert the settings back to stock before going to dealer? And what happens if they determine the modules have been updated? Is warranty voided?
 
Have one question tho. After one makes changes with Forscan and needs to take the truck in for warranty work, do you guys revert the settings back to stock before going to dealer? And what happens if they determine the modules have been updated? Is warranty voided?
The option to fine tune these settings are there. How would a Ford technician working on your truck know what settings were there from factory or even if some other tech has out them in place for a customer. In other words, i doubt they know all default settings on each MY truck or that they would even care to check. Thinking that if for example your seat belt warning is off and they take it for a test drive they might tell you about it, but thats the extend of it.

Now if during your own forscan updates you f something up and bring it to dealership on to restore it, then yes i dont think they will want to fover that under warranty:)
 
I recently had my vehicle in for warranty work and made sure I had a backup/documentation of my changes, but did not revert back to the original settings. This is important since they may re-flash your modules and you, ideally, would want to save yourself some work getting back to where you started.
 
  • Like
Reactions: ccw
Happy New Year Forscan users!

I have started to compile a “Best Practices” summary to help with the repeat questions I (and probably others) have received. This is intended to be neither a full tutorial on Forscan nor instructions for any specific changes as there are plenty of other good references already in existence. My hope is that by documenting this it provides some basic guidance to new users and a consistent post to refer back to as people receive their vehicles and want to make updates. I am open to input if there are items I missed that would be helpful and will edit this post accordingly (@ccw @MiTremor906 @SomethingRandom @BroncoHooves @PapaRaptor )
  1. Preparation: Before you even take possession of your truck there are things you can do to get ahead of the game and set yourself up for success. These will also serve as good reference tools ongoing if you encounter issues or have questions:
    1. Once you have a VIN and your vehicle is in production you can access the “As-Built” data from your control modules (more detail on this below). Go to https://www.motorcraftservice.com/AsBuilt and enter your VIN
      1. The data listed for your vehicle should be copied and saved as a backup just in case!
      2. Highlight the entire page starting with “Module” at the top and ending with “End of information” at the bottom
      3. Ctrl-C to copy
      4. I pasted mine into Excel and selected “Keep Source Formatting” it will look like this, but will be ~835 rows of data.View attachment 43112
    2. Download and take a look at the various summary spreadsheets available:
      1. 2022 SuperDuty - https://www.fordtremor.com/threads/forscan-for-2022.5886/
        1. Specific to the changes for this model year, but not fully populated yet
      2. 2020-21 SuperDuty - https://www.forscan.org/forum/viewtopic.php?t=13978
        1. USE WITH CAUTION FOR 22MY - Good reference as many changes are common for the 22MY SD
      3. 2021 F150 - https://docs.google.com/spreadsheet...Nwyqu5v3dgpbluvJcezUItTSVI/edit#gid=364824617
        1. USE WITH CAUTION FOR 22MY – Good reference as many changes are common for SYNC4 and not yet mapped for the 22MY SD
    3. There are many online resources to look at while you are waiting:
      1. https://forscan.org/ – Good forum for tutorials, answers to many common questions, also where you access/download the software…
      2. Our own Tremor forum has specific threads for 2020, 2021, and 2022 model years
      3. Ford Truck Enthusiasts can also be very helpful: https://www.ford-trucks.com/forums/1668884-2022-forscan.html
      4. YouTube
  2. Hardware: You will need two things to execute your dream electronic customization of your truck. A laptop and an OBDII interface adapter.
    1. Laptop. I use an PC laptop that is probably ~7yrs old but works just fine for this purpose. I updated to Windows 10 but otherwise the specs can be found here if you would like to compare: https://specspro.net/laptops/1250-toshiba-satellite-c55-a5302/
    2. Adapter. Don’t mess around here and I do not recommend getting one with a Bluetooth interface – wired is the way to go 🔌. This is the one recommended by Forscan.org and the one I purchased: https://www.obdlink.com/products/obdlink-ex/?ref=forscan (can also be purchased on Amazon…)
  3. Software: Pretty straightforward, but I thought it was worth mentioning…
    1. https://forscan.org/
    2. I recommend purchasing the extended license as it helps to support the developers of this fine product!
    3. Check for updates and always run the latest version! This is very important for model years with significant changes like 2022. There has been much improvement from the initial to the current release for our trucks.
  4. Practice: “Practice does not make perfect, only perfect practice makes perfect” - Vince Lombardi. In this case it helps to just do some trial runs and get familiar with things.
    1. Once you have your laptop, adapter, and truck (obviously):
      1. Connect everything up and update/download any drivers (should happen automatically)
      2. Get familiar with the interface and the key sections in the software
      3. Open up some modules and look at what is there without changing anything
    2. Some modules have two distinct ways to access the settings:
      1. “As-Built” which is the same hexadecimal memory address and settings shown on the Motorcraft site
      2. “Plain English” which is more conversational – disable, enable, etc
      3. Not all modules have both. If there is a Plain English version changing this will also change the As-Built
      4. More detail available in my post here: https://www.fordtremor.com/threads/forscan-for-2022.5886/post-168312
  5. Documentation:
    1. Use the Motorcraft As-Built info to your advantage:
      1. The data listed for your VIN should be copied and saved as a backup just in case! (I just got Déjà vu writing this. I wonder why, hmmm… 🤔)
      2. Copying to Excel (or any other program of your choice) allows you to save the initial data, and use it to keep track of any changes you make, like this: View attachment 43115
    2. Document what you change.
      1. Hand written, Excel, take a picture, whatever works for you
      2. I have used all methods – just use at least one of them, please! 🙏
    3. Backup in Forscan:
      1. Save a module BEFORE you make any changes and then save a copy with a different name AFTER you make changes.
      2. If you are proactive you can makes copies of the most used modules before you start: Body, IPC, APIM
  6. Other Thoughts:
    1. Backup, backup, backup your data. If your are not sure, back it up again!
    2. Early in a model year the Plain English domain may or may not work as intended. It gets more accurate over time with each updated Forscan release.
    3. When working in the As-Built module, do not take the entire memory address from someone else's truck without understanding the potential unintended consequences. The settings in a single memory address can (and most of the time do) control multiple functions.
    4. When in doubt, ask. There are lots of people willing to help on this forum or others. Most questions can be answered quickly before an issue is created and you enter into “what did I just do” mode 🙀
Thanks so much for all this info! I've got an F-350 Plat Trem w. 6.7 on order, and it'll be the first real truck I've had. Don't know much about any programming, so this info is a huge gain for me!
Appreciate you putting this together!
Tom
 
Question for you FORScan wizards and some background first. Finally got the courage to do some FORScan stuff. Did all the plain English changes with before & after files saved, labelled said files and documented what changes were made from one file to another via an excel sheet.

Went to do my first change in AS BUILT, triple startup ding. From Motorcraftservice.com my data I downloaded lists IPC module 720-01-02 with the following values: 221B 50B7. Went to replace the zero on 50B7 with a 2 and wrote the change from 0 to 2. After the write IPC AS BUILT for 720-01-02 reads 221B 52A9. Were the last two values, B7, supposed to change to A9 when I replaced the 0 with a 2? Could've sworn after I replaced the 0 with a 2 and before I hit write the values read 52B7.

Thanks in advance. I'm sure someone has had a similar question. Sorry, but wanted to get a direct answer rather than making a conclusion from someone else' Q & A.
 
Something looks odd... The "B7" is a checksum so it adds up the rest of the fields in the memory string (in Hexadecimal). Since you added "2" to the string "50" the checksum also has to increase by "2". In Hex B7 + 02 = B9

Weird that it would go from B7 to A9. If I calculate it manually the B7 looks correct:

1664646438652.png



If everything is working properly I wouldn't be concerned as Forscan auto calculates the correct Checksum, it is not something you have to do when you make a change unless you want to. I would be curious if you double check it to confirm the A9, though.

Hope this makes sense...
 
Something looks odd... The "B7" is a checksum so it adds up the rest of the fields in the memory string (in Hexadecimal). Since you added "2" to the string "50" the checksum also has to increase by "2". In Hex B7 + 02 = B9

Weird that it would go from B7 to A9. If I calculate it manually the B7 looks correct:

View attachment 61822


If everything is working properly I wouldn't be concerned as Forscan auto calculates the correct Checksum, it is not something you have to do when you make a change unless you want to. I would be curious if you double check it to confirm the A9, though.

Hope this makes sense...
Awesome reply. Appreciate you. Only because I am curious I am going to reload the stock module that I saved before I did any edits and see what it looks like before and after I make the change to turn off the triple start up ding. You mind explaining how I write the stock parameters I saved?
 
Well, wrote factory as built, 50B7. Typed and wrote 52B7 and no more triple start up ding. Disconnected, came back to vehicle, hooked up FORScan and 720-01-02 reads 52A9 again. Weird, but I guess nothing to worry about. Everything is working as it should and no triple startup chime
 
Well, wrote factory as built, 50B7. Typed and wrote 52B7 and no more triple start up ding. Disconnected, came back to vehicle, hooked up FORScan and 720-01-02 reads 52A9 again. Weird, but I guess nothing to worry about. Everything is working as it should and no triple startup chime
Cool! I'm going to have to chew on this one for a bit, has me puzzled now...
 
Not sure if its been addressed in another thread and i apologize if it has. I've downloaded the software and installed to the point where it asks for a license file. The file that was emailed to me came as a .key csv file. It is not recognized when I try to install into the Forscan folder, or any folder for that matter. It will open up but Forscan will not accept it. Any help will be appreciated.
 
Back
Top