ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Wrench
messaged do not include a Header
field. Without a header, there is no timestamp information available with which to synchronise incoming messages.
You'll need to use a message with a Header
, such as WrenchStamped
.
2 | No.2 Revision |
Wrench
messaged do not include a Header
field. field (docs). Without a header, there is no timestamp information available with which to the TimeSynchronizer
can synchronise incoming messages.messages. From the wiki page:
The
TimeSynchronizer
filter synchronizes incoming channels by the timestamps contained in their headers [..]
You'll need to use a message with a Header
, such as geometry_msgs/WrenchStamped.WrenchStamped
what i do is just change the topic and the type of argument, but it is wrong somewhere
that is a good approach, but as most things are (almost statically) typed with topics (at least in C++), can lead to issues such as the one you encountered.
3 | No.3 Revision |
/opt/ros/indigo/include/message_filters/sync_policies/exact_time.h:127:101: error: ‘value’ is not a member of ‘ros::message_traits::TimeStamp<geometry_msgs::Wrench_<std::allocator<void> >, void>’ Tuple& t = tuples_[mt::TimeStamp<typename mpl::at_c<Messages, i>::type>::value(*evt.getMessage())];
Wrench
messaged do not include a Header
field (docs). Without a header, there is no timestamp information available with which the TimeSynchronizer
can synchronise incoming messages. From the wiki page:
The
TimeSynchronizer
filter synchronizes incoming channels by the timestamps contained in their headers [..]
You'll need to use a message with a Header
, such as geometry_msgs/WrenchStamped.
what i do is just change the topic and the type of argument, but it is wrong somewhere
that is a good approach, but as most things are (almost statically) typed with topics (at least in C++), can lead to issues such as the one you encountered.