PID Charting Tool ***Improved Version***
From Forscan.org:
Supported vehicles:
- Ford, Lincoln, Mercury models of 1996 - 2023MY (some models of 1994-1995MY are also supported). Attention: Some 2023MY Ford models may not be indentified (we work on it). FORScan may support limited set of functions and configuration parameters for brand new 2021-2023MY models (we work on it). 2024MY Ford and Lincoln models are not supported!
- Mazda models of 1996 - 2022MY up to 6G (inclusively). Attention: Mazda 7G models (new Mazda 3, CX-30, MX-30, CX-50 etc) are supported partially or not supported at all!
I was particularly talking about the PID charting tool. This one seems to be setup to graph out diesel specific information, and lacks information that might be important for a gasoline engine. IE: O2 sensor info, TPS, etc.
I can definitely grab the data logs with ForSCAN, but a PID charting tool like this makes them a lot easier to read and make sense of.

You could most likely graph a FORScan log from the 5.0L using the PID charting tool, but would need to cut and paste (text only paste) or type in the PID names you want in place of the diesel ones you don't need. Your 5.0L PIDs should show up in the "PIDS captured from CSV" side just like the 7.3L ones did.
Then update the chart scales to match the information. Takes a little fiddling, but you are welcome to play with it.
If you'd like, post a log here and I'll play with it as well, and send you what I come up with.

You could most likely graph a FORScan log from the 5.0L using the PID charting tool, but would need to cut and paste (text only paste) or type in the PID names you want in place of the diesel ones you don't need. Your 5.0L PIDs should show up in the "PIDS captured from CSV" side just like the 7.3L ones did.
Then update the chart scales to match the information. Takes a little fiddling, but you are welcome to play with it.
If you'd like, post a log here and I'll play with it as well, and send you what I come up with.
Turns out I didn't need to put in that much effort. An O2 sensor doesn't usually cause a lean condition, just reports it, which causesthe system to add fuel in an attempt to correct. I'd checked over all my vacuum lines and leak points. Didn't want to start pulling the intake and swapping injectors around. Then an aquantence with lots of experience on that particular engine installation said the combination of codes was likely the O2. Figured why not Bought a repalcement on the way home, went to install it the next day and discovered that the plug on the original looked connected but wasn't. Plugged it in good and codes went away.
Next time I'm doing datalogs will probably be for a tuner on the new 5.0L thats getting built and it probably won't be with ForSCAN.





