Yesterday my truck developed a misfire, started from cold, cel is on so I checked for codes.
TP showed no codes, Forscan showed ICP low or high (can't remember the exact code).
Drove for around 3-4 miles & cel goes out & misfire is gone. After work it was the same again, misfire until reaching operating temperature then absolutely fine. I did a buzz test this morning & it showed number 2 to be weak.
I don't have my automotive tools with me so can't start pulling stuff apart until I get home next week, then I've got a whole bunch of stuff to do, I've just had all my stuff arrived from Riffraff to go through the top end, up pipes, turbo rebuild, o-rings for everything, UVCH & gaskets & replacing all CAC boots, so I should have everything covered.......
Any suggestions as to the misfire welcome, I'm a long way from home & have my toy hauler/work trailer to haul home in a couple of days.

 

Cold issues like that can be caused by worn injector poppets. After they warm up and expand a little the problem goes away. But they are usually a symptom of high(er) mileage and I believe that you have a low mileage truck. If you're popping the VC's check your poppet clearances. I do not know how that's done but others do and once you're in there I don't think it's hard to do.

 

Thanks, yes the truck is still relatively low mileage (around 75k miles) so it should be unlikely....but you never know!
My first thought was injector harness due to age, but then when it picked up & cleared it kinda threw that thought out....
My main concern is getting it home, but I guess if it's running fine, that shouldn't be an issue. The egt's are low until it clears but I'm guessing with one out of four cylinders just pumping air on the side where the probe is, that would explain that.

 

This thread suggests oil additives short term, to clean things up, or 5W-40 synthetic, as options. Good plan to change out the UVCH/gaskets. You have a unique situation with those low miles.

https://www.ford-trucks.com/forums/1...-help-plz.html

How does the fuel pressure look?

If you can log your cold start/miss on Forscan and post the CSV file, we'll take a look. It would be helpful to know that code as well.

 

The truck has been running on 5W-40 since I got it at 19k Km's, I'll be doing the UVCH & gaskets anyway.
Here's a couple of screenshots from TP, first one is at idle.



Below is 2000rpm in neutral



Screen shot of Forscan, mmm, different to last time....



Don't know if I can do csv file from my phone, don't have a laptop with me

 

To save that CSV file from your phone, you can email the file to yourself.

After stopping the log, either by hitting the stop box at the top of the screen, or by shutting down the truck, tap the 3 vertical dots at top right:



Tap "Save", and you'll get this screen:


Tap "Send CSV", and it will prompt you for your email. This is how I save logs - you can then get them whereever you are later, and bring them up on your laptop.

Tap "Save CSV" to put a copy of the log on your phone. You can upload it to the forum from your phone that way if you want.

Finally, tap "Save" if you want to save the log in Forscan format for later viewing in the Forscan app.

 

Thanks, I've not used Forscan for logging, haven't needed too up 'till now lol! I'll try to get my head around it tomorrow if I get time. What pid's should I use?

 

P1316 might be pointing to your wiring/harnesses/solenoid after all for #2. Now that you have P1316, running the buzz test again should provide a code that will point to the offending injector - probably #2 again.

In Forscan Lite, run KOEO on demand self test (buzz test) to retrieve those codes. I have not had consistent luck getting TP to report codes for some reason.

The data in your screen shots look normal to me. Pretty cold where you are today, though.

For PIDs, use the ones listed in the charts below. Go ahead and put all of them in. Might as well have too much data than not enough, and it does not slow down the logging, just the display.

Skip ECT if you have an auto transmission. Skip TFT and TC_SLIPACT if you have a ZF6.




Unfortunately, Forscan sometimes lists 2 PIDs with the same name, but only one of them works. You can pick both of them, and then start logging in the Graph view to see if the data is smooth. It will be spiky if the PID is not right, and you can remove that one.

Here's some screenshots of the PIDs I picked that work when there are 2 listed:

 

Thanks again, I've got to try to get a job finished tomorrow so if I get time before it gets too late, I know what I'll be doing. Temperature was around 60°f at the time I took the screen shots. It took a little longer for the misfire to go tonight too......

 

One more thing - set up Forscan Lite for comma delimited CSV files - they paste into Excel easier. Forscan defaults to semicolon delimited CSV files. Not sure why.

In the home screen, tap Settings:



Then tap "CSV delimiter"



Tap the Comma radio button.

 

Why does ForScan have two identical options for some of the PID's? And how do you know which one to pick?

 

I wish I knew, Mark. Maybe we'll learn some trucks work with one PID as opposed to the other as we go along. I need to start posting questions like this on the Forscan forum.

The way to pick the right PID when two are identically named, is to pick both of them, tap the graph view in Forscan Lite, or the Oscilloscope view in Forscan, and tap the play button to start graphing/logging. You will see both PIDs plotted. One will be a smooth trace, and the other will jump around. Remove the jumpy one from your selected PID list and you're all set. Forscan will remember the PIDS you selected, so you don't have to pick them each time you open the app.

To be safe, you can save your PID profile, so you can recall the list that works for your truck if it gets messed up, or if Forscan.org pushes out an update and resets your app.

Here is an example with the EOT PID. 2 PIDs are available, and I did not know which one to pick until I charted them.


The green EOT trace is spikiing and not very useable. The blue EOT trace is smooth and easy to read. That's the one we pick. Thankfully, you only have to do this once. Once we get Forscan/Forscan Lite set up to read the typical PIDs for your truck, all you will have to do is start the app, hit play and you're logging.

 

Latest update, the truck got me home, just over 300 miles pulling my loaded toy hauler & it didn't miss a beat once warmed up.......
Next morning started rough, warmed up & ran OK. Left it running while uncoupling the trailer & sorting stuff out & the misfire returned........first time it's done this.
Today is the day I start throwing all the new parts at it, I've set up Forscan graphs for all the PIDs as per above & set the CSV file format, took the truck for a short drive with logging running & sent the file to my email. This is it....

LiveData_2020-09-09_09.01.22.xlsx

If it hasn't worked or isn't quite how it should be let me know if I can do better, I has to put all the pids on one file as I couldn't see how to save separate charts...
Now to start getting dirty!

Edit, also ran a buzz test again, 2 & 4 are bad, thinking UVCH..



Quick update, pulled driver side VC & the UVCH was barely touching the connector..........to the point that I'm surprised it ran at all, pushed it back in & laid the VC in place before cranking up the motor & it's as sweet as ever. Fair bit of play back & forth on the turbo impeller so time to get back under the hood.

 

Alright - you got it fixed! Didn't need the graphing of PIDs for this one, since you have the P1272 and P1274 codes.

You did the PID file correctly. It's comma separated, and has all the PIDs in one file, ready to paste into the PID charting tool. I see about 11 minutes of data here.

If you want, you can change MAP.OBDII (psi) to MAP(psi), so it populates in the charting tool automatically, but this is a case where both PIDs give good data.

You have two VPWR(V) PIDs in the file, so you can delete one of them in your PID list.

Nice work. Was the truck missing during your drive? I think I can see one spot below. I'm still learning what electrical issues look like on these charts - RPM, MFDES and FUELPW fluctuations, with IPR and ICP steady, are a clue.

 

@BWST I added several versions of the same PIDs, as per your suggestion, I thought I had deleted all the unreadable or unnecessary duplicate ones, must have missed that one.
The graph was a nearly cold start (had to run the truck a few times while setting up the pids) then a short drive around the block which was a couple of miles in heavy traffic, the truck was running worse than before & missed constantly. Which was hardly surprising given how the UVCH was barely resting against the connector.
I could have probably got away with the 50c mod but as I've got all the stuff, it would be silly not to fit it now. I now have the injectors out, the up pipes & turbo out, tomorrow is clean, rebuild and refit. I didn't think I had any leaks, but there's a little bit of soot around the old pipes, I cut them off & they were loose too. I used to wrench for a living (30 years ago though) so it's all basic stuff, just a bit fiddly getting to some of the fasteners.....