We have a misfiring 2000 Ford F250, under 30,000 miles, with the 5.4 liter gas V8. I had a new fuel pump and filter and fresh gas. Now that the truck runs again we have misfires under load. (It had a totally dead fuel pump.) Flat roads and idle are fine, but climbing hills or accelerating to pass are an issue. There is no Check Engine Light and are no P codes.

I have the BAFX OBD2 blue tooth interface which had successfully worked with Torque Lite for a couple of years, but because I needed the mode 6 data I just upgraded to Torque Pro. I can successfully connect to the BAFX interface with Torque Pro version 1.8.158.

I think I have enabled the “Ford (Incl PowerStroke)” predefined set if PIDs. When I connect to the truck I cannot see the results of the scan for misfire.

So, what am I doing wrong?

Thanks in advance for any help you can give,

steven1955

The Ford custom pids for misfire are not returning data, but the 8 “lines” for that data is showing up in a grey color.

Some of the Ford custom pid data is being reported, and those “lines” are green in color, but I cannot remember what that data was reporting.

The battery was disconnected overnight in the truck before I attempted to read the mode 6 data.

Could the data being unavailable have something to do with not having enough drive cycles since the battery disconnect?

We are now driving the truck, which runs well when cold, but misfires when warmed up or when the COPs are heat soaked. Misfires occur under load (hills or even mild acceleration) , but can be reduced or eliminated by downshifting and/or stomping on the gas.

We may end up replacing all of the COPs and maybe spark plugs if I can’t get mode 6 data to confirm the problem is in only one or just a few cylinders.