micro-ROS / micro-ROS/micro-ROS-Agent

Multiple Microros agents

未关闭
#235 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
C++
星标
201
派生
111
平均合并
1 天 6 小时
30 天内合并 PR
10

描述

## Issue template

- Hardware description: Using linux PC Ubuntu 22.04.5
- RTOS: none for now later will use teensy 4.0
- Installation type: setting agent in the pc and vm directly without docker
- Version or commit hash: foxy-microros; humble-ros2

#### Steps to reproduce the issue
I used the following commands to run the agent - ros2 run micro_ros_agent micro_ros_agent udp4 --port 2019 (on PC with ip 10.221.38.153) then similarly ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888 (on VM with ip 10.221.38.78)

I want to try vm as one device pc as another run both the microros agents and connect it to the clients to receive the ping messages respectively.

#### Expected behavior
Should be able to run the multiple agents for pc and vm acting as separate devices

#### Actual behavior
I have the agent running
![image](https://github.com/user-attachments/assets/1d417ac3-98c2-4d1f-9f7d-375a25119170)

the ping gets sent
![image](https://github.com/user-attachments/assets/255aa61b-d8cb-40d7-a7b7-c2485f33b08e)

and is correctly publishing the expected pings
![image](https://github.com/user-attachments/assets/d6421b5c-d13e-4e07-98a4-5cb81844d83d)

This is happening in both the devices separately
Could you please help me with further steps on how to connect both the agents(one of pc other of vm) to the respective clients on each device. so for example I have to pub msgs via say vm agent and this msg has to get subscribed to the vm subscriber(connected to pc agent)
Overall I have to try
case 1: multiple agents accessing one publisher
case 2: one agent accessing multiple publisher

#### Additional information
I get the impression that multiple agents is possible and listening to the specific agent has a cmd that gives the particular ip address and port via the clients/nodes or some configuration modification please help with the method

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从 issue 中描述的两个 `ros2 run micro_ros_agent micro_ros_agent udp4` 命令以及 PC 和 VM 各自的地址和端口开始。检查针对多个 agent 和 publisher 场景的 agent 与 client 连接指南,然后为这两种情况记录或验证一个可复现的设置。

由索引模型根据 Issue 内容生成。

评估

技术栈
ubuntu
领域
distributed-systems, networking
Issue 类型
功能
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。