-
Notifications
You must be signed in to change notification settings - Fork 83
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
fail to run controller_manager #18
Comments
Hi, |
I've used default configurations with jetson nano and version ROS foxy. I'm a beginner with ROS2 I don't know the real problem, please acknowledge the problem. I don't know the real problem.
|
Hi @ReginaldSourn, Just check that you have selected the correct branch, must be the same as your odrive firmware version. I had the same problem with the RPi board, after the branch change, everything works great. |
Thank @rgruberski!! |
@rgruberski you're right !! what I was missing is I changed only the Odrivetool version and branch version switching from
libsub also can create trouble in compiling also please make sure we use Thank @borongyuan for giving me the answer. |
@ReginaldSourn I did all the steps you mentioned, flashed the firmware, removed libusb-0.1-4 so it won't mess up with the driver yet it's not working. What are the odrive hardware configuration you mentioned? The first error when I run full output below:
My setup is ubuntu 22.04.4, |
Found the solution. |
THIS IS my controller.yaml file
This is my launch file
[ERROR] [ros2_control_node-1]: process has died [pid 28410, exit code -6, cmd '/opt/ros/foxy/lib/controller_manager/ros2_control_node --ros-args --params-file /tmp/launch_params_0nfwf8mm --params-file /home/khadas/workspace/install/odrive_bringup/share/odrive_bringup/config/odrive_controllers.yaml'].
Could any one tell me the reason why it fails?
The text was updated successfully, but these errors were encountered: