| mavros |
1.20.1-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros1-noetic |
| mavros |
2.0.4-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-galactic |
| mavros |
2.14.0-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-humble |
| mavros |
2.14.0-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-jazzy |
| mavros |
2.14.0-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-kilted |
| mavros-examples |
2.14.0-1 |
Example scripts demonstrating MAVROS usage |
meta-ros2-rolling |
| mavros-examples |
2.14.0-1 |
Example scripts demonstrating MAVROS usage |
meta-ros2-humble |
| mavros-examples |
2.14.0-1 |
Example scripts demonstrating MAVROS usage |
meta-ros2-jazzy |
| mavros-examples |
2.14.0-1 |
Example scripts demonstrating MAVROS usage |
meta-ros2-kilted |
| mavros-extras |
1.9.0-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros1-melodic |
| mavros-extras |
2.14.0-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-rolling |
| mavros-extras |
1.20.1-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros1-noetic |
| mavros-extras |
2.0.4-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-galactic |
| mavros-extras |
2.14.0-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-humble |
| mavros-extras |
2.14.0-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-jazzy |
| mavros-extras |
2.14.0-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-kilted |
| mavros-msgs |
1.9.0-1 |
mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros1-melodic |
| mavros-msgs |
2.0.3-1 |
mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-foxy |
| mavros-msgs |
2.14.0-1 |
Messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-rolling |
| mavros-msgs |
1.20.1-1 |
mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros1-noetic |
| mavros-msgs |
2.0.4-1 |
mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-galactic |
| mavros-msgs |
2.14.0-1 |
Messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-humble |
| mavros-msgs |
2.14.0-1 |
Messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-jazzy |
| mavros-msgs |
2.14.0-1 |
Messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-kilted |
| mbedtls |
3.6.6 |
Lightweight crypto and SSL/TLS library |
meta-networking |
| mbedtls |
3.6.5 |
Lightweight crypto and SSL/TLS library |
meta-freescale |
| mbedtls |
3.6.6 |
Lightweight crypto and SSL/TLS library |
meta-voltumna |
| mbf-abstract-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros1-melodic |
| mbf-abstract-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros1-noetic |
| mbf-abstract-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros2-humble |
| mbf-abstract-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. |
meta-ros2-jazzy |
| mbf-abstract-nav |
0.4.0-1 |
The mbf_abstract_nav package contains the abstract navigation server implementation of Move Base Flex (MBF). The abstract navigation server is not bound to any map representation. It provides the actions for planning, controlling and recovering. MBF loads all defined plugins at the program start. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. |
meta-ros1-melodic |
| mbf-abstract-nav |
0.4.0-1 |
The mbf_abstract_nav package contains the abstract navigation server implementation of Move Base Flex (MBF). The abstract navigation server is not bound to any map representation. It provides the actions for planning, controlling and recovering. MBF loads all defined plugins at the program start. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. |
meta-ros1-noetic |
| mbf-abstract-nav |
1.0.5-1 |
The mbf_abstract_nav package contains the abstract navigation server implementation of Move Base Flex (MBF). The abstract navigation server is not bound to any map representation. It provides the actions for planning, controlling and recovering. MBF loads all defined plugins at the program start. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. |
meta-ros2-humble |
| mbf-abstract-nav |
1.0.5-1 |
The mbf_abstract_nav package contains the abstract navigation server implementation of Move Base Flex (MBF). The abstract navigation server is not bound to any map representation. It provides the actions for planning, controlling and recovering. MBF loads all defined plugins at the program start. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. |
meta-ros2-jazzy |
| mbf-costmap-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the CostmapPlanner, CostmapController and CostmapRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_costmap_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and binds the system to a local and a global costmap. |
meta-ros1-melodic |
| mbf-costmap-core |
0.4.0-1 |
This package provides common interfaces for navigation specific robot actions. It contains the CostmapPlanner, CostmapController and CostmapRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_costmap_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and binds the system to a local and a global costmap. |
meta-ros1-noetic |
| mbf-costmap-nav |
0.4.0-1 |
The mbf_costmap_nav package contains the costmap navigation server implementation of Move Base Flex (MBF). The costmap navigation server is bound to the <a href="wiki.ros.org/costmap_2d">costmap_2d</a> representation. It provides the Actions for planning, controlling and recovering. At the time of start MBF loads all defined plugins. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. Additionally the mbf_costmap_nav package comes with a wrapper for the old navigation stack and the plugins which inherits from the <a href="wiki.ros.org/nav_core">nav_core</a> base classes. Preferably it tries to load plugins for the new API. However, plugins could even support both <a href="wiki.ros.org/move_base">move_base</a> and <a href="wiki.ros.org/move_base_flex">move_base_flex</a> by inheriting both base class interfaces located in the <a href="wiki.ros.org/nav_core">nav_core</a> package and in the <a href="mbf_costmap_core">mbf_costmap_core</a> package. |
meta-ros1-melodic |
| mbf-costmap-nav |
0.4.0-1 |
The mbf_costmap_nav package contains the costmap navigation server implementation of Move Base Flex (MBF). The costmap navigation server is bound to the <a href="wiki.ros.org/costmap_2d">costmap_2d</a> representation. It provides the Actions for planning, controlling and recovering. At the time of start MBF loads all defined plugins. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. Additionally the mbf_costmap_nav package comes with a wrapper for the old navigation stack and the plugins which inherits from the <a href="wiki.ros.org/nav_core">nav_core</a> base classes. Preferably it tries to load plugins for the new API. However, plugins could even support both <a href="wiki.ros.org/move_base">move_base</a> and <a href="wiki.ros.org/move_base_flex">move_base_flex</a> by inheriting both base class interfaces located in the <a href="wiki.ros.org/nav_core">nav_core</a> package and in the <a href="mbf_costmap_core">mbf_costmap_core</a> package. |
meta-ros1-noetic |
| mbf-mesh-core |
1.0.1-1 |
The mbf_mesh_core package |
meta-ros1-melodic |
| mbf-mesh-core |
1.0.1-2 |
The mbf_mesh_core package |
meta-ros1-noetic |
| mbf-mesh-nav |
1.0.1-1 |
The mbf_mesh_nav package |
meta-ros1-melodic |
| mbf-mesh-nav |
1.0.1-2 |
The mbf_mesh_nav package |
meta-ros1-noetic |
| mbf-msgs |
0.4.0-1 |
The move_base_flex messages package providing the action definition files for the action GetPath, ExePath, Recovery and MoveBase. The action servers providing these action are implemented in <a href="http://wiki.ros.org/mbf_abstract_nav">mbf_abstract_nav</a>. |
meta-ros1-melodic |
| mbf-msgs |
0.4.0-1 |
The move_base_flex messages package providing the action definition files for the action GetPath, ExePath, Recovery and MoveBase. The action servers providing these action are implemented in <a href="http://wiki.ros.org/mbf_abstract_nav">mbf_abstract_nav</a>. |
meta-ros1-noetic |
| mbf-msgs |
1.0.5-1 |
The move_base_flex messages package providing the action definition files for the action GetPath, ExePath, Recovery and MoveBase. The action servers providing these action are implemented in <a href="http://wiki.ros.org/mbf_abstract_nav">mbf_abstract_nav</a>. |
meta-ros2-humble |
| mbf-msgs |
1.0.5-1 |
The move_base_flex messages package providing the action definition files for the action GetPath, ExePath, Recovery and MoveBase. The action servers providing these action are implemented in <a href="http://wiki.ros.org/mbf_abstract_nav">mbf_abstract_nav</a>. |
meta-ros2-jazzy |
| mbf-recovery-behaviors |
0.1.0-1 |
The mbf_recovery_behaviors package |
meta-ros1-melodic |
| mbf-simple-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the SimplePlanner, SimpleController and SimpleRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_simple_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and there is no binding to a map representation. |
meta-ros2-humble |
| mbf-simple-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the SimplePlanner, SimpleController and SimpleRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_simple_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and there is no binding to a map representation. |
meta-ros2-jazzy |