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
描述
[MAIN.C 6.txt](https://github.com/user-attachments/files/21734883/MAIN.C.6.txt)
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
[MAIN.C 6.txt](https://github.com/user-attachments/files/21734876/MAIN.C.6.txt)
" style micro-ROS publisher/subscriber example, but I have modified it slightly.
Here is the situation:
1. I have a publisher that is supposed to send an integer value (std_msgs/msg/Int32) periodically using a ROS timer.
2. 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.
3. I am successfully connecting to the ROS 2 agent (no connection error), and I do see messages being published.
4. However, the message always shows data: 0 instead of the value I expect (for example 123 or incrementing numbers).
5. 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