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

Map is not rendered if not published before rviz launch #400

Open
bergercookie opened this issue May 15, 2019 · 6 comments

Comments

Projects
None yet
4 participants
@bergercookie
Copy link

commented May 15, 2019

I'm following the tutorial of the nav2 stack: https://github.com/ros-planning/navigation2/tree/master/nav2_bringup

Following its instructions, rviz2 is launched first and subscribes to the /map topic which is not published yet. Then I'm launching amcl which is publishing map messages to /map. I can pick inspect the latter from the command line ros2 topic echo /map but not from rviz2 unless I restart the latter

@mkhansen-intel

This comment has been minimized.

Copy link

commented Jun 20, 2019

@wjwwood - this issue is a result of the /map topic using transient_local, reliable QOS, which I mentioned in the TSC

@mkhansen-intel

This comment has been minimized.

Copy link

commented Jul 8, 2019

@wjwwood - can we get an update as to when rviz will support transient local reliable QOS?

@jacobperron jacobperron self-assigned this Jul 11, 2019

@wjwwood

This comment has been minimized.

Copy link
Member

commented Jul 11, 2019

I think @jacobperron is going to have a look at it, since he's messing with stuff in the displays classes already, but a community pull request (not necessarily from you @mkhansen-intel or @bergercookie) is always appreciated for things like this.

@wjwwood wjwwood added the bug label Jul 11, 2019

@wjwwood wjwwood added this to Proposed in Dashing Patch Release 2 via automation Jul 11, 2019

@wjwwood wjwwood removed this from Proposed in Dashing Patch Release 2 Jul 11, 2019

@wjwwood

This comment has been minimized.

Copy link
Member

commented Jul 11, 2019

I think this would a good candidate for backport as well, depending on how the changes look.

@mkhansen-intel

This comment has been minimized.

Copy link

commented Jul 22, 2019

@jacobperron - any update on this?

@jacobperron

This comment has been minimized.

Copy link
Member

commented Jul 22, 2019

@mkhansen-intel No, I haven't had a chance to take a look yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.