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

Allow different MoveGroup namespace #95

Open
JStech opened this issue Jun 8, 2021 · 1 comment
Open

Allow different MoveGroup namespace #95

JStech opened this issue Jun 8, 2021 · 1 comment

Comments

@JStech
Copy link
Contributor

JStech commented Jun 8, 2021

The MoveGroup interface uses the default (empty) namespace, and so it won't work with a robot that is using a non-empty namespace.

@playertr
Copy link

In my case, I was able to work around this by starting rviz in my robot's namespace. Previously, the calls to "robot_description" and "planning_scene_monitor" within handeye_control_widget.cpp and handeye_context_widget.cpp had been attempting to access these topics relative to the rviz namespace. By changing the namespace rviz was launched in, the calibration plugin can access these values without significant modification of the rest of my launch file.

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

2 participants