2nd Generation S-series (1995-2005) Tech Discuss 2nd generation S-series (1995-2005) general tech topics here.

PO340 Camshaft Position sensor code and no tach after Manifold job

Thread Tools
 
Search this Thread
 
Old Jan 26, 2018 | 01:26 AM
  #1  
Besel53's Avatar
Thread Starter
|
New Member
Joined: Aug 2017
Posts: 91
Besel53 is on a distinguished road
Default PO340 Camshaft Position sensor code and no tach after Manifold job

I'm pulling my hair out on this one, so any help would be greatly appreciated. No Tachometer and throwing a PO340 code (camshaft position sensor).

After all the things I did (listed below), I finally got to start it tonight. Took a couple seconds of cranking, but fired up and ran smooth. Tach was being weird, jumping way high, then went to zero, and it's been there since . 2 minutes of run time, then I got a call and had to go. Came back an hour later, started it up, and it spit out PO340. I was hoping it was a fluke, so I cleared it and restarted, but it came back again.

Voltage looks good at connector, pink wire to black, pink to ground, 12+ volts without engine running.

Before the project, tach was fine, and no codes.

Do I just get a camshaft sensor? Or is it possible I screwed something up somewhere? Does the sensor being bad cause the tach to register 0?

Here are some screenshots from Torque lit, not sure what it all means though. One screenshot at idle, other at 2K revs

Did all this, I have a build thread going....

New lower Manifold gaskets
New Valve cover gaskets
New MPI spider upgrade
New Distributor cap and Rotor
New #3 plug
New idler and tensioner pulleys
New plug wires
Cleaned MAF sensor.
Replaced steering rag joint
Fixed clockspring (radio controls and airbag)
Full cooling system flush
 
Attached Thumbnails PO340 Camshaft Position sensor code and no tach after Manifold job-screenshot_20180125-225655.png   PO340 Camshaft Position sensor code and no tach after Manifold job-screenshot_20180125-225518.png  
Old Jan 26, 2018 | 03:15 PM
  #2  
Besel53's Avatar
Thread Starter
|
New Member
Joined: Aug 2017
Posts: 91
Besel53 is on a distinguished road
Default

Sensor was cracked. Fixed now. What was interesting is the RPMs were fine on my scanner, but didn't show on the tach.
 
Old Jan 26, 2018 | 08:54 PM
  #3  
christine_208's Avatar
BF Guru
Joined: Dec 2016
Posts: 5,601
From: Moscow, ID
christine_208 has a spectacular aura aboutchristine_208 has a spectacular aura about
Default

Originally Posted by Besel53
Sensor was cracked. Fixed now. What was interesting is the RPMs were fine on my scanner, but didn't show on the tach.
Thanks for sharing the solution. Was it obviously cracked just by looking at the sensor or did you have to remove it?
 
Old Jan 26, 2018 | 09:39 PM
  #4  
Besel53's Avatar
Thread Starter
|
New Member
Joined: Aug 2017
Posts: 91
Besel53 is on a distinguished road
Default

Originally Posted by christine_208
Thanks for sharing the solution. Was it obviously cracked just by looking at the sensor or did you have to remove it?
I gave up diagnosing and just took the dizzy top all apart again. It was my own fault. Put too long of screw in the rotor, and it broke the magnet off the sensor at the end.
 
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
russ1609
2nd Generation S-series (1995-2005) Tech
9
Jan 30, 2012 07:08 PM
bulletuga
2nd Generation S-series (1995-2005) Tech
3
Jul 26, 2010 08:26 PM
kiwiblazer
The Lounge
13
Jun 19, 2010 03:00 AM
murfthesurf4
Engine & Transmission
5
Nov 26, 2007 11:00 AM
88blackzcand95blazer
2nd Generation S-series (1995-2005) Tech
1
Jan 26, 2007 04:36 PM




All times are GMT -5. The time now is 06:08 PM.