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

Problems with ros1_bridge static_bridge "No template specialization for the pair" #208

Closed
i-am-neet opened this issue Aug 2, 2019 · 1 comment · Fixed by #209
Closed
Labels
bug Something isn't working

Comments

@i-am-neet
Copy link

Bug report

Required Info:

  • Operating System:
    • Ubuntu 18.04, ROS2 Dashing
  • Installation type:
    • from source
  • Version or commit hash:
  • DDS implementation:
    • RTI Connext
  • Client library (if applicable):

Steps to reproduce issue

# Shell 1
$ source /opt/ros/melodic/setup.bash
$ roscore &
$ rosrun rospy_tutorials talker

# Shell 2
# I built the ros1_bridge in ros2_ws
$ source ros2_ws/install/setup.bash
$ ros2 run ros1_bridge static_bridge
[INFO] [ros_bridge]: create bidirectional bridge for topic chatter
terminate called after throwing an instance of 'std::runtime_error'
  what():  No template specialization for the pair

Expected behavior

I want to bridge the specific topic to ROS2, but it doesn't work on tutorial's talker


Feature request

Filters for bridge specific topic or except some topics

Feature description

I want to use ros1_bridge to communicate between multi-robots which based on ROS1 through DDS
But there is a problem with bridging big data like image_raw when I use dynamic_bridge --bridge-all-topics
It will cause the network traffic jams

Is it possible to filter some topics or make a rule file to bridge topics that I wanted?

@dirk-thomas dirk-thomas added the bug Something isn't working label Aug 2, 2019
@dirk-thomas
Copy link
Member

Thank you for reporting this. #209 fixes the static_bridge.

The static bridge is a demonstration how a single topic with a specific type can be bridged. You could implement your own static bridge for you specific topic types / names - all you need to change from the example are these few lines:

// bridge one example topic
std::string topic_name = "chatter";
std::string ros1_type_name = "std_msgs/String";
std::string ros2_type_name = "std_msgs/msg/String";

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

Successfully merging a pull request may close this issue.

2 participants