Fuel Delivery
P0400
Exhaust Gas Recirculation Flow Malfunction
The PCM detected that commanded exhaust gas recirculation did not produce the expected change in airflow, manifold pressure, combustion behavior, or EGR feedback.
Diagnostic Snapshot
Atlas Academy
Learn the System
Before diagnosing this code, it helps to understand the system behind it.
Read Understanding Fuel Delivery SystemsTechnical Summary
The PCM detected that commanded exhaust gas recirculation did not produce the expected change in airflow, manifold pressure, combustion behavior, or EGR feedback.
Final QA emphasis: P0400 requires correlation of commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions. The code should be diagnosed by reproducing the enable condition, proving loaded electrical integrity, and independently confirming the physical system. OEM thresholds and system design take priority over universal values.
What You'll Learn
- Understand the exact EGR failure represented by P0400
- Separate restricted flow, excessive flow, control-circuit, and feedback faults
- Use commanded-versus-actual data correctly
- Test vacuum, wiring, sensors, and valve movement before replacement
- Confirm the repair with live data and the correct drive cycle
Think Like a Technician
First decide whether this is a flow problem, an unwanted-flow problem, a control-circuit problem, or a feedback problem. Then use scan data and one direct test to prove the category before removing or replacing parts.
For P0400, ask three questions in order: what did the controller command or observe, can the circuit carry and report that condition correctly, and did the physical system actually respond? Use commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions to identify which layer fails first.
What This Code Means
The EGR system is not operating as expected, but this code does not identify whether the fault is caused by restricted flow, excessive flow, a control problem, a sensor problem, or a mechanical failure.
System Overview
The EGR system routes a controlled amount of exhaust gas back into the intake to reduce peak combustion temperature and nitrogen-oxide emissions. The PCM may verify operation through valve-position feedback, manifold pressure, airflow, oxygen-sensor response, or differential pressure.
Why This Code Sets
The PCM commands EGR under a calibrated operating condition and compares MAP, MAF, oxygen-sensor, combustion, or EGR-position feedback to the expected response. P0400 sets when the response is missing or implausible.
Common Symptoms
- Check Engine Light
- Possible rough idle or hesitation
- Spark knock under load
- Increased NOx emissions
- Possible stalling if the valve sticks open
Most Likely Causes
- 1. carbon restriction or sticking EGR valve/passages
- 2. EGR actuator/solenoid/position-sensor electrical fault
- 3. vacuum/control supply fault where used
- 4. biased MAP/MAF/differential-pressure/temperature feedback
- 5. connector/wiring/reference/ground fault
- 6. PCM driver/input fault after electrical and flow proof
Common Vehicles
EGR faults occur across gasoline and diesel vehicles. Ford DPFE-equipped applications, electronically controlled Chrysler/Jeep EGR valves, GM linear EGR systems, and diesel EGR systems may use different feedback strategies and require manufacturer-specific testing.
Freeze Frame Clues
Engine Temperature
EGR monitors usually run only after the engine reaches operating temperature. A cold freeze-frame may point toward an electrical fault rather than a completed flow test.
RPM and Load
Flow codes commonly set during steady cruise or light-to-moderate load. A code setting at idle may support a valve leaking or stuck open.
Related Data
Review MAP, MAF, fuel trims, commanded EGR, actual EGR position, and related circuit codes before clearing anything.
Live Data Expectations
Commanded EGR and actual EGR position should track each other where position feedback is available. Introducing EGR should create a predictable change in MAP, MAF, fuel trim, idle quality, or differential pressure. The exact response depends on the manufacturer strategy.
Typical Verification Tests
- Command the EGR valve with a bidirectional scan tool
- Compare commanded and actual EGR position
- Monitor MAP, MAF, fuel trim, and idle response
- Apply vacuum manually where appropriate
- Inspect and clean EGR passages
- Test control-solenoid power, ground, and command
- Verify feedback-sensor reference voltage, signal, and ground
Before You Condemn
Do not condemn the EGR valve until the passages, feed tube, vacuum supply, control circuit, feedback sensor, connector, and relevant live data have been checked.
Before Replacing Parts
- Save codes and freeze-frame data
- Check related MAP, MAF, DPFE, misfire, and circuit codes
- Inspect hoses, connectors, and harness routing
- Command the EGR system and watch engine/data response
- Verify passage flow and valve movement
- Test power, ground, signal, and vacuum as applicable
Diagnostic Workflow
- Confirm P0400; save current, pending, history, freeze-frame, readiness, misfire/fuel-trim data where applicable, and the complete powertrain scan before clearing codes.
- Verify the exact definition — Exhaust Gas Recirculation Flow Malfunction — and review VIN-specific system design, enabling criteria, fail-safe strategy, wiring, component locations, bulletins, and test procedures.
- Prioritize companion DTCs and basic prerequisites: battery/charging voltage, module powers/grounds, engine mechanical condition, coolant temperature plausibility, and any shared reference or network faults.
- Recreate the freeze-frame condition safely and graph commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with RPM, load, temperature, vehicle speed, and system voltage.
- Inspect the relevant harnesses, connectors, hoses, pipes, grounds, vacuum lines, fuel/exhaust components, and recent repair areas before disconnecting or replacing anything.
- Compare commanded and actual data. Decide whether the failure is electrical, hydraulic/pneumatic, mechanical, combustion-related, or a sensor-plausibility problem before choosing the next test.
- Perform loaded electrical tests on affected powers, grounds, reference, signal, solenoid, injector, relay, or actuator circuits; static continuity alone is not sufficient for current-carrying circuits.
- Use bidirectional controls where supported to command the affected actuator or system and compare command with current/voltage feedback, sensor response, and actual physical operation.
- Independently verify the physical condition with the appropriate test: calibrated fuel-pressure equipment, smoke/EVAP test, compression/leak-down, ignition waveform, injector balance, airflow/pressure response, or another OEM-approved method.
- Separate bank-specific or cylinder-specific faults from shared-system faults by comparing the opposite bank, neighboring cylinders, redundant sensors, or common feeds under the same operating condition.
- Check for heat-, vibration-, and load-dependent failures by repeating the test as the system warms and by carefully manipulating suspect harness sections while monitoring data.
- Do not condemn a sensor because its reading is abnormal until an independent measurement establishes whether the sensor is wrong or accurately reporting a real physical fault.
- Do not condemn an actuator because it fails to respond until power, ground, control authority, mechanical freedom, and the load side of the circuit are proven.
- Before condemning the PCM, prove stable module powers/grounds, terminal tension, external loads, circuit capability, prerequisite inputs, network integrity, and current calibration/software.
- Repair only the fault supported by test evidence, then perform any required relearn, adaptation, fuel-trim reset, or monitor-specific service procedure.
- Repeat the original enable condition and verify P0400 remains absent current and pending, the monitored data is plausible, driveability is normal, and readiness progresses.
Labor & Inspection Checklist
- Scan all modules and save freeze-frame
- Identify EGR system design
- Inspect valve, passages, tube, hoses, wiring, and connector
- Review commanded and actual EGR data
- Verify vacuum or electrical control
- Test feedback sensor
- Confirm repair with drive cycle
Common Repairs
- Clean EGR passages
- Replace failed EGR valve
- Repair wiring or connector
- Replace failed control solenoid
- Replace biased feedback sensor
- Repair damaged vacuum hoses
Shop Notes
- EGR valve replacement does not fix a clogged intake passage.
- Flow confirmation may use MAP, MAF, oxygen-sensor, combustion, position, or differential-pressure data depending on the vehicle.
- Always check for technical service bulletins and software updates before condemning the PCM.
- On diesel applications, soot loading and cooler restrictions may require additional system-specific tests.
Final QA diagnostic boundary for P0400: Exhaust Gas Recirculation Flow Malfunction. The technician should center the diagnosis on commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions rather than treating the DTC as a replacement instruction.
Evidence hierarchy: preserve freeze-frame first; confirm prerequisites second; compare command/input with loaded circuit behavior third; verify the physical system independently fourth. This order prevents a biased PID or unloaded continuity test from driving the repair.
Failure-pattern note: separate faults that follow engine load, heat, vibration, bank, cylinder, key cycle, purge/EGR command, or pressure demand. A repeatable pattern is often more diagnostic than a single static reading.
Before-parts rule: sensors require plausibility proof, actuators require power/ground/control plus mechanical-response proof, and modules require external circuit/load proof. Do not use a code description as proof of component failure.
Safety/driveability note: Usually driveable with caution, but EGR faults can cause rough idle, stalling, spark knock, smoke, elevated combustion temperature, reduced power, and emissions failure. Severe stalling or power loss requires prompt repair.
Verification standard: reproduce the original enable condition after repair, not merely a warm idle in the bay. Confirm the monitor's related PIDs remain plausible and that no pending code returns.
P0400 QA case-pattern 1: Reproduce the original operating condition and compare commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0400 QA case-pattern 2: Reproduce the original operating condition and compare commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0400 QA case-pattern 3: Reproduce the original operating condition and compare commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0400 QA case-pattern 4: Reproduce the original operating condition and compare commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0400 QA case-pattern 5: Reproduce the original operating condition and compare commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0400 QA case-pattern 6: Reproduce the original operating condition and compare commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
P0400 QA case-pattern 7: Reproduce the original operating condition and compare commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions with an independent physical or electrical measurement. If the scan value changes but the physical system does not, investigate sensor interpretation, control authority, or a mechanical restriction. If the physical system changes but scan feedback does not, investigate the sensing/reference path. If neither changes, prove power, ground, command, and prerequisite conditions before escalating to the controller. Document the before-and-after data so the repair is verified by evidence rather than by the temporary absence of a code.
Technician Notes
- EGR valve replacement does not fix a clogged intake passage.\n- Flow confirmation may use MAP, MAF, oxygen-sensor, combustion, position, or differential-pressure data depending on the vehicle.\n- Always check for technical service bulletins and software updates before condemning the PCM.\n- On diesel applications, soot loading and cooler restrictions may require additional system-specific tests.\n\n
Mechanic's Tip
Graph commanded EGR, actual EGR position, and MAP or MAF together. Seeing the command, valve response, and engine response on one screen quickly separates electrical, mechanical, and flow faults.
Common Mistakes
- Replacing the EGR valve before checking clogged passages
- Ignoring vacuum supply and hose routing
- Cleaning only the valve while leaving the intake passage restricted
- Condemning a DPFE or MAP sensor without checking its hoses and signal
- Clearing the code before saving freeze-frame data
Tools Used During Diagnosis
- Bidirectional scan tool
- Digital multimeter
- Vacuum pump and gauge where applicable
- Back-probes or breakout leads
- Smoke machine where useful
- Basic hand tools
- Service information and wiring diagram
Customer Explanation
The vehicle computer detected that the exhaust gas recirculation system is not flowing or responding correctly. This system lowers combustion temperature and emissions. The valve is only one possible cause, so the passages, controls, sensors, and wiring should be tested before parts are replaced.
Frequently Asked Questions
What does P0400 mean?
P0400 is Exhaust Gas Recirculation Flow Malfunction. The monitor is focused on commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions.
Does the code prove a part has failed?
No. It identifies a failed monitored relationship. Electrical integrity, physical system behavior, and sensor plausibility must be separated before parts are replaced.
Is it safe to drive with P0400?
Usually driveable with caution, but EGR faults can cause rough idle, stalling, spark knock, smoke, elevated combustion temperature, reduced power, and emissions failure. Severe stalling or power loss requires prompt repair.
What should be checked first?
Save freeze-frame and the complete scan, verify the exact system design by VIN, then reproduce the failure while comparing commanded data with actual electrical and physical response.
What freeze-frame clues matter most?
RPM, load, vehicle speed, coolant temperature, system voltage, fuel trims, pressure/airflow data, command state, and companion DTCs show whether the failure occurs at idle, startup, cruise, acceleration, deceleration, or high load.
What live data is most useful?
Graph commanded EGR flow versus actual airflow/pressure/position response, valve movement, passages, differential-pressure or position feedback, and enabling conditions plus system voltage, RPM/load, temperature, and relevant redundant or opposite-bank/cylinder data. Look for the first relationship that breaks.
Can another system create this code?
Yes. Shared voltage, airflow, fuel delivery, exhaust, vacuum, mechanical, or combustion faults can make the named monitor fail even when the named component is functional.
Should I replace the most common part first?
No. Common-failure statistics are useful for prioritizing inspection, not for skipping tests. Expensive or invasive parts should have at least two consistent forms of evidence.
When is professional equipment justified?
Enhanced graphing data and bidirectional controls are strongly recommended. Depending on the code, a pressure transducer/gauge, scope, current clamp, smoke machine, injector balance equipment, or compression/leak-down tools may be justified.
How do I verify the repair?
Repeat the original operating condition, confirm electrical and physical results agree, check current and pending codes, and complete enough of the drive cycle to show stable data and readiness progress.
Related Atlas Resources
Related Atlas Resources
Understanding EGR and Emissions Control
Related Reference Chapters
Diagnostic Confidence
High when commanded-versus-actual data is combined with direct valve, passage, vacuum, and circuit testing.
Related Codes
Project Atlas Feedback
Was this article helpful?
Needs Improvement
Working on this repair?
Create a professional estimate in minutes.
Why Trust This Guide?
Built by mechanics. Improved by mechanics.
This guide is maintained for working mechanics, mobile technicians, fleet maintenance professionals, and independent repair shops.