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

# Keyword 2000 ECUs

If a Keyword 2000 ECU is selected on the [ECUs](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-setup/ecus-view.md) view then the tabs after the ECU Basics tab will look like those along the top of **Figure 1**. These other tabs let you create and change diagnostic items like LIDs, IDs, and Memory Data. Just click on a tab to see all items of that type in the ECU. A shared interface is used to enter data for the different types of items. The LIDs tab in Figure 1 is an example of this interface.

![Figure 1: The setup tabs for Keyword 2000 diagnostic data items share a 3 part interface.](/files/EsepOVY0pv0czEL1dKjr)

The area on the left (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smOne.gif)) has a list for finding, selecting, and editing diagnostic items. The "**+**" and "**-**" buttons add and delete items in the list. The cut, copy, and paste buttons will cut, copy, and paste items in the list. Type in the search field above the list to quickly find items in a long list.

The upper right area (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smTwo.gif)) defines basic aspects of the item selected in the list. The first field is the item's short name used for display throughout Vehicle Spy. The second field is the item's hexadecimal identifier and varies slightly depending upon the item type. For LIDs and IDs it is a 1 byte Identifier or Parameter ID. For Memory Data it is a 2 to 4 byte Start Memory Address. The third field can have a long description to help understand what the item is or describe its data.

The lower right area (Figure 1: ![](https://cdn.intrepidcs.net/support/VehicleSpy/assets/smThree.gif)) defines signals for the diagnostic item selected in the list. Signals are defined the same way as [message signals](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-spy-networks/message-editor/message-signals.md) are defined in the Messages Editor.

### Environment Data Tab

Diagnostic Trouble Codes (DTCs) requested from a Keyword 2000 ECU can include extra environment data at the time the code was set, such as battery voltage or air temperature for example. The Environment Data tab lets you specify these extra signals that will apply to all DTCs requested from the selected ECU.

### Saving Changes

When finished making changes don't forget to click the **Save Database Changes** button located at the top of the ECUs view, above the tabs. This will store the changes into the [diagnostics database](/vspy-3-documentation/vehicle-spy-main-menus/main-menu-setup/network-databases.md) file (\*.gmd).


---

# 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/vehicle-spy-main-menus/main-menu-spy-networks/ecus-view/keyword-2000-ecus.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.