rmw

ROS 2: Why are there so many Topics?

ROS 2 is designed as an everything-included framework for robotics. It generally maintains alignment with the architecture and philosophy of the original ROS.

Carried-over from ROS to ROS 2 was its topic naming convention, and the inclusion of the 'Parameter' system for every application.
These two details work together to create large numbers of 'parameter' topics, even in systems that do not use the ROS 2 parameter feature.
Here's how that happens:

ROS 2: RTI Tools Overview

RTI's specialized tools for DDS give you vastly increased visibility into your system, which saves time and improves the outcome.

As an example, consider a ROS 2 system running a simple "Hello World!" pub/sub pair, using the default ROS 2 demo_nodes_cpp package and the 'talker' and 'listener' applications.

ROS 2 command-line tools will show you 3 topics in this system:

ROS 2: Why Use Connext

This will depend on the needs of the project, both during development and in long-term deployment:

ROS 2: What is DDS

What is ROS 2?

ROS 2, or Robot Operating System 2, is an open-source framework designed to simplify the development of robot software. It builds upon the concepts introduced in the original ROS but incorporates several key improvements:

  • Real-Time Capabilities: ROS 2 has improved support for multi-threading and asynchronous operations, which is crucial for applications requiring timely and predictable responses.

ROS 2 and Connext DDS

Welcome ROS 2 Users 

This page will help you get the most from the easy-to-use ROS 2 ecosystem of robotics tools and packages, and the power and performance of RTI Connext DDS.

If you're new to ROS or DDS:

If you're using ROS 2 and are interested in RTI Connext:

Subscribe to RSS - rmw