FORScan forum

I'll carry on here for now.
So I restarted Forscan after deleting any profiles stored. Upon reconnection I did get a DTC in the PCM.
https://limewire.com/d/fegYY#su2ywmTBpW
Tried lots of things, even put the old PCM back in. Got a DTC saying car immobilised because of PATS problem. The PCM configuration didn't shoiw with that PCM as well.
Put the new PCM back in and no DTCs this time but still no configuration available, see screenshot
https://limewire.com/d/OQcRn#B6Svih5cdH
The 2 PCMs are different. Original 3R23-12650-AH, ABU 212, new 3R23-12650-AAE, ABU-242
Thinking if that was a problem, PATS would not work and I wouldn't be able to drive it. Maybe a cable problem? Should I try Forscan on another laptop?

markb7 wrote: Sun Apr 05, 2026 2:18 am I'll carry on here for now.
So I restarted Forscan after deleting any profiles stored. Upon reconnection I did get a DTC in the PCM.
https://limewire.com/d/fegYY#su2ywmTBpW
Tried lots of things, even put the old PCM back in. Got a DTC saying car immobilised because of PATS problem. The PCM configuration didn't shoiw with that PCM as well.
Put the new PCM back in and no DTCs this time but still no configuration available, see screenshot
https://limewire.com/d/OQcRn#B6Svih5cdH
The 2 PCMs are different. Original 3R23-12650-AH, ABU 212, new 3R23-12650-AAE, ABU-242
Thinking if that was a problem, PATS would not work and I wouldn't be able to drive it. Maybe a cable problem? Should I try Forscan on another laptop?

According to your Screen shots you are using 2.3.70 which is not PCM/VID Block configuration capable! PCM Configuration and Firmware VID block programming require version 2.4.xx(Currently 2.4.22)!

This version is available only to Paid license members who have Registered and logged in to the Forum with the Paid members token that comes with the Paid license activation! With that token registered login you will see a "Private Beta test" thread( Top thread Sticky) that contains the download link for the current 2.4.xx version of FORScan!

The other fly in this ointment has to do with the old age of the vehicles you working on! Before about 2004 the network the PCM is on is called PWM(Check your Modules tab) and FORScan has not yet developed the PCM Firmware/VIDblock configuration for these PWM Networked PCM's!

If the PCM you are working with is on the HSCAN network there is a chance VIDBlock and Firmware Update configuration will be available under PCM configuration and programming using 2.4.xx(.phf file Based from ~2004 to 2008)!
Even if it is, be advised that in order to change any thing in the VIDBlock it requires a full PCM erase and a re-upload of the all firmware files with the requested changes(Very Dangerous as any interruption/low battery voltage Laptop sleep can brick the PCM)!

Firmware/VIDblock programming also requires a Paid license!

Changing laptops will not be any help(Your screen shots show the Laptop or the adapter is not the problem) and you would have to revoke and move your Paid license!

Just some info as to what you are getting yourself into!

@ tractmec

I was about to tell him to download / purchase: FORScan v2.4.22 beta and try again


FORScan works on a 2003 BA Falcon. It is highly effective for reading/clearing diagnostic trouble codes (DTCs), monitoring live data, and performing module programming or PATS key resets. A high-speed USB OBD2 adapter (like VGate vLinker FS) with MS-CAN/HS-CAN support is required for full access.


Forscan 1 Year Licence

https://forscan.org/support/show_conten ... id_expired

thanks for the reply.
The car is quite drivable at the moment. The process of vid-block editing sounds interesting so will prpbably try it out. I have a paid licence. Oh, how I miss my old EH Holden!

Well, it worked! Speed correct and new firmware installed. Thanks guys.
Downloaded beta version from thread and it installed over the existing Forscan program keeping registration which was good.
Hooked laptop up to car and the PCM configure appeared. Not many options to configure. Changed diff ratio to 3.45, speed reading to ABS only, oxygen to normal (other option was retard).
Clicked on write, Forscan then said it would erase everything and install latest firmware with my changes. Forscan downloaded the files and installed. Nearly had a problem as my car battery was nearly flat from having the ignition on and off all day!
Log:
(OK) [16:11:29.461] PCM Vehicle ID block configuration has been started
(WARN) [16:11:30.613] Low battery voltage. Please charge the battery and try again
(ERR) [16:17:20.938] Unable to rewrite VID block
(OK) [16:17:38.750] Service procedure completed successfully.
(OK) [16:18:18.308] PCM Module firmware update has been started
(WARN) [16:18:18.319] Reading vehicle info...
(WARN) [16:18:18.392] Unable to read current firmware p/n, use assembly p/n: HAANGA3
(WARN) [16:18:18.395] Unable to read current firmware p/n, use assembly p/n: 35601200
(WARN) [16:18:18.402] Redirect from the function Vehicle ID block configuration...
(WARN) [16:18:50.741] Downloading firmware files from the Internet...
(OK) [16:18:54.862] Downloading HAANGF5: OK
(OK) [16:18:54.872] Downloading 35601200: OK
(ERR) [16:19:18.406] Service procedure has been interrupted
(OK) [16:19:37.465] PCM Vehicle ID block configuration has been started
(ERR) [16:19:39.370] Service procedure has been interrupted
(OK) [16:19:46.353] PCM Vehicle ID block configuration has been started
(ERR) [16:19:48.268] Service procedure has been interrupted
(OK) [16:21:41.689] PCM Vehicle ID block configuration has been started
(WARN) [16:21:42.778] Low battery voltage. Please charge the battery and try again
(ERR) [16:23:57.257] Unable to rewrite VID block
(OK) [16:24:13.010] Service procedure completed successfully.
(OK) [16:24:15.541] PCM Module firmware update has been started
(WARN) [16:24:15.552] Reading vehicle info...
(WARN) [16:24:15.633] Unable to read current firmware p/n, use assembly p/n: HAANGA3
(WARN) [16:24:15.636] Unable to read current firmware p/n, use assembly p/n: 35601200
(WARN) [16:24:15.650] Redirect from the function Vehicle ID block configuration...
(WARN) [16:24:55.887] Total size: 1.44 Mb. Estimated duration: 2m - 4m
(OK) [16:25:06.513] FEPS programming signal has been applied
(WARN) [16:25:10.082] Loading firmware to ECU: Strategy HAANGF5
(WARN) [16:25:10.083] Erasing sector AA (1/1)...
(WARN) [16:25:28.011] Loading block 1/2...
(WARN) [16:27:25.138] Loading block 2/2...
(OK) [16:28:32.284] Firmware loaded successfully
(WARN) [16:28:32.313] Loading firmware to ECU: Strategy/#2 35601200
(WARN) [16:28:32.322] Erasing sector BB (1/1)...
(WARN) [16:28:32.837] Loading block 1/2...
(WARN) [16:28:43.168] Loading block 2/2...
(OK) [16:30:10.902] Firmware loaded successfully
(OK) [16:30:22.021] Please wait...15 seconds
(OK) [16:30:48.213] Service procedure completed successfully.

Extra note. My new PCM was from a 2005 fairmont so that probably helped

markb7 wrote: Sun Apr 05, 2026 9:43 am Extra note. My new PCM was from a 2005 fairmont so that probably helped

I neglected in my reply to relate that there should always be a 10 amp minimum charger or external power supply on the battery and the laptop Charger plugged into power whenever this process is attempted. This is by personal experience and as per this topic: viewtopic.php?f=13&t=18751! I am considering you very lucky that FORScan interrupted the process due to low battery voltage, before the PCM was erased(Bricked/unresponsive, possibly permanently, PCM if process is interrupted at this point)!

I saw no reference in your post as to the VIN field being changed to match the vehicle you are installing the 2005 PCM into! The VIN is in a writable/re-writable field at the beginning/top of the VID block and very likely would have contained the VIN from the original 2005 Fairmont!
Leaving that VIN unchanged could cause VIN/Configuration mismatch DTC's such as U2100 in any other modules that communicate with the PCM! To change it now if you have not, you will have to do this process all over again!
Pats Initialization may not complete either!

I am somewhat surprised that this has worked this well as crossing vehicle model lines and model years usually causes all kinds of incurable mismatch U code DTC's!

Let us know how this experiment works!

f-wolf wrote: Sat Apr 04, 2026 10:26 pm

markb7 wrote: Sat Apr 04, 2026 9:06 am Hi,
I have a 2003 BA Falcon wagon and put a 2005 Fairmont Ghia PCM into it. Got everything working ok, but when I went for a drive discovered that when travelling at 60kph the speedo only reads 40kph. Do I need to install new VID files (whatever they are)? Cannot see PCM in configuration menu on Forscan. Have the VGATE VLINKER FS USB OBD2 ADAPTER from OBD2 Aust.

Re, Cannot see PCM in configuration menu on Forscan

See if deleting the existing profile will help ...After you done...Restart Forscan.


https://limewire.com/d/J8xSa#w6BUSjHGpa

The standard tyre size for a 2003 BA Ford Falcon Wagon (XT or Futura) is 215/60R 16.

The standard tyre size for a 2005 Ford Fairmont Ghia (both BA II and BF models) is 225/50R 17.


Based on the standard specifications for a 2003 BA Falcon wagon (non-turbo, non-XR), the standard rear axle ratio is typically:

3.45:1 (Often paired with the 4-speed automatic or manual transmission for base XT models)

The 2005 Ford Fairmont Ghia (BA Mk II) generally came equipped with a 2.73:1 axle ratio as standard.


See if this will help you ...Any changes ...Make sure you write down...Before and after !!!

How to:

https://limewire.com/d/IJudK#AeOrwezl4F

Be careful about what info you get from some forums or via AI. Only part of the info is correct
3.23 is the most common axle ratio if 4 speed auto, including Fairmont unless it was optioned with the ZF6. Most were only 4 speed auto
3.45 if 5 speed manual & there are far less manual
3.73 if BF 6 speed manual
2.73 if BF & fitted with the 6 speed auto

Usually the speedo error is related to the wrong speed source being selected in the VID block. This inputs the wrong count, so calculates the wrong output to the cluster

A new VID file isn't required. You adjust the settings in the VID block.

You need a current paid licence & 2.4.22beta to program the VID block & complete MFU