P0330 Knock Sensor, 15 min. Hack Repair...
#226
I do not disbelieve what you are saying, but I don't think the ECU engineers would build an audio algorithm into the ECU ... More likely they are looking for step changes and peaks?
One way to get around that would be to feed it a steady signal. No step changes, no peaks, no problem Or a steady tone ...
What I'm getting to is that a vehicle with 200,000+ miles may not be a candidate for an expensive repair
But a bit of weekend fiddling could keep it on the road
Point being we are discussing a temporary hack to get by until a more permanent solution is available. Just taking the "hack" to the logical end ...
Of course I could be completely wrong ... Been there, dun that
One way to get around that would be to feed it a steady signal. No step changes, no peaks, no problem Or a steady tone ...
What I'm getting to is that a vehicle with 200,000+ miles may not be a candidate for an expensive repair
But a bit of weekend fiddling could keep it on the road
Point being we are discussing a temporary hack to get by until a more permanent solution is available. Just taking the "hack" to the logical end ...
Of course I could be completely wrong ... Been there, dun that
Last edited by Broc; 03-07-20 at 11:50 AM.
#228
2002 es 300
Hi Linusvp ,
I have 2002 ES 300 and get the code P0330 . Would you like to help me with the wire color of two knock sensor at ECU if you finished to hack it . Thank you and have a nice day !
I have 2002 ES 300 and get the code P0330 . Would you like to help me with the wire color of two knock sensor at ECU if you finished to hack it . Thank you and have a nice day !
#230
I have 2002 ES300 and get the code P0330 the same here . I would like to ask you how you figured out your knock sensor wire color at ECU. Please help me if you did hack successful .
Thank you for your time !
#231
Thank you very much bob!
My story here. Bought a used 2003 es300 3.0 v6, no check engine light till now. Acceleration sucks, takes 14 to 15s to get to 60mph.
I changed my instrument cluster from junkyard, now i get the check engine light.
So after doing this hack, sensor 1 error comes on. So i checked the splice and lo and behold, the dealer has cut the transparent white wire (sensor 1). So i put it back together and this hack works great till sensor 1 goes out in the future.
So to help someone in the future, maybe your wires are broke or frayed some where, if not than its the knock sensor or clogged up fuel injectors and or bad gas. And ebay have reasonable prices for original denso knock sensors.
My story here. Bought a used 2003 es300 3.0 v6, no check engine light till now. Acceleration sucks, takes 14 to 15s to get to 60mph.
I changed my instrument cluster from junkyard, now i get the check engine light.
So after doing this hack, sensor 1 error comes on. So i checked the splice and lo and behold, the dealer has cut the transparent white wire (sensor 1). So i put it back together and this hack works great till sensor 1 goes out in the future.
So to help someone in the future, maybe your wires are broke or frayed some where, if not than its the knock sensor or clogged up fuel injectors and or bad gas. And ebay have reasonable prices for original denso knock sensors.
The following users liked this post:
Bobster999 (07-01-24)
#232
My main aim was to get my car shifting into 4th gear with no check engine light and fault codes showing up. I also had no intention of removing the inlet manifold and fitting new knock sensors. I tried all the tricks I could find on the forums including Boxster's by wiring up each sensor in turn - both are faulty - and also trying a second hand sensor earthed to various brackets on the motor but nothing worked. A test drive always resulted in a CEL and no 4th gear.
By chance I decided to clamp the knock sensor with the threaded end firmly in contact with the inlet manifold, and this was the solution I was looking for. The microphone in the knock sensor needs to be in close contact to generate sufficient AC voltage to satisfy the computer, not screwed to a bracket attached to the cylinder head, or somewhere else.
My earlier thread titled "2001 Toyota Harrier" has pictures of how I did this. I hope nobody minds me posting the solution to my problems here and if it helps anyone I would be very pleased. The s/h sensor I used cost ZAR50 (under $3) and my car now runs perfectly.
Thanks.
By chance I decided to clamp the knock sensor with the threaded end firmly in contact with the inlet manifold, and this was the solution I was looking for. The microphone in the knock sensor needs to be in close contact to generate sufficient AC voltage to satisfy the computer, not screwed to a bracket attached to the cylinder head, or somewhere else.
My earlier thread titled "2001 Toyota Harrier" has pictures of how I did this. I hope nobody minds me posting the solution to my problems here and if it helps anyone I would be very pleased. The s/h sensor I used cost ZAR50 (under $3) and my car now runs perfectly.
Thanks.
#233
Works great
Thanks for posting this, I don't splice wires, just cut the bad sensor and add jumper to it. Now i can rev above 5k rpm, have overdrive, and a lot of knock. Gotta need higher octane fuel
Edit: interestingly enough, my rx now misfired like mad and revs slower.
Edit2: after resetting ECU, I got the power back when warm. The knock also gone
Edit: interestingly enough, my rx now misfired like mad and revs slower.
Edit2: after resetting ECU, I got the power back when warm. The knock also gone
Last edited by qoqzgood; 11-23-20 at 10:26 AM. Reason: Add more more details
#234
I have gone thru all 14 pages of this thread hoping to find the answer, but could not. I have a 2004 RX330 and am looking for the hack for this. I found one picture explanation online where the wires are in the second bank from the bottom with black and red wires. I cut those and reconnected as pictured but the code is still present. Obviously these were the wrong wires. Can someone who has done this hack on an 2nd gen assist me? Attached is the photo that I used for my wiring. Obviously it is wrong.
#235
Hi Internal88, the RX300 has piezo single wire knock sensors. Your RX330 has resonance type two wire sensors. The red (pin2) and the black (pin 1) are the correct wires to bridge together but perhaps you should also cut the white earth wire (pin28) and join it to green wire (pin 20) . I read a post where this was done successfully. Hope this helps, let us know.
#236
Thanks Bob I have not seen many people do this hack on their RX330. This is the scary part.
Anyway, I found out my local mechanic would charge me $350 labor for the knock sensors replacement. Which is a very fair price since the book listed 3.5 hours job. I would have to supply the OE parts and probably replaced the spark plugs at 120,000 miles.
Anyway, I found out my local mechanic would charge me $350 labor for the knock sensors replacement. Which is a very fair price since the book listed 3.5 hours job. I would have to supply the OE parts and probably replaced the spark plugs at 120,000 miles.
#237
yes i have already used this hack i replaced both knock sensors on my 2000 RX300 knock sensors wire harness and all that darn ECM KEEP READING MY KNOCK SENSOR BANK 2 AS BAD THANK GOD FOR THIS BRILLIANT HACK !
The following users liked this post:
bobwatt (10-10-20)
#238
#239
Ok so to save time I will give you the easy details instead of answering PM's. My car is a 99/00 model so here is the dilly-o... Where my thumb is there is a black and white wire right beside each other. The white wire is more of a clear color than a white color. Anyway, the black wire is to the sensor # 2 and the white is for #1. For my example, my #2 sensor is bad, So i cut the wire and connected the part of the wire going to the ECU to the #1 sensor right next to it. This way the computer just uses the input from the first sensor and all is well. It so simple it makes me wanna slap myself. lol... ......... She runs beautiful and.....oh yea, I do love my Lexus!
The following users liked this post:
Bobster999 (07-01-24)
#240
If a person had a modest scan tool (i.e. one that let you monitor live data for at least some PIDs) would there be some way to tell from the scan tool whether this hack has been performed on a car you are evaluating? It seems to me that if this hack had been done, then the data from both knock sensors would be in lock step with each other. And I am suspecting (but do not know) that in real life, they would be sending slightly different info at any given moment in time.
I have an Actron CP9580, but have not learned enough about the live monitoring side of it to use it effectively. But if it would let me determine this, it could be useful if I found myself evaluating another RX300.
I suspect that there are some PIDs that should be looked at closely here, but I do not know what they are. I also wonder if access to TechStream Lite would be enough of a tool to determine if this had been done.
My understanding is one would need to remove the glove compartment to determine visually whether this hack had been done.
I have an Actron CP9580, but have not learned enough about the live monitoring side of it to use it effectively. But if it would let me determine this, it could be useful if I found myself evaluating another RX300.
I suspect that there are some PIDs that should be looked at closely here, but I do not know what they are. I also wonder if access to TechStream Lite would be enough of a tool to determine if this had been done.
My understanding is one would need to remove the glove compartment to determine visually whether this hack had been done.