Rep Power: 0

Greetings Folks!

Over the course of last 1-2 weeks, I've done the following on my 2005 Civic -

1. Changed the O2 sensor (CEL indicated P0135; replaced with Denso O2 sensor)
2. Air bag light came on (fixed the seat buckle issue).
3. Checked the air filter under the hood to check if it's clean or dirty. It was clean and I put it back in.
4. Wanted to check how to get the spark plugs out to check for the gap. I was able to get the screws holding the plugs out but didn't have the ratchet extension tool to get the spark plugs themselves out. I didn't touch the spark plug itself but removed the long black plug and put it back in exactly as-is.
5. One of the hub-caps was broken so I got a new one. Used the ratchet tool found in the trunk to remove the lug nuts, removed the cracked one and put the new one in by loosening/tightening the lug nuts in the star fashion (described in a you tube video)

Since the last couple of days, apart from the regular rumbling of the engine on startup, I've noticed a secondary low-pitch rumbling sound. I've been driving this car for almost a decade so I know this sound is different. It's not from the A/C. May be it's just my mind but the car also seems a little sluggish.

Based on what I've done above, do you folks see any issues? I've ran the OBD scanner again and it again showed P0135 but there is no CEL. I drive about 6 miles a day as I live close to my work place. OBS Scanner mentioned that some codes will be reset after the on board computer detects succesful "n" number of runs.

Please advise.

 
Rep Power: 518

Erase the code with your reader or disconnect the battery to erase the code.
Then recheck for codes to make sure it's gone before you drive again.
This way you know you have a "clean slate" as far as engine computer and codes go.

Gonna be tough to check this out over the internet. Got a recording? Have you got out and checked to see where it might be coming from?

 
Rep Power: 0

Hi ezone, thanks for the help! Turns out my O2 sensor was not activated at all. I had to take the car for inspection and it failed O2 Sensor and EVAP readiness tests. I'm read that this might happen if the car didn't complete enough drive cycles. I have erased the codes and have now performed basic drive cycle from the link - http://repairpal.com/how-to-perform-a-basic-drive-cycle.
I don't hear the weird sound anymore and the when I ran the scanner again, there are no codes.

Hopefully, I'll pass next time (have an appointment tomorrow). Is there any way to test the O2 sensor readiness without going to the store? My inspection tag ends this month. I have the OBD II bluetooth adapter and the Torque app.

Thanks again, sir!

 
Rep Power: 518

I didn't know you have to do an emissions test. Erasing codes resets those monitors so you do need to drive the car and get them to indicate they have been completed before an emissions test.

Look for anything like "readiness" or "monitors" or "OBD status" or the like in the list of stuff you can access with your app.
There would be items like cat, misfire, O2, EVAP, and more. There would be "continuous", "yes", or "no" type indicators as to whether or not they have run their self tests yet.



Or the simple way: Sit down in the car. Turn on the key but do not start the engine. Watch the check engine light for about 30 seconds:
"If all readiness codes are complete, the MIL comes on for 20 seconds and then goes off.
If one or more codes are incomplete, the MIL comes on for 20 seconds and then blinks five times"

AFAIK all states can allow you to take an emissions test even if at least one (or maybe two) of the monitors has not completed yet (check your local regs).
BUT this blinking light method can't tell you how many or which ones have not completed.


HTH