-
Notifications
You must be signed in to change notification settings - Fork 86
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
[Bug]: xsarm_moveit.launch.py does not get the planning scene and the robot pose #203
Comments
Please provide the entire contents of your terminal. I would also note that ROS 2 Rolling is not a supported distribution and we do not test it regularly. You may face issues or unexpected behavior when on that branch. |
Is there a timeline for when Jazzy will be supported? Everything works rather well with Rolling except for the MoveIt integration. |
Hello @lukeschmitt-tr , thank you for your quick reply. Below is the entire content:
|
Taking a look at the stack trace, we can see that move group node is throwing an exception. The type for some parameter has likely changed between distributions, specifically something used in the We currently do not have the bandwidth to do further investigation, but this is where I would start looking. |
What happened?
I aim at planning motion with a physical Interbotix Widow-X250s robotic arm, and a Raspberry Pi 5 as controller, using
xsarm_moveit.launch.py
.Unfortunately, the Planning Scene cannot be loaded in the RViz station. Moreover, the actual pose of the arm is not shown in the station.Robot Model
wx250s
Operating System
Ubuntu 22.04
ROS Distro
ROS 2 Rolling
Steps To Reproduce
I set the working directory, I source
setup.bash
, then I launchxsarm_moveit.launch.py
as indicated in the constructor's tutorial.Unfortunately, the Planning Scene cannot be loaded (as seen in the screenshot below) and the actual pose doesn't match the one shown in the station.
In the terminal, the log output reveals several problems, particularly in defining the Move Group node and the Controller Manager (below are shown only errors and warnings)
However, the joint states are visible to ROS, I checked it using
ros2 topic echo /wx250s/joint_states
in the terminal. It returns consistent data.The planning scene also seems to get data, I checked it using
ros2 topic echo /monitored_planning_scene
in the terminal. It returns this content : topic monitored_planning_scene terminal feedback.txtRelevant log output
Additional Info
Potential reasons I suppose :
.launch
?.launch
?The text was updated successfully, but these errors were encountered: