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

Open & Closed loop options in the joint limits interface #2

Open
po1 opened this issue Nov 8, 2013 · 2 comments
Open

Open & Closed loop options in the joint limits interface #2

po1 opened this issue Nov 8, 2013 · 2 comments
Assignees

Comments

@po1
Copy link

po1 commented Nov 8, 2013

In some cases, feedback might not be available for one of the state variables (position, velocity). The joint limits interface has no knowledge of what is available and what is not.

The idea here would be to be able to choose between open and closed loop (default) joint limits enforcers. The closed loop would be slower, but potentially safer.

Issue related to #1

@adolfo-rt @efernandez

@ghost ghost assigned adolfo-rt Nov 8, 2013
@adolfo-rt
Copy link

Yes, I'll try to propagate these changes, and reflect them in the tests/doc.

@po1
Copy link
Author

po1 commented Dec 20, 2013

After further thinking, and discussion about the diff drive limiters, it appeared that the open-loop joint limits seem much better, and safer. Maybe we should ask around if there is any good reason to have closed-loop limits.

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