ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2016-04-19 14:54:56 -0500 | received badge | ● Famous Question (source) |
2016-04-19 09:07:49 -0500 | answered a question | Gmapping with a priori map I think this can answer my question about using gmapping with a priori map. |
2016-04-19 09:07:13 -0500 | received badge | ● Editor (source) |
2016-04-14 09:44:58 -0500 | commented answer | Gmapping with a priori map If i use it in gazebo the localization is almost perfect, but it has some problems when i use it to the real robot... Does the amcl use odometry or it only uses the information from the laser? |
2016-04-14 08:52:32 -0500 | commented answer | Gmapping with a priori map I've tried that solution, but it doesn't seems the best solution for navigation because the localization for amcl is poor with an a priori map. I followed this link for configuration: http://www.openrobots.org/morse/doc/1... |
2016-04-13 18:50:56 -0500 | commented question | Gmapping with a priori map Yes, i'm referring to that question. It has more than 5 years and i'm hoping that someone has resolved this problem since then. |
2016-04-13 18:22:00 -0500 | received badge | ● Notable Question (source) |
2016-04-13 07:13:40 -0500 | received badge | ● Popular Question (source) |
2016-04-12 11:46:57 -0500 | asked a question | Gmapping with a priori map Hi, guys! I know that this question has been e answered before, but it was some years ago! Since then was this ever developed or something similar? I'm asking this, because gmapping was the best package to use for navigation but it has the disadvantage of not working for long-term navigation (everytime i need to use it, i have to map a new environment). I searched for a different solution for navigating with hokyuo and odometry, but gmapping is the best one to build the map and navigate using move_base. Can anyone of you help me please? Thanks. |
2016-04-10 08:59:58 -0500 | received badge | ● Famous Question (source) |
2016-03-17 03:30:10 -0500 | received badge | ● Notable Question (source) |
2016-02-26 01:44:41 -0500 | received badge | ● Notable Question (source) |
2016-02-25 12:20:03 -0500 | received badge | ● Popular Question (source) |
2016-02-25 05:05:29 -0500 | asked a question | move_base documentation Is there any kind of documentation describing the move_base package besides http://wiki.ros.org/move_base ? I really want to understand how does it work. |
2016-02-25 05:01:08 -0500 | commented question | Clear map around the robot i'm doing both at the same time |
2016-02-25 04:59:27 -0500 | received badge | ● Famous Question (source) |
2016-02-25 04:02:34 -0500 | received badge | ● Popular Question (source) |
2016-02-19 09:29:51 -0500 | received badge | ● Enthusiast |
2016-02-16 13:18:43 -0500 | asked a question | Clear map around the robot Hi, guys! I'm using hector_mapping with an hokuyo UTM-30lx to generate a map for navigation but i'm having some issues that i need to solve before continuing with some other stuff. At first, the environment is perfectly mapped but it can have some irregularities that are causing problems to the navigation of the robot. They are like noise due to some person passing or something like that and they stay in the map and don't erase. So the robot thinks it can't move forward or rotate due to an obstacle even if there is nothing in that place. My question is if it's possible to "clear" this imperfections dynamically or update the map without this. |
2016-02-15 08:17:51 -0500 | received badge | ● Famous Question (source) |
2015-11-21 15:22:55 -0500 | received badge | ● Notable Question (source) |
2015-11-20 14:03:11 -0500 | answered a question | Problems visualizing robotmodel and tf's of urdf model in rviz Deleting the base_footprint link and the joint for base_link and base_footprint as well as changing parameters for the gazebo plugin referred to the odometry, seems to solve the problem. Thank you all ;-) |
2015-11-20 12:20:14 -0500 | commented question | Problems visualizing robotmodel and tf's of urdf model in rviz no, there are no errors... even in gazebo i got no errors |
2015-11-20 12:13:22 -0500 | received badge | ● Popular Question (source) |
2015-11-20 11:37:30 -0500 | commented question | Problems visualizing robotmodel and tf's of urdf model in rviz here it is... |
2015-11-19 11:52:37 -0500 | asked a question | Problems visualizing robotmodel and tf's of urdf model in rviz Hi! I have build my own robot on sketchup, created an urdf file for it with plugins for the laser (libgazebo_ros_laser.so) and for the odometry (libgazebo_ros_p3d.so) and i'm simulating an navigation with it in gazebo. Until here it's almost 100% correct... I run rviz to visualize what is happening with the sensors, tf's, etc... I just run rviz in command line and then i add what i need in the left bar (tf's, LaserScan, RobotModel and map). Problems: 1 - i can't see correctly the tf's of my robot that are "continuous"; 2 - i can't see the robot model I think i' having this problem due to the type of the joints that are "continuous", but i have to use this for the odometry plugin for gazebo. Maybe is some problem on the joint_state_publisher, i don't know. Do i have to create any kind of a launch file to launch rviz with joint_state_publisher too, just like for gazebo? And why can't i see the RobotModel in rviz for my model, even if the joints are fixed? Maybe because it was designed in Sketchup? Here is my model in urdf. <robot name="guide_robot"> (more) |
2015-11-19 11:17:42 -0500 | received badge | ● Notable Question (source) |
2015-11-19 11:17:41 -0500 | received badge | ● Supporter (source) |
2015-10-23 05:08:45 -0500 | received badge | ● Popular Question (source) |
2015-10-22 10:13:27 -0500 | commented answer | Problems linking hokuyo_node to hector_slam and showing data on rviz Thank you for your answer! You were right i was not quite especific, sorry about that. I resolved my problem simply by modifying the hector_mapping launch file, changing the base_frame to "laser" and pub_map_odom_transform to "false". Now i can see in rviz the position and orientation of the laser. |
2015-10-22 10:08:24 -0500 | received badge | ● Scholar (source) |
2015-10-21 13:01:36 -0500 | asked a question | Problems linking hokuyo_node to hector_mapping Sorry but i'm new to ros and i'm having problems linking the data received by hokuyo_node and to hector_mapping. My goal is show the pose of the LIDAR in rviz using the data received by the hokuyo (the LIDAR isn't connected to a robot yet, it is just on a table, i'm rotating it so i cant see the laser scan in rviz). I don't know if i need to create a new package for this or if i can work without it. Can someone help me? |
2015-10-21 13:01:35 -0500 | asked a question | Problems linking hokuyo_node to hector_slam and showing data on rviz Sorry but i'm new to ros and i'm having problems linking the data received by hokuyo_node and to hector_mapping. My goal is show the pose of the LIDAR in rviz using the data received by the hokuyo (the LIDAR isn't connected to a robot yet, it is just on a table, i'm rotating it so i cant see the laser scan in rviz). I don't know if i need to create a new package for this or if i can work without it. Can someone help me? |