ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Move group node crashes while planning with approximate constraint manifold

asked 2021-03-16 19:31:53 -0600

Gokul gravatar image

Platform:

Ubuntu 18.04.2 (Kernel: 5.4.0-66-generic) - Vmware

ROS Melodic

Moveit debian installation

Issue

I have created a constraint database with orientation constraints following the instructions from the moveit tutorial. Given below is the constraint msg whicnh i used to create the database.

name: orientation_constraints
constraints:
- type: orientation
  frame_id: base_link    
  link_name: ee_link    
  orientation: [-3.1415269, -1.57079632, 0] #RPY    
  tolerances: [6.28318531, 0.2, 6.28318531]
  weight: 1.0

Now when I try to plan and execute a path using the orientation constraint, move group node crashes. GIven below is the constraint which I am using while planning a path

   orientation_constraint = moveit_msgs.msg.OrientationConstraint()
    orientation_constraint.header.frame_id = self.move_group.get_planning_frame()
    orientation_constraint.link_name = self.move_group.get_end_effector_link()     
    orientation_constraint.orientation.x=-0.707044
    orientation_constraint.orientation.y=-0.000472224
    orientation_constraint.orientation.z= 0.707168
    orientation_constraint.orientation.w=0.000954376
    orientation_constraint.absolute_x_axis_tolerance = 0.01
    orientation_constraint.absolute_y_axis_tolerance = 0.01
    orientation_constraint.absolute_z_axis_tolerance = 0.01
    orientation_constraint.weight = 0.9

I am able to execute the path with the above constraint without using the database. But when I try to use the database, it crashes. I also tried changing the tolerances and weight values but nothing happened. Given below is the debug output of the move group node.

[ INFO] [1615938113.480885794]: manipulator: Using precomputed state sampler (approximated constraint space) for constraint 'orientation_constraints'
[ INFO] [1615938113.480915564]: RRTConnect: Starting planning with 1 states already in datastructure
[DEBUG] [1615938113.480939369]: RRTConnect: Waiting for goal region samples ...
[DEBUG] [1615938113.481038877]: Beginning sampling thread computation
[DEBUG] [1615938113.481206214]: getPositionIK
[DEBUG] [1615938113.486549535]: End effector index: 7
[DEBUG] [1615938113.487436069]: Solution passes callback
[DEBUG] [1615938113.487724595]: End effector index: 7
[DEBUG] [1615938113.487859751]: Adding goal state
[DEBUG] [1615938113.487958569]: getPositionIK
[DEBUG] [1615938113.491063008]: RRTConnect: Waited 0.010110 seconds for the first goal sample.
[move_group-4] process has died [pid 76735, exit code -11, cmd /opt/ros/melodic/lib/moveit_ros_move_group/move_group --debug __name:=move_group __log:=/home/gokul/.ros/log/f9b1ab98-86b0-11eb-84f3-000c299cc7bf/move_group-4.log].
log file: /home/gokul/.ros/log/f9b1ab98-86b0-11eb-84f3-000c299cc7bf/move_group-4*.log

========================================

edit retag flag offensive close merge delete

Comments

Hi, did you manage to use the database?

xibeisiber gravatar image xibeisiber  ( 2021-11-03 09:04:47 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2021-05-13 09:33:09 -0600

artemiialessandrini gravatar image

updated 2021-05-13 09:38:33 -0600

You're having a typo in database name - constraints msg.
As it's explained in database-loading-and-usage:

For planning just initialize the constraints message as always and set the messages name to the exact name that was used to construct the database.

Likely changing moveit_msgs.msg.OrientationConstraint() name to orientation_constraints would fix it? Let me know if it fixed the problem.

[EDIT]
Also check your Moveit! logs if database is actually loaded.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2021-03-16 19:31:53 -0600

Seen: 223 times

Last updated: May 13 '21