Thread: SES light :(
View Single Post
Old 10-24-2011, 04:30 PM   #8 (permalink)
xgrudgex
Base Member
 
xgrudgex's Avatar
 
Join Date: Jul 2010
Location: California
Age: 38
Posts: 111
Drives: My neighbors crazy
Rep Power: 15
xgrudgex is on a distinguished road
Default

Quote:
Originally Posted by wstar View Post
Yeah if you think you may have run over something, especially check the wiring and sensors for the rearmost pair of O2 sensors (behind the cats). They're pretty exposed, I'm not fond of the design there.

As far as the MAFs go, when they're dirty/oiled it can take a while to throw something like P0157. What triggers the code is that it's trying to use the MAF input to verify the response curve of the rear O2 sensor, and after a while of driving it ends up eventually blaming the rear O2 sensor's response curve when the MAF is actually the one at fault more commonly (assuming no damage under there).
Yea I honestly dont think I snagged anything while driving even tho it sounded like I ran over a flattened bird cage but I took a look at lunch to see if I could see something without lifting the car but NO DICE... cars to efin' low so that will have to wait...

As for the dirty/oiled MAF, about how long do you think it would take until it started blaming the o2? you think 5k miles long or more like a couple hundred before it started blaming the o2?

Im realllllly hoping it is the MAF... Ill buy some MAF cleaner today even if I find out I snagged something because the more I think about it I remember them drop in were pretty oiled... or its my imagination because thats what I want it to be! lol
xgrudgex is offline   Reply With Quote