yahboom
HomeTutorialsProduct
Solution
Blog
Online Store
About Us
EN/中文
Store
Jetson Orin NANO Developer Kit📖
01.Get started
  • 01. Learning route
  • 02. Get started quickly
  • 03. System Update Notes
  • 04. Disabling automatic updates and troubleshooting issues
  • 05. Jetson Orin Nano official kit screwdriver instructions
02.Jetson basic course
  • 01.Jetson board introduction
  • 02.Write Jetson original system
  • 03.Installing Jetson environment
  • 04.Backup SSD system
  • 05.Restore initial image system
  • 06.Upgrade to SUPER version (Optional)
  • 07.Write SUPER boot (Must read)
  • 08.SSD expansion
  • 09.Jetpack old system upgraded to Yahboom SUPER factory system
  • 10.Write the system onto your own SSD
03.Basic setting course
  • 01.Basic knowledge
  • 02.Network configuration
  • 03.SSH remote login
  • 04.VNC remote control
  • 05.RDP remote control
  • 06.Remote file transfer
  • 07.Jtop tool
  • 08.Exchange space expansion
  • 09.Use VSCode
  • 10.Use VMware
  • 11.Modify screen resolution
04.GPIO control course
  • 01.GPIO description
  • 02.GPIO library installation
  • 03.GPIO reading
  • 04.GPIO output
  • 05.Serial communication
  • 06.I2C communication
05.Vision basic course
  • 01.CSI camera preview
  • 02.USB camera preview
  • 03.Use Jupyter Lab
  • 04.Use JetCam
06.OpenCV basic course
  • 01.Image reading
  • 02.Image saving
  • 03.Image modification
  • 04.Image scaling
  • 05.Image cropping
  • 06.Image translation
  • 07.Image mirroring
  • 08.Image grayscale conversion
  • 09.Image binarization
  • 10.Image edge detection
  • 11.Add line segments
  • 12.Add rectangles
  • 13.Add circular shape
  • 14.Add ellipses
  • 15.Add polygons
  • 16.Add Text
  • 17.Preview USB camera image
  • 18.Preview CSI camera image
07.Vision advanced course
01.Environment construction
  • 01.TensorFlow
  • 02.PyTorch
  • 03.Torchvision
02.DeepStream development
  • 01.DeepStream environment
  • 02.License plate detection and recognition
  • 03.Parallel multi-model inference
  • 04.Object embedding vector generation
  • 05.Pose recognition
  • 06.NV optical flow anomaly detection
  • 07.Single-view 3D tracking
  • 08.Multi-view 3D tracking
03.NVIDIA TAO toolkit application
  • 01.Traffic scene object detection
  • 02.Person object detection
  • 03.Vehicle brand classification
  • 04.Vehicle model classification
  • 05.License plate detection and recognition
  • 06.Person semantic segmentation
  • 07.Retail product detection and recognition
  • 08.Person feature extraction and matching (ReID)
  • 09.Person action and pose classification
  • 10.Transformer-based person detection
  • 11.3D human skeleton detection
  • 12.LiDAR 3D point cloud detection
04.YOLO11 development
  • 01.YOLO environment construction
  • 02.CLI use
  • 03.Object detection
  • 04.Instance segmentation
  • 05.Pose estimation
  • 06.Image classification
  • 07.Oriented object detection
  • 08.Model conversion
  • 09.Dataset annotation
  • 10.Model training conversion
  • 11.Model prediction
05.Mediapipe development
  • 01.Mediapipe environment
  • 02.Hand detection
  • 03.Face detection
  • 04.Face effects
  • 05.3D object recognition
  • 06.Virtual brush
  • 07.Gesture recognition
  • 08.Finger control
  • 09.Posture estimation
  • 10.Face mask
  • 11.Overall detection
  • 12.Green scene removal(Human)
06.YOLO26 development
  • 01.YOLO environment construction
  • 02.CLI use
  • 03.Object detection
  • 04.Instance segmentation
  • 05.Pose estimation
  • 06.Image classification
  • 07.Oriented object detection
  • 08.Model conversion
  • 09.Dataset annotation
  • 10.Model training conversion
  • 11.Model prediction
07.QR code recognition
  • QR code recognition
08.Docker basic course
  • 01.Docker introduction
  • 02.Docker installation
  • 03.Docker command
  • 04.Docker usage
  • 05.Docker interaction
09.ROS2-Jazzy
01.ROS2 basic course
  • 1.Introduction to ROS2
  • 2.ROS2 install Jazzy
  • 3.ROS2 development environment
  • 4.ROS2 workspace
  • 5.ROS2 function package
  • 6.ROS2 node
  • 7.ROS2 topic communication
  • 8.ROS2 service communication
  • 9.ROS2 action communication
  • 10.ROS2 custom interface message
  • 11.ROS2 parameter service case
  • 12.ROS2 meta-function package
  • 13.ROS2 distributed communication
  • 14.ROS2 DDS
  • 15.ROS2 time related API
  • 16.ROS2 common command tools
  • 17.ROS2 rviz2 use
  • 18.ROS2 rqt toolbox
  • 19.ROS2 Launch startup file configuration
  • 20.ROS2 recording and playback tool
  • 21.ROS2 URDF model
  • 22.ROS2 Gazebo simulation platform
  • 23.ROS2 TF2 coordinate transformation
02.ROS2 vision course
  • 01.Camera preview (USB)
  • 02.Camera preview (CSI)
  • 03.Camera calibration (USB)
  • 04.Camera calibration (CSI)
  • 05.AR vision (USB)
  • 06.AR vision (CSI)
10.Large model basic course
01.Offline large model
  • 01.AI large model environment deployment
  • 02.Install large model dialogue platform
  • 03.Meta AI - Llama model
  • 04.Alibaba Cloud - Qwen model
  • 05.Microsoft - Phi-4-mini model
  • 06.DeepSeek - DeepSeek model
  • 07.Alibaba Cloud - Qwen-VL visual multimodal large model
  • 08.Google - Gemma visual multimodal large model
  • 9.Llava visual multimodal large model
  • 10.MiniCPM-V visual multimodal large model
  • 11.High-quality vision-language grounding (LocateAnything)
02.Online large model
  • 01.Tongyi Qianwen large model
  • 02.OpenRouter large model API aggregation platform
11.Large model application practice
01.Voice interaction application
  • 1.Voice interaction hardware connection (Must read)
  • 2.Offline speech to text (ASR)
  • 3.Offline text to speech (TTS)
  • 4.AI large model voice interaction
  • 5.AI large model offline voice assistant
02.Multimodal large model application (Online_Offline large model + Text_Voice interaction)
  • 01.Multimodal visual understand application
  • 02.Multimodal text image application
  • 03.Multimodal video analysis application
  • 04.Multi module visual position application
  • 05.Multimodal table scanning application
  • 06.Multimodal autonomous agent application
12.NVIDIA Isaac ROS course
  • 01.Build Isaac ROS environment
  • 02.Deep segmentation
  • 03.DNN stereoscopic depth
  • 04.Free space segmentation
  • 05.Image distortion processing
  • 06.Image segmentation
  • 07.3D scene reconstruction and mapping
  • 08.Object detection
  • 09.3D attitude estimation
  • 10.Visual SLAM
13.OpenClaw deployment and basic usage
01.OpenClaw deployment and introduction
  • 01.Quick start with the pre-configured environment (Recommended)
  • 02.OpenClaw Deployment
  • 03.OpenClaw WhatsApp Plugin Application
  • 04.OpenClaw WebChat Interaction
  • 05.OpenClaw TUI Interaction
  • 06.OpenClaw Tools Introduction
  • 07.OpenClawGate Gateway User Manual
  • 08.OpenClaw Features Overview
  • 09.OpenClawHub Introduction (Skill Installation)
02.OpenClaw basic application
  • 01.OpenClaw Application - File Management
  • 02.OpenClaw Application - Camera
  • 03.OpenClaw Application - Browser Control
  • 04.OpenClaw Application - Script Execution
  • 05.OpenClaw Application - AI Programming (Peripheral & GPIO Control)
  • 06.OpenClaw Application - Dedicated AI Assistant
  • 07.OpenClaw Web Search Capability Configuration
03.NVIDIA official Agent Skills application
  • 01.AI-assisted development with VS Code or Cursor
  • 02.Jetson device skills
  • 03.Jetson BSP custom agent skills
14.OpenClaw advanced development
01.Preparation Before Use
  • 01.Peripheral Hardware Configuration
  • 02.OpenClaw API-KEY Configuration
  • 03.OpenClaw Model Switching
  • 04.OpenClaw Prompts
  • 05.AI Voice Interaction Configuration
  • 06.Three Dialogue Configuration Tests
02.OpenClaw AI Programming Peripheral Control
  • 1. Servo Control
  • 2. RGB Strip
  • 3. OLED Display
  • 4. Temperature and Humidity Sensor
  • 5. Camera Application
  • 6. AI Script Peripheral Control
03.OpenClaw Peripheral Integration Applications
  • 1. Plant Care Assistant
  • 2. AI Calorie Estimation
  • 3. AI Rock Paper Scissors Game
  • 4. AI Pet
  • 5. AI Weather Station
  • 6. Temperature Humidity Dashboard
  • 7. Scheduled Tasks
Download
  • System_File
  • VMFile_BootFile
  • 3D Model File
  • DataSheet
  • Software_Tools
  • Code
  • Manual
Download ZIP

Welcome to Jetson Orin NANO Developer Kit repository

13.ROS2 distributed communication

13. ROS 2 Distributed Communication

1. Concept

Multi-machine communication, that is, distributed communication, refers to a communication strategy that enables data exchange between different hosts through a network.

ROS 2 itself is a distributed communication framework, which can conveniently implement communication between different devices. The middleware on which ROS 2 is based is DDS. When in the same network, distributed communication can be implemented through the domain ID mechanism of DDS (ROS_DOMAIN_ID). The general process is: before starting a node, you can set the value of the domain ID. If different nodes have the same domain ID, they can freely discover each other and communicate; conversely, if the domain ID values are different, it cannot be implemented. By default, the domain ID used when all nodes start is 0. In other words, as long as you ensure they are in the same network, you do not need to do any configuration, and different nodes on different ROS 2 devices can implement distributed communication.

The application scenarios of distributed communication are relatively wide: unmanned vehicle formation, drone formation, remote control, and so on. The data exchange in all these relies on distributed communication.

2. Implementation

2.1. Default Implementation

You only need to put the host and the slave(s) 【there can be multiple】 in the same network, and distributed communication works. For example, the host and the slave are connected to the same Wi-Fi or the same router.

In Windows, setting the virtual machine network to 【bridged mode】 puts it in the same network as the host.

Test:

  • Here we assume that we have two hosts A and B. They can be hosts that can connect to the network in any form, for example: a virtual machine, Raspberry Pi, jetson, x86/ARM host, card mainboard. They only need to have the same version of the ros2 environment installed.

  1. Execute on host A:

This demo runs the car in Docker with host network mode. In simple terms, host mode means sharing the same network as the car, so there is no difference from executing on the car.

ros2 run demo_nodes_py talker
  1. Execute on host B:

xxxxxxxxxx
ros2 run demo_nodes_py listener

If the following is displayed: the topic published by the host can be subscribed to by the slave in time, which means multi-machine communication has been implemented.

2.2. Distributed Network Grouping

Suppose there are other robots in use in the network you are currently in. To avoid interference from other robots, you can also set a group for your robot.

ROS 2 provides a DOMAIN mechanism, which is similar to grouping. Only computers in the same DOMAIN can communicate. We can add the following configuration line to the .bashrc of the host 【the car】 and the slave 【the virtual machine】 to assign the two to the same group:

xxxxxxxxxx
$ export ROS_DOMAIN_ID=<your_domain_id>

If the ID assigned to the host 【the car】 and the slave 【the virtual machine】 is different, the two cannot communicate, thus achieving the purpose of grouping.

2.2.1. Case 1

  1. Execute on the host 【the car】:

This demo runs the car in Docker with host network mode. In simple terms, host mode means sharing the same network as the car, so there is no difference from executing on the car.

xxxxxxxxxx
echo "export ROS_DOMAIN_ID=6" >> ~/.bashrc  # Here 6 is the ROS_DOMAIN_ID. It does not have to be 6, as long as it conforms to the rules of ROS_DOMAIN_ID
source ~/.bashrc
ros2 run demo_nodes_py talker
  1. At the same time, execute on the slave 【the virtual machine】:

xxxxxxxxxx
echo "export ROS_DOMAIN_ID=6" >> ~/.bashrc  # Here the value is kept the same as on the host
source ~/.bashrc
ros2 run demo_nodes_py listener

If the following is displayed: the topic published by the host can be subscribed to by the slave in time, which means grouped multi-machine communication has been implemented

2.2.2. Case 2

Control the movement of the turtlesim through distributed communication

  • Host A runs the command

xxxxxxxxxx
ros2 run turtlesim turtlesim_node
  • Host B runs the command

xxxxxxxxxx
ros2 run turtlesim turtle_teleop_key

3. Notes

Setting the value of ROS_DOMAIN_ID is not arbitrary, and there are certain constraints:

  1. It is recommended that the value of ROS_DOMAIN_ID be between [0,101], including 0 and 101;

  2. The total number of nodes in each domain ID is limited and needs to be less than or equal to 120;

  3. If the domain ID is 101, the total number of nodes in that domain needs to be less than or equal to 54.

4. DDS Domain ID Value Calculation Rules (Advanced Knowledge)

The relevant calculation rules for domain ID values are as follows:

  1. DDS is based on the TCP/IP or UDP/IP network communication protocol. Network communication requires a specified port number, which is represented by a 2-byte unsigned integer, and its value range is between [0,65535];

  2. The allocation of port numbers also has its rules and cannot be used arbitrarily. According to the DDS protocol, 7400 is used as the starting port, so the available ports are [7400,65535]. It is also known that, according to the DDS protocol, each domain ID occupies 250 ports by default. Then the number of domain IDs is: (65535-7400)/250 = 232, and the corresponding value range is [0,231];

  3. The operating system also sets some reserved ports. When using ports in DDS, these reserved ports also need to be avoided to prevent conflicts during use. The reserved ports differ among different operating systems. The final result is that in Linux, the available domain IDs are [0,101] and [215-231], and in Windows and Mac, the available domain IDs are [0,166]. In summary, for compatibility with multiple platforms, it is recommended that the domain ID take a value within the range of [0,101].

  4. Each domain ID occupies 250 ports by default, and each ROS 2 node needs to occupy two ports. In addition, according to the DDS protocol, within the port segment of each domain ID, the 1st and 2nd ports are the Discovery Multicast port and the User Multicast port, and starting from the 11th and 12th ports are the Discovery Unicast port and the User Unicast port of the first node in the domain. The ports occupied by subsequent nodes follow in sequence. Then the maximum number of nodes in one domain ID is: (250-10)/2 = 120;

  5. Special case: when the domain ID value is 101, the latter half of its ports belong to the reserved ports of the operating system, and the maximum number of nodes is 54.

It is sufficient to understand the above calculation rules.

ROS2 meta-function package
ROS2 DDS

COMPANY

  • About us
  • Team Style
  • Blog

LEARNING & EXPLORATION

  • Tutorials
  • Edge AI hardware
  • Educational robots
  • Embedded intelligent hardware

WHERE TO BUY

  • Yahboom Online Store
  • Amazon
  • Alibaba
  • AliExpress
  • Mercado

TECHNOLOGY SUPPORT

  • Email: support@yahboom.com

BE A DISTRIBUTOR

  • Email: sales@yahboom.com
QR Code

Copyright © 2017-2026 Yahboom. All Rights Reserved.

EN/中文