fkie / multimaster_fkie

ROS stack with FKIE packages for multi-robot (discovering, synchronizing and management GUI)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cant connect Raspberry pi and dekstop computer

Jan190 opened this issue · comments

I am trying to connect my raspberry pi and computer that are on the same network. I have on both OS Ubuntu 20.04 and ROS Noetic installed. i followed pdf (https://digital.csic.es/bitstream/10261/133333/1/ROS-systems.pdf) with instruction but this two masters cant see each other. I can ping machines and when i start nodes master_discovery and master_sync on both machines there is no error but they don't detect each other.

Selection_001

Selection_002

Selection_003

Selection_004

I have set on both machines this instructions:

sudo sh -c "echo 0 >/proc/sys/net/ipv4/icmp_echo_ignore_broadcasts"
sudo sh -c "echo 1 >/proc/sys/net/ipv4/ip_forward"

And i had configure with correct IP addresses file /etc/hosts on both of the machines.

Please, try to run the master_discovery with
rosrun fkie_master_discovery master_discovery _mcast_group:=224.0.0.251 _robot_hosts:=[ubuntu,ros]

If they can discover each other the multicast doesn't work properly.

It looks like you've set the interface variable too. Therefore the master_discovery binds to the interface with the IP 192.168.46.100. You have to make sure that the multicast messages are also forwarded on this interface.

If that was not the intention, it would be best to delete all variables from the ROS parameter server or restart roscore.

After i had restarted roscore on both machines and run command you gave me it worked and connection have been established. Problem that I have now is temporary failure in name resolution:

Selection_001

Selection_002

sorry, my fault! Use _robot_hosts:=[ubuntu,pc] instead of _robot_hosts:=[ubuntu,ros]

But you should try to get it runs without _robot_hosts, since for each entry a unicast message is send to discover the remote host.

Thank you for the help now everthing is working. After you told to try with unicast I figure it out that problem was on raspberry Pi. It didn't had package python-is-python3 so node master_discovery on raspberry actually didn't worked and didn't show any error on start.