open-rmf / free_fleet

A free fleet management system.
Apache License 2.0
156 stars 65 forks source link

Unable to connect Robot ROS1 free_fleet client and PC ROS2 free_fleet server using Pocket Wifi. #122

Closed suztakur closed 1 year ago

suztakur commented 1 year ago

Description of the bug

 I started free_fleet_client on my robot's PC and free_fleet_server on my PC according to barebones example, but I can't connect. I have confirmed the ping connection and port connection between the robot and the PC. Both the robot and PC set ROS_DOMAIN_ID=0 and opened ports 7400~8000, which would be used by DDS, to check the connection. Pocket Wifi is used as a common network.

Steps to reproduce the bug

 PC: ROS_DOMAIN_ID=0, open ports 7400~8000 and start ff_examples_ros2 fake_server.launch.xml  Robot: ROS_DOMAIN_ID=0, open ports 7400-8000 and run ff_examples_ros1 fake_client.launch.  No connection.

Expected behavior

 The free_fleet_client running on the robot is registered in the log of free_fleet_sever.

Actual behavior

 No log is registered and no communication is established.

Additional information

 Network settings were confirmed at the following link. http://wiki.ros.org/ja/ROS/NetworkSetup  The following link was used as a reference for opening the port. https://docs.ros.org/en/foxy/Concepts/About-Domain-ID.html  A Raspberry Pi 4 Model B is used as the robot PC.

aaronchongth commented 1 year ago

Hello there! Unfortunately I am unable to recreate this issue without the same hardware at hand. Some questions before I look further into it,

Some things to note,

I will be removing the bug label as this is not related to free_fleet's implementation or our usage of cyclonedds, but rather the requirement of using a Pocket Wifi instead.

suztakur commented 1 year ago

Thanks for the reply. I was able to confirm the connection by inactivating the firewalls on the robot PC and ROS2PC.