2014 Transit Custom 2.2 ABS & Traction & seatbelt light on

[_matt]

ABS & Traction & seatbelt light came on the other day and not went off after a clear with Forscan, no cruise control or hill assist available.

No change in driving/braking feel and speedo readings all fine.

Scanned codes are:

ABS U0401:68-8B - Invalid Data Received from ECM/PCM A
ABS C0031:12-83 - Left Front Wheel Speed Sensor - Short to Battery
ABS C0031:11-8B - Left Front Wheel Speed Sensor - Short to Ground
ABS C0034:12-83 - Right Front Wheel Speed Sensor - Short to Battery
ABS C0034:11-8B - Right Front Wheel Speed Sensor - Short to Ground

Checked fuses for ABS and all fine replaced them anyway.
Fluids all showing correct levels.

Both ABS sensor wires to be replaced? or could it be something else to try first?

Screenshots below:

[cenchaz]

Hi matt have you got any where with this problem? im having the same issue with a transit atm. I am thinking of getting the abs module checked out.
i have also checked all fuses and levels. ive also done a quick brake bleed on the scanner to make sure that works and all works fine.
i have also changed the front left sensor aas iam getting no reading from live dats front left.
i am getting U0401:68 code in the air bag system too is this code in yours too?

[_matt]

Yeh, getting that code also,

I think its possibly where the two front wires feed into the abs module, which i think is behind the drivers headlight, need to check there but cant find any decent pictures/diagrams which show where all the wires feed to

[cenchaz]

im sending the abs module off this morning for testing. before i go too deep. ill let you know the outrcome

[rmeeh]

Hello, I ve got the same problem with the same car. For two weeks the error vanished after a motor stop and then acellerating above 75km/h in the 3. gear. But since some days the errors stay permanent. In addition I geht an ESP error, exact that the "hill start assist" does not work. Also start/stop is inactive.
I think so much errors at once may only result from a disturbed CAN communication, isnt it?
Have you solved your problem in the meantime?
-Ralf-

[_matt]

No, error still persists.

Need to chase the wires back first to see where the problem is.