ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hi,

I watched the ROSCon talk by ahendrix, and tried out few different types of network configurations, I guess this might be helpful for anyone who is having trouble setting up their own network with ROS.

Things needed :

  1. A router (DNS server), which is capable of assigning IP addresses.
  2. connect all the devices which are part of your ROS ecosystem to this router. (also having access to the router homepage can be handy to get the mapping of 'devices to their respective IP address' ). if not try to use $ ifconfig command to find out IP address on each device.
  3. On your Master Device, Just execute the following commands, Start with $ roscore, now open another terminal, and issue the following commands,

    (For eg. Assuming the IP is 192.168.1.10, check yours and make suitable changes )

    $ export ROS_IP=192.168.1.10

    $ export ROS_MASTER_URI=http://192.168.1.10:11311

  4. Now, On you slave or Client device/s, get the IP of your slave device/s and issue the following commands, Again assuming your slave IP is 192.168.1.5 (check this and modify according what you get)

    $ export ROS_IP=192.168.1.5

    $ export ROS_MASTER_URI=http://192.168.1.10:11311

NOTE: These commands are localized to the terminal you are currently working on. So, when you want to working on a new terminal make sure you issue these commands again. Also, It is not necessary to export your ROS_HOSTNAME. Be sure to export only your ROS_IP. This reduces all sort of complications.

5 . if you have done steps 1 to 4 correctly, then there should not be any trouble with your ROS network setup. Follow the same pattern in all your successive slave device/s.

Some of you might want to setup a direct connection between your PC and say for eg, an embedded device like Arduino or Rpi with an Ethernet cable. In that case make sure you follow the ROSCon video mentioned above, the last 5 or 7 minutes of the talk will give you an Idea as to what is essential for you in your setup.

Regards,

Murali

Hi,

I watched the ROSCon talk by ahendrix, and tried out few different types of network configurations, I guess this might be helpful for anyone who is having trouble setting up their own network with ROS.

Things needed :

  1. A router (DNS server), which is capable of assigning IP addresses.
  2. connect all the devices which are part of your ROS ecosystem to this router. (also having access to the router homepage can be handy to get the mapping of 'devices to their respective IP address' ). if not try to use $ ifconfig command to find out IP address on each device.
  3. On your Master Device, Just execute the following commands, Start with $ roscore, now open another terminal, and issue the following commands,

    (For eg. Assuming the IP is 192.168.1.10, check yours and make suitable changes )

    $ export ROS_IP=192.168.1.10

    $ export ROS_MASTER_URI=http://192.168.1.10:11311

  4. Now, On you your slave or Client device/s, get the IP of your slave device/s and issue the following commands, Again assuming your slave IP is 192.168.1.5 (check this and modify according what you get)

    $ export ROS_IP=192.168.1.5

    $ export ROS_MASTER_URI=http://192.168.1.10:11311

NOTE: These commands are localized to the terminal you are currently working on. So, when you want to working on a new terminal make sure you issue these commands again. Also, It is not necessary to export your ROS_HOSTNAME. Be sure to export only your ROS_IP. This reduces all sort of complications.

5 . if you have done steps 1 to 4 correctly, then there should not be any trouble with your ROS network setup. Follow the same pattern in all your successive slave device/s.

Some of you might want to setup a direct connection between your PC and say for eg, an embedded device like Arduino or Rpi with an Ethernet cable. In that case make sure you follow the ROSCon video mentioned above, the last 5 or 7 minutes of the talk will give you an Idea as to what is essential for you in your setup.

Regards,

Murali

Hi,

I watched the ROSCon talk by ahendrix, and tried out few different types of network configurations, I guess this might be helpful for anyone who is having trouble setting up their own network with ROS.

Things needed :

  1. A router (DNS server), which is capable of assigning IP addresses.
  2. connect all the devices which are part of your ROS ecosystem to this router. (also having access to the router homepage can be handy to get the mapping of 'devices to their respective IP address' ). if not try to use $ ifconfig command to find out IP address on each device.
  3. On your Master Device, Just execute the following commands, Start with $ roscore, now open another terminal, and issue the following commands,

    (For eg. Assuming the IP is 192.168.1.10, check yours and make suitable changes )

    $ export ROS_IP=192.168.1.10

    $ export ROS_MASTER_URI=http://192.168.1.10:11311

  4. Now, On your slave or Client device/s, get the IP of your slave device/s and issue the following commands, Again commands. Again, assuming your slave IP is 192.168.1.5 (check this and modify according to what you get)

    $ export ROS_IP=192.168.1.5

    $ export ROS_MASTER_URI=http://192.168.1.10:11311

NOTE: These commands are localized to the terminal you are currently working on. So, when you want to working on a new terminal make sure you issue these commands again. Also, It is not necessary to export your ROS_HOSTNAME. Be sure to export only your ROS_IP. This reduces all sort of complications.

5 . if you have done steps 1 to 4 correctly, then there should not be any trouble with your ROS network setup. Follow the same pattern in all your successive slave device/s.

Some of you might want to setup a direct connection between your PC and say for eg, an embedded device like Arduino or Rpi with an Ethernet cable. In that case make sure you follow the ROSCon video mentioned above, the last 5 or 7 minutes of the talk will give you an Idea as to what is essential for you in your setup.

Regards,

Murali