AdBlue top-up issue (merge)
- Thread starter Cuiken
- Start date
-
- Tags
- adblue we connect
That was exactly our issues too, we’ve been going on holiday or on holiday when the lights come on and a long way from home, we simply couldn’t trust the vehicle or the dealers anymore.
Cancelled holidays to Europe this year because of it all, there’s clearly a major fault in some of these and with the evidence we amassed we finally got the result we deserved.
If it’s any help, the software updates made no difference for us, neither did replacing glow plugs or clearing the adblue systems or having VW carry out remap all under their recommendations and warranty.
I do hope you get sorted mate, it’s all really bloody stressful.
@Drew75
Any chance you could run/record the linked EGR test on your engine?
www.t6forum.com
Any chance you could run/record the linked EGR test on your engine?
[T6_measured] 01-Engine - Built-in test for EGR
So it seems - inevitable P0401. Well, visited a VW garage to be tested - the van had accumulated 30 events in ECU's memory since July 2021 (since 20 months now). Eventually managed turn on the emission light at event number 31 - thus had a priviledge to have EGR flow tested. The result -...
I’m guessing people with start checking to see if it’s been deleted or not
Please ignore the blockmap for now. Your VCDS-cable is probably an older generation - which just can't handle the current protocol.
The actual test should work though.
On the picture you need to navigate to the folder where you downloaded the setting file (the prefs.u01 is the default).
Sorry to hear that. I guess under Basic Settings it's the same limitation which prevents the VCDS-cable to create the blockmap file.
Yes, not a good sign...
Instead of running the test in Basic Settings, can you make a log as follows
VCDS >Select > Engine > Adv. Meas. Values
- tick the 5 values mentioned earlier
- select Log, Start
- start the engine
- record for 30 seconds
- stop logging, etc.
The log file should be in folder C:\Ross-Tech\VCDS\Logs\...
Thanks for the log. Nothing obvious - DPF seems to be fairly clean for the mileage.
If you take the van for a drive perhaps you could make another log with the following values ticked
Would like to see the "effectiveness" of injected AdBlue vs. NOx emissions.
Please note - for a proper log need to keep engine running at least 30 minutes (preferably start/stop turned off) because NOx sensor needs 10-15 minutes (from cold) to activate and give meaningful values.
Would expect to see something like these
www.t6forum.com
If you take the van for a drive perhaps you could make another log with the following values ticked
IDE00021 Engine RPM
IDE00075 Vehicle speed
IDE00347 Air mass: actual value:
IDE04090 Exhaust temperature bank 1
IDE07744 Particle filter: air pressure sensor 1 bank 1: raw value
IDE07757 Exhaust recirc.valve 1 bank 1: posit.feedback - Actual value
IDE09017 NOx sens.dwnstrm.SCR cat conv: NOx conc.
IDE10241 Reducing agent pump module relative press.: calculated
IDE11219 Reducing agent inj. quantity: spec. value
Would like to see the "effectiveness" of injected AdBlue vs. NOx emissions.
Please note - for a proper log need to keep engine running at least 30 minutes (preferably start/stop turned off) because NOx sensor needs 10-15 minutes (from cold) to activate and give meaningful values.
Would expect to see something like these
[T6_measured] NOx emissions, AdBlue consumption, DPF regeneration - Before and after ECU update
Introduction An update campaign for T6 EU6 diesel engines took place in 2019-20. Affected engines were on van of model years MY16-MY18, including some of MY19. For M1 class (passenger carriers, VIN WV2...) the update was an official recall. For N1 class (VIN WV1....) the update was not...
Similar threads
