> For the complete documentation index, see [llms.txt](https://docs.irs.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f3projectwizard/signalsdefinition.md).

# Signals Definition

{% hint style="info" %}
A **signal** is an analog output of your device under test or any other DUT related data you want to evaluate through a limit test (for example a CAN message).
{% endhint %}

![Signals](https://1704635928-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH5etzy4TvPRLxLRNfHlb%2Fuploads%2Fgit-blob-652a5ee2158c4af0bd9667b2e966b8b7049b0701%2FDLG_PW_Signals.png?alt=media)

To **add a signal** simply click on an empty row in the grid and type a name. Description is optional.

To **delete a signal** select a row and press the DEL key on your keyboard.

You assign a signal to one more **DUT types** (which you have defined previously). By default, each created signal is assigned to all available DUT Types. In most cases this common but it may happen, that one variant of your DUT has less/different analog outputs than another one.

Usually you want to evaluate all analog DUT outputs which are defined in the [MesSy configuration file](/ltt/documentation/ltt-gui-manual/configuration/messyconfiguration.md). Therefore you can import the signals defined there.

[go to initial setup guide](/ltt/documentation/ltt-gui-manual/gettingstarted/initial-setup-guide.md#SETUP_GUIDE)


---

# 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.irs.systems/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f3projectwizard/signalsdefinition.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.