Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Multiple Microros agents

未關閉
#235 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
ubuntu

研究方向

從 issue 中描述的兩個 ros2 run micro_ros_agent micro_ros_agent udp4 命令以及 PC 和 VM 各自的位址和連接埠開始。檢視針對多個 agent 和 publisher 情境的 agent 與 client 連線指南,然後為這兩種情況記錄或驗證一個可重現的設定。

由索引模型根據 Issue 內容生成。

描述

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

the ping gets sent
image

and is correctly publishing the expected pings
image

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

主要語言
C++
星號
201
分支
111
平均合併
1 天 6 小時
30 天內合併 PR
10

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

micro-ROS/micro-ROS-Agent 的其他 Issue

查看 micro-ROS/micro-ROS-Agent 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。