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

Open
#423 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
embedded-iot, robotics

Research direction

Start with the attached MAIN.C 6.txt files and the micro-ROS data publisher/subscriber example, then run ros2 topic echo /traveo_publisher against the TRAVEO T2G custom UART transport. Trace where the std_msgs/msg/Int32 value is assigned and published; done means the echo output reflects the expected or incrementing value instead of always showing data: 0.

Written by the indexing model from the issue text.

Description

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

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

Dominant language
SCSS
Stars
127
Forks
71
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from micro-ROS/micro-ROS.github.io

All issues in micro-ROS/micro-ROS.github.io

Similar issues

More Embedded & IoT issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.