xSlowbalt09x

Saying that it has a bad circuit on sensor/bank 2? engine-codes.com said to replace the knock sensor and it would most likely fix the CEL. Just replaced the knock sensor on the car myself. CEL is still on. No loss of power before or after the install, no real issue it seems like. The car is tuned but has never really had any problems.

I can visually inspect the wiring but I seriously doubt I will find anything. If the wiring looks good visually, how do I prove it from a technical standpoint?

I refuse to buy a new PCM or ECM before breaking down and going to the dealer. I don't know how to determine which one is "bad" anyway.

Does anyone have any thoughts on this? I really don't want to go to the dealer. I will definitely get raped but I am guessing they would have the technology to fix this, correct?

Anything is appreciated.

Chevrolet Cust Svc

I see you have a 2009; you should still have warranty coverage of some sort. If you wanted to send me the last 8 of your VIN and current mileage I could look into what's still in effect on your vehicle.

Best,
Sarah
GM Customer Service

Gremlin85

iTrader: (8)

Wow, I haven't heard of anyone getting that code on these before lol. If you replaced the correct sensor (assuming you have) then it's gotta be wiring or PCM. Definitly try warranty first seeing as that any mod you've possibly done to your car wouldn't have made the Knock Sensor go bad.

Chevycobaltss3

iTrader: (2)

I have, a few times. Once was a lnf that was tuned by a shop in Louisville that had massive kr. It sent the signal to the ecm and it through the code. I checked the wiring out and etc and no issue. I later retuned it and its good. The other csr was a wiring issue.

xSlowbalt09x

i will have to check the wiring but i don't believe that it is.

chevy - you believe a retune will fix this issue? the car needs to go back to the dyno anyway due to new mods anyway.

and whats a kr?

Chevycobaltss3

iTrader: (2)

Kr "knock retard". Log it first and check. But if your heavily getting kr it can cause true cel.

twilson380

Did you ever figure out what the cause of the code was? Bad KS or ?