| marti-status-msgs |
1.2.0-1 |
marti_status_msgs |
meta-ros2-dashing |
| marti-status-msgs |
1.2.0-1 |
marti_status_msgs |
meta-ros2-eloquent |
| marti-status-msgs |
1.2.0-1 |
marti_status_msgs |
meta-ros2-foxy |
| marti-status-msgs |
1.3.0-3 |
marti_status_msgs |
meta-ros2-humble |
| marti-visualization-msgs |
0.10.0-2 |
marti_visualization_msgs |
meta-ros1-melodic |
| marti-visualization-msgs |
1.2.0-1 |
marti_visualization_msgs |
meta-ros2-dashing |
| marti-visualization-msgs |
1.2.0-1 |
marti_visualization_msgs |
meta-ros2-eloquent |
| marti-visualization-msgs |
1.2.0-1 |
marti_visualization_msgs |
meta-ros2-foxy |
| marti-visualization-msgs |
1.3.0-3 |
marti_visualization_msgs |
meta-ros2-humble |
| marvelmind-nav |
1.0.11-1 |
Marvelmind local navigation system |
meta-ros1-melodic |
| marvelmind-ros2 |
1.0.2-3 |
Marvelmind ROS2 package |
meta-ros2-humble |
| marvelmind-ros2-msgs |
1.0.2-1 |
Marvelmind message package for ROS2 |
meta-ros2-humble |
| master-discovery-fkieblacklisted |
0.8.12 |
Discover the running ROS Masters in local network. The discovering is done by sending an echo heartbeat messages to a defined multicast group. The alternative is to use a zeroconf/avahi daemon to register the ROS master as service and discover other ROS masters. |
meta-ros1-melodic |
| master-sync-fkieblacklisted |
0.8.12 |
Synchronize the local ROS master to the remote masters discovered by master_discovery_fkie node. The registration of topics and services is only perform by local ROS master. |
meta-ros1-melodic |
| mav-comm |
3.3.2 |
Contains messages and services for MAV communication |
meta-ros1-melodic |
| mav-msgs |
3.3.2 |
Package containing messages for communicating with rotary wing MAVs |
meta-ros1-melodic |
| mav-planning-msgs |
3.3.2 |
Messages specific to MAV planning, especially polynomial planning. |
meta-ros1-melodic |
| mavlink |
2021.10.10-1 |
MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). |
meta-ros1-melodic |
| mavlink |
2020.11.11-1 |
MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). |
meta-ros2-eloquent |
| mavlink |
2021.10.10-1 |
MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). |
meta-ros2-foxy |
| mavlink |
2021.10.10-1 |
MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). |
meta-ros2-rolling |
| mavlink |
2021.9.9-1 |
MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). |
meta-ros2-rolling |
| mavlink |
2022.8.8-1 |
MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). |
meta-ros2-humble |
| mavros |
1.9.0-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros1-melodic |
| mavros |
2.0.3-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-foxy |
| mavros |
2.0.3-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-rolling |
| mavros |
2.0.4-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-rolling |
| mavros |
2.3.0-1 |
MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. |
meta-ros2-humble |
| 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.0.4-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-rolling |
| mavros-extras |
2.3.0-1 |
Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-humble |
| 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.0.4-1 |
mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-rolling |
| mavros-msgs |
2.0.3-1 |
mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-rolling |
| mavros-msgs |
2.3.0-1 |
mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. |
meta-ros2-humble |
| mbedtls |
2.16.6 |
Lightweight crypto and SSL/TLS library |
meta-networking |
| 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-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-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-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-mesh-coreblacklisted |
1.0.1-1 |
The mbf_mesh_core package |
meta-ros1-melodic |
| mbf-mesh-navblacklisted |
1.0.1-1 |
The mbf_mesh_nav package |
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-melodic |
| mbf-recovery-behaviors |
0.1.0-1 |
The mbf_recovery_behaviors package |
meta-ros1-melodic |
| mbf-simple-nav |
0.4.0-1 |
The mbf_simple_nav package contains a simple navigation server implementation of Move Base Flex (MBF). The simple navigation server is bound to no map representation. It provides actions for planning, controlling and recovering. MBF loads all defined 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. It tries to load the defined plugins which implements the defined interfaces in <a href="wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. |
meta-ros1-melodic |
| mbf-utility |
0.4.0-1 |
The mbf_utility package |
meta-ros1-melodic |
| mbusd |
0.4.1+gitX |
Open-source Modbus TCP to Modbus RTU (RS-232/485) gateway |
meta-tanowrt |
| mcap-vendor |
0.5.0-1 |
mcap vendor package |
meta-ros2-humble |
| mcl-3dl |
0.6.0-1 |
3-D/6-DOF localization for mobile robots with 3-D LIDAR(s) |
meta-ros1-melodic |