A reverse ROS bridge for the MiR100 robot

URDF description of the MiR100 robot

Action definitions for the MiR100 robot

mini_maxwell

This package contains ros_control based robot controller for PANASONIC MINAS EtherCAT Motor Driver Control System

Meta package for minas for PANASONIC MINAS EtherCAT Motor Driver Control System

A driver for IMUs compatible the microstrain 3DM-GX2 and 3DM-GX3 protocol. Includes a heavily modified standalone driver pulled from the player distribution, and a ROS node.

micros_swarm_stage package.

micros_swarm_gazebo package.

This is a programming framework to facilitate application development involving robot swarms. It makes coding for swarms much easier by providing an adequate swarm-level abstraction, as well as tools for swarm management, various communication mechanisms and so on. It also provides essential data structures, such as Neighbor, Swarm, and Virtual Stigmergy, to the user. Most importantly, it is completely compatible with ROS Indigo and presented in the form of a C++ library, which means that all resources in the ROS ecosystem are still available to the user. It is currently extensible to Opensplice DDS.

micros_swarm package.

The micros_rtt package

This is a ROS package used for the mult-task allocation in a robot team. It is based on Multi-Agent theory and is an abstraction of ALLIANCE model. A cooperative robot team is a multi-agent robot system in essence. In the team, each robot can be seen as an intelligent agent. We have developed a prototype system by python hitherto. The nodelet-based C++ version is being developed and will be released in short time periods.

A package for path planning

An automatically generated package with all the configuration and launch files for using the mico with the MoveIt Motion Planning Framework

3D Model and URDF of the Kinova MICO Arm

message_to_tf translates pose information from different kind of common_msgs message types to tf. Currently the node supports nav_msgs/Odometry, geometry_msgs/PoseStamped and sensor_msgs/Imu messages as input. The resulting transform is divided into three subtransforms with intermediate frames for the footprint and the stabilized base frame (without roll and pitch).

Package modeling the run-time dependencies for language bindings of messages.

Lightweight communication patterns built on top of nanomsg for use in embedded scenarios where only a single socket connection is desirable.

Package modeling the build-time dependencies for generating language bindings of messages.

A set of message filters which take in messages and may output those messages at a later time, based on the conditions that filter needs met.

Placeholder package enabling generic export of media paths.

Plugin which uses directional friction to simulate mecanum wheels.

The md49_serialport package

The md49_messages package

The md49_base_controller package

The mcl_3dl message definition package

3-D/6-DOF localization for mobile robots with 3-D LIDAR(s)

The mbf_utility package

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

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

The mbf_costmap_nav package contains the costmap navigation server implementation of Move Base Flex (MBF). The costmap navigation server is bound to the

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.

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.

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.

mavros_msgs defines messages for

Extra nodes and plugins for

MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station.

MAVLink message marshaling library. This package provides C-headers and pymavlink library for both 1.0 and 2.0 versions of protocol.

Messages specific to MAV planning, especially polynomial planning.

Package containing messages for communicating with rotary wing MAVs

Contains messages and services for MAV communication

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.

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.

Marvelmind local navigation system

marti_visualization_msgs

marti_status_msgs

marti_sensor_msgs

marti_perception_msgs