| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Often when debugging, a launch which was responsible for the original Master goes down. When this happens things that were connected that stay up are unable to communicate with the new Master when it comes up.
In rospython it seems it's possible (if dangerous?) to do the following:
rospy.client._init_node_args = None
rospy.init_node( "node_name" )
I'm not sure if it's wise but it seems to work.
I always launch a master manually with roscore for this reason. IMO there's too much potential for weird inconsistencies, e.g., with parameter server values, to try reconnecting.
Asked: 2011-11-11 05:53:07 -0500
Seen: 640 times
Last updated: Nov 11 '11
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.
