Who is this for?
This is an introductory topic for robotics and edge developers who want to get started with making a Robot Operating System 2 (ROS 2) system discoverable and callable by other devices and AI agents using Device Connect, without changing the ROS 2 application itself.
What will you learn?
After completing this Learning Path, you'll be able to perform the following tasks:
- Identify how a Device Connect adapter bridges a containerized ROS 2 system to a Device Connect network.
- Set up ROS 2 in Docker and the Device Connect Python packages on an Arm-based Linux machine.
- Run the adapter in device-to-device (D2D) mode and call read-only ROS 2 inspection remote procedure calls (RPCs) from a Python client.
- Describe how deployment profiles map the same adapter onto real hardware such as a Raspberry Pi 5 with a camera.
Prerequisites
Before starting, you'll need the following prerequisites:
- An Arm-based Linux machine, such as a Raspberry Pi 5, an Arm cloud instance, or an Arm-based laptop, running Ubuntu 22.04 or later
- Basic familiarity with Python, the Linux command line, and ROS 2 concepts such as nodes and topics
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll expose a containerized ROS 2 system on Arm-based Linux as a discoverable Device Connect device. You’ll see how the Device Connect adapter wraps ROS 2 commands as RPCs without changing the application. First, you’ll start a ROS 2 Humble container, install the Device Connect packages, and run the adapter in D2D mode. Then, you’ll inspect the ROS 2 graph from a Python client and explore profiles for a Raspberry Pi 5 camera or robot.