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

Enforce joint position limits on internal joint state before making trajectory #13

Merged

Conversation

AdamPettinger
Copy link

Description

This switchs the order that composeJointTrajMessage and enforcePositionLimits is called so that enforcePositionLimits works on a JointState and uses internal_joint_state_ which holds position and velocity information regardless of what should be published. Previously: it was operating on the JointTrajectory and had to take publishing booleans into consideration

Tested locally, including being able to back away from joint position limit. Shameless plug for new Servo tutorial which includes using a keyboard as input (how I tested the joint limits)

@JafarAbdi JafarAbdi merged commit 94f2e5d into JafarAbdi:pr-fix_servo_bug Jun 21, 2021
@AdamPettinger AdamPettinger deleted the pr-servo_seg_fault branch June 21, 2021 19:04
JafarAbdi added a commit that referenced this pull request Jun 25, 2021
… and a joint is close to position limit (moveit#497)

* moveit_servo: Fix segfault when publish_joint_velocities set to false and a joint is close to position limit

* Enforce joint position limits on internal joint state before making trajectory (#13)

* Use the input joint state to check bounds

Co-authored-by: AdamPettinger <adam.pettinger@utexas.edu>
JafarAbdi added a commit that referenced this pull request Jun 28, 2021
… and a joint is close to position limit (moveit#497)

* moveit_servo: Fix segfault when publish_joint_velocities set to false and a joint is close to position limit

* Enforce joint position limits on internal joint state before making trajectory (#13)

* Use the input joint state to check bounds

Co-authored-by: AdamPettinger <adam.pettinger@utexas.edu>
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

Successfully merging this pull request may close these issues.

None yet

2 participants