• Welcome Visitor! Please take a few seconds and Register for our forum. Even if you don't want to post, you can still 'Like' and react to posts.

Todays 2.9 puzzle


sspencer82

Member
Joined
May 4, 2009
Messages
19
City
Aubrey, Texas
Vehicle Year
1988
Transmission
Manual
'88 2.9 starts and runs fine for 3 seconds, "check engine light" comes on, rpm drops.
Yes this is the same engine from 'Stuck at 3K'... the thing will NOT go into tune like it should. Doesn't matter whether PIP plug is in or out...no change. The engine has no power. Have to turn radio up to drown out the valve clatter when accelerating.
 
'88 2.9 starts and runs fine for 3 seconds, "check engine light" comes on, rpm drops.

Hard to say.. I would start on that by pulling codes since the CEL is coming on, and checking the fuel pressure to make sure it's in spec.
 
Have to turn radio up to drown out the valve clatter when accelerating.

..Hmm. Yeah I would start with codes too but, Perhaps the distributor is loose and knocked itself out of time???

Is it possible the valve chatter was actually pinging from detonation?

Just an idea..
 
It's been spitting out 3 codes: O2 (always did that), PIP, and I forget the 3rd one. Haven't checked codes on it since Jeep went down. It has a new pressure regulator, relatively new TPS... Could it be the re-man computer? Could it need to be reprogrammed? The engine was re-built last year, should be roaring instead of sputtering
 
The PIP code could be tripped by the sputtering but an 02 sensor can cause this too. Especially the bogging down. Unplug it and give it a ride around town...See if it still does it.

I guess it could be a CPU problem but I would try to find out whats up with the O2 or its circuit.
 
If it's o2 sensor lean code, a lot of times it really is sensing too much oxygen in the exhaust. Misfire, vacuum leak, etc can all cause this code. Something funny in the ignition could be causing a mis-fire. Think you should try and tackle the code 14 first, clear codes by pulling the jumper while the stored memory codes are being output, and wait and see if that resolves the o2 sensor code. Were those just stored memory codes, or did you run through the KOER test?
 
Are you using a code scanner or doing it manually with a jumper wire at the diagnostic connector?

Probably not the o2 sensor then unless it's a wiring issue, but mostly bad o2s will cause problems when the engine is up to temp. Think it's likely it's sensing too much oxygen, seen this senario many times. The codes don't always point to a specific sensor at fault, but that what it's reading is out of range of what it's suppose to be.
 

Sponsored Ad


Sponsored Ad

TRS Events

Member & Vendor Upgrades

For a small yearly donation, you can support this forum and receive a 'Supporting Member' banner, or become a 'Supporting Vendor' and promote your products here. Click the banner to find out how.

Recently Featured

Want to see your truck here? Share your photos and details in the forum.

Ranger Adventure Video

TRS Merchandise

Follow TRS On Instagram

TRS Sponsors


Sponsored Ad


Sponsored Ad


Amazon Deals

Sponsored Ad

Back
Top