> 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.16/vehicle-spy-tutorials/tutorial-database-setup/part-5-diagnostic-decoding.md).

# Part 5 - Diagnostic Decoding

### 1. ECU Diagnostic Database:

The last step is to add any needed diagnostic information. Diagnostic information can come from a number of sources. The ECU Diagnostic Database can be accessed from Setup -> [ECU Diagnostic Database](/vspy-3-documentation/3.9.16/vehicle-spy-main-menus/main-menu-setup/ecus-view.md).\
\
The far left will show a listing of all the ECUs brought in from your [Network Database setup](/vspy-3-documentation/3.9.16/vehicle-spy-main-menus/main-menu-setup/network-databases.md) (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)). Selecting an ECU will display information on the right.

![Figure 1: ECU Diagnostic Database](https://content.gitbook.com/content/l4AHCa3zNeJQNFBrgCqy/blobs/0vlJUUkBlzLLvH7v8euF/diagdatabase.gif)

### 2. Import:

To import diagnostic data, click on "Import" (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) and select the database type. The database types are broken in to different types: [GMLAN](/vspy-3-documentation/3.9.16/vehicle-spy-main-menus/main-menu-spy-networks/ecus-view/gmlan-ecus.md), [ISO 14229](/vspy-3-documentation/3.9.16/vehicle-spy-main-menus/main-menu-spy-networks/ecus-view/iso-14229-ecus.md), [Keyword 2000](/vspy-3-documentation/3.9.16/vehicle-spy-main-menus/main-menu-spy-networks/ecus-view/keyword-2000-ecus.md), ICS Database, or Memory information. To Import an ODX type file, select ISO14229, then ODX/PDX. Select the ODX file to load. A converter dialog will popup identifying any issues in the import, click Ok to move on.\
\
The Import dialog will pop up next. This screen is where the imported data can be mapped to the available ECU list. The ECU column (Figure 2: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) lists the ECU names present in the database that is being imported. The ECU name to link this data to is presented in the Target ECU column (Figure 2: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)). If the correct name is not automatically selected, it can be chosen from the Target ECU drop down (Figure 2: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)). Some ODX files have Diagnostic Jobs built in. Import options for diagnostic jobs is shown under Jobs Importing (Figure 2: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)). "Import jobs into current setup" enables importing diagnostic jobs. The "Merge with Existing Jobs" option will update any jobs the currently exist in the database. OK (Figure 2: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFive.gif)), will confirm and start the import.

![Figure 2: Import Options](https://content.gitbook.com/content/l4AHCa3zNeJQNFBrgCqy/blobs/BXZgMIQ3DHjCErHgrFul/ECUImportOptions.gif)

For each ECU with data to import, a Merging dialog will appear (Figure 3). This will ask how to add this new data. The options are explained below:

* Do fix-up based on item and signal name: Use of this option will use the signal names to match up new items with existing ones.
* Keep properties from old ECU: Checking this will keep old signals that are not defined by the new database.
* Do this for remaining merges: This option will repeat the above selections for the remaining ECU data to be imported.

![Figure 3: Merging Options](https://content.gitbook.com/content/l4AHCa3zNeJQNFBrgCqy/blobs/XA0EhIaRbANAwjMCJO8Z/ECUMergingOptions.gif)

### 2. Save:

The last thing to do is to save! Again, this can be done through 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.16/vehicle-spy-tutorials/tutorial-database-setup/part-5-diagnostic-decoding.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.