Question about how to debug communication data between micro-ROS-agent and micro-ROS-client

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
arduino, cpp, linux
领域
devtools, networking

调研方向

先使用 /dev/ttyACM0 及其 -v 选项运行 micro_ros_agent 串行命令，然后检查 micro_ros_arduino 客户端如何与 agent 通信。完成的标准是确定一种切实可行的方法来检查或记录发送和接收的数据，并记录调试方法或工具。

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

描述

Hello.
I'm running micro-ROS-agent on Linux. And micro-ROS-client (I'm running micro_ros_arduino) on the MCU to communicate with the agent.

However, as I've been running micro-ROS, I've noticed a lot of data being sent and received, and the data cycles are fast, so I've been experiencing frequent communication issues.

So, I'd like to know how to identify where communication issues and bottlenecks are occurring in micro-ROS.

As far as I know, changing the log level with the -v option when running micro-ROS-agent itself changes the diversity of the logs.
ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyACM0

However, when I use the -v option to view the data, it's too fast for the human eye. I'd like to either print out the transmitted and received data so it can be viewed by the human eye, or record it.

Is there an easy way to view or record this data, or a way to implement my own code, or a free debugging tool?

Thank you.

主要语言
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 摘要。