2nd Generation Specific (1986-1992) 1986-1992 Discussion including performance modifications and technical support sections.

Knock Sensor

Thread Tools
 
Search this Thread
 
Old Apr 24, 2003 | 02:21 PM
  #1  
AreExSeven's Avatar
Thread Starter
Huh?
Tenured Member 10 Years
 
Joined: Nov 2001
Posts: 1,087
Likes: 0
From: Lost
Knock Sensor

Ok so while I was doing some stuff I broke the wire on the knock sensor connector too close to put it back together, so I cut the other half of the connector off and hooked the loose wires together. Now my check engine light comes on once in a while, usually after driving a bit, throwing the knock sensor code. It goes away if I stop the car and start it, but the code is still in the ecu. So I've cleared the code and it comes back. I just can't seem to get it to go away, no matter how many different ways I reconnect the wire. Is there any other possibiliy that would cause the check light to come on other than a bad connection?

Also, the ECU fail safe method for knock sensor is retarding the timing 2 degrees. Does it run this way until I clear the code, or is it only doing it while the check engine light is on?
Reply
Old Apr 24, 2003 | 06:44 PM
  #2  
AreExSeven's Avatar
Thread Starter
Huh?
Tenured Member 10 Years
 
Joined: Nov 2001
Posts: 1,087
Likes: 0
From: Lost
^
Reply
Old Apr 24, 2003 | 06:59 PM
  #3  
Scott 89t2's Avatar
SOLD THE RX-7!
Tenured Member 10 Years
 
Joined: Mar 2001
Posts: 7,451
Likes: 0
From: Vancouver, BC, Canada
it would always be that way if the code is there weither the light is on or not.

I would try to fix the wire better?
Reply
Old Apr 24, 2003 | 07:14 PM
  #4  
AreExSeven's Avatar
Thread Starter
Huh?
Tenured Member 10 Years
 
Joined: Nov 2001
Posts: 1,087
Likes: 0
From: Lost
I have reattached the wire 100 times. I've used various crimps and connectors. Nothing seems to do the trick. So I want to believe it is something other than the lack of connection that is causing it.
Reply
Old Apr 24, 2003 | 07:18 PM
  #5  
DuX's Avatar
DuX
Full Member
Tenured Member 05 Years
 
Joined: May 2002
Posts: 179
Likes: 0
From: New Jersey
maybe it is just a coincidince, but check out whateer the engine teh ecu is telling you is wrong. Perhaps you knocked the wire out, and now thing the is frigged.
Reply
Old Apr 24, 2003 | 07:25 PM
  #6  
AreExSeven's Avatar
Thread Starter
Huh?
Tenured Member 10 Years
 
Joined: Nov 2001
Posts: 1,087
Likes: 0
From: Lost
The ECU doesn't say what is wrong with it. It just throws code #5 which is the knock sensor. It tells you what part is giving an error, not whats wrong with it.
Reply
Old Apr 24, 2003 | 07:29 PM
  #7  
DrifterFD3S's Avatar
Senior Member
Tenured Member 05 Years
 
Joined: Feb 2003
Posts: 582
Likes: 0
From: DALLAS TX
maybe its actually knocking....
Reply
Old Apr 24, 2003 | 07:32 PM
  #8  
AreExSeven's Avatar
Thread Starter
Huh?
Tenured Member 10 Years
 
Joined: Nov 2001
Posts: 1,087
Likes: 0
From: Lost
Maybe, but I set the timing almost perfectly. And it runs perfectly fine w/o any hiccups or anything.

Oh, and it never did it before I broke the wire...
Reply
Old Apr 24, 2003 | 11:18 PM
  #9  
AreExSeven's Avatar
Thread Starter
Huh?
Tenured Member 10 Years
 
Joined: Nov 2001
Posts: 1,087
Likes: 0
From: Lost
Just tested it and I have continuity between the knock sensor and the 2M pin on the ECU, and I'm still getting the code. Does this mean I need to replace the knock sensor?

Would the ECU throw a code even if it were knocking?
Reply
Old Apr 24, 2003 | 11:22 PM
  #10  
ViperKillerWannabe's Avatar
Resident Moonwalker
Tenured Member 10 Years
 
Joined: Jan 2002
Posts: 173
Likes: 2
From: St. Louis, MO, USA
Did you try soldering it? From my experience, crimps don't work very well for long, so you might want to try it.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
rgordon1979
3rd Generation Specific (1993-2002)
40
Mar 15, 2022 12:04 PM
eddierotary
Engine Management Forum
16
Oct 4, 2016 08:22 PM
83revival
New Member RX-7 Technical
4
Sep 3, 2015 10:42 PM




All times are GMT -5. The time now is 08:21 AM.