My Bronco II needs help again
Thread Starter
|
New User
Joined: Jun 2004
Posts: 14
Likes: 0
My Bronco II needs help again
I hope you all can help again, you did before.
1988 Bronco II 2.9. I changed the O2 sensor when I was having problems with rich/lean and a code telling me it was the O2 sensor. She drove fine for 1 day then died. The code said it was the ECU. Changed it but she still will not start I get spark and I can hear the fuel pump work. When I spray either in the intake it will start and die.
I have not checked the codes again but the first time I tried to start it the code said system pass. Since it has not run I do not expect any code on this new ECU, am I wrong?
1988 Bronco II 2.9. I changed the O2 sensor when I was having problems with rich/lean and a code telling me it was the O2 sensor. She drove fine for 1 day then died. The code said it was the ECU. Changed it but she still will not start I get spark and I can hear the fuel pump work. When I spray either in the intake it will start and die.
I have not checked the codes again but the first time I tried to start it the code said system pass. Since it has not run I do not expect any code on this new ECU, am I wrong?
Postmaster
Joined: Dec 2001
Posts: 3,742
Likes: 2
From: UT
It is still possible to have codes come up, even though the engine hasn't run.
1) KOEO hard fault codes (the first set of codes during the KOEO test) represent faults that currently exist at the time of the test.
2) There are a few codes (fuel pump, for example) that can be set in continuous memory (the second set of codes during the KOEO test) just from trying to start the engine.
As easy as it is to run the KOEO test, I'd do it, just in case there is something noteworthy.
The fact that it will start on ether suggests that the fault lies in fuel delivery. There's more to fuel delivery than just having the fuel pump run. The engine requires a certain amount of pressure at the fuel rail (tested using a pressure gauge) and that the fuel injectors open and close properly.
Next things I would do are pull the codes and check the fuel pressure.
1) KOEO hard fault codes (the first set of codes during the KOEO test) represent faults that currently exist at the time of the test.
2) There are a few codes (fuel pump, for example) that can be set in continuous memory (the second set of codes during the KOEO test) just from trying to start the engine.
As easy as it is to run the KOEO test, I'd do it, just in case there is something noteworthy.
The fact that it will start on ether suggests that the fault lies in fuel delivery. There's more to fuel delivery than just having the fuel pump run. The engine requires a certain amount of pressure at the fuel rail (tested using a pressure gauge) and that the fuel injectors open and close properly.
Next things I would do are pull the codes and check the fuel pressure.
Thread
Thread Starter
Forum
Replies
Last Post
