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

# Troubleshooting

RX MODBUS: troubleshooting

<h2 align="center">Troubleshooting</h2>

<p align="center">Need help with your RX MODBUS? Access our FAQ below or ask your question to the assistant</p>

<p align="center"><button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask your question</button><a href="/centre-aide/assistance/assistance-en/assistance/faq.md" class="button primary">Access the FAQ</a></p>

<h4 align="center"><i class="fa-arrow-trend-up">:arrow-trend-up:</i> Frequently asked questions</h4>

<details open>

<summary><strong>What is the receiver's power consumption?</strong></summary>

Consumption is normally less than 50 mA at 12 V. During the sensor installation phase, there may be peaks of 500 mA.

To avoid any issues, please maintain 1 A at 12 V on the power terminal block.

</details>

<details>

<summary><strong>What is the maximum number of simultaneous TCP clients?</strong></summary>

The Enless receiver behaves like a server and can only accept one client at a time. Being queried by another Modbus device can disrupt Modbus communication with the current TCP client.

</details>

<details>

<summary><strong>What function codes are supported by the RX MODBUS?</strong></summary>

Below are the supported function codes for **reading** Modbus registers:&#x20;

* 01: Read coil-type registers&#x20;
* 03: Read holding-type registers
* 04: Read input-type registers&#x20;

Below are the supported function codes for **writing** in Modbus registers:

* 05: Write single Coil.
* 06: Write single register.
* 15: Write multiple coils&#x20;
* 16: Write multiple registers

</details>

<details>

<summary><strong>What does a red icon next to my sensor on the TX CONFIG page mean?</strong></summary>

The red reload badge on the server of a LoRa Easy receiver indicates that a new configuration has been set for a transmitter, but it has not yet been received by it. \
\
Why does this happen?

* Enless transmitters are bidirectional only at power-up.
* After receiving their initial configuration, they send frames but can no longer receive live changes.

How can the configuration be forced?

* Unplug then reconnect the transmitter battery so it applies the configuration as on first startup.
* Hold down the transmitter push button for 5 seconds.&#x20;

</details>


---

# 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/gateway-and-receivers/rx-modbus/troubleshooting.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.
