Jorge Nicho
Jorge Nicho
I'm not looking for any files in particular , I'm just trying to determine if the start state is being properly initialized but it sounds like that isn't the issue...
The Rviz motion planning plugin doesn't automatically sync it's start state to the current state of the robot before sending a plan request to MoveIt!. You can view the start...
@TheDash let me know if you made any progress here, thanks
@TheDash I'd be good if you could print the joint values of the start and goal states. Also, in theory the check bounds function on **continuous** joints should validate but...
@broesdecat is this a STOMP issue or a moveit issue? Base on your comments I can't tell which one it is.
@broesdecat could you point me to a repo that I could test this on?
@broesdecat and @TheDash after further inspection using @broesdecat example code I pinned it down to the [MoveGroupInterface::group.setStartStateToCurrentState()](http://docs.ros.org/kinetic/api/moveit_ros_planning_interface/html/move__group__interface_8cpp_source.html#l00421) method, it in fact doesn't do anything other than to reset a smart...
@ipa-bfb are you setting the robot state start state as described above?
@broesdecat Excellent. This probably merits an issue in the moveit repo to address this problem with the MoveGroupInterface.