> 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/configuration/moduleconfiguration.md).

# Module Configuration

{% hint style="info" %}
[Click](https://github.com/irs-systems/IRS-LTT/blob/GitBook/doc/30%20User%20Documentation/.gitbook/assets/ltt_module_config.xml) to open the module configuration file `ltt_module_config.xml`.
{% endhint %}

{% hint style="info" %}
For training or demonstration purposes you can take the default module configuration and go on with your setup.
{% endhint %}

The module configuration's main purpose is to configure the drivers for LTT standard hardware, which is:

* power supplies (for the DUT's)
* temperature sensors (for climatic chambers)
* temperature chamber contact (TCC) (digital I/O)
* uninterruptible power supply (UPS)

Each LTT hardware is configured by a `<Module name="xxx"></Module>` block. The **name attribute** determines the type of hardware and the concrete instance of it.

{% hint style="info" %}
A LTT can have multiple instances of a power supply and/or temperature sensor, but only one TCC and UPS.
{% endhint %}

The name attribute value is composed of a **predefined prefix** and an **optional index** number **starting with 1**. The index number is mandatory for those hardware modules, which are able to have more than one instance, even if only one instance is used.

| Prefix | Type of hardware                          | More than one possible? |
| ------ | ----------------------------------------- | ----------------------- |
| PS     | power supply                              | yes                     |
| TS     | temperature sensor                        | yes                     |
| TCC    | temperature chamber contact (digital I/O) | no                      |
| UPS    | uninterruptible power supply unit         | no                      |

{% hint style="info" %}
After installation there is a default module configuration, containing 2 simulated power supplies and 1 simulated temperature sensor.
{% endhint %}

Each module has at least a **path parameter**, which is mandatory and pointing to the driver file for this module. A module driver is a file with the extension **.lvlibp**. All so far existing module drivers are located at

```
50_LTT_SW\LTT TS\lib\IRS.Mod
```

The path to the module driver should be provided relative to the `50_LTT_SW\LTT TS` folder.

{% hint style="info" %}
Each module type comes with a default simulation driver. That way you can run the LTT SW without having any actual hardware.
{% endhint %}

Any other parameter a module may need is provided in form of a `<Parameter name="xxx" value="yyy"/>` block. The parameters of each possible module type are explained in the following sub chapters.


---

# 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.irs.systems/ltt/documentation/ltt-gui-manual/configuration/moduleconfiguration.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.