> 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/vehicle-spy-main-menus/main-menu-setup/network-databases.md).

# Network Databases

Network databases can be configured using the **Setup> Network Databases** menu selection or by selecting the **Network Databases** icon ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/NetworkDatabase.gif) from the Menu Bar.

The Database Platforms view (Figure 1) is divided into two main sections. At the top, notice the **Current Platform** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)). A platform is a group of network databases. Each network database defines all messages for a given network like HSCAN, MSCAN, etc. You can create multiple platforms and quickly switch between them as needed. Two buttons sit just to the right of the **Current Platform** drop down: **Save** **Platform Changes** & **Setup Platforms** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)). The **Save Platform Changes** updates any changes you have made in the Database view. This button will flash red when changes have not been saved. **Setup Platforms** opens a dialog to add, rename, copy, or remove platforms. Shortcuts to **Save Platform Changes** ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/saveplatformchanges.gif) and **Setup Platforms** ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/setupplatforms.gif) can also be found on the Menu Bar.

Just below the **Current Platform** section is a tabbed interface. Descriptions of each tab follow below:

#### Network Databases:

On the left side of the Network Databases tab is a list of possible networks (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)). Add additional networks by selecting **Add** just above the list. **Rename** or **Remove** networks by using the buttons at the bottom of the list. When a network in the list is selected, the right half of the tab switches to setup fields for that network.

The first field is for **DBC and VS3 Databases for Network** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)). (The \*.VS3 type of database is a Vehicle Spy 3 setup file. It uses the Receive message table from another setup file as a database.) Press the **Add** button at the far right and choose the desired database type from the pop up menu. After you choose the type, a dialog will open allowing you to choose the file from its location on your computer.

The second field is for specifying a **FIBEX Database** (Field Bus Exchange) file for FlexRay (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFive.gif)). Click the **Browse** button to select the file from its location on your computer. Press **Clear** to remove the file.

The third field is for specifying a **LIN LDF Database File** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSix.gif)). Press the **View** button to open the LDF Tool to setup LIN capabilities. Use the **Create Schedule Table Function Blocks** button to create [Function Blocks](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-scripting-and-automation/function-blocks.md) to help simulate LIN nodes.

The fourth field is for selecting a **Network UEF Database Name** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSeven.gif)).

![Figure 1: Adding a VS3 database for the HSCAN network on the Network Databases tab.](/files/9XWs6LMGKdtQKbkhFqvX)

#### UEF / VSDB Support:

The **UEF / VSDB Support**tab (Figure 2) is where a Vehicle UEF Database file and/or Vehicle Spy Message database (VSDB file) can be configured. Press **Browse** to select the file. Press **Clear** to remove a file. Using **ARXML**, AUTOSAR files can be imported.

![Figure 2: Selecting a vehicle UEF database file.](/files/wBNaquQhQgGcqkSZhYL7)

#### Diagnostics:

The **Diagnostics** tab (Figure 3) is where a Vehicle Spy diagnostic database is specified. These files have a GMD extension and hold information on diagnostic parameters like DIDs, PIDs, DPIDs, CPIDs, memory addresses, etc. The diagnostic parameters can be manually created within Vehicle Spy or imported from other diagnostic database file formats like A2L, ODX, MDX, or GDX using the [ECUs view](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-setup/ecus-view.md). Information in the GMD database is used for [Snapshot](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/snapshot.md) and the [Diagnostics Setup](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/diagnostics/diagnostics-setup.md) view in Vehicle Spy. Press **Browse** to select an existing file. Press **Create New** to make a new file. Press **Clear** to remove the file.

![Figure 3: Selecting a Vehicle Spy diagnostic database.](/files/8sSE6W2NBDT7p6OaAe2N)

#### ODI Support & John Deere:

Setup tabs for other unique OEM database formats.


---

# 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/vehicle-spy-main-menus/main-menu-setup/network-databases.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.