Reading EVAP Scan Data and DTCs: Purge, Vent, and FTP Diagnosis

The short version — Every EVAP DTC question comes down to one thing: compare what the scan tool commanded the purge/vent valves to do against what the FTP sensor actually shows happened — the mismatch tells you whether it's a valve, a leak, or a bad sensor.

What the EVAP system is doing and why it matters

The whole point of EVAP is to trap fuel vapor in the charcoal canister and burn it through the intake instead of letting it vent to atmosphere. When something in that path fails — containment, purge flow, or the leak-check itself — you get a code. Before you touch a wrench, understand that scan data and DTCs on this system are telling you which of three functions broke: sealing the tank, purging the canister, or testing for leaks.

The PIDs you'll actually use

On a bi-directional scan tool, the relevant data list normally includes:

• Purge Valve duty cycle / commanded state
• Vent Valve commanded state
• Fuel Tank Pressure (FTP) sensor voltage or pressure reading
• Fuel Level

The primary diagnostic method is comparing the commanded state to the actual pressure response — if the tool says "vent commanded closed" and the FTP reading never moves, the valve (or its wiring) isn't doing what it's told.

To confirm this in the field, you actively command the purge and vent solenoids on and off with the bi-directional scan tool while watching FTP response and listening/feeling for the valve to actuate. If you command the valve and get no pressure change and no physical click/movement, that valve — or its circuit — is your problem.

Matching symptoms to the failed component

This is the part ASE loves to test, because the symptoms are opposite depending on whether the valve is stuck open or stuck closed.

Purge valve:

• Stuck open → unmetered air/vapor keeps leaking into the intake at idle → rough idle, stalling, or lean codes.
• Stuck closed → no purge flow at all, canister can't unload, you may get a fuel-vapor odor, and the purge-flow monitor can fail and set a code.

Vent valve:

• Stuck closed → system can never equalize with outside air → false leak-test failures, or the driver complains the car is hard to fill / fuel backs up at the pump.
• Stuck open → system can never seal, so the leak test can't even run → sets a "system unable to test" code.

Notice the pattern: for both valves, "closed when it should open" and "open when it should close" produce very different — sometimes opposite — symptoms. That's exactly the kind of distinction a test question will hinge on.

Don't blame the mechanical parts before checking the sensor

FTP sensor problems — opens, shorts, or drift — can produce pressure readings that don't make sense, and that alone can set a leak-detection DTC even though the tank, lines, and canister are perfectly sealed. Before you condemn a valve or start smoke-testing hoses, check the FTP sensor output against a known baseline (atmospheric, engine-off) to confirm it's reading correctly. A tech who jumps straight to replacing a purge valve without checking the sensor first can end up throwing parts at a wiring or sensor fault.

Verifying a leak with test equipment — and staying safe doing it

When scan data points toward an actual leak (not a sensor or valve command issue), you'll move to physical leak detection:

• Relieve any residual system pressure or vacuum first, following the smoke machine or pressure tester manufacturer's instructions — don't just hook up cold.
• Only use EVAP-rated leak-detection equipment that applies low, controlled pressure. The tank, lines, and canister are not built for shop air pressures; too much pressure can damage them.
• Never do functional purge/vent solenoid activation testing near open flame or other ignition sources, and remember fuel vapor is present at the fill neck and vent points while you're testing. This isn't a minor housekeeping note — it's a real ignition hazard during a test you'll be running with the engine off and vapors moving.

Easy to mix up

• Purge valve stuck open vs. stuck closed — open = drivability symptoms (rough idle/stall/lean) from unwanted airflow; closed = no purge, odor, saturated canister, failed purge-flow monitor. Reverse those in your head and you'll pick the wrong answer.
• Vent valve stuck closed vs. stuck open — closed = can't equalize (false leak fail, hard refueling); open = can't ever seal (test won't even run, "unable to test" code). These are also opposites, not variations of the same fault.
• A leak DTC doesn't always mean a leak — it can be a bad FTP sensor giving implausible readings. Always verify sensor plausibility before condemning the canister, lines, or valves.

Check yourself

Question: A vehicle sets a code indicating the EVAP system could not complete its leak test, and the customer has no complaint about fueling. Which valve fault fits, and why?

A vent valve stuck open. If the vent can't close, the system can never seal up enough to run the pressure/vacuum decay leak test, so the monitor can't complete and sets a "system unable to test" code. (A vent stuck closed would instead cause hard refueling or false leak-test failures, not an inability to test.)

Question: Technician A says a purge valve stuck closed can cause a lean code and rough idle. Technician B says a purge valve stuck open can cause a lean code and rough idle. Who is right?

Technician B. A purge valve stuck open lets unmetered vapor/air into the intake at idle, causing rough idle, stalling, or lean codes. A purge valve stuck closed instead causes no purge flow, a possible fuel-vapor odor, and a failed purge-flow monitor code — not a lean/rough-idle complaint.

Question: You command the vent valve closed with the scan tool and watch the FTP PID — it never changes, and you don't hear or feel the valve move. Before condemning the valve, what should you check, and why?

Check the FTP sensor's plausibility against a known baseline (atmospheric or engine-off) first. FTP sensor opens, shorts, or drift can produce implausible readings and make it look like nothing happened even when the valve actually moved, so you want to rule out a bad sensor before replacing the valve.