Audi CRTD engine.

User avatar
admin
Site Admin
Posts: 150
Joined: Sun Jun 02, 2019 10:58 pm

Re: Audi CRTD engine.

Post by admin » Thu Jun 04, 2020 10:30 pm

That feature already exists, but it's activated only when the automatic data reading is active.

foreroadicto
Posts: 23
Joined: Sat Mar 07, 2020 4:41 pm

Re: Audi CRTD engine.

Post by foreroadicto » Tue Jun 16, 2020 2:40 pm

Hi. Today it regenerated me and worked perfectly in group 16.

Tip: be able to activate or deactivate separately the sound of passive and active regeneration.

Thank you.

SinSinSin
Posts: 3
Joined: Sun Jul 05, 2020 2:42 pm

Re: Audi CRTD engine.

Post by SinSinSin » Sun Jul 05, 2020 2:49 pm

Hello Everyone ,
I tried to observe VAG DPF when it starts to go in active mode while driving - it's around 100%+14% in my A6 allroad C7 3.0 CRTD . I did 30km highway and readings went down to ~20% .
When I had 100%+14% (ECU readings) I switched to Group 10 and 16 and got 100%+5% .
It World be great if You could fixx the problem .
On my other two 2.0 TDI engines it works perfectly (thank You for that😁 ) !

User avatar
admin
Site Admin
Posts: 150
Joined: Sun Jun 02, 2019 10:58 pm

Re: Audi CRTD engine.

Post by admin » Mon Jul 06, 2020 9:07 am

This mismatch with 3.0 TDI engines is the reason why I added a special option in the menu to override the field regeneration limit.
I didn't tested any 3.0 TDI so all the compatibility is based on user's reports. I read that many users have the same problem due to a different dimension of the DPT filter in their car. Without certain data to be used, I added the option to let all user the possibility to set a custom value.
Consider that almost all 2.0 TDI engines have a limit set around 22-24 grams.
If you see your regeneration starting at 114%, your limit value should be around 28-30 grams (considering that many times the regeneration starts a little below the 100% value).
Try to set a custom limit value of 28 or 30 and check if your values become more realistic.

Bye

SinSinSin
Posts: 3
Joined: Sun Jul 05, 2020 2:42 pm

Re: Audi CRTD engine.

Post by SinSinSin » Mon Jul 20, 2020 10:52 am

Welcome again,
I did some measurements during driving . I got max 100%+32% , DPF started to "warm up" at 29.23 g of sort mass. How can i overwrite calulacions ? :twisted:
Attachments
Screenshot_20200718-200942_VAG DPF.jpg

SinSinSin
Posts: 3
Joined: Sun Jul 05, 2020 2:42 pm

Re: Audi CRTD engine.

Post by SinSinSin » Mon Jul 20, 2020 11:01 am

Ok , i'm sorry ... i gave a new value 29 in overwrite field .
We'll see how it will work 8-)

User avatar
admin
Site Admin
Posts: 150
Joined: Sun Jun 02, 2019 10:58 pm

Re: Audi CRTD engine.

Post by admin » Mon Jul 20, 2020 4:40 pm

29 or 30 should be the right value.
Let us know how it works, thanks

foreroadicto
Posts: 23
Joined: Sat Mar 07, 2020 4:41 pm

Re: Audi CRTD engine.

Post by foreroadicto » Thu Jul 23, 2020 6:32 pm

Hi.

First regeneration by "soot mass calc (g)" limit Up to now I always did it by KM limit (1.400), but now I use it for short journeys.

I'm passing you some screenshots because there are a couple of faults in group 16:
- It does NOT change the value of "field regn. request status". When it is done by km it does change.
- The red hourglass marking the regeneration does NOT appear. When it is done by km it does appear.

I don't care because at least I know when it regenerates even if those two things don't work, but just so you know.

I'll keep trying if it jumps to 29.8 g all the time. Thank you.

REGENERATION BY "G" LIMIT

20200723_123913.jpg
20200723_125306.jpg
20200723_125320.jpg
20200723_125602.jpg
20200723_130013.jpg
20200723_130333.jpg


REGENERATION BY "KM" LIMIT

20200616_104425.jpg

User avatar
admin
Site Admin
Posts: 150
Joined: Sun Jun 02, 2019 10:58 pm

Re: Audi CRTD engine.

Post by admin » Thu Jul 23, 2020 9:07 pm

Thanks for the update, useful to know how your engine works. Unfortunately, I can't test every VAG engine and these ECU differences can't be predicted without a real engine scan using my instruments.
As you said, this isn't a blocking issue and you can use the app without problems, keeping in mind this different behavior.
In the meantime I register the issue hoping to solve it in the future, maybe testing a similar engine.

Post Reply