*** Restricting New Posts to SD Premium Members ONLY *** (09 May 2025)

Just made a new account? Can't post? Click above.

Help us help you. By posting the year, make, model and engine near the beginning of your help request, followed by the symptoms (no start, high idle, misfire etc.) Along with any prevalent Diagnostic Trouble Codes, aka DTCs, other forum members will be able to help you get to a solution more quickly and easily!

Scan Tool Stopped reading Mode 6 misfire data

  • A Little ED
  • A Little ED's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
1 year 3 months ago #66186 by A Little ED
Hello all,

I have a 2006 Ford 5.4L Triton and have been dealing with the misfire issues that are pretty common to this engine. 

I bought an Autophix Bluetooth scanner a few years back that has worked great. It would tell me which cylinder was acting up under the mode 6 misfire data before a code was thrown so I could address it with a new coil.  

I recently did a tune up where I disconnected the battery and removed the ECM for access.  Now, the scan tool no longer reads misfire data and says "not supported" when I run the diagnostic. 

I thought maybe my cheap scanner was to blame so I bought a BlueDRIVER but same thing.  It's like the computer stopped reporting this data or something. 

Any ideas why that might happen?  

This thing misfires so often that i cant imagine having to guess which cylinder it is when it starts acting up. 

Any help is appreciated. 

Please Log in or Create an account to join the conversation.

  • Chad
  • Chad's Avatar
  • Offline
  • Moderator
  • Moderator
  • I am not a parts changer.
More
1 year 3 months ago #66193 by Chad
If you disconnected the wiring harness from the ECM, make sure that no pins got bent when reconnecting.

"Knowledge is a weapon. Arm yourself, well, before going to do battle."
"Understanding a question is half an answer."

I have learned more by being wrong, than I have by being right. :-)

Please Log in or Create an account to join the conversation.

  • A Little ED
  • A Little ED's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
1 year 3 months ago #66197 by A Little ED
Replied by A Little ED on topic Scan Tool Stopped reading Mode 6 misfire data
I will check tonight. Thank you.

Please Log in or Create an account to join the conversation.

  • A Little ED
  • A Little ED's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
1 year 3 months ago #66222 by A Little ED
Replied by A Little ED on topic Scan Tool Stopped reading Mode 6 misfire data
Checked the ECM and all pins look good.

Is it possible the vehicle needs to be driven a certain amount of miles before the computer starts to read that data? Doesn't make any sense to me.

Please Log in or Create an account to join the conversation.

  • Tyler
  • Tyler's Avatar
  • Offline
  • Moderator
  • Moderator
  • Full time HACK since 2012
More
1 year 3 months ago #66258 by Tyler

Is it possible the vehicle needs to be driven a certain amount of miles before the computer starts to read that data? Doesn't make any sense to me.


It's possible that the misfire profile got reset when you disconnected the battery. If that's the case, you may not see the misfire counts populating in Mode $06. From Ford theory and operation:

"In the event of battery disconnection or loss of Keep Alive Memory the correction factors are lost and must be relearned."

"The correction factors are learned during closed-throttle, non-braking, de-fueled decelerations in the 60 to 40 mph range after exceeding 60 mph (likely to correspond to a freeway exit condition)."

However, I don't think that should stop the vehicle from reporting back about Mode $06 results if the scanner asks for them. As in, if you ask for Test ID $53 or $0B/0C results, the vehicle should report something back, regardless if there's no misfires or if the profile hasn't learned.

Do any of the other Mode $06 tests report back any results? Do the other OBD functions work correctly (readiness monitors, codes, Mode $09)?

Please Log in or Create an account to join the conversation.

Time to create page: 0.939 seconds