Starts....runs 1 second...then dies.
2005 4WD Dakota, 4.7L, auto trans, with over 1/4 tank of gas. The truck is driven nearly daily and has always started fine. Yesterday during normal startup it started, ran for about 1 second and died...would not restart or even start for 1 second. 30 minutes or so later I tried again and same thing happened...although this time I was able to rev the engine before it died...total on time about 2 seconds. Did the same thing about an hour later... If try to restart immediately after the 1 second run time it will not fire at all...must wait for some time before it will even run for the 1 second before dying.
The battery and fuel filter are both very old...don't know why battery would be the cause but I could see a filter doing this...but so suddenly???
Any ideas...??
Thanks, Bob
The battery and fuel filter are both very old...don't know why battery would be the cause but I could see a filter doing this...but so suddenly???
Any ideas...??
Thanks, Bob
If you have another key, try it. It sounds like your chipped key is not being recognized for some reason.
SENTRY KEY IMMOBILIZER — IF EQUIPPED
With this system, an electronically coded ignition key
sends a signal to the vehicle electronics. If the electronics
recognizes the signal, the vehicle will start and continue
to run. If the system does not recognize the signal, the
vehicle will start and run for 2 seconds, then shut off.
After six unsuccessful attempts at starting, the system
will shut down until the correct key is used.
Of course, it could be something else causing the issue.
SENTRY KEY IMMOBILIZER — IF EQUIPPED
With this system, an electronically coded ignition key
sends a signal to the vehicle electronics. If the electronics
recognizes the signal, the vehicle will start and continue
to run. If the system does not recognize the signal, the
vehicle will start and run for 2 seconds, then shut off.
After six unsuccessful attempts at starting, the system
will shut down until the correct key is used.
Of course, it could be something else causing the issue.






