The Volkswagen T6, a popular van known for its versatility, sometimes presents challenges when diagnosing engine readiness using VCDS (Vag-Com Diagnostic System). Specifically, certain T6 engines, including CXGB, CXHA, CXHC, CXEB, and CXEC (and likely the CXGA and CXHB variants), exhibit inconsistencies in reporting readiness status. These engines are found in both early and later versions of the T6.
Inconsistent Readiness Reporting in VCDS
Accessing engine information directly or through an Auto-Scan in VCDS often results in a “Readiness N/A” message instead of displaying the actual readiness bits. This issue contrasts with the expected behavior where individual component statuses are clearly indicated. Here’s a breakdown of the observed discrepancies:
-
Readiness Button Error: Attempting to use the dedicated readiness button within the engine module often generates an error message concerning non-compliance, failing to provide the status.
-
OBD-II Functionality: Utilizing the OBD-II Functions > Mode 1-01 Readiness path, however, successfully retrieves and displays the individual component readiness statuses.
-
Advanced Identification Issue: Under Engine > Advanced Identification/FAZIT in VCDS Info, the system reports “Readiness: No script available.”
-
Intermittent Correct Status: While rare, instances of correctly reported readiness statuses (“0000 0000”) have been observed when accessing the engine directly. Reproducing this consistently remains elusive, with “N/A” being the predominant result, especially in Auto-Scans.
Example of an error message in VCDS
T6.1 Engine Readiness: A Different Story
Interestingly, newer T6.1 models equipped with DMZA, DNAA, and DNAB engines seem to exhibit the expected readiness reporting behavior within VCDS. This suggests a potential difference in engine control module (ECM) software or communication protocols between the T6 and T6.1 generations.
A successful scan from a T6.1 engine using VCDS
Addressing the Readiness Discrepancy
While a definitive solution to the inconsistent readiness reporting in certain T6 engines remains to be confirmed, using the OBD-II Functions > Mode 1-01 Readiness path provides a reliable workaround for retrieving the necessary information. This discrepancy highlights the importance of being aware of potential variations in VCDS behavior across different Volkswagen T6 engine types and utilizing alternative diagnostic paths when encountering issues. Further investigation and potential software updates from Ross-Tech, the developers of VCDS, may provide a more permanent resolution in the future.
