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
I have recently updated to Driver 4.2.0, and I am getting unexpected behavior on my system due to the driver publishing periodically on /tf_static , typically reserved for "unchanging" transforms.
I propose the frequently updating, periodic transforms get published to /tf rather than /tf_static and the static transformation (sensor->odometer_link ) get published once, since that is expected to be unchanging.
I can see that sensor->gnss_1_antenna_link sensor->gnss_2_antenna_link and sensor->odometry_link are being published . The sensor->gnss_*_antenna links are changing (maybe because of antenna calibration).
I have recently updated to Driver 4.2.0, and I am getting unexpected behavior on my system due to the driver publishing periodically on
/tf_static
, typically reserved for "unchanging" transforms.See: Section 4.8 http://wiki.ros.org/tf2 on tf_static v.s. tf.
I propose the frequently updating, periodic transforms get published to
/tf
rather than/tf_static
and the static transformation (sensor->odometer_link
) get published once, since that is expected to be unchanging.I can see that sensor->gnss_1_antenna_link sensor->gnss_2_antenna_link and sensor->odometry_link are being published . The sensor->gnss_*_antenna links are changing (maybe because of antenna calibration).
https://github.com/LORD-MicroStrain/microstrain_inertial_driver_common/blob/6d62789b0492e28a0e4b86be8b4dc0e562d08a5e/src/publishers.cpp#L1740C34-L1740C47
I think this is one o the offending lines?
The text was updated successfully, but these errors were encountered: