VCDS 17.8.0: Advanced Measurement Data

With the upgrade from version 15.7 to 17.8, the profile files for the advanced measurements are no longer working. The file extension *.a01 in the older version is now *.u01, and apparently has a different format.
Is there a way to transform this? I don't want to have to rewrite the entire sentence.
After installing version 17.8 and the firmware update for the interface, reading data with version 15.7 is no longer possible, as the CAN interface is no longer recognized.

Herbert.

Hi Herbert,

Please email me both an old version and a new version of the file.

Best regards, Rainer.

Hello Herbert,

In my opinion, it can't be converted. I suspect you've switched to a different car where you've tried it out, right?

The .a01 files simply indicate which extended measurement channel is selected. The .u01 files, however, not only have a different name, but also contain identifiers for UDS measurement channels that didn't exist before, and which have different names due to protocol requirements.

I would have implemented it differently; instead of using arbitrary channel numbers, I would have consistently used the English-language identifiers for the corresponding measured values and selected the respective channels by comparing the text.

But nobody listens to me, do they?

After updating to a newer firmware, older versions of VCDS that were designed for older firmware may no longer be usable.

Best regards, Rainer.

Hello Rainer,
Please don't take this personally, but perhaps you could forward this to Uwe at RossTech?
Why should I buy a Hex-V2 if...
- a 2018 Golf MJ is not fully supported (e.g., no data is available for the MSG).
- your own work
- customized profiles for extended measurement data
- the update for the KATS was due to the manufacturer (Ross-Tech) simply changing the data structure;
- Updates are not backward compatible;
- It's been years, and there are still no reasonably complete label files available for the A4 8K (which is a widely used model in the US).
Ross-Tech is gaining recognition and acclaim.
It seems like they've had enough.

Herbert.

Hi Herbert,

Quote:

Why should I buy a Hex-V2 if... - a Golf MJ 2018 is not fully supported (e.g., no data for MSG);

"Exactly, the HEX-V2 supports the 2018 Golf and newer models, while, as you can see, the HEX-USB+CAN no longer supports individual new control units. Furthermore, you can't expect a 2018 Golf to roll off the production line and be fully supported from day one by a manufacturer of a diagnostic tool that has nothing to do with VAG. "

It was kind of a bad example from you, that's exactly what HEX-V2 is for, and how many kilometers does your Golf have? If I remember correctly, it was only picked up a few days ago...

It is backward compatible with both the new firmware and older VCDS software, although this use case is likely very rare, as the newer software is generally more advanced. However, there are reasons why it is designed this way, even though it could be done differently.

I don't understand why it's so difficult to create useful "compilations" of measurement data and to store, select, and load them efficiently. Also, I don't understand exactly what's wrong with the UDS service recovery assistant; the standard version works, and the issue/need has already been discussed.

I partially agree with you, Rest. We always try to be nice and avoid saying anything that could be misinterpreted, but sometimes you simply have to make a clean break if you want to move forward. This requires competent employees, the ability to accept criticism, and, above all, teamwork.

If labels or control unit descriptions are missing, I recommend contacting Ross-Tech or me directly with Autoscan and the .pla/.plb file.
Please always (!) test the latest VCDS version beforehand, because I often receive messages that are based on very old/years-old releases.

Best regards, Rainer.

Let's approach this in a practical way.
A specific selection of extended measurement data can be saved as a *.U01 file and retrieved later. The file contains a list of IDE***** numbers, each of which is associated with a specific measurement value (Note: previously, this was a *.A01 file containing a list of numbers).
Based on initial observations, it appears that the IDE numbers are VAG-specific rather than vehicle-specific. For example, the numbers for calculated soot mass for the particulate filter are the same (IDE00434).
Now the question: Is there an almost complete list of these IDE numbers with their corresponding names or descriptions?
I'll try creating a U01 file using a simple text editor; that would be much easier than doing it in VCDS.
Suggestion for improvement for VCDS:
- Generation of a list of the measured values available in the STG (System Test Generator).
- A clean menu for creating *.U01 files (I've suggested this before).
The *.A01 files distributed with VCDS in the "Scaling" folder are obsolete.
hg
Herbert.

Okay, I'm ready. Please provide the German text you want me to translate.