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

BoBiBù's profile - activity

2019-03-01 12:41:46 -0500 marked best answer MoveIt: troubles with joint values

I have just started with ROS and MoveIt! and I'd like to use it for planning trajectories on a Sawyer robot (ROS version: kinetic). I have followed the tutorial on SDK intera webpage then I went through the Python tutorial linked at the end of that page.

After the commands roslaunch sayer_moveit_config sawyer_movit.launchand roslaunch sayer_moveit_config group_movit.launch, I ran python tutorial.py, the script containing the code in the linked Python tutorial, with the only difference that I defined group = moveit_commander.MoveGroupCommander("right_arm") instead of left_arm (because Sawyer robot has only right arm).

Well, in Rviz I can see the planned trajectory. The problem arose while attempting to execute the plan: in the output I can read

1) a vector of zeros for 'positions', like in this question (but I don't have to rename the joint_states topic, because for Sawyer the topic is already '/robot/joint_states')

2) "Joint values for monitored state are requested but the full state is not known", whilst $ rostopic echo /robot/joint_states shows a stream of positions..

Googling this error, I have found here

if (!current_state_monitor_->waitForCurrentState(opt_.group_name_, wait_seconds))

ROS_WARN_NAMED("move_group_interface", "Joint values for monitored state are requested but the full state is not "known");

Do you have some some suggestion? What's wrong? I only have these files and the Python tutorial. Many thanks.

2018-05-04 10:42:07 -0500 received badge  Famous Question (source)
2018-01-30 14:45:47 -0500 received badge  Notable Question (source)
2018-01-30 14:21:05 -0500 received badge  Popular Question (source)
2018-01-30 12:51:44 -0500 asked a question MoveIt: troubles with joint values

MoveIt: troubles with joint values I have just started with ROS and MoveIt! and I'd like to use it for planning trajecto