-
Notifications
You must be signed in to change notification settings - Fork 189
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
'Use Cartesian Path' crashing RViz #864
Comments
I am having the exact same problem. Tested with Ubuntu, ROS2 Humble, moveit2 with a custom robot arm.
|
This is an issue introduced after a change to the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The 'Use Cartesian Path' option in the MotionPlanning plugin crashes RViz
When going through the MoveIt Quickstart in RViz tutorial I followed all of the steps in order. I am able to get the arm to move when not selecting 'Use Cartesian Path', but when that option is selected I get an error which I will include below and RViz becomes unresponsive. It is at this point in the tutorial that I get the error. I'll also add that the Show Trail checkbox does nothing when I select it with a path planned. It does not show the arm's path in the viewer. I'm not sure if that's related but the original issue is that 'Use Cartesian Path' is giving an error and crashing RViz.
Your environment
Steps to reproduce
At this point in the tutorial I get the issue. I move the goal state to some desired location. Press 'Plan' in the MotionPlanning plugin and immediately get the error pasted below. I am able to both Plan and Execute a motion if 'Use Cartesian Path' is not selected.
Expected behaviour
The arm in the world should move from Start State to Goal State in a straight path in Cartesian space. It also should not crash my RViz application preventing me from making further motions using MotionPlanner.
Backtrace or Console output
Use gist.github.com to copy-paste the console output or segfault backtrace using gdb.
The text was updated successfully, but these errors were encountered: