How to communicate other PC on ROS2
Hello, I am a beginner of ros2, and I'm trying to send ros message from window 10 PC to Ubuntu PC. Both PC is installed ROS2 and I just implement the listener and talker of demo_nodes_cpp project in different PC.
But it can not communicate ecah other. I also check the ros node list in Ubuntu and Window. I also, used two RMW types (Fast_RTPS, RTI). When I did test the talker and listener nodes in one PC, it was worked fine, but it cannot cummunicate with other PC. There is no error or warrning message.
Is there anything that i miss for the communication in multi-PC?
please help me.... I spent 4 days for this problem....
Can you provide a little more details on the network configuration? Are both PCs in the same network? Are they using the same IP subnet? How are the firewalls configured? Are you using the same Domain ID on all PCs?
Yes all PC is in the same network and same IP subnet and I truned off the firewalls.
But I don't know how to check the Domain ID.... How to check???
Make sure you can ping both machines from each other and that talker/listener work on both machines individually. The ROS_DOMAIN_ID is an environment variable: https://discourse.ros.org/t/how-to-ru...
Thank you for answer, Karsten. I checked both machines can work talker/listener, and i also, check both machines can ping each other
I set the ROS_DOMAIN_ID=1 for both machines but, it can not communicate...
If you have an RTI license, you can check if the talker and listener are matching using the RTI Admin software. Or use Wireshark to check the RTPS messages. I would suggest to try using the same RMW (RTI-RTI or FastRTPS-FastRTPS) to make sure the it is not an interoperability issue.
Just to make sure about the configuration you have, can you list the network interfaces you have on Windows and Ubuntu and edit your question with this information?
One last question, are the talker/listener communicating if they are on the same machine? (and if they are built on the same OS)
when using RTI, make sure it is configured for multicast and not for SHM.