Robot Operating System

ROS (a.k.a Robot Operating System or Robot OS), can be seen as a kind of Robotic Framework. Because it can't be installed directly on robotic equipment (ROS needs a computer and works above its OS), it can't be considered as a pure operating system. In addition to providing a complete development and execution environment, ROS includes numerous simulation tools. However, it does not guarantee runtime properties, services or event processing in deterministic time spots (i.e. realtime processing), though it is possible to integrate ROS with realtime code (openCV is supported).

Originally developed in 2007 by the Stanford Artificial Intelligence Laboratory (see Stair Project), ROS is now widely used by the robotic ecosystem thanks to the open source community and Willow Garage (a robotics research institute/incubator, which produce the famous PR2 or TurtleBot and is currently making the main development).
Many robots are supported: WifiBot, Lego Mindstorm NXT, HERB (see http://www.ros.org/wiki/Robots for a full list).

A ROS application is organized into "nodes" which are Unix competitors processes. The nodes interact by sending events via "topics" in a publisher-subscriber model. The implementation of internal functions can be achieved in C++ or Python language. Many robotic equipment have their dedicated ROS nodes developped (Lidar, Kinect, ...).

ROS is available on a wide range of OS, but the Ubuntu version, for compatibility reasons and rapid implementation, is the best choice.

In this short page, we propose to you a short ROS start guide, with the most frequent errors you can encounter during your development.

Installation

"Note: we choose to present to you the latest ROS development environment available (in March 2013): Ubuntu 12.10 and ROS v7 (named Groovy Galapagos). We also work with Ubuntu 13.04 without facing problems. With its last release, Willow Garage introduced a new ROS build system: catkin. Given the huge amount of packages out there build with rosbuild, and the impossibility to migrate simply from one system to the other, we will continue to use rosbuild. Most of the robotic Equipment works with the couple (Ubuntu 12.10 / ROS Groovy), however check before if there is not incompatibilities issues (for example: Kinect works better with Ubuntu 12.04 / ROS Fuerte). "

Setup sources.list

In a terminal, type the following line:

sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu <distribution> main" > /etc/apt/sources.list.d/ros-latest.list'

where <distribution> is your Ubuntu ditsribution name (e.g. "precise", "quantal", "raring", ...) This will add ROS repositories to your distribution.

Setup your keys

wget http://packages.ros.org/ros.key -O - | sudo apt-key add -

Now, you are able to download the latest updates from ROS.

Installation

Update the Debian packages:

sudo apt-get update

Install the full Groovy configuration:

sudo apt-get install ros-groovy-desktop-full

It will install ROS, rqt, rviz, robot-generic libraries, 2D/3D simulators, navigation and 2D/3D perception.

Initialize rosdep:

sudo rosdep init rosdep update

This tool is used to install system dependencies required by ROS packages.

ROS is now installed but in order to run it, some environment variables must be assigned. This can be automatically done at the launch of the session:

echo "source /opt/ros/groovy/setup.bash" >> ~/.bashrc

Install python tools:

sudo apt-get install python-rosinstall python-rosdep

Finally, execute the script:

~/.bashrc

Configuration

Create a ROS workspace:

rosws init ~/groovy_workspace /opt/ros/groovy mkdir ~/groovy_workspace/sandbox rosws set ~/groovy_workspace/sandbox

Every time you modify or add entries in your workspace, re-source ~/groovy_workspace/setup.bash:

source ~/groovy_workspace/setup.bash

Use ROS

Principles

• Packages

ROS is organized in packages. They include, among other, ROS nodes. They allows developers to easily reuse pieces of software. You can create a package by hand or with the command: roscreate-pkg <package-name>. Actually, a ROS package is nothing but a directory descended from ROS_PACKAGE_PATH that has a manifest.xml file in it. A package may include the following contents:
msg/: message types
srv/: service types
scripts/: executable scripts (Pyhton sources for example)
CMakeLists.txt/: CMake build file (ROS package are build with [CMake], this file describes how to do it)
manifest.xml/: minimal specification about the package: describes metadata and dependancies (see an example).
To build a package, type rosmake <package-name>

• Nodes

ROS nodes are processes, that reside in the same or different machines. Usually, there are many nodes to control a robot (e.g. one for a motor, another one for a sensor, etc.) The nodes are combined together and communicate with topics or services. They get to know each other via a particular node, rosmaster. A node has a name and a type. During an execution, type rosnode list to list the currently running nodes.

• Topics

A topic is a bus over which nodes communicate data, thanks to the publisher/subscriber model (communication many-to-many). Communication over a topic is unidirectional and asynchronous. Type rostopic list to list the current topics.

• Services

Services allows nodes to make remote procedure calls (communication one-to-one). Communication over a service is synchronous.

• Launch files

Launch files are XML files that specify a list of nodes, topics, services, parameter values and eventually the machines for distributed applications.

Useful commandline tools

• roscd [package-name]: change directory directly to a package (indepently from your current directory)
• rosls [package-name]: list directory contents directly
• rosnode list: lists the currently running nodes
• rostopic list: lists the current topics
• rosmake [package-name]: build a package

Graphical tools

• rviz: a 3D visualization tool
• rxgraph display a graph of the currently running nodes and the topics

Troubleshooting

• Error messages:
  • "No ROS_WORKSPACE set": check if your environment variable ROS_WORKSPACE is assigned (echo $ROS_WORKSPACE). If not, update your .bashrc file (echo "export ROS_WORKSPACE=/home/<username>/groovy_workspace" >> ~/.bashrc).
  • "No ROS_PACKAGE_PATH set": check if your environment variable ROS_PACKAGE_PATH is assigned (echo $ROS_PACKAGE_PATH). If not, update your .bashrc file (echo "export ROS_PACKAGE_PATH=/home/<username>/groovy_workspace/sandbox/" >> ~/.bashrc).
  • "roscd: No such package/stack '<package_name>': check if the package exists and is included in your ROS_PACKAGE_PATH.

Others

For industrial robots, a dedicated ROS version exists: ROS industrial.

Polytech' Projects which use ROS

RobAIR2013
Armind
EA2012_Langages_et_Canevas_pour_la_robotique_de_service

API

Javascript

rosnodejs Programming robots with Javascript & Node.js

AIR Projects

• RobAIR2013-RICM5 tunnelling XMPP entre des nodes ROS. GStreamer
• Armind
• Robot d'inspection géotechnique

References

• ROS official website
• fOSSa presentation
• French guide (install ROS Fuerte and use NXT)