> 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-23/configuration/modbus-activation-and-data.md).

# Modbus activation and data

This step follows the page [Configuration](/centre-aide/guides-installation/documentation-en/products/editor-23/configuration/configuration.md).

Here, you power the MODBUS TX, then validate that the data is reported up to the receiver's Modbus table.

### Before you begin

Check that the MODBUS TX is already declared on the receiver server with its slaves and registers.

{% hint style="info" %}
If you haven't already, start by [Configuration](/centre-aide/guides-installation/documentation-en/products/editor-23/configuration/configuration.md).
{% endhint %}

### Activate the MODBUS TX

1. Power the MODBUS TX with a voltage between `7.5` and `24 VDC`, or with the `12 V`.
2. Check the LED status.

Activation is successful if `L1` is on and `L3` or `L4` lights up.

| LED  | Expected status | Meaning                                        |
| ---- | --------------- | ---------------------------------------------- |
| `L1` | Always on       | Powered product                                |
| `L2` | On              | Installation failed                            |
| `L3` | On              | Installation successful with weak radio signal |
| `L4` | On              | Installation successful with good radio signal |

{% hint style="warning" %}
If `L2` remains on, installation failed. Check the configuration, power supply, and radio range before starting again.
{% endhint %}

### Verify activation (CONFIG TX tab)

In the **CONFIG TX**tab, refresh the page after powering on the MODBUS TX.

You should see:

* a **green dot** in front of each enabled slave
* a **red dot** only while retrieving the configuration

If the green dot does not appear right away, wait a few moments then refresh the page.

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

### Check the frames (Network tab)

In the **NETWORK**, check that the MODBUS TX frames are being reported with the configured periodicity.

This step confirms:

* that the MODBUS TX has been activated correctly
* that slave data is being reported
* usable radio level on site

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

The RSSI value makes it possible to validate 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>Acceptable 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" %}
If the RSSI is poor, 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/products/rx-repeater.md).
{% endhint %}

### Read the Modbus table (Modbus tab)

Open the **MODBUS**.

Select a slave from the list on the left. The associated registers then appear in the receiver's Modbus table.

You can use this view to:

* check the values read for each slave
* confirm register assignment
* export the table with **Export CSV**

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

For more details on this tab, see [MODBUS tab](/centre-aide/guides-installation/documentation-en/products/rx-modbus/configuration/modbus-tab.md).

### Write to the Modbus table

You can write to the registers exposed by the Modbus table for each configured slave.

{% hint style="warning" %}
Writing is only possible on registers of type `Hold` or `Coil`.
{% endhint %}

{% hint style="info" %}
Write only to registers supported by the targeted Modbus slave. Then check the effect on the equipment side.
{% endhint %}

### Checking register read/write

The "Alarm Status" registers in the Modbus table of the TX Modbus slaves can be used to verify that register reads and writes on the slaves have been performed correctly.&#x20;

The "Alarm Status" register is encoded on 16 bits, 6 of which allow you to verify that the slave registers were read successfully and 6 of which allow you to verify that writing to the slave registers (Hold or Coil type) was performed correctly, as shown in the attached "Status Registers" sheet below the Modbus table [attached](/centre-aide/ressources/ressources-en/lora-easy-receivers/modbus-table.md) :

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

**Example**: Read and write must be encoded in the "Alarm Status" register.

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

Here, the read value is 3e3e (hexadecimal). Convert this hexadecimal value to 16-bit binary:

3e3e (hex) = 00**111110** 00**111110** (binary)&#x20;

**111110:** Only the first register of the slave was read successfully.&#x20;

**111110:** Writing was successful only in the first register of the slave.&#x20;

### Next

Once activation has been validated, move on to [Checks](/centre-aide/guides-installation/documentation-en/products/editor-23/configuration/checks.md).


---

# 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-23/configuration/modbus-activation-and-data.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.