micro-ROS / micro-ROS/micro_ros_arduino

Isolating Micro-ROS topics

Open
#1,612 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
576
Forks
146
PR merge metrics
No merged PRs in 30d

Description

When I add the line 'export ROS_DOMAIN_ID=47' to the bashrc file and then load Micro-ROS, my custom topics are not visible. However, when I comment out the ROS domain ID line, restart the agent, and reload Micro-ROS, my custom topics become visible. I'm stuck and unsure how to properly isolate my Micro-ROS topics without interference from the ROS domain ID and Can anyone provide guidance on how to properly isolate Micro-ROS topics in this setup?

Note:For Isolating the ROS2 topics using ROS_DOMAIN_ID is working fine.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the setup with ROS_DOMAIN_ID=47 in bashrc, then compare topic visibility after restarting the Micro-ROS agent and reloading Micro-ROS. Done means custom Micro-ROS topics remain visible while ROS 2 topics stay isolated; the issue does not name a source file or test to run.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.