-
Notifications
You must be signed in to change notification settings - Fork 157
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
Gazebo demo - mapping #52
Comments
OK, I just saw that this issue or similar was already treated in #32 (closed). I will give it a try. |
In the mapping case it does not work within the VM. Is there any setting that can be changed in order to get a correct /scan message? |
Thanks, fixed!
I think I have solved the issue. I've committed a fix for this problem, so please pull the latest code and let me know whether it works! |
Thanks for the feedback. Glad I could help! |
Hi,
I was following the instructions for mapping with the mir100 and I encountered some problems. First, under ### mapping: I think it should be
roslaunch mir_navigation hector_mapping.launch
without the xml extension.But this is a minor issue. I have troubles with the command under # navigation:
roslaunch mir_navigation move_base.xml with_virtual_walls:=false
I get this output in the terminal
Then I run
rviz -d $(rospack find mir_navigation)/rviz/navigation.rviz
In the rviz window no black lines or dots are drawn and while commanding the robot to move this does move in gazebo but nor in rviz.
I tested this on Ubuntu 16.04 / Kinetic Kame respectively 18.04 / Melodic, both running on VMWare Fusion 11.5 on a Mac.
I tried to find out what it could be, but with no success.
Thanks in advance
The text was updated successfully, but these errors were encountered: