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

unable to subscribe to topic with MarkerArray messages under ROS 2 Galactic #756

Open
crystal-butler opened this issue Mar 30, 2022 · 1 comment

Comments

@crystal-butler
Copy link

crystal-butler commented Mar 30, 2022

I'm trying to use the Marker plugin with a Mapviz install under ROS 2 Galactic to display MarkerArray messages, but am getting the following error:

[mapviz-1] [ERROR] [1648669993.058815599] [mapviz]: Unhandled RCLError in Qt event loop: could not create subscription: failed to create topic, at /tmp/binarydeb/ros-galactic-rmw-cyclonedds-cpp-0.22.4/src/rmw_node.cpp:2552, at /tmp/binarydeb/ros-galactic-rcl-3.1.2/src/rcl/subscription.c:105

I had an earlier installation of Mapviz under ROS 2 Eloquent that was able to subscribe to the same topic and messages I'm attempting to visualize under Galactic. I reran colcon build on the publisher package under Galactic and confirmed that the messages were publishing with the command ros2 topic echo /poi_marker_array visualization_msgs/msg/MarkerArray. Any thoughts on whether this is a problem with Mapviz or with my publisher, or additional troubleshooting tips?

@crystal-butler crystal-butler changed the title unable to subscribe to MarkerArray under ROS 2 Galactic unable to subscribe to topic with MarkerArray messages under ROS 2 Galactic Mar 30, 2022
@agyoungs
Copy link
Contributor

agyoungs commented May 23, 2022

Sorry for such a late reply, but this appears to be caused by multiple subscriptions with the same name:

https://github.com/swri-robotics/mapviz/blob/ros2-devel/mapviz_plugins/src/marker_plugin.cpp#L126

I tested this by commenting out the Marker subscription and was able to subscribe to MarkerArray. This will likely need to be handled in a different way than it currently is (potentially just by looking up the type of the topic)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants