Scaled joint trajectory controller
This package contains a joint trajectory controller leveraging on-the-fly speed scaling to slow down trajectories using a robot's teach pendant.
position_controllers/ScaledJointTrajectoryController and velocity_controllers/ScaledJointTrajectoryController
These controllers work similar to the well-known `joint_trajectory_controller`.
However, they are extended to handle the robot's execution speed specifically. Because the default joint_trajectory_controller would interpolate the trajectory with the configured time constraints (ie: always assume maximum velocity and acceleration supported by the robot), this could lead to significant path deviation due to multiple reasons:
- - The speed slider on the robot might not be at 100%, so motion commands sent from ROS would
- effectively get scaled down resulting in a slower execution.
- than expected and therefore not reaching the desired target in a control cycle.
for ROS commands, such as the `external_control` program node for Universal Robots running on the robot controller.
The following plot illustrates the problem:
The graph shows a trajectory with one joint being moved to a target point and back to its starting point. As the joint's speed is limited to a very low setting on the teach pendant, speed scaling (black line) activates and limits the joint speed (green line). As a result, the target trajectory (light blue) doesn't get executed by the robot, but instead the pink trajectory is executed. The vertical distance between the light blue line and the pink line is the path error in each control cycle. We can see that the path deviation gets above 300 degrees at some point and the target point at -6 radians never gets reached.
All of the cases mentioned above are addressed by the scaled trajectory versions. Trajectory execution can be transparently scaled down using the speed slider on the teach pendant without leading to additional path deviations. Pausing the program or hitting the E-stop effectively leads to speed_scaling being 0 meaning the trajectory will not be continued until the program is continued. This way, trajectory executions can be explicitly paused and continued.
With the scaled version of the trajectory controller the example motion shown in the previous diagram becomes:
The deviation between trajectory interpolation on the ROS side and actual robot execution stays minimal and the robot reaches the intermediate setpoint instead of returning "too early" as in the example above.
Under the hood this is implemented by proceeding the trajectory not by a full time step but only by the fraction determined by the current speed scaling. If speed scaling is currently at 50% then interpolation of the current control cycle will start half a time step after the beginning of the previous control cycle.