Camshaft POS - Tach Issue
My 2000 WS6 is an all stock motor w/ M6 - 76k miles.
I had some intermittent starting where on occasion it would fire on the 2nd or 3rd crank. In the past 6 months I've replaced plugs, wires, crank sensor and finally the camshaft sensor using OEM sensors. I took the car for test drive. The issue came maybe 5 minutes into normal driving conditions. At about 35mph the tach needle dropped to 0 and the car was still cruising but firing poorly...almost like how it feels if you have a plug or two fowled. Upon reading I noticed that the sensor controls timing on cylinders 2 and 8 so that would make sense that it feels that way. At random the needle will pop back up to where it should be reading.
My next step is to pop the manifold back off and check grounding but prior to doing so, would there be any other external checks? My thoughts revolve around fuel injection or ignition coils. Checking the grounds seems like an intimidating task but if that's what it takes then so be it. Because of the random issue, I feel strong that it is related to grounding, which I will need to do some heavy reading in this forum on how to efficiently and properly find the bug.
I would inspect grounds as suggested also the wiring and plug to the cam sensor. I'm guessing the car sits a fair bit. Any chance of rodents getting to the wiring? Anything else happened that may have affected any wires/ connections?
As the 3rd owner, I know the guy before me barely drove it - in fact I want to say he only put maybe 100 miles on the car in the 10 or so years he had it. So to your point, it's very possible something would have gotten into the wires. I haven't done heavy digging for visual inspection on the grounds yet but I think it's very possible I will find something. The car has always been garage kept and still is. No rust and never driven in rain/snow.
I did inspect the harness and pins when I put the new sensor in and it looked okay which is why I'm more willing to bet its going to take some poking around the meter and moving some things around to check for interruption in the resistance. I think a good start is to check the aforementioned grounds.
When I purchased the car an E check was needed, however at the time it would not pass. In doing so, I had a local race shop install new O2 sensors, new throttle position sensor, repaired instrument cluster, and flash computer tune. At this point I passed E-check. The car ran well for the time being but then encountered an issue with starting. The motor would turnover but not fire, until at a max of 3 attempts. Eventually I received the code which I believe was P0335 - related to Crankshaft Position Sensor. At this time in July 2019 I replaced the crank position sensor (ACDelco 213-354 GM OEM Sensor) and installed new plugs and wires (8.5mm LS wire set from Summit SUM-887828 in conjunction with new NGK-TR5GP plugs gapped @ 0.040"). I then took the car back to the shop to have the crank relearned and code cleared. I was given news that the car did accept the relearn procedure, however, if the issue comes back and the tach needle drops to 0, it's likely the Cam Position Sensor. Low and behold on the way home this issue came back. The car would misfire for a short time and tach read 0.
Over the winter I removed the intake manifold and installed the cam position sensor (ACDelco 213-363 GM OEM Sensor). In doing so, I also purchased a new LS1 intake manifold as my original one was cracked and experienced a vacuum leak. New FELPRO gaskets on both intake manifold and throttle body. I installed a new Duralast Thermostat and housing assy (#37987) as well as a new battery. All the while, I have been looking for any electrical shorts or breaks in wires or insulation and haven't found anything damaged or shorting out. I also have a hard time believing it may be an electrical short due to it's predictable nature, but my eyes are open to the potential of that being the case.
****Today*****
The car starts cold with no issues. The engine runs great as it idles toward operating temperature ~200°F. Once it reaches this temperature (about 13 min of idle) the motor will misfire and tach needle reads 0. This happens for about 1 min 30 sec. After that, the tach goes back to it's idle RPM and can be driven. Additionally, if I were to go WOT - wide open throttle - the engine shuts off. It can be started immediately after with no issues, but the ECU obviously does not like going WOT. After a few days my check engine light has finally came on (not sure on code yet - but willing to bet it's related to cam/crank synchronization)
To eliminate some more variables my next steps are to check the thrust bearing play with dial indicator and pry bar to see if the crank thrust (thrust bearing) is worn. Could be losing signal as the wheel moves away from the pick up. I also want to do some more homework on the cam sensor circuit itself in conjunction with the ECU to see if I can probe out something that is causing this malfunction.
Trending Topics
On the other hand everything related to the crank sensor is critical. There are posts here about people going through 2 or 3 crank sensor until they get one which works perfectly, although the AC-Delco ones seem to be much more reliable that the no-brand ones.
The Best V8 Stories One Small Block at Time
What I wish I could pin point and understand why the misfire and tach loses signal when the engine reaches operating temp. And it only happens for 90 seconds....then we're live again and showing idle rpm. It's like clockwork after every cold start. Doesn't matter if I'm driving or idle, the tach loses signal soon as that temp reaches ~200-~205°. Would love an explanation on how temperature and signal loss are related - but maybe before I dig deeper, let's see what the DTC reads first. As mentioned, the light just came on last time I drove it.
On the other hand everything related to the crank sensor is critical. There are posts here about people going through 2 or 3 crank sensor until they get one which works perfectly, although the AC-Delco ones seem to be much more reliable that the no-brand ones.
As mrvedit had suggested, could have gotten a lemon crank sensor - can't hurt to try another.
Also going to hook up to ECU with stock tune just eliminate that variable.
https://ls1tech.com/forums/pcm-diagn...f-voltage.html
It indicates how sensitive the crank sensor is; even needing a clean mounting surface. I've seen other threads where the OP goes through several crank sensors before he finds one that works. I suspect that a marginal reluctor wheel position makes the crank sensor even more sensitive to getting a particularly good one.
https://ls1tech.com/forums/pcm-diagn...f-voltage.html
It indicates how sensitive the crank sensor is; even needing a clean mounting surface. I've seen other threads where the OP goes through several crank sensors before he finds one that works. I suspect that a marginal reluctor wheel position makes the crank sensor even more sensitive to getting a particularly good one.
As a new update I swapped PCMs with stock tune to check the computer isn't the problem but the issue continues to exist. Saturday I pulled the intake off to check the PCM grounds on the back of the driver side cylinder head. Cleaned all surfaces including the washers and the bolt. As I was putting the intake back on, it must have bumped the oil pressure sending unit and it cracked - I've been warned time and time again to watch for that. What are those things like 10 feet tall??? Jeeze. Just one more new sensor to add to the list (and a new deep well socket)...

I look forward to the day I can post the solution to this problem. Thanks again for everyone's input.
https://www.youtube.com/watch?v=PVmOnFHb4oo
cam A brown/white signal
B pink/black ground (low)
c red 12v
crank A signal
B ground low ref
C 12 volts
is this how gen 3 cam and crank are labeled at the plug or is the cam like this
In turn, I did come to find out cylinder 6 continues to misfire. Checking the plug for cracks and likely running a compression test. Looking to eventually replace all fuel injectors as well. At any rate, I'm thrilled this little issue is resolved.











