power stroke 6.0 black smoke
#2
Well, some more info would help.
https://www.dieselbombers.com/ford-p...questions.html
But from the very minimal information given, could be the early signs of a turbo sticking, or possibly a gummed up EPB sensor/tube.
https://www.dieselbombers.com/ford-p...questions.html
But from the very minimal information given, could be the early signs of a turbo sticking, or possibly a gummed up EPB sensor/tube.
The following users liked this post:
zx97021 (09-14-2011)
#6
Well, some more info would help.
https://www.dieselbombers.com/ford-p...questions.html
But from the very minimal information given, could be the early signs of a turbo sticking, or possibly a gummed up EPB sensor/tube.
https://www.dieselbombers.com/ford-p...questions.html
But from the very minimal information given, could be the early signs of a turbo sticking, or possibly a gummed up EPB sensor/tube.
Read the link posted above, that will tell you what info I need. The less info you give, the harder it is for someone to diagnose, ESPECIALLY over the net. It's hard enough trying to solve an issue when someone is half way around the world from you and the truck isn't in front of you, but when no info is given, the job becomes immensely more difficult.
Here's the link to cleaning the turbo...
DTS Articles - Turbocharger Reconditioning
The following users liked this post:
zx97021 (09-15-2011)
#7
ok i got ya I use the truck for every day use. It started about two weeks ago while iI was on my way up to my cabin in pa I was on the parkway when it happened first. I plugged in my bullydog to see if ther were any codes and it read a0603 but it was not in use when this took place he truck was still set on stock. I do have the bully dog in use now and seems to be a bit beter now I put in this seafoam last night when I got home and drove to work this morn and it did not smoke or miss at all so I hope this helped but then again I only drove to work about 5 mi
---AutoMerged DoublePost---
---AutoMerged DoublePost---
Last edited by zx97021; 09-15-2011 at 09:42 AM. Reason: Automerged Doublepost
#8
Stupid bullydog reading the wrong damn codes all the time. My buddy had an 04 harley truck that had a triple dog. He would always have problems, use his bullydog to read the codes, and they never made a damn bit of sense. I can tell you already that's what's happening right now again. His would change the letters around in the beginning of the code, so your a0603 is probably supposed to be a P0603. His would put a U in, so instead of properly diagnosing a motor issue, the U signified it was a general function, so instead of a FICM code we were getting a stupid window motor control code or something dumb like that.
A P0603 is a KAM (keep alive memory) code, and I'll bet the Bullydog is actually what is causing it. It's really nothing in 99% of the cases though, it could have happened from a reflash from the bullydog, or even a battery disconnect. I wouldn't worry about it.
If you have further problems be sure to let us know, and thanks for the truck info, helps a lot more!
Here's a few fun facts about some of the generic tuners including the bullydog, provided by Doug from GoGo diesel. If you don't know who Doug is, I'll explain a little bit, this guy will forget more stuff about a 6.0 than most of us will ever know...
Bully Dog used to corrupt the Mode 9 data that was retrievable with an IDS. They would cram files into the pcm that didn't quite match up with what was supposed to be there.
You would go to pull up what the calibration was in the pcm and instead of seeing something like VXAN0N2.hex for example. It would say something like Copyright Bullydog Technologies blah blah blah.
Lots of the try before you buy flashes with a decay rate of 30 days or whatever it was used to burn up PCMs. And then even if you went to load an SCT file into the unit, you would get strange things that would pop up.
Only a blind module installation would bring it back around to normal from that state.
The Sniper stuff never really went back to stock correctly. The TS 5X was based off of that. Neither of them had full transmission control and relied on base torque management and learning capabilites of the processor. Neither were full files.
The diablosport stuff had no trans tuning capabilities. And relied off of only the first 5 characters in the PCM strategy which is a big issue. It also relies on the learning capabilities. And also retrieves the stock file. Modifies only part of it. And sends it back. They are not full files.
Edge evolution was superchips based and had no trans control. Because neither did the superchips. And they even made the same tones as an Xcal2. However since superchips only had and old version of the SCT database, they never really got everything.
To answer your original questions, start with checking out the EPB sensor and tube, it comes off of the drivers side exhaust manifold, should be a stainless tube about 8" long or so, then a sensor at the top. Take the sensor off, clean it up. Take the tube out, clean that out really well too, reinstall and try the truck out. If it still does the hesitation, remove the turbo and clean it per the link above.
A P0603 is a KAM (keep alive memory) code, and I'll bet the Bullydog is actually what is causing it. It's really nothing in 99% of the cases though, it could have happened from a reflash from the bullydog, or even a battery disconnect. I wouldn't worry about it.
If you have further problems be sure to let us know, and thanks for the truck info, helps a lot more!
Here's a few fun facts about some of the generic tuners including the bullydog, provided by Doug from GoGo diesel. If you don't know who Doug is, I'll explain a little bit, this guy will forget more stuff about a 6.0 than most of us will ever know...
Bully Dog used to corrupt the Mode 9 data that was retrievable with an IDS. They would cram files into the pcm that didn't quite match up with what was supposed to be there.
You would go to pull up what the calibration was in the pcm and instead of seeing something like VXAN0N2.hex for example. It would say something like Copyright Bullydog Technologies blah blah blah.
Lots of the try before you buy flashes with a decay rate of 30 days or whatever it was used to burn up PCMs. And then even if you went to load an SCT file into the unit, you would get strange things that would pop up.
Only a blind module installation would bring it back around to normal from that state.
The Sniper stuff never really went back to stock correctly. The TS 5X was based off of that. Neither of them had full transmission control and relied on base torque management and learning capabilites of the processor. Neither were full files.
The diablosport stuff had no trans tuning capabilities. And relied off of only the first 5 characters in the PCM strategy which is a big issue. It also relies on the learning capabilities. And also retrieves the stock file. Modifies only part of it. And sends it back. They are not full files.
Edge evolution was superchips based and had no trans control. Because neither did the superchips. And they even made the same tones as an Xcal2. However since superchips only had and old version of the SCT database, they never really got everything.
To answer your original questions, start with checking out the EPB sensor and tube, it comes off of the drivers side exhaust manifold, should be a stainless tube about 8" long or so, then a sensor at the top. Take the sensor off, clean it up. Take the tube out, clean that out really well too, reinstall and try the truck out. If it still does the hesitation, remove the turbo and clean it per the link above.
Last edited by Mdub707; 09-15-2011 at 10:03 AM.
The following users liked this post:
zx97021 (09-15-2011)
#10
Yes it would. It gets gummed up with soot and crap and sometimes stops working correctly because of it. Usually a good cleaning will help. It's easier to start with that and clean it than the turbo. The EPB tube and sensor shouldn't take long at all to remove/clean/replace. The turbo isn't exactly harder, just a lot more time consuming.
The following users liked this post:
zx97021 (09-15-2011)