Well, I was able to pull these codes from my 98 gsr, bone stock motor with 50k miles. I got the following codes.

#22 VTEC pressure valve
#23 Knock sensor

Before I bring this to my mechanic to have the above fixed. Is there anything I could do on my own that could maybe fix those problems? Is my motor at any risk of damage with the above problems? I would definitely appreciate some helpful tips, Thanks!

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by VTECth1s &raquo;</TD></TR><TR><TD CLASS="quote">Well, I was able to pull these codes from my 98 gsr, bone stock motor with 50k miles. I got the following codes.

#22 VTEC pressure valve
#23 Knock sensor

Before I bring this to my mechanic to have the above fixed. Is there anything I could do on my own that could maybe fix those problems? Is my motor at any risk of damage with the above problems? I would definitely appreciate some helpful tips, Thanks!</TD></TR></TABLE>

you could try cleaning out the vtec solenoid. knock sensor just replace.

 

Cool, any diy's on cleaning the selonoid? So the knock sensor is just faulty, theres no risk of damage? thanks for info.

 

Updates:

I cleared the codes by unplugging the negative terminal on the battery for about 30 seconds. Then plugged it back, then drove the car and the CEL came back on, as I thought it would.

Then I re-checked the CEL codes, and now its only throwing a code #23 Knock Sensor. My only option now is to just get the knock sensor replaced by my mechanic.

 

Also forgot to mention, a faulty/malfunctioning knock sensor can hinder some of the engine's power correct?

 

Check for lose wiring from the knock sensor to the PCM/ECU. Most of the time it's not even the unit that is bad. But in your case it might be. It wouldn't hurt to do the basics first though...

 

I don't know which wires connect to the knock sensor and back to the ecu. I'm not savvy when it comes to electrical parts. I can't even use a voltmeter neither, and I've had one for a long time, too confusing to use, lol.