micro-ROS / micro-ROS/micro-ROS.github.io
micro-ROS publisher always printing "dat:0" on ROS2 echo instead of the updated values
還沒有人認領這個 Issue。
- 主要語言
- SCSS
- 星號
- 127
- 分支
- 71
- PR 合併指標
- 30 天內沒有已合併 PR
描述
I am working on a micro-ROS example on a TRAVEO™ T2G MCU using a custom UART transport. The code is based on the "data
" style micro-ROS publisher/subscriber example, but I have modified it slightly.
Here is the situation:
-
I have a publisher that is supposed to send an integer value (std_msgs/msg/Int32) periodically using a ROS timer.
-
I am running ros2 topic echo /traveo_publisher on the host PC to see the published messages this will give value never changes to from 0 . it is publishing periodically but within same incorrect value.
-
I am successfully connecting to the ROS 2 agent (no connection error), and I do see messages being published.
-
However, the message always shows data: 0 instead of the value I expect (for example 123 or incrementing numbers).
-
The value does not update continuously as I move around in my code or directory — it just stays the same in ROS 2 echo output.
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從附加的 MAIN.C 6.txt 檔案和 micro-ROS 資料發布者/訂閱者範例開始,然後針對 TRAVEO T2G custom UART transport 執行 ros2 topic echo /traveo_publisher。追蹤 std_msgs/msg/Int32 值在哪裡被指派和發布;當 echo 輸出反映預期值或遞增值,而不是始終顯示 data: 0 時,即表示完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- c
- 領域
- embedded-iot, robotics
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100