Skip to content

Possible bug with Header message type #821

@pnn16004

Description

@pnn16004

Issue template

  • Hardware description: Arduino Due, ESP32 Feather
  • Installation type: micro-ROS library for Arduino, PlatformIO, VS Code
  • Version or commit hash: Galactic

Steps to reproduce the issue

Implement the micro-ros_subscriber example and change message type to std_msgs/msg/header.

Implement the ROS2 C++ publisher example and change message type to std_msgs/msg/header.

Have them communicate through the micro-ROS Agent on a topic.

Expected behavior

Reach the subscription_callback() function when debugging or see with a serial monitor that it has been reached.

Actual behavior

No sign that it reaches the subscription_callback() function, but the Agent reacts to the publisher the first minute or so, then it stops.
No messages from printf() inside the function and only one response from the printf inside loop().
The debugging goes into some memory files after rclc_executor_spin_some() and never returns to the main code.
These results are for both Arduino Due and ESP32 Feather.
Agent output:
Screenshot from 2022-03-10 22-14-08

Additional information

I implemented ping pong peng applications in micro-ROS with Arduino, ESP-IDF, and STM32CubeIDE.
Using the Header message type, the ping side works with all of them, but the pong side didn't work in Arduino, even though the code functionalities were identical.
Thus I tried with these basic examples and it doesn't work either, so I suspect it might be the message type, as I tried the same examples but with Int32 and it worked.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions