ROS 2 / JAZZY
controller_manager
Manifest version: 4.50.0 · Upstream repository ID: ros2_control
Purpose and upstream context
Topics explicitly mentioned in the upstream description: controllers.
What to test before changing versions
Other released packages use this runtime component. For a robot image or workcell upgrade, replay a task from a real consumer and verify it with the direct runtime dependencies listed below.
Execution (25): backward_ros · controller_interface · controller_manager_msgs · diagnostic_msgs
Runtime consumers in upstream release manifests (including unindexed packages): 51 · bcr_arm_gazebo · bcr_arm_moveit_config · beckhoff_ads_bringup · canopen_ros2_controllers
- Upstream license declarations
- Apache License 2.0
- Build type
- ament_cmake
- Release repository version
- 4.50.0-1
Selection evidence, excluding generic scaffolding and test fixtures
- Qualifying runtime consumers
- 46
- Non-generic runtime dependencies
- 21
- Of these, released ROS dependencies
- 18
- Other repositories supplying these ROS dependencies
- 13
Direct dependency declarations
These are manifest declarations, not installed packages. A generic depend applies to build, export and execution. Evaluate conditions and version bounds in the target environment. An unindexed name can be a system dependency key.
Build and export (21)
Execution (25)
Testing (10)
Documentation (0)
No matching record in this snapshot
Group references (0)
No matching record in this snapshot
Direct dependency declarations · Not declared or not confirmed (19)
ros2_control_cmake· Released; no detail page in this catalogament_cmake· Released; no detail page in this catalogament_cmake_gen_version_h· Released; no detail page in this catalogament_cmake_python· Released; no detail page in this catalogbackward_ros· Released; no detail page in this catalogdiagnostic_updater· Released; no detail page in this catalogfmt· Not a released name in this snapshot; check rosdep or the source workspacestd_msgs· Released; no detail page in this cataloglaunch_testing_ros· Released; no detail page in this catalogpython3-filelock· Not a released name in this snapshot; check rosdep or the source workspacepython3-yaml· Not a released name in this snapshot; check rosdep or the source workspaceament_cmake_gmock· Released; no detail page in this catalogament_cmake_pytest· Released; no detail page in this catalogexample_interfaces· Released; no detail page in this cataloghardware_interface_testing· Released; no detail page in this cataloglaunch_testing· Released; no detail page in this cataloglaunch_testing_ament_cmake· Released; no detail page in this catalogpython3-coverage· Not a released name in this snapshot; check rosdep or the source workspaceros2_control_test_assets· Released; no detail page in this catalog
Which packages directly depend on it?
Counts cover direct declarations in this snapshot only. They are neither install counts nor the full transitive impact.
Build and export (12)
View all matches (12) ↗Execution (46)
View all matches (46) ↗Testing (36)
View all matches (36) ↗Documentation (0)
No matching record in this snapshot
Verify in your Jazzy environment
In a configured Jazzy shell, confirm the distribution and inspect the installed prefix, manifest and registered executables. Libraries and interface packages may list no executables. These commands are for local checks, not CHINZY deployment or benchmark results.
printenv ROS_DISTRO
ros2 pkg prefix controller_manager
ros2 pkg xml controller_manager
ros2 pkg executables controller_managerDownload verification checklist (CSV) ↓Jazzy distribution source
· Jazzy · 43a0316dfc39
Where this check fits in a robot project
Treat controller management, joint state publication and recording as separate acceptance items. Inspect runtime dependencies before checking control cycles, timestamps and replay evidence.