Go Back   Ford Truck Enthusiasts Forums > Diesel > 6.7L Power Stroke Diesel
Sign in using an external account
Register Forgot Password?


6.7L Power Stroke Diesel 2011-2015 Ford Powerstroke 6.7 L turbo diesel engine

Reply
 
 
 
 
LinkBack Thread Tools Search this Thread
  #1  
Old 12-29-2010, 09:02 PM
JerryEdinger JerryEdinger is offline
New User
 
Join Date: Jul 2010
Posts: 6
JerryEdinger is starting off with a positive reputation.
Check Engine Light

I have a 2011 F350 6.7 loaded Lariat SRW 4x4. I recently had the check engine light come on and noticed that I was using a lot of DEF. Took it to the dealer and they diagnosed the issue as being the heater in the DEF tank. Thery had to replace the DEF Tank Heater Asm to resolve the issue, a week later the check engine light was back on throwing the same fault code. Truck is now in for repair.. Anyone having the same issue?
Reply With Quote
  #2  
Old 12-30-2010, 02:51 AM
Scott96fs Scott96fs is offline
Freshman User
 
Join Date: Dec 2010
Posts: 27
Scott96fs is starting off with a positive reputation.
Do you know what codes the truck is throwing? My check engine light came on last week while I was up in some cold weather. I ran a check and got 2 codes that were showing, P138B and P20C2. I took truck to dealer on Thursday morning, Thursday afternoon they called saying that the truck had needed a software update which caused the check engine light to come on. So I go to pick it up, start the truck and before I could even pull out of the drive way of the dealer back comes the check engine light. So I turn right around (not very happy at this point) and tell them its back on and that it needs to be fixed. 4 days later they finally figured out what the problem was, apparently the P138B code was a glow plug module fault code, that was caused by the power plug to the glow plug controller not being snapped completely in. Once they got that figured out they found that the P202C code was caused my the Uria (DEF) heater connector also not being plugged in all the way. So 4 days in the shop to find out all my troubles were caused by 2 connectors not being plugged in by the factory when the truck was assembled. Although I am glad it was nothing serious, I hate to see a $60k truck with 500 miles on it giving me problems. The ford technicians don't seem to know what they are doing and had to call some big shots with ford corporation to even figure out what the codes were. Sorry for the long winded answer but maybe this will save somebody some time and headache!
Reply With Quote
  #3  
Old 12-30-2010, 05:48 AM
Marauder92V's Avatar
Marauder92V Marauder92V is offline
Posting Guru
 
Join Date: Oct 2010
Posts: 1,774
Marauder92V has a good reputation on FTE.Marauder92V has a good reputation on FTE.
Quote:
Originally Posted by Scott96fs View Post
Do you know what codes the truck is throwing? My check engine light came on last week while I was up in some cold weather. I ran a check and got 2 codes that were showing, P138B and P20C2. I took truck to dealer on Thursday morning, Thursday afternoon they called saying that the truck had needed a software update which caused the check engine light to come on. So I go to pick it up, start the truck and before I could even pull out of the drive way of the dealer back comes the check engine light. So I turn right around (not very happy at this point) and tell them its back on and that it needs to be fixed. 4 days later they finally figured out what the problem was, apparently the P138B code was a glow plug module fault code, that was caused by the power plug to the glow plug controller not being snapped completely in. Once they got that figured out they found that the P202C code was caused my the Uria (DEF) heater connector also not being plugged in all the way. So 4 days in the shop to find out all my troubles were caused by 2 connectors not being plugged in by the factory when the truck was assembled. Although I am glad it was nothing serious, I hate to see a $60k truck with 500 miles on it giving me problems. The ford technicians don't seem to know what they are doing and had to call some big shots with ford corporation to even figure out what the codes were. Sorry for the long winded answer but maybe this will save somebody some time and headache!
Scott -- what was your build date? Just curious since I read another post with problems on a truck with low mileage. My truck was built on 12/2. Wondering if these are all related.
__________________
F350 4x4 Crew, Short Bed, Diamondback Tonneau, DuraFlaps, Ford LockPick, Extended Remote Start, DDM HIDs all around, Epic door seals
Reply With Quote
  #4  
Old 12-30-2010, 07:27 AM
Adobe 11SD's Avatar
Adobe 11SD Adobe 11SD is offline
Senior User
 
