micro-ROS / micro-ROS/micro_ros_espidf_component
Micro-ros Ping utility issue
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 419
- Forks
- 124
- Avg merge
- 21h 35m
- Merged PRs (30d)
- 3
Description
## Issue template
- Hardware description: esp32s3 devkit
- RTOS: freertos
- Installation type: standard
- Version or commit hash: humble
#### Steps to reproduce the issue
try the rmw_uros_ping_agent() utility to see whether the Agent is up or not it does not require creating a micro-ros context first...
#### Expected behavior
When I turn the Agent on it should output as RMW_RET_OK else it should throw an error value
#### Actual behavior
There is a variable called agent_state_flag in the code which gives 0 when agent is off and 1 when agent is on...
Here I have not started the agent yet
Here I have started the agent
Still it the rmw_uros_ping_agent() is not giving me a RMW_RET_OK even when the agent is alive
#### Additional information
The code snippet which I am using...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported rmw_uros_ping_agent() entry point and reproduce the behavior on the ESP32-S3 with the Agent stopped and running. Compare its return value with the reported agent_state_flag values and the expected RMW_RET_OK result. Done means the utility reliably distinguishes an available Agent from an unavailable one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100