> 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-tutorials/tutorial-getting-fancy-with-diagnostics.md).

# Tutorial: Getting Fancy with Diagnostics

### Overview

This tutorial explains how some diagnostic services can work together to expand their functionality.

The scenarios that will be covered in this example are:

* Write Identifier from Read Data by Identifier
* Read Dynamic Identifier created with Dynamically Define Data Identifier

This example assumes that the previous examples have been completed and some basic knowledge of ISO 14229 Diagnostics is known. A vehicle or bench will be helpful but is not necessary. The important things to understand are the concepts presented.

Before moving to the next step, please create a platform and import the 'Getting Fancy with Diagnostics.odx' file to a new ECU. For instructions on how to do this, please see the 'Database Setup' tutorial [here](/vspy-3-documentation/vehicle-spy-tutorials/tutorial-database-setup.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intrepidcs.com/vspy-3-documentation/vehicle-spy-tutorials/tutorial-getting-fancy-with-diagnostics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.