| 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-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-noetic |
| mbf-mesh-core |
1.0.1-2 |
The mbf_mesh_core package |
meta-ros1-noetic |
| 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-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-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 |
| 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-noetic |
| mbf-simple-nav |
1.0.5-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-ros2-humble |
| mbf-simple-nav |
1.0.5-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-ros2-jazzy |
| mbf-test-utility |
1.0.5-1 |
Contains tools that help with testing move base flex modules. This package should only be used as a test dependency. If some tool shall be used in production, move it into mbf_utility for example. |
meta-ros2-humble |
| mbf-test-utility |
1.0.5-1 |
Contains tools that help with testing move base flex modules. This package should only be used as a test dependency. If some tool shall be used in production, move it into mbf_utility for example. |
meta-ros2-jazzy |
| mbf-utility |
0.4.0-1 |
The mbf_utility package |
meta-ros1-noetic |
| mbf-utility |
1.0.5-1 |
The mbf_utility package |
meta-ros2-humble |
| mbf-utility |
1.0.5-1 |
The mbf_utility package |
meta-ros2-jazzy |
| mbpoll |
1.5.2 |
Command line utility to communicate with ModBus slave (RTU or TCP) |
meta-oe |
| mcap-vendor |
0.33.1-1 |
mcap vendor package |
meta-ros2-rolling |
| mcap-vendor |
0.15.16-1 |
mcap vendor package |
meta-ros2-humble |
| mcap-vendor |
0.26.11-1 |
mcap vendor package |
meta-ros2-jazzy |
| mcap-vendor |
0.32.0-2 |
mcap vendor package |
meta-ros2-kilted |
| mcl-3dl |
0.6.4-1 |
3-D/6-DOF localization for mobile robots with 3-D LIDAR(s) |
meta-ros1-noetic |
| mcl-3dl-msgs |
0.6.0-1 |
The mcl_3dl message definition package |
meta-ros1-noetic |
| md4c |
0.5.2 |
Markdown for C |
meta-oe |
| mecanum-drive-controller |
6.6.0-1 |
Implementation of mecanum drive controller for 4 wheel drive. |
meta-ros2-rolling |
| mecanum-drive-controller |
2.53.1-1 |
Implementation of mecanum drive controller for 4 wheel drive. |
meta-ros2-humble |
| mecanum-drive-controller |
4.40.1-1 |
Implementation of mecanum drive controller for 4 wheel drive. |
meta-ros2-jazzy |
| mecanum-drive-controller |
5.15.1-1 |
Implementation of mecanum drive controller for 4 wheel drive. |
meta-ros2-kilted |
| mecanum-gazebo-plugin |
0.2.0-1 |
Plugin which uses directional friction to simulate mecanum wheels. |
meta-ros1-noetic |
| media-export |
0.3.0-1 |
Placeholder package enabling generic export of media paths. |
meta-ros1-noetic |
| mender |
5.1.0 |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender |
5.0.3 |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender |
5.0.1 |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender |
5.0.0 |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender |
5.0.5 |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender |
5.0.2 |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender |
5.0.4 |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender |
master-gitX |
Mender tool for doing OTA software updates. |
meta-mender-core |
| mender-flash |
1.0.1 |
Utility to flash block devices. |
meta-mender-core |
| mender-flash |
1.1.0 |
Utility to flash block devices. |
meta-mender-core |
| mender-flash |
master-gitX |
Utility to flash block devices. |
meta-mender-core |
| mender-flash |
1.0.2 |
Utility to flash block devices. |
meta-mender-core |
| mender-flash |
1.0.0 |
Utility to flash block devices. |
meta-mender-core |
| menge-vendor |
1.3.0-1 |
Menge is a powerful, cross-platform, modular framework for crowd simulation developed at the University of North Carolina - Chapel Hill. This package includes the core simulation part of origin menge package, with a bit modification for crowd simulation in gazebo and ignition gazebo. |
meta-ros2-rolling |
| menge-vendor |
1.0.1-1 |
Menge is a powerful, cross-platform, modular framework for crowd simulation developed at the University of North Carolina - Chapel Hill. This package includes the core simulation part of origin menge package, with a bit modification for crowd simulation in gazebo and ignition gazebo. |
meta-ros2-humble |
| menge-vendor |
1.2.1-1 |
Menge is a powerful, cross-platform, modular framework for crowd simulation developed at the University of North Carolina - Chapel Hill. This package includes the core simulation part of origin menge package, with a bit modification for crowd simulation in gazebo and ignition gazebo. |
meta-ros2-jazzy |