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
Hi, these days I am using rocon_tutorials for test my rocon installation but I get some problem which is I just got message of couldn't connect to redis server when I use two computers communication by wireless, and following is my configuration.
By the way chatter_concert can work properly individually.
After a quick look this seems to be a network setup issue...
Please double check your network settings. Rocon is not a simple client-server software, it is multi-master, meaning all machines need to be able to connect to all other machines. that means the IP/hostname defined need to be resolvable for all.
Looking at the configuration you describe, are you sure that inno is 192.168.0.1 ? It is defined as 192.168.0.101 ?
@asmodehn Hi, Thank you very much for your answer.
I got some confused about rocon multimaster configuration, such as what is meaning about inno? How to configure network let each machines know each other.
And I follow your advices that change my PC's inno to 192.168.0.101 in /etc/hosts, but I got the same problems, Can you tell me if my configuration is wrong?
Thanks!
Hi, these days I am using rocon_tutorials for test my rocon installation but I get some problem which is I just got message of couldn't connect to redis server when I use two computers communication by wireless, and following is my configuration.
By the way chatter_concert can work properly individually.
Rocon installation
I just use code in here
Concert PC configuration
ROS_HOSTNAME=192.168.0.110
ROS_IP=192.168.0.110
ROS_MASTER_URI=http://192.168.0.110:11311
with
/etc/hosts
192.168.0.1 inno
Client laptop configuration
ROS_HOSTNAME=inno
ROS_IP=192.168.0.101
ROS_MASTER_URI=http://localhost:11311
with
/etc/hosts
127.0.1.1 inno
OUTPUT ON CONCERT PC
OUTPUT ON Client laptop
Thank you!
Waiting for the letter!
The text was updated successfully, but these errors were encountered: