Fuel Pressure Regulator Help | Ford Explorer Forums

  • Register Today It's free!

Fuel Pressure Regulator Help

JKristel

Member
Joined
January 14, 2000
Messages
18
Reaction score
0
My 1991 Mazda Navajo (94k miles, Auto) has been surging at idle (it varies between 500-800 RPM) and the exhaust smells rich. Fuel economy has been down as well. This all started 3 weeks ago and since that time, I have run a scanner on it which revealed a code 41 (oxygen sensor.) So I replaced the sensor and the engine still ran poorly, in addition, after warming up, the code came right back again (Code 41) Because I am a gluten for punishment and seeking to make sure I did not have a bad part, I went back to my parts store replaced the senor again, and got the same problem. Since then, I have checked the vacuum hoses, replaced the spark plugs, replaced the air filter and cleaned out and inspected the IAC motor.

I read on another post here regarding fuel mileage that the fuel regulator is the likely culprit, but before I do that, are there any other suggestions? Anyone with similar problems?
 



Join the Elite Explorers for $20 each year or try it out for $5 a month.

Elite Explorer members see no advertisements, no banner ads, no double underlined links,.
Add an avatar, upload photo attachments, and more!
.





I too am in about the same situation. I have noticed the idle is a little rougher than normal for about the last month as well as lower fuel mileage. I purchased a code scanner as well after my check engine light finally came on Dead Link Removed . I was showing the same code 41 but it was only on the stored memory (continuous) codes. The check engine light started coming on after driving a minimum of 15 minutes. After checking the codes last week and resetting them, the light came on today for the first time since the middle of last week so I wanted to check it. I pulled over at a local park and WITHOUT shutting the engine off, (while the light was still on), I connected my scanner and it gave me a code of 42 (fuel mixture rich). This is known as a running code.

I then turned the ignition off and waited about 15 seconds and then turned the key on (engine not running) and read my codes again. I then had a code 41, "Oxygen sensor signal fault, switching not detected." When you first start the engine, the engine goes into a closed loop (set program) and it takes about 15 minutes before it starts reading the sensors like the O2. When it warmed up and found the signal to be out of range or not even there, then it turned the check engine light on. Whenever the key is turned off and then engine restarted, it takes 15 minutes again to start reading the signal.

Forgive me if I may sound too basic about this but I do not know what your mechanical ability is and I don't mean to offend you. The code reading consists of different steps. The first step is with the key on and engine off. It tells you any codes that are stored in memory (continuous), even though they may not be bad now...in other words, the problem could have been corrected in the past and still showing to be bad if the codes have not been reset.

The second test is with the engine running. When you do the scan this time, it picks up any codes that are CURRENTLY showing at fault at that immediate time...not an hour before or so but since the engine has been started this time.

I would reccommend resetting the codes, (read the instructions with your scanner to see how), resetting your computer by disconnecting battery cable for 5 minutes, and then driving for a while (1 hr+) and then rechecking them again. By resetting the computer, it will possibly straighten itself out after the problem has been resolved Dead Link Removed .

Last week, I also thought about the fuel pressure regulator so I bought a fuel pressure gauge from AutoZone ($35) and connected it to the test fitting on the fuel rail. It was showing the pressure to be within the specification so I kinda put the FPR out of my mind for the time being. I am now going to replace the O2 sensor and reset my codes and computer and see what happens.

I hope this may help you. I will stop here because I am beginning to confuse myself Dead Link Removed . Good luck and keep us posted.

------------------
Ira

91 XLT 4x4
 






save yourself the trouble and just replace the fuel pressure regulator. A code 41 "rich running" does not neccesarily mean that the o2 sensors are bad. It just means that the sensor is not switching as it should be. Usually it means that the o2 sensor is sensing a rich or lean condition. The code 42 "rich" code than tells you that the engine is running rich. Which in all my years of experience usually means a bad fuel preesure regulator. The fuel regulator sometimes sticks and that is when the code 42 comes on. What I would do is insta1l the fuel pressure gauge and let the car run and when the check engine light comes on check the fuel pressure. Or just save the time and trouble and just replace the fuel regulator...
 






Thanks for the replies. I have decided to replace the Fuel regulator. I was able to order it from Wrenchead .com for 72.98 and it should be in by Friday. I will post again to let everyone know if it makes a difference or not.
 






If the fuel pressure regulator doesn't fix it, check out your AIC (air idle control).. or it might be called IAC (idle air control) valve. One way to check it is turn on your A/C. If the idle doesn't go up your AIC may be bad. Another check is to remove the connector on your AIC. The idle should go down when you disconnect the connector. The AIC is located on the plenum, on the driver side of it. I believe it is held on by two 10 or 8mm bolts.



------------------
Mark
mark@legendz.com
http://mark.legendz.com
Off-Road and Motorcycle Information, Pictures and Movies
 






I installed the Fuel Pressure regulator and it completely fixed the idle problem, fuel economy problem and the "rich" smell from the exhaust.
Thanks again for all who replied.
 






Featured Content

Back
Top