Ferrarium your a big help to people here.
@Ferrarium were you able to locate a pic for the top crank sensor bolt. I have the 24" extension and still can't seem to get in there. Thanks!
2-ft quarter inch extension swivel and then a one foot extension. There is a 20 degree or so angle. Put a bright light under the car shining up you'll be able to see it. Push it through then go under the car put the socket on the bolt. Go back to the fender well and loosen it up. Then you can go underneath and remove it with your fingers. Same process in reverse. Sent from my SM-G990U using FerrariChat.com mobile app
Ok...we finally managed to swap the 5-8 sensor today. Unfortunately, the intermittent stumble and 5-8 CEL is still happening. At one point during the troubleshooting process this car ran without symptoms so I'm still convinced these crank sensors are the issue. But...maybe its in the wiring from the connector to the ECU? What should I check next? I was thinking of hitting the connectors with contact cleaner. Any other ideas?
What is the CEl code? If it is crank sensors it's usually the wire in front of the plug. But the code you have to pull. Sent from my SM-G990U using FerrariChat.com mobile app
Have you check the spark when it is stumbling. A number of years ago I had a similar problem on my 355. Intermittent misfire, running on 6 cylinders. Turned out to be a bad coil. Coils are cheap, about $50 at Rockauto.
Wouldn't be the first time. Sometimes the crank sensor wiring damage is more visible: https://www.ferrarichat.com/forum/posts/148738152/ https://www.ferrarichat.com/forum/posts/145947012/ Othertimes not. Because the left bank (5~8) crank sensor also supplies data to the tachometer, in theory, you may see a more dramatic rpm change on the tacho than the actual engine rpm. It would depend on how long the problem persisted.
Excellent. Thanks. So an unplugged Cat ECU will cause a code but not light the CEL. What is weird to me is that the code for a "bad" Cat ECU was the first code to flash. If that code does not light the CEL, it should be a low priority fault. So either it was the oldest code stored and it flashed oldest to newest or the priority is lowest to highest.
