> 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-9/activation-procedure/enless-lorawan-gateway.md).

# Enless LoRaWAN gateway

TX TEMP CONT2: Enless LoRaWAN gateway

Let’s see here how to use your TX TEMP CONT2 with the **Enless LoRaWAN Gateway**.

{% hint style="warning" %}
If you have not yet taken control of your **LoRaWAN Gateway**, please first consult the [installation guide](/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan.md) for the LoRaWAN gateway (ref: RX LORAWAN 500-602)
{% endhint %}

## Register the sensor

Log in to the configuration interface of your **LoRaWAN Gateway** and go to the **TX CONFIG**.

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

1. **Profile** : Select the matching Enless sensor model (`600-232 | TX TEMP CONT2`). The choice of profile automatically adapts the decoding options.
2. **DEVEUI** : Unique 16-character hexadecimal identifier specific to the sensor (available on the product label and in the QR Code).
3. **APPKEY** : 32-character hexadecimal security key required for LoRaWAN pairing (available on the product label and in the QR Code).
4. **Location** : Free field allowing the sensor's physical location in the building to be identified (e.g., `Technical room - Ground floor`).
5. **Interval** : Sets the desired periodicity in minutes between two data transmissions (*uplinks*).
6. **Advanced Settings** : Depending on the chosen profile, this section unlocks specific parameters (alert thresholds, special operating mode, etc.).

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

{% hint style="info" %}
The **keys** for activating your sensors **LoRaWAN** Enless can be provided by **format** **.csv** by our service **Administration** **From** **Sales**. \
Please **contact** <mark style="color:blue;"><adv@enless.fr></mark>&#x20;
{% endhint %}

Once the sensor has been added, it should appear in the list of Enless sensors.

## Make sure your sensor is indeed in LoRaWAN 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%2Fo3sKr5yN53XflBW0fWvZ%2FJumper%20-%20ouvert.png?alt=media&amp;token=365c33b9-5f03-4107-905b-2d7d98f12800" 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 **position** **open** (not connecting the two pins), as shown opposite.

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

## Getting started

Only a few steps remain to get the TX TEMP CONT2 up and running **:**

{% stepper %}
{% step %}

### Position the sensor at its final location

It is important that you power the sensor where it will be permanently installed.\
**Why is that?** Once powered on, the sensor will lock onto a [Spreading Factor](https://enless.gitbook.io/centre-aide/assistance/assistance/utilisation-en-lorawan#quest-ce-quun-spreading-factor) suited to its distance from the gateway. If you power your sensor too close to the gateway, then move it away to install it in its final location, it may keep a low Spreading Factor, and consequently communication may no longer be established once it is moved away from the gateway. Ideally, the sensor should lock onto the correct Spreading Factor as soon as it is installed.
{% endstep %}

{% step %}

### Power supply

Power the TX TEMP CONT2 by plugging in the battery Molex connector.
{% endstep %}

{% step %}

### Activation

The TX TEMP CONT2 will proceed with its activation with the *gateway* Enless; the status LED will flash <mark style="color:$success;">**green**</mark> then turn 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 RSS is weak, so there is a risk of LoRa frame loss.
* <mark style="color:$danger;">**Red**</mark> : The sensor is not activated, it must be brought closer to the *gateway.*
  {% endstep %}

{% step %}

### Operation

After activation, the LED flashes let you monitor the sensor's 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>Flashes with each frame transmission<br>Stays fixed when the battery is low</td></tr><tr><td><mark style="color:$danger;"><strong>Red</strong></mark></td><td>Flashes every 1 min in case of alarm</td></tr></tbody></table>
{% endstep %}

{% step %}

### Installation

Once the TX TEMP CONT2 is correctly activated on the network, all that remains is to install it on the wall:

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

## Network connectivity management

TX sensors include advanced connectivity management mechanisms to guarantee the reliability and optimization of communications on the LoRaWAN network.

**Join Requests (Activation procedure)**

* **Initialization** : The sensors automatically initiate a *Join* procedure as soon as they are powered on.
* **Link check** : In nominal operation, the sensor sends a control request (LinkCheckReq) every 24 hours.
* **Maintaining the link** : To confirm the validity of the session, the sensor must receive LinkCheckAck responses from the network.
* **Automatic reactivation** : In the event of prolonged failure (if 6 *LinkCheckReq* requests remain unanswered), the sensor considers the session lost and initiates a new *Join*.

**ADR (Adaptive Data Rate)**

* **Initial configuration** : During the first *Join*, the transmitter uses SF12 and BW125 parameters by default.
* **Dynamic optimization** : The sensor retains these maximum robustness parameters as long as it does not receive a LinkADRReq command from the network server (via the gateway) instructing it to adapt its *Spreading Factor* to optimize power consumption and bandwidth.

Go to the section [Use](/centre-aide/guides-installation/documentation-en/sensors/editor-9/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-9/activation-procedure/enless-lorawan-gateway.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.