Open ajshank opened 3 years ago
@hildebrandt-carl This can be addressed by what you described as a waypoint manager.
Addressed by #8 in devel branch, flight tests pending.
Consider changing waypoint_mode
enumerations to begin at 1 instead of 0 -- ROS constructor will automatically fill it with 0 if nothing is specified by the caller, thereby defaulting to TIME
mode.
Smooth, energy-optimal trajectories can be generated between two "waypoints" using motion primitives. The end-user waypoint publishing might be a point of conflict, but consider how this might be used at large.
Possible behaviors
[pn, pe, pd, dt]
[idx, pn, pe, pd, dt]
.Behaviour needs to be fully defined if (1) is abused by making multiple service calls rapidly.