Closed rcj86 closed 7 years ago
This appears to be bug #42. The MoveIt execution monitor is sending a stop command to the robot when the first motion takes longer than expected (see here for more detail).
The pendant message STOP received
is indicative of this bug.
There are multiple causes for this:
Other than addressing the causes above, there is a work around (based on the last item in the list here ).
~/execution_duration_monitoring
to FALSE (Disables monitoring)~/allowed_execution_duration_scaling
to a something greater than 1 (i.e. 2) (to increase the time a motion is allowed to exectue)@rcj86, please let me know if this solves the problem.
@shaun-edwards, This issue was also addressed by PR #62.
I'm closing this because of inactivity.
I am having the same issue. After sending the trajectory data the teach pendant receives a STOP command. On the terminal I get a Controller is taking too long to execute error.
I am using Kinetic-Devel repository in my project and running ros on UBUNTU 16.04.
Any help in this would be appreciated.
Please see How do I disable execution_duration_monitoring ?. The robot is too slow and MoveIt cancels execution of your trajectory because of that.
I want move the robot in robotstudio with ros-industrial (virtual machine), but I only can move the robot once. I use irb2400 abb package.
launch: roslaunch irb_2400_moveit_config moveit_planning_execution.launch sim:=false robot_ip:=<robot's ip>
Additional info: Windows 7 64 bits RobotStudio 5.61 VirtualBox 4.3.12 ROS distro hydro Desktop-Full Install ROS-I intalled binary package abb packages -> https://github.com/ros-industrial/abb.git