-
Notifications
You must be signed in to change notification settings - Fork 16
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
mros2 node name cannot be observed from ROS 2 host #44
Comments
takasehideki
added a commit
that referenced
this issue
Sep 7, 2023
added as the limitation on README 6532fc1 |
The followings is the code space on ROS 2 implementation that may help us (I hope,,,;(
|
This was referenced Sep 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We cannot observe the name of mros2 nodes from ROS 2 host, e.g., by
ros2 node list
.We think this is due to the functionality limitation of embeddedRTPS, which is employed as the RTPS layer for mROS 2. While topic names in ROS2 are realized using standard DDS functions, node names seem to be implemented as a unique feature in ROS2. Officially supported DDS for ROS 2 (e.g., FastDDS) seems to work with RCL and RMW to achieve node names.
We think it is unrealistic to allow embeddedRTPS to handle node names as a feature, because it is just an RTPS stack used as the standalone software for the embedded devices. Therefore, we should realize this feature in the mROS 2 hierarchy to be able to handle node names because mROS 2 corresponds to RCL and RMW layers.
The text was updated successfully, but these errors were encountered: