Revision history [back]

The plain and simple answer to this question is:

This doesn't work because nobody required and/or implemented it until now. The GetCartesianPath.srv ROS service offered by the move_group does not support a max_velocity_scaling_factor in its request section and the MoveGroupCommander uses that service to compute the cartesian trajectory.

So either you have to implement support for this in there, or you have to live with the full-speed trajectory you receive and re-scale the time parameterization afterwards.