micro-ROS / micro-ROS/rmw_microxrcedds

Questions about the RMW_UXRCE_PUBLISH_RELIABLE_TIMEOUT parameter

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

Nobody has claimed this yet.

Dominant language
C
Stars
47
Forks
36
Avg merge
2d 19h
Merged PRs (30d)
6

Description

Hello?
I have a few questions about the RMW_UXRCE_PUBLISH_RELIABLE_TIMEOUT parameter.

When I read the description of RMW_UXRCE_PUBLISH_RELIABLE_TIMEOUT, it said that it is the default time to wait for publish. Can you tell me if my understanding is correct?

* Reference address: https://github.com/micro-ROS/rmw_microxrcedds

What I understand is that RMW_UXRCE_PUBLISH_RELIABLE_TIMEOUT is the time it takes to wait for permission to publish when a publisher with reliable settings calls the publish function.

* Reference address(Reliable QoS) : https://micro.ros.org/docs/tutorials/programming_rcl_rclc/qos/

However, looking at the address below, it says that RMW_UXRCE_PUBLISH_RELIABLE_TIMEOUT is the blocking time or waiting time for approval while the spin function is called and publish is being processed. When publish is called from the spin function, is this the time waiting for permission for the operation? Or is the blocking time while processing publish correct?
Or is what I understood wrong and different?

Can you explain the RMW_UXRCE_PUBLISH_RELIABLE_TIMEOUT parameter?

Thank you.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the RMW_UXRCE_PUBLISH_RELIABLE_TIMEOUT description in the rmw_microxrcedds documentation and compare it with the linked Reliable QoS tutorial. Trace the referenced publish and spin behavior only as far as the existing documentation identifies it; done means the parameter's waiting and blocking semantics are explained unambiguously.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
distributed-systems
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.