> 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-20/troubleshooting.md).

# Troubleshooting

TX IO: troubleshooting

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

<p align="center">Need help with your TX IO? 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>How do I read the open/closed status of the TX IO inputs and outputs?</strong></summary>

Information about the status (open/closed) of the inputs and outputs is given in the Status Registers sheet of the Modbus Table Excel file: [Broken mention](broken://spaces/SivuVFNeBsenUAqOB2m6/pages/fff48e44be1d28cf3027835616a14a49ba5f2932)

The open/closed status of inputs Ch1 and Ch2 is indicated respectively on bits 4 and 5 of the “Status” register. (0 = open / 1 = closed).

</details>

<details>

<summary><strong>What is the minimum delay between sending two commands to the TX IO?</strong></summary>

The minimum delay between sending two commands to the TX IO is 2 seconds. If you send a second command before this 2-second delay, it will not be taken into account by the TX IO.

</details>

<details>

<summary><strong>What is the TX IO power consumption?</strong></summary>

The TX IO power consumption is normally less than 85 mA at 12 V. During the transmission of periodic message frames, there may be peaks at 130 mA.

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

</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/sensors/editor-20/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.