No fuel pressure at startup...?
 

I got in my Mustang this morning, turned the key to prime (both) pumps, and it never stopped running...?

I installed a 255lph in-tank 2 years ago, along with the T-rex for the S-trim. Worked great for 2 years and 5K miles...

Suddenly (when I was to display it at Ford this morning) it doesnt
stop running. No fuel pressure, car wont start, and keeps running in key-on mode (not just for 2 seconds).

I can hear that at least the loud T-rex is running. No fuel on the ground. Just no fuel getting to the injectors. I dont believe that I did anything to affect this (didnt play with fuel system), just suddenly started this morning.

WHAT IS IT?

Check the fuel pump relay. It should be under the driver's seat under a little metal bracket. It can be replaced for around $15 from your local parts store. Sometimes they can stick as they get old.

--nathan

Had the car out 2 days prior, and all was working fine.
(was in a hurry to get to work, and when car didnt start,
just took the Ranger)

Ok, I'll look into a few things:
1. Check and verify that _both_ pumps are running. I can
easily hear the loud T-rex (only?).

2. See if the 2 separate relays are all grounded and
not sticking. (did have stuff in the wheelwell area, and
may have bumped relay#2 or something...)

3. I have the JMS Autologic chip still in there (didnt play with the tweecer, yet).
Havnt touched the J3 port, but maybe, just maybe I jiggled the wires as I cleaning the car out last night. If may be a dirty J3 connector.


Thanks guys, this all helps!!!

Hopefully its nothing serious, and just a simple
loose wire/connection somewhere. I plan on leaving
in 24 hours for two opentrack (vacation) days!

Well I got home last night and re-tested... First just tried it again (hoping it went away), and pumps ran no stop.

So I unplugged the T-rex solenoid, and the 255lph in-tank one ran. Plugged in the T-rex and BOTH were running. Hmmmmm?

So I unplugged the Autologic chip at the J3 port (in/out several times). Turned the key, and voila, FIXED!!!

That was it, a dirty connection on the J3 port.
Thanks guys.

I'll bet it's a dirty connection on the J3 port.

;)

I second that. Good call, Chris. :D

--nathan