# F5 Limit Configuration

In this dialog you can define limits for the signals you have defined in [project wizard](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f3projectwizard/signalsdefinition.md).

{% hint style="info" %}
You have to go through the project wizard first, before you can configure limits.
{% endhint %}

Here are some quick facts:

* There are separate limit definitions for each [DUT type](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f3projectwizard/duttypesconfiguration.md).
* A signal can have multiple limits.
* Each limit has an unique numeric identifier (the error number) and a name.
* **The error number must be unique within the same DUT type.**
* The limit name must be unique within the same signal.
* It is possible to define numeric and string limits.

When you open the F5 dialog, you see near the top of the dialog a tab for each DUT type you have defined in [project wizard](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f3projectwizard/duttypesconfiguration.md). In each tab, the signals you have defined in [project wizard](/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f3projectwizard/signalsdefinition.md) are listed. If you expand those signals (small down arrow), you will see the limits defined for each signal. In case you have a newly setup LTT there are no limits yet.

![F5 Empty](/files/8cTK64cLsVZJpeKGq4ST)

To define a limit, simply click in an empty row below an expanded signal. You have to provide a **unique error number** and a **unique limit name**. You have to check by yourself which error number is unused, but the dialog will not allow you to apply any changes if there are duplicate error numbers or limit names.

{% hint style="info" %}
A limit error number must be unique within the same DUT type. A limit name must be unique within the same signal. You are responsible!
{% endhint %}

The preset limit name is **default**, but you can change it to whatever you want. The idea is, to provide multiple limits for the same signal, because the signal can be tested under different circumstances / in different contexts. For example, you have a default limit for a signal when it is not stimulated / active. That limit might be around 0 V, depending on your signal type. Then you have a limit for the case, when the signal is stimulated / active. A possible limit value could be around 12 V and the limit could be named **active**. Additionally you may want to test the signal under different stimulation levels, for example under voltage. You could create another limit name **under\_voltage** with a different limit range.

{% hint style="info" %}
There can be multiple limits per signal, depending on in how many different scenarios you want to test the signal. Read about [Limit Tests](/ltt/documentation/ltt-gui-manual/teststand/limittests.md) to learn how to select and perform a specific limit test.
{% endhint %}

![F5 Example](/files/Wrxkk3coYbF5xWU2DK6f)

{% hint style="info" %}
It is a good practice to keep **numeric gaps** between the error numbers for each signal. That way, you can later add additional limits to a signal while having a continuous numeration within that signal. A numeric gap of 10 should be sufficient for most cases.
{% endhint %}

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


---

# Agent Instructions: 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:

```
GET https://docs.irs.systems/ltt/documentation/ltt-gui-manual/lttgui/dialogs/f5limitconfiguration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.