Closed WyattShawDal closed 4 months ago
Please obtain a traceback for us to know where it comes from to look into: https://docs.nav2.org/tutorials/docs/get_backtrace.html
Please also edit your issue and properly fill in the template with your ROS, Nav2 versions and install methods.
Thanks for the quick reply Steve, and sorry about the post formatting. I've added Nav2 Versions to the post, installation was done through binaries.
I followed your guide to add backtracing to the navigation_launch.py from Nav2 Bringup and was able to capture the following trace:
PS Is there a nice way to enable copy-pasting from Xterm so I can send you the string. Or is the image okay?
Image is ok, I know how that goes :smile:
Please compile from source and try again so we can get a full trace, this unfortunately isn't detailed enough to tell us much of anything. It might very well be that that CPU is functionally too old to run the SIMD CPU accelerated optimizations which MPPI requires if its a 5th generation CPU (that's nearly 10 years old)
Thanks Steve, I thought it looked a little bit limited.
I'll give compiling from source another go tomorrow morning. Would that require purging the current Nav2 install and then going through the build from source process to replace it?
In the mean time, are there any less compute heavy options that might still provide better results for dynamic obstacle avoidance than the DWB controller that you know of?
Thanks again for your help.
Would that require purging the current Nav2 install and then going through the build from source process to replace it?
You don't have to purge it, you can just build, but purging wouldn't hurt and take like 30s to reinstall after. The build itself is what takes the time (hopefully over a lunch / coffee break).
After discussion with my team and looking at the timelines I'll have to pause any investigation into this, but if I get a chance in the future I will look into it further.
Thank you for your help anyway.
Error when running
Issue Information
Hi all, I'm working on switching my Robot from running the DWB Controller to the MPPI Controller. Our Robot is required to navigate a course with dynamic obstacles, so I wanted to see if MPPI would offer more control and better performance in the course. I was able to use and tune the controller on my ThinkPad running the same version of Linux as my robot in a Gazebo simulation. However, when running the same code on my robot the Controller server is unable to find the inflation layer.
The robot is being ran from a BeeLink Mini PC https://www.bee-link.com/products/beelink-minis-12-pro-intel-n100-processor
Upon investigating this error further I found that the TF2 Map frame is now missing
I cannot find a reason for this failure when working across the two devices. Below are the Params file and launch file. Thanks for any suggestions in identifying this issue.
And the Launch File