VAG diagnostic database

The diagnostic database provides vehicle models, ECU variants, and data descriptions for the VAG module. Configuring it does not start polling the vehicle.

Install VAG Extension with its required dependencies. Open Settings → Application → Profile, select Automotive and the VAG module. The Diagnostic database block appears below the profile selection, with a Database source field.

Choose a method

Method	Requirements	Dependency after setup
Server database	Account sign-in, an active subscription, and network access	Missing data is downloaded from the server; the local cache has size and access expiry limits
Index ODIS	An existing ODIS installation with diagnostic data	The original installation must remain accessible; rebuild indexes after it changes
Independent installation	An ODIS installation folder or Postsetup supply, and space for a separate database	The source folder is no longer needed for reads after preparation completes

Indexing saves disk space by using ODIS files. Independent installation needs more space and a longer preparation, but stores its own data and speeds up subsequent reads. Preparing a database from Postsetup does not require installing ODIS itself.

Using local data without a network connection still requires a valid Protohaund license. A subscription to server data and permission to use the module are separate access requirements.

Shared local cache

Local cache size sets one limit for the server database, ODIS indexing, and independent installations. The used space and selected limit are shown alongside it; the bar shows the proportion in use. Previously loaded diagnostic descriptions are reused while they match the selected database and language. When space is needed, the application removes entries that have not been used recently and loads them again when required.

The original ODIS installation, indexes, and independent database are stored separately from this cache. The cache does not replace the original files in indexing mode or extend access to server data.

Server database

1. Sign in under Settings → Account. An active subscription is required to obtain server diagnostic data.
2. Select Server diagnostic database in Database source.
3. Wait for the project list. Refresh projects reloads the catalog available on the server.
4. Set Local cache size to suit the available disk space.

There is no need to install ODIS or download the entire database in advance: data is loaded when requested. The project list helps you check model availability; it does not mean all project data has already been downloaded.

The cache lets you reuse received data while its retention period and access permission remain valid. Missing or expired data requires a server connection. Increasing Local cache size does not turn the server database into a permanent offline installation.

If the list fails to load, check the network and account status, and sign in again if needed. A subscription message means you need to check access to server data.

Index an existing ODIS installation

1. Finish installing or updating ODIS before preparing the database.
2. Select Local diagnostic database.
3. Click the main Index existing installation… button under Database management.
4. Select an existing ODIS installation folder containing diagnostic data. If several sources are found, choose the required one in the dialog.
5. Review the detected contents and click Index. Indexing covers all compatible projects in the selected installation; individual project selection is not needed in this mode.
6. Wait for preparation to finish. Settings will show ODIS installation and the indexed project list.

Protohaund creates a search catalog and reads detailed diagnostic descriptions from the original ODIS files. Keep that installation accessible and in its original location while using it as a source.

After updating ODIS, click Update indexes. If the source folder has moved or you want to use another installation, remove the previous indexes and configure the source again. Missing source files or read errors do not switch the application to the server automatically.

Independent installation

1. Prepare an ODIS installation folder or a Postsetup supply. Wait for its download and any source data updates to finish.
2. Select Local diagnostic database.
3. Open the additional menu on the Database management button and select Independent installation…. This option is available before a local database is configured; see database management to change an existing setup.
4. Select the source folder. Protohaund detects its type and displays the available projects.
5. Find projects by brand, model, or project code. Use the checkboxes, Select all, and Clear to change the selection. Review the displayed data size and available disk space.
6. Click Install and wait for preparation to finish. Settings will show Independent diagnostic database and the installed project list.

After successful completion, the database works without the original ODIS installation or Postsetup folder. To update it or add projects, click Update diagnostic database…, select a source supply, and confirm the required projects.

Manage a local database

The additional Database management menu depends on the configured method:

• Remove indexes… removes Protohaund indexes and keeps the original ODIS files.
• Remove projects… lets you remove selected projects from an independent database.
• Remove diagnostic database… removes the entire independent database and its local files.
• Clean up unused files frees space used by unused preparation files when they are detected.

To switch from indexing to an independent installation, use Remove indexes… first, then select Independent installation…. To switch back, remove the independent database and use Index existing installation…. Use Database source to switch between server and local data.

Check the result and resolve problems

After changing the source, reload the model list and select the vehicle model or ECU variant again. Existing virtual ECUs keep their applied profiles and values.

• No Diagnostic database block: check that Automotive → VAG is selected.
• Local preparation unavailable: check that VAG Extension is installed, and restart the application if the package manager requested it.
• A project is missing: check the source supply and the projects selected for the independent database. Only compatible projects are listed; a file being present in ODIS does not guarantee support.
• Model names or translations are missing: check that the source supply is complete. Projects without vehicle names may be listed by their codes.
• Preparation failed: check the source folder, file access, and free disk space, then try again.

If the problem persists, prepare a log and issue description.