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

Cartesian control #178

Open
vopsi99 opened this issue May 23, 2024 · 8 comments
Open

Cartesian control #178

vopsi99 opened this issue May 23, 2024 · 8 comments
Assignees
Labels
enhancement New feature or request

Comments

@vopsi99
Copy link

vopsi99 commented May 23, 2024

Hello, I tried using this repository but my knowledge in ros is rather mediocre. I am curious if this stack has cartesian control implementation or not.

It may be a stupid question, but I am stuck for quite some time and I could really use some help..

@mhubii
Copy link
Member

mhubii commented May 23, 2024

no worries @vopsi99 and thank you for raising this issue. In principle yes, in practise users have to put in some effort to do this right now. I can pinpoint you to some examples and try to improve the demos.

What are you trying to achieve:

  • Move to an absolute pose?
  • Specify an end-effector velocity?

@vopsi99
Copy link
Author

vopsi99 commented May 23, 2024

I managed to move the end-effector incrementally but it is really unstable, so I need to move to an absolute pose with a certain velocity. I supposed this kind of motion would be the best to further integrate a stereo camera to position the robot in correlation to some markers in the workspace.

@mhubii
Copy link
Member

mhubii commented May 23, 2024

@vopsi99
Copy link
Author

vopsi99 commented May 23, 2024

So I should only send from another node my desired pose to this demo? This is the demo that I modified to send incremental values for x,y,z on position and orientation, but on Y orientation, for example, it always went crazy even if I was doing really small movement increments.

@mhubii
Copy link
Member

mhubii commented May 23, 2024

okay I'll have to double check this demo, as it was community contributed. But this demo sends an absolute pose.

You will have to make sure you:

  • Get the initial pose
  • Send a small (like really small) increment on top of the initial pose

@mhubii mhubii added the enhancement New feature or request label May 23, 2024
@mhubii mhubii self-assigned this May 23, 2024
@mhubii
Copy link
Member

mhubii commented May 23, 2024

I think this demo needs an update and should really allow users to control a velocity rather than absolute poses maybe

@vopsi99
Copy link
Author

vopsi99 commented May 23, 2024

Yes, I realised that a really small increment (0.001) would make the movement smoother.For positioning on x,y and z everything seems fine, but when I am trying to orient it, it just breaks everything.

After sending the increment on Y for longer it tends to jump into a position and i get the inverse kinematics failed error.

I think velocity control would be really useful for everyone.

@mhubii
Copy link
Member

mhubii commented May 23, 2024

thank you for the feedback. Let's add support for this then.

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

No branches or pull requests

2 participants