-
Notifications
You must be signed in to change notification settings - Fork 1k
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
UR10 Gazebo Launching Problem #386
Comments
gazebo 7 or 9? |
gazebo 7 |
So I get these errors too which - according to the last two warnings - gravity acts weird, and to solve it, we either have to set gazebo_pid parameters, switch to the VelocityJointInterface or EffortJointInterface, or upgrade to Gazebo 9. I may be wrong and am about to try myself right now with the UR10 but according to ros-simulation/gazebo_ros_pkgs#612 it should be the solution. Let me know how you get on...
|
@ipa-mjp could you please give some details about how did you started the simulation? This command
@shloakmehta I have never had this issue, unfortunately I can't reproduce it. did you solve the problem? Are you mounting somewhere the arm or is it a "arm-solo setup"? |
@ipa-mjp Did you run this command line
|
Hey, ROS Distro: Kinetic Any help will be appreciated! |
Unfortunately set the |
Does this still need to be developed for kinetic? I have had issues in the past with UR in gazebo where I cannot actuate the joints using kinetic, gazebo7 and 16.04 |
There has been quite some work on all packages in this repository in the context of #448. I've recently updated the Gazebo packages myself and I've not encountered any issues. We will not be backporting any of that to Kinetic. |
Please see #443 as well. |
Hello all,
I am using UR10 arm. While lunching gazebo model of UR10 arm in the kinetic, it is falling down on the ground. I think but not sure this is the problem of the gravity. I tried to tune this parameter but not successed yet. If any one facing same problem and solve it than please let me know.
My setup:
The text was updated successfully, but these errors were encountered: