> 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/other-lorawan-networks-public-or-private.md).

# Other LoRaWAN networks (public or private)

TX TEMP CONT2: other LoRaWAN networks (public or private)

Your TX TEMP CONT2 is compatible with the networks **public LoRaWAN** and **private**. In order to make full use of it, here are the items you will need.

## Declare the sensor

### Activation

Your transmitter activates via Over-The-Air (**OTAA**) only thanks to its three identification keys.

<table data-header-hidden><thead><tr><th width="142.73046875">Information</th><th>Description</th></tr></thead><tbody><tr><td><strong>DevEUI</strong></td><td>Unique identifier, 64 bits (8 bytes / 16 hexadecimal characters). Example: <code>00:18:B2:00:00:00:00:01</code></td></tr><tr><td><strong>AppEUI</strong></td><td>Global identifier designating the entity responsible for activation, 64 bits (8 bytes / 16 hexadecimal characters). Example: <code>70:B3:D5:7E:D0:00:AF:12</code></td></tr><tr><td><strong>AppKey</strong></td><td>Symmetric encryption key, 128 bits (16 bytes / 32 hexadecimal characters). Example: <code>2B7E151628AED2A6ABF7158809CF4F3C</code></td></tr></tbody></table>

{% hint style="info" %}

#### Where can I find the keys?

The LoRaWAN keys for Enless sensors are available:

* By scanning the **QR Code** sticker on the sensor
* On **the rear label** of the sensor
* On **request** from our **Administration** **From** **Sales** (<adv@enless.fr>)
  {% endhint %}

### Decoding

Enless Wireless provides various **codecs** in order to decode the *uplinks* from your transmitter but also to generate *downlinks* to send to it.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Frame decoding Excel file</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FJm3c35o45CIeSV4UjUbO%2FExcel.png?alt=media&amp;token=c7782215-6330-442b-8d15-170cd8454d89">Excel.png</a></td><td><a href="broken://pages/f44bf02fc4389641e5f5faff73e2193344545476">Broken link</a></td></tr><tr><td>JavaScript codecs</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FIZLJqJvCIfA5eQWthJw2%2FJavaScript%20logo.png?alt=media&amp;token=d2b2f7a7-dbb3-4482-adc9-2235705c5a34">JavaScript logo.png</a></td><td><a href="broken://pages/c581a725be7b564d776df6bb2e9302f89ad8c1e1">Broken link</a></td></tr><tr><td>TTN codecs</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2Fwuo7aIDanOoVbtqvmnmJ%2FTTN%20logo.png?alt=media&amp;token=9f62d382-e42a-4757-b5a2-932a8857896f">TTN logo.png</a></td><td><a href="broken://pages/d56fee85200351ad72cae7ba98497a6f68cb21af">Broken link</a></td></tr><tr><td>Chirpstack codecs</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FdRTJjmfwze4EOPD7RDqz%2FLogo%20chirpstack.png?alt=media&amp;token=70928d52-ec93-4f42-b131-0398c9031728">Logo chirpstack.png</a></td><td><a href="broken://pages/6f82256bbc5fc357f62e47af4a49d8a2d031506f">Broken link</a></td></tr><tr><td>Multitech AP Conduit BACnet codecs</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FKTmkmRqvbYRapju84C2V%2FLogo%20Multitech.png?alt=media&amp;token=e0ebe62c-5d3d-401e-b480-0c347c970d15">Logo Multitech.png</a></td><td><a href="broken://pages/73464cbfbe732fd509dcaa593b32fe03c49c5fd5">Broken link</a></td></tr></tbody></table>

## Check that 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 activate this mode, the jumper must be in the **position** **open** (not connecting the two pins), as shown opposite.

{% hint style="info" icon="circle-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 TEMP CONT2 up and running **:**

{% stepper %}
{% 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 on the LoRaWAN network; the status LED will blink and 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, there is then a risk of LoRa frame loss.
* <mark style="color:$danger;">**Red**</mark> : The sensor is not activated. Several possible factors: \
  1\. The switch was not in LoRaWAN position at the time of activation\
  2\. The DevEUI, AppEUI and AppKey keys were not entered correctly\
  3\. The LoRaWAN network does not cover the area well
  {% endstep %}

{% step %}

### Operation

After activation, the LED blinks 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 solid 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 TEMP CONT2 is correctly activated on the network, all that remains is to install it on the wall:

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

## Network connectivity management

TX sensors integrate advanced connectivity management mechanisms to ensure 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 verification** : In nominal operation, the sensor sends a control request (LinkCheckReq) every 24 hours.
* **Link maintenance** : To confirm the validity of the session, the sensor must receive LinkCheckAck responses from the network.
* **Automatic reactivation** : In case of prolonged failure (if 6 *LinkCheckReq* requests in a row go 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 settings by default.
* **Dynamic optimization** : The sensor keeps these maximum robustness settings 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 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/other-lorawan-networks-public-or-private.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.