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

Revision history [back]

click to hide/show revision 1
initial version

You can see the number of dropped messages by enabling topic statistics. Read more about it here: http://wiki.ros.org/Topics#Topic_statistics

You can see the number of dropped messages by enabling topic statistics. Read more about it here: http://wiki.ros.org/Topics#Topic_statistics

Update: Pretty sure this gives the publisher's queue drop count, however. For the subscriber's drop count, you'll have to check within your own subscriber that the header.seq number is always incrementing by only one.

You can see the number of dropped messages from the __publisher's__ queue by enabling topic statistics. Read more about it here: http://wiki.ros.org/Topics#Topic_statistics

Update: Pretty sure this gives the publisher's queue drop count, however. For the subscriber's __subscriber's__ drop count, you'll have to check within your own subscriber that the header.seq number is always incrementing by only one.

You can see the number of dropped messages from the __publisher's__ publisher's queue by enabling topic statistics. Read more about it here: http://wiki.ros.org/Topics#Topic_statistics

For the __subscriber's__ subscriber's drop count, you'll have to check within your own subscriber that the header.seq number is always incrementing by only one.

For the subscriber's drop count, you'll have to check within your own subscriber that the header.seq number is always incrementing by only one.

You can see the number of dropped messages from the publisher's queue by enabling topic statistics. Read more about it here: http://wiki.ros.org/Topics#Topic_statistics

For the subscriber's drop count, you'll have to check within your own subscriber that the header.seq number is always incrementing by only one.