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

Tool contact action #37

Open
wants to merge 4 commits into
base: humble-devel
Choose a base branch
from

Conversation

URJala
Copy link
Contributor

@URJala URJala commented Jan 23, 2025

This PR adds two actions, one for use with the tool contact controller, and one for use with the TrajectoryUntilNode, which is used to execute a trajectory until some condition is met (or the trajectory is finished). Right now the only available condition is tool contact.

Copy link

@urfeex urfeex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for the driver PR, I think it would make sense to split the tool contact and move_until into two separate PRs.


---
int32 SUCCESS=0
int32 CANCELLED_BY_USER = -1
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is usually called PREEMPTED in ROS.

Comment on lines 5 to 6
int32 ABORTED_BY_HARDWARE = -2
int32 ABORTED_BY_CONTROLLER = -3
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure whether it makes sense to separate this. I understand your intention, but with that thinking you tie the action definition closely to the controller.

@URJala URJala requested a review from urfeex February 26, 2025 13:38
Co-authored-by: Felix Exner <feex@universal-robots.com>
Comment on lines +3 to +5
int32 SUCCESS=0
int32 PREEMPTED = -1
int32 ABORTED = -2
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the intended use for those?

A general "has the action succeeded / canceled / aborted" is part of the action definition already. In the end a caller would want to know whether a tool contact was detected or not, right? Those cases would both fall under the term "action succeeded" from my point of view.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I might not have thought that through all the way. Yeah, you are right that information would be nice to have.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After looking through how the interface to the robot itself works, you are right that the preempted and aborted dont make sense, but a "not triggered" result also doesnt really make sense. Once tool contact has been activated it stays active until it either finds contact or is cancelled by a user, in which case the action should report either cancelled or aborted, in my opinion.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, good point. Would we need a result at all, then?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess not actually, the state of the action itself should be sufficient

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.

2 participants