> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/vspy-3-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-tutorials/tutorial-database-setup/part-3-adding-database-files.md).

# Part 3 - Adding Database Files

### 1. Add Database files:

The next step is to add database files for the normal mode messages on the bus. Select the network to add the database to on the left (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)). With the proper network selected, "Add..." on the right (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) can be clicked to select the type of database to load. Here you will find imports for a few different file types: \*.DBC, \*.VS3, and \*.VSDB. Other options will appear depending on the [OEM Specific Features](/vspy-3-documentation/3.9.17/vehicle-spy-main-menus/main-menu-tools/tools-options/options-spy-networks-tab.md) enabled under Tools -> Options. Selected Databases for the selected network are shown in the center of the screen (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)). The location of the database can also be verified in this part of the dialog.

![Figure 1: Adding a database file](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/LenFxsLAGqv19WQJqCxM/PlatformAddDBC.gif)

### 2. UEF and VSDB Support:

The tab for "UEF / VSDB Support" is where a UEF, VSDB, and ARXML databases can be configured (Figure 2: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)). To add a database, click on Browse (Figure 2: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) and select the proper database file. The path will be shown in the box above the Browse button. If a UEF, VSDB, or ARXML file is not available, this can be skipped.

![Figure 2: UEF and VSDB files](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/zBbvlhLwe21665v884B2/dbUefVsdbAdd.gif)

### 3. Diagnostic Database:

Diagnostic information is held in a different database. When a new platform is created, a new or blank database is created. The new database name matches the database platform name. This can be viewed in the Diagnostics tab (Figure 3).

![Figure 3: Diagnostic Database](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/ZyloWaW7O0r9AprTnv5z/dbGMDSetup.gif)

### 4. Save:

The next step is to save! Saving can be done in a few different. The simplest is the "Save Platform Changes" button (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)). This will flash with a red border to warn that things are not saved. Another way to save is to go to File -> Save Platform Changes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/3.9.17/vehicle-spy-tutorials/tutorial-database-setup/part-3-adding-database-files.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.