-
Notifications
You must be signed in to change notification settings - Fork 495
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
Servo: Allow a negative joint margin #501
Servo: Allow a negative joint margin #501
Conversation
Codecov Report
@@ Coverage Diff @@
## main #501 +/- ##
=======================================
Coverage 46.65% 46.65%
=======================================
Files 183 183
Lines 19654 19654
=======================================
Hits 9168 9168
Misses 10486 10486 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea seems OK to me, and I do think spitting out a warning is good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm the use-case :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also seems reasonable to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more context on why a servo specific solution is needed. Some smoothing algorithms appropriate for use with servo do not consider position limits and will "smooth" commands beyond them.
On the other hand, time parameterization algorithms used by move group, etc, handle pos as well as vel+acc+... limits directly.
Modifying joint_limits.yaml would impact both of these when we only want to adjust this for servoing. So this servo specific solution is needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This parameter in general is just a way to simulate soft limits, which should be avoided, but can be moved out of. I would love to have support for them in MoveIt generally, but that's a bigger effort...
Co-authored-by: Michael Görner <me@v4hn.de>
Servo has a
joint_limit_margin
parameter that provides a little padding around joint limits from the URDF. This is useful to make sure the robot has time to stop before the actual joint limits.We have an unusual use case where one joint has very narrow joint limits and the encoders are pretty noisy. Also, there are hard stops, so it's no big deal if the software joint limit gets exceeded. For that, we want to allow a negative joint limit margin. Although we still throw a warning because this is so unusual.