VCDS Mobile: Data logging contains bad timestamps between 4000s and 4300s; Temperatures contain unit in each line

[alexnoe]

Using HEX-NET and VCDS Mobile, I found two things:

• I logged a very long drive using VCDS Mobile, and time stamps between 4000s and 4300s are wrong (close to 2^32/1000 instead). After that, they restart. It's as if the timestamps are handled in microseconds using unsigned 32 bit integers. I haven't tried logging more than 4000s with VCDS on Windows, so I don't know if this is specific to VCDS Mobile.
• Temperature readings contain a unit in each cell ("75.6°C"). VCDS on Windows doesn't do that, and when trying to create a graph from that data, it's better to have only the numbers in each cell. Specifying the unit in the header is totally sufficient.

The following excerpt contains the CSV headers, the first few lines, and the area where the problem starts. Timestamp 4000.46 is OK, but 0.00 and 4294677.00 are not.

Marker,TIME,Group 1 - Field 0,TIME,Group 1 - Field 3,TIME,Group 6 - Field 0,TIME,Group 7 - Field 0,TIME,Group 15 - Field 1,TIME,Group 15 - Field 2,TIME,Group 41 - Field 2,TIME,Group 62 - Field 2,TIME,Group 67 - Field 0,,,,,,,
,STAMP,Engine Speed (G28),STAMP,Coolant Temperature (G62),STAMP,Vehicle Speed (actual),STAMP,Fuel Temperature (G81),STAMP,Engine Torque ,STAMP,Fuel Consumption,STAMP,Position (act.) EGR-Actuator,STAMP,Ambient Temperature,STAMP,Temperature bef. Turbo Charger,,,,,,,
,, /min,,°C,, km/h,,°C,, Nm,, l/h,, %,,°C,,°C,,,,,,,
,1.12,0,1.12,34.2°C,1.32,0.0,1.53,17.1°C,1.73,-150.0,1.73,0.00,1.94,0.0,2.14,9.0°C,0.91,138.0°C,,,,,,,
,2.55,0,2.55,34.2°C,2.76,0.0,2.96,17.1°C,3.17,-150.0,3.17,0.00,3.37,0.0,3.58,9.0°C,2.35,138.0°C,,,,,,,
,3.99,0,3.99,34.2°C,4.19,0.0,4.40,17.1°C,4.60,-150.0,4.60,0.00,4.81,0.0,5.01,9.0°C,3.78,138.0°C,,,,,,,
...
...
...
,3993.29,2058,3993.29,90.0°C,3993.49,114.0,3993.70,75.6°C,3993.92,123.0,3993.92,6.30,3994.11,17.4,3994.31,16.2°C,3993.08,480.0°C,,,,,,,
,3994.72,2058,3994.72,90.0°C,3994.93,114.0,3995.13,75.6°C,3995.34,123.0,3995.34,6.30,3995.54,16.0,3995.75,16.2°C,3994.52,474.0°C,,,,,,,
,3996.16,2058,3996.16,90.0°C,3996.36,114.0,3996.57,75.6°C,3996.77,117.0,3996.77,6.09,3996.98,18.4,3997.18,16.2°C,3995.95,474.0°C,,,,,,,
,3997.59,2058,3997.59,90.0°C,3997.80,114.0,3998.00,75.6°C,3998.21,114.0,3998.21,5.88,3998.41,18.4,3998.62,16.2°C,3997.39,468.0°C,,,,,,,
,3999.03,2058,3999.03,90.9°C,3999.23,114.0,3999.44,75.6°C,3999.64,108.0,3999.64,5.67,3999.85,20.3,4000.05,16.2°C,3998.82,468.0°C,,,,,,,
,4000.46,2058,4000.46,90.9°C,4000.67,114.0,4000.88,75.6°C,4001.08,102.0,4001.08,5.04,4001.28,23.7,4001.49,15.3°C,4000.26,462.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,96.0,0.00,4.83,0.00,22.3,0.00,15.3°C,0.00,450.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,99.0,0.00,4.83,0.00,19.4,0.00,15.3°C,0.00,444.0°C,,,,,,,
,4294677.00,2058,4294677.00,90.9°C,4294677.00,114.0,4294677.50,75.6°C,4294678.00,96.0,4294678.00,4.83,4294678.00,21.8,4294678.00,15.3°C,4294677.00,438.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,90.0,0.00,4.20,0.00,24.2,0.00,15.3°C,0.00,438.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,96.0,0.00,4.62,0.00,17.4,0.00,15.3°C,0.00,426.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,99.0,0.00,4.83,0.00,18.4,0.00,15.3°C,0.00,426.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,96.0,0.00,4.62,0.00,22.3,0.00,14.4°C,0.00,426.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,87.0,0.00,4.20,0.00,22.8,0.00,14.4°C,0.00,426.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,81.0,0.00,3.99,0.00,24.7,0.00,14.4°C,0.00,420.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,81.0,0.00,3.78,0.00,24.2,0.00,14.4°C,0.00,408.0°C,,,,,,,
,0.00,2058,0.00,90.9°C,0.00,114.0,0.00,75.6°C,0.00,78.0,0.00,3.57,0.00,23.7,0.00,14.4°C,0.00,402.0°C,,,,,,,
,4294690.00,2058,4294690.00,90.9°C,4294690.50,114.0,4294690.50,75.6°C,4294690.50,78.0,4294690.50,3.57,4294691.00,24.2,4294691.00,14.4°C,4294690.00,396.0°C,,,,,,,

 

[Shaun]

Interesting, thanks for the report. I'll look into it.

 

[Shaun]

There is a fix for this now on our internal alpha testing channel, if you are planning on doing more logging soon and want to test the fix, I can put your interface onto the alpha channel.

 

[alexnoe]

Thank you very much! Assuming this is a fix in the interface firmware, if I install an alpha version, can I revert to the preceding non-alpha version in case this alpha introduces new problems? I mean, it's called "alpha" after all...

 

[Uwe]

can I revert to the preceding non-alpha version in case this alpha introduces new problems?

No, you can't go backwards in versions. If new problems are present, we'll fix them in a newer version.

-Uwe-

 

[alexnoe]

No, you can't go backwards in versions. If new problems are present, we'll fix them in a newer version.

-Uwe-

OK, then I'll wait for a public release. Still, thanks for the offer.

 

[alexnoe]

I tested this today with FW 1.64, it looks a lot better than before

 

[Uwe]

I tested this today with FW 1.64, it looks a lot better than before

I would expect it's the updated CB, not the FW, that makes the difference.

-Uwe-