Pruittx2
Been around a bit
Yes,, I concur :iagree: ):h
-
Welcome to The Truck Stop! We see you haven't REGISTERED yet.
Your truck knowledge is missing!
- Registration is FREE , all we need is your birthday and email. (We don't share ANY data with ANYONE)
- We have tons of knowledge here for your diesel truck!
- Post your own topics and reply to existing threads to help others out!
- NO ADS! The site is fully functional and ad free!
Problems registering? Click here to contact us!
Already registered, but need a PASSWORD RESET? CLICK HERE TO RESET YOUR PASSWORD!
Cranks, but won't fire
- Thread starter sspence65
- Start date
buddy
Active Member
Does the WIF light work when you first turn on the ignition?
Lacking fuel can point to a PMD, but you do have an IP problem. Has the SES light been on at all in the recent past, or the truck seem real sluggish? cant imagine youve have a bad OS for a while an not noticed and now coincidentally also have a bad PMD. Definately should remote mount the PMD regardless anyway.
Lacking fuel can point to a PMD, but you do have an IP problem. Has the SES light been on at all in the recent past, or the truck seem real sluggish? cant imagine youve have a bad OS for a while an not noticed and now coincidentally also have a bad PMD. Definately should remote mount the PMD regardless anyway.
Acesneights1
New Member
Can you elaborate on that ?
IIRC you can operate the shutoff manually ??. Anyway just thought that sounded a little screwy.What do you mean 3 bolts ? The ESO screws into the IP. Do you mean the 3 bolts that hold the ip shaft to the cam gear because if they backed out or are missing the IP no turny, could give OS codes ?? Just not sure what you mean .
buddy
Active Member
I was kind of thinking his IP internals are busted (since the nuts came off before, and must have turned and broke off the ESO solenoid). And it should have been retimed after getting nuts back on. Then ULSD without a good lubricant additive.
The ESO/FSO wont cause the OS codes but will cause no fuel, but also with another code which is not present. The ESO solenoid plunger can be removed easily by removing the snap ring. PMD also wont cause OS codes.
The ESO/FSO wont cause the OS codes but will cause no fuel, but also with another code which is not present. The ESO solenoid plunger can be removed easily by removing the snap ring. PMD also wont cause OS codes.
sspence65
New Member
Months ago the three nuts that hold the pump on came off. Only the injection lines were holding the pump in place. Engine still ran. I reinstalled them. Of the 4 tangs on the bottom of the ESO, one was cracked, one was completely broke off. Fuel leaking badly from bottom of ESO. Used jbweld to put the eso back on. This was the same time the nuts came off the pump. Since then, no sluggishness, no bad fuel mileage (20mpg), everything running smooth and beautiful. No water in fuel light or anything out of ordinary except the engine light and the two codes mentioned.
buddy
Active Member
Does the WIF light work though? It should come on to test the light when you first turn on ignition.
Was there any SES light before the truck died?
Were you pulling that 30' trailer around at the time?
Was there any SES light before the truck died?
Were you pulling that 30' trailer around at the time?
Acesneights1
New Member
Hmmm....I'd be suspicious of that ESO Never seen the three nuts come off an IP before. The ESO is ridicoulous money from the Stealer. I bought a used one from Accurate Diesel for around 35-40$ IIRC.
buddy
Active Member
A failed ESO will cause a different code and not cause the codes that are present. Have to eliminate the possibilities that the symptoms actually support, which is an OS issue, or internal IP failure where the cam reference is not spinning to keep up with the crank sensor and not pushing fuel.
Because it should start in limp mode with a bad OS unplugged, the issue must not be just a bad OS, like actual broke IP. If it were a bad OS then there is another problem as well, like a PMD, or a fuse blown that powers the PMD. Is there a blown Fuel Solenoid (FSOL) fuse (which would likely cause an ESO DTC)? Or ECM B fuse or other ECM fuses? I dont know the fuses on OBDII.
Of course bad fuel, or especially air in the fuel will cause all sorts of strange things that are unexplained. Although would expect some random other DTCs, like 18, 35, 36, etc....
Because it should start in limp mode with a bad OS unplugged, the issue must not be just a bad OS, like actual broke IP. If it were a bad OS then there is another problem as well, like a PMD, or a fuse blown that powers the PMD. Is there a blown Fuel Solenoid (FSOL) fuse (which would likely cause an ESO DTC)? Or ECM B fuse or other ECM fuses? I dont know the fuses on OBDII.
Of course bad fuel, or especially air in the fuel will cause all sorts of strange things that are unexplained. Although would expect some random other DTCs, like 18, 35, 36, etc....
- Staff
- #29
All three of those are possibilities here, still.
PMD will cause 0251 and has been known to cause even stranger ones ... even though (you're right) it shouldn't. If the PMD is acting up (but not dying), strange things happen in the IP and so the whole feedback circuitry can report inaccurately. That's why a lot of codes disappear when the root cause is fixed, something that's occasionally lost on dealership technicians, leading to chanigng everything that was indicated, all at once, leading to BIG repair bills.
The PMD could well be the major culprit here, although the IP has had more than its fair share of breaks and knocks... I'd be tempted to just change it out of sympathy... poor thing.
sspence65
New Member
The SES light was not lit until the truck quit. I was not towing at the time. I do not recall seeing a wif light, ever.