-
Notifications
You must be signed in to change notification settings - Fork 9
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
Cartographer SITL SLAM not working, VisOdom: not Healthy #24
Comments
Thank you for reporting. I will give this a try soon and report back if I can reproduce or fix this problem. |
Any tips?
|
try xhost +local:* |
The problem is that the tf topic changed several times in ardupilot. Since ArduPilot/ardupilot#25384 ardupilot_dds is listening to |
I have setup the simulation exactly as specified in the repository. (dependencies, param settings etc)
mavproxy shows the message VisOdom: not Healhy
to reproduce the issue I have prepared a Dockerfile (will need Nvidia container toolkit for GPU rendering):
bash script to build image:
bash script to launch simulation using Nvidia graphics card:
otherwise:
start mavproxy
Then parameters are set using mavproxy using the commands
Then, SITL simulation is restarted.
The text was updated successfully, but these errors were encountered: