ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Not adding start point into waypoints solved this problem for me. In the Move Group Interface Tutorial they've added start point for visualisation:

You can plan a cartesian path directly by specifying a list of waypoints for the end-effector to go through. Note that we are starting from the new start state above. The initial pose (start state) does not need to be added to the waypoint list but adding it can help with visualizations

Seem's to me that something like: "Initial pose must not be added to the waypoint list" would be better. Another note: even if fraction is less than 100% controller will still execute as much trajectory as was planned.

Not adding start point into waypoints solved this problem for me. In the Move Group Interface Tutorial they've added start point for visualisation:

You can plan a cartesian path directly by specifying a list of waypoints for the end-effector to go through. Note that we are starting from the new start state above. The initial pose (start state) does not need to be added to the waypoint list but adding it can help with visualizations

Seem's to me that something like: "Initial pose must not be added to the waypoint list" would be better. Another note: even if fraction is less than 100% controller will still execute as much trajectory as was planned.