6 hours ago, Neb_engineer said:

So I looked, and I don't seem to have software update as an option. I tried rebooting it and it stayed the same.

You need the paid license then download the version that allows updates

3 hours ago, DaveT70 said:

You need the paid license then download the version that allows updates

I have the paid licence, I'm on version 2.3.63

So has anyone got anymore ideas? I'm really scratching my head with this one.

I got the similiar problem. It starts when i changed normal cluster to digital.

On 8/22/2025 at 10:44 AM, Neb_engineer said:

I have the paid licence, I'm on version 2.3.63

the decent Paid version that does updates is 2.4.18 ?

 

FORScan v2.4.18 beta

Changelog (full change history can be found in FORScan.Changelog.2.4.txt available in the FORScan installation folder):

2.4.18 beta, 2025-05-16
+ v2.3.66 functionality
+ Firmware database update
+ Support Black OAK/Green OAK 448/512K TCM programming on 2003-2007 F-Series/E-Series (experimental!)
- bug: incorrect recongition HEX/PHF files in some cases

 

1. The user acknowledges that he understands and accepts all the risks, requirements and limitations of using version 2.4 listed above, and agrees to use the product on an AS IS basis (that is claimed in FORScan End User License Agreement but nobody reads it anyway).

2. The user is paid Extended License owner.

3. The latest v2.4 is available for download in the hidden forum (for registered users only).

54 minutes ago, Botus said:

the decent Paid version that does updates is 2.4.18 ?

 

FORScan v2.4.18 beta

Changelog (full change history can be found in FORScan.Changelog.2.4.txt available in the FORScan installation folder):

2.4.18 beta, 2025-05-16
+ v2.3.66 functionality
+ Firmware database update
+ Support Black OAK/Green OAK 448/512K TCM programming on 2003-2007 F-Series/E-Series (experimental!)
- bug: incorrect recongition HEX/PHF files in some cases

 

1. The user acknowledges that he understands and accepts all the risks, requirements and limitations of using version 2.4 listed above, and agrees to use the product on an AS IS basis (that is claimed in FORScan End User License Agreement but nobody reads it anyway).

2. The user is paid Extended License owner.

3. The latest v2.4 is available for download in the hidden forum (for registered users only).

The only issue with using a beta version is, I really don't want to risk a forscan bug causing my car to get bricked 

.... any module updating carries some risk - but only that version is currently recco as the one to try...   anyone that has updated any ford using that tool I believe has to use the beta version

its the version they actually develop, tweak and offer support on, based on success of updating people are having - if you want to update any Ford at home you should be reading and following the experts advice and success and or failure using that edition or any later ones...

 

you were trying with an old version from Oct 2024 that doesn't do updates - the tool I linked is three versions newer from May 2025 - if you study the release notes for the one I pointed out or the later versions of the simple tool you were trying, there are lots of bug fixes and improvements in those three updates

in addition I believe the advice from others above, was to use forscan to check for updates - not necessarily try to update 

 

8 hours ago, Botus said:

.... any module updating carries some risk - but only that version is currently recco as the one to try...   anyone that has updated any ford using that tool I believe has to use the beta version

its the version they actually develop, tweak and offer support on, based on success of updating people are having - if you want to update any Ford at home you should be reading and following the experts advice and success and or failure using that edition or any later ones...

 

you were trying with an old version from Oct 2024 that doesn't do updates - the tool I linked is three versions newer from May 2025 - if you study the release notes for the one I pointed out or the later versions of the simple tool you were trying, there are lots of bug fixes and improvements in those three updates

in addition I believe the advice from others above, was to use forscan to check for updates - not necessarily try to update 

 

So, I have checked, this version doesn't give me an IPC update option. Also I enabled dte Calculation menu, and initially it was stuck in towing mode, but then I drove and it went to normal mode (no change in dte value though)

So the more I look, the more I'm thinking the car may have been clocked. To fix this, would it be as simple as using forscan to put the IPC to the same mileage as the pcm?

For anyone who looks back at this thread in the future, I found a work around by setting the fuel level reference in IPC from pcm to IPC, then adjusted the fuel tank capacity in both litres and gallons to what the user manual said. Then I wrote the changes and my dte on the trip computer now functions as intended.

Update - the second.

The things done in the previous update gave a functioning DTE readout, however they also made the fuel gauge read wrong. I looked back at the mileage difference between the PCM and the IPC (after this time switching forscan to show in miles) and found the discrepancy was only 1000 miles. I thought with such a small amount, what have I got to lose? So I updated the mileage on the IPC to be the same as PCM which also changed the other modules to the same mileage. The DTE then changed to 165miles (I had 3/4 in the tank) then I drove for a bit, the DTE  suddenly dropped to 9 miles then worked down to 0 miles (still had 3/4 of a tank) then stayed on 0 miles for about 20 miles but then after that eventually started going up mile by mile until it reached the real DTE value. And now works exactly as it should. This update is mainly to benefit other people as some people unhelpful on the Facebook groups and other forums say if your dash mileage has been clocked or it is disagreeing with your PCM then the cluster's firmware has been corrupted, this is just not true.

Hi Ben, I Have the same issue with my 2019 (68 plate) Mk4 Ford Focus Estate 1.5 Tdi. When Brimmed to the max i'm only managing to get 180miles of range, but the car is getting 50mpg pretty much all the time or better.

Did you have any luck into what was causing this? The needle is accurate and so is the fuel light... just not the range-until-empty.

Thank you, Harvey 

On 1/9/2026 at 11:57 AM, Harvmk4fordfocus1.5tdi said:

Hi Ben, I Have the same issue with my 2019 (68 plate) Mk4 Ford Focus Estate 1.5 Tdi. When Brimmed to the max i'm only managing to get 180miles of range, but the car is getting 50mpg pretty much all the time or better.

Did you have any luck into what was causing this? The needle is accurate and so is the fuel light... just not the range-until-empty.

Thank you, Harvey 

Hi Harvey, if you have read my post "update the second" it says what I did to fix it. If you haven't already, get a vlinker or compatibile interface with forscan, plug your car in. See if there is a mileage difference between PCM miles and IPC miles. If the IPC miles are lower than pcm (more then a couple of miles) then that's most likely your issue. The other modules get their miles from IPC, it's only pcm and IPC that keep track of mileage.

On 11/11/2025 at 7:44 PM, Neb_engineer said:

Update - the second.

The things done in the previous update gave a functioning DTE readout, however they also made the fuel gauge read wrong. I looked back at the mileage difference between the PCM and the IPC (after this time switching forscan to show in miles) and found the discrepancy was only 1000 miles. I thought with such a small amount, what have I got to lose? So I updated the mileage on the IPC to be the same as PCM which also changed the other modules to the same mileage. The DTE then changed to 165miles (I had 3/4 in the tank) then I drove for a bit, the DTE  suddenly dropped to 9 miles then worked down to 0 miles (still had 3/4 of a tank) then stayed on 0 miles for about 20 miles but then after that eventually started going up mile by mile until it reached the real DTE value. And now works exactly as it should. This update is mainly to benefit other people as some people unhelpful on the Facebook groups and other forums say if your dash mileage has been clocked or it is disagreeing with your PCM then the cluster's firmware has been corrupted, this is just not true.

Hi Ben, thanks for this. I have a 2022 1.5 tdci kuga and it’s showing the exact same symptoms. Quick question, how easy is this for a novice? Is it pretty straight forward?