|Please ask about problems and questions regarding this tutorial on answers.ros.org. Don't forget to include in your question the link to this page, the versions of your OS & ROS, and also add appropriate tags.|
Remote monitoring and controlDescription: Remote monitoring and control from a distance computer
Tutorial Level: INTERMEDIATE
Next Tutorial: Robot navigation
To monitor and command your robot from remote computer you have two main options: one is using a graphical remote access program such as TeamViewer and the other option is using a command-line remote connection such as ssh.
First, You will need to install the armadillo2 package on the remote machine, see the Installation tutorial for instructions.
For this tutorial assume that the remote computer and the robot are connected to the same network and have that the robot IP is 10.0.0.14 and the remote computer IP is 10.0.0.13.
You can check your IP address by typing ifconfig in a terminal.
- If you want to check the connectivity between the remote computer and the robot we can ping the robot by running the following command in a terminal:
$ ping 10.0.0.14
and check that we get a response from the robot.
We will use the robot computer as the ROS master, by setting the ROS_MASTER_URI and ROS_IP variables to the robot's IP. To log into the robot computer we use the following command:
$ ssh firstname.lastname@example.org
- This command will open a ssh channel to the robot. To change the variables we use the following commands:
$ export ROS_MASTER_URI=http://10.0.0.14:11311 $ export ROS_IP=10.0.0.14
- After this you can run the robot launch file on the robot's computer, for example:
$ roslaunch armadillo2 armadillo2.launch
On the remote computer we need to set the ROS_MASTER_URI to the robot's IP and the ROS_IP to the remote computer IP. Open a new terminal and type the following:
$ export ROS_MASTER_URI=http://10.0.0.14:11311 $ export ROS_IP=10.0.0.13
- You will need to type the above two commands in each new terminal that will interact with the robot.
- To check that the remote computer can access the robot's topics you can run:
$ rostopic list
- If this command return the robot list of topics than the remote connection is successful.
You can also try to publish commands to operate the robot.