ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2016-03-20 03:31:15 -0500 | received badge | ● Student (source) |
2015-12-06 15:30:39 -0500 | received badge | ● Taxonomist |
2015-06-29 01:32:13 -0500 | received badge | ● Famous Question (source) |
2015-06-28 15:42:04 -0500 | received badge | ● Famous Question (source) |
2015-04-29 17:38:47 -0500 | received badge | ● Notable Question (source) |
2015-04-29 17:38:47 -0500 | received badge | ● Notable Question (source) |
2015-04-14 01:43:00 -0500 | received badge | ● Notable Question (source) |
2015-04-13 08:46:16 -0500 | received badge | ● Popular Question (source) |
2015-04-13 07:55:08 -0500 | answered a question | Nav2d call getmap service failed Thank you very much, this solved my problem. But now the robot is easily stuck because of the obstacles. Which parameters can I change in the costmap and navigator configuration files to decrease the obstacle influence? edit: I can only read your edit text and I see no comments. I used RVIZ to visualize the map as you said and I noticed two things: the turtlebot does a lot of circle because sometimes it isn't able to detect part of the map without obstacle: http://hpics.li/e0e94ff ( it's because of the bad laser quality) and it's not able to go between two obstacles (1m). The blue navigation line is good but not the green corrected line. I think it's because the costmap is too large for obstacles. edit_2: Finally I changed of robot and I use an Hokuyo laser instead of the Kinect. All the nav2d packages are now working well and I'm able to use the default mapper node to build a map. Thank you very much for your answers. |
2015-04-13 07:51:25 -0500 | received badge | ● Scholar (source) |
2015-04-13 02:52:27 -0500 | received badge | ● Popular Question (source) |
2015-04-11 03:14:14 -0500 | received badge | ● Enthusiast |
2015-04-10 10:05:59 -0500 | asked a question | Nav2d call getmap service failed Hello, I already asked a question here. I received no answer but I found a way to work around the problem. I'm currently still trying to use the exploration service provided by nav2d. I solved my problem of map building by changing the mapper node by the gmapping one. But now I'm still not able to call the StartMapping and StartExplore services. I got this message: "Could not get a map." I looked at the code to find the not respected condition and I found that: Have you any idea of what to do when a service doesn't work? And particularly this one? Thank you in advance for any answer! |
2015-04-10 06:46:10 -0500 | received badge | ● Supporter (source) |
2015-04-02 10:38:31 -0500 | received badge | ● Editor (source) |
2015-04-01 06:40:02 -0500 | commented question | Nav2d_karto mapper doesn't build a map Sorry for my bad english. If you need any more information to find the problem source, I can provide it. |
2015-03-31 11:08:03 -0500 | asked a question | Nav2d_karto mapper doesn't build a map Hello, I followed the nav2d tutorials to adapt it to a turtlebot. The first two tutorials work well but I have a problem with the 3rd one. I noticed that the mapper node from the nav2d_karto doesn't build a map: no frame are published and the map topic is empty. I get this message when I run the launchfile: [ WARN] [1427816737.545498816]: MessageFilter [target=map ]: Dropped 95.01% of messages so far. Please turn the [ros.rviz.message_notifier] rosconsole logger to DEBUG for more information. Sometimes it's 98% or 100% dropped. Edit: I checked the rosconsole in debug mode and I get two new messages: First message: Second message: Here is the tf tree: http://hpics.li/a627710 And the rviz screenshot related: http://hpics.li/14f0f88 Here is my launch file: <launch> </launch> and the ros.yaml related: Defines topics services and frames for all modules TF frames ROS topics ROS services Thank you in advance for any answer! |