> 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-request-and-save-dtc-data/part-1-create-a-diagnostic-job.md).

# Part 1 - Create a Diagnostic Job

Part 1 will begin by making a diagnostic job to request trouble codes.

### 1. Logon to Vehicle Spy:

After Vehicle Spy is opened and a logon name is selected, use the main menu bar to select **File > New**. For this tutorial the logon name is more important than usual. The data collected will be saved in the selected users data directory.

### 2. Create a Request DTC Job:

The next step is to create the diagnostic job to read DTCs. Open the Diagnostics screen using **Vehicle Networks> Diagnostics**. The screen should default open on the **Setup** tab. To add a job, use the **+ button** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) and select **GMLAN > $A9 Check Codes** job from the pull down. (This example will work with any diagnostic service.)

### 3. Verify Settings and Edit the Description:

For the purpose of this example the default settings will work. The diagnostic job will request DTCs from all functioning ECUs on the High Speed CAN network of a GMLAN vehicle. Change the **Job Description** (Figure 1:![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) to **Request DTCs from all nodes**. The setup should look like **Figure 1** below.

![Figure 1: Setup for a diagnostic job to request all trouble codes on HS CAN.](https://content.gitbook.com/content/ZqysKgxMTlY1CiNX5qrT/blobs/ss0UXhVIfTfcfE828mWQ/spyexampledtc1.gif)


---

# 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-request-and-save-dtc-data/part-1-create-a-diagnostic-job.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.