2012 Ford S-Max facelift

Hi,

I have had this intermittent issue for a couple of days now and a read somewhere that the fault could be due to a faulty wheel speed sensor.

After watching a youtube video i tried a couple of tests that were suggested:

I disconnected both of the front wheel sensors and put a meter on the two terminals of each wheel sensors, one was 21.8 ohms and the other was 21 ohms. According to the video the difference is acceptable and would indicate that the Wheel speed sensors are ok?

The second test i did was to check for a voltage going to each sensor and both were in the 12v range.

 

I was hoping that the problem was due to a faulty Wheel speed sensor as they look easy to replace. Perhaps the results of the two tests i carried out were not sufficient to fully eliminate  the wheel speed sensors as the cause?

 

Is anyone familiar with this issue and possibly suggest some likely causes? 

 

Thanks

It'll be the sensor or the hub

4 hours ago, Calabar72 said:

I was hoping that the problem was due to a faulty Wheel speed sensor

You won't get any sensible results checking the ABS wheel speed sensors with a multimeter.

Use FORScan:

On 4/7/2024 at 8:59 PM, unofix said:

FORScan (for use with Windows Laptop) : https://forscan.org/download.html

It's what many Ford owners use including some Ford technicians.

• vLinker FS, cable for laptop: https://www.amazon.co.uk/Vgate-vLinker-Adapter-FORScan-MS-CAN/dp/B0952P4MLP

OR

• OBDLINK EX, cable for laptop: https://www.amazon.co.uk/OBDLINK-EX-FORScan-OBD-Adapter/dp/B081VQVD3F/ref=sr_1_5

For diagnostic use only:

• vLinker FD, for android phone: https://www.amazon.co.uk/Vgate-Bluetooth-vLinker-Scanner-Diagnostic/dp/B08H82WC8L
• vLinker FD+, for iPhone: https://www.amazon.co.uk/Vgate-Bluetooth-vLinker-Scanner-Diagnostic/dp/B08H8JHW2

 

On 9/12/2025 at 3:42 PM, unofix said:

You won't get any sensible results checking the ABS wheel speed sensors with a multimeter.

Use FORScan:

 

Thanks,

I ordered the vLinker FS OBD2 USB adapter and it arrived this morning. After installing Forscan software on my laptop and the driver for the vLinker FS USB adapter I was able to successfully connect to my vehicle and run Forscan diagnostics.

 

My next step is to learn more about how to use the Forscan software and interpret the results of its diagnostics.

 

Can Forscan identify specific components? In my case, should there be a wheel speed sensor fault, is forscan capable of stating "OSF wheel sensor"?

46 minutes ago, Calabar72 said:

Can Forscan identify specific components? In my case, should there be a wheel speed sensor fault, is forscan capable of stating "OSF wheel sensor"?

FORScan will identify a faulty ABS wheel sensor, and which wheel. There will usually be a DTC stored if waning lights such as ABS, ESC and EML have been on during driving.

The DTC's stored will probably show that the EML is not active at the time of checking, but will still show that it has occurred.

EXAMPLE:

DTC:  C0031-15 is front left ABS wheel sensor fault.

18 hours ago, unofix said:

FORScan will identify a faulty ABS wheel sensor, and which wheel. There will usually be a DTC stored if waning lights such as ABS, ESC and EML have been on during driving.

The DTC's stored will probably show that the EML is not active at the time of checking, but will still show that it has occurred.

EXAMPLE:

DTC:  C0031-15 is front left ABS wheel sensor fault.

Thank you for the information, much appreciated .

 

I have multiple DTC's stored after running the read DTC codes in FORscan and non of the DTC's point to an ABS wheel sensor. The DTC's refer to the Anti - Lock Brake System (ABS) Control Module and the Body Control Module.  I have pasted the results below.

=PCM DTC U0415:86-AF===
Code: U0415 - Invalid Data Received From Anti-Lock Brake System (ABS) Control Module

===PCM DTC U0129:00-27===
Code: U0129 - Lost Communication with Brake System Control Module 'A'

===PCM DTC U0129:87-2F===
Code: U0129 - Lost Communication with Brake System Control Module 'A'

