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
Using a discovery server for ones ROS nodes can easily be configured using an environment variable like so: export ROS_DISCOVERY_SERVER="127.0.0.1:11811;127.0.0.1:11888"
However creating a super client (for example for ros2 bag) requires a XML file of at least 26 lines with hardcoded values for discovery server id and location.
Keeping these files in sync with the robots and users configuration is a hassle (for us). It would be nice if we can use an environment variable for this as well: export ROS_SUPER_CLIENT=true.
Or, as this only makes sense for discovery servers, combine the two in a backwards compatible manner: export ROS_DISCOVERY_SERVER="127.0.0.1:11811;127.0.0.1:11888#super" or something.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Using a discovery server for ones ROS nodes can easily be configured using an environment variable like so:
export ROS_DISCOVERY_SERVER="127.0.0.1:11811;127.0.0.1:11888"
However creating a super client (for example for
ros2 bag
) requires a XML file of at least 26 lines with hardcoded values for discovery server id and location.Keeping these files in sync with the robots and users configuration is a hassle (for us). It would be nice if we can use an environment variable for this as well:
export ROS_SUPER_CLIENT=true
.Or, as this only makes sense for discovery servers, combine the two in a backwards compatible manner:
export ROS_DISCOVERY_SERVER="127.0.0.1:11811;127.0.0.1:11888#super"
or something.Beta Was this translation helpful? Give feedback.
All reactions