VCDS Part 1-4: How to Perform Your First Auto-Scan on a Volkswagen or Audi

If you have completed the first three articles in this VCDS series, you now understand what VCDS is, how Volkswagen and Audi electronic systems communicate, and what the main VCDS functions are used for. Now it is time to put that knowledge into practice by performing your first Auto-Scan.

An Auto-Scan gives you a broad view of the vehicle’s electronic systems before you begin detailed diagnosis. It can identify installed control modules, communication status, fault codes, controller information, coding, and software information. However, an Auto-Scan is the starting point for diagnosis, not the diagnosis itself.

What Is a VCDS Auto-Scan?

Auto-Scan is a VCDS function that systematically communicates with the control modules associated with a selected vehicle profile. Instead of opening each controller manually, VCDS checks the vehicle’s diagnostic system and builds an overall report.

Depending on the vehicle, the scan may include the engine, transmission, ABS, airbags, Central Electronics, Instruments, CAN Gateway, HVAC, Steering Assist, Infotainment, door modules, and other controllers.

This overview is especially useful when a vehicle has several warning lights or apparently unrelated problems. Because the control modules exchange information, a fault in one area can sometimes affect other modules.

Before You Start

1. Park the vehicle safely

Engage the parking brake, select the parking transmission position, and keep the vehicle stationary. If the engine must run, make sure there is adequate ventilation.

2. Check the battery

A weak or unstable battery can cause warning lights, communication errors, control-module faults, and failed diagnostic procedures. For longer sessions or procedures requiring stable voltage, use an appropriate charger or power supply according to the vehicle manufacturer’s requirements.

3. Connect the VCDS interface

Connect the compatible VCDS interface to the vehicle’s diagnostic connector, commonly located under the dashboard. Then connect the interface to the computer. Follow the appropriate procedure if using a wireless-capable interface.

4. Switch the ignition on

For most diagnostic operations, switch the ignition on without starting the engine unless the procedure specifically requires the engine to run. On push-button vehicles, use the vehicle-specific method for switching on the ignition.

Step-by-Step: How to Perform a VCDS Auto-Scan

Step 1 — Open VCDS

Start VCDS on the computer and establish communication with the connected interface.

Step 2 — Test the VCDS Interface

Before starting the Auto-Scan, verify that VCDS can communicate with the interface and the vehicle.

Follow these steps:

• Connect the VCDS interface.
  Plug the VCDS interface into the vehicle’s diagnostic connector. Then connect the interface to your computer if your interface requires a physical computer connection.
• Switch the ignition on.
  Turn the vehicle’s ignition on, but do not start the engine unless the vehicle-specific diagnostic procedure requires it.
• Open VCDS.
  Start the VCDS software on your computer and wait for the main menu to appear.
• Open the interface test function.
  From the VCDS main screen, select Options. Then select Test. The exact wording or screen appearance can vary depending on the VCDS version and interface.
• Run the test.
  Allow VCDS to test the interface connection. The software should detect the connected VCDS interface and attempt to communicate with the vehicle.
• Check the test result.
  Confirm that VCDS recognizes the interface and reports successful communication. If the test indicates that the interface is not connected or communication is unsuccessful, do not start the Auto-Scan yet.
• If the test fails, check the connection.
  First, make sure the interface is firmly connected to the vehicle’s diagnostic connector. Next, check the connection between the interface and computer. If applicable, verify the USB or wireless connection.
• Check the vehicle conditions.
  Make sure the ignition is switched on and that the vehicle battery has sufficient voltage. A low battery or incorrect ignition state can prevent reliable communication.
• Test again.
  After correcting the problem, run the Test function again. Continue only after VCDS can communicate reliably with the interface and vehicle.

Important: A failed interface test does not automatically mean that a vehicle control module has failed. Check the interface, connections, ignition state, battery condition, and software configuration before suspecting a vehicle module.

Once the interface test is successful, return to the VCDS main menu and proceed to Auto-Scan.

Step 3 — Open Auto-Scan

From the VCDS main menu, select Auto-Scan. The exact screen layout can vary with the VCDS version.

Step 4 — Select the correct vehicle profile

Choose the profile that corresponds to the vehicle being scanned. Depending on the VCDS version, this may involve vehicle platform, model, model year, engine, or chassis/platform information. Do not select a profile simply because it looks similar.

Step 5 — Start the scan

Start the Auto-Scan. VCDS will communicate with the vehicle’s control modules, identify controllers, retrieve diagnostic information, check fault memory, and move through the applicable modules.

Step 6 — Let the scan finish

Allow VCDS to complete the scan. The duration depends on the vehicle and the number of installed modules. Avoid interrupting the scan unnecessarily.

Step 7 — Review the results

Look first at the module list, communication status, and reported faults. Note which controllers responded and which, if any, could not be reached.

Step 8 — Save the original report

Save the complete Auto-Scan before clearing faults or making repairs. This original report is your baseline and can be used for troubleshooting, documentation, and before-and-after comparison.

What You Will See in an Auto-Scan

A typical report can contain module addresses, controller identification, part numbers, software information, coding, fault memory, and communication status. Common addresses include:

The exact list varies by vehicle. The address identifies the control system with which VCDS is communicating.

How to Interpret the First Scan

Do not judge the vehicle simply by counting fault codes. A healthy vehicle can still produce a report containing controller identification, software information, and coding data.

Likewise, a fault code does not automatically identify the failed component. For example, P0299 indicates an underboost condition, but further testing is needed to determine whether the cause involves boost leaks, wastegate operation, a diverter valve, sensors, the turbocharger, or another related system.

Multiple faults can also have one underlying cause. For instance, low voltage can produce several low-voltage or communication-related faults. Therefore, examine the pattern of faults and communication problems rather than replacing components based on individual codes.

Communication Faults: What to Do

If VCDS cannot communicate with a module, do not immediately conclude that the module has failed. First check the interface, ignition state, battery voltage, diagnostic connector, fuses, power, grounds, wiring, CAN network, Gateway, and configuration. If several modules are affected, network-level causes become particularly important.

The Correct Diagnostic Workflow

Use the Auto-Scan as a controlled baseline. First, scan the vehicle. Next, save the original report. Then analyze the faults and communication patterns, perform the appropriate diagnostic tests, and repair the underlying cause. Afterward, clear faults when appropriate, rescan the vehicle, and compare the new report with the original.

A practical sequence is:

Prepare → Connect → Ignition On → Test Communication → Auto-Scan → Review → Save → Diagnose → Repair → Rescan → Verify

Before-and-After Scan Method

The first scan establishes the baseline. After diagnosis and repair, perform a second Auto-Scan and compare the results. This comparison can show whether the original fault disappeared, communication was restored, the same fault returned, or related faults remain.

Common Beginner Mistakes

• Clearing fault codes before saving the original Auto-Scan.
• Replacing a component solely because a fault code mentions that component.
• Ignoring faults in other control modules.
• Treating every stored fault as a current failure.
• Ignoring communication faults.
• Changing the vehicle before establishing a diagnostic baseline.

Your First Auto-Scan: What You Should Be Able to Do

After completing this tutorial, you should be able to connect VCDS, verify communication, select the correct vehicle profile, run an Auto-Scan, recognize common control-module addresses, identify fault and communication information, and save the original report. More importantly, you should understand that the scan provides evidence for diagnosis rather than automatically telling you which part to replace.

What Comes Next — VCDS Part 1-5

In Part 1-5, we will take the Auto-Scan report you created and learn how to read it systematically. The next lesson will examine module addresses, controller identification, part numbers, software versions, coding, fault status, fault frequency, mileage, supporting information, communication problems, and missing or non-responsive modules.

Key Takeaways

• Always select the appropriate vehicle profile.
• Verify VCDS communication before scanning.
• Allow the Auto-Scan to complete.
• Save the original report before clearing faults or making changes.
• Do not assume a fault code identifies the failed component.
• Consider common causes when several modules report faults.
• Treat communication failures as symptoms that require systematic troubleshooting.
• Use a second scan to verify the result of a repair.

Related VCDS Resources

If you want to understand the concepts behind the Auto-Scan more deeply, continue with these related Akotex guides:

VCDS Part 1-2 — Understanding Volkswagen and Audi Diagnostic Architecture — Learn how CAN, LIN, UDS, the CAN Gateway, module addresses, and the OBD-II diagnostic connection work together.X

VCDS Part 1-3 — Understanding the VCDS Main Menu — Review the major VCDS functions and understand when to use Auto-Scan, Control Module, Fault Codes, Measuring Values, Basic Settings, Adaptation, Coding, and Output Tests.X

These articles provide the background needed to understand why Auto-Scan results can contain communication faults and why a fault code should not automatically be interpreted as a failed component.