Describe the bug
After running the master_discovery node on the fetch robot, we expected the master_sync node to automatically see that master_discovery node is running, but it does not. We are also running the master_discovery node and the master_sync on the workstation and other robots, and the master_sync node discovers the discovery node without problem.
To Reproduce
We are following the official technical guide to set up the system. Also, when we bring up the master_discovery node other machines, the fetch robots says ROS masters obtained from /master_discovery/list_masters. The master_discovery node on the workstation says the same thing.
When we then start the sync node (as stated in the guide), it says the Master_discovery node appear not to running. Wait for topic with type 'MasterState. It continually throws this error. This does not happen on any other robot/workstation.
Expected behavior
We expect the sync node to automatically discover the master_discovery node like the workstation.
Screenshots
catkin workspace (please complete the following information):
fetch_ros version: Indigo
Ubuntu version: Ubuntu 14.04
ROS Workstation version: Indigo
Additional context
On the workstation and on the other bots, we noticed that they have the service /master_sync/get_sync_info The fetch robot does not have this service. (I don't know if this is relevant, but I thought I may add it.)
Describe the bug After running the master_discovery node on the fetch robot, we expected the master_sync node to automatically see that master_discovery node is running, but it does not. We are also running the master_discovery node and the master_sync on the workstation and other robots, and the master_sync node discovers the discovery node without problem.
To Reproduce We are following the official technical guide to set up the system. Also, when we bring up the master_discovery node other machines, the fetch robots says
ROS masters obtained from /master_discovery/list_masters
. The master_discovery node on the workstation says the same thing.When we then start the sync node (as stated in the guide), it says the
Master_discovery node appear not to running. Wait for topic with type 'MasterState.
It continually throws this error. This does not happen on any other robot/workstation.Expected behavior We expect the sync node to automatically discover the master_discovery node like the workstation.
Screenshots![Screenshot from 2019-06-06 11_51_55](https://user-images.githubusercontent.com/20187929/59049177-6d5e3900-8855-11e9-9759-4dc749f2fd7d.png)
catkin workspace (please complete the following information):
Additional context On the workstation and on the other bots, we noticed that they have the service
/master_sync/get_sync_info
The fetch robot does not have this service. (I don't know if this is relevant, but I thought I may add it.)It is related to: https://github.com/fkie/multimaster_fkie