-
Notifications
You must be signed in to change notification settings - Fork 152
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
Comments
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 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 ).
|
@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
The text was updated successfully, but these errors were encountered: