Skip to content

Conversation

@fmauch
Copy link
Contributor

@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
Contributor

@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
Contributor 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!

@fmauch fmauch deleted the moveit_no_trajectory_monitoring branch October 9, 2024 10:21
URJala pushed a commit to URJala/Universal_Robots_ROS2_Driver that referenced this pull request Dec 20, 2024
…nitoring by default (UniversalRobots#1132)

With the scaled JTC execution time monitoring doesn't make much sense as
long as MoveIt is not aware of the trajectory scaling.
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