-
Notifications
You must be signed in to change notification settings - Fork 155
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
Humble branch demo fails on execution #579
Comments
Not sure how I missed that commit on my fork, sorry about the sloppy workspace management! I still get these warnings. Should the controllers be explicitly set in each Stage?
|
Something like #582 fixes that issue for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing a few issues when trying to execute the Demo pick and place program.
Found empty JointState message
's when executing (seems to not be causing any issues)If I ask the demo config to execute the solution with the mock_components:
execute: true
The robot can only execute up to the pick point and then collision detection with the object causes it to stop.
[pick_place_demo-1] [moveit_task_constructor_demo 1717364678.467567393]: Planning succeded [pick_place_demo-1] [moveit_task_constructor_demo 1717364678.467579243]: Executing solution trajectory [pick_place_demo-1] [moveit_task_constructor_executor_110240201996832 1717364681.185096688]: Goal was aborted or canceled [pick_place_demo-1] [moveit_task_constructor_demo 1717364681.206986352]: Task execution failed and returned: 99999 [pick_place_demo-1] [moveit_task_constructor_demo 1717364681.207010792]: Execution complete
I'm also seeing a few empty JointState messages while it approaches the pick point:
and if you inspect the Rviz terminal we can see that we get a bunch of warnings about which controller is going to execute each stage:
and then the robot is stopped because it would collide with the target object.
I tried to look into how the planning scene is passed to the executor action (I think this is how it's set when making the goal) but can't see the source of the issues with it not being properly passed to
move_group
to execute.The text was updated successfully, but these errors were encountered: