Notices
86-95 Trucks & 4Runners 2nd/3rd gen pickups, and 1st/2nd gen 4Runners with IFS

stumped by code 52.

Old 03-28-2015, 09:28 AM
  #1  
Registered User
Thread Starter
 
Nathan_F's Avatar
 
Join Date: Mar 2015
Posts: 19
Likes: 0
Received 0 Likes on 0 Posts
stumped by code 52.

OK posted here before. Got some excellent advise. Thanks to the guy who suggest I try to fix my VAF. Was able to do so. Any way 1989 Toyota 4x4 extra cab, base model 5spd, 3.0. Code 52 removed knock sensor, checked with a volt meter, like was suggested here. Good. Checked pigtail lead, fairly new, as is the sensor, no resistance. Checked, shielded wire, good continuity, no continuity to ground. Sensor is not Toyota. Wanna drive this thing, new engine just got running.
Old 03-28-2015, 09:58 AM
  #2  
Registered User
Thread Starter
 
Nathan_F's Avatar
 
Join Date: Mar 2015
Posts: 19
Likes: 0
Received 0 Likes on 0 Posts
Just checked another way. Used ohm meter between ground side of shielded wire and ground. Good continuity. But this is unplugged from the ECM ???? Normally grounded thru another circuit? Appears that shield is connected to 2 other shields and then to a brown wire to the ECM plug. Really stumped now.

Last edited by Nathan_F; 03-28-2015 at 10:11 AM.
Old 03-28-2015, 01:00 PM
  #3  
Registered User
 
scope103's Avatar
 
Join Date: Sep 2007
Location: San Francisco East Bay
Posts: 8,250
Likes: 0
Received 820 Likes on 648 Posts
How did you check a knock sensor with a voltmeter? There IS a way to do it (sorta), but requires an RMS voltmeter and a vibration source.

I've never disassembled the actual KNK wire and shield, but my circuit diagrams show the KNK signal goes to the ECM through connector B, but the grounds connect directly to a Brown wire which is independently grounded at the camshaft bearing cap. So "unplugging" connector B doesn't affect the shield ground to the engine. (Also, connector B doesn't contain the ECU ground.)
Old 03-28-2015, 02:57 PM
  #4  
Registered User
Thread Starter
 
Nathan_F's Avatar
 
Join Date: Mar 2015
Posts: 19
Likes: 0
Received 0 Likes on 0 Posts
I set my meter on the lowest a/c voltage touched the negative to the threads and the positive to the connector terminal and it registered 25mV when I tapped it with an end wrench it jumped to 50mV then settled back to 25mV. I performed this same test with the sender in place and the pigtail connected, only ground probe to block and positive to the pigtail. 2 wires. One is a dead end the other checked about 30mV and when I tapped on the intake with a screw driver it jumped to 100mV. I don't know what the parameters should be. Any answers. Don't want to buy another sender if I don't need to.
Old 03-28-2015, 03:07 PM
  #5  
Registered User
 
scope103's Avatar
 
Join Date: Sep 2007
Location: San Francisco East Bay
Posts: 8,250
Likes: 0
Received 820 Likes on 648 Posts
Good job. That isn't an "official" test (the sensor is "tuned" to a certain frequency), so there is no "parameter," but I would say your sensor is working. (The dead wire on the pigtail is the ground, and it is not connected at the sensor end. Only at the ECU end.)
Old 03-28-2015, 03:37 PM
  #6  
Registered User
Thread Starter
 
Nathan_F's Avatar
 
Join Date: Mar 2015
Posts: 19
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by scope103
Good job. That isn't an "official" test (the sensor is "tuned" to a certain frequency), so there is no "parameter," but I would say your sensor is working. (The dead wire on the pigtail is the ground, and it is not connected at the sensor end. Only at the ECU end.)
Didn't follow you on the ground conversation in first response. There are three shielded wires that have the ground shield connected to each other and to a brown wire that goes only to the ECM. Unless it comes back out at another pin it doesn't go to the can cap. I also read somewhere that if the TPS has an issue that it might cause a code 52. Is this possible. Next step for me might be to bypass the knock sensor in the truck with another externally mounted. This would definitely rule out the sensor that I have and the pigtail. Any other suggestions? Had this thing apart 3 different times (for various reasons). Getting good at it but don't need another habit.
Old 03-28-2015, 03:44 PM
  #7  
Registered User
 
scope103's Avatar
 
Join Date: Sep 2007
Location: San Francisco East Bay
Posts: 8,250
Likes: 0
Received 820 Likes on 648 Posts
My schematic (which is not the same as looking at your wires) shows that the knock sensor, and two O2 sensors (if you have a Calif. vehicle) have shielded wires. The shields all end up on a brown wire that connects to lots of places, including the cam cap, and also to one of the plugs on the ECU. But there is no particular reason that ground wiring in the harness will exactly match the schematic. Ground is ground.

Sort of. The tricky part of the knock sensor is that the shield is only grounded at one end (the ECU "end"). It is not connected to ground at the sensor (that's why the sensor connector only has one pin, but the pigtail-to-harness connector has two). This is probably to prevent what audio guys call "ground loops."

I know that people occasionally mention "bypassing" the knock sensor with one mounted elsewhere (like a lifting hook), but I just can't imagine that would ever work. (Why would Toyota mount it in such an inaccessible location if the lifting hook would work?) But I can't prove it won't work, so you're welcome to try it, but please report back.
Old 03-28-2015, 07:29 PM
  #8  
Registered User
 
Shady Cadence's Avatar
 
Join Date: Mar 2015
Location: Franconia Twp. MN
Posts: 219
Likes: 0
Received 0 Likes on 0 Posts
Get a timing light, and a tachometer if your truck doesn't have one. Connect the tools and get the truck to operating temperature. Have someone hold the throttle at 2000 rpm and note the position of the timing mark. Now tap on the exhaust manifold with a wrench while watching the mark and see if it retards. If it does not, try replacing the knock sensor(it could be weak).
If it still throws the code, or if it DOES properly retard timing yet still throws the code, replace the ecu.
Old 03-30-2015, 07:40 PM
  #9  
Registered User
 
HappyCamper's Avatar
 
Join Date: May 2007
Location: Concord, CA
Posts: 70
Likes: 0
Received 0 Likes on 0 Posts
doesn't the code mean it's working?

Originally Posted by Nathan_F
OK posted here before. Got some excellent advise. Thanks to the guy who suggest I try to fix my VAF. Was able to do so. Any way 1989 Toyota 4x4 extra cab, base model 5spd, 3.0. Code 52 removed knock sensor, checked with a volt meter, like was suggested here. Good. Checked pigtail lead, fairly new, as is the sensor, no resistance. Checked, shielded wire, good continuity, no continuity to ground. Sensor is not Toyota. Wanna drive this thing, new engine just got running.
If you get the code, doesn't that mean it's working? That it actually detected a knock and protected your new motor?

When I replaced my motor, I had drained all the gas because it had been sitting for a while, filled it up with new low-octane gas, set the TPS and timing, and was getting code 52. I added some octane booster (because tank was full, otherwise would have just added some premium gas) and the problem went away. I've been running mid-octane ever since. I've been meaning to try 1/2 tank of low octane and 1/2 tank of mid octane to see what happens but haven't gotten around to it yet.

PS. I've got to remember Shady's method -- excellent!
Old 03-30-2015, 08:55 PM
  #10  
Registered User
 
Shady Cadence's Avatar
 
Join Date: Mar 2015
Location: Franconia Twp. MN
Posts: 219
Likes: 0
Received 0 Likes on 0 Posts
Code 52 is defined as "Open circuit in knock sensor signal (knk)", meaning the ecu is not seeing what it should. The knock sensor is Piezoelectric, meaning it generates voltage from vibration. When the engine starts and runs, the knock sensor generates a very small signal which will spike larger if detonation occurs, prompting the ecu to retard timing. If the ecu does not see that small signal on startup and while running, it will throw code 52.
Old 03-30-2015, 09:18 PM
  #11  
Registered User
 
scope103's Avatar
 
Join Date: Sep 2007
Location: San Francisco East Bay
Posts: 8,250
Likes: 0
Received 820 Likes on 648 Posts
Originally Posted by HappyCamper
If you get the code, doesn't that mean it's working? That it actually detected a knock and protected your new motor?
...
That is exactly wrong.

Shady Cadence's explanation is spot on.

Lots of people seem to think that code 52 has something to do with the engine knocking, so they retard the base timing or use high octane gas. A complete waste of time. Code 52 means "the ECU doesn't know if the engine is knocking (or not)", so it dramatically retards the timing in a desperate attempt to save the engine (in case it IS knocking).
Old 04-01-2015, 06:37 PM
  #12  
Registered User
 
HappyCamper's Avatar
 
Join Date: May 2007
Location: Concord, CA
Posts: 70
Likes: 0
Received 0 Likes on 0 Posts
Good to know

Thanks for the correction! Since I had gotten that code, I'll replace my knock sensor (cheap insurance). Perhaps that's also the solution to the OP's problem. Additionally, I wouldn't trust a cheap aftermarket part in such a critical function.

Originally Posted by scope103
That is exactly wrong.

Shady Cadence's explanation is spot on.
.
Old 04-04-2015, 05:24 PM
  #13  
Registered User
 
50kta's Avatar
 
Join Date: Apr 2015
Posts: 31
Likes: 0
Received 0 Likes on 0 Posts
this code 52 is bull crap im ssooooo tired of dealing with itbut im going to try shadys test tomorrow. fingers crossed
Old 04-06-2015, 11:45 AM
  #14  
Registered User
 
Shady Cadence's Avatar
 
Join Date: Mar 2015
Location: Franconia Twp. MN
Posts: 219
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by 50kta
this code 52 is bull crap im ssooooo tired of dealing with itbut im going to try shadys test tomorrow. fingers crossed
Well, where did it bring you?
Old 04-06-2015, 12:01 PM
  #15  
Registered User
iTrader: (1)
 
catwrangler's Avatar
 
Join Date: Sep 2014
Posts: 30
Likes: 0
Received 0 Likes on 0 Posts
stumped: Me too

93-4rI have a new Toyota KS mounted externally, shielded cable wired directly to ECU harness 5 inches from ECU , new Toyota Pigtail, new (reconditioned/tested) ECU...still have a code 52...WTF, so good luck.
The only thing I can think of is a bad ground somewhere. Hope you find your problem
Old 04-06-2015, 12:14 PM
  #16  
Registered User
 
Shady Cadence's Avatar
 
Join Date: Mar 2015
Location: Franconia Twp. MN
Posts: 219
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by catwrangler
93-4rI have a new Toyota KS mounted externally...
What do you mean, mounted externally?
Old 04-06-2015, 12:43 PM
  #17  
Registered User
iTrader: (1)
 
catwrangler's Avatar
 
Join Date: Sep 2014
Posts: 30
Likes: 0
Received 0 Likes on 0 Posts
Secured under the hood, but external to the normal mounting point under intake.
Old 04-06-2015, 01:20 PM
  #18  
Registered User
 
Shady Cadence's Avatar
 
Join Date: Mar 2015
Location: Franconia Twp. MN
Posts: 219
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by catwrangler
Secured under the hood, but external to the normal mounting point under intake.
Is it firmly attached to the engine?
Old 04-06-2015, 01:55 PM
  #19  
Registered User
iTrader: (1)
 
catwrangler's Avatar
 
Join Date: Sep 2014
Posts: 30
Likes: 0
Received 0 Likes on 0 Posts
secured using two metal hose clamps to engine lift point(I didn't want to drill a hole as others have suggested).
I'm doing my timing belt and valves this week so while I am in there I am putting everything back to normal using the new parts.
Old 04-06-2015, 02:02 PM
  #20  
Registered User
 
Shady Cadence's Avatar
 
Join Date: Mar 2015
Location: Franconia Twp. MN
Posts: 219
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by catwrangler
secured using two metal hose clamps to engine lift point(I didn't want to drill a hole as others have suggested).
I'm doing my timing belt and valves this week so while I am in there I am putting everything back to normal using the new parts.
Put everything back where it's supposed to be and you shouldn't get a code. Attaching to the engine lift point isolates the sensor from the engine noise, and it won't generate the small running signal the ECU looks for.

Thread Tools
Search this Thread
Quick Reply: stumped by code 52.



All times are GMT -8. The time now is 11:32 PM.