-
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
Getting some problems running the gazebo demo(mapping) #32
Comments
This makes the hector_mapping Gazebo demo work with the instructions from the README (see #32).
For the demo do work, you don't even need to install anything into your catkin workspace; you can install everything from binaries like this: sudo apt install ros-kinetic-mir-robot ros-kinetic-hector-mapping Then, simply follow the steps from the section "Gazebo demo (mapping)" in the README. I just tried them, and they worked, except that I found a small bug. You have to add ### gazebo:
roslaunch mir_gazebo mir_maze_world.launch
rosservice call /gazebo/unpause_physics # or click the "start" button in the Gazebo GUI
### mapping:
roslaunch mir_navigation hector_mapping.launch.xml
### navigation:
roslaunch mir_navigation move_base.xml with_virtual_walls:=false local_planner:=dwb
rviz -d $(rospack find mir_navigation)/rviz/navigation.rviz I've just pushed a commit that makes this fix unnecessary in the future. |
Nice, i will try this! Thank you |
@mintar I works when running the nodes, but the sensor don't map the environment, no obstacles are showing up. One possibility is that is the graphic card is to slow and memory overflow.. Got When running the move_base launch file. Either way, i moved around with the robot and no mapping was done. the only thing that i got was. I followed your directives, attaching result from rviz and gazebo can be seen below. |
Could you run the following command and paste the result (while everything is running)? rostopic echo -n1 /scan Also, can you visualize the "scan" topic in RViz? Probably your guess is right, and the graphics card is not sufficient for Gazebo. This has been reported several times before: #1 |
@mintar Yes. it was the graphic cards. Got exactly like result generated by the attached link. I will test the same with a nvidia graphic card. Thank you @mintar! very helpful. |
Hi guys!
I having a problem when running Gazebo demo(mapping). I started looking at this fork yesterday and when i runned the hector_mapping launch file it could not run. I looked at the file and saw the hector_mapping node tag so did some research. This ended with finding the fork of hector_slam.
I cloned it into my catkin_ws and this made it possible for the launch file to run.
At this point all things worked. In Gazebo mir_maze_world was up and running
I continued by running commands of #navigation directives and here i get into some problems when i run the navigation.rviz command, rviz opens and when i either run the 2D Nav or using the controller. rviz shows only the mir robot and some shitty background of the potential map.
But in the Gazebo, the mir robot is running but nothing happens with mapping in rviz?
What should I do to get mapping started??
I attached pictures of rviz and gazebo.
The text was updated successfully, but these errors were encountered: