-
Notifications
You must be signed in to change notification settings - Fork 30
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
Firmware bug for ROS2 Foxy #53
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am facing the same issue of hardware.launch failing to execute. When trying to back trace the issue, I realized that after successfully uploading the openCR firmware, the robot does not go to the home configuration as observed with ROS1 Neotic. Hence, I believe that might be an untraceble (missed) bug in ROS2 firmware for turtlebot3_manipulation. Any suggestions on how can I fix this?
The text was updated successfully, but these errors were encountered: