| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I use ros2 for communication on a embedded linux machine. The Ros nodes is started using systemd when the machine boots. However when the network is not connected at boot time the ros nodes does not detect eachother, even after the network is up.
Is there any way to force discovery messages to be sent out from a node?
I think the adapter used is selected on startup, so adapters that come up after the node will not be considered. There's no portable way (that I'm aware of) to make it reevaluate the available adapters. I'm not sure what you should do instead. If you can wait to start the node until the network is up, you can simply add a dependency in systemd so that the node only starts after the network. Otherwise, you'll probably have to restart the node after the network becomes available.
You might also be able to use a virtual adapter to fix this, but I've never done that before, so you'll probably have to look elsewhere for solutions like that.
Asked: 2018-05-24 07:48:52 -0500
Seen: 433 times
Last updated: Jun 05 '18
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
