Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Troubleshooting Modbus RTU Communication Failures

Diagnosing Common Modbus RTU Connection and Communication Issues

Modbus RTU communication issues can occur even when baud rate, parity, wiring, and other serial communication settings appear to be configured correctly.

Common symptoms include:

  • No response to Modbus RTU commands
  • Communication that stops after extended polling
  • Unexpected bytes or response data, such as 0xFC
  • Responses that do not match the documented Modbus behavior
  • Communication failures despite confirmed baud rate and parity settings

            Use the following steps to identify whether the issue is related to serial communication settings, the physical connection, the Modbus request, or device-specific Modbus behavior.

            You can also refer to the Setting Up Modbus on the Vista Touch Series article for additional guidance.

            1. Verify Communication Settings

            Confirm that the Modbus master and Trumeter device are configured with matching serial communication settings.

            Verify:

            • Baud rate
            • Parity
            • Data bits
            • Stop bits
            • Modbus slave address

                      A mismatch in any of these settings can prevent the device from responding correctly.

                      2. Verify the RS485 Connection

                      Inspect the physical RS485 connection before troubleshooting the Modbus commands.

                      Verify:

                      • RS485 A and B connections are correctly wired.
                      • Connections are secure.
                      • The correct device terminals are being used.
                      • Cable length and routing are appropriate for the installation.
                      • Termination and biasing are appropriate for the RS485 network.

                                If multiple devices are connected to the network, isolate the Trumeter device, when possible, to determine whether another device or network condition is affecting communication.

                                3. Test With a Known-Good Modbus Tool

                                Use a Modbus testing application such as Modbus Poll or Simply Modbus to send a basic request directly to the device.

                                Start with a single request rather than continuous polling.

                                Verify:

                                • Slave address
                                • Function code
                                • Register address
                                • Register quantity
                                • Expected data type

                                          If available, capture the transmitted request and device response for comparison.

                                          4. Check the Modbus Request

                                          Confirm that the requested function code and register are supported by the device.

                                          If the device does not respond, returns unexpected data, or returns bytes such as 0xFC, record the complete request and response rather than evaluating the unexpected byte independently.

                                          The complete Modbus frame provides more information for determining whether the response represents valid data, an exception, or unexpected device behavior.

                                          5. Test Communication Without Continuous Polling

                                          If communication initially works but fails after extended polling, stop continuous polling and restart communication using individual requests.

                                          Then gradually increase the polling frequency.

                                          Record:

                                          • Polling interval
                                          • Function code
                                          • Registers being requested
                                          • Number of devices on the network
                                          • Approximate time before communication stops

                                                    This information can help identify communication behavior associated with sustained or repeated requests.

                                                    6. Compare Actual Behavior with the Modbus Documentation

                                                    If the serial settings, wiring, and Modbus request have been verified but the device still behaves differently from the published documentation, the issue may be related to the device-specific Modbus implementation or its documentation.

                                                    Contact Trumeter Technical Support

                                                    If the issue continues after completing these steps, contact Trumeter Technical Support. 

                                                    Include the following information:

                                                    • Trumeter product and model number
                                                    • Firmware version, if available
                                                    • Baud rate and parity settings
                                                    • Modbus slave address
                                                    • Function code and register being accessed
                                                    • Complete Modbus request and response frames
                                                    • Polling interval
                                                    • Modbus software or hardware used for testing
                                                    • Description of the expected b

                                                                        Providing a communication capture or oscilloscope/logic analyzer trace, when available, can help Technical Support identify the cause more quickly.