Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ros-industrial robotstudio #41

Closed
rcj86 opened this issue Jun 7, 2014 · 6 comments
Closed

ros-industrial robotstudio #41

rcj86 opened this issue Jun 7, 2014 · 6 comments

Comments

@rcj86
Copy link

rcj86 commented Jun 7, 2014

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

ros-i

fpu

nodes_topic

@shaun-edwards
Copy link
Member

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:

  • The robot is in teach mode (or some other speed limited mode) causing the trajectory to take longer
  • The robot joint speed limits are set too high (under the /config directory in the joint_limits.yaml file). This causes MoveIt to think the robot can move faster than it can (the controller doesn't allow this). Assuming you are using the default joint limits file, this does not appear to be the case.

Other than addressing the causes above, there is a work around (based on the last item in the list here ).

  • Set ONE of the following (under the move group node):
    • ~/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)

@shaun-edwards
Copy link
Member

@rcj86, please let me know if this solves the problem.

@Levi-Armstrong
Copy link
Member

@shaun-edwards, This issue was also addressed by PR #62.

@gavanderhoorn
Copy link
Member

I'm closing this because of inactivity.

@jclinton830
Copy link

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.

@gavanderhoorn
Copy link
Member

Please see How do I disable execution_duration_monitoring ?. The robot is too slow and MoveIt cancels execution of your trajectory because of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants