You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
kirillin
changed the title
Too large error of trajectory tracking using moveIt
Too large error of trajectory tracking using moveIt for real robot
Jan 31, 2022
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: