Last post on Jul 10, 2011 at 7:23 PM
You are in the Ford Ranger
What is this discussion about?
Ford Ranger, Engine, Truck
#6 of 13 Re: 2005 Ranger misfire codes [bolivar]
Dec 03, 2009 (10:08 pm)
One of the first things I did was change air filter, pull MaF, and inspect the Throttle Body......all spotless. But wouldn't a low fuel pressure cause a lean mixture thus white exhaust smoke? And wouldn't a misreading MaF throw a code?...And to anyone else reading these, Has anyone ever replaced the computer?
#7 of 13 Re: 2005 Ranger misfire codes [bigd11775]
Dec 06, 2009 (9:09 am)
Here's the latest. They had one of their "engineers" figure out that since everything else was good ie., compression, spark, air flow, mixture, etc. that I had a faulty Power Train Control Module that will only be $688.00, and it will take a week to get the part. I'm like you though, this will be my last Ford. Don't start spending money like I did to start; which, looking back, was all trial and error to replace things that didn't need replacing. Consider this, but I don't know how to check it. Hope this helps.
#8 of 13 Re: 2005 Ranger misfire codes [bigd11775]
Dec 06, 2009 (9:18 am)
According to a Ford "Engineer" that looked at my truck, I need a new Power Train Control Module. Everything else was thoroughly checked and tested. A mere $688.00 and a week for the part will get me back on the road. Anyway, consider this before you replace everything like injectors, plugs, coil packs, cat convertors, etc. I can't believe the money I've spent and still didn't get my problem fixed. I wished I would have kept all my old parts now.
#9 of 13 Ok new problem discovered
Dec 09, 2009 (10:02 pm)
Today I was leaving work and I left my key turned forward for about 5 sec before trying to crank the engine over. It took me about 30sec to get it started, and it didn't start until I hit the gas pedal. Now last week, I was driving for about 20 min and I stopped to get gas and it was running ok. As soon as I filled the tank up and started the truck, it ran like it was on 2 cyl for about a minute until I revved the engine in neutral a few times.....no power but again no smoke.
#10 of 13 Re: Ok new problem discovered [bigd11775]
Feb 06, 2010 (8:16 am)
I just wanted you to know I have just now gotten my truck correctly repaired. Turns out of all things I had a weak valve spring. All this other crap I went through and $3600.00 worth of parts and repairs, and I finally found someone who got it right. And it sure wasn't the Ford Dealership. I actually took it to two different ones and they couldn't get it right. I just got ripped off big time I guess, so now I am going to see what recourse I have on that end. Good luck, I hope you found your problem, and if not consider the valve spring(s)
#11 of 13 2005 Ranger 3.0L multiple codes
Feb 03, 2011 (4:58 pm)
I came across a thread earlier today stating the same symptoms I have with my engine. It involves replacing the o-ring on the IMT valve. However, I simply cannot find a picture or a good enough description to show me where the IMT valve is. It is a 2005 Ford Ranger 3.0L v6. Can anyone post a pic with an arrow for me or describe it for me? Also I noticed a small amount of burnt oil drips on top of the driver side valve cover. Not enough to drip down to the exhaust but enough to notice. I pulled the wire harness off and ran my hand all underneath the upper intake and felt nothing but dry dusty metal. Clueless to where it could be coming from. Any thoughts?
#12 of 13 won't fire
Jun 01, 2011 (1:53 pm)
i have a 1998 ford ranger. we just had the computer repaired and had the trigger switch changed and have checked all the fuses. it still will not fire. any suggestions
Jul 10, 2011 (7:23 pm)
I have an '01 Ranger w/4.0 v6 that developed an engine misfire. I have done the following: plugs, 3 sets of plug wires, intake gaskets, fuel filter, cleaned MAF, cleaned idle air control valve, checked air filter, cleaned EGR (but still get codes PO401 and PO402 - excessive and too little gas flow in EGR), new coil pack. Miss starts after engine warms up and it is on a pull. Has anyone seen similar problems? Can anyone help?