Notices
6.2L V8 Discuss the 6.2L V8

ECU freaked out; one code remaining - P260F

Thread Tools
 
Search this Thread
 
Old Jul 27, 2018 | 07:27 PM
  #1  
memilanuk's Avatar
memilanuk
Thread Starter
|
Cross-Country
5 Year Member
Liked
Loved
Community Favorite
Joined: May 2018
Posts: 89
Likes: 46
From: Central Washington state
ECU freaked out; one code remaining - P260F

Had the truck (2012 F250 CCSB 4x4 XL/FX4 6.2L gas w/ 3.73 gears) out on the return leg of a 3500 mile two-week road trip, towing a 31 ft bumper pull TT. Overall the truck pulled and handled great, with one exception. Stopped briefly for a few hours to have lunch with a relative; the truck sat for maybe 2-3 hrs with an ambient temp of ~95F. Got hot enough inside the cab to over heat and shut off the tablet I use for GPS/navigation and to run Torque (an OBDII dashboard app). When I turned the truck on, pretty much every alarm light came on, and a litany of error messages scrolled thru the DIC. As I was pretty close to being in the middle of nowhere, and everything seemed to be running fine despite the errors, I got out of the drive way and down the road a bit before I turned it off and restarted. Everything but the check engine light cleared, and a scan for errors/faults with the OBDII app) showed only one remaining - P260F.

A little reading through the owner's manual seemed to indicate that the check engine light would either clear over the next few start/run cycles, or it wouldn't. Looking up the code on the interweb didn't reveal anything that was either too scary - or very helpful in the immediate sense. Drove to the next scheduled gas stop, and when I turned the engine back on after fueling, the check engine light was clear. But the error code still shows when I run a scan using the OBDII app.

If there isn't any easy way to clear/reset that error, I'll definitely take it in to the local Ford shop now that I'm back home. But I am kind of wondering just WTF happened, what made the dash go berserk like that, and what the long-term implications are? Anybody here have an educated guess?
 
Reply
Old Jul 27, 2018 | 07:55 PM
  #2  
Chuck's First Ford's Avatar
Chuck's First Ford
Postmaster
Joined: Jul 2015
Posts: 4,392
Likes: 22
From: very South Texas
was the tablet connected to the OBDII connector ??? while you went to lunch ...

remember the OBDII is a 2 way street.... hand shaking, protocols.. procedures.
 
Reply
Old Jul 28, 2018 | 02:39 AM
  #3  
memilanuk's Avatar
memilanuk
Thread Starter
|
Cross-Country
5 Year Member
Liked
Loved
Community Favorite
Joined: May 2018
Posts: 89
Likes: 46
From: Central Washington state
Originally Posted by Chuck's First Ford
was the tablet connected to the OBDII connector ??? while you went to lunch ...
Yes, it was. That crossed my mind initially when everything 'blew up'... but with the one code still in and not clearing I'm less certain that the app on my tablet could have caused a fault on the ECU....
 
Reply
Old Jul 28, 2018 | 07:18 AM
  #4  
rvpuller's Avatar
rvpuller
Moderator
Veteran: Coast Guard
20 Year Member
Photogenic
Photoriffic
Joined: May 2004
Posts: 6,517
Likes: 917
From: Home Base Nebraska
Club FTE Gold Member
That code is for the emisions vapor canistor, no big deal because it will clear itself. It may have been going through a gas tank vacuum test when you shut the hot truck off, it thinks the gas cap was not tight. I wouldn't leave my laptop live and hooked to the port when the truck is shut down because the Torque app could be running all kinds of test and messing with the computer in the truck.
Denny
 
Reply
Old Jul 28, 2018 | 09:24 AM
  #5  
memilanuk's Avatar
memilanuk
Thread Starter
|
Cross-Country
5 Year Member
Liked
Loved
Community Favorite
Joined: May 2018
Posts: 89
Likes: 46
From: Central Washington state
Originally Posted by rvpuller
That code is for the emisions vapor canistor, no big deal because it will clear itself. It may have been going through a gas tank vacuum test when you shut the hot truck off, it thinks the gas cap was not tight
We had just filled up about 15 minutes before the truck had been parked, so there's always the possibility that the cap *wasn't* tight. I definitely checked it thereafter, though

How long should it take to clear? It's been a couple days... numerous fill-up... over a thousand miles
 
Reply
Old Jul 28, 2018 | 10:25 AM
  #6  
krewat's Avatar
krewat
FTE Leadership Emeritus
Joined: Jul 2002
Posts: 42,561
Likes: 423
From: Long Island USA
Club FTE Gold Member
Clear it with Torque. Then monitor it for a bit. The high ambient heat, the laptop/tablet draining the battery, the fact that it was connected to the OBD-II port at the time, who knows. It's best to clear the code, which will probably clear the KAM (Keep Alive Memory), and the PCM will relearn.

Let us know what happens
 
Reply
Old Jul 28, 2018 | 02:26 PM
  #7  
Chuck's First Ford's Avatar
Chuck's First Ford
Postmaster
Joined: Jul 2015
Posts: 4,392
Likes: 22
From: very South Texas
I guess I did not make myself clear..

it is possible .. the tablet... went nuts from the heat.. and put out data garage into truck computer...
as the old saying is'""""""" trash in,,, you get trash out.......

reset your truck computer... even disconnect truck battery for a few minutes... your call
 
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
cdestuck
2004 - 2008 F150
3
Jan 2, 2014 11:25 AM
redbull660
Modular V10 (6.8l)
6
Nov 26, 2012 08:03 PM
Stroked99
1997 - 2006 Expedition & Navigator
3
Dec 1, 2008 02:27 PM
misspolly1969
Explorer, Sport Trac, Mountaineer & Aviator
2
Sep 28, 2004 09:27 AM
Albie
Explorer, Sport Trac, Mountaineer & Aviator
17
Nov 14, 2001 02:35 PM




All times are GMT -5. The time now is 03:07 PM.