![]() |
AutoAPMS
Resilient Robot Mission Management
|
Generic template class for executing a PX4 mode implementing the interface of a standard ROS 2 action. More...
#include <auto_apms_px4/mode_executor.hpp>
Additional Inherited Members | |
![]() | |
ActionWrapper (const std::string &action_name, rclcpp::Node::SharedPtr node_ptr, std::shared_ptr< ActionContextType > action_context_ptr) | |
Constructor. | |
ActionWrapper (const std::string &action_name, rclcpp::Node::SharedPtr node_ptr) | |
Constructor. | |
ActionWrapper (const std::string &action_name, const rclcpp::NodeOptions &options) | |
Constructor. | |
Generic template class for executing a PX4 mode implementing the interface of a standard ROS 2 action.
The modes to be executed must be registered with the PX4 autopilot server before any action goals are sent. By default, only the standard PX4 modes may be executed, but the user may also implement custom modes using ModeBase. Refer to ModeExecutorFactory if you want to set up a ROS 2 node for executing your custom modes.
To register a ROS 2 node component that is able to execute for example the land mode when requested, the corresponding executor is implemented as follows:
auto_apms_px4
comes with ROS 2 node components for the most common standard modes and they work out of the box.ActionT | Type of the ROS 2 action. |
Definition at line 89 of file mode_executor.hpp.