-
Notifications
You must be signed in to change notification settings - Fork 557
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
Launch Error #2734
Comments
The output of
|
Getting the same error on iron too, my environment:
Project is a custom urdf. Haven't tried moveit2 with binary, will now! |
I got the same error on the same setup. Probably because of |
any luck with this issue? I am having the same issue when launching "ros2 launch demo.launch.py rviz_tutorial:=true " |
when i install moveit2 from build from source, then i don't get this error "[ERROR] [launch]: Caught exception in launch (see debug for traceback): 'capabilities'". i was looking for previous version number than "ros-iron-moveit/jammy,now 2.8.0-1jammy.20240213.190919 amd64 [installed]" apt list -a ros-iron-moveit |
I recently experienced the same error when building a custom panda setup with the moveit_setup_assistant. I eventually traced my error to having built the colcon moveit_ws as instructed in their tutorial here: https://moveit.picknik.ai/humble/doc/tutorials/getting_started/getting_started.html. After removing the old log, install, and build folders from that old workspace in addition to my new workspace, I was able to launch my custom configuration based on the panda arm. My new workspace just included the panda_description package and my newly generated package that was generated by the setup_assistant and based on panda description package. |
I also have the same problem and could not solve it with the solutions provided so far, any other ideas?
|
Too bad, this does not fix the same issue on my end. |
Also getting this issue. Here's my console output, with and without the debug flags:
I'm on ros2 humble and using I'm using a ur10e moveit config that I just created, with no additions to the urdf. I did not set virtual joints or an end effector. |
I have fixed this issue by changing the line 199-206 into |
Same here.
I removed the launch argument as well as the capabilities parameter, and it works fine now. Do you know what the parameter is supposed to control? |
no idea.... sorry. :) |
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups. |
+1 same issue here, just on Docker Rolling tutorial source image. |
Same issue and the above changes to launches.py only seem to add more issues. Using Ubuntu 24.04 and Jazzy |
I made a PR to revert the change: #2912 In the meantime, |
I have the exact same issues and the changes to the launch file haven't solved it for me |
* this fixes an issue seen when no capabilities are defined (moveit#2734) * also adds ability to specify disabled capabilities
* this fixes an issue seen when no capabilities are defined (moveit#2734) * also adds ability to specify disabled capabilities
I've opened #3018 to fix this - looks like we need to backport to both humble and iron as well |
Fix is merged into 'humble' (which this referenced) and 'main' branch. Still working on the 'iron' branch fix |
+1 same setup, same issue. |
Description
I have a problem with launcher. This problem is in source build installation, not binary. When I use binary, it works correctly. But when I install MoveIt 2 from source, it doesn't work. Note, tutorials launch files works without problems.
My environment
Steps to reproduce
I created a moveit package using setup_assistant. Its name is moveit2_package. After building and sourcing the workspace, I launched the launch file.
$ ros2 launch moveit2_package demo.launch.py
Expected behaviour
Opening RViz2 with the robot
It is correct when I install MoveIt 2 from binary!
Actual behaviour
An error occured.
Backtrace or Console output
[ERROR] [launch]: Caught exception in launch (see debug for traceback): 'capabilities'
The text was updated successfully, but these errors were encountered: