ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

Address already in use

That appears to be your error, I’d look into why that’s being a problem, which is in turn failing the lifecycle transition causing the Lifecycle Manager / BT Navigator issue.

I’d also use the CLI to verify everything is namespaced with robot0/1 properly, but from the logs it looks correct to me. Could also just be an issue with node name collisions when the manager is trying to transition up a server of the same name that was already up from the other robot’s manager.

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.

Powered by Askbot version 0.10.2