Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace for /execute_task_solution Action Client #414

Closed
swiz23 opened this issue Dec 22, 2022 · 1 comment
Closed

Namespace for /execute_task_solution Action Client #414

swiz23 opened this issue Dec 22, 2022 · 1 comment

Comments

@swiz23
Copy link

swiz23 commented Dec 22, 2022

Hi,

For my ROS2 project, I am launching move_group in a namespace 'arm1'. This will end up advertising the execute task solution action server as /arm1/execute_task_solution.

Using a custom node, I can then plan a task which is published to the /arm1/solution topic.

Then, using Rviz, I select the task in the Motion Planning Tasks plugin, highlight the cost, then hit the 'Exec' button. However, it fails to execute, giving a warning in the terminal that was used to launch Rviz of:
[rviz2-1] [ERROR] [1671738043.591988305] [moveit_task_constructor_visualization.task_view]: Failed to connect to task execution action

Upon closer inspection, it seems the reason this is happening is that the Motion Planning Tasks plugin spins off a node called 'task_view_private' that hosts the action client in the root namespace (so just /execute_task_solution). So since the server and client are in different namespaces, they cannot communicate with each other.

I noticed that the MotionPlanning plugin contain a 'namespace' field which allow action clients to be mapped to the correct namespace. However, I do not see this field present in the Motion Planning Tasks Rviz plugin. Is there another way to get the Rviz Execute Task Solution Action Client in the correct namespace? Note that launching the Rviz node in the 'arm1' namespace is not an option since this will cause issues with the MotionPlanning plugin.

Thanks.

@swiz23
Copy link
Author

swiz23 commented Dec 27, 2022

So it turned out that I was able to launch Rviz in the 'arm1' namespace, and still get the MotionPlanning plugin to work. See moveit/moveit2#1831.

@swiz23 swiz23 closed this as completed Dec 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant