> 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/products/rx-http/configuration/tx-config-tab.md).

# TX CONFIG tab

The tab **TX CONFIG** is the central interface for managing your Enless Wireless sensor fleet. It allows you to declare, configure, and manage transmitters (TX) communicating with the gateway via the protocol **LoRa Easy**.

## Main actions

At the top of the interface, four quick functions allow you to manage your device list globally:

* **+ Add** : Opens the configuration window to register a new sensor.
* **Clear all** : Deletes all sensors from the list (confirmation is required before action).
* **CSV export** : Generates a CSV file containing the current configuration of all your sensors (useful for backup or reporting).
* **CSV import** : Allows you to bulk import sensors from a pre-filled file to save time on large installations.

### Add or Edit a transmitter

When adding a sensor (or modifying it), a pop-up window (modal) appears with the following settings:

<table data-header-hidden><thead><tr><th width="143.02734375"></th><th></th></tr></thead><tbody><tr><td><strong>TX Type</strong></td><td>Select the Enless sensor model (e.g.: <code>600-036 | TX PULSE</code>) compatible with LoRa Easy.</td></tr><tr><td><strong>Location</strong></td><td>Free field to identify the sensor's physical location (e.g.: <code>Technical room - ground floor</code>).</td></tr><tr><td><strong>LoRa ID</strong></td><td>Unique device identifier, available on the label attached to the sensor housing.</td></tr><tr><td><strong>Periodicity</strong></td><td>Time interval (in minutes) between each data transmission to the gateway.</td></tr></tbody></table>

In addition to the previous settings, optional settings are available via the **+** **Options** :

<table data-header-hidden><thead><tr><th width="182.5859375"></th><th></th></tr></thead><tbody><tr><td><strong>Update config</strong></td><td>If enabled, the gateway will automatically synchronize the configuration with the sensor every 24 hours.</td></tr><tr><td><strong>Specific options</strong></td><td>Depending on the selected TX type, additional parameters related to the sensor's specific features may appear.</td></tr></tbody></table>

### List of registered sensors

Once configured, the sensors appear in a summary table allowing quick tracking of the fleet:

1. **Synchronization status** : Displays the synchronization status of the sensor configuration.
2. **TX reference** : Displays the sensor type and model.
3. **Location** : Reminds you of the entered installation location.
4. **LoRa ID** : Unique product identifier.
5. **Periodicity** : Configured data transmission frequency.
6. Actions:
   * **Edit** : Opens the modal again to adjust the settings.
   * **Delete** : Permanently removes the sensor from the gateway reception list.

{% hint style="warning" %}
**Important note** : Make sure the entered LoRa ID exactly matches the one on the label to ensure data reception. In LoRa Easy mode, the gateway will only process messages from IDs declared in this list.
{% 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 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://enless.gitbook.io/centre-aide/guides-installation/documentation-en/products/rx-http/configuration/tx-config-tab.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.