ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

navigation transform information problem

asked 2016-07-05 05:43:19 -0500

lfr gravatar image

updated 2016-07-06 05:23:41 -0500

Hello !

I try to run the navigation stack with a real robot (move_base + gmapping).
My problem is that when I launch my launch file which is supposed to run the move_base node and the slam_gmapping node (and load my YAML configuration files), I get completely randomly warnings which disturb the behaviour of my robot.

When I send no goal, I get this warning randomly:

Costmap2DROS transform timeout ... could not get robot pose, cancelling pose reconfiguration

And when I send a goal, I get this warning randomly:

Unable to get starting pose of robot, unable to create global plan

When the first warning appear, the robot begins to get an hesitating behaviour with very slow speeds.
I didn't find anywhere a real solution to this problem.
If anyone could help me, I would be very grateful,
lfr

edit retag flag offensive close merge delete

Comments

Could you post your launch file?

Icehawk101 gravatar image Icehawk101  ( 2016-07-05 08:17:35 -0500 )edit

Thanks for answering me. The launch files are correct. I found the problem is the communication between the robot and my computer. There are some packets which are loss.

lfr gravatar image lfr  ( 2016-07-06 05:25:00 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-07-06 05:34:29 -0500

lfr gravatar image

Hello,

I give this answer because it is possible that someone else have the same problem.

I found that the problem is with the communication between the robot and my computer.
Indeed, some packets are loss (I saw that in trying to ping the robot). And each time I lose a packet, this is exactly when the second warning appear.
Moreover, sometimes, the delay in communication exceeds my transform_tolerance (I saw that with the ping too) and this is when the first warning appear.

The only solution I can see is to improve the communication way.

I hope it can help someone to find the problem,
lfr

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-07-05 05:43:19 -0500

Seen: 404 times

Last updated: Jul 06 '16