You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,6 +167,7 @@ To publish a given u-blox message to a ROS topic, set the parameter shown below
167
167
*`publish/mon/hw`: Topic `~monhw`
168
168
169
169
### NAV messages
170
+
* NAV messages are time stamped with `i_tow`, and multiple messages can be synchronized with [ublox_msg_filters](ublox_msg_filters)
170
171
*`publish/nav/all`: This is the default value for the `publish/mon/<message>` parameters below. It defaults to `publish/all`. Individual messages can be enabled or disabled by setting the parameters below.
Time synchronize multiple uBlox messages to get a single callback
4
+
5
+
Port of [message_filters::ExactTime](http://wiki.ros.org/message_filters#ExactTime_Policy) message synchronization policy to use integer time of week in milliseconds `i_tow` instead of `ros::Time` in a header.
6
+
7
+
The [message_filters::ApproximateTime](http://wiki.ros.org/message_filters#ApproximateTime_Policy) message synchronization policy is not relevent because messages generated by a ublox sensor for a single update contain identical `i_tow` time stamps.
8
+
9
+
See [src/listener.cpp](src/listener.cpp) for example usage.
10
+
11
+
Launch the example with `ros2 launch ublox_msg_filters example.launch.xml`
0 commit comments