blowre1
Registered User
My daily driver pickup recently got stolen and I need to fix my dad's King Ranch 6.0L to have a truck again. It's either a 2004 or 2006; he took the paperwork out of it and the batteries were dead yesterday when we checked in it.
He got so fed up with local Ford dealer changing "bad injectors" he parked it and bought a new ford diesel this summer.
I'm not a diesel mechanic, but I have fixed lots of little things. I found these websites for troubleshooting 6.0L:
http://www.internationalpowerstroke.com/6.0L-powerstroke-problems.html
http://performancewise.net/ford/ford-6-0l-power-stroke-problems/
Real quick history: Bought used with 80,000 miles and no maintenance records. Truck went through 2 reman sets of injectors then one new ford set. No known aftermarket products. We had long periods of time between problems. Started losing power slowly after new injector set, then would start cold and die when warm, and now won't start at all. Has ~200,000 miles.
The first thing I'm going to do is get it to a Ford dealer or other fancy code reader to have all the codes and such pulled.
Any other great ideas? Do we have a 6.0L troubleshooting algorithm for such cases?
Brooks
He got so fed up with local Ford dealer changing "bad injectors" he parked it and bought a new ford diesel this summer.
I'm not a diesel mechanic, but I have fixed lots of little things. I found these websites for troubleshooting 6.0L:
http://www.internationalpowerstroke.com/6.0L-powerstroke-problems.html
http://performancewise.net/ford/ford-6-0l-power-stroke-problems/
Real quick history: Bought used with 80,000 miles and no maintenance records. Truck went through 2 reman sets of injectors then one new ford set. No known aftermarket products. We had long periods of time between problems. Started losing power slowly after new injector set, then would start cold and die when warm, and now won't start at all. Has ~200,000 miles.
The first thing I'm going to do is get it to a Ford dealer or other fancy code reader to have all the codes and such pulled.
Any other great ideas? Do we have a 6.0L troubleshooting algorithm for such cases?
Brooks