Skip to content

Commit 988b151

Browse files
Felix Exner (fexner)gavanderhoorn
andauthored
Add note about TEM (#1136)
--------- Co-authored-by: G.A. vd. Hoorn <[email protected]>
1 parent 2d026bc commit 988b151

File tree

3 files changed

+31
-1
lines changed

3 files changed

+31
-1
lines changed

ur_moveit_config/config/moveit_controllers.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ trajectory_execution:
55
allowed_execution_duration_scaling: 1.2
66
allowed_goal_duration_margin: 0.5
77
allowed_start_tolerance: 0.01
8-
execution_duration_monitoring: false # Not much use when using the scaled JTC
8+
execution_duration_monitoring: false # May lead to unexpectedly aborted goals with scaled JTC
99

1010
moveit_simple_controller_manager:
1111
controller_names:

ur_moveit_config/doc/index.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,3 +23,21 @@ interaction using
2323
2424
Now you should be able to use the MoveIt Plugin in rviz2 to plan and execute trajectories with the
2525
robot as explained `here <https://moveit.picknik.ai/main/doc/tutorials/quickstart_in_rviz/quickstart_in_rviz_tutorial.html>`_.
26+
27+
.. note::
28+
The MoveIt configuration provided here has Trajectory Execution Monitoring (TEM) *disabled*, as the
29+
Scaled Joint Trajectory Controller may cause trajectories to be executed at a lower velocity
30+
than they were originally planned by MoveIt. MoveIt's TEM however is not aware of this
31+
deliberate slow-down due to scaling and will in most cases unnecessarily (and unexpectedly)
32+
abort goals.
33+
34+
Until this incompatibility is resolved, the default value for ``execution_duration_monitoring``
35+
is set to ``false``. Users who wish to temporarily (re)enable TEM at runtime (for use with
36+
other, non-scaling controllers) can do so using the ROS 2 parameter services supported by
37+
MoveIt.
38+
39+
.. literalinclude:: ../config/moveit_controllers.yaml
40+
:language: yaml
41+
:start-at: trajectory_execution:
42+
:end-at: execution_duration_monitoring
43+
:caption: moveit_controllers.yaml

ur_robot_driver/doc/usage/move.rst

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -67,4 +67,16 @@ To test the driver with the example MoveIt-setup, first start the driver as desc
6767
Now you should be able to use the MoveIt Plugin in rviz2 to plan and execute trajectories with the
6868
robot as explained `here <https://moveit.picknik.ai/main/doc/tutorials/quickstart_in_rviz/quickstart_in_rviz_tutorial.html>`_.
6969

70+
.. note::
71+
The MoveIt configuration provided here has Trajectory Execution Monitoring (TEM) *disabled*, as the
72+
Scaled Joint Trajectory Controller may cause trajectories to be executed at a lower velocity
73+
than they were originally planned by MoveIt. MoveIt's TEM however is not aware of this
74+
deliberate slow-down due to scaling and will in most cases unnecessarily (and unexpectedly)
75+
abort goals.
76+
77+
Until this incompatibility is resolved, the default value for ``execution_duration_monitoring``
78+
is set to ``false``. Users who wish to temporarily (re)enable TEM at runtime (for use with
79+
other, non-scaling controllers) can do so using the ROS 2 parameter services supported by
80+
MoveIt.
81+
7082
For more details, please see :ref:`ur_moveit_config`.

0 commit comments

Comments
 (0)