*** Restricting New Posts to SD Premium Members ONLY *** (09 May 2025)

Just made a new account? Can't post? Click above.

Help us help you. By posting the year, make, model and engine near the beginning of your help request, followed by the symptoms (no start, high idle, misfire etc.) Along with any prevalent Diagnostic Trouble Codes, aka DTCs, other forum members will be able to help you get to a solution more quickly and easily!

2002 ford Taurus 3.0l ohv. P0171 p174

  • Benoitjos52
  • Benoitjos52's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
5 years 1 month ago #42176 by Benoitjos52
2002 ford Taurus 3.0l ohv. P0171 p174 was created by Benoitjos52
Hi all. OK got this 2002 ford Taurus 3.0l ohv was getting these codes before blown head gasket. Had replaced all 02 sensors and maf sensor. Blew head gasket fix that and replaced heads. So new gaskets all the way up. Fired up and day later same codes. Don't have scanner but did make smoke tester and found leak at war valve. Fixed that. Day later check engine light. Now I Do think here vacuum leak sprayed and smoke test and nothing I can see. What are some areas that people found leaks in please help.

Please Log in or Create an account to join the conversation.

  • Noah
  • Noah's Avatar
  • Offline
  • Moderator
  • Moderator
  • Give code definitions with numbers!
More
5 years 1 month ago #42177 by Noah
Replied by Noah on topic 2002 ford Taurus 3.0l ohv. P0171 p174
Did you replace the oxygen sensors before or after the head gasket failure? They don't like coolant...

Without a scanner to provide some data, you're really shooting from the hip.
If these codes showed up only after the head job, I would suspect some kind of gasket leak but you said they were there before.

Assuming the o2s were changed after the repair, the first thing I would check is freeze frame data to see when the lean code set.

While a vacuum leak is the most common cause of a lean condition, it will generally only effect the engine at low rpm.

Long term and short term fuel trim at warm idle, 2000rpm and 3000 rpm will help differentiate the issue from a potential vacuum leak or fuel delivery issue.

"Ground cannot be checked with a 10mm socket"

Please Log in or Create an account to join the conversation.

More
5 years 1 month ago #42178 by Matt T
Replied by Matt T on topic 2002 ford Taurus 3.0l ohv. P0171 p174
Yeah really need scan data to get some direction here. Since it's a Ford buying a Forscan compatible OBD to bluetooth or USB adapter is probably the best, inexpensive, way to get it.

Please Log in or Create an account to join the conversation.

  • Benoitjos52
  • Benoitjos52's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
5 years 1 month ago #42183 by Benoitjos52
Replied by Benoitjos52 on topic 2002 ford Taurus 3.0l ohv. P0171 p174
I replaced o2 and maf before headgaskets. And was still getting codes then. I will have to see about getting a cheap scanner. Any ideas. Thanks all

Please Log in or Create an account to join the conversation.

More
5 years 1 month ago #42185 by Matt T
Replied by Matt T on topic 2002 ford Taurus 3.0l ohv. P0171 p174

Benoitjos52 wrote: I will have to see about getting a cheap scanner. Any ideas.


A USB or bluetooth adapter + app(s) is the better value at $100 and under. Much more capable than the handheld code readers. Link to the Forscan compatibility list below.

forscan.org/forum/viewtopic.php?t=6142

Personally I've got an Obdlink MX+ which is on the upper end of the price range for these things. I went with it because I wanted something that'd work with iOS which limits your options on hardware and apps. When I bought mine the only other options were wi-fi adapters with terrible reviews.

It works fine with Forscan. Also the app that comes with it will pull OE codes and data from Ford, Toyota, and newer nissans. OE codes only on gm, usually a bunch of 'em :lol: Generic OBD only for chrysler.
The following user(s) said Thank You: Noah

Please Log in or Create an account to join the conversation.

Time to create page: 0.355 seconds