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
{{ message }}
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.
We have managed to get as far as having MoveIt (+ rviz) get the correct current position of the robot. However, when trying to execute a path to a goal position, the robot does not move.
In addition, there are no gripper topics listed. MoveIT complains about not having the gripper states:
We followed the instructions (after digging around in other branches to find the required backups (addition-demo, two-grippers realtime) ). We found someone with a similar issue
(#21) but there were no detailed steps listed to solve the issue.
Any help would be appreciated.
The text was updated successfully, but these errors were encountered:
Wr tried installing YumiPy but ran into a lot of issues- we are using ros-kinetic and the YumiPy docs explicitly say it has only been tested on jade. We might give it another go.
Thank you for linking your repo. It looks like it will be helpful. We will try it next week when we return from conference.
*To mods: Please do not close this issue yet, thanks.
Well, I used yumipy with kinetic and even melody, and I did not have problem at all. But there is another package that I think it is built on top of OrebroUniversity/yumi, here you have the link: https://github.com/kth-ros-pkg/yumi
I tried with that one, I did couple of applications and it works pretty well, the difference between the yumipy and the kth-ros-pkg/yumi is that you will have more capabilities to leverage the yumi robot with MoveIt if you go with kth package.
Best regards
Cesar
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have managed to get as far as having MoveIt (+ rviz) get the correct current position of the robot. However, when trying to execute a path to a goal position, the robot does not move.
In addition, there are no gripper topics listed. MoveIT complains about not having the gripper states:
We followed the instructions (after digging around in other branches to find the required backups (addition-demo, two-grippers realtime) ). We found someone with a similar issue
(#21) but there were no detailed steps listed to solve the issue.
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: