Skip to content
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

[Fetch] Add jsk_fetch_user.rosinstall.noetic to avoid moveit_msgs error #1800

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

tkmtnt7000
Copy link
Member

Without this PR, the following error occurs at client users' noetic PC.
ros-planning/moveit_msgs format changes between melodic and noetic.

[ERROR] [1684468275.276098137]: Client [/move_group] wants topic /planning_scene_world to have datatype/md5sum [moveit_msgs/PlanningSceneWorld/373d88390d1db385335639f687723ee6], but our version has [moveit_msgs/PlanningSceneWorld/79457311445f53d410ab4e3781de8447]. Dropping connection.

@k-okada
Copy link
Member

k-okada commented May 19, 2023 via email

@tkmtnt7000
Copy link
Member Author

tkmtnt7000 commented May 22, 2023

Sorry for late.

I suppose /move_group running on melodic(robot).

Yes, /move_group runs on melodic robot.

Who publishes the planning_scene_world topic ?

$ rostopic info /planning_scene_world
Type: moveit_msgs/PlanningSceneWorld

Publishers: 
 * /look_at_human (http://fetch15:44267/)
 * /fetch_eus_interface_1684721715440405383 (http://133.11.216.180:40255/)

Subscribers: 
 * /move_group (http://fetch15:40017/)

That error above occurs when we run roseus on local noetic laptop with rossetip and rossetmaster fetchxx.
When we initialize fetch-interface, moveit-enrironment is called and the error occurs at this point.

(send self :set-moveit-environment (instance fetch-moveit-environment :init :robot moveit-robot))

@tkmtnt7000
Copy link
Member Author

FYI:
moveit_msgs/PlanningSceneWorld does not change itself, but moveit_msg/CollisionObject changes slightly after melodic version released, so md5sum of moveit_msg/CollisionObject is different.

[http://fetch15:11311][133.11.216.180] tsukamoto@tsukamoto-desktop-ryzen ~/ros/fetch_ws/src/jsk-ros-pkg/jsk_pr2eus/pr2eus_moveit (master=) 
$ apt search moveit-msg
ソート中... 完了
全文検索... 完了  
ros-noetic-moveit-msgs/focal,now 0.11.4-1focal.20230216.003351 amd64 [インストール済み、自動]
  Messages, services and actions used by MoveIt

[http://fetch15:11311][133.11.216.180] tsukamoto@tsukamoto-desktop-ryzen ~/ros/fetch_ws/src/ros-planning/moveit_msgs/msg (master=)
$ git diff melodic-devel 0.11.4 CollisionObject.msg
diff --git a/msg/CollisionObject.msg b/msg/CollisionObject.msg
index 5e8b138..db1aeaa 100644
--- a/msg/CollisionObject.msg
+++ b/msg/CollisionObject.msg
@@ -1,6 +1,10 @@
 # A header, used for interpreting the poses
 Header header
 
+# The object's pose relative to the header frame.
+# The shapes and subframe poses are defined relative to this pose.
+geometry_msgs/Pose pose
+
 # The id of the object (name used in MoveIt)
 string id
 
@@ -8,7 +12,7 @@ string id
 object_recognition_msgs/ObjectType type
 
 # The collision geometries associated with the object.
-# Their poses are with respect to the specified header
+# Their poses are with respect to the object's pose
 
 # Solid geometric primitives
 shape_msgs/SolidPrimitive[] primitives
@@ -22,6 +26,14 @@ geometry_msgs/Pose[] mesh_poses
 shape_msgs/Plane[] planes
 geometry_msgs/Pose[] plane_poses
 
+# Named subframes on the object. Use these to define points of interest on the object that you want
+# to plan with (e.g. "tip", "spout", "handle"). The id of the object will be prepended to the subframe.
+# If an object with the id "screwdriver" and a subframe "tip" is in the scene, you can use the frame
+# "screwdriver/tip" for planning.
+# The length of the subframe_names and subframe_poses has to be identical.
+string[] subframe_names
+geometry_msgs/Pose[] subframe_poses
+
 # Adds the object to the planning scene. If the object previously existed, it is replaced.
 byte ADD=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants