VCDS on VW cars - Mileage reporting seems in error?

voxmagna1 · Dec 24, 2017

Hi All, I've been using HEX CAN V2 for a few years for home diagnostics on my VW and Skoda cars. When I come across various mileage values they seem screwed up. This hasn't bothered me much because it's the fault codes and what they mean plus adaptations I use most. Last week I wanted to initiate a manual DPF regen. Looking at the DPF data after the regen, the time in seconds since last regen appeared to be correct, although I think it is the time SINCE the last regen started and inclusive of it?

But the mileage since last regen. is screwy. I get 5 digit figures like 22,500 since a regen. I started about 10 miles ago. This doesn't make sense unless it is inches or centimetres! Can somebody help me understand what these mileage figures might mean, or are they gobbledegook?

Uwe · Dec 24, 2017

Please show us a scan so we can see the control module(s) in question, and then show us actual data that you think is questionable.

This will greatly assist our ability to explain what's going going on, or to fix what's broken.

-Uwe-

voxmagna1 · Dec 25, 2017

Hi, here you go. I'm not allowed to post attachments, so here are the raw text files:
First is the advanced measurements with the DPF options selected where you can see that time since last regen I did yesterday is 2337 seconds. The car car has been stood all day and I don't know what that figure really means because shortly after doing a dpf regen. I could see the seconds counting up whilst vcds was connected. I don't know what happens either when the field overflows to show the real time which would be nearer 28,800 seconds = 8 hours. But as I said, I've never believed some of the data I get back.

I have scanned an older VW diesel with a BMM engine many times and found similar confusing mileage data reported for service intervals. If there is something common wrong in the mileage calculation algorithm and simple to fix, that would be a great result. If fields are overflowing to present wrong data or not scaling the units correctly, it would be better not to show them at all?

The particle filter kilometers since last regeneration which is in miles ( but who knows?) but very confusing is 23664 when I know it went through a regen. cycle yesterday. I would be expecting something closer to zero in that field.

This engine has a Bosch EDC17 tri-core ECU. vcds does not allow me to look at engine blocks 08 which is grayed out. It's not grayed out for an earlier EDC16 ECU I have in a VW. This caused me some confusion trying to follow the wiki for emergency dpf regen where I am using the advanced parameters section and not engine blocks.

Code:

VCDS Version: 17.8.1.0
Data version: 20171130 DS276.6
www.Ross-Tech.com


VIN: TMBMD75L5C604XXXX   License Plate: YETI
Mileage: 58175   Repair Order: Post dpf regen



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


                Address 01: Engine  (03L 906 018 BR)

16:20:53
  IDE00432   Particle filter: time since last regeneration 2337 s
  IDE00433   Particle filter: oil ash volume 0.06 l
  IDE00435   Particle filter: soot mass measured 0.73 g
  IDE00436   Particle filter: kilometers since last regeneration 23664 m
  ENG100152   ECUNAME ECM 

--------------------------------------------------------------------------------------------------------------------------------

Code:

Monday,25,December,2017,16:53:15:44280
VCDS -- Windows Based VAG/VAS Emulator Running on Windows XP x86
VCDS Version: 17.8.1.0
Data version: 20171130 DS276.6
www.Ross-Tech.com


VIN: TMBMD75L5C604XXXX   License Plate: YETI
Mileage: 93620km-58172mi   Repair Order: Full auto scan



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 5L-SK35 (7N0)
Scan: 01 03 08 09 10 15 16 17 19 22 25 42 44 46 52 56 62 69 72

VIN: TMBMD75L5C604XXXX   Mileage: 93620km-58172miles

01-Engine -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
04-Steering Angle -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
10-Park/Steer Assist -- Status: OK 0000
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
22-AWD -- Status: OK 0000
25-Immobilizer -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
46-Central Conv. -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
56-Radio -- Status: OK 0000
62-Door, Rear Left -- Status: OK 0000
69-Trailer -- Status: OK 0000
72-Door, Rear Right -- Status: OK 0000
 
-------------------------------------------------------------------------------
Address 01: Engine (J623-CFHC)       Labels:. 03L-906-018-CFF.clb
   Part No SW: 03L 906 018 BR    HW: 03L 906 018 BR
   Component: R4 2.0l TDI   H24 9977  
   Revision: 42H24---    Serial number: 00000000000000
   Coding: 00190012042700080000
   Shop #: WSC 23041 210 00000
   ASAM Dataset: EV_ECM20TDI01103L906018BR 003008
   ROD: EV_ECM20TDI01103L906018BP_003.rod
   VCID: 7BFE8718F249989EC4-802E

No fault code found.
Readiness: 0 0 0 0 1 

-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104)       Labels:. 1K0-907-379-60EC1F.clb
   Part No SW: 1K0 907 379 BJ    HW: 1K0 907 379 BJ
   Component: ESP MK60EC1   H31 0121  
   Revision: 00H31001    
   Coding: 933F400E09260102C91302EA9022808A300000
   Shop #: WSC 33361 790 00999
   VCID: 7BFE8718FA49989EC4-802E

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J255)       Labels:| 5K0-907-044.clb
   Part No SW: 3T0 907 044 BL    HW: 3T0 907 044 BL
   Component: Climatronic   H18 0506  
   Revision: 00001007    
   Coding: 0000000002
   Shop #: WSC 33361 790 00999
   ASAM Dataset: EV_Climatronic A01010
   ROD: EV_ClimaAutoBasis_SK35.rod
   VCID: 7DFA8900EC5D96AEFA-8028

No fault code found.

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels:. 1K0-937-08x-09.clb
   Part No SW: 1K0 937 086 M    HW: 1K0 937 086 M
   Component: BCM PQ35  M   110 0651  
   Revision: 00110 AC    
   Coding: 48000AB8A05BF1C040080082110001E4430000AE724D85605C8140000040
   Shop #: WSC 33361 790 00999
   VCID: 3A70421CB5F361969F-806E

   Subsystem 1 - Part No: 5L2 955 119 A  Labels: 1KX-955-119.CLB
   Component: SK356  26  0604 
   Coding: 00F7B5

   Subsystem 2 - Part No: 1K8 951 171 
   Component: DWA-Sensor 00  001 0104 

   Subsystem 3 - Part No: 1K8 951 605 B
   Component: LIN BACKUP HO  H11 9005 

No fault code found.

-------------------------------------------------------------------------------
Address 10: Park/Steer Assist (J446)       Labels:| 5J0-919-475.clb
   Part No SW: 5J0 919 475 A    HW: 5J0 919 475 A
   Component: PARKHILFE 4K  H11 0005  
   Revision: --H11---    Serial number: 32901133001955
   Coding: 118013
   Shop #: WSC 00424 210 999999
   ASAM Dataset: EV_EPHVA14SKxxx0000 001001
   ROD: EV_EPHVA14SKxxx0000_001.rod
   VCID: 336E6F389A9990DE5C-8066

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags (J234)       Labels:| 5K0-959-655.clb
   Part No SW: 5C0 959 655 B    HW: 5C0 959 655 B
   Component: AirbagVW10    013 0613  
   Serial number: 003G5RADPT98  
   Coding: 00005442
   Shop #: WSC 33361 790 00999
   ASAM Dataset: EV_AirbaVW10SMEVW360 A01014
   ROD: EV_AirbaVW10SMEVW360.rod
   VCID: 316265306085A2CE2E-8064

   Crash sensor for side airbag: driver side: 
   Subsystem 1 - Part No SW: 5K0 959 354     HW: 5K0 959 354 
   Component: S.Sens.Fahr.V  H01 ---- 
   Serial number: 3572MSME5C322666ZZZZ

   Crash sensor for side airbag: front passenger side: 
   Subsystem 2 - Part No SW: 5K0 959 354     HW: 5K0 959 354 
   Component: S.Sens.Beif.V  H01 ---- 
   Serial number: 3582MSME5D322666ZZZ.

   Crash sensor for side airbag: rear: driver side: 
   Component: S.Sens.Fahr.H  --- ---- 
   Serial number: 3512QSME623F681BZZZ0

   Crash sensor for side airbag: rear: passenger side: 
   Component: S.Sens.Beif.H  --- ---- 
   Serial number: 3522QSME46346738ZZZX

No fault code found.

-------------------------------------------------------------------------------
Address 16: Steering wheel (J527)       Labels:| 5K0-953-569.clb
   Part No SW: 5K0 953 521 BN    HW: 5K0 953 569 E
   Component: LENKS.MODUL   014 0140  
   Revision: FF010040    Serial number: 20111129200840
   Coding: 1082140000
   Shop #: WSC 33361 790 00999
   ASAM Dataset: EV_SMLSNGVOLWSXS A01004
   ROD: EV_SMLSNGVOLWS.rod
   VCID: 79F29D10F875AA8ED6-802C

   Multifunction steering wheel control module: 
   Subsystem 1 - Part No SW: 3T0 959 537     HW: 3T0 959 537   Labels: 3C8-959-537.CLB
   Component: E221__MFL-URO  H07 0012 
   Coding: 800000

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels:| 5K0-920-xxx-17.clb
   Part No SW: 5L0 920 940 K    HW: 5L0 920 940 K
   Component: KOMBI         H05 0607  
   Serial number: 00000000000000
   Coding: 420E00
   Shop #: WSC 33361 790 00999
   ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04114
   ROD: EV_Kombi_UDS_VDD_RM09_A04_VW32.rod
   VCID: 346C6C249F9797E645-8060

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533)       Labels:. 7N0-907-530-V2.clb
   Part No SW: 7N0 907 530 M    HW: 1K0 907 951 
   Component: J533  Gateway H42 1623  
   Revision:   H42       Serial number: 041211F2002495
   Coding: 356303
   Shop #: WSC 33361 790 00999
   VCID: 3A70421CB5F361969F-806E

No fault code found.

-------------------------------------------------------------------------------
Address 22: AWD        Labels: 0AY-907-554-V1.clb
   Part No SW: 0BR 907 554 C    HW: 0BR 907 554 C
   Component: Haldex 4Motion      3018  
   Coding: 0000005
   Shop #: WSC 00000 000 00000
   VCID: 458A21E00C0D1E6EE2-8010

No fault code found.

-------------------------------------------------------------------------------
Address 25: Immobilizer (J334)       Labels:| 5K0-920-xxx-25.clb
   Part No SW: 5K0 953 234     HW: 5K0 953 234 
   Component: IMMO          H05 0607  
   Serial number: 00000000000000
   Coding: 000000
   Shop #: WSC 00000 000 00000
   ASAM Dataset: EV_Immo_UDS_VDD_RM09 A03009
   ROD: EV_Immo_UDS_VDD_RM09_VW21.rod
   VCID: 6AD0B25C8DD311162F-803E

No fault code found.

-------------------------------------------------------------------------------
Address 42: Door Elect, Driver (J386)       Labels:. 7N0-959-793.clb
   Part No SW: 7N0 959 793 D    HW: 7N0 959 793 
   Component: TSG FA        H04 0400  
   Revision:             Serial number: 0000122699013 
   Coding: 011402208001231004
   Shop #: WSC 33361 790 00999
   VCID: 438E3FF8C239205ECC-8016

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist        Labels: 1K0-909-14x-GEN3.clb
   Part No: 1K0 909 144 N
   Component: EPS_ZFLS Kl. 70     3301  
   Revision: 00H22000    
   Shop #: WSC 33361 790 00999
   VCID: 356A51205CED8EEE72-8060

No fault code found.

-------------------------------------------------------------------------------
Address 52: Door Elect, Pass. (J387)       Labels:. 7N0-959-792.clb
   Part No SW: 7N0 959 792 D    HW: 7N0 959 792 
   Component: TSG BF        H04 0400  
   Revision:             Serial number: 0000122197376 
   Coding: 011400208001231004
   Shop #: WSC 33361 790 00999
   VCID: 42803AFCDD232956C7-8016

No fault code found.

-------------------------------------------------------------------------------
Address 56: Radio (J503)       Labels:. 5M0-035-1xx-56.clb
   Part No SW: 1Z0 035 156 M    HW: 1Z0 035 156 M
   Component: BOLERO        001 0008  
   Revision: -----08S    Serial number: SKZ4Z3L1147632
   Coding: 0D0004000001
   Shop #: WSC 33361 790 00999
   VCID: 3C7C4404BFC75FA68D-8068

No fault code found.

-------------------------------------------------------------------------------
Address 62: Door, Rear Left (J388)       Labels:. 7N0-959-795.clb
   Part No SW: 7N0 959 795 D    HW: 7N0 959 795 
   Component: TSG HL        H03 0400  
   Revision:             Serial number: 0000122735610 
   Coding: 010000200001531004
   Shop #: WSC 33361 790 00999
   VCID: 458A21E0CC0D1E6EE2-8010

No fault code found.

-------------------------------------------------------------------------------
Address 69: Trailer (J345)       Labels:. 1K0-907-383-V2.clb
   Part No SW: 1K0 907 383 F    HW: 1K0 907 383 F
   Component: Anhaenger     H09 0100  
   Revision: 3A001001    Serial number: 00000148613760
   Coding: 0100000100000000
   Shop #: WSC 00000 000 00000
   VCID: 30646034638FABC621-8064

No fault code found.

-------------------------------------------------------------------------------
Address 72: Door, Rear Right (J389)       Labels:. 7N0-959-795.clb
   Part No SW: 7N0 959 795 D    HW: 7N0 959 795 
   Component: TSG HR        H03 0400  
   Revision:             Serial number: 0000122735580 
   Coding: 010000200001531004
   Shop #: WSC 33361 790 00999
   VCID: 458A21E0CC0D1E6EE2-8010

No fault code found.

End-------------------------(Elapsed Time: 03:05)--------------------------

Uwe · Dec 25, 2017

IDE00436 - distance since last regen is in meters. Not sure why they the heck they use meters as the unit of measurement for that field when their text label for the field is "kilometers". It would certainly be better if that label were just "distance since last regeneration", but all of this is from VW's own data and I'm confident ODIS would show the same. Anyway, 22.5 km is about 14 miles, not for off from the 10 miles you're reporting.

IDE00432 - time since last regeneration: I would suppose this only counts time that the engine is actually running. 2337 seconds is about 39 minutes. Is this within the realm of reason for engine run-time since you started the last regen?

As for function 08 "Measuring Blocks" not being available, that's because this ECU uses the newer UDS protocol, which simply does not support the old-school Measuring Blocks.

-Uwe-

voxmagna1 · Dec 26, 2017

Thanks that is great and you cleared up something else: Time is the engine running time (in seconds). What happens in vcds if the allocated field fills up? E.g in the time (seconds running) and mileage (metres)? Does vcds use fixed field widths for numeric data or extend the numeric field size according to the data reported back or do the values roll over to zero after 9999.....? Is the units labelling which vcds reports real data coming from the car or is it added by vcds?

I have found a lot of inconsistencies with the labelling of numeric values and always assume they are wrong so I don't get confused! On some ECUs there are some labelled values that are always zero? Rather than get confused with those I assume there probably isn't any data, but it would be nice if vcds just reported an empty field. I guess vcds uses a standardized universal results templates and some values are not output, even though the field names are shown. With OBDII scanners you can scan for valid pids. They put up all possible PID values then highlight those that are active in a particular ECU.

Thanks for your help - vox

PetrolDave · Dec 26, 2017

voxmagna said:
Thanks that is great and you cleared up something else: Time is the engine running time (in seconds). What happens in vcds if the allocated field fills up? E.g in the time (seconds running) and mileage (metres)? Does vcds use fixed field widths for numeric data or extend the numeric field size according to the data reported back or do the values roll over to zero after 9999.....? Is the units labelling which vcds reports real data coming from the car or is it added by vcds?

I have found a lot of inconsistencies with the labelling of numeric values and always assume they are wrong so I don't get confused! On some ECUs there are some labelled values that are always zero? Rather than get confused with those I assume there probably isn't any data, but it would be nice if vcds just reported an empty field. I guess vcds uses a standardized universal results templates and some values are not output, even though the field names are shown. With OBDII scanners you can scan for valid pids. They put up all possible PID values then highlight those that are active in a particular ECU.

Thanks for your help - vox

VCDS can only report the values that the VAG firmware responds with - any inconsistencies are down to the software teams working for VAG.

Uwe · Dec 26, 2017

voxmagna said:
Thanks that is great and you cleared up something else: Time is the engine running time (in seconds). What happens in vcds if the allocated field fills up? E.g in the time (seconds running) and mileage (metres)? Does vcds use fixed field widths for numeric data or extend the numeric field size according to the data reported back or do the values roll over to zero after 9999.....? Is the units labelling which vcds reports real data coming from the car or is it added by vcds?

Whether and when any overflow occurs depends on how VAG deals with the raw data. Since they specified meters or seconds as the unit, I'm reasonably confident they also allocated enough bits to make overflow unlikely in an reasonable scenario.

-Uwe-

VCDS on VW cars - Mileage reporting seems in error?

voxmagna1

Verified VCDS User

Uwe

Benevolent Dictator

voxmagna1

Verified VCDS User

Uwe

Benevolent Dictator

voxmagna1

Verified VCDS User

PetrolDave

Verified VCDS User

Uwe

Benevolent Dictator