> 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-main-menus/main-menu-spy-networks/diagnostics/diagnostics-view.md).

# Diagnostics View

Diagnostic jobs are launched using the Diagnostics screen (Figure 1) in Vehicle Spy. This screen is found under **Spy Networks> Diagnostics**.\
\
Use the **+ button** in the upper left \*\*\*\* to add jobs from the specified diagnostic service. You can remove a job by selecting the - button from the same area.\
\
Jobs will be listed under the **Name** field on the left (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)). To launch a job, click the gray button just right of its name (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)). The job **Status** column (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)) will tell you if the job is running or complete.\
\
The response data appears in three locations in different formats. The simplest two are found in the **Results** area (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFour.gif)).\
\
The default view is the **Results** tab which gives the information in a simple text based format. Each line can be expanded to show more details by clicking the **+** in front of the text.\
\
Clicking on the **Signals** tab will display the response data in a table format. The table includes information like number of negative responses, success, time the service took to run, and the decoded signals that were returned.\
\
The other place to see the response data is in the **Message History** area (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smFive.gif)). This shows a small message history filtered for diagnostic messages. The acquired data can be saved using the **Save** button (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSix.gif)).\
\
**Tree** and **List** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smSeven.gif)), give two different ways to sort diagnostic jobs. **List** shows all the diagnostic jobs in a list, while **Tree** groups ECUs and jobs.

![Figure 1: The Diagnostics screen is used to launch jobs and view their results.](https://content.gitbook.com/content/l4AHCa3zNeJQNFBrgCqy/blobs/YY4WodCepXSu1JeszsvG/spydiagnosticsjoblauncher.gif)

**\*Note:** Signals acquired from diagnostic jobs can be used throughout Vehicle Spy just like any other signal. In the [Expression Builder](/vspy-3-documentation/3.9.16/shared-features-in-vehicle-spy/shared-features-expression-builder.md), diagnostic signals are saved under Jobs.


---

# 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-main-menus/main-menu-spy-networks/diagnostics/diagnostics-view.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.