> 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/editor-22/configuration/local-control-mode.md).

# Local control mode

In local control mode, the TX IO can be configured to synchronize the inputs with the relay outputs using a configurable delay (to ensure that the relay does not switch instantly in the event of a momentary change in input state).

Here are the configuration steps to follow for this mode:

{% stepper %}
{% step %}
**Configuring TX IO settings from its server**
{% endstep %}

{% step %}
**Viewing the status of inputs and outputs**
{% endstep %}

{% step %}
**Declaring the TX IO from the RX server**
{% endstep %}

{% step %}
**Activating the TX IO**
{% endstep %}

{% step %}
**Validating TX IO activation from the receiver server**
{% endstep %}
{% endstepper %}

## **Configuring TX IO settings from its server**

Go to the TX IO management interface to begin configuration.

### **Selecting Local Control mode**&#x20;

Select the operating mode **Local control** from the **CONFIG TX IO**. Once selected, restart your TX IO so that the mode change is taken into account using the Reboot button from the Admin tab of the TX IO server.&#x20;

{% embed url="<https://app.arcade.software/share/QT8hL3YtfvU3RYeu7PDM>" %}

### **Configuring TX IO settings from its server**&#x20;

In the **CONFIG TX IO**, configure your relays by selecting for each relay:&#x20;

* **Input** : input 1 or input 2&#x20;
* **Relay mode** : normally closed or normally open&#x20;
  * Normally closed: corresponds to a closed rest state. When the status is 0,\
    the relay is closed. When the status is 1, the relay is open.&#x20;
  * Normally open: corresponds to an open rest state. When the status is 0,\
    the relay is open. When the status is 1, the relay is closed.&#x20;
* **Delay** : 1 sec, 5 sec, 10 sec, 30 sec, 60 sec or 120 sec.&#x20;

{% embed url="<https://app.arcade.software/share/WzA86Ql8SJIwocdXVQoY>" %}

{% hint style="danger" %}
Click Save to save your configuration.
{% endhint %}

## **Viewing the status of inputs and outputs**&#x20;

In the **STATUS** you can view the status display of the digital inputs and relays, as well as the number of state changes since power-up. You can test the state of the relays by clicking the Operate Relay button.

The selected relay is activated for one second. The TX IO is now configured; you can power it off.&#x20;

{% embed url="<https://app.arcade.software/share/IymnDVemtwre75vzRZtX>" %}

## **Declaring the TX IO from the RX server**

TX IO configuration will be done from the RX receiver server with which the TX IO will communicate:

* RX MODBUS 500-302
* RX BACNET 500-312

{% hint style="warning" %}
If you have not yet gotten to know your **LoRa Easy receiver**, please first consult the corresponding installation guide.

[RX MODBUS](/centre-aide/guides-installation/documentation-en/products/rx-modbus.md)

[RX BACNET](/centre-aide/guides-installation/documentation-en/products/rx-bacnet.md)
{% endhint %}

Log in to the configuration interface of your **LoRa Easy receiver** and go to the **CONFIG TX**.

When adding a sensor manually, the following information must be entered:

1. **TX Type** : Select the Enless sensor model (e.g. `600-040 | TX IO`) compatible with LoRa Easy.
2. **Location** : Free text field to identify the physical location of the sensor (e.g. `Technical room - Ground floor`).
3. **LoRa ID** : Unique device identifier, available on the label attached to the sensor housing.
4. **Periodicity** : Time interval (in minutes) between each data transmission to the gateway.

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

1. **Update config** : If enabled, the gateway will automatically synchronize the configuration with the sensor every 24 hours.
2. **Specific options** : Depending on the selected TX type, additional parameters related to the sensor's specific features may appear.

Finish adding the sensor by clicking the **Add**.

## **Activating the TX IO**&#x20;

Once declared on the receiver server and configured, you will need to activate the TX IO to pair it with the receiver. Below are the steps to activate the TX IO:

1. Power your TX IO externally (between 7.5 and 24 VDC) or with our 12V power supply. For more information, see the page [Power supply](/centre-aide/guides-installation/documentation-en/products/editor-22/installation/power-supply.md).
2. Validate the product's proper behavior using its LEDs.

<table data-header-hidden><thead><tr><th width="110.2421875"></th><th width="146.20703125"></th><th></th></tr></thead><tbody><tr><td><mark style="color:$success;"><strong>L1</strong></mark></td><td>Always ON</td><td>Powered sensor</td></tr><tr><td><mark style="color:$danger;"><strong>L2</strong></mark></td><td>ON</td><td>Installation failed</td></tr><tr><td><mark style="color:$warning;"><strong>L3</strong></mark></td><td>ON</td><td>Installation successful but radio signal weak</td></tr><tr><td><mark style="color:$success;"><strong>L4</strong></mark></td><td>ON</td><td>Installation successful and signal good</td></tr></tbody></table>

In the **NETWORK**, the RSSI value allows validation of the signal quality with the receiver:

<table data-view="cards"><thead><tr><th></th><th></th><th data-type="rating" data-max="5"></th></tr></thead><tbody><tr><td><mark style="color:$success;"><strong>Good signal</strong></mark></td><td>Up to -105 dBm</td><td>5</td></tr><tr><td><mark style="color:$warning;"><strong>Fair signal</strong></mark></td><td>from -106 to -112 dBm</td><td>4</td></tr><tr><td><mark style="color:$danger;"><strong>Weak signal</strong></mark></td><td>below -112 dBm</td><td>2</td></tr></tbody></table>

{% hint style="info" %}
If the RSSI is poor, we **recommend** installing a **repeater** **for** **signal**.\
To learn more about installing the signal repeater, please visit [the RX REPEATER installation guide](/centre-aide/guides-installation/documentation-en/products/rx-repeater.md).
{% endhint %}

## **Validating TX IO activation**

#### From the CONFIG TX tab

In the RX receiver's CONFIG TX tab, refresh your browser page. A validation badge should appear in front of the TX IO you just activated.&#x20;

{% embed url="<https://app.arcade.software/share/rUn8IeywkXVhiMYVP65u>" %}

{% hint style="info" %}
A red badge means the configuration is being retrieved. Feel free to wait a few moments and refresh your page if the green badge does not appear.
{% endhint %}

#### From the NETWORK tab

In the RX receiver's NETWORK tab, the frames from the TX IO you just powered should come through at the configured periodicity. This tab allows you to validate proper reception of TX IO frames.

{% embed url="<https://app.arcade.software/share/bauxbNlAV5rnm00fHzyq>" %}

{% hint style="info" %}
To decode the status of the TX IO inputs from the receiver's Modbus table, please refer to [this article](https://enless-wireless.freshdesk.com/fr/support/solutions/articles/101000495014--lora-propri%C3%A9taire-statut-ouvert-ferm%C3%A9-des-entr%C3%A9es-et-sorties-du-tx-io).
{% endhint %}

{% hint style="info" %}
The TX IO relays are electronic MOSFET relays of the polarity-free contact type. The maximum voltage between the two relay terminals is 48 VDC and the maximum current is 500 mA.&#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 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/editor-22/configuration/local-control-mode.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.
