You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my current application I am trying to combine clearpath jackal with open manipulator pro arm and control the arm firstly over rviz2 and after over my application package.
Sofar I could succesefully load all controllers in namespace i.e. mobile base, manipulator and gripper, and also could start the moveit2 inside the namespace
Humble, Ubuntu 22, from source
Expected behavior
Rviz2 action clients being also inside the namespace
Actual behavior
Currently I can see the arm inside the rviz
the MotionPlanning section does not work at all, because as i see output from ros2 topic list and ros action list
even though the rviz2 node is inside the namespace /j100_0000/rviz2 the actions and topics are not inside the namespace. Therefore it is not working.
How could I fix it and bring the rviz2 action clients inside the namespace?
Description
Hello,
In my current application I am trying to combine clearpath jackal with open manipulator pro arm and control the arm firstly over rviz2 and after over my application package.
Sofar I could succesefully load all controllers in namespace i.e. mobile base, manipulator and gripper, and also could start the moveit2 inside the namespace
Humble, Ubuntu 22, from source
Expected behavior
Rviz2 action clients being also inside the namespace
Actual behavior
Currently I can see the arm inside the rviz
the MotionPlanning section does not work at all, because as i see output from
ros2 topic list
andros action list
even though the rviz2 node is inside the namespace
/j100_0000/rviz2
the actions and topics are not inside the namespace. Therefore it is not working.How could I fix it and bring the rviz2 action clients inside the namespace?
Thanks in advnace
Backtrace or Console output
and here is my controller.yaml file
and
move_group
node is started correctlywith following launch file
The text was updated successfully, but these errors were encountered: