RMS-LOG-L Modbus communication
Hello, I am hoping for some clarification of the "Connection Timeout" statement in the Modbus communication section of the RMS-LOG-L manual.
It is said that after 30 seconds of no communication the TCP connection is closed. Does this mean that if the logger can not contact the Modbus master, it will keep trying for 30 seconds, after which the connection will be closed? If this is the case, will the connection automatically re-open the next time data is due to be sent?
Thanks!
It is said that after 30 seconds of no communication the TCP connection is closed. Does this mean that if the logger can not contact the Modbus master, it will keep trying for 30 seconds, after which the connection will be closed? If this is the case, will the connection automatically re-open the next time data is due to be sent?
Thanks!
Hi Philip
Any RMS LAN device always closes the TCP connection after the last package is sent.
If an interruption of the communication occurs, the device closes the connection automatically after 30 seconds to prevent the socket from being blocked. The device is not going to retry for 30 seconds.
The connection is reopened by the Modbus master for the next request.
Any RMS LAN device always closes the TCP connection after the last package is sent.
If an interruption of the communication occurs, the device closes the connection automatically after 30 seconds to prevent the socket from being blocked. The device is not going to retry for 30 seconds.
The connection is reopened by the Modbus master for the next request.
Hi Phil,
I have checked, it is stated in the manual, but not for every single device. I will update accordingly:
https://service.rotronic.com/manual/modbus5.html
Regards,
James
I have checked, it is stated in the manual, but not for every single device. I will update accordingly:
https://service.rotronic.com/manual/modbus5.html
Regards,
James
You need to move on a moving trucks to reach the destination in cluster rush
No matching posts in this thread.
