Adblue warning.

Hi mmi thank you for all help
I manage today to do that extra log and boom Error disappeared and 6500 adblue show up.....I did rev over 2k as someone mention before
I only assume van needed long run to clear it and was about 3 time before when wanted to clear DPF and as you mentioned before with old software adbleu its added after DPF finish cleaning , now when this its sorted I can start working on other issues with van XD
below as requested files from run as reference
 

Attachments

  • LOG-01-IDE00021_&11.CSV
    2 MB · Views: 2
  • blockmap-01-04L-906-056-KG_WV1ZZZ7HZJH164911-20241003-1335.CSV
    126.5 KB · Views: 1
  • blockmap-17-7E0-920-970-S_WV1ZZZ7HZJH164911-20241003-1336.CSV
    33 KB · Views: 1
when I reach home and switch off engine I could hear was still working and I assume DPF regen was on its way l assume that will show on next scan
Correct - the recorded log was 41 minutes and 32.6 km - before capturing the blockmap data below.

IDE00432Particle filter: time since last regeneration42min
IDE00436Particle filter: kilometers since last regeneration33

When I try next sample I will try to ensure revs are high to try force DPF regan
I'm afraid there is no way to force a DPF regen - except using e.g. VCDS

I manage today to do that extra log
Thank you very much - appreciated. Perhaps you could make another set of blockmaps (01, 17) at sometime later when you have accumulated some more miles. E.g. after 100-300 more miles - I'm curious to see how the NOx counters mentioned in post#17 have developed then.
 
Back
Top