-
Notifications
You must be signed in to change notification settings - Fork 212
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
Error in rviz2 while sending navigation 2d goal in ros2 #521
Comments
This might be fixed via #519, since until then RViz clock and the clocks used for publishing the navigation goal are not the same, so something might go wrong there - if you could check with master that would be great. |
@pankhurivanjani seems like #519 is merged. Mind checking to see if the error is fixed? |
Sure, I will check it and provide you with the review. |
thanks! |
Hello @claireyywang ! |
By "ros2 dashing" do you mean the |
I have updated ros2. Not going into specific branch, for more information I wanted to convey I am using dashing. |
To get the latest #519 fix, you need to update your current
You might have to update packages |
Hi @claireyywang
I could not find any existing issue for this problem. Could you suggest something? |
@pankhurivanjani I'd suggest you don't build using About the issues you're seeing. The error logs you're seeing do not seem related to clock mismatch issues. At best, it's just I'll assume you're using
If everything else fails, do know that |
One last thing. This kind of questions are more appropriate for answers.ros.org, where the entire community can chime in and provide some guidance on how to proceed. There, all exchanges remain visible for others to learn from them, as opposed to left forgotten in an eventually closed issue. So I'll close this now, and encourage you to continue with the discussion over there. |
Hello!
I am working on navigation2 using ros2 dashing. While sending nav2 goal, robot isn't responding. Checking the logs lead me to this rviz2 error
I tried looking into similar issues with ros1 in other threads, some of which suggested changing queue size in laserscan, I tried that too but it didn't help.
I have done few changes from regular configuration:
Does it affect the navigation goal sending?
Any suggestion in this matter would be helpful.
Thanks and Regards,
Pankhuri
The text was updated successfully, but these errors were encountered: