VCDS (Vag-Com Diagnostic System) offers powerful advanced measuring values functionality for in-depth vehicle diagnostics. This guide addresses common questions regarding accessing, grouping, and logging these values, specifically focusing on UDS engine modules.
Accessing Measuring Value Locations
Unfortunately, VCDS doesn’t currently offer a direct method to export a complete list of available measuring values and their locations to a text file. This makes reviewing them offline without the car and ignition on challenging. Workarounds involve taking multiple screenshots and using OCR, which is time-consuming. A feature request for this functionality would be beneficial for users working with UDS modules like the CAEB engine (06H-907-115-CAB.clb).
Understanding Measuring Value Groups in UDS Modules
The concept of “groups” for maximizing sample rates, as discussed in the Vcds Advanced Measuring Values Tour, primarily applies to older, non-UDS systems. In UDS modules, value locations often start with identifiers like “IDE” and “ENG,” but these don’t necessarily represent distinct groups in the traditional sense. They likely indicate different functional areas within the module. While selecting only “IDE” locations versus both “IDE” and “ENG” might yield a slightly higher sample rate due to reduced data volume, the difference is generally negligible in modern UDS systems.
Value Selection Limits and HEX Hardware
Using the “Group UDS” option typically limits selection to 8 values with a HEX+CAN USB interface. Upgrading to a HEX-V2 or HEX-NET interface allows utilizing the “split” functionality, potentially increasing the number of simultaneously logged values. However, the maximum split size per group often remains limited by the engine module itself. Even with splitting, the CAEB engine might still restrict each group to 8 values. While theoretically, 16 values could be logged with two split groups, the module’s inherent limitations might prevent this.
Log File Naming Conventions
VCDS log file names currently lack unique identifiers, relying solely on the number of captured values. This can make identifying specific logs difficult. Incorporating an index counter, date/time stamp, or user-defined identifier into the file name would significantly improve log management. Submitting an enhancement request to Ross-Tech, the developers of VCDS, is recommended to address this. Refer to the VCDS Logging Tour page for more information on current logging features.
Conclusion
VCDS advanced measuring values provide invaluable diagnostic insights. However, addressing the limitations regarding offline access to measuring value lists, clarifying group functionality in UDS modules, and enhancing log file naming conventions would greatly improve user experience and workflow efficiency.
