Open Source RoboticsRobots, software & learning

ros2_control

Software

ROS 2 framework for managing controllers and hardware interfaces, with mock components for checking integration before physical hardware trials. [1]

Installation & first result →Official websiteGetting started

For
ROS 2 developers implementing or integrating robot hardware drivers [1]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

ros2_control connects controller management to robot-specific hardware interfaces. Its controller manager handles controller lifecycles and access to those interfaces, while hardware components are described as System, Sensor or Actuator types. This review preserves a development commit and separately captures the current Rolling getting-started guide; the chosen ROS distribution still determines the installation and compatible branch. [1] [2] [5] [8] [9]

Is this for you?

Workflows
  • Describe hardware and interfaces in URDF
  • Configure and activate controller plugins
  • Check launch/controller integration with mock hardware
  • Integrate real hardware and measure timing under its actual workload

Editorial workflow based on documented component architecture; physical timing not measured.

[5] [6] [7] · Editorial assessment

Known limitations
  • Mock components normally mirror commands into idealized states; this does not validate physical dynamics
  • Real-time scheduling depends on host permissions and kernel/hardware conditions
  • Fallback activation depends on interface availability
  • Pinned development commit and current Rolling guide are separately dated evidence

Documented limitations plus source-scope clarification.

[5] [7] [9] · Editorial assessment

What you need

Dependencies
  • Matching ROS 2 distribution and ros2_control branch/packages
  • ros2_controllers for the documented packaged controller route
  • Robot-specific hardware plugin, URDF and controller configuration

[1] [5] [6] [9]

Installation & first result

Open the upstream getting-started guide [9] · Project documentation [1] [9]

  • Select matching ROS 2 distribution and packages
  • Provide the robot description and hardware plugin
  • Configure controller types and YAML parameters
  • Use mock_components/GenericSystem to exercise integration
  • Test physical hardware timing and failure handling separately

Editorial sequence, not a reproduced installation.

[1] [5] [6] [7] [9] · Editorial assessment

Installation

Rolling guide provides Ubuntu apt and RHEL dnf packages for ros2_control plus ros2_controllers; source route imports distribution-specific repositories, resolves dependencies with rosdep and builds with colcon.

[9]

Hardware, models & data

Interfaces
  • Hardware command and state interfaces
  • Controller-manager lifecycle and ROS services
  • System, Sensor and Actuator component types

[5] [6] [8]

File formats
  • URDF XML with ros2_control tags
  • ROS 2 YAML controller parameters

[5] [6]

Project notes

Describe the robot and select the software route

The Rolling guide describes Ubuntu and RHEL binary packages for both ros2_control and ros2_controllers. Its source route imports a distribution-specific repository set, resolves dependencies with rosdep and builds with colcon. These instructions were inspected but not run here. The repository README also lists separate branches and documentation for several ROS distributions, so a user should choose the matching set before combining examples. [1] [9]

Hardware is described in URDF using ros2_control tags, a hardware plugin and command/state interfaces. Controller parameters use ROS 2 YAML. Every joint named in those control tags must also exist in the URDF received by the controller manager. The manager documentation states that reloading the URDF is not yet supported in this snapshot. [5] [6]

Mock hardware checks integration, not the mechanism

mock_components/GenericSystem supplies idealized hardware behavior, including mirroring commands into states. This is useful for checking controllers, broadcasters, launch files and integrations without access to the real robot. It can reveal configuration errors, but it does not establish the physical mechanism's response, electrical behavior or timing. [7]

When moving to hardware, the controller-manager guide discusses loop jitter, scheduling permissions and kernel choices. The main thread attempts FIFO scheduling at priority 50, which ordinary users may not be permitted to request. Neither the presence of that setting nor a working mock configuration proves that a particular host and driver meet the application's timing requirements. No timing measurement was performed in this review. [5] [7]

Fallback controllers also need the required state and command interfaces to be available. The upstream guide recommends testing the fallback strategy in simulation before using it on a physical robot. Treat lifecycle and failure behavior as part of the integration, alongside normal command flow. [5]

Scope of the open source

The reviewed repository declares Apache-2.0. That covers the selected framework source and repository documentation; it does not automatically establish the licensing, completeness or performance of an independently supplied robot driver. This profile provides a documented integration route, not a qualified hardware-control installation. [1] [3]

What we checked

Source research only; no installation, physical build or performance test performed. No affiliate links added.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Sep 29, 2026 [2]
Latest release
Not established
Profile updated
Sep 30, 2026
Sources last checked
Sep 30, 2026
Next review
Oct 30, 2026
Reviewed revision
a3c9d4df3a917a58149fd71e0a744d8684e6a9bb (commit snapshot; no published stable release found) · software repository

Source files and licenses

Available project sources support research coverage; complete build and commercial qualification remain separate.

LayerAvailability / license
softwareavailable · Apache-2.0
Repository license; robot vendor drivers and external dependencies remain separate. [1] [3]
documentationavailable · Apache-2.0
Pinned repository documentation; external website is separately captured as evidence. [3] [5] [6] [7]

Control framework profile does not select a trained policy or training dataset.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1

Change history