Join Date: Sep 2010
Location: League City, TX
Posts: 407
Adobe 11SD is gaining momentum as a positive member of FTE.
Quote:
Originally Posted by Scott96fs View Post
Do you know what codes the truck is throwing? My check engine light came on last week while I was up in some cold weather. I ran a check and got 2 codes that were showing, P138B and P20C2. I took truck to dealer on Thursday morning, Thursday afternoon they called saying that the truck had needed a software update which caused the check engine light to come on. So I go to pick it up, start the truck and before I could even pull out of the drive way of the dealer back comes the check engine light. So I turn right around (not very happy at this point) and tell them its back on and that it needs to be fixed. 4 days later they finally figured out what the problem was, apparently the P138B code was a glow plug module fault code, that was caused by the power plug to the glow plug controller not being snapped completely in. Once they got that figured out they found that the P202C code was caused my the Uria (DEF) heater connector also not being plugged in all the way. So 4 days in the shop to find out all my troubles were caused by 2 connectors not being plugged in by the factory when the truck was assembled. Although I am glad it was nothing serious, I hate to see a $60k truck with 500 miles on it giving me problems. The ford technicians don't seem to know what they are doing and had to call some big shots with ford corporation to even figure out what the codes were. Sorry for the long winded answer but maybe this will save somebody some time and headache!
Yea, it is kind of frustrating when errors happen at the factory but I try to keep in mind that these trucks are built by people (and machines). Considering the number of trucks built, welds, electrical connections, vendors, parts, fabrication processes, etc... I am actually suprised that there are not more issues. It frustrated me when I found that the retainer clip on the back seat release handle and rubber bumper under the console lid were not installed but got over it pretty quickly after considering the above.

As frustrating as it is for you I imagine it is also frustrating to FoMoCo because they had to pay the dealership for 4 days of troubleshooting when the problem could have been avoided by the installer spending 5 additional seconds to make sure that the connectors were fully seated. I reserve the right to recant these statements if I start having problems with mine.
__________________
Randy

2011 6.7L XLT CC FX4, 3.55 ELD, 275/65/20. Mods - Infinity 6829 & 6832 speakers, door seal mod, Husky Liners, back up lights, Tonneau Pro Tri-fold cover, Bilstein 5100 shocks, Bilstein Steering Stabilizer,GT Endura seat covers, EZ Down, AMP Power Steps, LED bed lighting and JVC KW-NT810HDT Navigation.
Reply With Quote
  #5  
Old 12-30-2010, 02:19 PM
JerryEdinger JerryEdinger is offline
New User
 
Join Date: Jul 2010
Posts: 6
JerryEdinger is starting off with a positive reputation.
My code was P20C3. It was the same code as the first error. They replaced another part today and so far so good. As far as the build date of ours, it was March 25,2010.. It does have low milage on it and the dealer told us today when we picked it up that the help line had mis-diagnosed the original failure. I am happy with the way the dealer is treating us and hopeully this issue is behind us. They did check all the wiring connectors as well and did not find any issues with any of them... This was a heater sensor that failed.
Reply With Quote
  #6  
Old 12-30-2010, 06:50 PM
gearloose1 gearloose1 is offline
Post Fiend
 
Join Date: Jul 2005
Posts: 6,127
gearloose1 has a good reputation on FTE.gearloose1 has a good reputation on FTE.gearloose1 has a good reputation on FTE.
Couple thoughts:

All of you are early adopters, and you get the bragging rights of the newest stuff in the driveway.

While I do not excuse Ford for not getting it right (e.g. connectors not properly fastened), I have to say, part of the adventure of going first is exactly that.

"You can always tell the pioneers in the business... they are lying face down on the ground with arrows sticking out of their backs".

So please, have a little patience.

We are all here because we support Ford.

Let's kick their posterior if they don't get these same bugs worked out in a few months.
Reply With Quote
  #7  
Old 12-31-2010, 06:20 AM
JerryEdinger JerryEdinger is offline
New User
 
Join Date: Jul 2010
Posts: 6
JerryEdinger is starting off with a positive reputation.
Great Comment and you are right on the money.
Reply With Quote
  #8  
Old 01-22-2011, 11:29 PM
fixdent fixdent is offline
Senior User
 
Join Date: Jul 2010
Location: Northwestern Ontario
Posts: 261
fixdent is gaining momentum as a positive member of FTE.
My "check engine" light came on today, while idling in the driveway. I live 150 miles from my dealer, so can't just drive over to have it checked.

