Exporting a ROS Master to a Local Machine
How to import all of the ROS messages from a remote machine to your machine (for visualization, for example).
Step-by-step guide
- Sometimes, you can't have a direct connection to the machine running the ROS Master you need access to...
- You could ssh into it, and see nothing OR
- You can export the ROS Master to your Machine.
- You can do this in three easy steps. (Or, you can write an alias for it! More on that later).
To Export the ROS Master to your local machine:
$ export ROS_MASTER_URI=http://<ip of machine running ROS Master>:11311 $ export ROS_IP=<ip of machine running ROS Master> $ source ~/.bashrc
If you want to write an alias, do the following on your local machine
$ sudo nano ~/.bash_aliases # at the bottom of the .bash_aliases file, append the following alias <name of macnine running ROS Master>='export ROS_MASTER_URI=http://<ip of machine running ROS Master>:11311 && export ROS_IP=<ip of machine running ROS Master>' # REMEMBER: you MUST update the IP of the machine running the ROS Master in this alias each time it changes (about once per day)
Special Instruction for BANSHEE
- BANSHEE is special. She doesn't like talking to other computers, so
- From your host machine, ping BANSHEE as per the ssh'ing into a Jetson how-to article.
On your host machine:
$ sudo nano /etc/hosts
append "<BANSHEE's IP address> BANSHEE" to the /etc/hosts file. For example, on MALICE:
127.0.0.1 localhost 127.0.1.1 MALICE <IP address> BANSHEE # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters
- You MUST update this every time you ssh into BANSHEE, as it's IP address changes everyday.
Related articles
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.