Cannot read mode6 data in 2.3.67 release

[CAR155]

I just started using Forscan, as I apologize for being such a NUB, but I can’t find a reference to this problem in 2.3.67.
I cannot find where to access the Mode6 TID data for the individual tests identified in the factory manual “Diagnostic Monitoring Test Results” table. I need to access the individual oxygen monitor test results.
2002 F250 V10.
Thank you for the help.

[HappyPenguin]

"Mode 6" information is accessed via the screen that comes up when you click the icon on the left side that looks like a clipboard with check marks. Click on the "OBDII -- Mode 6 Test Results for Specific Monitored Systems" line and press the 'play' icon at the bottom. Your "Mode 6" data should appear on a "Results" tab that should have appeared at the top of the screen (right after the "Tests" and "Log" tabs).

[CAR155]

Thank you, Happy Penguin!
Unfortunately, when I go to tests, I only get the KOEO and KOER tests as options. I tried running them but did not get the Mode6 data. I have tried both version 2.3.67 and the latest version 1 I found on the site.
I did the 1 year subscription. No Joy.
There is an older thread that shows a fix for version 1, but the link is broken.

[HappyPenguin]

Thank you, Happy Penguin!
Unfortunately, when I go to tests, I only get the KOEO and KOER tests as options. I tried running them but did not get the Mode6 data. I have tried both version 2.3.67 and the latest version 1 I found on the site.
I did the 1 year subscription. No Joy.
There is an older thread that shows a fix for version 1, but the link is broken.

I just tried some tests (all with the free, non-subscription releases, for a 2004 Ford Ranger) and it looks like there's a bug in the latest Windows version (FORScan 2.3.67).

When I run an older version (2.3.66), I see this:

FORScan-2.3.66--Vehicle-Tests.png (42.44 KiB) Viewed 1687 times

But when I run the latest version (2.3.67), the "Mode 6" selection has disappeared! All I see is this:

FORScan-2.3.67--Vehicle-Tests.png (41.89 KiB) Viewed 1687 times

At first I thought that maybe the developers moved the entry, but I cannot find any "Mode 6" option on any of the screens under 2.3.67.

So, as a work-around for now, I would suggest that you try installing the older 2.3.66 to see if that helps.

P.S. I'm not sure what you mean when you refer to "version 1". Can you please clarify that?

[HappyPenguin]

I see that FORScan for Windows version 2.3.68 is now available and mentions that the "Mode 6" issue on 2.3.67 has been fixed, so I tested it...

Good news: The "Mode 6" test is available once again:

good-news.png (42.59 KiB) Viewed 1214 times

Bad news: It doesn't run to completion or generate a "Results" tab:

bad-news.png (49.4 KiB) Viewed 1214 times

This is on a 2004 Ford Ranger, but I suspect it will affect several other vehicles, given that there were multiple complaints about Mode 6 on FORScan version 2.3.67.

For the record, other OBD2 apps (like "OBDwiz") are able to generate a proper Mode 6 report for this same setup (vehicle, scantool, etc), so the problem is unique to FORScan.

Bottom Line: Anybody who has problems with "Mode 6" on FORScan for Windows, version 2.3.68 (or 2.3.67) should probably go all the way back to version 2.3.66.

[tractmec]

Bottom Line: Anybody who has problems with "Mode 6" on FORScan for Windows, version 2.3.68 (or 2.3.67) should probably go all the way back to version 2.3.66.

It would also be helpful to report this error(Assuming it is an error in FORScan rather than an error in your Ranger) to the FORScan team so if the Bug that appeared in 2.3.67 was not fully cleared they can find out where the error in the code that caused it still resides! Without members like you reporting errors like this, especially with these older vehicles, the team may not be able to see that they have a bug that affects vehicles with the older networks(PWM ISO UBP ect)

If you have never sent in FORScan debug files you can review the process here: https://forscan.org/contactus.html and/or here: https://forscan.org/contactus.html#debug_info!

Up to you!

[HappyPenguin]

Bottom Line: Anybody who has problems with "Mode 6" on FORScan for Windows, version 2.3.68 (or 2.3.67) should probably go all the way back to version 2.3.66.

It would also be helpful to report this error(Assuming it is an error in FORScan rather than an error in your Ranger) to the FORScan team [...]

I don't own the vehicle, so I have no idea if/when I'll be able to connect to it again. But I don't think it will be that hard for the FORScan developers to duplicate this "Mode 6" problem. And, as I said, it doesn't occur with other software so, AFAICT, it is indeed a FORScan problem.

[tractmec]

Bottom Line: Anybody who has problems with "Mode 6" on FORScan for Windows, version 2.3.68 (or 2.3.67) should probably go all the way back to version 2.3.66.

It would also be helpful to report this error(Assuming it is an error in FORScan rather than an error in your Ranger) to the FORScan team [...]

I don't own the vehicle, so I have no idea if/when I'll be able to connect to it again. But I don't think it will be that hard for the FORScan developers to duplicate this "Mode 6" problem. And, as I said, it doesn't occur with other software so, AFAICT, it is indeed a FORScan problem.

Was not stating that the problem was only in the Ranger(And sorry for assuming the Ranger was yours)! I was only suggesting that the only sure way to know is to send the Debug and log files into the team!
I was suggesting this because a few years ago I had a 2005 F150 PCM become unresponsive during a VID block change for Tire Size using the 2.4.09 beta(During the Development of Firmware Updates for .php firmware files) and did not send in my files! When I finally did send them in about 10 months to a year later, I was sent back a very terse email saying: "It is too bad you did not send us this sooner as if you had we could have found and cleared this error 10 months sooner"!

That is all I was suggesting and there was no need to shout your opinion in CAPITAL Abbreviations, you may very well be right! I was only suggesting it as a way to be sure!

You do not have to reconnect or be connected to the vehicle to send in the support files, just send in an email relating what you have experienced with the Ranger and Mode 6 along with the Debug files(dump.bin) and Log files(FORScan.txt ) attached(Zipping them Makes the Attachment smaller for easier emailing) from the FORScan Log folder (link is in the FORScan Folder in the Windows start menu) as per the Support instructions at the links I posted above and if you are right, the Team may be able to clear this suspected error much sooner(they usually only respond to paid license holders but may make an exception if the error is really bad)!

I also Participated in sending in those files to aid in developing UBP Protocol network ability in FORScan(Had two Vehicles at the time with UBP networks and no way to view them and still have the above F150 used in the testing) during the testing and release of Version 2.3.09(Unfortunate they could only get UBP network to read and configure using the FORD VCM2 adapter)!
That experience is just another reason I suggested sending them debug information and log files!

Of course if you cannot be bothered and do not want to help, No skin off my A$$! It is totally up to you whether you wish to help with FORScan's development or not!

[HappyPenguin]

You've already admitted that you jumped to one wrong conclusion, yet you continue to do so with your latest reply. Since I don't think that I can ever explain my situation to you in a manner that you will accept, I won't even bother trying.

P.S. I'm utterly befuddled by your accusation of "shouting", simply because I capitalized the common acronym "AFAICT" ("As Far As I Can Tell") in my previous post. I humbly suggest that you carefully read this, Wikipedia's definition of "acronym":

An acronym is an abbreviation formed using the initial letters of a multi-word name or phrase. Acronyms are often spelled with the initial letter of each word in all caps with no punctuation.

Are you also "shouting" when you capitalize the acronym "PM" in your signature?