Hey everyone, I am seeking assistance on finding and solving potential cause of a Modbus RTU issue, from a Micro820 PLC.
We are unable to successfully establish any Modbus RTU messages from the PLC. Any messages almost immediately fail, with error code 55, which appears to relate to a time-out of the message. We are only attempting to read, not write.
We have checked over the configuration time and time again, baud rate, parity and the rest of it, and everything is certainly matching, and the parameters all appear to be correct in CCW.
What's important to note is that the Modbus device connection works just fine when established from a MicroLogix 1400 PLC, which I assume would likely rule out any failures in the cabling or the Modbus slave device itself.
The PLC in question is more specifically a model 2080-LC20-20QWB, we are using the embedded serial port, and the program on the PLC is also handling completely unrelated Modbus TCP messages in another routine, and those Modbus connections are working perfectly fine.
Is there anybody else who has experienced similar issues to this, and is there anything else we should check or consider in order to resolve this issue?
Thanks very much in advance.
We are unable to successfully establish any Modbus RTU messages from the PLC. Any messages almost immediately fail, with error code 55, which appears to relate to a time-out of the message. We are only attempting to read, not write.
We have checked over the configuration time and time again, baud rate, parity and the rest of it, and everything is certainly matching, and the parameters all appear to be correct in CCW.
What's important to note is that the Modbus device connection works just fine when established from a MicroLogix 1400 PLC, which I assume would likely rule out any failures in the cabling or the Modbus slave device itself.
The PLC in question is more specifically a model 2080-LC20-20QWB, we are using the embedded serial port, and the program on the PLC is also handling completely unrelated Modbus TCP messages in another routine, and those Modbus connections are working perfectly fine.
Is there anybody else who has experienced similar issues to this, and is there anything else we should check or consider in order to resolve this issue?
Thanks very much in advance.