12thManChild said:
Howdy,
You've already stated what i think it may be, but it's still very likely associated with cam/crank correlation. We had an nb with the same cam sensor in the valve cover. any irregularity in depth on install would create the same symptom you have with crank/no start. We did also have a bad sensor right out of the box and had to get a 2nd cam sensor. finally getting it physically close enough to the cam sprocket fixed our issue. if you still have the old sensor, does throwing it back on make any noticable change?
Just spit-balling based on miata life: have you confirmed that it is still in time? Sounds like you got down to water pump, but can't tell if you had to touch idler/tensioner. I've had 1.6/1.8s jump a tooth when speeding through replacement.Mainly happened on the intake side. Now i use the crossed boxed wrench and a clamp method or 3d printed cam lock just to be sure I don't screw it up like I normally would.
Sorry I don't have more useful advice. If it's not firing with starting fluid down the pipe, based on your description of the issues and video, my first check would be physical timing.
Good Luck!
Thanks for the thoughts!
We replaced the cam sensor, but the codes remained. The new sensor was a little shorter and smaller than the original. So I replaced the replacement with one that looked exactly like the original, and the code went away. I know the crankshaft sensor is good, because the water pump starts up when I manually turn the tooth past the sensor.
We didn't touch the timing belt. I thought we were going to have to fix the gasket behind the water pump, but the problem ended up being with the outflow. So we didn't mess with the timing belt at all including tensioners and didn't remove the water pump.
It was doing similar stuff before, but it was an air flow problem. That doesn't seem to be the issue now. Also, we didn't touch the fuel system, so I don't think that's the problem. I appreciate the help and may try jacking with the cam sensor again. When it finally started running last time, it ironed out all those issues and ran smooth. I feel like it would do that again if I could get to to start up, but that's probably just wishful thinking.