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

See here:

http://www.ros.org/wiki/rospy/Overview/Publishers%20and%20Subscribers#Connection_Information

click to hide/show revision 2
No.2 Revision

See here:

http://www.ros.org/wiki/rospy/Overview/Publishers%20and%20Subscribers#Connection_Information


Edit (by @jayess):

Just so you don't have to go clicking around for the answer (from @bhaskara's link):

A subscriber can get access to a "connection header", which includes debugging information such as who sent the message, as well information like whether or not a message was latched. This data is stored as the _connection_header field of a received message.

e.g.

print m._connection_header
{'callerid': '/talker_38321_1284999593611',
 'latching': '0',
 'md5sum': '992ce8a1687cec8c8bd883ec73ca41d1',
 'message_definition': 'string data\n\n',
 'topic': '/chatter',
 'type': 'std_msgs/String'}

We do not recommend using callerid information beyond debugging purposes, as it can lead to brittle code in an anonymous publish/subscribe architecture.

click to hide/show revision 3
No.3 Revision

See here:

http://www.ros.org/wiki/rospy/Overview/Publishers%20and%20Subscribers#Connection_Information


Edit (by @jayess):@jayess ):

Just so you don't have to go clicking around for the answer (from @bhaskara's link):

A subscriber can get access to a "connection header", which includes debugging information such as who sent the message, as well information like whether or not a message was latched. This data is stored as the _connection_header field of a received message.

e.g.

print m._connection_header
{'callerid': '/talker_38321_1284999593611',
 'latching': '0',
 'md5sum': '992ce8a1687cec8c8bd883ec73ca41d1',
 'message_definition': 'string data\n\n',
 'topic': '/chatter',
 'type': 'std_msgs/String'}

We do not recommend using callerid information beyond debugging purposes, as it can lead to brittle code in an anonymous publish/subscribe architecture.