Hi comunity!
When I execute "move_base" node in the local machine (the robot) I do not get any errors or warnings. But, when I run that node remotely (from my PC), after getting the message "odom received!", I get persistently the same warnings:
[ WARN] [1534427628.512533003]: Costmap2DROS transform timeout. Current time: 1534427628.5125, global_pose stamp: 1534427628.2315, tolerance: 0.2000
Could not get robot pose, cancelling reconfiguration
In both cases the configuration files used are the same. My PC and the robot clocks are synchronized using ntp.
Any idea what can be happening? Would increasing the tolerance be a good idea for solving the problem? Thanks in advance.
Pd.: The reason why I want to execute it remotely is because the CPU consumption of the robot is over 100% and I believe that is the reason why when setting a navigation goal it gets lost...And it says: "Control loop missed its desired rate of 10.0000hz navigation... the loop actually took X.XXX seconds". Amcl works fine, so I do not think localization is the problem.
↧