-
Notifications
You must be signed in to change notification settings - Fork 121
Fixes eager interface claiming bug in franka_hardware #124
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
jcarpinelli-bdai
wants to merge
1
commit into
frankaemika:humble
Choose a base branch
from
jcarpinelli-bdai:humble
base: humble
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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 is very hardcoded.
What do you actually want to achieve?
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.
On
humble
today, the hardware interface assumes every hardware plugin loaded by the controller manager is aFrankaHardwareInterface
owned resource. This is often not true; for example, if a custom hardware (gripper, extra joints etc.) is loaded in the same controller manager. As a result, if you try to launch two separate hardware interfaces in the same controller manager, theFrankaHardwareInterface
crashes.The
FrankaHardwareInterface
allows for a subset of the standard interfaces:position
,velocity
,acceleration
, andeffort
. TheFrankaHardwareInterface
also includes non-standard interface names, e.g.1/cartesian_pose
.This PR first checks if the hardware interface is not one of the standard interfaces supported by the class. If not, it assumes (as it does on
main
) that the interface is owned by the class. If the interface is a standard interface, then it checks that the "joint" part of the interface name is a joint owned by the class.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.
@AndreasKuhner do you have any thoughts on allowing for this functionality? Regardless of the hard-coding of the interface names, I think this is critical functionality for users. Should I replace
"position"
withhardware_interface::HW_IF_POSITION
?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 think for a custom solution it works. But for our 'bigger' picture, it would need to resolve a few more issues... But I didn't have much time so far to investigate and see what that exactly means 😓
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.
Would it be possible to merge this, or a similar PR? The behavior change is very important for users running multiple hardware types in one controller manager (which I understand to be a common use case in
ros2_control
).