Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rviz2 MarkerArray Display error #363

Closed
sagniknitr opened this issue Oct 16, 2018 · 4 comments
Closed

rviz2 MarkerArray Display error #363

sagniknitr opened this issue Oct 16, 2018 · 4 comments
Labels
bug Something isn't working

Comments

@sagniknitr
Copy link

Selecting the MarkerArray Display in the latest rviz2 is showing No transform to fixed frame [base_link]. TF error: [Lookup would require extrapolation into the past. Requested time 1511969984.89534 but the earliest data is at time 1511970003.02050, when looking up transform from frame [odom] to frame [base_link]] error in the display window.

The said MarkerArray message contains markers with two different frame_id : 1) base_link and 2)odom.

All the markers with odom frame_id are not displayed in the rviz2 window.

marker_array

@clalancette clalancette added the bug Something isn't working label Oct 18, 2018
@sagniknitr
Copy link
Author

A update on this issue : the exception seems to come from the function TFFrameTransformer::transform(const rviz_common::transformation::PoseStamped & pose_in, const std::string & target_frame) in the file. (https://github.com/ros2/rviz/blob/ros2/rviz_default_plugins/src/rviz_default_plugins/transformation/tf_frame_transformer.cpp)

It seems that using ros2 run tf2_ros static_transform_publisher 0 0 0 0 0 0 map odom is the only solution to the issue. I don't understand why rviz2 needs to listen to /tf_static topic. published by the static_transform_publisher, to update the TF tree.

@Martin-Idel-SI
Copy link
Contributor

Yes, definitely. The error message is a tf error as the message tells you, hence must come from the lookupTransform call in the display, which calls transform. In other words, it must come from within TFFrameTransformer.

Static transforms are no problem, because their transform is available at any time as the name suggests.

This is probably yet another issue that will be solved once message filters are available - or at least the real problem should become much more apparent!

@sagniknitr
Copy link
Author

Thanks at follow up @Martin-Idel-SI . I thought it may be related to tf2 message_filters, but needed some confirmation.

@shiveshkhaitan
Copy link
Contributor

@sagniknitr if the error still persists can you please tell how to reproduce the same. I have an implementation of rviz tf message filters ready PR. It would be helpful in confirming if that actually serves the purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants