ROS 2 intra-process communication and composition explained
ROS 2 composition loads several nodes into one process, and intra-process communication passes messages between them without serialisation or a middleware hop.
Evergreen explainers, how-tos and hardware comparisons for robotics developers. Written to stay useful and updated as the tooling changes.
ROS 2 composition loads several nodes into one process, and intra-process communication passes messages between them without serialisation or a middleware hop.
ROS 2 lifecycle nodes add a managed state machine to drivers and servers: configure, activate, deactivate and clean up in a deliberate order.
Nav2 is the ROS 2 navigation stack: a behavior tree driving planner and controller servers over costmaps, with lifecycle nodes and recovery actions.
ROS 2 launch files start a whole system: nodes, parameters, remappings, namespaces and event handlers. How launch and launch_ros split the work.
How ROS 2 executors run callbacks, what callback groups change about concurrency, and why a synchronous service call inside a callback deadlocks.
How ROS 2 QoS policies work: reliability, durability, history, depth, deadline and liveliness, the preset profiles, and why a topic sometimes reaches nobody.
rosbag2 captures ROS 2 topics, services and clock data into bags you can replay later. How recording, inspection, compression and playback work in ros2 bag.
Topics stream continuous data, services answer a request, actions run long tasks with feedback. How the three ROS 2 interfaces work, and how to choose.
A spec-verified comparison of the Jetson Orin Nano and Orin NX modules from NVIDIA's official documentation: compute, memory, power modes, I/O and ROS 2 fit.
NVIDIA Isaac Sim is an open source robotics simulator built on Omniverse and OpenUSD, with PhysX and Newton physics, RTX sensors, and Python plus ROS 2 workflows.
ROS 2 is the open-source framework most modern robots run on. This guide covers its client libraries, middleware, nodes, topics, services, actions and tooling.