[Open Source] DDS AutoDiag v0.1.0 — ROS 2 DDS Diagnostics with AI-Assisted Troubleshooting
[Open Source] DDS AutoDiag v0.1.0 — ROS 2 DDS Diagnostics with AI-Assisted Troubleshooting
DDS AutoDiag v0.1.0 is an independent, MIT-licensed open-source tool for diagnosing ROS 2 communication problems across robots, computers, and containers. It offers 23 diagnostic checks covering DDS discovery, network configuration, middleware settings, and QoS compatibility. The tool provides a graphical interface for visual diagnostics and includes AI-assisted troubleshooting that explains findings, suggests configuration changes, and references curated documentation. Additionally, it supports natural-language instructions to configure RViz visualizations. This is the first public release, with the author seeking community feedback on diagnostic accuracy, missing failure scenarios, and workflow improvements.
DDS AutoDiag v0.1.0 is an independent, MIT-licensed open-source tool developed by Animesh Gunaki to diagnose ROS 2 communication issues across distributed systems, featuring 23 diagnostic checks, a graphical interface, and AI-assisted troubleshooting suggestions.
Source: ROS Discourse — Community updates · Read original article ↗
Article text · Original source · English
Hi ROS community! 
Ever had two ROS 2 systems that could ping each other, use the same ROS_DOMAIN_ID, but still couldn’t discover each other’s topics?
I’ve encountered similar issues while working with distributed ROS 2 systems. Troubleshooting often means manually investigating DDS discovery, middleware configurations, QoS policies, and container networking.
To make this process more systematic, I developed DDS AutoDiag v0.1.0, an independent, MIT-licensed open-source tool for diagnosing ROS 2 communication problems across robots, computers, and containers.
What does it offer?
23 diagnostic checks
Investigates common ROS 2 communication issues, including DDS discovery, network configuration, middleware settings, and QoS compatibility.
Visual diagnostics
Provides a graphical interface to explore diagnostic results and identify potentially broken communication paths.
AI-assisted troubleshooting
Explains diagnostic findings, suggests configuration changes, and references curated ROS 2 documentation to help developers understand the underlying issues.
AI-powered RViz integration
Allows developers to configure supported RViz visualizations through natural-language instructions.
See it in action
Try DDS AutoDiag:
Documentation: DDS AutoDiag - DDS AutoDiag
Looking for community feedback
This is the first public release, and I’d love to hear from developers working with distributed ROS 2 environments.
I’m particularly interested in feedback on diagnostic accuracy, missing failure scenarios, and improvements to the troubleshooting workflow.
If you encounter issues or have suggestions, feel free to open a GitHub issue or contribute!
How do you currently troubleshoot DDS communication failures across multiple ROS 2 systems?
Thanks for taking a look!
Regards,
Animesh Gunaki
What the source reports
Publisher-reported claims, with original evidence. These results have not been independently verified by RoboSignal.
Reported numbers
diagnostic checks
23
View original evidence
Diag v0.1.0, an independent, MIT-licensed open-source tool for diagnosing ROS 2 communication problems across robots, computers, and containers. What does it offer? 23 diagnostic checks Investigates common ROS 2 communication issues, including DDS discovery, network configuration, middleware settings, and QoS compatibility. Visual diagnostics Provides a graphical interface to explore diagnostic results and identify p
Open source S3
- paper: not_reported
Source excerpts and review record
Automatically extracted; no manual editorial approval recorded.
Diag v0.1.0, an independent, MIT-licensed open-source tool for diagnosing ROS 2 communication problems across robots, computers, and containers. What does it offer? 23 diagnostic checks Investigates common ROS 2 communication issues, including DDS discovery, network configuration, middleware settings, and QoS compatibility. Visual diagnostics Provides a graphical interface to explore diagnostic results and identify p
Open source S3
Hi ROS community! Ever had two ROS 2 systems that could ping each other, use the same ROS_DOMAIN_ID , but still couldn’t discover each other’s topics? I’ve encountered similar issues while working with distributed ROS 2 systems. Troubleshooting often means manually investigating DDS discovery, middleware configurations, QoS policies, and container networking. To make this process more systematic, I developed DDS Auto
Open source S2
Hub: GitHub - Animesh2507/dds-autodiag: Tells you why your ROS 2 nodes can't talk to each other, and fixes your RViz view for you. Read-only DDS diagnostics + AI. · GitHub Documentation: DDS AutoDiag - DDS AutoDiag Looking for community feedback This is the first public release, and I’d love to hear from developers working with distributed ROS 2 environments. I’m particularly interested in feedback on diagnostic accu
Open source S5
racy, missing failure scenarios, and improvements to the troubleshooting workflow. If you encounter issues or have suggestions, feel free to open a GitHub issue or contribute! How do you currently troubleshoot DDS communication failures across multiple ROS 2 systems? Thanks for taking a look! Regards, Animesh Gunaki
Open source S6
otentially broken communication paths. AI-assisted troubleshooting Explains diagnostic findings, suggests configuration changes, and references curated ROS 2 documentation to help developers understand the underlying issues. AI-powered RViz integration Allows developers to configure supported RViz visualizations through natural-language instructions. See it in action https://youtu.be/OwRHfeO_ueo Try DDS AutoDiag: Git
Open source S4
Source：ROS Discourse — Community updates · discourse.openrobotics.org