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 issues configuring DDS discovery for my setup, comprising two real-time machines connected with each other by Ethernet (subnet 192.168.10.x). Additionally, both machines have a wifi NIC (subnet 192.168.0.x) connecting them to a control laptop via wifi:
When adding the wifi NICs as well (currently commented out), discovery works but we observe extremely slow communication.
Also, I have read here that whitelisting multiple interfaces results in duplicate messages being send, which is obviously not desirable.
How should we configure DDS for fast and reliable communication? Any pointer to an example config would be helpful.
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
Uh oh!
There was an error while loading. Please reload this page.
I have issues configuring DDS discovery for my setup, comprising two real-time machines connected with each other by Ethernet (subnet 192.168.10.x). Additionally, both machines have a wifi NIC (subnet 192.168.0.x) connecting them to a control laptop via wifi:
Participants partially use ROS2 and partially native DDS communication.
Currently, we use the following DDS config on the robot PCs:
When adding the wifi NICs as well (currently commented out), discovery works but we observe extremely slow communication.
Also, I have read here that whitelisting multiple interfaces results in duplicate messages being send, which is obviously not desirable.
How should we configure DDS for fast and reliable communication? Any pointer to an example config would be helpful.
All reactions