FORScan User's Thread

[Steve_C]

I see a few folks are familiar with using FORScan Diagnostics & Programming on their vehicles. I just downloaded the latest version from FORScan.org and bought a 1 year subscription licence for $12.00. Seems like the OEM Ford version of IDS will set you back about $400 or more, depending on who you purchase from, for a 1 year licence. If you have used FORscan, was it on a Lincoln or Ford vehicle? Did you do any re-programming with it? What interface brand & type are you using, Bluetooth or USB cable? I put this post in the Nautilus Forum, since that is the vehicle I have, but of course this works across all Lincoln lines. I could not find a dedicated forum within this site to post it so all Lincoln owners could see it across the Lincoln Lineup!

 

[System]

Hi Steve.... I'm a long time FORScan user and a huge advocate of the program. I've used it on my last 3 Ford SD trucks and our current Corsair GT. When our 24 Nautilus lands, I'll be jumping right in there too. I've also used it on many friend's vehicles as well. Up until recently, I ran the OBDLink MX and have recently upgraded to the MX+. I did this because the plus will work with my iPhone as well so I can run FORScan Lite on the fly to do some service procedures like clearing adaptive learning tables on my trucks trans, clear DTCs, etc. Both are BT and both have always performed flawlessly. You likely won't find a Lincoln specific spreadsheet for available changes but using the equivalent Ford spreadsheet will get you where you need to be.

As you probably know, always back up whatever module you are modifying before making any changes just in case something goes wrong. You can also download your complete as built profile from the Ford Service website which will contain all your values from day one. One thing to remember is that once you make a change with FORScan, the next time the dealer plugs in, your current As Built will be uploaded to Ford's server and it will become your vehicle's new As Built. So, having an original copy from before doing any changes is always a good idea... although I've never once had the need for it...

What's also great is FORScan has come a long way in recent years with plain English changes. When it first started, there was little plain English and almost everything had to be done by changing values in HEX. Although, sometimes plain English changes are ineffective. But, the great thing about Forscan is nothing is permanent. If something doesn't work, switch it back. If something has a negative effect, switch it back.

Anyways, have fun tweaking! I am a moderator on the major Ford truck forums (Ford Truck Enthusiasts) and one of my areas includes many Forscan specific threads. So, while I'm not a guru, I've been around it a lot. I also have a friend who is indeed a guru. He actually wrote a computer program to isolate different values in as built profiles and is one of the ones who creates new changes for the spreadsheets and also communicates directly with FORScan about progress and helps them add new plain English options on new releases of the software. So, if you (or anyone else here on the Lincoln forums) ever get stuck on something, I'll try to help if I can.

 

[tinner]

I've been running FORScan for years on my "16 F150, '22 Nautilus, as well as several other F150's and other Fords ( Explorers, Mustangs, Edges,) etc. I use the OBDLink EX (USB version) as I found it to work better on '21 and above models as far as reading all the modules compared to the my OBDLink MX (bluetooth version) did.

F150forum has great FORScan info. Be sure to back up your As Built, so with one click you are back to stock in each module that changes were made if need be.

 

[MattMacMan]

Hi Steve.... I'm a long time FORScan user and a huge advocate of the program. I've used it on my last 3 Ford SD trucks and our current Corsair GT. When our 24 Nautilus lands, I'll be jumping right in there too. I've also used it on many friend's vehicles as well. Up until recently, I ran the OBDLink MX and have recently upgraded to the MX+. I did this because the plus will work with my iPhone as well so I can run FORScan Lite on the fly to do some service procedures like clearing adaptive learning tables on my trucks trans, clear DTCs, etc. Both are BT and both have always performed flawlessly. You likely won't find a Lincoln specific spreadsheet for available changes but using the equivalent Ford spreadsheet will get you where you need to be.

As you probably know, always back up whatever module you are modifying before making any changes just in case something goes wrong. You can also download your complete as built profile from the Ford Service website which will contain all your values from day one. One thing to remember is that once you make a change with FORScan, the next time the dealer plugs in, your current As Built will be uploaded to Ford's server and it will become your vehicle's new As Built. So, having an original copy from before doing any changes is always a good idea... although I've never once had the need for it...

What's also great is FORScan has come a long way in recent years with plain English changes. When it first started, there was little plain English and almost everything had to be done by changing values in HEX. Although, sometimes plain English changes are ineffective. But, the great thing about Forscan is nothing is permanent. If something doesn't work, switch it back. If something has a negative effect, switch it back.

Anyways, have fun tweaking! I am a moderator on the major Ford truck forums (Ford Truck Enthusiasts) and one of my areas includes many Forscan specific threads. So, while I'm not a guru, I've been around it a lot. I also have a friend who is indeed a guru. He actually wrote a computer program to isolate different values in as built profiles and is one of the ones who creates new changes for the spreadsheets and also communicates directly with FORScan about progress and helps them add new plain English options on new releases of the software. So, if you (or anyone else here on the Lincoln forums) ever get stuck on something, I'll try to help if I can.

I’m also an avid FORScan user. Been using it since 2016 on my Ford Fusion Titanium and the wife’s Ford Focus. But my 23 Nautilus BL isn’t recognized by FORScan. It says it doesn’t recognize the PCM contact the developers. I’ve used an OBDLINK MX (not MX+) and an OBDLINK EX no dice. Any suggestions?

______________________________

 

[Steve_C]

I’m also an avid FORScan user. Been using it since 2016 on my Ford Fusion Titanium and the wife’s Ford Focus. But my 23 Nautilus BL isn’t recognized by FORScan. It says it doesn’t recognize the PCM contact the developers. I’ve used an OBDLINK MX (not MX+) and an OBDLINK EX no dice. Any suggestions?

Matt, I have noted comments from System and Tinner above as well as Miked51 in another thread. Very helpful info so far, thanks guys!
I just received an OBDLink EX usb, and have the most recent Forscan ver. software. I am hoping to try my first connect before this weekend. I will keep you posted on my attempt. I am glad you reported that I might have an issue, will keep me from (freaking out) if I get a PCM not recognized message!
Being that you seem to be familiar with the program, I am expecting a problem! Again, will report back!

 

[Miked51]

Matt, I have noted comments from System and Tinner above as well as Miked51 in another thread. Very helpful info so far, thanks guys!
I just received an OBDLink EX usb, and have the most recent Forscan ver. software. I am hoping to try my first connect before this weekend. I will keep you posted on my attempt. I am glad you reported that I might have an issue, will keep me from (freaking out) if I get a PCM not recognized message!
Being that you seem to be familiar with the program, I am expecting a problem! Again, will report back!

 

[Miked51]

Forscan V 2.3.58 date 01/02/2024 still no 2023 Lincoln Nautilus Data Base yet, just have to keep waiting for update!

 

[tinner]

On my wife's '22 Nautilus, I get the PCM to show, but I have never been able to get the APIM to show and I have several changes on the Sync 4 screen I wanting to make,

I have wiped my FORScan log so it's like I'm using it for the first time every time I've used it and still nothing. I get all the other 36 modules according to the Motorcraft As Built site.

I've reached out to FORScan support and crickets. FORScan forum members and F150forum members both groups are leaning towards a database glitch.

If anybody is getting the APIM to show with a '22, then that would rule out a database glitch, please chime in.

Not to high jack OP's thread.

______________________________

 

[Steve_C]

On my wife's '22 Nautilus, I get the PCM to show, but I have never been able to get the APIM to show and I have several changes on the Sync 4 screen I wanting to make,

I have wiped my FORScan log so it's like I'm using it for the first time every time I've used it and still nothing. I get all the other 36 modules according to the Motorcraft As Built site....."

 

[MattMacMan]

On my wife's '22 Nautilus, I get the PCM to show, but I have never been able to get the APIM to show and I have several changes on the Sync 4 screen I wanting to make,

I have wiped my FORScan log so it's like I'm using it for the first time every time I've used it and still nothing. I get all the other 36 modules according to the Motorcraft As Built site.

I've reached out to FORScan support and crickets. FORScan forum members and F150forum members both groups are leaning towards a database glitch.

If anybody is getting the APIM to show with a '22, then that would rule out a database glitch, please chime in.

Not to high jack OP's thread.

I just wanted to be able to clear codes (I’ve done a few things and unplugged others while making modifications) and the biggest thing I want to do is change my turn signal flashes from 3 to 5.

 

[tinner]

When get up and running, you should be able to change the signal flashes in the SCCM Module-
724-01-01 xxxx xBxx xx.. I changed 7 to B to get 5 blinks.
This was one of my first changes on my wife's Reserve 2 along with disabling Auto Stop Start and double honk and autolock.
Good luck'

 

[Steve_C]

When get up and running, you should be able to change the signal flashes in the SCCM Module-
724-01-01 xxxx xBxx xx.. I changed 7 to B to get 5 blinks.
This was one of my first changes on my wife's Reserve 2 along with disabling Auto Stop Start and double honk and autolock.
Good luck'

tinner,
So, on your 2022 Naut you are able to access & address modules in Forescan, yet the 2023 Nauts (as a few of us have reported here) cannot? We see "PCM Not Found" message. I find it strange and do not understand why this would be when 2022 systems are identical to 2023's! I hope the Forescan admins can update profiles to read 2023 & up PCM's! I know you have thoroughly addressed the issue in above postings. To sum up, you get 36 modules to show, and you can address them, but you cannot get access to APIM?

______________________________

 

[tinner]

Correct. I should have stated 35 modules showing(APIM would be 36) and able address them and module resets after changes, etc. Just updated to V. 2.3.58 and still no go.

 

[System]

tinner,
So, on your 2022 Naut you are able to access & address modules in Forescan, yet the 2023 Nauts (as a few of us have reported here) cannot? We see "PCM Not Found" message. I find it strange and do not understand why this would be when 2022 systems are identical to 2023's! I hope the Forescan admins can update profiles to read 2023 & up PCM's! I know you have thoroughly addressed the issue in above postings. To sum up, you get 36 modules to show, and you can address them, but you cannot get access to APIM?

