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
Currently the ROS-Humble-ROS1-Bridge uses basic pattern matching (so equality of strings or substrings) to match messages between ROS1 & ROS2. Because there is no equivalent messages of all our previous message definitions in ROS1, the bridge cannot pick up on it, and thus cannot echo it into ROS 2.
The first step to converting our whole repo into ROS 2, would be to add a package, with all our message definitions. In addition, we might have to a basic listener for all of them. This is so that electrical can begin embedding them in ROS2.
For the link to where the docs talk about how messages are bridgedrefer here.
Alternatives?
Alternatively, we can also bridge only selected topics and services. Link to docs is referred here.
The text was updated successfully, but these errors were encountered:
Main Problem
Currently the ROS-Humble-ROS1-Bridge uses basic pattern matching (so equality of strings or substrings) to match messages between ROS1 & ROS2. Because there is no equivalent messages of all our previous message definitions in ROS1, the bridge cannot pick up on it, and thus cannot echo it into ROS 2.
The first step to converting our whole repo into ROS 2, would be to add a package, with all our message definitions. In addition, we might have to a basic listener for all of them. This is so that electrical can begin embedding them in ROS2.
For the link to where the docs talk about how messages are bridged refer here.
Alternatives?
Alternatively, we can also bridge only selected topics and services. Link to docs is referred here.
The text was updated successfully, but these errors were encountered: