How to connect FORScan to cars with non-stock/tuned/custom PCM firmware

Any issues related to FORScan application
Post Reply
FORScan
Site Admin
Posts: 2970
Joined: Fri Jun 13, 2014 2:21 am

How to connect FORScan to cars with non-stock/tuned/custom PCM firmware

Post by FORScan »

This article is actual for 2011-2012+ model year vehicles with a custom tune. Older models contain no ECU partnumbers in the AB file.

FORScan uses PCM number to recongize the car. On new cars PCM strategy is required in fact. FORScan reads the strategy number from PCM, but if the strategy is missing in FORScan database, it shows the following dialog:

Image

Important note: the same error will appear if the car is too new for this version of FORScan. Please make sure that you use the latest version of FORScan.

The simplest workaround in this case is to obtain factory (stock) strategy number for the car in trouble and enter this number in the dialog. Here is step by step instruction:

1. Go to the Motorcraft site As Built page:

https://www.motorcraftservice.com/AsBuilt

Please note Ford may ask for additional information, such as your country. Please sumbit all the necessary information, it is not difficult.

2. Enter VIN of the car (we recommend copy and paste, to avoid typos) and fill Captcha field, submit the request.

3. Press the "DOWNLOAD FILE" button at top of the page and store the file in a folder you can find it later in.

4. Open the file downloaded on step #3 with any convenient XML viewer.

This is the most confusing step, as the downloaded file has .ab extension that is not associated with XML format in Windows, and majority of normal people don't use XML viewers in their normal work. So as a quick workaround, it does make sense to rename (or save as) the file and add .xml and the end, then click it to let Windows find some software to view the XML.

5. Using XML viewer search, find the NODEID tag with 7E0 value, the find F188 tag inside and copy it's value:

Image

6. Copy and paste or type the value in FORScan dialog and press OK.
valdayn
Posts: 2
Joined: Tue Jun 29, 2021 10:25 am
Vehicle: mazda cx7 2l. 147hp.2008

Re: How to connect FORScan to cars with non-stock/tuned/custom

Post by valdayn »

добрый вечер. подскажите как активировать форскан???
zx9rcpa
Posts: 4
Joined: Thu Aug 08, 2024 8:41 pm
Vehicle: 2017 Ford Fiesta ST 1.6L EcoBoost engine

Re: How to connect FORScan to cars with non-stock/tuned/custom

Post by zx9rcpa »

What do I do if this doesn't work?

I went through the instructions step by step - TWICE! I found them straightforward and easy to follow, and came up with the same result both times. But entering the result into the "unable to identify vehicle" response box just gets me a "unable to identify vehicle, please contact developers" message.

I have no idea who the "developers" were, so what should I do next?
Joh150413
Posts: 225
Joined: Fri Oct 19, 2018 10:18 pm
Vehicle: Taurus,3.5 Ecoboost, 2016

Re: How to connect FORScan to cars with non-stock/tuned/custom

Post by Joh150413 »

I can think of two options for you.

1) Get the PCM part number directly from the label on the PCM. You may have to remove the PCM to view the label.

2) Temporarily remove the tune and restore the PCM to factory. Connect FORScan and save the profile. Reinstall your tune and use the previously stored profile.
zx9rcpa
Posts: 4
Joined: Thu Aug 08, 2024 8:41 pm
Vehicle: 2017 Ford Fiesta ST 1.6L EcoBoost engine

Re: How to connect FORScan to cars with non-stock/tuned/custom

Post by zx9rcpa »

Thanks Job150413. In addition to what the Motorcraft site As Built page told me to use, I also tried the P/N and the H/W numbers directly off the PCM, and have tried restoring the PCM to factory, as you suggested. I'm beginning to believe that someone swapped in an non-compatible PCM at some point for a reason only they would understand. Unless you have other suggestions, that's where I'm going to look next.

Maybe you can tell me this: Is the number Motorcraft said I SHOULD use the part number the car was originally built with? If you can tell me that much it'd make my search for a replacement PCM a lot easier.
tractmec
Posts: 2109
Joined: Thu May 26, 2016 11:43 pm
Vehicle: F150 5.4 Triton 2005 Fusion 3.0 2010

Re: How to connect FORScan to cars with non-stock/tuned/custom

Post by tractmec »

zx9rcpa wrote: Fri Aug 09, 2024 12:49 am Thanks Job150413. In addition to what the Motorcraft site As Built page told me to use, I also tried the P/N and the H/W numbers directly off the PCM, and have tried restoring the PCM to factory, as you suggested. I'm beginning to believe that someone swapped in an non-compatible PCM at some point for a reason only they would understand. Unless you have other suggestions, that's where I'm going to look next.

Maybe you can tell me this: Is the number Motorcraft said I SHOULD use the part number the car was originally built with? If you can tell me that much it'd make my search for a replacement PCM a lot easier.
I will attempt at least a possible answer and perhaps more of an educated guess?

If you mean the Strategy file number that resolves in the .xml version at <NODEID188> in the AsBuilt file(CM5A-14C204-ASC as in the Focus example below) you supposedly downloaded from Motorcraftservice.com/Asbuilt, yes that is the file number that the vehicle left the Factory with the originally installed PCM!

If you have a <NODEID> tagged #F113 in the .xml file under the 7E0 Address, in all I have looked at so far with that <NODEID, it should show the original Part Number of the PCM (Example from a 2013 Focus: <CM5A-12A650-ASA>) and yours will be different but if it has 12A650 as the middle alpha numeric set, it is very likely the original part Number of the PCM installed at the Factory!
The first four characters usually will represent the vehicle family and will usually be the same in all PCM revisions although this is not a hard and fast rule depending on how many revisions were done, and the last set (ASA as above) will show the PCM revision level!

IF that number on the PCM is different from your .xml #F113 then at some point the PCM has either been replaced or upgraded to a later configuration(If the latter was done by a Dealer there should be sticker type tag glued or pasted over the original PCM label or at least they are supposed to paste a new label(possibly even Hand Written) on the PCM or somewhere under the hood when the dealer does this. Out side of the dealer this is my not be likely although pro tuners are supposed to do this too!

Try the _12A650_ Part Number in the FORScan field and if it still is not able to Identify the Vehicle then for some reason the PCM is not responding to the FORScan query with a return ACK and information Packets containing the PCM configuration! That can happen for number of reasons including a tuner configuration that FORScan has never seen, an external switched adapter in the MSCAN position or wired incorrectly, the HSCAN(DLC PIN 6 and 14 and should show ~60 ohms across those connections) network is not communicative due to a wiring harness trauma or pin and socket corrosion etc.(The Adapter you are using would have been a help?)

If you still have trouble the "Developers can be contacted(Paid license required) by following the instructions after the Heading "Providing FORScan Debug Information" at this link: https://forscan.org/contactus.html

Just some possible scenarios and I may be wrong?
oldtinfords
Posts: 664
Joined: Sat Mar 18, 2017 2:51 am
Vehicle: 06 BFII XR8 260kw,08 BFII GT 302kw,07 BFII XR6T 245kw

Re: How to connect FORScan to cars with non-stock/tuned/custom

Post by oldtinfords »

Here's a link to the XML Viewer I use if anyone needs it
https://jsonformatter.org/xml-viewer
xpiodm
Posts: 1
Joined: Tue Mar 25, 2025 4:50 pm
Vehicle: Mazda CX30 (2.0) 2022

Re: How to connect FORScan to cars with non-stock/tuned/custom

Post by xpiodm »

...to obtain factory (stock) strategy number...
1. Go to the Motorcraft site As Built page:
https://www.motorcraftservice.com/AsBuilt
How to obtain strategy number for JDM car (no VIN, just short chassis number).
I have an ordinary mazda cx30, imported from Japan, and can't even connect to it with FORScan (like it worked with my old cx8)
Post Reply