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

[moveit] Add config for trajectory execution and disable execution mo… #1132

Merged
merged 1 commit into from
Oct 9, 2024

Conversation

fmauch
Copy link
Collaborator

@fmauch fmauch commented Oct 8, 2024

…nitoring by default

With the scaled JTC execution time monitoring doesn't make much sense as long as MoveIt is not aware of the trajectory scaling.

…nitoring by default

With the scaled JTC execution time monitoring doesn't make much sense as
long as MoveIt is not aware of the trajectory scaling.
Copy link
Collaborator

@VinDp VinDp left a comment

Choose a reason for hiding this comment

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

Tested: with this the execution is not stopped anymore when the velocity is not 100%, so it definitely solves #1129 for me.

@VinDp VinDp merged commit 2d026bc into UniversalRobots:main Oct 9, 2024
6 of 11 checks passed
@gavanderhoorn
Copy link
Contributor

I would strongly recommend to document the change in this PR, perhaps by adding a warning in a (very) visible place.

It deviates from the default MoveIt behaviour (ie: monitoring trajectory execution) -- and I understand why -- but it will also mean any mistakes or other causes for trajectory execution running 'over time' will not be handled by MoveIt's TEM anymore.

This now delegates responsibility for keeping track of trajectory execution to essentially action clients, which could result in unsuspecting clients running into 'hangups' of MoveIt (as it can't abort goals automatically anymore).

@fmauch
Copy link
Collaborator Author

fmauch commented Oct 9, 2024

I would strongly recommend to document the change in this PR, perhaps by adding a warning in a (very) visible place.

That's a valid comment, thank you!

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.

3 participants