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

Personne n'a encore pris cette 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.

* Note: Github address of the micro-ROS-client library I am running
https://github.com/micro-ROS/micro_ros_arduino

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.

Commencez par la commande série de micro_ros_agent utilisant /dev/ttyACM0 et son option -v, puis examinez comment le client micro_ros_arduino communique avec l’agent. Le travail est terminé lorsqu’une manière pratique d’inspecter ou d’enregistrer les données transmises et reçues a été identifiée et que l’approche ou l’outil de débogage a été documenté.

Rédigé par le modèle d'indexation à partir du texte de l'issue.