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

Initialize MotionData using provided initial values #9

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Yadunund
Copy link

This PR updates updates the implementation of abb::robot::initializeMotionData() to accept initial state and command values for position, velocity and effort for each joint. The changes here do not break API and should not affect any existing downstream users.

This PR would allow downstream implementations of hardware interfaces/ROS drivers to properly initialize EGM such that the robot remains at a desired initial state on startup.

It is essential to fix PickNikRobotics/abb_ros2#44

Signed-off-by: Yadunund <yadunund@openrobotics.org>
@Yadunund
Copy link
Author

Yadunund commented Jan 4, 2024

@gavanderhoorn could you provide some feedback on this PR?

@Yadunund
Copy link
Author

@gavanderhoorn friendly ping.

@Yadunund
Copy link
Author

@gavanderhoorn another ping.

@tgaspar
Copy link

tgaspar commented Oct 25, 2024

A friendly ping also from me - is there anything that can still be done on this PR before it can be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Robot is forced to 0rad joint positions once hardware interface establishes EGM connection
2 participants