EML Light on, VCDS scan implies an SCR fault?

[mmi]

It seems that there is an update available:

It should cure both P204F and P20EE issues.

As the light went out of its own accord would you leave doing anything and see if it re appears? I didn't clear the fault code.

The long term solution would be to get the ECU updated. It's a bit difficult to predict if/when it will reappear. I recorded on mine 26 occurrences of the P20EE but it never crossed the threshold to turn on emission warning light.

Worth noting that VCDS has two different modes to scan the faults.

The trick is that VW tester ODIS uses "non-aggressive" mode which e.g. doesn't show your P204F fault (no freeze frame data any more). Also the current P20EE will be beyond their reach after approx. 300 km's - the ECU makes it fade away but fortunately keeps updating the frequency counter.

 

[huw169]

Yes, it can be seen under Advanced ID - Flash Status, 0/1/1 would be as from factory.

@mmi please can you point out where you are seeing that?
Thanks

 

[mmi]

@mmi please can you point out where you are seeing that?
Thanks

VCDS > Select Control Module > Engine > Advanced ID

 

[huw169]

VCDS > Select Control Module > Engine > Advanced ID

Not in the scan then. I was going through mine line by line.
Thank you

 

[BrenR]

It seems that there is an update available:
View attachment 95021
It should cure both P204F and P20EE issues.

The long term solution would be to get the ECU updated. It's a bit difficult to predict if/when it will reappear. I recorded on mine 26 occurrences of the P20EE but it never crossed the threshold to turn on emission warning light.

Worth noting that VCDS has two different modes to scan the faults.
View attachment 95024
The trick is that VW tester ODIS uses "non-aggressive" mode which e.g. doesn't show your P204F fault (no freeze frame data any more). Also the current P20EE will be beyond their reach after approx. 300 km's - the ECU makes it fade away but fortunately keeps updating the frequency counter.

Thanks. So worth seeing about the update then.

Would you suggest I only do the non aggressive scan in future?

 

[mmi]

Would you suggest I only do the non aggressive scan in future?

Non-aggressive scan shows only "active" faults, or very recent ones. Just good to know that only these are seen at VW garage.

The non-active faults are more just a history log - possibly long-term early warning kind of thing.

I would keep on doing aggressive scans - more is better

 

[sippe]

Could it be that for the central electrics faults that there's a connector loose or something (after disconnecting one for works, forgot to reconnect or so, don't ask why I think about this possibility ;-) )

 

[Cb83]

Hi all, I have fault code P20EE and after reading this thread I'm still quite confused. As far as I can see from carista:

Engine
Part #: 04L906056KA
Component: R4 2.0l TDI
Software version: 4047

My software is the older version? So would updating this stop the fault? Can any vw specialist do this or is it a main dealer only situation. Any help is greatly appreciated.

 

[mmi]

Hi all, I have fault code P20EE and after reading this thread I'm still quite confused. As far as I can see from carista:

Engine
Part #: 04L906056KA
Component: R4 2.0l TDI
Software version: 4047

My software is the older version? So would updating this stop the fault? Can any vw specialist do this or is it a main dealer only situation. Any help is greatly appreciated.

Yes, the software version 4047 is old/initial one. The new version is 6163.
Yes, this will fix the software glitch which caused elevated NOx levels in the exhaust thus eventually triggering the P20EE fault.
I'd stick with VW for the update - you might even get free AdBlue refills. Although, the update is available to any garage (as was regulated by EU).

 

[Cb83]

Brilliant @mmi thank you for that.

 

[Martinf]

I noticed EML showing half way through an 80 mile journey on 12/12/20. A Carista scan reported P20EE fault. Next day I booked it into VW for first available date, which was yesterday 19/01/21. Not impressive if anything is critical!
To resolve the issue they performed software update TPI 2054601. I hope it is a permanent resolution. Compensation for the said increased AdBlue consumption is the ‘voucher’ for 8 AdBlue refills.

 

[mmi]

I noticed EML showing half way through an 80 mile journey on 12/12/20. A Carista scan reported P20EE fault. Next day I booked it into VW for first available date, which was yesterday 19/01/21. Not impressive if anything is critical!
To resolve the issue they performed software update TPI 2054601. I hope it is a permanent resolution. Compensation for the said increased AdBlue consumption is the ‘voucher’ for 8 AdBlue refills.

Did you note down engine software identifiers before and after the update by any chance?

Engine
Part #: 04L906056KA
Component: R4 2.0l TDI
Software version: 4047

 

[Cb83]

Is there a cost involved in having the software updated? My van is out of warrenty

 

[Robert]

Is there a cost involved in having the software updated? My van is out of warrenty

Out of warranty software updates are normally being charged by VW stealers unless it is Recall or Service Campaign.

Volkswagen Transporter Recalls in EU

List of Volkswagen Transporter recalls that have been issued via the European Safety Gate alert system and by the German KBA.

car-recalls.eu

 

[T6Paul]

I had to pay £80, I tried to argue for good will but was refused. Well over 4k miles now since the update, Ad-blue consumption has increased but re-gens seem to be quicker and no EML.

 

[Martinf]

Did you note down engine software identifiers before and after the update by any chance?

Carista output before and after. I note that the 'before' does not include a "Software version:". Maybe update to Carista OBD2 v5.4 added this detail?

Engine
Part #: 04L906056KG
Component: R4 2.0l TDI
Coding: 00254014432401090000 (hex)
Fault codes:
31103 Manufacturer-specific code

Engine
Part #: 04L906056KG
Component: R4 2.0l TDI
Software version: 6168
ASAM/ODX identifier: EV_ECM20TDI03004L906056KG
Coding: 00254014432401090000 (hex)
[No fault codes]

 

[mmi]

Carista output before and after. I note that the 'before' does not include a "Software version:". Maybe update to Carista OBD2 v5.4 added this detail?

Engine
Part #: 04L906056KG
Component: R4 2.0l TDI
Coding: 00254014432401090000 (hex)
Fault codes:
31103 Manufacturer-specific code

Engine
Part #: 04L906056KG
Component: R4 2.0l TDI
Software version: 6168
ASAM/ODX identifier: EV_ECM20TDI03004L906056KG
Coding: 00254014432401090000 (hex)
[No fault codes]

Thank you for sharing, really appreciated! Yes, indeed early versions of Carista didn't report the version.

The reason (one of them) why I'm snooping around Forum is that sometimes the update hasn't been a "descendant" of the initial software. Although it was the case with yours "04L906056KG" - most likely the initial version was 04L906056KG 3771 - now 6168. These are easy to track.

However, @Loz got a different kind of package - the logic is unknown to me, thus I've been "collecting" data

04L 906 056 KP 3807 before update​

04L 906 056 AF 6207 after update​

Initial scan: https://www.t6forum.com/threads/high-beam-assistant-retrofit-coding-help.14603/post-203449
After update: https://www.t6forum.com/threads/adblue-software-update-from-dealership.14129/post-209524

Another interesting series of updates found on an early T6 (EU6 AdBlue engine) built in Nov-2015:

​

 

[mmi]

Out of warranty software updates are normally being charged by VW stealers unless it is Recall or Service Campaign.

A future T6Forum service perhaps then?

 

[Robert]

Thank you for sharing, really appreciated! Yes, indeed early versions of Carista didn't report the version.

The reason (one of them) why I'm snooping around Forum is that sometimes the update hasn't been a "descendant" of the initial software. Although it was the case with yours "04L906056KG" - most likely the initial version was 04L906056KG 3771 - now 6168. These are easy to track.

However, @Loz got a different kind of package - the logic is unknown to me, thus I've been "collecting" data

04L 906 056 KP 3807 before update​

04L 906 056 AF 6207 after update​

Initial scan: https://www.t6forum.com/threads/high-beam-assistant-retrofit-coding-help.14603/post-203449
After update: https://www.t6forum.com/threads/adblue-software-update-from-dealership.14129/post-209524

Another interesting series of updates found on an early T6 (EU6 AdBlue engine) built in Nov-2015:

View attachment 99492​

Slightly off topic.
Have you got any notes about 04L 906 056 KH (H02 3805) ?
Just curious, I am not looking for anything special/specific.

 

[n10n]

Hi,

Just to contribute another data point, AF 6207 after update here as well. Don’t know what it was before, updated before my time.

Date: 2020-08-01 10:45

VIN: WV2ZZZ7HZJHXXXXXX
Car: Volkswagen Caravelle
Year: 2018
Body type: VAN
Engine: CXEB 150 kW (204 HP) 2.0 l
Mileage: 33540 KM

---------------------------------------------------------------
01 Engine

System description: R4 2.0l BTD
Software number: 04L906056AF
Software version: 6207
Hardware number: 04L907445A
Hardware version: H03
ODX name: EV_ECM20BTD03004L906056AF
ODX version: 004007
Long coding: 0025401CC33601080000

Trouble codes:
No trouble codes found