> 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-13/activation-procedure/enless-lora-easy-receivers.md).

# Enless LoRa Easy receivers

TX PULSE ATEX: Enless LoRa Easy receivers

Let's see here how to use your TX PULSE ATEX with a receiver **LoRa Easy Enless** :

* RX MODBUS 500-302
* RX BACNET 500-322
* RX HTTP 500-322

{% 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/gateway-and-receivers/rx-modbus.md)

[RX BACNET](/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-bacnet.md)

[RX HTTP](/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-http.md)
{% endhint %}

## Register the sensor

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** : Enless sensor model selection (`600-037 | TX PULSE ATEX`) compatible with LoRa Easy.
2. **Location** : Free 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 parameters, optional settings 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 chosen TX type, additional parameters related to the sensor's specific features may appear.

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

## Make sure your sensor is in LoRa Easy mode

{% columns %}
{% column width="41.66666666666667%" %}

<figure><img src="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FCpvGzDnXqePuoWYtyDrj%2FJumper%20-%20ferme%CC%81.png?alt=media&amp;token=779e0701-1311-476e-a527-c59bc5c635e0" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="58.33333333333333%" %}
LoRaWAN mode is activated by a jumper located on the motherboard. To enable this mode, the jumper must be in the **position** **closed** (connecting the two pins), as shown opposite.

{% hint style="info" %}
The **switching** of the jumper switch is only **taken into account** when the product is **powered off**. Make sure your product is completely powered off before positioning the jumper.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

## Getting started

Only a few steps remain to get the TX PULSE ATEX up and running **:**

{% stepper %}
{% step %}

### Power supply

Power the TX PULSE ATEX by plugging in the battery Molex connector.
{% endstep %}

{% step %}

### Activation

The TX PULSE ATEX will proceed with its activation with the *of the LoRa Easy receiver* Enless; the status LED will flash <mark style="color:$success;">**green**</mark> then take on one of the following three colors for 30 seconds:

* <mark style="color:$success;">**Green**</mark> : The sensor is activated.
* <mark style="color:$warning;">**Orange**</mark> : The sensor is activated but the RSSI is low, so there is a risk of losing LoRa frames.
* <mark style="color:$danger;">**Red**</mark> : The sensor is not activated. Several possible reasons:\
  1\. Check that the jumper is correctly set to LoRa Easy mode (see above).\
  2\. Check that you have entered the sensor's LoRa ID correctly on the receiver\
  3\. The sensor is too far from the receiver.

In the **NETWORK**tab, 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>Adequate 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" %}
In case of poor RSSI, we **recommend** installing a **repeater** **of** **signal**.\
To learn more about installing the signal repeater, please visit [the RX REPEATER installation guide](/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-repeater.md).
{% endhint %}
{% endstep %}

{% step %}

### Operation

After activation, the LED flashes allow you to monitor the sensor status:

<table data-header-hidden><thead><tr><th width="134.90625"></th><th></th></tr></thead><tbody><tr><td><mark style="color:$success;"><strong>Green</strong></mark></td><td>Flash every minute</td></tr><tr><td><mark style="color:$warning;"><strong>Orange</strong></mark></td><td>Flash with each frame transmission<br>Stays steady in case of low battery</td></tr><tr><td><mark style="color:$danger;"><strong>Red</strong></mark></td><td>Flash every 1 min in case of alarm</td></tr></tbody></table>
{% endstep %}

{% step %}

### Installation

Once the TX PULSE ATEX has been properly activated on the network, all that's left is to install it on the wall:

* By fixing it to the wall (screws and anchors not supplied).
* By mounting it on the DIN rail (mounting accessory not supplied)
  {% endstep %}
  {% endstepper %}

Go to the [Usage](/centre-aide/guides-installation/documentation-en/sensors/editor-13/use.md) to learn more about the sensor's installation and features.


---

# 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-13/activation-procedure/enless-lora-easy-receivers.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.