-
Notifications
You must be signed in to change notification settings - Fork 324
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
[JTC] Jerky motion with Franka Emika Panda - Effort interface #673
Comments
Seems like I am not the only one having this issue: frankaemika/franka_ros2#10 (comment) |
Thank you, @JafarAbdi! I can confirm that I got the expected behavior, that is, the robot motion was smooth, when I checked out the parent commit: ce0aeb2. I will continue testing tomorrow. |
@JafarAbdi, I have found the source of the jerky/wobbly motion. The bug was introduced in 8e6697b as you expected. The velocity error term is not computed when using an effort command interface, only for velocity command interfaces. This can be fixed by changing this line from if (has_velocity_state_interface_ && has_velocity_command_interface_) to if (has_velocity_state_interface_ && (has_velocity_command_interface_ || has_effort_command_interface_)) I'll submit at PR for this. I also have a problem with non-zero effort commands commanded after execution as mentioned in issue #671 (comment), but I'll take that discussion there. |
@tingelst This should be closed since the bug is fixed in the main branch, right? |
@JafarAbdi, yes indeed. Thank you for the help in tracking this down. |
Describe the bug
I have a Franka Emika Panda setup working with Humble. With the original
joint_effort_trajectory_controller
I get smooth motions in MoveIt and when usingrqt_joint_trajectory_controller
. However, when using thejoint_trajectory_controller
here on thehumble
branch I get jerky motions.To Reproduce
rqt_joint_trajectory_controller
and move the robotExpected behavior
The robot should move smoothly.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: