> For the complete documentation index, see [llms.txt](https://enless.gitbook.io/centre-aide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enless.gitbook.io/centre-aide/guides-installation/documentation-en/sensors/editor-20/configuration.md).

# Configuration

TX IO: configuration

The TX IO offers integrators different control options. As a reminder, the TX IO has 2 dry-contact inputs and 4 controllable relay outputs. It can be used in 3 distinct modes, which can be configured from the embedded server in the transmitter. 

By default, the TX IO is delivered ready to use in remote control mode. 

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>First connection</strong></td><td>Configure your computers correctly to access the TX IO configuration page.</td><td><a href="/centre-aide/guides-installation/documentation-en/sensors/editor-20/configuration/first-connection.md">First connection</a></td></tr><tr><td><strong>Remote control mode</strong> </td><td>The TX IO outputs are controlled by commands from the receiver. The TX IO also reports the status of its inputs back to the receiver. In remote control mode, the TX IO behaves like any other Enless transmitter (sending periodic messages) while also having the ability to receive commands from the receiver to control its 4 relay outputs</td><td><a href="/centre-aide/guides-installation/documentation-en/sensors/editor-20/configuration/remote-control-mode.md">Remote control mode</a></td></tr><tr><td><strong>Local control mode</strong></td><td>The TX IO controls its relay outputs according to the state of its inputs. It can send reporting messages to the receiver. The TX IO can be configured to synchronize the inputs to the relay outputs with a configurable delay (to ensure that the relay does not perform an instant match in the event of a momentary change in the input state).</td><td><a href="/centre-aide/guides-installation/documentation-en/sensors/editor-20/configuration/local-control-mode.md">Local control mode</a></td></tr><tr><td><strong>D2D (Device to Device) mode</strong></td><td>The TX IO communicates with Enless LoRa sensors (4 maximum) and controls its outputs according to the alarm thresholds configured on the sensors</td><td><a href="/centre-aide/guides-installation/documentation-en/sensors/editor-20/configuration/d2d-mode.md">D2D mode</a></td></tr></tbody></table>

{% hint style="info" %}
To change the operating mode of the TX IO, please access its configuration server (same procedure as for [accessing the receiver server](/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-modbus/configuration/first-connection.md) ).&#x20;
{% endhint %}


---

# 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://enless.gitbook.io/centre-aide/guides-installation/documentation-en/sensors/editor-20/configuration.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.