Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged waypoint_manager at Robotics Stack Exchange
Package Summary
| Version | 0.0.0 |
| License | MIT |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Description | Software for guidance, navigation and control for the Vortex AUVs. Purpose built for competing in AUV/ROV competitions. |
| Checkout URI | https://github.com/vortexntnu/vortex-auv.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-02-23 |
| Dev Status | UNKNOWN |
| Released | UNRELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Maintainers
- Jorgen Fjermedal
Authors
Waypoint Manager — ROS 2 Node
The Waypoint Manager node coordinates mission-level navigation by managing waypoint queues, forwarding them to a Reference Filter for trajectory generation, and exposing both an action interface (for mission planners) and a service interface (for perception-driven waypoint updates).
Interfaces
- WaypointManager (action server)
- WaypointAddition (service server)
- ReferenceFilterWaypoint (action client)
Behavior Summary
Mission Start
- On receiving a new action goal, any existing mission is aborted.
- Waypoints are stored, state is reset, and the first waypoint is sent to the reference filter.
During Mission
- Each waypoint is executed sequentially.
- Pose feedback from the reference filter is forwarded to the mission planner.
-
convergence_thresholddetermines when a waypoint is reached. - If
persistent = true, the action does not end even when waypoints run out.
Mission End
- If
persistent = false, the action completes when the last waypoint is reached. - If cancelled externally, all state is cleared and reference filter goals are cancelled.
Dynamic Waypoint Addition
Allowed only during persistent missions:
-
overwrite = true→ clears old queue and restarts from new waypoints -
overwrite = false→ appends waypoints to queue -
priority = true→ turn on priority mode. In this mode additional service requests withpriority = falseare ignored. Priority mode is set to false again when there are no more waypoints in queue.
Check available interfaces:
ros2 action list
ros2 service list
beware of namespace!
Example Action Goal (CLI)
ros2 action send_goal /orca/waypoint_manager vortex_msgs/action/WaypointManager "{
waypoints: [
{
pose: {
position: {x: 5.0, y: 0.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
convergence_threshold: 0.1,
persistent: false
}" --feedback
Example Waypoint Addition Service Call
ros2 service call /orca/waypoint_addition vortex_msgs/srv/SendWaypoints "{
waypoints: [
{
pose: {
position: {x: 2.0, y: 3.0, z: 0.0},
orientation: {x: 0.0, y: 0.0, z: 0.0, w: 1.0}
},
mode: 1
}
],
overwrite_prior_waypoints: false,
take_priority: false
}"
Package Dependencies
| Deps | Name |
|---|---|
| ament_cmake | |
| launch_testing | |
| launch_testing_ros | |
| launch_testing_ament_cmake | |
| reference_filter_dp | |
| auv_setup | |
| rclcpp | |
| rclcpp_action | |
| geometry_msgs | |
| vortex_msgs | |
| vortex_utils_ros | |
| tf2_geometry_msgs |