Selecting a ROS 2 RMW for a Wi-Fi Mobile Robot Fleet
Pick the right ROS 2 RMW for a Wi-Fi robot fleet: Fast DDS with Discovery Server avoids multicast issues and stays license-free on ROS 2 Jazzy.
Loading…
ReadMeFeed / Community knowledge
#ros-2
Real questions. Useful conversations. Find the people who know your stack.
rosSpawning a Custom URDF Model in Gazebo with the ROS 2 spawn_entity Service
Learn how to load a custom URDF robot into Gazebo Classic using the ROS 2 /spawn_entity service, including prerequisites, the exact service call, verification steps, and recovery options for common mesh and naming failures.
gazeboHarnessing ROS 2 Lifecycle Nodes: A Practical Guide to Reliable Robot Software
Unpredictable node startup leads to race conditions in ROS 2. Managed lifecycle nodes expose explicit states—unconfigured, inactive, active, finalized—providing deterministic startup, shutdown, and error handling. Guide shows the state machine, a minimal C++ example, and integration with launch.
Gazebo Classic vs. Modern Gazebo (gz-sim): A Decision Guide for Robotics Teams
Gazebo Classic 11 is end-of-life. This guide compares Classic with modern Gazebo (gz-sim) across architecture, physics, ROS integration, and migration cost, then shows a concrete validation path.
Fine‑Tuning ROS 2 DDS QoS: Reliability, Durability, and Cross‑Node Compatibility
Learn how to adjust ROS 2 DDS Quality‑of‑Service (QoS) settings to balance latency and message reliability, verify correct profiles across nodes, and recover from common mis‑configurations.
ROS 2 rosbag2 Guide: Record, Inspect, and Replay Topics for Debugging
Learn how to record, inspect, and replay ROS 2 topics with rosbag2 for reliable debugging and regression testing. Follow step‑by‑step commands, checks, and recovery options to ensure deterministic playback.
Managing Deterministic Robot Behavior with ROS 2 Lifecycle Nodes
ROS 2 Lifecycle nodes let you control node state transitions—unconfigured, inactive, active, cleanup, shutdown—ensuring predictable behavior. This blog walks through a sample node, shows how to trigger transitions, and discusses trade‑offs and best practices.
FastDDS discovery cache behavior change in ROS 2 when nodes terminate abruptly
Goal: identify FastDDS configuration parameters that minimize the duration of stale participant entries after a node is terminated abruptly without generating excessive multicast traffic. Constraints include variation across DDS implementations (FastDDS vs CycloneDDS), dependence on network latency, and the trade‑off between rapid dead‑node detection and hea