The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
[ WARN] [1508121443.319273668]: Failed to validate trajectory: couldn't receive full current joint state within 1s.
You don't show any launch files - so it's hard to know for certain, but it sounds like the JointState msgs from your driver instances are not reaching MoveIt / the MoveIt commander.
Easiest is probably to use a joint_state_publisher instance with the source_list parameter to publish an aggregate message on /joint_states. See moveit_resources/fanuc_moveit_config/launch/demo.launch for an example, and wiki/joint_state_publisher - Node API - parameters for info on source_list.
| | 2 | No.2 Revision |
[ WARN] [1508121443.319273668]: Failed to validate trajectory: couldn't receive full current joint state within 1s.
You don't show any launch files - so it's hard to know for certain, but it sounds like the JointState msgs from your driver instances are not reaching MoveIt / the MoveIt commander.
MoveIt will try to make sure that the trajectory that you want to execte actually starts at the current state of the robot (to avoid large sudden movements). For that it needs JointState messages, or it can't determine current state. Your two ur_driver instances should be publishing in the left and right namespaces, so there is no global /joint_states topic for MoveIt to listen to.
Easiest is probably to use a joint_state_publisher instance with the source_list parameter to publish an aggregate message on /joint_states. See moveit_resources/fanuc_moveit_config/launch/demo.launch for an example, and wiki/joint_state_publisher - Node API - parameters for info on source_list.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
