quangdog
Well-Known Member
- First Name
- Kimball
- Joined
- Mar 31, 2020
- Threads
- 33
- Messages
- 685
- Reaction score
- 2,200
- Location
- Meridian, Idaho
- Website
- www.youtube.com
- Vehicle(s)
- 2019 Ranger Lariat FX4
Whelp, I tried this. I reset the CEL on Tuesday, then hooked up a laptop and every time I drove the truck since then I did it with Forscan running and making pretty graphs of what the EVAP system components were doing. I was able to capture the EVAP tests running, but I'm having trouble making good sense of the results. The PIDs I was able to plot don't always make a lot of sense, and everything is pretty cryptic. Also, Forscan is pretty limited with how much it lets you zoom out and read through the results. Here are a few screenshots - First, here's a list of the PIDs I graphed, though this does not:The best suggestion I've found so far is to start by understanding the system, then use Forscan to real-time monitor each of the components in the system while driving around trying to get the code to trigger. If you can catch the test as the vehicle runs it, while monitoring each component in Forscan, it should be easy to identify which specific component has failed.
Still - pain in the arse to troubleshoot.
And here is the Oscilloscope graph of these pids for a drive which detected a problem and turned on the CEL:
Apologies that it's pretty tough to read (click on it to zoom in) - I may try to see if I can get a better capture by hooking up to an external display that offers a higher resolution.
Does anyone have enough experience troubleshooting this sort of thing in Forscan to be able to point me to which component may be my culprit? I mean - I can clearly see the test running, clearly see pressures changing, but I'm not sure which phase of the test caused it to fail, and which pressure reading was out of spec.
I saved all my drive oscilliscope data, and would be happy to share it with anyone who may be interested in troubleshooting further with me.
Thanks!
Sponsored