Closed joeDonuts closed 1 month ago
It turns out I encountered a problem in my CMakeLists.txt file due to discrepancies between two different sources I was following: the Articulated Robotics guide and the official ROS 2 documentation. Each source provided different codes and setups, which led to conflicts in my configuration.
For those of you experiencing similar issues, here is the CMakeLists.txt code that resolved my problem. I'll be closing this issue now, but feel free to reference the code below if you're following a similar path. CMakeLists.txt
Hi, I have the same issue,but I don't understand how can I solve it,could you please tell me more details about your solution?
Hi, I have the same issue,but I don't understand how can I solve it,could you please tell me more details about your solution?
I see that his solution is add dependencies to CMakeList.txt file like this:
find_package(rclcpp REQUIRED)
find_package(hardware_interface REQUIRED)
find_package(rclcpp_lifecycle REQUIRED)
And add config to share folder
install( DIRECTORY src launch rviz config # Add config here
DESTINATION share/${PROJECT_NAME})
try that and see whether it solves yours
I am experiencing an issue where the controller_manager services are not available, which prevents any interaction with hardware interfaces. Despite installing all necessary dependencies, reinstalling them, and ensuring that the ros2_control_node is activated first in the launch file, the problem persists. I have tested this on both my custom workspace and the publicly available articubot_one repository.
Steps to Reproduce:
Expected Outcome: The controller_manager services should be available, and the command ros2 control list_hardware_interfaces should list the available hardware interfaces.
Actual Outcome: The command ros2 control list_hardware_interfaces fails with an error: "Could not contact service /controller_manager/list_hardware_interfaces."
Both the custom workspace and the articubot_one repository exhibit the same issue under the same conditions. Here is the content of my launch file for reference import os from ament_index_python.packages import get_package_share_directory from launch import LaunchDescription from launch.actions import IncludeLaunchDescription, DeclareLaunchArgument from launch.launch_description_sources import PythonLaunchDescriptionSource from launch.substitutions import LaunchConfiguration from launch_ros.actions import Node
def generate_launch_description(): package_name = 'firebot'
Error: [spawner-6] [INFO] [1714997730.121901418] [spawner_diff_cont]: Waiting for '/controller_manager' services to be available [spawner-7] [INFO] [1714997730.152824682] [spawner_joint_broad]: Waiting for '/controller_manager' services to be available [spawner-6] [INFO] [1714997732.141807404] [spawner_diff_cont]: Waiting for '/controller_manager' services to be available [spawner-7] [INFO] [1714997732.176311279] [spawner_joint_broad]: Waiting for '/controller_manager' services to be available [spawner-6] [INFO] [1714997734.166914743] [spawner_diff_cont]: Waiting for '/controller_manager' services to be available [spawner-7] [INFO] [1714997734.205966275] [spawner_joint_broad]: Waiting for '/controller_manager' services to be available [spawner-6] [INFO] [1714997736.189367049] [spawner_diff_cont]: Waiting for '/controller_manager' services to be available [spawner-7] [INFO] [1714997736.224687879] [spawner_joint_broad]: Waiting for '/controller_manager' services to be available [spawner-6] [ERROR] [1714997738.214785799] [spawner_diff_cont]: Controller manager not available [spawner-7] [ERROR] [1714997738.257940291] [spawner_joint_broad]: Controller manager not available [ERROR] [spawner-6]: process has died [pid 15294, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner diff_cont --ros-args']. [ERROR] [spawner-7]: process has died [pid 15296, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner joint_broad --ros-args'].
Could anyone please help identify what might be causing this issue or suggest further debugging steps?