Dropped sensor messages in Navigation Stack

asked 2012-02-07 23:39:07 -0600

rohan_k
31 ●5 ●6 ●10

updated 2012-02-08 07:18:51 -0600

Hi,

I'm trying to run the navigation stack on my own robot. I have run through the RobotSetup Tutorial and have made sure I am publishing everything I am required to.

I have published the tfs such that I have a tree that looks like map-->odom-->base_link-->base_sonarA (which is the sonar sensor I am using - data being published as a LaserScan message). However I am getting this error:

[ WARN] [1328706898.660733327]: MessageFilter [target=/map /base_sonarA ]: Dropped 100.00% of messages so far. Please turn the [ros.costmap_2d.message_notifier] rosconsole logger to DEBUG for more information.
[ WARN] [1328706899.306808499]: MessageFilter [target=/odom /base_sonarA ]: Dropped 100.00% of messages so far. Please turn the [ros.costmap_2d.message_notifier] rosconsole logger to DEBUG for more information.

Then when I turn on DEBUG as suggested, I get this:

[DEBUG] [1328707633.947505776]: MessageFilter [target=/map /base_sonarA ]: Removed oldest message because buffer is full, count now 50 (frame_id=base_sonarA, stamp=0.000000)
[DEBUG] [1328707633.956223854]: MessageFilter [target=/map /base_sonarA ]: Added message in frame base_sonarA at time 0.000, count now 50
[DEBUG] [1328707633.964573867]: MessageFilter [target=/odom /base_sonarA ]: Removed oldest message because buffer is full, count now 50 (frame_id=base_sonarA, stamp=0.000000)
[DEBUG] [1328707633.984351031]: MessageFilter [target=/odom /base_sonarA ]: Added message in frame base_sonarA at time 0.000, count now 50`

When I run rosrun tf tf_echo map base_sonarA I get:

At time 1328707774.058
- Translation: [2.283, 0.489, -0.035]
- Rotation: in Quaternion [0.000, 0.000, 0.829, 0.560]
        in RPY [0.000, -0.000, 1.953]

So the transform exists, but from what other threads have told me, this means the transform on the data is not happening.

As a result of this, I can't use the sensor data and hence the stack doesn't work.

Does anyone know what the problem could be?

Thanks!

EDIT 1:

Sample message from sonar sensor (LaserScan message) using rostopic echo sonar_dataA )

---
header: 
  seq: 821
  stamp: 
    secs: 0
    nsecs: 0
  frame_id: base_sonarA
angle_min: 0.0
angle_max: 10.0
angle_increment: 0.10000000149
time_increment: 1.0
scan_time: 0.10000000149
range_min: 0.00999999977648
range_max: 1.45000004768
ranges: [1.4827419519424438]
intensities: []
---

edit retag flag offensive close merge delete

add a comment

1

answered 2012-02-08 07:06:46 -0600

ahendrix

47576 ●179 ●367 ●662 http://namniart.com/

updated 2012-02-08 07:28:33 -0600

There are a couple of possibilities here:

Something is wrong with your tf tree, and it isn't possible to transform sonar data into the base frame
Your sonar data is being published with the wrong frame in the header
Your sonar data is being published with the wrong timestamp in the header

I suspect one of the latter two problems; if you can capture and post a sample sonar message, that should narrow things down.

EDIT:

After looking at your sample message, this is definitely due to improper timestamps in your sonar messages. It should be relatively simple to set header.stamp to the current time for every message.

This is a problem because tf works in both space and time; since some frames move with time, it buffers a short history so that it can transform scan data taken a few seconds ago between moving frames. The buffer is relatively short, so it doesn't have enough information to transform data that's more than a few seconds old, much less all the way back to unix time 0 (Dec 31, 1969!).

edit flag offensive delete link

Comments

I've posted a rostopic echo of the LaserScan message and as you say there looks to be an issue with the timestamp on each message. I'll have a look at where I populate the message and repost.

rohan_k ( 2012-02-08 07:21:33 -0600 )edit

FIXED! the error was that I had the timestamp in making the LaserScan message = ros::Time(); when it needed to be ros::Time::now(); for some reason. 100 more errors to deal with, but that one done! Thanks very much for the help!

rohan_k ( 2012-02-08 07:40:31 -0600 )edit

add a comment

1

answered 2012-02-08 00:59:08 -0600

DimitriProsser

11163 ●79 ●116 ●169

The navigation stack relies on the "base_footprint" tf frame. This frame represents the ground point directly below the robot's center of mass or center of rotation. This frame should be equivalent in the z-direction to the map frame. Your tf tree does not contain this frame, so that very well could be your problem.

edit flag offensive delete link

Comments

Adding base_footprint to the tree (such that it now looks like map-->odom-->base_footprint-->base_link-->base_sonarA) didn't change anything unfortunately. I published a fixed tf of 0 0 0 0 0 0 between base_footprint and base_link. If it's so crucial, why is it not in any of the setup tutorials?

rohan_k ( 2012-02-08 05:45:50 -0600 )edit

Are you assigning a stamp to your tf to base_sonarA? You need to timestamp it, but it looks like it's zero

DimitriProsser ( 2012-02-08 06:15:35 -0600 )edit

I run: broadcaster.sendTransform(tf::StampedTransform( tf::Transform(tf::Quaternion(0, 0, sin((0*M_PI)/360), cos((0*M_PI)/360)), tf::Vector3(0.05, 0.00, -0.035)), ros::Time::now(),"base_link", "base_sonarA")); so I believe so. I don't know why it says it's zero as you pointed out however

rohan_k ( 2012-02-08 06:51:00 -0600 )edit

add a comment

Dropped sensor messages in Navigation Stack

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

Dropped sensor messages in Navigation Stack edit

2 Answers

Comments

Comments

Question Tools

Stats

Related questions

Dropped sensor messages in Navigation Stack