Node (ROS 2)
- In French:
- Nœud (ROS 2)
Definition
The unit of computation of a ROS 2 system, which ideally should fulfil a single function, such as reading a sensor or driving a motor. Nodes communicate through topics, services and actions, whether they run in the same process, in different processes or on different machines. A node can also expose parameters that can be adjusted at run time.
Checked on against the references below. · Written with AI · checked against the sources Source: Official ROS 2 documentation (Jazzy), “Nodes”.
Concrete examples
On the TurtleBot 4, the official manual describes turtlebot4_node as the node that handles the robot’s human-machine interface and other logic. It subscribes to topics such as battery_state, calls services such as e_stop and robot_power and actions such as dock and undock, and exposes four parameters, including menu.entries.
What it changes for you
Grouping nodes into processes is a trade-off. According to Stereolabs’ documentation, separate processes give fault isolation and easier debugging of individual nodes, while a single process has lower overhead.
Not to be confused with
A node is not a process: the ROS 2 composition demo uses the rclcpp_components API to compose several nodes in a single process, which avoids the cost of marshalling messages between processes.
Additional material checked on .