In-use Performance Tracking. What is this?

Derek99B

Member
Hi
I've got a major problem with my CXEB 2.0Biturbo. 150k miles.
Oil 600miles/ litre. DPF goes from 9gm to 30gm in 11 miles. Regen for 24 miles. then repeat. Doing 28 MPG.
I contact VW, they send me to local VW Van centre to run a oil consumption test, stage 1 costs £99
Then massive changes.
DPF goes from 9gm to 30gm in 6 miles. Regen for 11 miles. then repeat. Doing 22 MPG. = costing a fortune.
Today I check the oil dipstick just touching the oil and here are readings using VCDS, engine running tick over..
Loc. IDE00151 Oil fill level mm 48
Loc. IDE00152 Oil warning threshold mm 60
Loc. IDE07234 Status bid for valid static oil level Condition not met
Loc. IDE07235 Status bid for dynamic oil level Condition not met
Loc. ENG103875-ENG99452 In-use Performance Tracking: 16 counters-Boost Pressure Monitor Completion Condition Counts counts 4006
Loc. ENG103875-ENG103994 In-use Performance Tracking: 16 counters-Boost Pressure Monitor Conditions Encountered Counts counts 3390
Loc. ENG103875-ENG102823 In-use Performance Tracking: 16 counters-Ignition Cycle Counter counts 6749
Loc. ENG103875-ENG99234 In-use Performance Tracking: 16 counters-NMHC Catalyst Monitor Completion Condition Counts counts 330
Loc. ENG103875-ENG99167 In-use Performance Tracking: 16 counters-NMHC Catalyst Monitor Conditions Encountered Counts counts 153
Loc. ENG103875-ENG101363 In-use Performance Tracking: 16 counters-NOx Adsorber Monitor Completion Condition Counts counts 0

So does anybody know what is going on here????
The oil light should have come on ages ago, why not?
Is it locked out by some type of "In-use Performance Tracking" flag???
What are these "Condition not met" results all about???
Do I have to go back to VW Van Centre to have the flag switched off??

Thanks for all your help/
Derek
 
@mmi may be able to read so datasets for you?

HIgh oil use at high mileage is normally a sign of worn engine, bores, turbo or other passing oil that's ingested and burned ultimately ending up clogging the dpf.
 
  • Like
Reactions: mmi
@mmi may be able to read so datasets for you?

HIgh oil use at high mileage is normally a sign of worn engine, bores, turbo or other passing oil that's ingested and burned ultimately ending up clogging the dpf.
Hi
Thanks for that, I've got lots of clogging DPF issues. I really need to get in touch with someone who takes these engines apart and fixes them. VW Van Centre are talking about whole engine replacement, 13k +. I'm sure there must be a better way.
 
DPF goes from 9gm to 30gm in 6 miles. Regen for 11 miles. then repeat. Doing 22 MPG. = costing a fortune.
Most likely it's the clogged DPF which triggers the DPF regeneration - because based on measured pressure loss across the DPF ECU decides DPF needs to be cleaned. Some plots were here.

Is the 22 MPG read from dash MFD display? Or actually measured by brim-to-brim tank fill-up? The MFD reading doesn't include the extra dose of fuel used during the the DPF regeneration - it wouldn't be nice figures to observe. Some early observations/measurements about MFD reading adjustments were done here (especially picture 4).



I contact VW, they send me to local VW Van centre to run a oil consumption test, stage 1 costs £99
I'm afraid the results can be misleading as long as the engine is doing almost continuos DPF regeneration. The DPF regeneration unavoidably dilutes the oil a bit by diesel fuel thus lost oil will be "replaced" with fuel. Thus when only weighed (without a proper oil content analysis) will show just no or very little oil consumption.


I check the oil dipstick just touching the oil and here are readings using VCDS, engine running tick over..
Loc. IDE00151 Oil fill level mm 48
Loc. IDE00152 Oil warning threshold mm 60
The oil light should have come on ages ago, why not?
Do you mean actual oil light on dash? I believe it's only low oil pressure which will light it up.

Instead as soon as staus of low oil level has been established there will be a message on dash "Check oil level". I think that by opening the bonnet will restart the self-diagnostic routine of oil level so it will take some time before ECU is convinced about too low oil level (as there still is good oil pressure, thus no emergency).

And yes, oil level being below threshold (which is also dynamic value) will turn on the dash message - eventually.
Please check/post controller 17-Instruments blockmap data for status of oil level there,

An example of blockmap of engine (controller 01)

Ignition ON

VCDS > Applications > Controller Channel Map >


1706641434033.png


Tick/fill boxes as above and hit Go.

VCDS flashes screens for a moment (when finished hit "Done, Go Back") and there will be file blockmap-01-... in folder C:\Ross-Tech\VCDS\Logs\....
Perhaps you could post full blockmaps of 01-Engine, 02-Auto Trans, 17-Instruments, 18-Aux. Heat - to arouse my curiosity :geek:



What are these "Condition not met" results all about???
I'm not sure if they are actually used on this engine - never seen any change on those.


Is it locked out by some type of "In-use Performance Tracking" flag???
Those seem to be just counting how many times specific engine's self-diagnostic routines have been run.

E.g below counters for a healthy CXEB engine across a period of 3500 km's.

1712476202018.png

Obviously some of the routines do not exist on this engine.
 
Most likely it's the clogged DPF which triggers the DPF regeneration - because based on measured pressure loss across the DPF ECU decides DPF needs to be cleaned. Some plots were here.

Is the 22 MPG read from dash MFD display? Or actually measured by brim-to-brim tank fill-up? The MFD reading doesn't include the extra dose of fuel used during the the DPF regeneration - it wouldn't be nice figures to observe. Some early observations/measurements about MFD reading adjustments were done here (especially picture 4).




I'm afraid the results can be misleading as long as the engine is doing almost continuos DPF regeneration. The DPF regeneration unavoidably dilutes the oil a bit by diesel fuel thus lost oil will be "replaced" with fuel. Thus when only weighed (without a proper oil content analysis) will show just no or very little oil consumption.




Do you mean actual oil light on dash? I believe it's only low oil pressure which will light it up.

Instead as soon as staus of low oil level has been established there will be a message on dash "Check oil level". I think that by opening the bonnet will restart the self-diagnostic routine of oil level so it will take some time before ECU is convinced about too low oil level (as there still is good oil pressure, thus no emergency).

And yes, oil level being below threshold (which is also dynamic value) will turn on the dash message - eventually.
Please check/post controller 17-Instruments blockmap data for status of oil level there,

An example of blockmap of engine (controller 01)

Ignition ON

VCDS > Applications > Controller Channel Map >


1706641434033.png


Tick/fill boxes as above and hit Go.

VCDS flashes screens for a moment (when finished hit "Done, Go Back") and there will be file blockmap-01-... in folder C:\Ross-Tech\VCDS\Logs\....
Perhaps you could post full blockmaps of 01-Engine, 02-Auto Trans, 17-Instruments, 18-Aux. Heat - to arouse my curiosity :geek:




I'm not sure if they are actually used on this engine - never seen any change on those.



Those seem to be just counting how many times specific engine's self-diagnostic routines have been run.

E.g below counters for a healthy CXEB engine across a period of 3500 km's.

View attachment 235856

Obviously some of the routines do not exist on this engine.
Fuel Usage:
Fuel usage based on written log, actual bought litres and fuel guage segment pint (0 to 64). .
25/3/24 Before segment 2 150772 add 15litre guage after segment 18
28/3/24 9/150765/49 40litre
6/4/24 9/150952/47 40litre.... 187miles used approx (+/_5%) 40litres = approx 22 mpg.
I've noticed that the DPF will not regen with the fuel guage below segment 8, low fuel light on. Soot builds up and eventually causes limp mode.
Hence I try to fill before the fuel light comes on.
Oil Light:
I mean the little indicator top right MFD, and then oil warning message in status page.

Block Maps;
I'll go out and do those and add as an extra posting. I assume without the engine running, but I'll do both.
Just for interest, Attached = VAG DPF app log for past 171 km
 

Attachments

  • Vag_DPF_log240406.txt
    385.7 KB · Views: 0
Last edited:
  • Like
Reactions: mmi
Most likely it's the clogged DPF which triggers the DPF regeneration - because based on measured pressure loss across the DPF ECU decides DPF needs to be cleaned. Some plots were here.

Is the 22 MPG read from dash MFD display? Or actually measured by brim-to-brim tank fill-up? The MFD reading doesn't include the extra dose of fuel used during the the DPF regeneration - it wouldn't be nice figures to observe. Some early observations/measurements about MFD reading adjustments were done here (especially picture 4).




I'm afraid the results can be misleading as long as the engine is doing almost continuos DPF regeneration. The DPF regeneration unavoidably dilutes the oil a bit by diesel fuel thus lost oil will be "replaced" with fuel. Thus when only weighed (without a proper oil content analysis) will show just no or very little oil consumption.




Do you mean actual oil light on dash? I believe it's only low oil pressure which will light it up.

Instead as soon as staus of low oil level has been established there will be a message on dash "Check oil level". I think that by opening the bonnet will restart the self-diagnostic routine of oil level so it will take some time before ECU is convinced about too low oil level (as there still is good oil pressure, thus no emergency).

And yes, oil level being below threshold (which is also dynamic value) will turn on the dash message - eventually.
Please check/post controller 17-Instruments blockmap data for status of oil level there,

An example of blockmap of engine (controller 01)

Ignition ON

VCDS > Applications > Controller Channel Map >


1706641434033.png


Tick/fill boxes as above and hit Go.

VCDS flashes screens for a moment (when finished hit "Done, Go Back") and there will be file blockmap-01-... in folder C:\Ross-Tech\VCDS\Logs\....
Perhaps you could post full blockmaps of 01-Engine, 02-Auto Trans, 17-Instruments, 18-Aux. Heat - to arouse my curiosity :geek:




I'm not sure if they are actually used on this engine - never seen any change on those.



Those seem to be just counting how many times specific engine's self-diagnostic routines have been run.

E.g below counters for a healthy CXEB engine across a period of 3500 km's.

View attachment 235856

Obviously some of the routines do not exist on this engine.
Hi
I've tried the blockmap as you suggested and just with measured values ticked the 4 you suggested returned nothing, so I added measured values.
I also did a "Whole Vehicle".
I've attached all the results. I hope this is useful for you.
Regards Derek
 

Attachments

  • adpmap-01-04L-906-056-AE_WV2ZZZ7HZGH148115-20240408-1027.CSV
    1.4 KB · Views: 2
  • adpmap-02-0BT-300-046-A_WV2ZZZ7HZGH148115-20240408-1027.CSV
    404 bytes · Views: 1
  • adpmap-17-7E0-920-980-L_WV2ZZZ7HZGH148115-20240408-1027.CSV
    5.3 KB · Views: 1
  • adpmap-18-7E0-963-273-A_WV2ZZZ7HZGH148115-20240408-1028.CSV
    3.9 KB · Views: 1
  • blockmap-6E-7E5-919-037-F_WV2ZZZ7HZGH148115-20240408-1001.CSV
    712 bytes · Views: 1
  • blockmap-0D-7E0-959-243-D_WV2ZZZ7HZGH148115-20240408-0956.CSV
    811 bytes · Views: 1
  • blockmap-0B-7E0-819-006-M_WV2ZZZ7HZGH148115-20240408-1002.CSV
    642 bytes · Views: 1
  • blockmap-09-7E0-937-090_WV2ZZZ7HZGH148115-20240408-0955.CSV
    3.7 KB · Views: 1
  • blockmap-14-3C0-907-376-A_WV2ZZZ7HZGH148115-20240408-0957.CSV
    2.4 KB · Views: 1
  • blockmap-19-7E0-909-901_WV2ZZZ7HZGH148115-20240408-0958.CSV
    1.1 KB · Views: 1
  • blockmap-61-7E0-907-534_WV2ZZZ7HZGH148115-20240408-1000.CSV
    1.7 KB · Views: 1
  • blockmap-69-1K0-907-383-H_WV2ZZZ7HZGH148115-20240408-1000.CSV
    808 bytes · Views: 2
  • blockmap-78-7E0-959-243-D_WV2ZZZ7HZGH148115-20240408-1002.CSV
    808 bytes · Views: 1
  • blockmap-OBD_WV2ZZZ7HZGH148115-20240408-1003.CSV
    2.4 KB · Views: 3
Thank you very much for your efforts - appreciated!
I've tried the blockmap as you suggested and just with measured values ticked the 4 you suggested returned nothing,
Ahhh... on those 4 controllers the VCDS blockmap feature obviously works only with the HEX-V2 and HEX-NET cables (the current ones). The controllers are just too modern for the earlier cables.
 
Back
Top