Use i_clamp_max/min in UR controllers #1483
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR aligns
ur_controllers
with the currentjoint_trajectory_controller
parameter schema on Rolling by switching the anti-windup clamping from the
symmetric
gains.i_clamp
to the explicitgains.i_clamp_max
/gains.i_clamp_min
.This matches how JTC exposes per-joint PID limits and the newer anti-windup
options, while keeping behavior identical when max = +M and min = −M.
What was added/changed in this PR
gains.i_clamp
withgains.i_clamp_max
/gains.i_clamp_min
in the anti-windup mapping.
ur_controllers
in line with JTC’s Rolling parameter names andanti-windup configuration.
About tests
The packages compile correctly and have passed the colcon tests.
Related PR's
Final notes
I'm very open to any recommendations to improve this code.