Rockledge
Pluggin' away
OK folks, this is the second time my SHO simply died on me, completly out of nowhere, and left me stranded with a no start condition. Now I suppose that means my initiation into the world of the SHO is proceeding right on schedule finger , but I kinda like driving it so I hope someone can help me out here.
The background: We (my SHO and I) were out on our usual Saturday morning sprint ...zipping along at a very good clip on a nice flat and straight expressway, had it up to about 5500 RPMs in 4th gear and was getting ready to shift into 5th when all of a sudden NOTHING. Engine is dead. Shifted into nuetral, tried starting it, but nothing. Rolled almost a mile (yep) to the next exit ramp and was able to get it off the expressway. Tried starting it many times, but nothing. Left it alone for 30 minutes and tried. Nothing. Tried again a few hours later. Nothing. Just cranks.
Codes pulled are as follows: 116, 114, 543, 524 repeat, and then 157, 214, 524, 542, 543 repeat.
Now, I recently had a fuel pump problem and so I had already gotten the 542, 543 and 524 codes during that ordeal. I replace the fuel pump and the CCRM and thought that was the end of it for those codes, though.
The 214 - Error in Cylinder ID (CID) circuit or signal code - I understand is usually the CID sensor which would make sense regarding the instantaneous shut down of the engine.
The 114 - IAT sensor out of range code and the 116 - Engine Coolant (ECT) sensor out of range code I think might be attributable to the fact that I didn't get a chance to pull the codes until the engine was cool and it is about 28 degrees outside right now.
But what about the 157 - Mass Air Flow signal is/was low or grounded code? That seemingly has nothing to do with any of the other codes nor can it easily be explained away by ambient temperature or anything else. So I'm thinking maybe there is another common cause to all of these sensor-related codes I am getting.
So what do you all think? Where should I initally focus my energy? I was thinking about replacing the CID sensor but I don't want to throw $$ at a part that may be OK but simply not operating properly because of some other problem.
Thanks in advance for any feedback.
<small>[ December 25, 2003, 10:26 PM: Message edited by: Rockledge ]</small>
The background: We (my SHO and I) were out on our usual Saturday morning sprint ...zipping along at a very good clip on a nice flat and straight expressway, had it up to about 5500 RPMs in 4th gear and was getting ready to shift into 5th when all of a sudden NOTHING. Engine is dead. Shifted into nuetral, tried starting it, but nothing. Rolled almost a mile (yep) to the next exit ramp and was able to get it off the expressway. Tried starting it many times, but nothing. Left it alone for 30 minutes and tried. Nothing. Tried again a few hours later. Nothing. Just cranks.
Codes pulled are as follows: 116, 114, 543, 524 repeat, and then 157, 214, 524, 542, 543 repeat.
Now, I recently had a fuel pump problem and so I had already gotten the 542, 543 and 524 codes during that ordeal. I replace the fuel pump and the CCRM and thought that was the end of it for those codes, though.
The 214 - Error in Cylinder ID (CID) circuit or signal code - I understand is usually the CID sensor which would make sense regarding the instantaneous shut down of the engine.
The 114 - IAT sensor out of range code and the 116 - Engine Coolant (ECT) sensor out of range code I think might be attributable to the fact that I didn't get a chance to pull the codes until the engine was cool and it is about 28 degrees outside right now.
But what about the 157 - Mass Air Flow signal is/was low or grounded code? That seemingly has nothing to do with any of the other codes nor can it easily be explained away by ambient temperature or anything else. So I'm thinking maybe there is another common cause to all of these sensor-related codes I am getting.
So what do you all think? Where should I initally focus my energy? I was thinking about replacing the CID sensor but I don't want to throw $$ at a part that may be OK but simply not operating properly because of some other problem.
Thanks in advance for any feedback.
<small>[ December 25, 2003, 10:26 PM: Message edited by: Rockledge ]</small>