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

Troubleshooting

Need help with your TX MODBUS? Access our FAQ below or ask the assistant your question

Access the FAQ

:arrow-trend-up: Frequently Asked Questions

What is the TX MODBUS consumption? The TX MODBUS consumption is normally less than 74 mA at 12 V. During transmission of periodic message frames, there may be peaks at 140 mA. To avoid any problem, please maintain 1A 12V on the power terminal block.
What is the delay for feedback after writing to a register of a TX MODBUS slave? If the TX MODBUS is configured for a one-minute period, it reads the slave register(s) one after the other at 1-second intervals in a loop. So if there are 10 slaves, 6 registers, it will take 60 seconds to go through them all. When you write a value in the receiver’s Modbus table, the value is immediately sent to the TX MODBUS. When the TX MODBUS receives this message, it immediately writes it to the registers, so end to end, the write will happen very quickly. However, since the TX MODBUS scans all the registers, it may take up to a minute before this register value is sent back to the receiver. During this time, if you update the register, say within 10 seconds, the latest value should reach the TX MODBUS very quickly and then the slave. But depending on which register is being scanned, again, it may take 1 minute before the value is sent to the receiver. If the TX MODBUS slaves are configured for a 5-minute period, the TX MODBUS reads the slave registers at 5-second intervals in a loop, so if there are 10 slaves, 6 registers, it will take 5 minutes to go through them all. Following the same logic as above, the feedback after writing to a slave register may take up to 5 minutes before this register value is sent back to the receiver.
What function codes are supported by the TX MODBUS? Below are the supported function codes for reading Modbus registers: * 01: Read Coil registers * 03: Read Holding registers * 04: Read Input registers Below are the supported function codes for writing to Modbus registers: * 05: Write single Coil. * 06: Write single register. * 15: Write multiple coils * 16: Write multiple registers
How do I check the reading/writing of TX MODBUS registers? The "Alarm Status" registers in the Modbus table of the TX Modbus slaves allow you to check whether the reading and writing of the slave registers have been carried out correctly. The "Alarm Status" register is coded on 16 bits, of which 6 bits are used to check whether the slave register read was successful and 6 bits are used to check whether writing to the slave registers (Holding or Coil type) was successful. **Example** : The reading and writing must be coded in the "Alarm Status" register If the value read is **3e3e** (hexadecimal). Convert this hexadecimal value to 16-bit binary: 3e3e (hex) = 00**111110** 00**111110** (binary) * **111110 :** Only the first register of the slave was successfully read. * **111110 :** Writing was successfully carried out only in the first register of the slave.
--- # 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/troubleshooting.md?ask=&goal= ``` `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.