Notices
2004 - 2008 F150 2004, 2005, 2006, 2007 and 2008 Ford F150's with 5.4 V8, 4.6 V8 engine

5.4 randomly misfiring

 
  #46  
Old 07-08-2017, 07:50 PM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.
Mode $06 report generated by Torque for Android
================================================

Vehicle VIN: 1FTPX14V46NB66040
Vehicle Manufacturer: Ford
Vehicle Calibration ID: TEJF5E7.HEX

Test report:
------------------
MID:$01 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 1 Sensor 1
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$01 TID:$80
- O2 Bank 1 Sensor 1
Max: 7.99527V Min: 0.45994V
Test result value: 0.72858V
PASS
----
MID:$01 TID:$81
- O2 Bank 1 Sensor 1
Max: 3A Min: 0.23A
Test result value: 0.484A
PASS
----
MID:$02 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 1 Sensor 2
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$02 TID:$81
- O2 Bank 1 Sensor 2
Max: 3A Min: 0.23A
Test result value: 0.469A
PASS
----
MID:$05 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 2 Sensor 1
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$05 TID:$80
- O2 Bank 2 Sensor 1
Max: 7.99527V Min: 0.45994V
Test result value: 0.74993V
PASS
----
MID:$05 TID:$81
- O2 Bank 2 Sensor 1
Max: 3A Min: 0.23A
Test result value: 0.452A
PASS
----
MID:$06 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 2 Sensor 2
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$06 TID:$81
- O2 Bank 2 Sensor 2
Max: 3A Min: 0.23A
Test result value: 0.456A
PASS
----
MID:$01 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 1 Sensor 1
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$01 TID:$80
- O2 Bank 1 Sensor 1
Max: 7.99527V Min: 0.45994V
Test result value: 0.72858V
PASS
----
MID:$01 TID:$81
- O2 Bank 1 Sensor 1
Max: 3A Min: 0.23A
Test result value: 0.484A
PASS
----
MID:$02 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 1 Sensor 2
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$02 TID:$81
- O2 Bank 1 Sensor 2
Max: 3A Min: 0.23A
Test result value: 0.469A
PASS
----
MID:$05 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 2 Sensor 1
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$05 TID:$80
- O2 Bank 2 Sensor 1
Max: 7.99527V Min: 0.45994V
Test result value: 0.74993V
PASS
----
MID:$05 TID:$81
- O2 Bank 2 Sensor 1
Max: 3A Min: 0.23A
Test result value: 0.452A
PASS
----
MID:$06 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 2 Sensor 2
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$06 TID:$81
- O2 Bank 2 Sensor 2
Max: 3A Min: 0.23A
Test result value: 0.456A
PASS
----
MID:$21 TID:$80
- Catalyst Monitor Bank 1
Max: 0.49999Ratio Min: 0Ratio
Test result value: 0.02344Ratio
PASS
----
MID:$22 TID:$80
- Catalyst Monitor Bank 2
Max: 0.49999Ratio Min: 0Ratio
Test result value: 0.02344Ratio
PASS
----
MID:$3a TID:$80
- EVAP Monitor (cap off)
Test incomplete or dependant test failed
--
MID:$3a TID:$81
- EVAP Monitor (cap off)
Test incomplete or dependant test failed
--
MID:$3a TID:$82
- EVAP Monitor (cap off)
Test incomplete or dependant test failed
--
MID:$3b TID:$80
- EVAP Monitor (0.090")
Test incomplete or dependant test failed
--
MID:$01 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 1 Sensor 1
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$01 TID:$80
- O2 Bank 1 Sensor 1
Max: 7.99527V Min: 0.45994V
Test result value: 0.72858V
PASS
----
MID:$01 TID:$81
- O2 Bank 1 Sensor 1
Max: 3A Min: 0.23A
Test result value: 0.484A
PASS
----
MID:$02 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 1 Sensor 2
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$02 TID:$81
- O2 Bank 1 Sensor 2
Max: 3A Min: 0.23A
Test result value: 0.469A
PASS
----
MID:$05 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 2 Sensor 1
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$05 TID:$80
- O2 Bank 2 Sensor 1
Max: 7.99527V Min: 0.45994V
Test result value: 0.74993V
PASS
----
MID:$05 TID:$81
- O2 Bank 2 Sensor 1
Max: 3A Min: 0.23A
Test result value: 0.452A
PASS
----
MID:$06 TID:$01
Rich to Lean sensor threshold voltage(constant) - O2 Bank 2 Sensor 2
Max: 7.99527V Min: 0V
Test result value: 0.44994V
PASS
----
MID:$06 TID:$81
- O2 Bank 2 Sensor 2
Max: 3A Min: 0.23A
Test result value: 0.456A
PASS
----
MID:$21 TID:$80
- Catalyst Monitor Bank 1
Max: 0.49999Ratio Min: 0Ratio
Test result value: 0.02344Ratio
PASS
----
MID:$22 TID:$80
- Catalyst Monitor Bank 2
Max: 0.49999Ratio Min: 0Ratio
Test result value: 0.02344Ratio
PASS
----
MID:$3a TID:$80
- EVAP Monitor (cap off)
Test incomplete or dependant test failed
--
MID:$3a TID:$81
- EVAP Monitor (cap off)
Test incomplete or dependant test failed
--
MID:$3a TID:$82
- EVAP Monitor (cap off)
Test incomplete or dependant test failed
--
MID:$3b TID:$80
- EVAP Monitor (0.090")
Test incomplete or dependant test failed
--
MID:$a1 TID:$80
- Misfire Monitor General Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a1 TID:$81
- Misfire Monitor General Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a1 TID:$82
- Misfire Monitor General Data
Max: 24.49993% Min: 0%
Test result value: 5.20976%
PASS
----
MID:$a1 TID:$83
- Misfire Monitor General Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a1 TID:$84
- Misfire Monitor General Data
Max: 966.60004C Min: 0C
Test result value: 494.60001C
PASS
----
MID:$a2 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 1 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a2 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 1 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a2 TID:$80
- Misfire Cylinder 1 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a2 TID:$81
- Misfire Cylinder 1 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a3 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 2 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a3 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 2 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a3 TID:$80
- Misfire Cylinder 2 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a3 TID:$81
- Misfire Cylinder 2 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a4 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 3 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a4 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 3 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a4 TID:$80
- Misfire Cylinder 3 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a4 TID:$81
- Misfire Cylinder 3 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a5 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 4 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a5 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 4 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a5 TID:$80
- Misfire Cylinder 4 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a5 TID:$81
- Misfire Cylinder 4 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a6 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 5 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a6 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 5 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a6 TID:$80
- Misfire Cylinder 5 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a6 TID:$81
- Misfire Cylinder 5 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a7 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 6 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a7 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 6 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a7 TID:$80
- Misfire Cylinder 6 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a7 TID:$81
- Misfire Cylinder 6 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a8 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 7 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a8 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 7 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a8 TID:$80
- Misfire Cylinder 7 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a8 TID:$81
- Misfire Cylinder 7 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----
MID:$a9 TID:$0b
EWMA Misfire counts (average) for last 10 drive cycles - Misfire Cylinder 8 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a9 TID:$0c
Misfire counts for last/current driving cycles(calculated) - Misfire Cylinder 8 Data
Max: 65,535 Min: 0
Test result value: 0
PASS
----
MID:$a9 TID:$80
- Misfire Cylinder 8 Data
Max: 24.49993% Min: 0%
Test result value: 0%
PASS
----
MID:$a9 TID:$81
- Misfire Cylinder 8 Data
Max: 0.99953% Min: 0%
Test result value: 0%
PASS
----


End of report.
 
  #47  
Old 07-08-2017, 10:57 PM
F150Torqued's Avatar
F150Torqued
F150Torqued is online now
Elder User
Join Date: Jan 2015
Location: San Antonio, Texas
Posts: 828
F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.
Looks to me like you have NOTHING to worry about - that's one fine running truck.


Lot of guys stress out over Mode 06 test results, and they DO look like a bunch of mumbo jumbo with the Hex numbers represented by the dollar sign. Reading their meanings in the Motorcraft OBDII Theory of Operation Manual is enlightening.


But the main thing we see in yours is the Test Results is ZERO misfire counts in the last 10 driving cycles - and the percentage of misfires is ZERO %, nowhere near the Maximum thresholds used in PCM in its "Exponentially Weighted Moving Average" for throwing a code or Flashing the CEL - on ANY one of the 8 cylinders.


You probably have cleared Codes recently (since its so easy with Torque), and that cancels and restarts the EVAP monitor. The conditions for it running are so stringent it can take days - or - weeks and miles for it to complete.


Looks like you're good to go.
 
  #48  
Old 07-09-2017, 12:24 AM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.
Thanks for reviewing the data... Good to hear you think it looks ok, I thought so too. I will stop stressing about it. And I'll change the spark plugs more often - no anti seize next time! I'll also plan on de-carboning using your method with the drill/hanger/soaked rag. The 5.4 gets a lot of bad press, but there are many of them out there performing very well.

Thanks for sharing your wisdom and experience!

Joe
 
  #49  
Old 07-10-2017, 08:25 PM
waldreps
waldreps is offline
Senior User
Join Date: Dec 2001
Location: MN
Posts: 220
waldreps is starting off with a positive reputation.
Originally Posted by F150Torqued View Post
@Datslab


The OBDII system maintains a counter that counts the number of drive cycles and is cleared when DTC's are cleared AND by any misfire occurring after the first 200 engine revolutions (PID 16DC, MFF_0_CNT). I monitor it with Torque Pro. With 225,000 miles on my 2004 now, this counter frequently gets up to 50 to 75 run cycles on my truck without a single misfire..
I want to monitor this in my Torque Pro app but I can't find it anywhere in the list. Am I missing some PIDs or is it custom? Can you give me the parameters for it so I can program it into mine? Thanks.
 
  #50  
Old 07-11-2017, 01:04 PM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.
Originally Posted by waldreps View Post
I want to monitor this in my Torque Pro app but I can't find it anywhere in the list. Am I missing some PIDs or is it custom? Can you give me the parameters for it so I can program it into mine? Thanks.
There are two places to look in Torque Pro - you can see Total Misfires in Realtime Information:



This is a total of all 8 cylinders, but doesn't give you specifics. You can see the Mode $06 data in Test Results:



From the main screen in Torque, select Test Results... it will start scanning and eventually display all the Mode $06 data on the screen. This will include data on each cylinder. You can send the data to your email address by clicking on the three dots in the upper right corner, then SEND. The data gets imbedded into the email. Give it time to scan and populate all the data, they continue to appear as it scans.

Freeze Frame data is only available if you throw a code, from the main screen under Fault Codes.

Hope this helps... I'm not a super-experienced Torque user.
 
  #51  
Old 07-11-2017, 01:23 PM
waldreps
waldreps is offline
Senior User
Join Date: Dec 2001
Location: MN
Posts: 220
waldreps is starting off with a positive reputation.
Thanks, jwiegele but I want to use the specific PID that F150Torqued mentioned that counts the number of driving cycles without a misfire. I'm already using the total number of misfires PID but it resets with each startup and also includes those below 1000 rpms.
 
  #52  
Old 07-11-2017, 04:32 PM
F150Torqued's Avatar
F150Torqued
F150Torqued is online now
Elder User
Join Date: Jan 2015
Location: San Antonio, Texas
Posts: 828
F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.
@waldreps - stand by. I'm putting together a list of a whole bunch of non-standard custom PIDs relating to 'MISFIRES" that can be added to your Torque Pro extended PIDs/Gauges and a CSV file that can be "Imported" directly into your Torque Pro directory. I'll post it here soon as done.
 
  #53  
Old 07-12-2017, 12:32 AM
F150Torqued's Avatar
F150Torqued
F150Torqued is online now
Elder User
Join Date: Jan 2015
Location: San Antonio, Texas
Posts: 828
F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.
Torque Pro MISFIRE MONITOR dashboard screen


Torque Pro Misfire Monitor dashboard screen


Ok, here's the deal. For all those Torque Pro users out there - WITH MISFIRE TROUBLES:


UNFORTUNATELY, Vehicle manufacturers (including Ford) has quiet intentionally made it difficult for the Scanner manufacturers (AND US) to figure out the proprietary information available to there service techs and for making money selling their Integrated Diagnostics System (IDS). Every ounce of information beyond the most elementary stuff is very difficult to get - and lots of information out there is 'BOGUS', or just plain wrong, and has to be researched, double checked and cross checked.


In my view - this is what is so 'ingenious' about Torque Pro. If you can 'scan' your PCM's OBDII link or 'hack' your OBDII system and find a PID, if the PCM will respond to it, you can add the PID to Torque Pro, work out a meaningful formula, and build any type gauge you like to display the information. Torque Pro even allows "IMPORTING" additional custom PIDs via a CSV (comma separated value) flat file which allows users to 'share' them to enhance the usefulness of Torque. /// I am attaching a CSV file to this post that contains all the gauge definitions for this dashboard that are NOT in the standard Torque Pro extended PID list for Ford. Copy the attached 'CSV' file to the .Torque/ExtendedPids folder on your Android device. Then from the Manage Extended gauges/PIDs menu > Import and select file "Torque Misfire Monitor v1-02.csv" file. ///


I have located and tested some interesting stuff about 'Misfires' and worked out formulas on my 2004 5.4L Lariat. They should work on most 2004 - 2008 models w/ 5.4s - but I know different vehicles - even within the Ford lineup (?? 4.6 ??) have PID assignments that are not uniform. This is, to some degree, due to obvious differences. (Ie: you will note the one EGR gauge here does not work --- Because the 5.4L Triton does NOT have one but instead accomplishes EGR via the variable valve timing system).


--------------------



This is not intended to take anything away from the MODE 06 Report - but rather augment it with a simple, quick, real time monitoring screen for an instant snapshot of misfire health, or non-health as the case may be.


The above Torque Pro dashboard is created using the following 'described' PIDs and Formulas that are NOT in the standard set. You should already have the FORD Custom PID's installed. A couple on my screen are from that standard FORD extended PIDs. (Note: All use Header of "Auto", Start Diagnostic Command of 'blank', Stop Diagnostic Command of 'blank'. NOTE ALSO: I recommend placing an underscore character "_" in front of MY custom PIDs to make them sort to the front of the Torque PID list.]

Torque PIDs for above dashboard are::::
============
Distance Traveled Since MIL cleared (MIL Off) is from the standard FORD Extended PID list. (Note: this PID does not work on my vehicle, but MAY on some other models. (This highlights the difficulty in this area. OBDII PID assignments are NOT uniform - even within a given manufacturers lineup, and especially across different vehicles.


============
Distance Traveled with MIL lit (MIL On) is from the standard FORD Extended PID list. (Works on the '04-'08 5.4L)

============
MISFIRE OCCURING button gauge. This "FLAG" is set if vehicle exceeds factory set limit of misfires during any 200 revolutions (including the first 1000 revolutions) or in any four 1000 rev blocks during the drive cycle. [Based on the Motorcraft OBDII theory manual. I have never witnessed this indication on my truck, but it is documented pretty good. However, I just don't have misfire troubles with my truck]

Mode/PID: 221102
Long Name: _Misfire Occurring Flag
Short Name: MISFIRE
Min/Max: 0, 1
Unit Yes/No
Formula: {A:7}

=======
Continuous Code Counter of total number of codes recorded (both fault & pending)


Mode/PID: 220200
Long Name: _Continuous Code Counter
Short Name: DTC Count
Min/Max: 0, 255
Unit: Cnt
Formula: A

=======
Total number of On-Demand Codes. It is 'my understanding' from documentation, research and testing that this parameter is a count of 'pending' codes which have to occur some multiple of times in order to set a hard DTC (fault). (Through testing I have not witnessed any such codes on my truck - feedback welcomed)

Mode/PID: 220202
Long Name: _Total Number of On-Demand Codes
Short Name: DTC_CNTD
Min/Max: 0, 255
Unit: Cnt
Formula: A

========
Total number of OBDII "TRIPS" completed. An OBDII Trip requires a number of events to occur - and generally requires lots of 'drive cycles' or 'run cycles'. To qualify as a "TRIP" the vehicle has to complete several accelerations up to freeway speed (50mph +), several decelerations from 60 to 40, completed EVAP tests (several things hold up evaporative emissions tests), Catalyst monitor tests and a 'bunch' of other stuff. TRIPS do NOT clock up very rapidly - and are cleared when the MIL is reset and DTCs are cleared - thus a good indication how LONG /many miles since MIL has been cleared. (For reference: I make 1 to 3 trips EVERY week commuting to and from a weekend lakehouse - and notice nearly 1500 drive cycles to clock 25 OBDII "Trips")


Mode/PID: 220100
Long Name: _Number of OBDII Trips completed
Short Name: TRIPCNT
Min/Max: 0, 255
Unit: Cnt
Formula: A ///--- I notice I should have set the number of 'decimal places' on this gauge to Zero ---///



==========
Total number of
"_Number of OBDII drive cycles - since codes have been cleared.


Mode/PID: 220101
Long Name: _Number of OB DII Drive Cycles completed"
Short Name: DRIVECT
Min/Max 0, 65535
Unit: Cnt
Formula: A*256+B



==========
Total number of Misfires during the curent drive cycle. This PID is included in the FORD extended PID list (which must be installed in Torque Pro to appear in the PID list) and be added to this dashboard. A gauge can be added for it by selecting it from the standard PID list. (NOTE: This count is RESET each 'run cycle'. Turn the key off and back and make the vehicle roll, and this counter will be zeroed. ALSO, it DOES Include misfires occurring during the 1st 1000 engine Revs.)


===========
Total number of "Drive Cycles" - SINCE the last (_post 1000 rev) Misfire or DTC clear occurred. (This Counter increments ONCE - for each Drive Cycle or 'run cycle' and is RESET when DTC's are cleared _AND_ when a (Post 1000 revolution) Misfire is detected. Misfires during the first 1000 Revs do NOT reset this counter.


Mode/PID: 2216DC
Long Name: _Number Drive cycles Since DTC CLR or MISFIRE
Short Name: MFF_0_CNT
Min/Max: 0, 65535
Unit: Cnt
Formula: A*256+B



============
The Misfire Monitor Wheel Profile Learned flag is set in KAM after the Misfire monitor has completed the correction profile of irregularities in CKS tone ring (ref: Motorcraft OBDII Theory of Operation manual). Misfires are detected by the very slight deceleration in crankshaft rotational speed and the tone ring wheel on the front of crankshaft provides the input for misfire monitoring. This correction 'profile' is re-learned and perfected at the beginning of each run cycle.


Mode/Pid: 2216DD

Long Name: _Misfire Monitor Profile Learned in KAM
Short Name: MFMLRN
Min/Max: 0, 1
Unit: Yes/No
Formula: {A:0}



==========
The Misfire Monitor completed this Drive Cycle. This is an element of comprehensive continuous OBDII Monitors ( It is 'dependant' upon MFMLRN, and must be completed in order for certain other Monitors -ie: specifically the Catalyst Monitor - to run)


Mode/PID: 22095D
Long Name: _Misfire Monitor Status
Short Name: MISSTAT
Min/Max: 0, 1
Unit: Yes/No
Formula {A:7}




==========
Fuel Status Monitor completed this Drive Cycle - an element of comprehensive continuous OBDII Monitors


Mode/PID: 22095D
Long Name: _Fuel Status Monitor
Short Name: FUELSTAT
Min/Max: 0, 1
Unit: Yes/No
Formula: {A:4}



==========
Fuel Injection Control Module signal for Cam-Crank in Sync


Mode/PID: 2209CD
Long Name: _FICM Signal for Cam-Crank in Sync
Short Name: FICMSYNC
Min/Max: 0, 1
Unit: Yes/No
Formula: {A:0}



===========
In Drive at time of misfire Flag (Captured at instant of misfire for Freeze frame data)


Mode/Pid: 2216DD
Long Name: _In Drive at time of Misfire
short Name; MFF_PNP
Min/Max: 0, 1
Unit: Yes/No
Formula: {A:1}



=============
Engine RPM at time of lastest Misfire. (This stastistic is captured & saved for Freeze Frame Data)


Mode/PID 2216D3
Long Name: _Engine RPM at time of Misfire
Short Name: MFF_RPM
Min/Max: 0, 6500
Unit: RPM
Formula (A*256+B)/10




=============
Engine Load at time of latest Misfire. (Captured for Freeze Frame Data)


Mode/PID 2216D4
Long Name: _Engine Load at time of Misfire
Short Name: MFF_LOAD
Min/Max: 0, 100
Unit: %
Formula (A*256+B)*(128/32768)




===============
Vehicle Speed at time of Misfire. (Captured for Freeze Frame Data)


Mode/PID: 2216D5
Long Name: _Vehicle Speed at time of Misfire
Short Name: MFF_VS
Min/Max: 0, 120
Unit: MPH
Formua: A



==============
Intake Air Temp at time of Misfire. (Captured for Freeze Frame Data)


Mode/PID: 2216D6
Long Name: _Intake Air Temp at time of Misfire
Short Name: MFF_IAT
Min/Max: 0, 200
Unit: Deg. F.
Formula: (A*9/5)+32



===============
Engine-Off SOAK at time of Misfire. (Captured for Freeze Frame Data)


Mode/PID: 2216D7
Long Name: _Engine-Off SOAK time at time of Misfire
Short Name: MFF_SOAK
Min/Max: 0, 65535
Unit: Minutes
Formula: (A*256+B)



==================
Engine Run time at time of Misfire. (Captured for Freeze Frame Data)


Mode/PID: 2216D8
Long Name: _Engine Run Time at time of Misfire
Short Name: MFF_RNTM
Min/Max: 0, 255
Unit: Secs
Formula: A



===================
Throttle Position at time of Misfire. (Captured for Freeze Frame Data)


Mode/PID: 2216DA
Long Name: _Throttle Position at time of Misfire
Short Name: MFF_TP
Min/Max: 0, 5
Unit: Volts
Formula: ((A*256+B)/32767)*5




==================
Exhaust Gas Recirculating valve (EGR or DFPE) commanded at time of Misfire (Captured for Freeze Frame Data).


Mode/PID: 2216D9
Long Name: _EGR-DFPE sensor at time of misfire
Short Name: MFF_EGR
Min/Max: 0, 5
Unit: Volts
Formula: ((A*256)+B)/32767)*5





///// Sorry for the long post. But hope it helps some of my fellow forum members deal with misfires.


Happy Torqueing




------------------------------- EDIT:


Added FUELSTAT PID parameters to CSV file (v1-03) that I had left out.
 
Attached Files
  #54  
Old 07-12-2017, 10:36 AM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.
F150Torqued, this is awesome! thank you for the detailed explanation, and the .csv file! I have it set up now in my app, and even though my 2006 truck seems to be behaving now, this is excellent information to monitor and keep track of. Well done sir! And thank you for sharing this, I can see you put a tremendous amount of effort into this. Knowledge is power!

Thanks again!
Joe
 
  #55  
Old 07-12-2017, 11:20 AM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.
F150Torqued... the only one I couldn't find in your .csv file was:

==========
Fuel Status Monitor completed this Drive Cycle - an element of comprehensive continuous OBDII Monitors


Mode/PID: 22095D
Long Name: _Fuel Status Monitor
Short Name: FUELSTAT
Min/Max: 0, 1
Unit: Yes/No
Formula: {A:4}

Doesn't look like it was mis-named or anything, it's just not there. I couldn't find anything similar in the Ford specific PID's either. Not a big deal - I set up my screen exactly the way you have yours, I like the way you grouped everything. Once again, this is great info for anyone dealing with misfire issues!

Thanks!
Joe

[edit] I tried my hand at creating the FUELSTAT myself, thanks to your showing the parameters, and I think I got it right...
 
  #56  
Old 07-12-2017, 12:11 PM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.


Fantastic!
 
  #57  
Old 07-12-2017, 12:20 PM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.


 
  #58  
Old 07-12-2017, 01:52 PM
F150Torqued's Avatar
F150Torqued
F150Torqued is online now
Elder User
Join Date: Jan 2015
Location: San Antonio, Texas
Posts: 828
F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.F150Torqued has a very good reputation on FTE.
@jwiegele
Thank you for your reply and pointing out the missing parameter in the CSV file. I have corrected that and edited the post uploading a v1-03 including it. THANKS for the FEEDBACK.


You are a "MASTER" Torque Pro user now - once you start 'plugging' in your own PIDs (and realize you won't KILL your PCM), you immediately become dangerous. Do not be afraid to spelunk and you can figure lots of stuff out by fiddling with the formulas and use the 'live' Test button at the bottom of the PID Edit screen.

>>> ONE COMMENT <<< In your screenshot above, the Equation is entered incorrectly and will produce incorrect results as Torque Pro's equation parser will fail. To sample a single 'bit' within an OBDII response 'byte' - in this case bit number 4 counting from the right as bit Zero, you MUST USE braces, NOT brackets.

Change those enclosing symbols to {A:4} and Torque will return a Zero if the bit is Off, a One if the bit is On. Brackets "[" are used to insert the results of another PID into an Equation. ie: as a ridiculous example, you can divide something by vehicle speed using xxxxx/[000D]. The latter being the PID for vehicle speed.




And BTW. I very happy to notice that Miles Driven with MIL Off is working on your vehicle. That makes the screen even more useful --- but 'pisses me off' how OBDII is supposed to be a standard, and that PID does NOT respond on my truck - almost the identical year and model. You can't imagine how much time I spent on that PID trying to figure out if I was doing something wrong!!!
 
  #59  
Old 07-12-2017, 02:08 PM
jwiegele
jwiegele is offline
New User
Join Date: Feb 2007
Posts: 23
jwiegele is starting off with a positive reputation.
F150Torqued
thanks for looking at my manually entered FUELSTAT equation, I didn't think I had it right. It's been corrected now! I've learned a lot just from your posts, so thanks again! The reason I thought it was wrong was that the entry didn't turn GREEN in the list, it remained BLUE. So glad you caught that...

I would be pissed off too, after counting on a standard OBDII and realizing (after all that time spent troubleshooting) that Miles Driven with MIL Off was not responding on your truck. One thing I did do about 3 years ago (maybe 2014), is took my truck in to my Ford dealer (Fitzpatrick Ford in Newnan, GA) as asked them to flash my PCM with the most recent version they had. They are great there at Fitzpatrick Ford, and although I try to do everything myself, I will take it there for just a few things. Maybe that's why it works for my 2006?

Thank you sir!
Joe
 
  #60  
Old 07-14-2017, 01:14 PM
waldreps
waldreps is offline
Senior User
Join Date: Dec 2001
Location: MN
Posts: 220
waldreps is starting off with a positive reputation.
Thanks for the info F150Torqued
 

Thread Tools
Search this Thread
Quick Reply: 5.4 randomly misfiring


Contact Us - About Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

© 2019 MH Sub I, LLC dba Internet Brands

We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.