Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncements
Discussion Groups
By Brand
BMWChevroletDodgeFordGMHondaLexusMercedes-BenzNissanPeugeotToyotaVolkswagenOther Brands
By Topic
4x4 CarsRVsDrivingMaintenance & RepairCar AudioCollectible Cars
Country Specific
Australian ForumsUK Forums
ArticlesAuto InsuranceBuyingCars & TechnologyMaintenanceMiscellaneousSafety
DMV Resources
Related Topics
MotorcyclesBoatsMore Topics ...

Car Forum / Ford / Ford Explorer / October 2006

Tip: Looking for answers? Try searching our database.

Check Engine Light

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Allan - 07 Oct 2006 02:37 GMT
Hi Folks,

I have a '99 Ford Explorer XLT 4L, 4WD SUV. 118,000KL on it. Lately I
have been getting engine ping, especially when entering and going uphill.

Today..this morning, I backed it out of the garage and drove over town
and back. Nothing out of the ordinary. This afternoon, my wife went
across town and when she got back, she told me the Check Engine Light
was on.

I went out to the vehicle and started it. Sure enough the check engine
light was on and there was a noticeable roughness in how it ran. I took
it around the block and it was low on power as well and continued the
rough running.

What may have broke so suddenly?

Thanks

Allan
Big Shoe - 07 Oct 2006 13:26 GMT
Enormous number of problems could cause this - can't tell anything
without knowing the codes.  Most likely a sensor failed.

>Hi Folks,
>
[quoted text clipped - 16 lines]
>
>Allan
Allan - 08 Oct 2006 20:49 GMT
Would a sensor cause it to run rough? Most noticable at idle?

There is a couple of things I am going to do first before looking for
faulty sensors, one is to change plugs as it's very unlikely these have
been changed since the vehicle was new. I bought the vehicle at
103,000km, put 15,000 on it in a 21 months. I have not changed plugs
since I owned it. Another is to change the fuel filter. Then I will run
some injector cleaner in the tank, just filled. Hopefully this will
correct it, as it's past due for this type of service anyway, if not
then I'll have to get it in and on a scope.

Allan

> Enormous number of problems could cause this - can't tell anything
> without knowing the codes.  Most likely a sensor failed.
[quoted text clipped - 19 lines]
>>
>>Allan
Craig - 08 Oct 2006 21:09 GMT
"Allan" <agrayson@yourlink.ca> wrote...

> Would a sensor cause it to run rough? Most noticable at idle?
>
[quoted text clipped - 3 lines]
> put 15,000 on it in a 21 months. I have not changed plugs since I owned
> it.

 Plugs are due at 100,00 miles, so your 118k km is early for needing plugs,
I'd think.

> Another is to change the fuel filter.

 You say "rought at idle". Wouldn't a restricted fuel filter have more
problems at hard acceleration rather than at idle?

> Then I will run some injector cleaner in the tank, just filled. Hopefully
> this will correct it, as it's past due for this type of service anyway, if
> not then I'll have to get it in and on a scope.
>
> Allan

 I'm rarely one to believe when it comes to auto advice, but before you do
a lot that's not necessary, wouldn't having the "check engine" codes read be
a better thing to do first?

Craig
Craig - 08 Oct 2006 21:10 GMT
"Craig" <wpyr@REMOVEMEworldnet.att.net> wrote...

>  Plugs are due at 100,00 miles, so your 118k km is early for needing
> plugs, I'd think.

 Whoops, make that 100,000 miles.
Jim Warman - 09 Oct 2006 02:29 GMT
The check engine light is the PCMs way of trying to tell you something... is
there any particular reason that you are refusing to listen?

If a car comes in to the shop with the CEL illuminated, the VERY FIRST thing
that happens is a code scan.

Fuel filter and plugs are routine maintenance items and should be addresed
according to schedule as long as no abnormal conditions have been
encountered.

> Would a sensor cause it to run rough? Most noticable at idle?
>
[quoted text clipped - 32 lines]
>>>
>>>Allan
Allan - 09 Oct 2006 19:35 GMT
Old school I guess. Older vehicles, if they acted like this I would
suspect fouled plug. I'll take it in and have it scanned once they are
open, holiday weekend here. Will post results.

Thanks

> The check engine light is the PCMs way of trying to tell you something... is
> there any particular reason that you are refusing to listen?
[quoted text clipped - 42 lines]
>>>>
>>>>Allan
Jim Warman - 09 Oct 2006 23:18 GMT
Still trying to recover from turkey overdose, myself....

Having the codes read is going to be the least painful way of addressing
your issue.... when I got my licence, cars still had points....THAT'S "old
school"....
Allan - 10 Oct 2006 04:15 GMT
Hurting tonight too...too much turkey;-)

Remember points well, my first was a 1962 Plymouth Savoy, slant six
standard. Next was a '63 Studebaker Daytona.

Cheers!

Allan

> Still trying to recover from turkey overdose, myself....
>
> Having the codes read is going to be the least painful way of addressing
> your issue.... when I got my licence, cars still had points....THAT'S "old
> school"....
Mark Barrett - 12 Oct 2006 20:23 GMT
> Still trying to recover from turkey overdose, myself....

> Having the codes read is going to be the least painful way of addressing
> your issue.... when I got my licence, cars still had points....THAT'S "old
> school"....

   Yes, my favorite of my cars is a 69 Camaro where I must manually
set the point dwell and ignition timing.  I never worry about a check
engine condition on that vehicle.  However, I only drive it on Sundays.
Mark
Allan - 13 Oct 2006 01:37 GMT
Vehicles I had but not anymore. 1969 Mustang 351 Cleveland. Go like
there's no tomorrow! 1958 Rambler Ambassador 327ci with Continental Kit.

Allan

>>Still trying to recover from turkey overdose, myself....
>
[quoted text clipped - 6 lines]
> engine condition on that vehicle.  However, I only drive it on Sundays.
> Mark
Allan - 11 Oct 2006 20:54 GMT
Hi Folks,

Code 301 came up and points to cylinder 1 misfire. Possibilities of a
bad wire or bad plug. Mechanic figures it's probably a bad plug as they
do go bad from time to time but didn't rule out a cracked wire. It's in
for service now, they'll call when ready.

Allan

> Hi Folks,
>
[quoted text clipped - 16 lines]
>
> Allan
Mark Barrett - 12 Oct 2006 20:20 GMT
> Hi Folks,

> I have a '99 Ford Explorer XLT 4L, 4WD SUV. 118,000KL on it. Lately I
> have been getting engine ping, especially when entering and going uphill.

  I've owned a 95 Explorer for over 10 years and recently I bought
a 98 Sport for my son.  (Explorer's can be bought for next to nothing.)
For the 95 I had about 5 check engine situations over a period of
250000 miles.  In all cases the problem was fixed by changing the
appropriate sensor.  A few weeks ago the check engine light came on in
the 98 and it turned out to be a bad O2 sensor on one of the exhaust
down pipes.  In all cases the easiest thing to do was to read the code
which pointed in the right direction.  After that a little experience
will help diagnose the problem.  I've always used a trusted mechanic
that does not charge me for the code read, just the part replaced.  
Mark
Allan - 13 Oct 2006 01:45 GMT
The code on ours was 301 (cylinder 1 misfire). Pulled the plugs and they
were fouled and wet for some reason. The mechanic asked if the vehicle
burned oil, no, it doesn't. Replaced all six plugs, changed the air
cleaner filter and fuel filter, runs nice now although it still surges a
bit when first starting, that is it drops rpm to almost stall, then
picks up immediately to proper idle. Mechanic said (local small town
shop) that he didn't have the equipment to determine why this was
happening. I'll have to take it into the Ford dealer next time I'm in
the city. Perhaps this is a sensor that is going bad. May have something
to do with the ping too perhaps?

Allan

>>Hi Folks,
>
[quoted text clipped - 12 lines]
> that does not charge me for the code read, just the part replaced.  
> Mark
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.