Recent Hard Start Unusual
I waited a few moments and retried to start the engine. Same circumstances - no start. On the fourth attempt the engine caught and everything seemed to be fine (less the cloud of unburned fuel surrounding the truck). This is my first diesel. I waited for the glow plug indicator to go out, didn't touch the accelerator, and only cranked for about a 45 seconds on each attempt. Should I have done anything differently?
Thanks for all the good advise in past posts.
DanAZ350 03 6.0 CC 4X4 LB
I would make a trip your dealer. A visiual inspection, fuel pressure check, a test on the injectors and glow plugs should be done by your tech.
I waited a few moments and retried to start the engine. Same circumstances - no start. On the fourth attempt the engine caught and everything seemed to be fine (less the cloud of unburned fuel surrounding the truck). This is my first diesel. I waited for the glow plug indicator to go out, didn't touch the accelerator, and only cranked for about a 45 seconds on each attempt. Should I have done anything differently?
Thanks for all the good advise in past posts.
DanAZ350 03 6.0 CC 4X4 LB
Welcome to the 6.0 L forum and FTE. Please take a moment to check out the Welcome sticky at the top of the forum page. It has a number of links to great threads and other info.
Regarding the hard to start thing. It's been seen occasionally by others. In fact that same thing did happen to me about a week ago for the 2nd time since I've owned the truck. It's been starting fine since.
Normally my truck will fire within a second or two of cranking but this time it didn't. After it cranked for about 8 to 10 seconds I stopped and waited a bit and then cranked again. After it didn't fire after cranking for a while I turned off the truck and waited a bit and then turned it back on and waited for the glow plugs to cycle again and then hit the key. Vroom, fired immediately.
Sometimes I think that the computer just gets confused. One of our other uses posted that turning the key off and then repeating the start sequence is kind of like a ctrl+alt+del reboot and seems to clear the problem.







