Jump to content

Knock Sensor Issues Won't Go Away

jdaniel83
 Share

Recommended Posts

jdaniel83 Enthusiast

jdaniel83

Posted
Posted

Hello all. It's been quite a while since I was on here last but I'm having some issues that I thought the great minds on this forum might be able to help me with. So my '01 Sierra's SES light started coming on a few months ago so I pulled up the code and sure enough got the P0332 Knock Sensor code. I just replaced the knock sensors and harness less than a year and maybe 10K miles ago so I decided to clear the code and see if it came back. For about 2 months and another 5K or so miles the code didn't come back and the truck ran fine. Then my fuel pump went out so I replaced it and on the test drive the SES light came back on and I started hearing the valve clattering that I've heard in the past when that 332 code used to come up.

 

So I went ahead and ordered new sensors and a new harness again just to be safe, and after getting it all back together I took it out for a drive and everything seemed good at first but after about 10 miles the SES came back on and I could tell the truck went back into "limp mode" with the lack of power and valve clattering. This is the 4th time that I've replaced the rear knock sensor and the 2nd harness I've put on and I'm still getting the codes. Any ideas as to what it could be or how to fix it? I'm getting tired of taking that bleeping intake off.

 

Oh and it only seems to have problems and throw the code in the summer time when it is very hot outside (100+ degrees).

Chris Senior Enthusiast

Chris

Posted
Posted

Also are you sealing the sensor covers to the valley cover per the TSB? If moisture is getting in there ic could upset the sensors. But as Rob said, Time to have it diagnosed using a shop scanner such as the Vertronix Tech 2 that the dealer has.

  • Like 1
jdaniel83 Enthusiast

jdaniel83

Posted
  • Author
Posted

Yeah I sealed the covers to the valley pan. I have a scanner but its not one of the shop scanners you talked about. Guess I'll end up having to take it somewhere that has the type of scanner you mentioned because today it showed both the PO327 and 332 codes so something isn't right.

Chris Senior Enthusiast

Chris

Posted
Posted

So now it is both sensors. Something common to the both most likely failed. A shop scanner ca test individual components as well as read codes

brucelimerick Enthusiast

brucelimerick

Posted
Posted

I agree with govtech4, I doubt it is the knock sensors. All I have done under the hood of my 2001 is change the oil, everything else is stock and original. Knock is fuel, timing and spark. The engine controler monitors the fuel quality (a sensor to check) and sets the timing. Nothing you can change or adjust there anymore. But to get knock your fuel is igniting early. I doubt it is the plugs, if you have knock they are firing. It would seem to me it could be a fuel issue especially when you mention the 100+ temperatures. You could pull an easy plug and check for deposits. Deposits can give you hot spots in the combustion chamber which can cause pre-ignition. It could be so-so fuel as well. You could try a 1/4 tank of premium and see if that makes a difference. The heat will vapourize the top end of your fuel. It could also be getting some vapour in the fuel line if it is running close to a hot area of the engine. The fuel lines do run close to the exhaust right around your feet and the catalytic converter is right there too.

gmtech4 Senior Enthusiast

gmtech4

Posted
Posted

fuel lines cross over at the rear of the tranny and go up the middle of the transmission so ,not near the exh at all actually

Bad Bowtie2 Enthusiast

Bad Bowtie2

Posted
Posted

You have to seal off the knock sensors to the harness & the knock sensor harness to the main harness as well.

 

Dielectric grease is one option here....

jdaniel83 Enthusiast

jdaniel83

Posted
  • Author
Posted (edited)

Ok so I haven't had time to work on the truck, but will tomorrow. After doing some research I have a couple of questions. 1) I didn't torque the knock sensors to spec (15 ft/lbs. if what I've read is right) I just tightened them down with a 1/2 in drive ratchet. I don't think I over-tightened them. If anything I didn't tighten them enough for fear of stripping the threads. Could not torqueing them to spec cause issues? 2) Can using aftermarket sensors cause issues? First time I did the change I used GM sensors and it worked fine for about a year but then started having issues. So I tried aftermarket (BWD from O'Reillys) and once again they worked fine for about a year or so. Same thing with the third time. This time since money is tight I ordered aftermarket ones off of eBay. Are these computers really that sensitive to aftermarket sensors?

Edited by jdaniel83
Chris Senior Enthusiast

Chris

Posted
Posted

Personally I would stick to AC Delco, Delphi, or Dorman

 

Sent from my Samsung Galaxy S4 using Tapatalk 4

 

 

  • Like 1
cobrajet84 Senior Enthusiast

cobrajet84

Posted
Posted

tried using bwd sensors for a brake light sensor issue I had and they actually made my problem worse, went with the acdelco from the dealer and fixed the problem, and was actually cheaper than the bwd ones from oreillys. So i'm not a fan of bwd.

  • Like 1
TJay74 Senior Enthusiast

TJay74

Posted
Posted

I would use AC Delco sensors, make sure to clean out the sensor chamber and once you put the new ones in RTV the rubber boots down so moisture does not get in and corrode the sensors again.

  • Like 1
jdaniel83 Enthusiast

jdaniel83

Posted
  • Author
Posted

Well I finally got some free time and got the intake back off this morning, and it seems that the knock sensors were a little loose. They were only torqued to about 8-10 ft/lbs so I tightened them down to 15 ft/lbs, used di-electric grease on the connectors, and put the RTV on each of the boots and where the wires go into them. I would have replaced the aftermarket sensors with some AC Delco or Delphi but the only place around here that had either wanted $90 per sensor, and I cant afford nor do I see spending that much on them when I can get them off eBay or from RockAuto for less than that for both. Plus I have to leave town and need my truck tomorrow so I'm going to let the RTV set overnight and hope for the best on the road trip tomorrow. If I'm still having problems I'll take it in somewhere that has a better scanner than me and see what's really going on. Thanks for all the suggestions. Wish me luck.

Chris Senior Enthusiast

Chris

Posted
Posted

If you have to go through it again, check out Amazon

jdaniel83 Enthusiast

jdaniel83

Posted
  • Author
Posted

Just thought I would update. I took off on a road trip and for the first 200 or so miles the truck ran great. No SES light and no valve clatter. Then the SES light came on and the valve clatter began again and continued for the rest of the 800 mile trip. The truck seemed to be running ok besides the valve clatter. Power was better than it had been before the sensor change and MPGs were better also. Still when I got home I pulled the codes and sure enough 0327 and 0332, so I ordered some AC Delco sensors and GM harness to replace the aftermarket ones. As soon as they come in I'll tear it all apart again and replace the sensors/harness again. Hopefully the better sensors will fix the problem, but I'm still going to take the truck into a place with a better scanner so that maybe they can tell me if there's some other issues going on.

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • contrabombarde
      2010 Avalanche 5.3 not running correctly after engine swap.

      By contrabombarde · Posted

      Yes, I used my multimeter to probe all of the wires at the MAF, both with the sensor connected, sensor disconnected, key on engine off, key on engine running, etc etc etc. I probed all of the wires again at the PCM, at the connectors, etc. All voltages are what they should be according to the service manual/wiring diagrams. All grounds are good, less than 20 millivolts from the battery negative under load. Both at the connector of the MAF, at the PCM connector etc.      I know this throws a pretty big wrench into things, but this truck was acting up before the swap. I don't have very much information, if any on what was causing it, but if you cleared all of the dtcs it would do the same thing where it would crank, fire, then die. And it would do the same thing a dozen or so times, and eventually it would start and run, but the difference is that it would run and actually be drivable. Whereas now if you can drive it at all, it goes into reduced power mode almost immediately, and even then it's not running correctly. When you come to a stop at a light it stumbles down to for 500 RPM before catching itself and returning to the smooth idle. And if you go more than about 50% throttle then it immediately goes back to doing the misfire thing.    Like I said, I know that throws a wrench into things, and unfortunately I was not able to pull any data or anything like that before I did this work, so I don't have much to go on.    I'm trying to not fixate on one particular thing as the cause of the problem, but it seems like all avenues are pointing me towards the PCM. Like I said I have tested the wiring extensively (see above), and during cranking the sensor does produce seemingly legitimate values at least according to my multimeter, but as soon as the engine fires those values quickly descend into gibberish. I've tried it with multiple different known working sensors, I have done literally every test I can think of multiple times on the wiring (probing the signals, probing the pins with the sensors unplugged, probing the pins at the PCM, voltage drop, voltage drop under load, continuity, ohms, and double-checking everything against the wiring diagrams/ proper values in the service data.)    Another thing that pushes me towards a possible PCM failure is, I have noticed in troubleshooting a little bit taking a break and coming back, that when I leave the truck to sit for a while and cool off, it starts and runs smoothly when I first start it up. However once it warms up. It starts having problems. For example, when I went out to the truck this morning after it had been sitting overnight, I was actually able to drive it down the block. And then once I got on the throttle a Little bit after going about a thousand ft, it started misfiring again. I pulled it back into the driveway, shut it down, and started it back up. It idled smoothly. As soon as I touched the throttle it did the misfire thing again. From then on as soon as I started it it would misfire. I shut the truck off and went to go get a coffee and do a bit more research. When I came back out I started the truck up and it immediately went into the smooth idle. After a couple of minutes of playing around with it, it would not idle smoothly anymore. Let it sit a couple of hours, rinse and repeat. This makes me think with temperature change something is going wrong inside the PCM. I have the PCM out of the 2007 donor vehicle and I'm thinking of getting a one-day subscription to the ACDelco programming service to try and program that and see if it helps.   Like I said, I'm really trying to not fixate myself on one potential cause, but it seems everything is pointing me towards PCM failure. I would really like to try to confirm that, but unfortunately I don't have an oscilloscope or a signal generator to do the GM service procedure where you feed 5 khz into the signal pin. 
    • Jsdirt
      2010 Avalanche 5.3 not running correctly after engine swap.

      By Jsdirt · Posted

      Ahh, sorry about that - I got some bad info. Newdude is correct. That's what I get for working 13 hours straight ... on my "vacation", lol.   Should've checked the files I had instead of the internet.   Anyway ... this is GREAT news, since this would've been an absolute friggin nightmare to get working.   I don't think the lack of VVT is causing this - you've got another issue. Wiring, I'm betting.   I'm telling you right now, your computer isn't bad. If it worked before the swap, it's working now. You need to do some more (better) diagnostics and figure out exactly what you're missing. Did you test every wire directly at the MAF? Have 5V reference? Ground? If you're reading ZERO g/s, your Hz isn't much use - it's going to be the wrong value anyway. The MAF is not working, and you need to find out WHY.   I got this off the net, so VERIFY first: Pin A: Black (BLK) wire, Circuit 552, serves as the Sensor Return (Ground).  Pin B: Tan (TAN) wire, Circuit 472, carries the Intake Air Temperature (IAT) signal.  Pin C: Yellow (YEL) wire, Circuit 492, is the primary MAF Sensor Signal output to the PCM. Pin D: Pink (PNK) wire, Circuit 339 or 539, provides Ignition 1 Voltage (Power).  Pin E: Tan/Black wire, Circuit 552 or similar, often associated with the Intake Air Temperature ground or signal return.  Global-A list: https://postimg.cc/KKJnQC85    
    • parthery
      GM Hard Folding Tonneau by REV review

      By parthery · Posted

      Correct....the end user can't reach to Realtruck directly like they can if they purchase a Bak, Undercover, etc...  It has to go through a dealer.
    • Matt Parker
      Clunk when putting truck into drive and reverse.

      By Matt Parker · Posted

      It is 4wd. shop told me it is the slip yoke. But not sure.
    • contrabombarde
      2010 Avalanche 5.3 not running correctly after engine swap.

      By contrabombarde · Posted

      No, I did not tune out vvt. From what I read it should still be able to run without it, it'll just lose some torque/power.    I can see how that would make it not run correctly, but why would that cause the faulty MAF readings?   EDIT: I just ran a quick test and checked, and as I expected, the computer sees that the VVT cam phaser solenoid is not present, and throws a code for it, and does not try to change the cam angle at all. Commanded position just remains at zero, 100% of the time. This makes me think that the VVT is most likely not the cause of the problem though if anyone has a different/better explanation, I'm all ears.   UPDATE: I was able to find that my scan tool does indeed support reading the frequency (hz) off of the MAF (I thought it wasn't supported but turns out I just didn't know where to look for it). I noticed that regardless of engine state it always however this Is not what I observed with my multimeter. Like I said before, the MAF seems to put out a normal signal during cranking and then the signal drops to a very erratic reading once the engine is running. It seems from what my scan tool is telling me that the ECM is not recognizing this at all, and just reads 0 Hz 100% of the time. This pushes me towards the the PCM itself is faulty. I I have the PCM out of the 2007 donor vehicle, which I may try to connect and program (it's only ~50 bucks to get the software for a one-time programming)

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...