Hey Guys,

I came out of VW cars and over on that platform we had a programming system called Vag Com or VCDS. It was a similar system to FORScan in that you can make some amazing changes to your vehicle by reprogramming the computers to turn on or turn off features. Vag Com worked quite a bit differently in how you acquired it ($350 cable you had to buy) and how the programming worked. FORScan is free if you already own the minimal cost OBD device.

Even with 8 years of experience programing my VW vehicles and friends vehicles I found the FORScan system a little daunting. Then one day I finally dug into it I discovered it wasn't that bad...at the same time I was happy I had a few years of experience doing this sort of work.

I put together a tutorial to help folks so that after they get their FORScan license to actually program their vehicles they can see just how to do it and how easy it is. I also show how to make changes using the 2 different ways to program....Enable/disable and then coding.

I recorded this video while in virgin territory attempting to apply some coding for our 2017+ Super Duty to my 2018 Expedition. One set of codes didn't work and I show what happens in that case in the video.

My favorite features I turned on where.

Particulate filter % full
Bambi mode for lighting...meaning fogs stay on with the high beam headlights
Digital temperature readout for the coolant

Hope this video can be helpful to anyone looking to dive into the world of FORScan.

 

I have to be honest that I was scared to death to start messing with Forscan but once I started and little help from ZooDaddy, I'm pretty comfortable now. All of the info here and the Forscan forum makes it a lot easier to learn up front and just fill in the rest on the fly. And another huge thank you to all those that compiled the spreadsheets and cheat sheets.

 

Thanks for making the video, I look forward to watching it tonight and getting started with Forscan mods on my '17 F350 soon!

 

Thank you, thank you, thank you for this! I am 100% intimidated to death of Forscan and this video helps a lot.

 

Hey Guys...you are welcome. The key is to take your time and check everything 2-3 times before you hit the "write" button.

Another idea would be to take a photo of the OEM coding of the command you want to change before you enter in the new code. That way if you accidentally make a change (like accidentally entering a code that the computer accepted but it was bad code) then you have a picture of the OEM coding to change it back and try again.

You will do great!

 

MAKE A BACKUP OF EACH MODULES DATA BEFORE YOU START!!!
When you go into each module to change data on the bottom is a "SAVE ALL" button. Click that and give it a name like APIM.STOCK, so if you ever want to restore it back to factory you can just click "LOAD ALL" and pick that module and then "WRITE ALL" and it will reload your stock settings.
Then after you make changes click "SAVE ALL" and give it a name like "APIM.MODDED" so you will have a copy of what was changed.

Here's another video where he talks about saving and naming modules.