> 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/remote-control-mode.md).

# Remote control mode

In remote control mode, the TX IO behaves like any other Enless transmitter (sending periodic messages) while also being able to receive commands from the receiver to control its 4 relay outputs.

<div data-with-frame="true"><figure><img src="/files/bbbbef418c70c751173bac4745af8fd200f801c2" alt=""><figcaption></figcaption></figure></div>

Here are the configuration steps to follow for this mode:

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

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

{% step %}
**Validating TX IO activation**
{% endstep %}

{% step %}
**Relay control**
{% endstep %}

{% step %}
**Optional step: Displaying input/output status**
{% endstep %}
{% endstepper %}

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

The TX IO configuration is 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 grips with 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 manually adding a sensor, the following information must be entered:

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

In addition to the previous parameters, optional parameters are available via the button **+** **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 chosen TX type, additional parameters related to the sensor's specific features may appear.

Finish adding the sensor by clicking the button **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 operation 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 can be used to validate 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>beyond -112 dBm</td><td>2</td></tr></tbody></table>

{% hint style="info" %}
In case of poor RSSI, we **recommend** installing a **repeater** **signal** **.**\
**To learn more about installing the signal repeater, please visit**the RX REPEATER installation guide [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 CONFIG TX tab of the RX receiver, refresh your browser page. A validation indicator should appear in front of the TX IO you have just activated.&#x20;

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

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

#### From the NETWORK tab

In the NETWORK tab of the RX receiver, the TX IO frames you have just powered should come in at the configured periodicity. This tab lets you validate the proper reception of TX IO frames.

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

## **Relay control**

Control the relays from your BMS.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h4>From an RX MODBUS</h4></td><td>Relay control is done by writing to the <strong>registers</strong> <strong>Status</strong> of the relays in the <strong>table</strong> <strong>Modbus</strong>. For example, you can activate relay 1 by changing the value of the corresponding status register (<strong>0</strong> = <strong>OFF</strong> / <strong>1</strong> = <strong>ON</strong>).</td></tr><tr><td><h4>From an RX BACNET</h4></td><td>Relay control is done by writing to the <strong>objects</strong> <strong>Status</strong> of the relays. For example, you can activate relay 1 by changing the value of the corresponding status object (<strong>0</strong> = <strong>OFF</strong> / <strong>1</strong> = <strong>ON</strong>).</td></tr></tbody></table>

{% hint style="info" %}
Information about the open/closed status of the inputs and outputs is provided in the Status Registers sheet of the Modbus Table Excel file: [Modbus Table](https://enless.gitbook.io/centre-aide/ressources/recepteurs-lora-easy/table-modbus)

The open/closed statuses of inputs Ch1, Ch2 are indicated respectively on bits 4 and 5 of the "Status" register. (0 = open / 1 = closed).
{% endhint %}

{% hint style="danger" %}
The minimum delay between sending two commands to the TX IO is 2 seconds. If you send a second command before this 2-second delay, it will not be taken into account by the TX IO.&#x20;
{% endhint %}

## **Optional step:** a**ffichage du statut des entrées/sorties**

In the **TX IO STATUS** you can see the display of the status of the digital inputs and the counters since power-up. At the bottom of the tab, you can see the status display of the relays ON or OFF and how many times the state has switched since the TX IO was powered.&#x20;

You can test the relay state by clicking the Actuate Relay button. The relay will activate for one second.

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

{% hint style="info" %}
The TX IO relays are electronic MOSFET relays of the dry-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/remote-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.