micro-ROS / micro-ROS/micro-ROS.github.io

Call service in Micro-ROS while using custom QOS settings

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

還沒有人認領這個 Issue。

主要語言
SCSS
星號
127
分支
71
PR 合併指標
30 天內沒有已合併 PR

描述

  • Hardware description: Portenta H7 & Ubuntu 22.04 PC
  • Version or commit hash: humble with custom ros2 packages

While using custom QOS Settings as described in https://micro.ros.org/docs/tutorials/advanced/create_dds_entities_by_ref/, creating a client for a service using Micro-ROS fails with an error:
[XMLPARSER Error] Error parsing XML buffer -> Function loadXML

The MicroRos Arduino library has been re-compiled to include custom ROS2 message and service types, and also configured to use custom QOS via references, as explained in the previous link.

The same code can run without that service client, while using different topics and message types, as they have been correctly defined in the "custom_qos.refs". The problem comes in when trying to add a service, as I haven't found a way to set up the QOS for a service and its request/response.

If the MicroRos Arduino library is compiled without the QOS reference setting, the client also works as expected.

So far, I tried to include the service as if it were a topic but using "rs" instead of "rt", according to the ROS Specific Namespace Prefixes standard here. I also tried to replicate the configuration laid out in this ROS2 tutorial, but using a similar approach for the "custom_qos.refs" file did not work.

What's the way moving forward? Is there a way to use both custom QOS settings and ROS2 services in Micro-ROS? Or should I choose only the custom QOS or the services?

Thanks!

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

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

研究方向

在啟用自訂 QoS 參照的 Portenta H7 和 Ubuntu 22.04 設定上重現服務用戶端失敗。先從 custom_qos.refs 以及連結的 Micro-ROS DDS-entities 和 ROS 2 Fast DDS configuration 教學開始,將服務請求/回應名稱與正常運作的 topic 項目進行比較。完成的標準是記錄一個可運作的設定,或確認自訂 QoS 參照與服務之間不相容。

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

評估

技術堆疊
arduino, ubuntu
領域
embedded-iot, networking
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
32/100

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

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