The hector_mapping and move_base can't work together ,but cartographer can.
Hi , all :
I want to use hector_mapping and move_base to work together on the turtlebot which has a rplidar,but when I shart up move_base to get a path planning, I find move_base continuously print the alarm information,
[ WARN] [1499649044.602318070, 109.050000000]: Control loop missed its desired rate of 3.0000Hz... the loop actually took 3.1000 seconds
[ WARN] [1499649044.602556838, 109.050000000]: Map update loop missed its desired rate of 3.0000Hz... the loop actually took 2.7667 seconds
which leads to the robot path planning is not smooth. The robot dosen't move. I have already reduced update_frequency, publish_frequency of global_costmap and local_costmap. I also decrease the controll frequence of planner in move base. However, move_base still continuously output the warning information. The robot dosen't move a little.
PS: when I only use hector_mapping build a map, everything is ok. who can tell me why move_base print this warn and how to solve this problem ? Thanks.
EDIT·1： I also tried the cartographer-ros and karto with movebase. They all worked fine.
Actually, we have monitored the usage of CPU and memory when running these SLAM packages. We have the order of consumption is cartographer>karto>hector.
So we wonder why the hector mapping with the lowest usage of CPU and memory can't work together with movebase, but cartographer with the highest usage of CPU and meory can!
Hopefully anyone give us any advices!
EDIT-2
For experiments in simulator(gazebo), the hardware is with Intel® Core™ i5-6500 CPU @ 3.20GHz × 4 , memory is 15.6 GiB. We thinks such hardware is totally enough for running hector and ftc_local_planner. So it is so weird that the above warning information is output. As I am told from some questions in answers.ros.org , this is usually because the CPU power or memory is not enough for running such packages.
EDIT-3
We found new situations and asked a new question here, please move to this link. Thanks!
