Kevin Varnes
Registered User
Okay here's the deal. I just replaced the head gaskets on my beater '93 SC in my spare time over the past few weeks (been out of town a bit). I finally got it all back together tonight, went to start it and it turns over fine, but no start.
I tested fuel pressure and I'm getting 40 psi on the rail and it appears to hold fine according to the service manual (held 41 psi through GNR Nighttrain). The fuel pump comes on with the key and also when I ground the circuit. According to my made in China spark detector I'm at least getting spark from the coil to the wires (checked two) although I'm not sure how bright the flashes are supposed to be it is flashing. I couldn't check at the plugs becuase I couldn't see while cranking it. I pulled the plugs and while they didn't look great they weren't fouled. Went ahead and replaced them anyway with new Champion coppers (yeah I know, but it's a beater and it runs fine with them). I checked, double checked and then checked again the plug wire locations on the coil and they are good per the Ford Service manual (not the Haynes misprint).
So, I appear to be getting fuel at the rail and spark at the coil. No upshift light while cranking. The car ran fine when I pulled it in. Other than running warm/hot it had no run/start issues. For kicks I scanned for codes before calling it a night and got a 542 (fuel pump circuit open; ECA to motor). I suspect that may be related to me grounding the fuel circuit while testing for pressure as all other indications show me having good fuel pressure (KO and while cranking).
Anybody have any ideas? I just did a quick search on and one thing that I did find was someone mentioning a ground strap from the rear driver's head to the firewall. Don't remember putting that on, but I don't remember taking it off either. I did replace my engine mounts and both ground straps at the engine mounts are attached in the same fashion as before. So I'm completely stumped. Oh one other probably non related thing, but while scanning for codes KOEO the fan did not come on while the computer ran through its diagnostics. Not sure why that was, but I know it did it previously when I scanned for codes. Any help anyone????????
I tested fuel pressure and I'm getting 40 psi on the rail and it appears to hold fine according to the service manual (held 41 psi through GNR Nighttrain). The fuel pump comes on with the key and also when I ground the circuit. According to my made in China spark detector I'm at least getting spark from the coil to the wires (checked two) although I'm not sure how bright the flashes are supposed to be it is flashing. I couldn't check at the plugs becuase I couldn't see while cranking it. I pulled the plugs and while they didn't look great they weren't fouled. Went ahead and replaced them anyway with new Champion coppers (yeah I know, but it's a beater and it runs fine with them). I checked, double checked and then checked again the plug wire locations on the coil and they are good per the Ford Service manual (not the Haynes misprint).
So, I appear to be getting fuel at the rail and spark at the coil. No upshift light while cranking. The car ran fine when I pulled it in. Other than running warm/hot it had no run/start issues. For kicks I scanned for codes before calling it a night and got a 542 (fuel pump circuit open; ECA to motor). I suspect that may be related to me grounding the fuel circuit while testing for pressure as all other indications show me having good fuel pressure (KO and while cranking).
Anybody have any ideas? I just did a quick search on and one thing that I did find was someone mentioning a ground strap from the rear driver's head to the firewall. Don't remember putting that on, but I don't remember taking it off either. I did replace my engine mounts and both ground straps at the engine mounts are attached in the same fashion as before. So I'm completely stumped. Oh one other probably non related thing, but while scanning for codes KOEO the fan did not come on while the computer ran through its diagnostics. Not sure why that was, but I know it did it previously when I scanned for codes. Any help anyone????????