Skip to content
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

Using MOVE for G0 can cause arm to go through the table #4

Open
mentarus opened this issue Mar 12, 2015 · 2 comments
Open

Using MOVE for G0 can cause arm to go through the table #4

mentarus opened this issue Mar 12, 2015 · 2 comments

Comments

@mentarus
Copy link
Contributor

Happened when moving across about 500mm distance, where the move command decided to spin forearm around joint 3. This caused the wrist to plow into the table.

@saljam
Copy link
Contributor

saljam commented Mar 17, 2015

Ouch...

Would it make sense to just not use the controller's builtin inverse kinematics and compute them ourselves? It seems to do weird stuff all the time.

(Also, hi Eugene!)

@mentarus
Copy link
Contributor Author

Given the number of issues with the IK solver in the arm this may be the
best option. We've got ROS move_it package working with the small arm and
we've already made a model for the staubli so it's shouldn't be that much
effort.
Will need to see CAM software like sprutcam can control the joints
directly, I believe it does so out of the box, just need to write the
driver for it.
(Also, hello! you are alive!)

On 17 March 2015 at 14:28, سلمان الجمّاز (Salmān Aljammāz) <
notifications@github.com> wrote:

Ouch...

Would it make sense to just not use the controller's builtin inverse
kinematics and compute them ourselves? It seems to do weird stuff all the
time.

(Also, hi Eugene!)


Reply to this email directly or view it on GitHub
#4 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants