OBDII connected but no fault codes seen

[Trademan101]

Hi all,

Ford Transit Connect 2012 LWB.

Hoping for some insight.
As per the title, I have some faults appearing on the dash but cannot be seen by two of my scanners (they are just cheapos).

Essentially I have an "ESP Malfunction" warning as well as the ABS icon illuminated. No other "symptoms".

In the past I've had a similar fault (wheel sensor) AFTER the garage has performed work on the brake system (new pads and discs) which is very similar to what's happening this time. Could be a red herring though.

Taking back to the garage has only resulted in a bill and no further information with exception of a belief that the fault lies "within the steering column". Garage would not provide fault codes.

I don't have a huge amount of confidence in the current garage so I am looking for some assistance on the following:

1) any garage recommendations around the Cumbernauld/Glasgow/Airdrie area (not within Glasgow due to the ULEZ).
2) any ideas/workarounds to enable me to see fault codes with my own OBDII?
I've had success with this scanner before but it cannot see a thing. P.s. it CAN see live data (voltages etc) and the connection seems firm and powering up ok. Also fuses fine. Not sure if the code is just beyond the abilities of my scanners.

Any insight would be great, thanks.

[metalworker0]

Forscan - that's what they recommend here .

NOTE: you can use forscan to get correct fault codes with proper explanation of them - a generic fault code reader may be somewhat misleading, or doesn't work

"Forscan" is FREE software that you download to a laptop..you buy the interface cable -- this is just the cable, you need a laptop)
You can join the forscan forum ..again free, to get the software and more answers.

https://forscan.org/forum/

Then you come here list the fault codes here ..and we will try to work out the problem.

ESP faults are usually down to An ABS sensor fault. wrong tyres fitted (they all have to be the same), underinflated tyres, most brake related fault codes are usually down to the abs sensors or reluctor rings... they give the speed of the wheels so lots of other stuff dependent on speed readings from the ABS system.

With forscan you can drive along and have it plot graphs in real time helping you spot the ABS sensor that is at fault. they may have fixed an ABS fault in the past ..but that does not prevent another occurring on another wheel .

The transit connects have the reluctor rings built into the wheel bearings, ive heard of this type failing on all cars and vans ..not quite sure how they fail cause haven't had that problem myself. think when they fail it is due to wheel bearing breaking up and spreading metal swarf debris around them so ..you are not getting the regular on/off chopping signal, but a confused one . which you'll be able to see on forscan.

You may be able to swap the sensors from one wheel to the other and see the fault swaps over to the other wheel ...that proves its the sensor.

ESP - Also the system is linked up with steering wheel angle sensor, that is under the steering wheel and may be reliant on the clock spring ribbon cable being in good order.

All electronics of your van, will not function correctly, if they have a low voltage supply to them from a bad battery or earths.

if non of that works out ..then you are looking at the module that is located somewhere behind the dash. this is a yaw rate sensor.

From google

The yaw rate sensor, measures the vehicle's rotation around its vertical axis and sends this information to the ABS control module. It uses a piezoelectric crystal to measure changes in acceleration and deceleration of the vehicle's body.

all the best.mark

[Trademan101]

Thanks Mark

I do remember seeing the recommendations here years ago for Forscan when I did more dabbling back then. Totally forgot all about it.

I'll certainly look into it as I fear it is a dead end with what I've got available at my end. Thanks for the heads-up.

In so far as the battery system. I think all is sweet there as newish battery and alternator (but not so new that I suspect them, if that makes sense). However I won't dismiss them as possible problems.

Thanks again and will look into Forscan for the time being. Cheers

[Trademan101]

Actually one more Q for yourself Mark or anyone else that uses Forscan.
I see there is an Android version. Anyone with experience on that version? Recommend? Or stick with the windows/laptop version?

[Trademan101]

Hi Mark or anyone else reading.
I have went ahead and ordered the OBDII cable to android as that would be the best option for me.
I've looked into your links and online and downloaded "FORScan Lite 1.5.27.3 for Android (Core 2.3.66) Independent Edition" (I also downloaded the Google play version due to android blocking).

However reading online there seems to be issues and comments around licensing/costs?
I tried the Google play version as well and although it's now downloaded I am receiving the error the application "fails to initialize".

So:

• Is there actual costs to buy a license? (You mentioned the software was free but perhaps you were only referring to the windows version?)
• Any idea about the software error? The FORScan forum FAQ is not much assistance.

Cheers, Andrew

[metalworker0]

i dont know a thing about android ..only that it's --- Bluetooth ..am i right ... you cant rely on it, no solid connection and commands - so ..but iffy i read...it's why i don't mention it in the forscan posts


and there have been issues here ...well read the mk6 forum, knobby telling people to use latptop only.

that's all i know

all the best.mark