Drew Hardrath
 |
|
• West Valley, UT, USA |
|
• Registered on 10/20/2003 |
|
• 33 posts |
|
|
|
 Posted:11/10/2003 23:14 |
|
|
|
OK, so i have a 90 Fullsize Bronco with the 351. I notice that in the morning when i start it up, it revs up to 1500- 1900 RPM and stays there for a good 4 or 5 minutes. Then it will come back down to just above 500 rpm and stay there. Then when i go to put it in reverse it jumps back up to 1500 RPM and clunks into gear. Then, when i go to put it in drive it DOESNT jump up in RPM while shifting, but once in gear it revs up to 1000 RPM. It also does this when i come to a stop, it will stay at 1000 RPM, then drop after a few seconds. It's really starting to get annoying, and has done it ever since i owned the truck. Anybody have any ideas as to what it can be? |
|
Bob Kennedy
 |
|
• Olympia, WA, USA |
|
• Registered on 9/19/2001 |
|
• 93 posts |
|
|
|
|
Posted:11/11/2003 22:32 |
|
|
Could be any number of things. When was the last tune up? Have you pulled the codes recently?
Bob
|
|
Drew Hardrath
|
|
• West Valley, UT, USA |
|
• Registered on 10/20/2003 |
|
• 33 posts |
|
|
|
|
Posted:11/12/2003 18:37 |
|
|
I just did the cap, rotor, wires, and plugs less then a week ago, mainly because it was scheduled maintenance, i wasnt too optimistic that it would cure the problem at hand.
Truth be told, I'm more of a GM guy, my other car is an 86 Trans Am, and pulling the codes on that is a breeze. But when it comes to my Bronco, i have yet to try and do so. Could I take it auto zone or checker and have 'em do a free diagnostic check, or would i be better off renting an auto x-ray or equivalent scanner? |
|
schmuck
 |
|
• nola, XX, USA |
|
• Registered on 5/21/2003 |
|
• 1,187 posts |
• 1 Vehicle
|
|
|
Posted:11/12/2003 21:59 |
|
|
auto zone will not pull codes unless the check engine light is on
check your tranny fluid and see if it smells burnt or if you see alot of debris in it, it sounds like to me anyway a bad or cloged up torque converter or like its getting to much fuel like a bad o2 sens
nucking futs
|
|
Bob Kennedy
|
|
• Olympia, WA, USA |
|
• Registered on 9/19/2001 |
|
• 93 posts |
|
|
|
|
Drew Hardrath
|
|
• West Valley, UT, USA |
|
• Registered on 10/20/2003 |
|
• 33 posts |
|
|
|
|
Posted:11/14/2003 16:49 |
|
|
Ok, thanks guys. Looks like im gonna replace the o2 sensor ( might as well, lord knows when the last time that was changed  ) and then take a look at my codes. Thanks for the help!  |
|
Bob Kennedy
|
|
• Olympia, WA, USA |
|
• Registered on 9/19/2001 |
|
• 93 posts |
|
|
|
|
Posted:11/14/2003 19:24 |
|
|
You betcha.
 |
|
Drew Hardrath
|
|
• West Valley, UT, USA |
|
• Registered on 10/20/2003 |
|
• 33 posts |
|
|
|
|
Posted:11/19/2003 16:23 |
|
|
|
Ok, so i did replace the o2 sensor today, and it still has its current problem. So next chance i get im gonna pull the codes. I have a question about pulling the codes, do i want the KOEO codes or the KOER codes??? |
|
Bob Kennedy
|
|
• Olympia, WA, USA |
|
• Registered on 9/19/2001 |
|
• 93 posts |
|
|
|
|
Posted:11/20/2003 15:30 |
|
|
You'll want both. The KOEO codes are based on voltage faliures for sensors. The KOER also includes a 'wiggle' test that makes sensors fail and then come back up. Also, it's tests the sensor array in a running condition.
Usually, I end seeing the same codes when I run both.
Bob K.
|
|
Drew Hardrath
|
|
• West Valley, UT, USA |
|
• Registered on 10/20/2003 |
|
• 33 posts |
|
|
|
|
Posted:11/22/2003 14:01 |
|
|
OK, thanks, looks like i'll end up doin it tomorrow, cus it should be a little warmer. right now its a blistering 29 degrees out  |
|
