Ranger Mods

Hi all, first post! I have a 2013 ford ranger owned for 2 flawless years of motoring till now. Got one of those lovely intermittent problems! Started a few days ago, going along and wouldnt rev past 2000, then kangarooed a little and carried on like normal... presumed fuel issue so replaced fuel filter and flushed through with injector cleaner (bit of water and gunk in housing) filter not over dirty.. last changed 6 months ago. but issue has reoccurred a few times and feels sluggish even when it will rev up fully. No lights on dash btw... Any ideas appreciated. Have got a forscan on order so will hopefully find something on there? although not used one before so any advice gratefully received! Cheers

What dongle are you doing to get to connect with Forscan?

A Scanguage or OBDLink MX are the better ones.

I got a bbflyOBD Vint elm327 with the hs/ms switch.. it said it was compatible for the forscan, although the forscan keeps asking to put it in hs mode, (which it already is) is that normal? Cheers


Sent from my iPhone using Tapatalk

Start with the basics, good first thought with the fuel filter, what about your air filter? also clean the MAF sensor. If you have ForScan try doing some real time logging and see if you can capture what the sensors are doing when its dropped out. It sounds like its going in to limp mode and that would normally throw a code and an error light on the dash.

The next thing would be a split inter-cooler hose, either side will cause a similar issue, but again it would likely throw a code. Maybe a faulty sensor.

What model and year is your Ranga?

sgould wrote: ↑Mon Jun 18, 2018 4:56 pm I got a bbflyOBD Vint elm327 with the hs/ms switch.. it said it was compatible for the forscan, although the forscan keeps asking to put it in hs mode, (which it already is) is that normal? Cheers


Sent from my iPhone using Tapatalk

flick the switch to the opposite of what position its in now to get it to HS mode. For me its in the DOWN position for HS

The ELM327 may be compatible with Forscan, but not the best to use on a Ranger.

I can't read all of the modules.

The better choice would be either a Scanguage or OBDLink MX.

ira11y wrote:Start with the basics, good first thought with the fuel filter, what about your air filter? also clean the MAF sensor. If you have ForScan try doing some real time logging and see if you can capture what the sensors are doing when its dropped out. It sounds like its going in to limp mode and that would normally throw a code and an error light on the dash.

The next thing would be a split inter-cooler hose, either side will cause a similar issue, but again it would likely throw a code. Maybe a faulty sensor.

What model and year is your Ranga?

Thanks for the replies! Yep air filter is good, will look into the maf sensor, I did a scan on forscan will attach the first read out later when back from work.. no codes that were associated with issue. Which modules/pids would be the best to stream? Hoses are good, as I said when it clears its throat it will drive as normal so hoses etc would give a consistent problem? Again many Thanks!

2013 2.2 ranger and I’ve tried the switch in both positions.. will look at the other adaptors suggested..


Sent from my iPhone using Tapatalk

This is from the first connection


Sent from my iPhone using Tapatalk

Makes sense.

PCM fault code is water in fuel. Drain replace fuel, replace filter and drain water from bottom of filter.

saeb wrote:Makes sense.

PCM fault code is water in fuel. Drain replace fuel, replace filter and drain water from bottom of filter.

All been done, low pressure fuel lines been flushed. Still showing same symptoms, consistently restricted to 2000 rpm when stationary. Dips depending on load when driving. Idles perfectly, starts perfectly. Showed it to local garage today he is also stumped have booked it in with a ford specialist next week.


Sent from my iPhone using Tapatalk

Have you cleared the fault codes though? The fault code states water in fuel, so the vehicle thinks there is water in fuel. Until you clear the fault code then it will still think there is water in fuel. If you clear it and it comes straight back then the bowl has not been drained properly of the water.

If problem persists then I would say either plug is not plugged back in or a faulty water in fuel sensor.

saeb wrote:Have you cleared the fault codes though? The fault code states water in fuel, so the vehicle thinks there is water in fuel. Until you clear the fault code then it will still think there is water in fuel. If you clear it and it comes straight back then the bowl has not been drained properly of the water.

If problem persists then I would say either plug is not plugged back in or a faulty water in fuel sensor.

No I didn’t actually, there is no light on the dash though, would that code give those symptoms? I will definitely try it in the morning though! Thanks


Sent from my iPhone using Tapatalk

I can only go by your fault codes as I assume you did the scan after the repairs were made?

I will not guarantee a fix bit I would like you to clear all the fault codes with Forscan as at least then you can list any new fault codes that do come up. So please do list them after a clear, a drive, a re scan.

saeb wrote:I can only go by your fault codes as I assume you did the scan after the repairs were made?

I will not guarantee a fix bit I would like you to clear all the fault codes with Forscan as at least then you can list any new fault codes that do come up. So please do list them after a clear, a drive, a re scan.

So I’m afraid I didn’t do that because I wanted all codes to be visible for taking it to an independent ford specialist, after a day and a half trying to make it fail (as usual works fine when someone else looks at it!) It was diagnosed as a faulty fuel temperature sensor?!?!! New one fitted today and so far so good! Hope this may be of use to someone else if they get similar symptoms.. fairly cheap fix of £35 plus diagnostics..


Sent from my iPhone using Tapatalk

Thanks for the heads up and hopefully it completely solves the problem.