Topic Sponsor
2004 - 2008 Ford F150 General discussion on the 2004 - 2008 Ford F150 truck.

Misfire/Surging Under Load with Cruise On

Thread Tools
 
Search this Thread
 
Old 01-13-2015, 11:38 PM
  #21  
Senior Member
 
lewissa81's Avatar
 
Join Date: Feb 2014
Location: Birmingham, Alabama
Posts: 1,068
Received 97 Likes on 96 Posts

Default

If the Torque app will let you, look at your fuel trims. Specifically long term. If one bank is significantly higher than the other, then focus on that bank.
With 200k miles, your upstream O2 is a good candidate for replacement. It's not that hard to do if you use a wrench instead of an O2 socket.
Old 01-14-2015, 07:19 AM
  #22  
Senior Member
Thread Starter
 
paintballdude05's Avatar
 
Join Date: Aug 2013
Location: Sudbury, Ontario
Posts: 1,244
Received 141 Likes on 135 Posts

Default

Originally Posted by lewissa81
If the Torque app will let you, look at your fuel trims. Specifically long term. If one bank is significantly higher than the other, then focus on that bank.
With 200k miles, your upstream O2 is a good candidate for replacement. It's not that hard to do if you use a wrench instead of an O2 socket.
I'm guessing you need to go after the O2 sensors from under the truck? I think I recall looking at them and checking their connections after the tranny rebuild. I was looking for an obvious source for the truck running like crap at the time.

I'm going to track fuel trims with my laptop on my way home tonight. It's got good graphs for that kind of stuff. Maybe from there I can start replacing pairs on a bank rather than 1 from each.
Old 01-14-2015, 09:35 AM
  #23  
Senior Member
 
wolfy53's Avatar
 
Join Date: Jun 2013
Posts: 639
Received 68 Likes on 58 Posts

Default

Did you ever happen to look at your FPDM? That is free to check it out at least.
Old 01-14-2015, 09:44 AM
  #24  
Senior Member
Thread Starter
 
paintballdude05's Avatar
 
Join Date: Aug 2013
Location: Sudbury, Ontario
Posts: 1,244
Received 141 Likes on 135 Posts

Default

Not yet, I've been working late all week so there's been no daylight to work with. It's also been bitterly cold too (-20*F) which is not fun to work in. I think tonight I'll get suited up (snowsuit) and take a look at the FPDM and the coils to see what up. I've been trying to do as much diagnostic as I can from inside the cab or my deskchair. The cold really sucks to work in.
Old 01-16-2015, 11:15 AM
  #25  
Senior Member
Thread Starter
 
paintballdude05's Avatar
 
Join Date: Aug 2013
Location: Sudbury, Ontario
Posts: 1,244
Received 141 Likes on 135 Posts

Default

It's finally fixed! I think. I bought a new phone (Nexus 5) so I had more time with the Torque Pro, but that isn't what led me to the bad misfiring cylinder. The ECU finally threw a code for a Cylinder #6 misfire. The truck was running really bad on my way into work in the morning so I guess there was finally enough misfires to throw a code. I changed out the coil on #6 and the truck seems to be running really good now. There was nothing physically wrong with the coil, boot or plug. But since the coil was the least well built of the three (eBay Chinese coil) I swapped it out for the spare I had from buying a set for a V10.

Now that the problem is solved, I think I have finally figured out where to get the misfire count for each cylinder. I had to download the TorqueScan add-in, run a PID scan, then I found that the misfire results for each cylinder was found under Test Results. I tried to do this by just monitoring PIDs but I couldn't get results for individual cylinders. All I got was total misfires. I'll keep an eye on it all but I'm happy it's fixed.

Here's the fault codes I pulled right after the CEL came on.

Vehicle VIN: 1FTPW14V18FC2****
Vehicle Manufacturer: Ford
Vehicle Calibration ID: Not present

Current Fault Log
------------------
P0306: Cylinder 6 Misfire Detected

Pending Fault Log
------------------
P0300: Random/Multiple Cylinder Misfire Detected

Historic Fault Log
------------------
ECU reports no historic faults
Other discovered fault codes
(possibly pending, current or manufacturer specific)
----------------------------------------------------
B1602: null
P0316: null
P1000: OBD-II Monitor Testing Incomplete
C1222: null
B1352: null
B1318: null

End of report.



Quick Reply: Misfire/Surging Under Load with Cruise On



All times are GMT -4. The time now is 09:47 PM.