You're reading the documentation for a version of ROS 2 that has reached its EOL (end-of-life), and is no longer officially supported. If you want up-to-date information, please have a look at Iron.
Overview and usage of RQt
Table of Contents
RQt is a graphical user interface framework that implements various tools and interfaces in the form of plugins. One can run all the existing GUI tools as dockable windows within RQt! The tools can still run in a traditional standalone method, but RQt makes it easier to manage all the various windows in a single screen layout.
You can run any RQt tools/plugins easily by:
This GUI allows you to choose any available plugins on your system. You can also run plugins in standalone windows. For example, RQt Python Console:
ros2 run rqt_py_console rqt_py_console
Users can create their own plugins for RQt with either
To see what RQt plugins are available for your system, run:
ros2 pkg list
And then look for packages that start with
Installing From Debian
sudo apt install ros-galactic-rqt*
Building From Source
RQt Components Structure
RQt consists of two metapackages:
rqt - core infrastucture modules.
rqt_common_plugins - Commonly useful debugging tools.
Advantage of RQt framework
Compared to building your own GUIs from scratch:
Standardized common procedures for GUI (start-shutdown hook, restore previous states).
Multiple widgets can be docked in a single window.
Easily turn your existing Qt widgets into RQt plugins.
Expect support at ROS Answers (ROS community website for the questions).
From system architecture’s perspective:
Support multi-platform (basically wherever QT and ROS run) and multi-language (
Manageable lifecycle: RQt plugins using common API makes maintainance & reuse easier.
ROS 2 Discourse announcment of porting to ROS 2).
Brief overview of RQt (from a Willow Garage intern blog post).