[T6_measured] Monitoring DPF regeneration, DPF condition, EGR operation

@ebiii
Attached an addendum to Torque - containing the following T6 PIDs

"T6-01 Lambda"​
"T6-01 NOx sensor"​
"T6-01 Particle sensor current"​
"T6-01 Particle sensor operation time"​
NOTE: "T6-01 Particle sensor operation time" will be logged only once in 10 seconds - to not unnecessarily slow down logging. However, the others are logged at maximum speed to catch all the fine details.​

How-to import:​

Torque > Main > Settings > Manage extra PIDs/Sensors > Settings (top right) > Import CSV file​

How-to setup logging:​

Torque > Main > Settings > Data Logging & Upload > Logging preferences/Select what to log > Settings (top right) > Select what to log > Scroll down to find/tick the above.​
At this time perhaps add only the two PIDs related to particle sensor - not to slow down the logging too much. Of course can try with all of them - shouldn't be too bad anyways.​
NOTE: the logging and the dashboard are separate/independent things - however, having the same data item in both doesn't slow down logging as Torque is quite smart combining the data.​
 

Attachments

  • 2023-08-05-T6-01-PIDs.csv
    581 bytes · Views: 8
Take 2 - brought a few obviously related parameters along the same time axis as earlier.

The exhaust temperature sensor S4 should be near the particle sensor. I would expect the IDE08340 be the indicator of detected soot. Obviously need to provide an update for Torque settings to @ebiii

IDE08721IDE08340IDE07984IDE09420IDE07990IDE07987IDE04090
2022-02-11Particle sensor: time in op. mode measurementParticle sensor: measuring current calculated [µA]Particle sensor: cleaning deviation reaction timeHeat quantity for dewpoint end: particle sensorParticle sensor: surface temperatureParticle sensor: exhaust temperatureExhaust temperature /S1/S2/S3/S4
14:35:22000013.8-0.4/8/-13/-15/-13 °C
14:37:270000198.80.3/201/64/35/1 °C
14:38:460000200.84.6/196/102/83/69 °C
14:39:390000200.84.7/321/150/101/66 °C
14:40:560000198.85/368/189/155/66 °C
14:42:040000200.87/360/221/202/83 °C
14:43:110000200.811.2/461/261/236/142 °C
14:44:190000198.814/306/266/272/188 °C
14:45:270000200.819.3/421/303/297/235 °C
14:46:310000198.820.3/305/282/297/258 °C
14:47:430000200.820.3/473/305/293/270 °C
14:48:53000100317.820.5/349/282/301/265 °C
14:49:55000100608.821.9/540/334/281/270 °C
14:51:0658.500.109100198.822.8/410/312/314/290 °C
14:52:14126.200.272100195.822.2/409/314/315/288 °C
14:53:21193.900.446100189.822.1/412/304/297/287 °C
14:54:30261.800.608100180.820.9/447/301/294/276 °C
14:55:38329.600.768100186.821.7/435/295/281/272 °C
14:56:46397.400.937100198.822.6/447/318/319/286 °C
14:57:53465.601.126100198.822.6/430/306/300/291 °C
14:58:58000100504.822.4/415/305/300/280 °C
15:00:17000100488.823/504/325/306/284 °C
15:01:1161.900.113100207.823.2/443/312/309/293 °C
15:02:27130.500.271100207.822.8/448/318/315/290 °C
15:03:31198.300.421100191.821.9/334/297/302/288 °C
15:04:47265.900.583100195.821.6/442/304/294/279 °C
15:05:43333.600.745100186.821.6/424/298/294/275 °C
15:07:02401.600.889100183.820.5/382/299/295/272 °C
15:08:01469.401.073100180.819.9/456/299/288/271 °C
15:09:14537.401.253100175.820.3/339/282/268/265 °C
15:10:21000100283.820.3/353/307/311/266 °C
15:11:29000100287.820.2/347/299/288/282 °C
15:12:36000100280.820.8/439/307/289/267 °C
15:13:43000100275.822.8/389/303/301/272 °C
15:14:52000100293.821.5/247/283/318/289 °C
15:16:02000100290.821.2/251/260/271/293 °C
15:17:06000100280.818.9/367/285/282/253 °C
15:18:15000100272.819.6/372/290/284/254 °C
15:19:24000100274.821/396/306/321/265 °C
15:20:32000100287.820.4/434/301/290/282 °C
15:21:39000100280.821/400/299/291/270 °C
15:22:47000100275.820.4/394/288/279/265 °C
15:23:54000100275.819.2/214/236/271/257 °C
15:25:01000100268.818.2/453/283/260/254 °C
15:26:11000100267.818.5/421/278/262/239 °C
15:27:17000100269.818.1/378/284/275/245 °C
15:28:27000100264.818.4/406/285/272/245 °C
15:29:29000100272.817.2/302/261/272/242 °C
15:30:41000100264.818/390/276/254/245 °C
15:31:50000100262.817.7/463/291/271/237 °C
15:32:53000100259.819.4/404/297/286/242 °C
15:34:05000100272.820.9/397/291/289/267 °C
15:35:12000100272.821.1/455/293/283/269 °C
15:36:20000100274.822.7/486/310/299/273 °C
15:37:27000100285.822.8/235/268/284/284 °C
15:38:35000100287.820.1/167/225/288/269 °C
15:39:43000100282.818.9/168/215/258/265 °C
15:40:51000100282.818.1/214/192/185/237 °C
15:41:58000100269.817.6/334/228/217/223 °C
15:43:07000100264.815.7/343/236/212/195 °C
15:44:56000100264.815.5/300/210/210/198 °C
15:46:10000100272.815/173/180/199/194 °C

Note: The snippet is an extract of a continuous recording stream of all engine parameters thus the sampling rate is quite slow (once per 70 seconds - because of 1495 parameters being recorded).

You have obiviously noted this already as marked in bold but interesting anyway how the sensor does it’s own regen heating before the actual measurement cycle begins. Maybe, being after DPF, the exhaust temperatures are never high enough to base sensor regen on exhaust only. Or simply because same sensors are probably used in wide variety of different engines.

Some other remarks:
  • Winter time… particle sensor exhaust temperature seems interesting. Maybe the sensor has it’s own mini-exhaust that goes straight to open air?
  • Can’t get my mind around what the IDE09420 means. Perhaps not significant at all but maybe worth checking out on some cold really moist morning if it’s ever different than 0 or 100.
  • Might be coincidental but exhaust temp S1 peaks right at when particle sensor surface temp does
  • IDE07984 is also bit of a mystery. It has a rising trend throughout the measurement, maybe some kind of a quality metric of the measurement? Hard to tell, would need to dive more into how particle sensors work
 
@ebiii
Attached an addendum to Torque - containing the following T6 PIDs

"T6-01 Lambda"​
"T6-01 NOx sensor"​
"T6-01 Particle sensor current"​
"T6-01 Particle sensor operation time"​
NOTE: "T6-01 Particle sensor operation time" will be logged only once in 10 seconds - to not unnecessarily slow down logging. However, the others are logged at maximum speed to catch all the fine details.​

How-to import:​

Torque > Main > Settings > Manage extra PIDs/Sensors > Settings (top right) > Import CSV file​

How-to setup logging:​

Torque > Main > Settings > Data Logging & Upload > Logging preferences/Select what to log > Settings (top right) > Select what to log > Scroll down to find/tick the above.​
At this time perhaps add only the two PIDs related to particle sensor - not to slow down the logging too much. Of course can try with all of them - shouldn't be too bad anyways.​
NOTE: the logging and the dashboard are separate/independent things - however, having the same data item in both doesn't slow down logging as Torque is quite smart combining the data.​
Thank you ! it's getting more and more interesting ! I'll update the torque and do some more logging and analysis ! And I'll catch up with the messages from the last 2 days
 
You have obiviously noted this already as marked in bold but interesting anyway how the sensor does it’s own regen heating before the actual measurement cycle begins. Maybe, being after DPF, the exhaust temperatures are never high enough to base sensor regen on exhaust only. Or simply because same sensors are probably used in wide variety of different engines.

Some other remarks:
  • Winter time… particle sensor exhaust temperature seems interesting. Maybe the sensor has it’s own mini-exhaust that goes straight to open air?
  • Can’t get my mind around what the IDE09420 means. Perhaps not significant at all but maybe worth checking out on some cold really moist morning if it’s ever different than 0 or 100.
  • Might be coincidental but exhaust temp S1 peaks right at when particle sensor surface temp does
  • IDE07984 is also bit of a mystery. It has a rising trend throughout the measurement, maybe some kind of a quality metric of the measurement? Hard to tell, would need to dive more into how particle sensors work

This looks interesting :geek:


Some quick takeaways:
  • Temperature has to be higher than dew point for the measurement to start, I suppose otherwise part of exhaust liquidifies and resistance measurement goes awry
  • Afaiu measurement works so that it measures until a threshold resistance (or time?) is reached. The time to reach the threshold is compared to a model map value of a similar driving cycle to decide pass/fail outcome
  • IDE08340 should indeed be the ”soot metric”. However it’s not linear - the absolute amount of soot during measurement cycle depends heavily on eg rpm so the current by itself is not enough
 
Last edited:
Just logged a bit on small trips with the new settings, here is my log, I'll perform some analysis soon !
 

Attachments

  • trackLog-2023-ao–t-06_17-45-56.csv
    488.7 KB · Views: 6
Indeed the particle sensor is registering something... :eek:

Did you also get any of the faults codes?
P226D00 - Particle filter damaged or substrate missing Intermittently
P24B100 - Particle sensor measurement electrode short-circuit to positive pole Intermittently
P24B000 - Particle sensor measurement electrode short-circuit to ground Intermittently

1691356725207.png

Zoomed in​

1691357008454.png

Well below the 10 minutes...
 
Indeed the particle sensor is registering something... :eek:

Did you also get any of the faults codes?


View attachment 208704

Zoomed in​

View attachment 208706

Well below the 10 minutes...
Well, no I just have a consistent P226D00 (intermittent but consistent motor light) since I replaced the EGR valve, (and P226D was present before the change as well). Do you see something fishy?
 
Last edited:
Thank you @ebiii for the data - now we know what the case of P226D might look like from the sensor perspective!

To me it looks like the particle sensor is working as expected. Combined with @mmi noting the measurement cycle is <10 min and the sensor operation PDF I linked earlier, it looks like the measurement cycle ends early due to measured soot levels reaching the simulated threshold value.

This probably confirms the earlier diagnosis of a partially shot DPF, it has a crack or some other damage that lets some soot through to the exhaust. Most likely a MOT failure and the soot might eventually degrade post-DPF sensors by covering them to soot. Other than that, I don’t think there’s immediate danger of breaking more components as the DPF still seems to perform regens normally and the differential pressures seem normal so probably the crack is a small one and let’s other systems function normally. That said, I’m not an expert so take above with a healthy dose of salt.
 
Thank you @ebiii for the data - now we know what the case of P226D might look like from the sensor perspective!

To me it looks like the particle sensor is working as expected. Combined with @mmi noting the measurement cycle is <10 min and the sensor operation PDF I linked earlier, it looks like the measurement cycle ends early due to measured soot levels reaching the simulated threshold value.

This probably confirms the earlier diagnosis of a partially shot DPF, it has a crack or some other damage that lets some soot through to the exhaust. Most likely a MOT failure and the soot might eventually degrade post-DPF sensors by covering them to soot. Other than that, I don’t think there’s immediate danger of breaking more components as the DPF still seems to perform regens normally and the differential pressures seem normal so probably the crack is a small one and let’s other systems function normally. That said, I’m not an expert so take above with a healthy dose of salt.
Thank you for your analysis, it's very plausible. One thing though, I passed the MOT successfully even with that problem (I erased the error but the emissions were not flagged as abnormal). A garage is advising ultra-sound cleaning but I think that now we know more about this error than most garages.
I think that as long as MOT passes there is no problems keeping it like this as long as I watch the regen and the pressure regularly.

Would be interesting to have it cleaned and check the data again
 
Last edited:
Yes indeed - thank you @ebiii for sharing the log files. It's something I haven't seen before - definitely a good reference for future. I agree with @n10n's analysis.
Well, no I just have a consistent P226D00 (intermittent but consistent motor light) since I replaced the EGR valve, (and P226D was present before the change as well). Do you see something fishy?
Good thing it's "only" P226D although a kind of mystery what were the other two glitches (which a kind of were pointing to the sensor or it's wiring).

After clearing the fault do you get the it back on the next trip or does the ECU "double-check" the failure before manifesting it as a fault code?
 
Yes indeed - thank you @ebiii for sharing the log files. It's something I haven't seen before - definitely a good reference for future. I agree with @n10n's analysis.

Good thing it's "only" P226D although a kind of mystery what were the other two glitches (which a kind of were pointing to the sensor or it's wiring).

After clearing the fault do you get the it back on the next trip or does the ECU "double-check" the failure before manifesting it as a fault code?
The p226D faut appears immediatly if I scan, however not before about 200 km on the car's dashboard.
 
Thanks - a good piece of information.
Have you checked the code with Torque - I would expect the fault would be "pending" the first 200 km. See post#2 >> [T6_measured] Monitoring DPF regeneration, DPF condition, EGR operation
Exactly it's pending. I have read the following :
"The error P226D means that the MSG is reported less differential pressure than expected in corresponding operating situations. If so much exhaust gas escapes through a defective EGR pipe that there is a total lack of exhaust gas volume at the DPF inlet, the differential pressures also fall out of the software window and the error message appears. That would be an explanation.....

However, if the error occurs with an intact exhaust system (no leaks), the differential pressure sensor or the lines must be checked."

Do you think there is a way to spot a leak between engine and dpf ? Maybe with the air intake data ? Or maybe it's a wrong idea but I think checking leaks makes sense. In the meantime I'll check for leaks with the soapy water method, it seems effective.
What I cannot comprehend is that if the metrics are ok, how can the ECU spot a cracked DPF (it could be soot build up not matching the differential pressure meaning a crack)
 
Last edited:
Well, you have soot in a tailpipe and particle sensor giving current readings >0.

These symptoms correspond exactly to the test situation in the particle sensor test setup in the PDF I linked in post #64. Here the DPF filter is drilled with holes to get a constant soot flow through the filter, where there should be none normally.

So, the leak would be within DPF, not to/from air.

IMG_3954.png


> What I cannot comprehend is that if the metrics are ok, how can the ECU spot a cracked DPF

This is why the particle sensor is there in the first place - it’s job is to detect any soot particles getting through DPF. Your particle sensor readings were not ok, ”Particle sensor current” metric rising and test cycle lasting less than 10 minutes.

That said, ofc there can be other faults as well but this is what the data we’re looking at now points to.
 
Well, you have soot in a tailpipe and particle sensor giving current readings >0.

These symptoms correspond exactly to the test situation in the particle sensor test setup in the PDF I linked in post #64. Here the DPF filter is drilled with holes to get a constant soot flow through the filter, where there should be none normally.

So, the leak would be within DPF, not to/from air.

View attachment 208864


> What I cannot comprehend is that if the metrics are ok, how can the ECU spot a cracked DPF

This is why the particle sensor is there in the first place - it’s job is to detect any soot particles getting through DPF. Your particle sensor readings were not ok, ”Particle sensor current” metric rising and test cycle lasting less than 10 minutes.

That said, ofc there can be other faults as well but this is what the data we’re looking at now points to.
Oh I didnt get it the first time thanks ! It makes sense now ! So the real soot detector is the resistance/current in the sensor if I understood correctly.
 
Things are weird today, just logged for a long trip uninterrupted. Static P226D should have come as usually but didn't.

P226D is there unconfirmed for way longer than usual, but P0401 Intermittent appeared as well despote the New EGR.
Also noticed it lost a lot of water, but I guess it's just condensation.

I'll analyse the log attached when I get home

Edit: p226d is now confirmer but it tool way longer than usual
P401 totally disappeared, I relog to compare

Screenshot_20230813_105921_Torque.jpg

20230813_110637.jpg
 

Attachments

  • trackLog-2023-août-13_08-05-24.csv
    1.7 MB · Views: 2
Last edited:
Things are weird today, just logged for a long trip uninterrupted.
Indeed. Thank you very much. Intriguing. :geek:
Static P226D should have come as usually but didn't.
Perhaps a set number of driving cycles is also needed? When it was cleared last time?

1691953876467.png

Note: For some reason recording of exhaust temperatures did not start until 6973 seconds. They were set to use generic OBD PIDs - all the others are VW specific PIDs.
 
Indeed. Thank you very much. Intriguing. :geek:

Perhaps a set number of driving cycles is also needed? When it was cleared last time?

View attachment 209566

Note: For some reason recording of exhaust temperatures did not start until 6973 seconds. They were set to use generic OBD PIDs - all the others are VW specific PIDs.
It was cleared by à non vw garage on Monday morning, did about 20km / day for 6 days and then about 300 km until it went back on. I dont think the leak has anything to do with as my AC stopped working few hours after the pictures
 

UPDATE:​

A Torque extension to monitor actual AdBlue level and AdBlue range counter in ECU​

revised in post #3 (direct link below)
 
Back
Top