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
Hi,
I have a setup with two ROS 2 applications running on the same machine.
One is the main application and it is always active, while the second one gets restarted from time to time.
The main application has a ROS 2 client and will wait for a corresponding server on the second application to come up.
We are currently using a discovery timeout of 10 seconds.
We know that the second application is already up and the server has already been created when we start the discovery timeout.
This usually works, with the server being discovered almost immediately, but we are noticing sporadic situations where the server doesn't get discovered and we time out.
This is happening with ROS 2 Humble and Fast-DDS 2.6.4
Do you have suggestions on how to make this setup more robust, besides increasing the timeout?
As already mentioned, both processes are in the same machine.
We are using the same XML profile for both applications, which allows discovery only on localhost
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I have a setup with two ROS 2 applications running on the same machine.
One is the main application and it is always active, while the second one gets restarted from time to time.
The main application has a ROS 2 client and will wait for a corresponding server on the second application to come up.
We are currently using a discovery timeout of 10 seconds.
We know that the second application is already up and the server has already been created when we start the discovery timeout.
This usually works, with the server being discovered almost immediately, but we are noticing sporadic situations where the server doesn't get discovered and we time out.
This is happening with ROS 2 Humble and Fast-DDS 2.6.4
Do you have suggestions on how to make this setup more robust, besides increasing the timeout?
As already mentioned, both processes are in the same machine.
We are using the same XML profile for both applications, which allows discovery only on localhost
Thank you
Beta Was this translation helpful? Give feedback.
All reactions