I have an issue, where every time I start the car, I get "Tyre Pressure Sys Malfunction - Service Required" show on the display.
Should probably start by saying it's a 61 plate Mk3 2011 Ford Focus (But Ford website shows it as a 2012)...
Having used ForScan (extended licence), it shows ABS fault U1031:41-2B - Deflation Detection System, General Checksum Failure
I was led to believe that the ABS module most likely had incorrect data, and that I should check the AsBuilt data is correct.
I've looked at the AsBuilt data for the ABS, and it shows:
760-01-01: 0000-0000-0069
760-01-02: 0000-0000-006A
760-01-03: 0000-0000-006B
760-01-04: 0000-006C
Looking on https://www.motorcraftservice.com/AsBuilt and using my VIN number WF0KXXGCBKBU47458, it shows no AsBuilt data for the ABS module
I am assuming that either the ABS data is incorrect, since it has just a bunch of zeros and a checksum, or, it's all zeros because there is no AsBuilt data showing on MotorCraftService.
I used ForScan to disable the DDS in Central Configuration, and the warning (along with the warning light) has gone, but, if the car was originally equipped to use DDS, I would like to keep it if possible.
For what it's worth, I've also checked the Live Data and monitored the Wheel Speed Sensors on ForScan, which appear to be reporting correctly, all 4 wheels.
As a side note, when DDS was enabled, if I go to Driver Assist > Tyre Deflation > and Hold 'OK', the progress bar gets all the way to the end as normal, but always results in "Tyre Pressure not stored".
Is anybody able to shed some light on this issue at all please?
I was told to use ForScan to select the "BCMii (Module Configuration)" option and check to see if there is anything in there that may not look correct (wrong DDS/TPMS option for example, and check to see if any TPMS module ID numbers are saved), but when trying to select this option, I get told "Service procedure has been interrupted"
Tyres are correct size, and also show correct size in ForScan, and wheels are also correct.
Ford Focus - Service Required - Unable to use ForScan to rectify
-
avisonjohn
- Posts: 3
- Joined: Sat May 28, 2022 3:24 pm
- Vehicle: 2005 1.4 Fusion
-
tractmec
- Posts: 2109
- Joined: Thu May 26, 2016 11:43 pm
- Vehicle: F150 5.4 Triton 2005 Fusion 3.0 2010
Re: Ford Focus - Service Required - Unable to use ForScan to rectify
This is just a suggestion as I do not have a 2011/2012 focus here to check if the TPMS or DDS is contained in the following, but the Focus line is CC or Central Configuration and much of the Module configuration is done through Engineering Modes which if you open the BCMii(Main) Configuration you should find a drop down menu box(top left corner) with one or probably two engineering mode configurations! These modes in central configuration are where most of the plan English Configurations for all modules are stored and Configuration changes are made and very little is done in AsBuilt or with Individual Module Configuration in Central Configuration vehicles(Focus/Fiesta/Transit)!avisonjohn wrote: Mon Feb 24, 2025 12:57 pm I have an issue, where every time I start the car, I get "Tyre Pressure Sys Malfunction - Service Required" show on the display.
Should probably start by saying it's a 61 plate Mk3 2011 Ford Focus (But Ford website shows it as a 2012)...
Having used ForScan (extended licence), it shows ABS fault U1031:41-2B - Deflation Detection System, General Checksum Failure
I was led to believe that the ABS module most likely had incorrect data, and that I should check the AsBuilt data is correct.
I've looked at the AsBuilt data for the ABS, and it shows:
760-01-01: 0000-0000-0069
760-01-02: 0000-0000-006A
760-01-03: 0000-0000-006B
760-01-04: 0000-006C
Looking on https://www.motorcraftservice.com/AsBuilt and using my VIN number WF0KXXGCBKBU47458, it shows no AsBuilt data for the ABS module
I am assuming that either the ABS data is incorrect, since it has just a bunch of zeros and a checksum, or, it's all zeros because there is no AsBuilt data showing on MotorCraftService.
I used ForScan to disable the DDS in Central Configuration, and the warning (along with the warning light) has gone, but, if the car was originally equipped to use DDS, I would like to keep it if possible.
For what it's worth, I've also checked the Live Data and monitored the Wheel Speed Sensors on ForScan, which appear to be reporting correctly, all 4 wheels.
As a side note, when DDS was enabled, if I go to Driver Assist > Tyre Deflation > and Hold 'OK', the progress bar gets all the way to the end as normal, but always results in "Tyre Pressure not stored".
Is anybody able to shed some light on this issue at all please?
I was told to use ForScan to select the "BCMii (Module Configuration)" option and check to see if there is anything in there that may not look correct (wrong DDS/TPMS option for example, and check to see if any TPMS module ID numbers are saved), but when trying to select this option, I get told "Service procedure has been interrupted"
Tyres are correct size, and also show correct size in ForScan, and wheels are also correct.
The IPC(backup) should also contain a backup of those configurations!
Entering these Modes to change a configuration will require obtaining a Secondary Boot loader(SBL) file from either the FORScan Paid Data Base or From motorcraftservice.com!
See this topic for more CC information: viewtopic.php?f=16&t=1932
-
avisonjohn
- Posts: 3
- Joined: Sat May 28, 2022 3:24 pm
- Vehicle: 2005 1.4 Fusion
Re: Ford Focus - Service Required - Unable to use ForScan to rectify
Thanks for the reply.tractmec wrote: Mon Feb 24, 2025 5:50 pmThis is just a suggestion as I do not have a 2011/2012 focus here to check if the TPMS or DDS is contained in the following, but the Focus line is CC or Central Configuration and much of the Module configuration is done through Engineering Modes which if you open the BCMii(Main) Configuration you should find a drop down menu box(top left corner) with one or probably two engineering mode configurations! These modes in central configuration are where most of the plan English Configurations for all modules are stored and Configuration changes are made and very little is done in AsBuilt or with Individual Module Configuration in Central Configuration vehicles(Focus/Fiesta/Transit)!avisonjohn wrote: Mon Feb 24, 2025 12:57 pm I have an issue, where every time I start the car, I get "Tyre Pressure Sys Malfunction - Service Required" show on the display.
Should probably start by saying it's a 61 plate Mk3 2011 Ford Focus (But Ford website shows it as a 2012)...
Having used ForScan (extended licence), it shows ABS fault U1031:41-2B - Deflation Detection System, General Checksum Failure
I was led to believe that the ABS module most likely had incorrect data, and that I should check the AsBuilt data is correct.
I've looked at the AsBuilt data for the ABS, and it shows:
760-01-01: 0000-0000-0069
760-01-02: 0000-0000-006A
760-01-03: 0000-0000-006B
760-01-04: 0000-006C
Looking on https://www.motorcraftservice.com/AsBuilt and using my VIN number WF0KXXGCBKBU47458, it shows no AsBuilt data for the ABS module
I am assuming that either the ABS data is incorrect, since it has just a bunch of zeros and a checksum, or, it's all zeros because there is no AsBuilt data showing on MotorCraftService.
I used ForScan to disable the DDS in Central Configuration, and the warning (along with the warning light) has gone, but, if the car was originally equipped to use DDS, I would like to keep it if possible.
For what it's worth, I've also checked the Live Data and monitored the Wheel Speed Sensors on ForScan, which appear to be reporting correctly, all 4 wheels.
As a side note, when DDS was enabled, if I go to Driver Assist > Tyre Deflation > and Hold 'OK', the progress bar gets all the way to the end as normal, but always results in "Tyre Pressure not stored".
Is anybody able to shed some light on this issue at all please?
I was told to use ForScan to select the "BCMii (Module Configuration)" option and check to see if there is anything in there that may not look correct (wrong DDS/TPMS option for example, and check to see if any TPMS module ID numbers are saved), but when trying to select this option, I get told "Service procedure has been interrupted"
Tyres are correct size, and also show correct size in ForScan, and wheels are also correct.
The IPC(backup) should also contain a backup of those configurations!
Entering these Modes to change a configuration will require obtaining a Secondary Boot loader(SBL) file from either the FORScan Paid Data Base or From motorcraftservice.com!
See this topic for more CC information: viewtopic.php?f=16&t=1932
Sadly, this is exactly what I have used to change from "DDS" to "Not Installed", in order to get rid of the warning message and the light, but doing this obviously would mean that I'm just disabling the system instead of fixing the issue.
I was suspecting that somebody previously may have messed with this exact screen, which is why I wanted to check the AsBuilt data to see if I could restore it to exactly how it was originally.
-
avisonjohn
- Posts: 3
- Joined: Sat May 28, 2022 3:24 pm
- Vehicle: 2005 1.4 Fusion
Re: Ford Focus - Service Required - Unable to use ForScan to rectify
Still having this issue. I've put everything back to how it should be, but still have an issue with Forscan showing Invalid Checksum error on the ABS/DDS module.
Would this maybe need reflashing, and if so, if this something that Forscan is capable of doing?
Would this maybe need reflashing, and if so, if this something that Forscan is capable of doing?
-
tractmec
- Posts: 2109
- Joined: Thu May 26, 2016 11:43 pm
- Vehicle: F150 5.4 Triton 2005 Fusion 3.0 2010
Re: Ford Focus - Service Required - Unable to use ForScan to rectify
The only thing I have noticed and like you I find it unusual that the ABS AsBuilt is all Zeros! The Check sums normally are the last two characters and would be normally calculated from the other characters in the line!avisonjohn wrote: Sat Mar 08, 2025 11:34 pm Still having this issue. I've put everything back to how it should be, but still have an issue with Forscan showing Invalid Checksum error on the ABS/DDS module.
Would this maybe need reflashing, and if so, if this something that Forscan is capable of doing?
In My 2010 Fusion, the VIN is encoded in the first 4 lines in Hex code, in the ABS Asbuilt configuration and I have found this VIN Hex encoding in many ABS modules as well as some others like Side Object detection Left and Right
(SODL 7C4 and SODR 7C6) and As well as some later M.Y. PCM's under address 7E0!
Example: Using the beginning of my Fusion VIN as 3FAHP
760-01-01 3346 4148 50 with Check sum BB as the last two characters! In Hex 3=33 F=46 A=41 H=48 P=50
Your Focus will of course encode with different hex characters(I have posted on this VIN Hex encoding in AsBuilt previously on the Forum)
The above would look like this in the first line and the rest of the VIN fitting into the next lines:
760-01-01 3346 4148 50 BB The check sum would be recalculated so it would be alright to ignore it.
760-02-01
760-03-01
760-04-01
Your Focus will be different encoding numbers! The Check sum can be ignored and will likely result in a Checksum warning but will usually calculate/encode without a problem!
You will need a Hex editor in order to calculate your VIN correctly! I use a program in Windows called 'NotePad++' and you have to download and install the Hex editor plug in! See here: https://notepad-plus-plus.org/!
No Idea why the ABS is not showing an AsBuilt encoding at MotorcraftService/fordserviceinfo.com but it is not unprecedented either!
My only Speculation(and it may be wrong) is that some one has replaced the ABS module at some point(new ones come blank as a rule and used ones would or should carry the original vehicles encoding) and was never programmed or at least the AsBuilt was not filled or they could not get any thing to work properly unless the Asbuilt was zeroed(every thing turned off, no VIN or disabled)!
Not sure if this is the problem, all I can say is that the Asbuilt with all zeros does seem odd and Encoding the Vehicles VIN into those 4 lines would be something I would try first!
New Modules are usually programmed at the dealer with IDS PMI in both Calibration and with Asbuilt(This may be why the Asbuilt is still All Zeros as there was no Asbuilt at Ford service to install but that is still my speculation as the process in IDS PMI is to Inhale the Original data first unless the Original is unavailable as in Dead module)! The fact that the ABS works mostly correctly except for TPMs would seem to suggest that the Calibration File section has at least been done!
You would need to have FORScan version 2.4.17Beta installed(Private thread in the Beta test section for Paid members only) in order to check for installed calibration Files(FORScan calls this Firmware Updates)!
There are also several AsBuilts I have come across that must have the VIN encoded with the Beginning of the VIN starting on the last line of the Asbuilt as in below example:
760-04-01 3346 4148 50 BB and ascending up to and finishing at 760-01-01! I even ran across one that needed to be done backwards as well as upside down as in:
760-04-01 50 4148 3346 BB etc.
Cannot say if this either or any one of those and who ever was trying to work this and did not know any of this, just gave up and zeroed everything(would be the safest thing actually so make sure you have the ABS Zeroed Asbuilt saved as backup so you can at least return it to that if none of this speculation works)!
Again just a semi educated guess or maybe just Idle speculation!!? Difficult to determine without any data from Motorcraftservice!
Beyond that little bit of speculation I have nothing further to add!