Agreed, sounds like a plan
Where did you find the engine flags above mateThank you very much!
Quite a discrepancy in remaining AdBlue range what Instruments sees (450 km) vs. what engine reports (9635 km).
Also marked with red/yellow other not normal values - obviously the AdBlue Warning is stored here.
View attachment 160500
Interesting why/how the Instruments has taken a separate path. Possibly the "flags" below from engine are the cause
ENG110382-ENG20519 SCR inducem system status-deviation of reagent consumption CONSUMP_DEVIATION ENG110382-ENG20518 SCR inducem system status-incorrect reagent INCORR_REAG ENG110382-ENG20518 SCR inducem system status-incorrect reagent INCORR_REAG ENG110382-ENG20518 SCR inducem system status-incorrect reagent INCORR_REAG ENG110382-ENG20516 SCR inducem system status-inducement system active active
Just remains the mystery what's the root cause -
They are in the blockmap -files you posted. I compared your files with quite a few of my logs - on yours they are different than in my logs (no faults) that''s why I believe they are some kind of status "flags".
Thanks! Intriguing data
A few snippets below -
(A) NOx sensor is powered at 672.56 seconds (12 minutes) - normal
(B) NOx sensor "initializes" approx. 20 seconds later (pattern 1650,...) - normal - starts reporting meaningful values a few seconds later - normal (below green 28, 46, 57,...)
(C) OBD channel IDE04098 for NOx sensor "wakes up" a minute later at 759.67 seconds - normal'ish
I do not have exact data on this - just observed that indeed there is a delay 1-2 minutes between sensor raw data and the OBD data (NOx11...)
I apologize unclear instructions - should have mentioned it's best to search the channels by IDExxxxx numbers as the descriptions are not always unique. A few channels of second NOx sensor (which this engine doesn't have) were now recorded - thus just no data from those.
However, the NOx values (channel IDE09017) show NOx average of 78 ppm - which is quite/very high when compared with engine revs on journey (average 1290 RPM).
I would expect to see less than 25ppm under these condition (even below 10ppm with the updated ECU software). The above might actually explain the P20EE faults in earlier log.
I believe the NOx sensor works correctly (wake up, live data). Assuming the values reported by sensor are of right magnitude, the evidence (high NOx) suggests that the AdBlue injection might be seriously hindered.
Do you know if something was done with the DPF approx. 10000 miles ago?
Thanks! Intriguing data
A few snippets below -
(A) NOx sensor is powered at 672.56 seconds (12 minutes) - normal
(B) NOx sensor "initializes" approx. 20 seconds later (pattern 1650,...) - normal - starts reporting meaningful values a few seconds later - normal (below green 28, 46, 57,...)
(C) OBD channel IDE04098 for NOx sensor "wakes up" a minute later at 759.67 seconds - normal'ish
I do not have exact data on this - just observed that indeed there is a delay 1-2 minutes between sensor raw data and the OBD data (NOx11...)
View attachment 160677
I apologize unclear instructions - should have mentioned it's best to search the channels by IDExxxxx numbers as the descriptions are not always unique. A few channels of second NOx sensor (which this engine doesn't have) were now recorded - thus just no data from those.
However, the NOx values (channel IDE09017) show NOx average of 78 ppm - which is quite/very high when compared with engine revs on journey (average 1290 RPM).
I would expect to see less than 25ppm under these condition (even below 10ppm with the updated ECU software). The above might actually explain the P20EE faults in earlier log.
I believe the NOx sensor works correctly (wake up, live data). Assuming the values reported by sensor are of right magnitude, the evidence (high NOx) suggests that the AdBlue injection might be seriously hindered.
Do you know if something was done with the DPF approx. 10000 miles ago?
After speaking to previous owner he said it had a dpf clean by a proper company a year or two agoThanks! Intriguing data
A few snippets below -
(A) NOx sensor is powered at 672.56 seconds (12 minutes) - normal
(B) NOx sensor "initializes" approx. 20 seconds later (pattern 1650,...) - normal - starts reporting meaningful values a few seconds later - normal (below green 28, 46, 57,...)
(C) OBD channel IDE04098 for NOx sensor "wakes up" a minute later at 759.67 seconds - normal'ish
I do not have exact data on this - just observed that indeed there is a delay 1-2 minutes between sensor raw data and the OBD data (NOx11...)
View attachment 160677
I apologize unclear instructions - should have mentioned it's best to search the channels by IDExxxxx numbers as the descriptions are not always unique. A few channels of second NOx sensor (which this engine doesn't have) were now recorded - thus just no data from those.
However, the NOx values (channel IDE09017) show NOx average of 78 ppm - which is quite/very high when compared with engine revs on journey (average 1290 RPM).
I would expect to see less than 25ppm under these condition (even below 10ppm with the updated ECU software). The above might actually explain the P20EE faults in earlier log.
I believe the NOx sensor works correctly (wake up, live data). Assuming the values reported by sensor are of right magnitude, the evidence (high NOx) suggests that the AdBlue injection might be seriously hindered.
Do you know if something was done with the DPF approx. 10000 miles ago?
We tested the adblue injector it was atomising but slowly and not much adblue was dosed but we have nothing to compare with if it's normal or not
Hmmm... that's interesting - makes me wonder why. The DPF should last over 150.000 miles.
Makes me wonder what's the condition of SCR trap catalytic converter inside the DPF (the NOx trap).
Specifically about T6 engines more here, page 27 onwards. The NOx trap on page 28.
SSP 564 - The T6 2.0L TDi
VW Self Study Programme, Document 564 - The 2.0 litre TDI Engine In The T6 The introduction of modern, particularly efficient Euro-6 engines represents a central feature of the new T6. All units are equipped with Blue Motion Technology as...
More general information about AdBlue systems
Unfortunately Engine's repair manual doesn't offer any more information.- just instructions how to replace parts.
Have you tried Adaptation of EGR... under Engine - Basic Settings?
Yes, by comparing first and last blockmap - sensor reading went from 131 mm down to 119 mm - while driven 691 km.
By those numbers the engine would be guzzling AdBlue - mine runs three times longer with the same sensor readings.
Perhaps the van was not parked the same way - incline may be?
I guess blockmap data was not captured right after the reflash? Would have been interesting to see what was different.
In the blockmap data these ones are still suspicious = different what i've seen.
| ENG110382-ENG20519 | SCR inducem system status-deviation of reagent consumption | CONSUMP_DEVIATION |
| ENG110382-ENG20518 | SCR inducem system status-incorrect reagent | INCORR_REAG |
| ENG110382-ENG20518 | SCR inducem system status-incorrect reagent | INCORR_REAG |
| ENG110382-ENG20518 | SCR inducem system status-incorrect reagent | INCORR_REAG |
| ENG110382-ENG20516 | SCR inducem system status-inducement system active | active |
I believe they are related. P20EE just indicates too high NOx level in the exhaust, which is a consequence of poorly working NOx reduction system as a whole. Thus a guess would be either the AdBlue system itself - P204F, or go with P20EE NOx Catalyst Bank - Efficiency too low. In the worst case the latter would mean that the SCR trap catalytic converter inside the DPF isn't working as desired.
Just to keep all pieces together - Readings of G849 Reducing agent quality sensor was briefly discussed here.:
More Adblue woes
Had a few issues with adblue on my 2016 102 t6 had it in the garage and all was ok now got and error adblue (Def) on the dash I've scanned it with vcds no error codes related to adblue although have an egr sensor implausible signal fault . It has happened before then cleared itself some the...
Won’t start. No fault codes
Quote from WSM. (Download above) Lock high-pressurepump hub with diesel injection pumplock‐ ing pin- T10492- . Todo this,insert lockingpin intofork -2-on hub and into hole -1- behind it in bracket for ancillaries. – Pull out locking pin, and slightly loosen nut for high-pressure pulley. Before...
PS. I edited the post #20 - now there is attached a VCDS preset file for setting up measurements. If you have a chance to make another recording so we could see AdBlue amounts the engine reports using vs. NOx levels.
I don't know if it would change anything - because it seems the engine is seeing the level correctly and also the range accordingly (below).
Probably won't hurt.
Similar threads