Steve, often new model years require a new version of Forscan before they will show all modules... even when there is no change between model years.

 

[tinner]

I

Steve, often new model years require a new version of Forscan before they will show all modules... even when there is no change between model years.

I've been waiting since Aug '22 and still no APIM with with several updated versions. As I stated above , I have reached out to FORScan support twice sending in my log data as they requested and it's been silence on their end.

Just to clarify-- FORScan isn't recognizing the '23 MY? Which isn't showing any modules to make changes, or just missing the PCM ( Powertrain Control Module) and you are getting the APIM that I'm missing?

 

[Steve_C]

Steve, often new model years require a new version of Forscan before they will show all modules... even when there is no change between model years.

Thanks Rodney! That is a good possible explanation. With that in mind, I will be proactive in looking for updates & keep trying them.
If I find someone who has a Ford IDS/FDRS program that can extract data for me, what would I ask for? I would want list of modules, and I would think the current values (coding/settings) those modules are set to. Anything else? My immediate need is to see if I have a TRM module already installed for future coding it for trailer installation. Any thoughts appreciated! If my vehicle does not have a TRM module, would someone with the Ford program be able to code TRM & applicable modules easily? Would they need to know what other individual modules need to be coded, or does the program have a factory setting option/selection for trailer tow application?

______________________________

 

[Steve_C]

I
I've been waiting since Aug '22 and still no APIM with with several updated versions. As I stated above , I have reached out to FORScan support twice sending in my log data as they requested and it's been silence on their end.

Just to clarify-- FORScan isn't recognizing the '23 MY? Which isn't showing any modules to make changes, or just missing the PCM ( Powertrain Control Module) and you are getting the APIM that I'm missing?

No mention of APIM at all on my '23 MY. Does not recognize my PCM! This is exactly what is recorded on screen:

(WARN) [16:18:36.936] Checking FTDI #1:223130142138...
(OK) [16:19:04.722] Connection to adapter has been established: FTDI #1:223130142138
(OK) [16:19:04.722] Adapter: OBDLink EX r2.2.1 STN2231 v5.8.1 (ELM327 v1.4b)
(OK) [16:19:04.817] Connection to vehicle has been established
(ERR) [16:19:18.995] Unable to identify the vehicle. Please contact developers
(OK) [16:20:23.258] Connection to vehicle has been established
(ERR) [16:20:30.744] Unable to identify the vehicle. Please contact developers

NOTE: Last 2 entries from above were from me trying to re-connect I believe.
Not sure what the "Warning" message (first line) is about.

From this, I assume my COM link to vehicle is OK...but it cannot ID the vehicle!

 

[tinner]

No mention of APIM at all on my '23 MY. Does not recognize my PCM! This is exactly what is recorded on screen:

(WARN) [16:18:36.936] Checking FTDI #1:223130142138...
(OK) [16:19:04.722] Connection to adapter has been established: FTDI #1:223130142138
(OK) [16:19:04.722] Adapter: OBDLink EX r2.2.1 STN2231 v5.8.1 (ELM327 v1.4b)
(OK) [16:19:04.817] Connection to vehicle has been established
(ERR) [16:19:18.995] Unable to identify the vehicle. Please contact developers
(OK) [16:20:23.258] Connection to vehicle has been established
(ERR) [16:20:30.744] Unable to identify the vehicle. Please contact developers

NOTE: Last 2 entries from above were from me trying to re-connect I believe.
Not sure what the "Warning" message (first line) is about.

From this, I assume my COM link to vehicle is OK...but it cannot ID the vehicle!

No mention of APIM at all on my '23 MY. Does not recognize my PCM! This is exactly what is recorded on screen:

(WARN) [16:18:36.936] Checking FTDI #1:223130142138...
(OK) [16:19:04.722] Connection to adapter has been established: FTDI #1:223130142138
d
(OK) [16:19:04.817] Connection to vehicle has been established
(ERR) [16:19:18.995] Unable to identify the vehicle. Please contact developers
(OK) [16:20:23.258] Connection to vehicle has been established
(ERR) [16:20:30.744] Unable to identify the vehicle. Please contact developers

NOTE: Last 2 entries from above were from me trying to re-connect I believe.
Not sure what the "Warning" message (first line) is about.

From this, I assume my COM link to vehicle is OK...but it cannot ID the vehicle!

Never seen a warning before. The adopter is the same one that I use and is highly recommended on the FORScan forum.

Go to motorcraftservice.com/AsBuilt---Type in your VIN, and the will give you the modules with FORScan values as it came from the factory. You always want to have a backup of the originals.

EDIT-- Forgot to mention that on my As Built coding TRM is 791's

 

[Miked51]

RE : Forscan, just look at the version release notes. The latest version doesn't support 2021 & up Nautilus yet.
just have to wait until they update the version data base lists.

 

[tinner]

As I stated in posts; 8,11,13, my '22 is able to make changes. Maybe when FORScan updates so the '23's can finally make access to FORScan since the '24's are on the boats, I will be able to have access to my missing module APIM (7DO).