These codes help identify why a gateway request did not complete successfully.
The target slave did not respond before the timeout expired.
Check slave power, address, wiring, serial settings, and response time.
The slave was still sending data when the timeout occurred.
Investigate slow or incoimplete responses and consider increasing the serial slave timeout.
The received slave response was not a valid Modbus message.
Check the protocol selection, message framing, and whether the response belongs to the requested transaction.
The gateway received an incorrect data length.
Examine the response length and serial timing; consult the manual’s timeout guidance.
The slave response contained an incorrect CRC.
Check serial wiring, noise, framing, and the integrity of the data arriving from the slave.
For errors related to slow responses, make timeout changes carefully. The manual specifies that the gateway’s Slave Timeout must remain shorter than the response timeout configured in the client software.
Troubleshooting tip: Record the error code, the affected slave address, the function code, and the timing of the failed request. Repeated errors from one device often point to a device-specific wiring, configuration, or response problem.