UTNuclearRoboticsPublic / jog_arm

A real-time robot arm jogger.
45 stars 22 forks source link

The real robot doesn't move and get Warn:Stale joint trajectory msg. Try a larger 'incoming_command_timeout' parameter. #76

Closed stevensu1838 closed 6 years ago

stevensu1838 commented 6 years ago

ROS Kinetic on Ubuntu 16.40

The robot moved the day before yesterday. I experienced a lot of robot protectively stopped and could not jog it smoothly, though.

However, today it stops moving somehow. Please see the following details of my operation. Thank you so much for your support. Cheers.

I source in each of the terminals:

source /opt/ros/kinetic/setup.bash
source ~/catkin_ws/devel/setup.bash
1. I ping to the real UR5 robot, it receives data.
2.roslaunch ur_modern_driver ur5_bringup.launch robot_ip:=192.168.0.1
   roslaunch ur5_moveit_config ur5_moveit_planning_execution.launch
   roslaunch ur5_moveit_config moveit_rviz.launch config:=true

3.SPACE MOUSE
  roslaunch spacenav_node classic.launch
  rostopic list
  rostopic echo /spacenav/joy

  The space mouse works well 

4.Launch the jog arm

roscd 
cd ..
cd Jog_arm_config
roslaunch jog_node.launch
roslaunch jog_arm jog_with_spacenav.launch

Seems robot and my PC are connected but I just cannot move the real ur5 robot at all. In the ternimal where I launch roslaunch jog_arm jog_with_spacenav.launch, the following errors shown:

[ WARN] [1542256008.643868467]: Stale joint trajectory msg. Try a larger 'incoming_command_timeout' parameter.
[ WARN] [1542256008.643937609]: Did input from the controller get interrupted? Are calculations taking too long?

I've all the above with a real UR5 robot. Btw, the arm is still out of control in simulation. Thanks a million.