I own an autobody shop, and have seen many vehicles come into the shop with their "check engine" light on. Disconnecting the battery for 10 minutes and reconnecting many times will erase the code which set the light off.

I'm going to try this on mine tomorrow, to see if it goes away. Hopefully it will, and not come back on.

It was -37C this morning (-32F). Truck runs great, starts great.

--
Gordon
Reply With Quote
  #9  
Old 01-22-2011, 11:35 PM
Tom's Avatar
Tom Tom is online now
Moderator
 
Join Date: Aug 2003
Location: Union, CT
Posts: 15,303
Tom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputationTom has a superb reputation
TomB985
Quote:
Originally Posted by fixdent View Post
I'm going to try this on mine tomorrow, to see if it goes away. Hopefully it will, and not come back on.

It was -37C this morning (-32F). Truck runs great, starts great.

--
Gordon
I wouldn't recommend this.

A CEL means something is wrong. The fastest way to get it fixed is to take it in and have them read the code. Clearing it out won't fix the problem.
__________________
Tom,

Currently truckless.
Most recently: 2013 F150 XLT 4x4 EcoBoost
Moderators, Guidelines, and How They are Enforced
Reply With Quote
  #10  
Old 01-22-2011, 11:44 PM
fixdent fixdent is offline
Senior User
 
Join Date: Jul 2010
Location: Northwestern Ontario
Posts: 261
fixdent is gaining momentum as a positive member of FTE.
If there is a reason....it will come back on....

--
Gordon
Reply With Quote
  #11  
Old 01-23-2011, 08:17 AM
sdetweil's Avatar
sdetweil sdetweil is offline
Post Fiend
 
Join Date: Nov 2000
Location: Liberty Hill, tx
Posts: 9,710
sdetweil has much to be proud ofsdetweil has much to be proud ofsdetweil has much to be proud ofsdetweil has much to be proud ofsdetweil has much to be proud ofsdetweil has much to be proud ofsdetweil has much to be proud ofsdetweil has much to be proud ofsdetweil has much to be proud of
see this topic

http://www.ford-trucks.com/forums/10...ml#post9850360

Sam
__________________
Sam

1955 F100 460/c6, 3.55ls - 436 hp, 489 tq
2012 F350 4x4, DRW, 3.73ls, CC, LB, 400 hp, 800 tq
2013 Keystone Alpine 3720FB 5th wheel. 40', 15,500gvwr
Reply With Quote
  #12  
Old 01-23-2011, 10:29 AM
fixdent fixdent is offline
Senior User
 
Join Date: Jul 2010
Location: Northwestern Ontario
Posts: 261
fixdent is gaining momentum as a positive member of FTE.
Thanks for that link.....
Reply With Quote
Old 01-23-2011, 10:29 AM
 
 
 
Reply

Similar Threads
Thread Thread Starter Forum Replies Last Post
High DEF use. kmrgeorge 6.7L Power Stroke Diesel 4 03-14-2013 12:06 AM
2011 F350 DEF System Issues Grassman09 Super Duty & Heavy Duty 0 11-16-2012 01:22 PM
DEF Fill Mistake OffroadSD 6.7L Power Stroke Diesel 4 08-26-2011 02:54 PM
DEF Question Blubeast01 6.7L Power Stroke Diesel 19 11-24-2010 09:42 PM
Motorcraft Diesel Exhaust Fluid (DEF) Parts Guy Wyatt 6.7L Power Stroke Diesel 15 12-24-2009 12:36 AM


Go Back   Ford Truck Enthusiasts Forums > Diesel > 6.7L Power Stroke Diesel

Tags
2011, 67, check, codes, diesel, duty, engine, f250, f350, ford, light, powerstroke, service, super, throwing

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On

Forum Jump


Participate In The Forums

Create new posts and participate in discussions. It's free!

Sign Up »





All times are GMT -5. The time now is 06:13 PM.


Powered by vBulletin® Version 3.8.7 AC1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Advertising - Terms of Use - Privacy Statement - Jobs
This forum is owned and operated by Internet Brands, Inc., a Delaware corporation. It is not authorized or endorsed by the Ford Motor Company and is not affiliated with the Ford Motor Company or its related companies in any way. Ford® is a registered trademark of the Ford Motor Company.

vbulletin Admin Backup