> 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-getting-fancy-with-diagnostics/part-2-write-data-by-identifier-setup.md).

# Part 2 - Write Data by Identifier Setup

### 1. Create a Write Data by Identifier Job:

Use the **+ button** to add a **ISO 14229 > $2E Write Data By Identifier** job.

### 2. Select the Identifier to Write:

The next step is to select which DID to write to. Again, the Example Identifier number will be used as an example. If connected to a vehicle or a bench use the same Identifier as setup for the Read Data by Identifier in Part 1. Select an **ECU to Physically address** (and network if not chosen from a database).

### 3. Select the Data to Write:

The last thing to setup is the link between the Write Data by Identifier and Read Data by Identifier services. Underneath the Identifier Number selection, choose how to enter the data to be written. Select **Identifier from Read Identifier** from the **Type** drop down and the **Job** drop down will appear. Find the Read Data by Identifier service to link to in the drop down list and select it. For this example there should be 2 identical services to choose from, **$22 Read Data by Identifier**, once from the ECU job, and the job created in the last step. Select either option to before you continue.

![Figure 1: Setup for a Write Data by Identifier diagnostic job that gets its data from a Read Data by Identifier job.](https://content.gitbook.com/content/l4AHCa3zNeJQNFBrgCqy/blobs/et7lO6u3i4RAkkwTWkvO/spyexamplegfwd2.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.16/vehicle-spy-tutorials/tutorial-getting-fancy-with-diagnostics/part-2-write-data-by-identifier-setup.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.