micro-ROS publisher always printing "dat:0" on ROS2 echo instead of the updated values

Personne n'a encore pris cette issue.

[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.

Commencez par les fichiers MAIN.C 6.txt joints et l’exemple de publisher/subscriber de données micro-ROS, puis exécutez ros2 topic echo /traveo_publisher avec le TRAVEO T2G custom UART transport. Suivez l’endroit où la valeur std_msgs/msg/Int32 est affectée et publiée ; le travail est terminé lorsque la sortie de echo reflète la valeur attendue ou incrémentée, au lieu d’afficher toujours data: 0.

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