Notices
The Lounge For casual talk about things unrelated to Blazers (ie. Off-Topic).

sel on that turns off?

Old Feb 24, 2014 | 05:26 AM
  #1  
er0ck273's Avatar
Thread Starter
|
Senior Member
Joined: May 2013
Posts: 629
er0ck273 is on a distinguished road
Default

My girl has an 03 Mitsubishi outlander...her sel came on and we got it checked it was a bad o2 sensor...this morning then light never came on

Is it possible the o2 sensor unclogged itself? Or some other phenomenon lol

And the code was never cleared by the way lol
 
Old Feb 24, 2014 | 10:32 AM
  #2  
ohsofly's Avatar
Super Member
Joined: Jan 2010
Posts: 1,534
From: Camrose AB... Canada
ohsofly will become famous soon enoughohsofly will become famous soon enough
Default

Just cause you got it scanned and the code said "O2 sensor circuit fault" does not mean the sensor is bad... It could mean there is some crud in the plug on it somewhere along the line too thats causing poor communication with the sensor, a wire rubbed through, or some other connection problem.

Its time you get underneath and rule that stuff out first. The sensor is probably a post-cat sensor, so look at the one after the cat. Look for the wires touching the exhaust pipe, or maybe yanked on by snow or grass or something.
 
Old Feb 24, 2014 | 03:04 PM
  #3  
er0ck273's Avatar
Thread Starter
|
Senior Member
Joined: May 2013
Posts: 629
er0ck273 is on a distinguished road
Default

naturally she doesnt keep track of her mpg (typical female lol) so i guess ill have to take a look next time shes over. she only has two on her suv i wish the guy told us what bank/sensor it was.

i will have to check the post cat, thats probably the easier one to get to

thank you for the info ohsofly!!
 
Old Feb 24, 2014 | 10:49 PM
  #4  
cleburne red's Avatar
BF Veteran
Joined: Sep 2011
Posts: 2,278
From: Texas
cleburne red will become famous soon enough
Default

I've had random codes come on once and never come back before. What I usually do, now, is to clear any code the first time it shows up, as long as the vehicle isn't exhibiting any symptoms. If it comes back, then it's time to check it out. But several times I'll clear it out, and it never resurfaces.

Now, I'm not saying to ignore any potential problems, but it seems like sometimes a system will be out of range just enough, for just long enough, to set a code, even if nothing is wrong.
 
Old Feb 25, 2014 | 06:55 PM
  #5  
er0ck273's Avatar
Thread Starter
|
Senior Member
Joined: May 2013
Posts: 629
er0ck273 is on a distinguished road
Default

Originally Posted by cleburne red
I've had random codes come on once and never come back before. What I usually do, now, is to clear any code the first time it shows up, as long as the vehicle isn't exhibiting any symptoms. If it comes back, then it's time to check it out. But several times I'll clear it out, and it never resurfaces.

Now, I'm not saying to ignore any potential problems, but it seems like sometimes a system will be out of range just enough, for just long enough, to set a code, even if nothing is wrong.
yea ill assume if it doesnt come back on it was fluke lol, but if it does ill have the code read and actually get the bank/sensor noted. next times she over i still wanna check the wires to make sure they arent touching the exhaust or another hot component
 
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
972disciple
2nd Generation S-series (1995-2005) Tech
4
Jul 13, 2009 11:33 PM
BirdofPrey
2nd Generation S-series (1995-2005) Tech
9
Jun 4, 2009 07:27 AM
Inferno
Engine & Transmission
4
Jun 11, 2008 05:06 AM
rooster
Steering, Suspension & Drivetrain
3
Jun 7, 2007 08:40 AM
blaze1925
2nd Generation S-series (1995-2005) Tech
2
Sep 20, 2005 11:54 PM


Thread Tools
Search this Thread

All times are GMT -5. The time now is 03:17 PM.