===PCM DTC U0418:08-2F===
Code: U0418 - Invalid Data Received from Brake System Control Module 'A'

Module: Instrument Panel Control Module

===END IPC DTC U0401:68-2A===

===IPC DTC U0415:68-2B===
Code: U0415 - Invalid Data Received From Anti-Lock Brake System (ABS) Control Module

Module: Instrument Panel Control Module

===END IPC DTC U0074:88-2B===
===IPC DTC U0422:68-2B===
Code: U0422 - Invalid Data Received From Body Control Module

===IPC DTC U0140:00-2A===
Code: U0140 - Lost Communication With Body Control Module

Module: Remote Function Actuator

===END RFA DTC U0121:00-0A===

===IPC DTC U3006:16-2B===
Code: U3006 - Control Module Input Power 'A' Circuit / Open

 

From the data above would I be right in thinking that I have either a control module issue or a wiring issue? If it is a wiring issue I guess the the first thing I should do is inspect the wiring and connections. Failing that, should I attempt  diagnosing CANbus network issues? or should i just give up and let a pro deal with it? I'm thinking out loud. I don't need my car for a few days and i do like to try and fix things myself :s If i eliminate wiring i am left with modules.

 

Firstly it is important to understand that any DTC that is "Uxxxx xx" is not in itself a fault. It is only indicating that there is a communication issue on the Canbus system. Think of it like interference, and it could be a problem just about anywhere on the network.

The Canbus systems(High Speed, and  Medium Speed) both are terminated at either end of the line by a 120 Ohm resistor. This means that if you measure the resistance of the network at any point you should get a reading of 60 Ohm. If you get a value of 120 Ohm then there is a break in the network.

A very common problem on many older vehicles is the soldering of the instrument cluster IPC which causes many problems with the Canbus network.  I'm not sure if your vehicle is affected by this issue but I'm sure that @rd457 would have a better idea if your 2012 instrument cluster could be one of those with this problem.

On 5/5/2025 at 9:21 PM, unofix said:

OBDII connections.

 

On 12/30/2024 at 3:10 PM, unofix said:

Time to get the multimeter out and start testing the Canbus systems. Both MS and HS should each read 60 Ohm.

There is one 120 Ohm resistor fitted across each pair of canbus wires at the start and finish of the network. So in effect two 120 resistors are fitted in parallel. If there is a break in the wiring then you will only read across one of the resistors which would give a value of 120 instead of 60 Ohms.

 

 

 

This type is affected by the cracked solder joint problem:

This one isn't:

18 hours ago, rd457 said:

This type is affected by the cracked solder joint problem:

This one isn't:

Thanks rd457,

I have the type 4 instrument cluster.

 

On 9/15/2025 at 12:34 PM, unofix said:

 

I took some readings this morning.

 

HS Bus between between pins  6 & 11 measured 61 ohms

MS Bus between pins 2 & 11 changed value each time I took a reading.  63 ohms, 151 ohms and 74ohms

MM Bus between pins 1 & 8 measured 59.6 ohms

 

MS Bus appears to have an issue.  would there be a specific order of fault finding to identify where on the MS bus the fault is?

 

Thanks

 

1 hour ago, Calabar72 said:

HS Bus between between pins  6 & 11 measured 61 ohms    

HS is between pins 6 & 14

1 hour ago, Calabar72 said:

MS Bus between pins 2 & 11 changed value

MS is between pins 3 & 11

1 hour ago, Calabar72 said:

MM Bus between pins 1 & 8 measured 59.6 ohms

MM is between pins 1 & 8

Think you need to check that were measuring the correct pins.

48 minutes ago, unofix said:

HS is between pins 6 & 14

MS is between pins 3 & 11

MM is between pins 1 & 8

Think you need to check that were measuring the correct pins.

Sorry, not sure how i managed to type the incorrect pin numbers

HS Bus between between pins  6 & 14  measured 61 ohms

MS Bus between pins 3 & 11 changed value each time I took a reading.  63 ohms, 151 ohms and 74ohms

MM Bus between pins 1 & 8 measured 59.6 ohms