ros2_control

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. [S001] [S009]

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. [S005] [S006]

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. [S007]

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. [S005] [S007]

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. [S005]

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. [S001] [S003]