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
I have a specific case I need to solve, for which I need the two sides of the domain bridge to connect to different machines.
I'm using FastDDS whitelisting setup with an XML file following the documentation here.
My issue is that the two ROS2 nodes, for example gateway_0 and gateway_1 use the same XML file. I want to specify one file for gateway_0 and another for gateway_1, but am not sure how to proceed.
What I'm looking for to start on this issue is the code location where the nodes are created to understand more, and maybe at this location I can do something to switch from the two XML files.
Any help on the subject is appreciated!
Victor
The text was updated successfully, but these errors were encountered:
Vicidel
changed the title
Different FastDDS configuration files for the two sides of the domain bridge
Different FastDDS XML configuration files for the two sides of the domain bridge
Jul 15, 2022
I'm not familiar with how to specify a particular FastDDS XML file for one ROS node in a process. Specifically, I guess you'll want to somehow associate the XML file per ROS context (which has a one-to-one mapping with DDS participants).
Hello all
I have a specific case I need to solve, for which I need the two sides of the domain bridge to connect to different machines.
I'm using FastDDS whitelisting setup with an XML file following the documentation here.
My issue is that the two ROS2 nodes, for example gateway_0 and gateway_1 use the same XML file. I want to specify one file for gateway_0 and another for gateway_1, but am not sure how to proceed.
What I'm looking for to start on this issue is the code location where the nodes are created to understand more, and maybe at this location I can do something to switch from the two XML files.
Any help on the subject is appreciated!
Victor
The text was updated successfully, but these errors were encountered: