You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When having connection interruptions with the RTDE client the reconnection approach seems not to run correctly. I assume that the RTDE server shuts down the connection so it never sends any data again.
Thus, while reconnecting to the socket might be working, we don't get any data anymore. Probably, we should re-establish the connection in that case. For this, we should not allow automatic reconnections (for more than x cycles?) and instead have a reconnection mechanism with re-initialization in the RTDEClient.
Uh oh!
There was an error while loading. Please reload this page.
When having connection interruptions with the RTDE client the reconnection approach seems not to run correctly. I assume that the RTDE server shuts down the connection so it never sends any data again.
Thus, while reconnecting to the socket might be working, we don't get any data anymore. Probably, we should re-establish the connection in that case. For this, we should not allow automatic reconnections (for more than x cycles?) and instead have a reconnection mechanism with re-initialization in the RTDEClient.
This needs to be further investigated.
This is connected to UniversalRobots/Universal_Robots_ROS2_Driver#1356
The text was updated successfully, but these errors were encountered: