SCR efficiency warning without a visible leak: test conversion conditions before condemning the catalyst
A dry AdBlue system can still have a dosing, exhaust-temperature, sensing or conversion problem. An efficiency code such as P20EE describes the system's assessment; it does not independently establish a worn SCR catalyst or a failed NOx sensor.
Establish that the measurements are valid
Identify the SCR configuration and installed sensor positions. Depending on the system, sensor number and diagnostic strategy differ. Record exact codes, readiness/status and conditions rather than comparing two ppm readings without context.
NOx values are meaningful only when the relevant sensors are ready and the operating state supports evaluation. Cold-start values, disabled dosing and rapid load changes are not interchangeable with a stable conversion test.
Compare delivery, temperature and exhaust evidence
Inspect for exhaust leaks and relevant engine-running faults, then assess reductant quality/delivery, dosing and temperature plausibility using the system-specific sequence. No external fluid leak does not prove correct injector quantity or spray behaviour.
Where upstream/downstream readings are available, compare them in a time-aware manner under the prescribed conditions; exhaust transport and sensor response introduce delay. A high downstream reading can reflect poor conversion or a measurement problem, while a low-looking number alone does not establish overall compliance.
Require evidence for the expensive repair
Resolve supply, dosing, temperature or sensor faults that invalidate the efficiency assessment before deciding on the catalyst. A NOx circuit/communication fault is a different starting point from a valid sensor reporting poor conversion.
Only after the supporting functions pass should catalyst performance be judged with the applicable diagnostic test. Do not use generic percentage thresholds, software defeat or repeated warning clears as substitutes for that assessment.
Outcome & verification
The repaired system should complete its relevant efficiency check under valid conditions, with plausible supporting data and no returning associated fault. Record incomplete monitors honestly; a short warning-free trip may not evaluate conversion at all.
Community discussion
Owner experiences, questions and other possible solutions.
No owner experiences yet. Share what was checked and what happened.
Sign in to share your experienceHelpful votes reflect community experience. Repair outcomes are self-reported.