VCDS in an Evidence-Driven Diagnostic Workflow

What VCDS is used for

VCDS (VAG-COM Diagnostic System, by Ross-Tech) is the specialist diagnostic tool for Volkswagen Group vehicles (Volkswagen, Audi, SEAT, Škoda). It communicates directly with the vehicle's control modules and provides:

• Auto-Scan — reads fault memory across all modules
• Control-module access — individual module diagnosis
• DTCs and freeze frames — fault detail with operating conditions
• Measuring values — live data (basic and advanced)
• Output tests / actuator tests — command components
• Coding and adaptations — module configuration

In an evidence-driven workflow, VCDS is the evidence acquisition tool. MechanIQ is the interpretation and reasoning layer that consumes VCDS output.

Scan tool vs MechanIQ — correct positioning

| Role | Owner | |---|---| | Acquire vehicle evidence (DTCs, freeze frames, live data, actuator results) | Scan tool (VCDS) | | Interpret evidence, rank hypotheses, recommend next-best test, verify repair | MechanIQ |

MechanIQ does not replace VCDS. It does not read the vehicle directly. It takes the evidence VCDS produces and applies structured diagnostic reasoning to find the next best test and confirm the root cause before any part is ordered.

Auto-Scan

The Auto-Scan reads fault memory from every control module the gateway exposes and produces a single report. Always save the full Auto-Scan before clearing anything. The report lists every module, every stored/pending code, and the freeze-frame summary — this is the baseline evidence for the whole diagnostic session.

Control-module addresses

VAG modules are addressed by channel/address. VCDS maps addresses to module names (01 Engine, 02 Auto Trans, 03 ABS, 17 Instruments, 19 Gateway, 46 Comfort, etc.). When a code appears in a non-engine module, the fault often lives there — reading only the engine module is the most common diagnostic shortcut on VAG vehicles.

DTCs and freeze-frame data

VCDS reports each DTC with its freeze frame: the operating conditions (RPM, load, coolant temperature, voltage, and the measured value that triggered the fault) captured at the moment the code set. The freeze frame is the condition you must reproduce during testing. A fault that sets only at full load, hot, cannot be reproduced idling in the bay — the freeze frame tells you so.

Measuring values / advanced measuring values

VCDS measuring-value blocks (MVBs) and advanced measuring values stream live data per module. The key diagnostic pattern is requested (soll) vs actual (ist):

• Requested vs actual boost
• Requested vs actual rail pressure
• Requested vs actual EGR position
• Requested vs actual cam phase
• Fuel-trim groups (STFT/LTFT)

Log the relevant values over a road test that reproduces the complaint. The gap between requested and actual, captured in the log, is the core performance evidence.

Requested vs actual

This pairing is the centre of VAG performance diagnostics. A growing requested-actual gap under load is the primary evidence of a performance fault (boost, fuel, EGR, cam phase). Looking only at actual values hides the disagreement the controller is reporting.

Logging

VCDS can log measuring values to a CSV while driving. A log under the complaint condition — with requested and actual columns — is far more diagnostic than a static snapshot. Import the log into MechanIQ alongside the fault memory for full context.

Module communication and gateway information

The gateway module (address 19) lists all installed modules and their communication status. "No communication" against a module points to module power/ground or the bus — not to the system the module controls. Always check the gateway installation list before assuming a module is faulty.

How to export / copy VCDS information

• Auto-Scan: Copy Results button → plain text → save as .txt
• Measuring-value log: saved as .csv
• Coding labels / adaptation channels: copy from the label screen

The plain-text Auto-Scan and the CSV log are the two evidence artefacts that import cleanly into MechanIQ.

How MechanIQ imports and interprets VCDS data

MechanIQ ingests:

1. The Auto-Scan text — all module fault memory and freeze frames
2. Measuring-value logs — requested vs actual over time
3. Freeze-frame conditions for the codes relevant to the complaint

It then structures the evidence: identifies the affected system, ranks hypotheses by the evidence, and recommends the next-best test that most changes the probability — before any part is ordered.

Common interpretation mistakes

• Reading only the engine module and missing faults in other modules
• Ignoring the freeze-frame operating conditions
• Looking at actual values without comparing to requested
• Clearing codes before saving the Auto-Scan
• Treating a single out-of-range value as the root cause without cross-parameter checks
• Condemning a module for "no communication" before checking its power and ground

Example evidence-driven workflow

1. Complaint: "Limp mode under motorway acceleration, Audi 2.0 TFSI."
2. VCDS Auto-Scan: Engine — P0299 (underboost); Gateway — all modules communicating.
3. Freeze frame: 82% load, requested boost 1.8 bar, actual 0.9 bar.
4. Measuring-value log (road test): requested rises, actual stalls at 0.9 bar; N75 duty at max.
5. MechanIQ interpretation: control trying, physical loss — boost leak or wastegate.
6. Next-best test: boost-leak test (MechanIQ recommendation).
7. Result: split intercooler hose found.
8. Repair + verify: requested vs actual within tolerance on full-load road test; no code return.

VCDS acquired the evidence; MechanIQ reasoned to the next-best test. The turbo was never replaced.

Trademark disclaimer

VCDS and Ross-Tech are trademarks of Ross-Tech, LLC. MechanIQ is not affiliated with, endorsed by, or sponsored by Ross-Tech. All references identify the tool for diagnostic purposes only. Vehicle-specific verified specification required for all tests.