-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Controller Manager not available #206
Comments
hi @jclinton830. So the connection is established well. The driver awaits To achieve this, simply press the green play button whilst holding one of the gray enabling switches on the KUKA smartPAD. In automatic mode, the robot will connect immediately. |
Hi @mhubii I am running the robot in automatic mode. I want to know why the controller manager is not available for the joint state broadcaster and the joint trajectory controller to spawn? |
the controller manager is stuck loading the When you engage the robot, the robot can switch to |
Hi,
I am currently running hardware.launch from the humble branch to bring up a real robot. I made sure to setup the robot's client as described in the doc. However, there seems to be a problem between the lbr_system_interface and ros2_control because even though the controller_manger node appears in the ros2 node list, the controller_manager is not available for the joint_state_broadcaster and the joint_trajectroy_controller to spawn properly.
See the below log.
The text was updated successfully, but these errors were encountered: