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

# D2D mode

***

In D2D mode, the TX IO communicates with Enless LoRa sensors (maximum 4) and controls its outputs according to the alarm thresholds configured on the sensors.

Here are the configuration steps to follow for this mode:

{% stepper %}
{% step %}
**Configuration of the TX IO parameters from its server**
{% endstep %}

{% step %}
**Activation and validation of the sensors**
{% endstep %}

{% step %}
**Viewing the output status**
{% endstep %}
{% endstepper %}

## **Configuration of the TX IO parameters from its server**

Access the TX IO management interface to begin the configuration.

### **Selecting D2D mode**

Select the operating mode **D2D** 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.

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

### **Declaration and configuration of sensor alarm thresholds**&#x20;

In the **CONFIG D2D**, you must declare the sensors you want to pair with the TX IO. The procedure is the same as when you declare sensors on a receiver&#x20;

{% hint style="info" %}
The alarm threshold configuration is done from the advanced options
{% endhint %}

{% hint style="info" %}
Below is the list of Enless transmitters compatible with the TX IO 600-040 in D2D mode:&#x20;

* TX T\&H AMB 600-021
* TX VOC\T\&H AMB 600-022
* TX CO2\VOC\T\&H AMB 600-023
* TX TEMPS INS 600-031&#x20;
* TX TEMP CONT 1 600-032
* TX TEMP CONT 2 600-232
* TX T\&H EXT 600-034
* TX CONTACT 600-039&#x20;
* TX 4\20 mA 600-035
  {% endhint %}

### **Relay configuration**

In the **CONFIG TX IO**, the relays can be associated with the alarm thresholds of the sensors we have just configured.&#x20;

To do this, for each relay select:&#x20;

* The**Identifier** (LoRa ID) of the configured sensor&#x20;
* The **Relay mode** : normally closed or normally open&#x20;
  * Normally closed : corresponds to a closed resting 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 resting state. When the status is 0, the relay is open. When the status is 1, the relay is closed.&#x20;
* The **alarm type** to trigger a relay.&#x20;

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

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

## **Activation and validation of the sensors**

#### From the CONFIG TX

In the **D2D CONFIG** tab of the TX IO, refresh your browser page. A validation dot should appear in front of the sensors that have been activated.

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

#### From the NETWORK

In the **STATUS** tab of the TX IO, the frames from the sensors you have just activated should come up at the configured periodicity. This tab allows you to validate the correct reception of sensor frames.

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

## **Viewing the output status**

In the **STATUS** in the Outputs section, you can see the display of the relay state ON or OFF and the number of times the state has switched since the TX IO was powered on. You can test the relay state by clicking the Toggle Relay button. The relay is activated for one second.&#x20;

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

{% hint style="info" %}
The TX IO relays are polarity-free contact type electronic MOSFET relays. 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/d2d-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.