Skip to content

Conversation

@JiangengDong
Copy link
Contributor

Description

In the Kconfig file, an MTU is defined. However, it is not passed to the Colcon build system, which means the MicroROS client always uses the default MTU, which is 512. This causes the publisher to always fail when sending a message larger than 500 bytes.

In this PR, one line is added to the makefile, so the configured_colcon.meta will have the correct MTU set.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

  • A 1024 byte message (uint32[256]) is published from a nucleo-f746zg board to a laptop. The MTU is set to 1036 in the prj.conf. It succeeds to get the message on the laptop with ros2 topic echo.

Signed-off-by: Jiangeng Dong <dongjiangeng@gmail.com>
@pablogs9 pablogs9 requested review from Acuadros95 and pablogs9 April 20, 2022 06:21
Copy link
Member

@pablogs9 pablogs9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Acuadros95
Copy link
Contributor

LGMT.

As a comment, you can send and receive messages longer than the MTU over reliable entities, chech this: docs

@Acuadros95 Acuadros95 merged commit 9be2009 into micro-ROS:galactic Apr 20, 2022
@Acuadros95
Copy link
Contributor

@mergify backport main foxy

@mergify
Copy link
Contributor

mergify bot commented Apr 20, 2022

backport main foxy

✅ Backports have been created

Details

Acuadros95 added a commit that referenced this pull request Apr 20, 2022
Pass the MTU config from Zephyr to colcon (backport #53)
Acuadros95 added a commit that referenced this pull request Apr 20, 2022
Pass the MTU config from Zephyr to colcon (backport #53)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants