> 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.15/vehicle-spy-tutorials/tutorial-request-and-save-dtc-data/part-3-make-a-graphical-panel.md).

# Part 3 - Make a Graphical Panel

Make requesting trouble codes easier for the user by building a graphical panel.

### 1. Open Graphical Panels:

From the main menu select **Measurement > Graphical Panels**. This is a chance to be creative! There is no real right or wrong way to make a graphical panel.

### 2. Build the Panel:

For this graphical panel, 3 tools will be selected from along the bottom of the screen and setup.\
\
The first is a **Function Block Button** to start the function block. The critical button properties to have set are:\
\
**FunctionBlock:** Check Codes and Log Them to a File\
**FBlockAction:** 0-Start\
\
This will cause the button to start the function block every time the button is clicked.\
\
Next, add an **LED** to let the user know that the code request is still in progress. Draw an LED and set the **Signal** property. Select the diagnostic job created under **Jobs** with the **Is Running** Property.\
\
Lastly, using a **Text Display** add some text to explain what the button does using the **Caption** property. **Figure 1** shows a finished example.

![Figure 1: An example of a finished graphical panel for requesting all DTCs from all ECUs on HS CAN.](https://2396693198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRJv2XDCMeZSU0VbeZlG%2Fuploads%2Fgit-blob-bfff7c981b0ccbb64182bcad18d1d53138c314dc%2Fspyexampledtc3.gif?alt=media)


---

# 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.15/vehicle-spy-tutorials/tutorial-request-and-save-dtc-data/part-3-make-a-graphical-panel.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.