-
Notifications
You must be signed in to change notification settings - Fork 151
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
Recovery Backup Not working #15
Comments
Hi Phil, This sounds more of a Nav2 related problem. Perhaps you could post in ROS answers instead. |
Sure I will post over there.
…On Fri, Dec 24, 2021, 12:33 AM Juan Miguel Jimeno ***@***.***> wrote:
Hi Phil,
This sounds more of a Nav2 related problem. Perhaps you could post in ROS
answers instead.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPS6NAR4V2MA7VWE7OSWTUSQA35ANCNFSM5KTMIVMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Closing this for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I am running Linorobot2 on Mecanum, NVIDIA Jetson computer with Teensy 4.1.
When my robot is stuck in a corner, I see it enters the recovery tree and does the spin and wait actions; however it has never performed the backup function and as a result it usually ends up aborting after a few tries and I have to restart the entire navigation stack.
Based on the Nav2 documentation it looks all pretty default for the parameters for recovery server so not sure why it wont try backup when it tries spin and wait pretty well
If it does abort is there any reason that I need to completely restart the entire Nav stack, rather than it being able to accept a new goal?
The text was updated successfully, but these errors were encountered: