-
Notifications
You must be signed in to change notification settings - Fork 250
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
Too large error of trajectory tracking using moveIt for real robot #278
Comments
I think it's a duplicate of #284, Did you find a solution? |
In fact, slow movements were enough for me at that time. And I didn't have enough time to dive deep into the problem. In the following projects, I used the FRI interface without moveIt and everything worked great. As for this problem, I think in iiwa_stack it need to send the trajectory from the moveIt to the controller and do retime using the internal interpolator of the robot. But that's just my thoughts. I didn't solve the problem. Also, I think there are another good solutions for iiwa that also can be test with moveIt |
Hi guys!
I have a problem with controlling a robot with an environment with obstacles.
On fast trajectories, the robot deviates too much from the desired trajectory. In the moveIt, the trajectory is set correctly, but in real life the robot breaks the exactly same environment.
The scene we used is
I have a hypothesis that this is due to the default position control implementation in iiwa_hw package, instead of the position velocity control. If anyone has an intuition, how can I solve my problem? Thanks!
The text was updated successfully, but these errors were encountered: